[Pvfs2-users] seqfault on "cp" when using pvfs2's kernel module

Matt langelino at gmx.net
Wed Jun 7 19:48:00 EDT 2006


Dear all,

with the help of Murali and Sam I finally resolved my  pvfs2-cp error
(see the "pvfs2-cp fails" thread).  Special thanks to Murali for  his help!

What is still unresolved is the seqfault of the "cp" command when I try
to copy
something on my pvfs2 mounted tree:
-----------8<----------------
[root at node1 pvfs2]# mount | grep pvfs2
tcp://node1:3334/pvfs2-fs on /mnt/pvfs2 type pvfs2 (rw)
[root at node1 pvfs2]# pwd
/mnt/pvfs2
[root at node1 pvfs2]# ls -l
total 6436
drwxrwxrwx  1 root root    4096 Jun  6 22:29 lost+found/
-rw-rw-rw-  1 root root 3291038 Jun  7 09:26 testfile
[root at node1 pvfs2]# cp testfile testfile3
Segmentation fault
[root at node1 pvfs2]# cp testfile /root/testfile2
cp: setting attributes for UHåHì: Operation not supported
----------->8----------------

The last message indicates some attribute setting problems. 
Interestingly, "scp" fails
like cp when copying out of the pvfs2 filesystem while it succeeds
without seqfault
if the target is remains on pvfs2:
-----------8<----------------
[root at node1 pvfs2]# scp testfile /root/testfile4
cp: setting attributes for UHåHì: Operation not supported
[root at node1 pvfs2]# scp testfile testfile4
----------->8----------------


My storage areas are on ext3 filesystems.  My pvfs2-fs.conf and pvfs2tab
are attached.
I'm running yesterday's (06/06/06) CVS version.

... Matt

-------------- next part --------------
tcp://cree:3334/pvfs2-fs /mnt/pvfs2 pvfs2 default,noauto 0 0
-------------- next part --------------
<Defaults>
	UnexpectedRequests 50
	LogFile /tmp/pvfs2-server.log
	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 cree tcp://cree:3334
	Alias node1 tcp://node1:3334
	Alias node10 tcp://node10:3334
	Alias node11 tcp://node11:3334
	Alias node12 tcp://node12:3334
	Alias node2 tcp://node2:3334
	Alias node3 tcp://node3:3334
	Alias node4 tcp://node4:3334
	Alias node5 tcp://node5:3334
	Alias node6 tcp://node6:3334
	Alias node7 tcp://node7:3334
	Alias node8 tcp://node8:3334
	Alias node9 tcp://node9:3334
</Aliases>

<Filesystem>
	Name pvfs2-fs
	ID 670884255
	RootHandle 1048576
	<MetaHandleRanges>
		Range cree 4-330382102
	</MetaHandleRanges>
	<DataHandleRanges>
		Range node1 330382103-660764201
		Range node10 660764202-991146300
		Range node11 991146301-1321528399
		Range node12 1321528400-1651910498
		Range node2 1651910499-1982292597
		Range node3 1982292598-2312674696
		Range node4 2312674697-2643056795
		Range node5 2643056796-2973438894
		Range node6 2973438895-3303820993
		Range node7 3303820994-3634203092
		Range node8 3634203093-3964585191
		Range node9 3964585192-4294967290
	</DataHandleRanges>
	<StorageHints>
		TroveSyncMeta yes
		TroveSyncData no
		AttrCacheKeywords datafile_handles,metafile_dist
		AttrCacheKeywords dir_ent, symlink_target
		AttrCacheSize 4093
		AttrCacheMaxNumElems 32768
	</StorageHints>
</Filesystem>


More information about the Pvfs2-users mailing list