(btw, i first sent this accidentally to egroups.....)

eventually i started fscking a little after 04:40, and it was fully done
at about 6:10 (i fsck-ed twice, once with badblocks checking, once
without). the output of the first run is at ~choo/fsck.errors . the second
run resulted no errors, as expected.

note the (probably) damaged files in the log - they should be re-fetched,
i guess.

i'll check the log files during the weekend to see if more errors will be
found.

guy

"For world domination - press 1,
 or dial 0, and please hold, for the creator." -- nob o. dy



Reply via email to