-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 23 Aug 2003 00:03:43 -0600, Rodolfo J. Paiz wrote:
> Will "sparsing" or "unsparsing" the file (whichever is the one that fixes > the problem) eliminate those blank spaces? I have 40M files that (after > being copied to a second hard drive) show up correctly with "ls -sh" but > then show up as 950MB files in "ls -l". > > If I do "cp --sparse=always" or "rsync -av --sparse", will the file be > returned to its normal real size? Will it still have all those blanks in > it? And is there a way for me to check whether or not this is indeed my > problem? Please see my other thread earlier today labeled "File sizes > reported incorrectly (and huge!)" for more detail. The problem with your WAV files is not that they contain sparse blocks. If they did, they would not sound good, because you would hear every blank block. And since they are listed as 20 times the original size, you would hear a lot of "silence", and each of them would play for several hours. ;) But as you've mentioned, two arbitrary "1GB songs" still sound good. Just out of curiousity, what do you get when you gzip such a huge file, transfer it to another machine and gunzip it? - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/RyIf0iMVcrivHFQRApkVAJoCDqWiqXFy0KFFmciSFtlln9jcRACeKVi6 5pVfV6eMFNXDZ1c4upE2yRI= =CT2E -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
