[26961] in Athena Bugs
Re: linux 9.4.30: nautilus
daemon@ATHENA.MIT.EDU (Robert Basch)
Tue Sep 12 19:22:03 2006
In-Reply-To: <200609121825.k8CIP20l016599@dewey.mit.edu>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <200B1EA1-545A-4038-B9EE-83EFC61F61AB@mit.edu>
Content-Transfer-Encoding: 7bit
From: Robert Basch <rbasch@mit.edu>
Date: Tue, 12 Sep 2006 19:21:46 -0400
To: Matthew Goldstein <austein@mit.edu>
X-Spam-Score: 1.217
X-Spam-Level: * (1.217)
X-Spam-Flag: NO
Cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
On Sep 12, 2006, at 2:25 PM, Matthew Goldstein wrote:
> Attempting to copy a file from my homedir to the directory
> which I had AFS write access to returned the error "Not on the same
> file system" from nautilus. Creating a subdirectory which I owned
> yielded the same error. Also, copying a file from the other user's
> Public to my homedir generated the same error again.
> Copying files from the local machine to both the other user's
> Public and to my homedir worked.
Were you trying to copy or move the file? I can reproduce the
error when trying to move a file, but copy works OK.
The move error occurs when the source and target are in
different AFS volumes. The offending code assumes that
it should be able to use rename() when the source and
target are on the same file system, but the check for the
latter only tests whether they are on the same device, as
returned by stat(); that will be true for any paths in AFS.
The rename() fails when the paths are in different volumes,
though.
There are other cases where this rename() assumption is
a bad one, and there is actually a GNOME bug filed on this
(http://bugzilla.gnome.org/show_bug.cgi?id=309592). A
proposed patch was attached to the bug report a while ago,
but progress on it seems to have stalled. We will look into
this further...
Thanks for reporting this.
Bob
