Quote:
Originally Posted by blue68f100
You have more patients than I do. Taking that long it tells me it's in pretty bad shape.
|
I would believe that too, except that it's leaving no traces in the logs that it has run into any problems. Early on, it was indicating read errors on a single block, but nothing like that since.
If it was just redoing the same blocks over and over I'd also agree, but it seems to be going through all the blocks, and not just those on Disk 1.
My best guess is it's doing some kind of integrity check on the blocks and i-nodes, and because the RAID was over 90% full (I know, I should have left at least 10% free) it's probably running this slow because it doesn't have much swap space. My past logs indicate that it didn't have much fragmentation:
10/13/2008 15:25:19 35 I L01 | File System Check : 4333039 files, 44150094 used, 5206842 free (0 frags, 5206842 blocks, 0.0%% fragmentation)
The above is from the last time it had to do a rebuild (power failure longer than an hour, UPS could only keep it running 40 minutes).
As I said at the start, I'm mainly doing this as an aid to help anyone else with this problem. None of the data on this Snap is critical, so I'm going to be patient and let it do what it's doing and then see what happens.
In my wanderings on the web I've come across this link,
Snap Server File System, maybe it'll prove to be a help to others.