??,?: ??????: [PVFS2-developers] how to overcome PVFS2's these unstable errors?

[Rob Ross]

Perhaps the check is on the directory in those cases?

Rob

On Wed, 2 Jun 2004 neillm at mcs.anl.gov wrote:

> Just a note regarding this past issue (see below).
> 
> On Tue, Mar 23, 2004 at 11:35:35AM -0600, neillm at mcs.anl.gov wrote:
> > [ ... bringing some other part of our discussion back on list ]
> > 
> > Hello Wenguo,
> > 
> > On Tue, Mar 23, 2004 at 09:03:02AM +0800, Wenguo WEI wrote:
> > > [root at lc1 iozone]# tar -xvf ../iozone3_217.tar 
> > > src/current/Changes.txt
> > > src/current/iozone.c
> > > docs/iozone.1
> > > src/current/makefile
> > > src/current/libasync.c
> > > src/current/libbif.c
> > > src/current/gnuplot.dem
> > > src/current/gengnuplot.sh
> > > src/current/Generate_Graphs
> > > tar: src/current/Generate_Graphs: Cannot utime: Permission denied
> > > tar: src/current/Generate_Graphs: Cannot change ownership to uid 26031, gid 1021: Permission denied
> > > src/current/gnu3d.dem
> > > tar: src/current/gnu3d.dem: Cannot open: Broken pipe
> > > 
> > > NOW THE PROBLEM APPEAR. we don't have any user with uid equal to 26031, otherwise it should display username (right?). WHY IT CAN UNTAR FRONT FILES BUT HAVE PROBLEM WITH Generate_Graphs? and we check pvfs2-server status:
> > 
> > I've narrowed this down to a bug in the pvfs2-server that fails the
> > permission check for the operation.  Since your user is root, I'm not
> > sure why it fails for you, but I can reproduce something similar when
> > running as a 'normal' user (and it'll probably all make sense when the
> > bug is fixed).
> > 
> > --
> > neillm at sahara test $ tar -xvf iozone3_196.tar 
> > src/current/Changes.txt
> > src/current/iozone.c
> > tar: src/current/iozone.c: Cannot utime
> > docs/iozone.1
> > tar: docs/iozone.1: Cannot utime
> > src/current/makefile
> > tar: src/current/makefile: Cannot utime
> > src/current/libasync.c
> > <snip>
> > --
> > 
> > In this case the server side permission check (in prelude.sm) is
> > failing to allow the setattr operation to occur, causing the client
> > side utime error (perm denied).  This is something to look into.
> 
> This problem was caused by tar unpacking a file with permissions that
> didn't include user write permission, which our server was *requiring*
> for a setattr operation.  It turns out that other file systems don't
> require write access to a file to set the attributes (via utime,
> touch, etc), so I've modified this for now.  Our
> permission/credential/permissions/access-control system needs work, so
> I'm sure it'll change over time when we decide what exact behaviours
> we want to honor.  I'm not even sure this fixes all of the cases (as
> it doesn't happen on all setups I'm running on to begin with), but
> it's a start.
> 
> -Neill.
> _______________________________________________
> PVFS2-developers mailing list
> PVFS2-developers at beowulf-underground.org
> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
> 
>