NW3.12 vol gets excessive vrepair errors
NW3.12 vol (soon to go to 4.11) must be
vrepaired every day. The thing begs to be
put out of its misery, and I plan to do
that with a conversion over the wire to a
new 4.11 server.
But before that high-wire act, I need to
find out where the vrepair errors are
coming from. A typical day will result in
between 15,000 to 20,000 (you read that
correctly) errors. And, yes, the poor
little vol is backed up religiously every
evening.
My vrepair settings (as I can remember them)
are
1. write all changes to disk immediately
2. no pause between errors
3. keep no error log
