On Wed, 2005-11-23 at 11:34 -0700, Brian D. Haymore wrote:
> We found a new quirk with our current build of 1.3.0 with the following
> patches applied: enable_fast.patch fedora_kernels_acl.patch
> statecomp.patch timestamps.patch zfill-fixup.patch. The quirk is only
> seen when you sftp attach to a box that has the pvfs2 space mounted and
> try to sftp a file out of the pvfs2 space back to the remote sftp
> client. Scp works just fine however. This quirk from the best we can
> tell was introduced in this last build of pvfs2 with the above listed
> patches and did not exist before then. This is not a show stopper as we
> have just told users to use scp instead and for this user who was using
> winscp that only means clicking the scp button. I've tested both
> windows sftp clients and linux sftp cli clients and the problem exists
> for both. So my guess is that this has something to do with how the
> sftp server portion is accessing the pvfs2 space. Thoughts?
Is the behavior you're seeing that the sftp client transfers the whole
file and then hangs waiting for the moral equivalent of an EOF? I see
the same behavior with the CVS version we're currently using
(1.3.1pre1-2005-11-03-215456 according to pvfs2-ls --version). The file
system remains usable on the sftp server side, and the entire contents
of the file get transferred -- you just have hit cntl-C to get out of
the sftp session if you're using the CLI version.
--Troy
--
Troy Baer [EMAIL PROTECTED]
Science & Technology Support http://www.osc.edu/hpc/
Ohio Supercomputer Center 614-292-9701
_______________________________________________
PVFS2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
