[PVFS-developers] another 1.6.3pre1 bug

[Porter Don]

I tracked this one down a bit further.  It only happens when one uses
kpvfsd.  The user-space daemon seems to work fine.  The only changes that
have happened were the mtime patch, which was only applied to the pvfsd
code, not the kpvfsd code.  Thus, the kpvfsd is no longer speaking the same
protocol as the other pieces.

This is not the first time we have had this problem with the two code bases.
If we weren't trying to move away from pvfs1, it would almost be worth the
trouble to consolidate some of that code with some judicious #define's.  

In the meantime, we all need to keep an eye out for this when making
changes.

Hopefully I can figure out what else has changed and get a patch out on the
list.

Thanks,
don

-----Original Message-----
From: Porter  Don
To: 'pvfs-developers at www.beowulf-underground.org'
Sent: 4/30/04 12:21 PM
Subject: [PVFS-developers] another 1.6.3pre1 bug

It seems that the 1.6.3pre1 has started getting incorrect ENOSPC's in
the
kernel module.

[root at jawa063 floppy]# ls -l
total 83968006
-rw-r--r--    1 root     root          156 Apr 30 12:17 a
drwxr-xr-x    1 dmethe   dmethe       4096 Apr 30 10:06 foo/
-rw-r--r--    1 root     root           78 Apr 30 11:40 i
-rw-r--r--    1 doport   doport        468 Apr 30 12:16 interactive
-rwxrwxr-x    1 doport   doport   42991616000 Apr 23 10:32 testfile*
-rw-r--r--    1 doport   doport   42991616000 Apr 27 14:58 testout
[root at jawa063 floppy]# cat i >> a
cat: write error: No space left on device
[root at jawa063 floppy]# ls -l
total 83968006
-rw-r--r--    1 root     root          234 Apr 30 12:17 a
drwxr-xr-x    1 dmethe   dmethe       4096 Apr 30 10:06 foo/
-rw-r--r--    1 root     root           78 Apr 30 11:40 i
-rw-r--r--    1 doport   doport        468 Apr 30 12:16 interactive
-rwxrwxr-x    1 doport   doport   42991616000 Apr 23 10:32 testfile*
-rw-r--r--    1 doport   doport   42991616000 Apr 27 14:58 testout

=================================

The cat seems to work, so perhaps the bug is in close...  I can't
replicate
the bug in 1.6.2 or my patched version of 1.6.0.  My guess is that I
screwed
something up in dropping fsize, but I am still looking.  Any
thoughts/suggestions are welcome.

Thanks,
don
_______________________________________________
PVFS-developers mailing list
PVFS-developers at www.beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs-developers