Hi list,
I expierienced the following problem:
When I create a volume, I can add a replication site, and can release it
without problems.
But when I copy some data to it, and try to release I get the error
"Volume needs to be salvaged" and the VolderLog tells:
VAttachVolume: Error reading large
Ralf Hornik (Mailings) wrote:
Hi list,
I expierienced the following problem:
When I create a volume, I can add a replication site, and can release it
without problems.
But when I copy some data to it, and try to release I get the error
"Volume needs to be salvaged" and the VolderLog tells:
VA
Hi Jason,
> Have you tried running 1.4.6?
No because on windows I can only use 1.5.3* which appears to be stable.
And I prefer to use the same version on server and clients.
But I will try out version 1.4.6 and give then short feedback.
Thanks
Ralf
Ralf Hornik (Mailings) wrote:
Hi Jason,
Have you tried running 1.4.6?
No because on windows I can only use 1.5.3* which appears to be stable.
And I prefer to use the same version on server and clients.
Windows 1.5.3x is production quality.
UNIX 1.5.3x is not. We say this in every announcem
Hi,
> Windows 1.5.3x is production quality.
> UNIX 1.5.3x is not. We say this in every announcement.
Sorry, I didn't receive announcements yet.
1.4.6 seems to work now.
Thank you and best regards
Ralf
___
OpenAFS-info mailing list
OpenAFS-info@opena
> 1.4.6 seems to work now.
Unfortunalely, the problem still exists. :-(
1 Volser: ListVolumes: Could not attach volume 536870922
(/vicepa:V0536870922.vol), error=101
VAttachVolume: Error reading namei vol header /vicepa/V0536870921.vol;
error=101
VAttachVolume: Error attaching volume /vicepa/V053
Am Mittwoch, 12. März 2008 schrieb ext Ralf Hornik (Mailings):
> After salvaging (bos salvage server daten) the Volume (daten) now is
> completely unusable:
>
> [EMAIL PROTECTED]:~# ls -al /afs/.daheim/daten/
> insgesamt 4
> drwxrwxrwx 4 root root 2048 2008-03-12 13:31 .
> drwxrwxrwx 2 root root 2
Hi,
> Hmm, I wonder if this really is a salvager problem. Did you compile with
GCC
> 4.2.x? If yes, try recompiling with 4.1.x. See
> http://www.nabble.com/Strange-access-problems-on-one-client-to12112808.html
Ubuntu 7.10 amd64 uses gcc-4.1 and the volume or at least the damaged
files where not a