Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2008-04-06 at 11:17 -0400, Sam Clemens wrote:
rsync --archive --acls --xattrs --hard-links --del --stats --human-readable /oldhome /newhome/
add --sparse
Yep, it's possible.
Or a lot of destination files could take up significantly more disk space than on the old disk drive.
¿A lot? No, shouldn't be a lot.
It depends on his data. Suppose a program does this: opens a file does an lseek 5000000000 writes one character and closes. That's a sparse file. All but the last character are zeros. In the above example, it only takes one block , or maybe a bit more to store...the inode or whatever structure containing mostly block pointers that point to null (indicating that the entire block is full of zeroes), or even indirect or doubly-indirect pointers pointing to null (indicating that all of the blocks which they would be pointed to by the list of direct pointers are full of zeroes). Only the last block actually needs to be recorded on disk. Now... say you do ls -l sparsefile You'll see the size indicated as 500000000001 but if you do ls -s sparsefile you'll see that it only takes up one or a couple blocks. of disk space. Now do cat < sparsefile > sparseback ls -l sparse* both files will have the same byte counts. ls -s sparse* sparsefile will still be the original size sparseback will use up millions of blocks cp --sparse=always sparsefile sparseback ls -l sparse* and ls -s sparse* will now indicate that sparse-back is both the same size, AND the same amount of disk space He might have no sparse files..or he might run some application which creates many. Who knows unless we know every app that he runs. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org