-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 24 Aug 2003 21:28:18 -0600, Rodolfo J. Paiz wrote:
> > Well, you could try unsparsing a file.. it's a blind shot, it makes no > >sense, but it's worth a try (on the smallest huge file). > > > >cp --sparse=always big.wav test.wav > > That's actually how I ended up on this thread... no one was paying me any > attention on my other attempts to get help on this issue, and sparse files > sounded like a possible explanation so I went through the thread and made > attempts to sparse or unsparse with both cp and rsync. > > No dice... I still get 1.2GB worth of file, yet the darn thing plays > properly in a media player and displays correctly in certain incantations > of ls. Because it makes no sense. The proposed "unsparsing the file" would expand the empty blocks and create a file that occupies as much space on disk as normal "ls -l" shows. What you would need in case of sparse files with lots of omitted blocks at the end, is a way to _cut off_ the files at the end. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Sfm50iMVcrivHFQRArVuAJ975eaxSC4lqNcFNRnXhxed1G6BKACfSZuI 6L37F90XwMpuDmHg3VYztE8= =LdKr -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
