"Grant Peel" <[EMAIL PROTECTED]> writes: > Is there any way to figure out the files that are not being read using the > DUMP error output below? > > DUMP: read error from /dev/da0s1g: Input/output error: [block 42718592]: > count=8192 > DUMP: read error from /dev/da0s1g: Input/output error: [sector 42718594]: > count=512 > DUMP: read error from /dev/da0s1g: Input/output error: [block 42671366]: > count=5120 > DUMP: read error from /dev/da0s1g: Input/output error: [sector 42671371]: > count=512
I had such a problem just last night. I tracked it down by copying directory trees within the filesystem to /dev/null until one failed. Then I repeated the process one directory level down, narrowing down the problem. [It turned out to be my wife's incoming mail spool...] _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
