[OpenAFS] Problem with vos release

[Lars Schimmer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Derrick J Brashear schrieb:
| On Tue, 14 Jun 2005, Lars Schimmer wrote:
|
|> And every night a vos release copy this volume to a readonly copy.
|> That should do it without problems, but it doesn't.
|>
|> the RW copy holds:
|> - -rw-rw----  1 mysql mysql   748 2005-06-14 14:53 flyspray_users.MYD
|> - -rw-rw----  1 mysql mysql  2048 2005-06-14 14:54 flyspray_users.MYI
|>
|> After a vos realease flyspray the RO copy holds:
|> - -rw-rw----  1 mysql mysql  560 2005-06-13 17:02 flyspray_users.MYD
|> - -rw-rw----  1 mysql mysql 2048 2005-04-08 15:11 flyspray_users.MYI
|>
|> And yes,vos release flyspray
|> Released volume flyspray successfully
|>
|> was printed out before.
|> WHAT the heck is wrong?
|
|
| what if you vos release -force?

Same effect.
Just for more information:
I mount the RW volume in our cell as RW mountpoint, and beside that
mountpoint I mounted the RO volume explicit RO as volumereadonly mountpoint.
After the vos release flyspray -force I went to /path/flyspray made a ls
- -l (no change, how could it), and further on I went to
../flysprayreadonly and made a ls -l. And it prints out the same as above.
There is only ONE RO copy of that volume. So I assume I made everything
right. If not, I´m eager to learn.

Btw, this could be the reason why we lost 1 month of flyspray entrys for
one project, nothing so important to fire me, but important enough for
me to understand the reason.
And yes, it´s mysql data on AFS, til a machine crash a few days ago it
went well for nearly half a year now.

Is it still not wise to save mysql database on AFS?

Thx so far,
Lars
- --
- -----------------------------------------------------------------
Technische Universität Braunschweig, Institut für Computergraphik
Tel.: +49 531 391-2109            E-Mail: schimmer@cg.cs.tu-bs.de
PGP-Key-ID: 0xB87A0E03
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCr/GlVguzrLh6DgMRAnktAJ9R7jnUj5zJLa6LpoAmKxHgpoD23wCfRdMr
4aTSDJKn5EkRa+1xSkmCIYg=
=M1QX
-----END PGP SIGNATURE-----