Jay Soffian jay@cimedia.com writes:
Do parity errors during a disk scrub necessarily indicate something is wrong with the filesystem?
Not neccessarily.
this rather distressing. The filer really needs a way to perform a filesystem health check w/o downtime.
Like running fsck on a mounted filesystem? Some things are better done in a quiesced state...
NA also needs to publish accurate timing data on wack via NOW. The only document I can find has ancient data.
There are way too many variables to that equation. It depends on the version of the OS, the version of wack, etc. I have seen times when running the incorrect version of wack yielded 3 hour wack's (before someone mentioned this should not be the case; we restarted with the proper version).
A similar table that would be nice is raid reconstruct speeds based on volume size, filer load and disk size. Now that would be interesting.. :)
Alex