check the clock of the machine. there may be a clock skew error.
To find out the real rx level error, use fs trace.
* fs trace -on -reset
* dir \\afs\ltu.se
* fs trace -dump -off
* examine contents of %windir%\temp\afsd.log
Jeffrey Altman
Anders Magnusson wrote:
We have one XP SP3 machine
Rich Sudlow wrote:
Giovanni Bracco wrote:
What is the situation for partitions larger than 2 TB?
...
See the attached script as a workaround for fixing the 32 bit issue.
We call the script quota in our cell.
Rich
Thank you, the script is very useful!
Giovanni
Hello,
When I was running vos syncvldb on my fileserver, I got error:
Could not create a VLDB entry for the volume 536870944
VLDB: volume entry exists in the vldb
Could not process entries on server psrwjmsafs1.umdnj.edu partition /vicepe
VLDB synchronized with state of server psrwjmsafs1
On Wed, 02 Dec 2009 12:11:52 -0500
Wenping Yang yan...@umdnj.edu wrote:
Hello,
When I was running vos syncvldb on my fileserver, I got error:
Could not create a VLDB entry for the volume 536870944
VLDB: volume entry exists in the vldb
Could not process entries on server
Andrew Deason wrote:
On Wed, 02 Dec 2009 12:11:52 -0500
Wenping Yang yan...@umdnj.edu wrote:
Hello,
When I was running vos syncvldb on my fileserver, I got error:
Could not create a VLDB entry for the volume 536870944
VLDB: volume entry exists in the vldb
Could not process entries
On Wed, 02 Dec 2009 12:36:12 -0500
Wenping Yang yan...@umdnj.edu wrote:
[r...@psrwjmsafs1 logs]# vos listvl 536870944
VLDB: no such entry
[r...@psrwjmsafs1 logs]# vos listvol psrwjmsafs1 |grep 536870944
gives no output.
Run the syncvldb with the -verbose flag, and show any output around
Time is correct (always checked first :-)
The log output doesn't tell me anything, but maybe someone
else: /afs/ltu.se/tests/error091202/afsd.log
-- Ragge
Jeffrey Altman wrote:
check the clock of the machine. there may be a clock skew error.
To find out the real rx level error, use fs trace.
Andrew Deason wrote:
On Wed, 02 Dec 2009 12:36:12 -0500
Wenping Yang yan...@umdnj.edu wrote:
[r...@psrwjmsafs1 logs]# vos listvl 536870944
VLDB: no such entry
[r...@psrwjmsafs1 logs]# vos listvol psrwjmsafs1 |grep 536870944
gives no output.
Run the syncvldb with the -verbose
On Wed, 02 Dec 2009 13:27:40 -0500
Wenping Yang yan...@umdnj.edu wrote:
with -verbose flag, it didn't give any more info for 536870944 except
this:
[r...@psrwjmsafs1 logs]# vos syncvldb psrwjmsafs1 -verbose |grep
536870944 VLDB: volume entry exists in the vldb
Could not create a VLDB entry
19270401 = Packet too short for security challenge
by any chance is there a firewall or router in the path that blocks udp
fragments?
Anders Magnusson wrote:
Time is correct (always checked first :-)
The log output doesn't tell me anything, but maybe someone
else:
On Wed, 2 Dec 2009 12:44:09 -0600
Andrew Deason adea...@sinenomine.net wrote:
On Wed, 02 Dec 2009 13:27:40 -0500
Wenping Yang yan...@umdnj.edu wrote:
with -verbose flag, it didn't give any more info for 536870944
except this:
[r...@psrwjmsafs1 logs]# vos syncvldb psrwjmsafs1 -verbose
Andrew Deason wrote:
On Wed, 2 Dec 2009 12:44:09 -0600
Andrew Deason adea...@sinenomine.net wrote:
On Wed, 02 Dec 2009 13:27:40 -0500
Wenping Yang yan...@umdnj.edu wrote:
with -verbose flag, it didn't give any more info for 536870944
except this:
[r...@psrwjmsafs1 logs]# vos
12 matches
Mail list logo
