Greetings!

Thanks for the help! I was not aware of the swapon / swapoff, and that gave me a clean FSCK of drive0. I am running it on drive1 now. The drive1 file system was mounted, but still gave that error. The FSCK I am running now was done on the devicename, and seems to be proceeding.

That is one scary looking error! Last time I saw superblock problems on a UNIX box was with Solaris 2.6, and I was backing up and rebuilding the box for far longer than I care to remember...

Hopefully, the FSCK will stabalize things a bit. Meanwhile, I took the precaution of getting emplode csv dumps at a few steps in the process. I will compare these to see if I can find out what went missing, if there was any pattern, etc.

=====

The FSCK came back clean on both drives. The csv dumps were too few and far between to be of much good. I will start taking snapshots, and uploading any missing files.

Paul G.
SN# 090000587 (96GB Smoke)

Edited by pgrzelak on 31/07/01 01:26 PM.