Re: NFS bug, 2.1.57 from Solaris 2.6 server
Todd T. Fries (toddf@acm.org)
Mon, 29 Sep 1997 19:50:12 -0500
On Sep 29, Steven N. Hirsch wrote
> > $ :>1 ; :>2 ; :>3 ; mkdir 4 ; mv * 4
> > mv: cannot move `4' to `4/4': Operation not permitted
> > $ ls -lF
> > total 0
> >
> > It doesn't make any difference what order the files and directory are
> > made. Nor does it matter if there is anything already in the
> > directory; it is always removed. I think it is necessary for the
> > directory name to be the last filename mv tries to rename. That is,
> >
> > $ :>2 ; :>3 ; :>4 ; mkdir 1 ; mv * 1
> > mv: cannot move `1' to `1/1': Operation not permitted
> > $ ls -lF
> > total 0
> > -rw-r--r-- 1 agriffis network 0 Sep 29 14:20 1
> >
> > mv 1 2 3 4 4 <-- produces bug (first example)
> > mv 1 2 3 4 1 <-- doesn't produce bug (second example)
> >
>
> Bill Hawes is in the midst of heavy debugging on the NFS client. This is
> a known problem resulting from the d_entry stuff.
Problem? You think there's a problem with the normal behavior of not being
able to move a subdirectory within itself? I'd call that sane behavior:
$ mkdir grin
$ mv grin grin
mv: cannot move `grin' to `grin/grin': Invalid argument
$
--
Todd Fries .. todd@heuris.com