[...]
Just some entries when everything seemed fine...
17:54:42 VAttachVolumeById: vol 1000008 (baierv.0) attached and online
17:54:42 create: volume 1000008 (baierv.0) created
17:54:42 S_VolSetLogParms: res flag on volume 0x1000008 set to 0 (resolution
disabled)
17:54:42 S_VolSetLogParms: volume 1000008 log parms set
VLDB created. Search lengths: RO 0, RW 1, BK 0.
When the server is coming up, does it show things like 'volume foo
attached'?
Yes, it does:
09:34:13 VAttachVolumeById: vol 1000001 (/.0) attached and online
09:34:13 VAttachVolumeById: vol 1000002 (anadel.0) attached and online
09:34:13 VAttachVolumeById: vol 1000003 (tautschn.0) attached and online
09:34:13 VAttachVolumeById: vol 1000004 (annap.0) attached and online
09:34:13 VAttachVolumeById: vol 1000005 (apommer.0) attached and online
09:34:13 VAttachVolumeById: vol 1000006 (arafat.0) attached and online
09:34:13 VAttachVolumeById: vol 1000007 (arndt.0) attached and online
09:34:13 VAttachVolumeById: vol 1000008 (baierv.0) attached and online
09:34:13 Attached 8 volumes; 0 volumes not attached
(this is fine, no more volumes existed then)
The reports of the volumes I created:
09:36:37 VAttachVolumeById: vol 100000a (bas.0) attached and online
09:36:37 create: volume 100000a (bas.0) created
09:36:37 S_VolSetLogParms: res flag on volume 0x100000a set to 0 (resolution
disabled)
09:36:37 S_VolSetLogParms: volume 100000a log parms set
VLDB created. Search lengths: RO 0, RW 1, BK 0.
09:36:38 VRDB created, 10 entries
09:36:41 Creating new log for root vnode
09:36:41 VAttachVolumeById: vol 100000b (beaudry.0) attached and online
09:36:41 create: volume 100000b (beaudry.0) created
09:36:41 S_VolSetLogParms: res flag on volume 0x100000b set to 0 (resolution
disabled)
09:36:41 S_VolSetLogParms: volume 100000b log parms set
VLDB created. Search lengths: RO 0, RW 5, BK 0.
09:36:41 VRDB created, 11 entries
09:36:44 Creating new log for root vnode
09:36:44 VAttachVolumeById: vol 100000c (brandtf.0) attached and online
09:36:44 create: volume 100000c (brandtf.0) created
09:36:44 S_VolSetLogParms: res flag on volume 0x100000c set to 0 (resolution
disabled)
09:36:44 S_VolSetLogParms: volume 100000c log parms set
VLDB created. Search lengths: RO 0, RW 6, BK 0.
09:36:45 VRDB created, 12 entries
09:36:47 Creating new log for root vnode
Getvolumelist gets the list of volumes this server is reponsible for.
The VLDB contains the list of all volume in your realm (i.e. on all
possible servers). Since the server isn't returning anything useful for
getvolumelist, it seems like it doesn't know there actually were volumes
created.
...
On the off chance, do you happen to run linux and have the ipv6 kernel
module loaded? I found an rpc2 problem which prevented the SFTP
sideeffects from completing because volutil sends packets with an ipv4
address but receives the responses from the corresponding ipv4-in-ipv6
address and it concludes someone is trying to fool it and drops the
replies.
...
Hmm, I do run linux and the ipv6 module is loaded; Should the new
rpc2-version fix this issue? I'll try and report ...
Thanks,
Michael
