Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
if you backup a full partition there is no used/free space, this information is not available.
If you backup files/dirs you can obviously skip "free" space. You can use for example rsync to do that.
if you backup a full partition there is no used/free space, this information is not available.
Tools like partclone can produce a backup that does not include a supported filesystem's free space. Partclone's image format includes only the used space, and can optionally be compressed. If you play the game right with losetup, you can even produce a mountable sparse file that looks like the original filesystem but does not allocate any disk blocks for the free space.
Tools like partclone can produce a backup that does not include a supported filesystem's free space. Partclone's image format includes only the used space, and can optionally be compressed. If you play the game right with losetup, you can even produce a mountable sparse file that looks like the original filesystem but does not allocate any disk blocks for the free space.
yes, partclone works on the filesystem, but dd has no any idea about that (including partclone.dd).
If it were recent I could tell you. I remember a lot of frustration, vaguely recalling it could have been the file system (NTFS). It was also very slow (I use old computers).
What if we had room to clone the whole disk then split the .img before compressing each chunk after? I mull the possibilities.
I also need to learn why defragmenting is "trimming" the disk instead of the old graphical read/write routine. If it works the partition could be shrunk to used + required space.
Normally you'd move the files to be contiguous. Then you'd Zero out free space.
I know what that means about not why it is a suggestion. If you .tar'd a partition that could be an archive if accurately replicated, not having to worry about what else is on a source disk.
Quote:
One can actually use windows backup feature on a hidden partition if they unhide it.
Windows has a default system backup I use, but I need a Linux version.
Quote:
If you have a way to attach a WD drive they offer a free Acronis version that works great. Attach can be isci I think too.
If you can download it as owner of a drive that sounds good.
Quote:
Clonezilla is normally a file by file clone if it can read the filesystem.
Again, the goal is to skip the unused space, split into manageable chunks, & ideally compress, but maybe not all in one step if done manually.
And the question is again, what have you tried, what went wrong? What do you want to achieve?
If you have windows/ntfs better to use windows based tools to make backups.
Why do you need linux at all?
Zeroing the free space has a "side effect": you can easily backup the whole partition without storing all of those the zeroes (called sparse file).
But anyway, as far as I see you want to backup files, and you have a solution already. It will automatically skip free space. Tar can make an archive like that, including splitting and compressing too.
If you have I/O errors you need to fix them first, but it looks like it is not important. Copying 240GB may take some time, and there is no tool to overcome hardware limitations (if any).
Would backup all of a windows "boot" partition with free/empty space compressed to almost nothing. (if it did not fail with an error)
For example, the 100 mb "boot" partition which was standard on windows7, results in a backup file "test.bin.gz" of less than 10 mb.
Of course, you would substitute the partition you want to backup in "if=/dev/", and put it's size (in mb) in "count="
This has worked for me for backing up fairly large windows partitions. But it can backup any partition that you can read from (even "hidden" partitions), no matter what filesystem/files it contains.
Quote:
Originally Posted by JASlinux
If it were recent I could tell you. I remember a lot of frustration, vaguely recalling it could have been the file system (NTFS). It was also very slow (I use old computers).
What if we had room to clone the whole disk then split the .img before compressing each chunk after? I mull the possibilities.
I also need to learn why defragmenting is "trimming" the disk instead of the old graphical read/write routine. If it works the partition could be shrunk to used + required space.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.