Tom,
I think you meant to send this to pvfs2 mailing list as well! cc'ing
pvfs2-users..
Glad that things are working finally for you!
As part of mount, you need to specify the file system name, not the
storage space directory..
That is why you are seeing this error (-ENODEV). The PVFS faq on
www.pvfs.org (if the website is up) is also a good source for common
errors/using the pvfs tools etc etc
mount -t pvfs2 tcp://node5:3334/pvfs2-fs /mnt/pvfs2
should do the trick.
pvfs2-ping is definitely one good source of troubleshooting.
I think Sam/Phil also had some other tools (pvfs2-validate?) that I think
they are most qualified to answer about.
Regards,
Murali
On 6/6/07, Tommy Butler <[EMAIL PROTECTED]> wrote:
Solution: download and install debian kernel for bigmem, kernel headers for
bigmem, make kernel modules under /usr/src/linux, make pvfs2 and pvfs2.ko,
insmod works.
Now... does pvfs2 offer any troubleshooting tools other than pvfs2-ping?
mount -t pvfs2 tcp://node5:3334/pvfs2-storage-space
/mnt/pvfs2
mount: tcp://node5:3334/pvfs2-storage-space: unknown device
contents of /etc/pvfs2tab:
tcp://node5:3334/pvfs2-storage-space /mnt/pvfs2 pvfs2
default,noauto 0 0
node5:~# ps aufx|grep pvfs
root 29911 0.0 0.0 30764 2468 ? Ssl 00:56 0:00
/usr/local/sbin/pvfs2-server --pidfile /var/run/pvfs2.pid /etc/pvfs2-fs.conf
/etc/pvfs2-server.conf-node5
root 18562 0.0 0.0 3300 388 ? Ss 13:55 0:00
pvfs2-client
root 18563 0.0 0.8 36296 24988 ? S 13:55 0:00 \_
pvfs2-client-core -a 5 -n 5 -L /tmp/pvfs2-client.log
node5:~# cat /etc/pvfs2-server.conf-node5
StorageSpace /pvfs2-storage-space
HostID "tcp://node5:3334"
LogFile /tmp/pvfs2-server.log
node5:~# cat /etc/pvfs2-fs.conf
<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
</Defaults>
<Aliases>
Alias lvsdirector2 tcp://lvsdirector2:3334
Alias lvsdirector1 tcp://lvsdirector1:3334
Alias node1 tcp://node1:3334
Alias node2 tcp://node2:3334
Alias node3 tcp://node3:3334
Alias node4 tcp://node4:3334
Alias node5 tcp://node5:3334
Alias sqlcluster1 tcp://sqlcluster1:3334
Alias sqlcluster2 tcp://sqlcluster2:3334
</Aliases>
<Filesystem>
Name pvfs2-fs
ID 66846137
RootHandle 1048576
<MetaHandleRanges>
Range lvsdirector2 4-238609297
Range lvsdirector1 238609298-477218591
Range node1 477218592-715827885
Range node2 715827886-954437179
Range node3 954437180-1193046473
Range node4 1193046474-1431655767
Range node5 1431655768-1670265061
Range sqlcluster1 1670265062-1908874355
Range sqlcluster2 1908874356-2147483649
</MetaHandleRanges>
<DataHandleRanges>
Range lvsdirector2 2147483650-2386092943
Range lvsdirector1 2386092944-2624702237
Range node1 2624702238-2863311531
Range node2 2863311532-3101920825
Range node3 3101920826-3340530119
Range node4 3340530120-3579139413
Range node5 3579139414-3817748707
Range sqlcluster1 3817748708-4056358001
Range sqlcluster2 4056358002-4294967295
</DataHandleRanges>
<StorageHints>
TroveSyncMeta yes
TroveSyncData no
</StorageHints>
</Filesystem>
Thank you all.
--
Tommy Butler
On 6/4/07, Murali Vilayannur < [EMAIL PROTECTED]> wrote:
> Rebuild the kernel, all the modules including pvfs2 with the same
> sources and config options
> and compiler. Reboot and reload pvfs2 and let us know what errors you get.
> In fact, I am now convinced that the bug that you see is because of a
> compiler issue.
> The kernel is expecting arguments to this function on registers and I
> think we may be passing it on the stack or something!
> So lets isolate those issues as well.
> thanks!
> Murali
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
