Chuck: It does sound like you are having the same problem as Andrew. Which linux version are you running? Andrew is running 3.2.14.
I am working with Andrew to resolve this problem. It definitely seems to be a kernel module issue where incorrect metadata is being kept. I was not able to reproduce the problem on older kernels using OrangeFS 2.8.5, so I assume the problem is some incompatibility with the newer kernels. Please let me know which kernel you are using. Thanks, Becky Ligon On Tue, May 29, 2012 at 9:06 PM, Chuck Cranor <[email protected]> wrote: > On Tue, May 29, 2012 at 05:55:49PM -0400, Chuck Cranor wrote: > > a little more info: > > > > it seems to be related to unlinking a file and then creating a new > > file with the same name. I tried an overwrite first, and that was ok. > > > ... and umount'ing the PVFS mount and then remounting it clears the error: > > h1# cat /m/pvfs/data > retest > h1# ssh h0 rm /m/pvfs/data > h1# > h1# echo newdata | ssh h0 dd of=/m/pvfs/data > 0+1 records in > 0+1 records out > 8 bytes (8 B) copied, 0.0299092 s, 0.3 kB/s > h1# cat /m/pvfs/data > cat: /m/pvfs/data: No such file or directory > h1# cat /m/pvfs/data > cat: /m/pvfs/data: Input/output error > h1# ls -ls /m/pvfs > ls: cannot access /m/pvfs/data: Input/output error > total 16 > 4 -rw-r--r-- 1 chuck plfs 4 2012-05-29 21:00 bar > ? ?????????? ? ? ? ? ? data > 4 drwxrwxrwx 1 root root 4096 2012-05-29 16:58 lost+found > 4 -rw-r--r-- 1 chuck plfs 11 2012-05-29 17:09 prime.msg > 4 -rw-r--r-- 1 chuck plfs 4 2012-05-29 17:51 renamed > h1# > h1# umount /m/pvfs > h1# mount -t pvfs2 tcp://h1:3334/pvfs2-fs /m/pvfs > h1# cat /m/pvfs/data > newdata > h1# > > > > chuck > -- Becky Ligon OrangeFS Support and Development Omnibond Systems Anderson, South Carolina
_______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
