Hi Tommy,
That is really weird..
Your config files all look ok to me..
Were all the servers pointed to the same config files when they were started?
Servers are assigned meta handle ranges and data handle ranges. i.e
they take owner ship
of handle ranges and requests are sent to those servers from the client.
What the error message says below is that the handle for the root
inode does not seem to be claimed by any server which means that it is
outside of any of the servers assigned ranges which is extremely weird
in this case since all the config files appear to be ok here..
SOmething else is going on or you found an elusive bug with the config
files stuff..
thanks,
Murali
On 6/7/07, Tommy Butler <[EMAIL PROTECTED]> wrote:
Can anyone help me understand this error (pasted in at the bottom of this
email)? After reading over the FAQ for a second time, as Murali suggested,
I still find no clues as to what I should do to fix this.
In order to aid in troubleshooting, I've put all the configuration files I
have for the pvfs2 cluster in a tgz file at
www.atrixnet.com/tmp/pvfs2-configs.tgz
As a side note, if anyone is wondering why there are only config files for
lvsdirector2, node1, node2, and node5, it is because those are the only
nodes that will start the pvfs2 server and are able to mount the pvfs2
filesystem, despite identical configurations and identical hardware (all
machines are ibm zseries 1U rack mounts with 4G ram and 2Gz CPU, IDE bus.
And now, the error from pvfs2-ping when issued from node5:
node5:~# pvfs2-ping -m /mnt/pvfs2/
(1) Parsing tab file...
(2) Initializing system interface...
(3) Initializing each file system found in tab file: /etc/pvfs2tab...
PVFS2 servers: tcp://node5:3334
Storage name: pvfs2-fs
Local mount point: /mnt/pvfs2
/mnt/pvfs2: Ok
(4) Searching for /mnt/pvfs2/ in pvfstab...
PVFS2 servers: tcp://node5:3334
Storage name: pvfs2-fs
Local mount point: /mnt/pvfs2
meta servers:
tcp://lvsdirector2:3334
tcp://node1:3334
tcp://node2:3334
tcp://node5:3334
data servers:
tcp://lvsdirector2:3334
tcp://node1:3334
tcp://node2:3334
tcp://node5:3334
(5) Verifying that all servers are responding...
meta servers:
tcp://lvsdirector2:3334 Ok
tcp://node1:3334 Ok
tcp://node2:3334 Ok
tcp://node5:3334 Ok
data servers:
tcp://lvsdirector2:3334 Ok
tcp://node1:3334 Ok
tcp://node2:3334 Ok
tcp://node5:3334 Ok
(6) Verifying that fsid 1665071444 is acceptable to all servers...
Ok; all servers understand fs_id 1665071444
(7) Verifying that root handle is owned by one server...
Root handle: 1048576
Failure: check root handle failed
PVFS_mgmt_setparam_all: Detailed per-server errors are available (error
class: 0)
Exactly one server must own the root handle.
In this setup, no servers own the root handle.
Per-server errors:
=============================================================
The PVFS2 filesystem at /mnt/pvfs2/ appears to have problems.
--
Tommy Butler
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
