Hello,
I haven't seen that error message in that particular context before. In
general, though, it happens on startup when the server finds that it has
a handle (storage object) in its directory that doesn't match the ranges
specified in the configuration file.
In this specific case it thinks there is a handle with value 0 in your
storage space, which shouldn't happen.
Has the server ever started successfully, or is this the first attempt
to get it running?
You may want to try just deleting the storage space (the
/usr2/pvfs-storage directory) and redoing the "-f" step, if you haven't
already.
You could also try running this command:
pvfs2-showcoll -s /usr2/pvfs-storage -c pvfs2-fs
That should list all of the handles in the storage space so that we can
confirm if there is really bad data in there or if there is something
wrong with the server's startup.
-Phil
Mark J. Hoy wrote:
Hi -
I'm trying to get PVFS2 version 2.7.1 (latest stable) up and running -
It compiles correctly without issue and to initialize my storage (via
"pvfs2-server -f /path/to/config/file" ) - but I'm having a problem
getting the server to start...
every time I try running "sbin/pvfs2-server /path/to/config/file" (where
/path/to/config/file is my configuration file generated via
pvfs2-genconfig), I keep getting an error: Error: handle 0 is invalid
(out of bounds)
The relevant pieces of the log are shown below:
[D 06/27 13:32] PVFS2 Server version 2.7.1 starting.
[E 06/27 13:32] Error: handle 0 is invalid (out of bounds)
[E 06/27 13:32] Error adding handle range
3-1317624576693539402,2635249153387078803-3952873730080618202 to
filesystem pvfs2-fs
[E 06/27 13:32] Error: Could not initialize server interfaces; aborting.
[E 06/27 13:32] Error: Could not initialize server; aborting.
This seems to happen both using a single-machine configuration, and
during a cluster configuration (with 6 machines) - _but_ in the multiple
machine configuration, it only happens when I try and start the first
I/O node - the other 5 machines startup without issue.
Has anyone else experienced this sort of problem? I've attached a copy
of my configuration file below (but changed the machine names to protect
the innocent). Also, I'm running on a homogeneous configuration where
all six of my machines are running Fedora Core 5, kernel: Linux version
2.6.19.1-001-K8, Dual-Core AMD Opteron(tm) Processor (model 1218, 2.6
GHz), 4GB RAM, and 400 GB of storage on the volume for pvfs2
<Defaults>
UnexpectedRequests 50
EventLogging none
LogStamp datetime
BMIModules bmi_tcp
FlowModules flowproto_multiqueue
PerfUpdateInterval 1000
ServerJobBMITimeoutSecs 30
ServerJobFlowTimeoutSecs 30
ClientJobBMITimeoutSecs 300
ClientJobFlowTimeoutSecs 300
ClientRetryLimit 5
ClientRetryDelayMilliSecs 2000
StorageSpace /usr2/pvfs-storage
LogFile /tmp/pvfs2-server.log
</Defaults>
<Aliases>
Alias server1 tcp://server1:3334
Alias server2 tcp://server2:3334
Alias server3 tcp://server3:3334
Alias server4 tcp://server4:3334
Alias server5 tcp://server5:3334
Alias server6 tcp://server6:3334
</Aliases>
<Filesystem>
Name pvfs2-fs
ID 1375400306
RootHandle 1048576
<MetaHandleRanges>
Range server1 3-1152921504606846977
Range server6 1152921504606846978-2305843009213693952
</MetaHandleRanges>
<DataHandleRanges>
Range server1 2305843009213693953-3458764513820540927
Range server2 3458764513820540928-4611686018427387902
Range server3 4611686018427387903-5764607523034234877
Range server4 5764607523034234878-6917529027641081852
Range server5 6917529027641081853-8070450532247928827
Range server6 8070450532247928828-9223372036854775802
</DataHandleRanges>
<StorageHints>
TroveSyncMeta yes
TroveSyncData no
</StorageHints>
</Filesystem>
Thanks!
_______________________________________________
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
