Bug 438116

Summary:	[sr# 1795478] nautilus/gnome-vfs - Can't move files between different NFS mounts
Product:	Red Hat Enterprise Linux 5	Reporter:	ritz <rkhadgar>
Component:	gnome-vfs2	Assignee:	Tomáš Bžatek <tbzatek>
Status:	CLOSED ERRATA	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.1	CC:	llim, riek, syeghiay, tao, tsmetana
Target Milestone:	beta
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-01-13 12:09:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ritz 2008-03-19 07:43:59 UTC

Description of problem:
When trying to move files from one nfs share to another nfs share, Nautilus
shows an error dialog stating "Error "Not on the same file system" while moving
"some_file". Would you like to continue? [Cancel] [Retry]" 

Version-Release number of selected component (if applicable):
nauilus-2.16
gnome-vfs2-2.16

Steps to reproduce:
1. Select a file on an NFS share.
2. Try to move it to a different NFS share (drag & drop, cut & paste, ...).
3. Scratch your head at the error dialog, thinking "Yeah ... so what?".

Actual results:
The error dialog pops up.

Expected results:
The files should simply be moved from one NFS share to the other.

Does this happen every time?
Yes.

Other information:
Copying the files works fine, moving doesn't.


Additional info:
Works fine with gnome 2.8 on RHEL4

Upstream bug - http://bugzilla.gnome.org/show_bug.cgi?id=505690

Comment 1 ritz 2008-03-19 07:48:09 UTC

From what i understand, gnome-vfs is used to move the files from one source to
another. As per gnome-vfs both files ( on different nfs share ) lie on the same
filesystem, and thus gnome-vfs ends up using file module to move.

  file module uses rename to move the file, and ends up with a EXDEV error.

Comment 2 Matthias Clasen 2008-07-07 16:42:55 UTC

Setting devack after feedback from package owner.

Comment 3 RHEL Program Management 2008-07-21 23:04:44 UTC

This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 5 RHEL Program Management 2009-03-26 17:04:27 UTC

This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 16 errata-xmlrpc 2010-01-13 12:09:15 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0032.html