J. Seth Henry wrote:
It crapped out on /rescue. On the SCSI disk, /rescue is 3.5MB. When I checked the ATA drive after stopping the copy, the directory was at 95MB (and the filesystem hopelessly full at 109%). I tried again using copy with the same results. Then, I tar'ed the folder, and extracted the tar file to the ATA drive. That worked, the folder was 3.5MB just like the SCSI drive. I found I could move files reliably from the SCSI drive to the ATA drive using tar, but not cp.
I can (so far) copy files between slices on the same disk with cp without error. For example, I can copy a binary from /usr to /, and the file is identical.
Sorry, I can't explain the rest of your problems, but I can explain this one.
The files that you see in /rescue are actually all hard links to one file (check it with ls -li and you see that they all have the same inode number).
And from man cp we read:
Note that cp copies hard linked files as separate files. If you need to preserve hard links, consider using tar(1), cpio(1), or pax(1) instead.
Cheers, -- Toomas _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
