Hi, On Tue, 26 Feb 2008 08:51:02 +0100, Peter Jeremy <[EMAIL PROTECTED]> wrote:
[...] But it also has some gotchas. The biggest one is that dump needs to be able to write past EOM (so it can record an end-of-volume block).
Just even I tried the following: -create a 50MB filesystem (with md) -put 29MB data on it -create 3 10MB md-devices -dump the 50MB filesystem at the three 10MB devices -restore the file into another, fresh 50MB filesystem Restore reported no error, all files are there and the number of used inodes is the same. Also the md5 checksum above all files does not differ. Since I'm almost sure that the md-devices does not allow to write behind the EOM signal this test would be an equvilalent to the SIGPIPE to SIGEOM thing. (Regardless how I implement this at the end.) So it doesn't seem that dump can handle such an abrupt EOM. This evening I'll try to change dump to interprete SIGPIPE like SIGEOM. Best regards, Martin L. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
