Juha Jäykkä wrote:
In my understanding you easily can propagate this error to your
readonly replicas by "vos release"ing the corrupt volume. The volserver
on the receiving side would remove any data not mentioned in the dump
stream.
This is frightening. Can I actually vos release the corrupt volume? From
the posts on the list, I'd gather it cannot even be attached - how could
it be released, then?
If it can't be attached anymore, probably not. But I don't know whether
it really won't come online after the salvager has thrown away the root
directory!
Better you do a "vos convertROtoRW" on the RO-site as soon as possible
to regain a valid RW-volume in this case.
Except that I'm unlikely to notice the corruption before it's released,
which happens automatically. Sounds like we need to change our backup
policy...
The best way to prevent the salvager from corrupting volumes is not to
run it automatically. If you configure your OpenAFS with with
"--enable-fast-restart" then the fileserver will not salvage
automatically after a crash. So if you find after a ccrash volumes which
couldn't be attached you salvage them by "bos salvage server partition
volume" and examine the SalvageLog. I suppose in the case he throws the
root-directory away you will see some thing in the log.
Hartmut
-Juha
--
-----------------------------------------------------------------
Hartmut Reuter e-mail [EMAIL PROTECTED]
phone +49-89-3299-1328
RZG (Rechenzentrum Garching) fax +49-89-3299-1301
Computing Center of the Max-Planck-Gesellschaft (MPG) and the
Institut fuer Plasmaphysik (IPP)
-----------------------------------------------------------------
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
