On 2011-02-28 09:35, Derrick Brashear wrote:
is the host multihomed perchance? in any case it's a EINVAL being
passed back on the socket.
does the command complete? i assume so, and they are spurious errors
from (well, via) the kernel. it's not your fault in any case.
Some more information.
Did not think about that issue and wanted to rename another volume.
Same error, at the end:
rx failed to send packet: rx_sendmsg: Invalid argument
Could not start transaction on the rw volume 1702193389
Possible communication failure
Error in vos rename command.
Possible communication failure
And afterwards:
vos exa 1702193389
rx failed to send packet: rx_sendmsg: Invalid argument
rx failed to send packet: rx_sendmsg: Invalid argument
Could not fetch the information about volume 1702193389 from the server
Possible communication failure
Error in vos examine command.
Possible communication failure
Dump only information from VLDB
user.aschiefe
RWrite: 1702193389 ROnly: 1702193390 Backup: 1702193391
number of sites -> 4
server 0.0.0.3 partition /vicepc RW Site
server 0.0.0.2 partition /vicepa RO Site
server 0.0.0.5 partition /vicepb RO Site
server 0.0.0.3 partition /vicepc RO Site
That does look strange.
A vos exa of existing volumes does show usual, correct values.
MfG,
Lars Schimmer
--
-------------------------------------------------------------
TU Graz, Institut für ComputerGraphik & WissensVisualisierung
Tel: +43 316 873-5405 E-Mail: [email protected]
Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
