On Sat, Jun 7, 2008 at 11:19 AM, Art Alexion <email@example.com
> I should remember this from the "what is a file?" December meeting. I've run
> into a problem backing up a precarious HD to another. The target drive is
> 500 GB, but I am running into "no space left on drive" after 182 GB.
> IIRC, the original filesystem may have been created by dd_rescue in the course
> of backing up a 200 GB drive with ~100 GB of data from a 111 GB partition. I
> am trying to add another 101 GB from another drive and it is failing for lack
> of space. cfdsk reports that the partition is ~500 GB, so I assume this is
> an inode problem.
> Short of starting over with some other strategy is there anything I can do?
> Rsync output below:
> building file list ... rsync: opendir "/mnt/m4/lost+found" failed: Permission
> denied (13)
> rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
> rsync: write failed
> on "/media/esata/m4/csny1969-12-06e.flac16/03-Long_Time_Gone.flac": No space
> left on device (28)
> rsync: connection unexpectedly closed (36 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(454)