"Jay" == Jay Soffian jay@cimedia.com writes:
Jay> On one of our filers, the first disk scrub that ran after the Jay> upgrade (6 days after the upgrade) found a bunch on parity Jay> inconsistencies:
Some additional questions:
Do parity errors during a disk scrub necessarily indicate something is wrong with the filesystem?
Is there any way to verify the health of a filesystem short of running wack? All outward appearances indicate that the filesystem is okay.
NA is now recommending that I run wackz off of 5.3.1D1 ASAP ('tonight or tomorrow night'). For a device we count on for 100% uptime, I find this rather distressing. The filer really needs a way to perform a filesystem health check w/o downtime. NA also needs to publish accurate timing data on wack via NOW. The only document I can find has ancient data.
j. -- Jay Soffian jay@cimedia.com UNIX Systems Engineer 404.572.1941 Cox Interactive Media