atomic rename buggy on NFS?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




	Hi

There's a bug (*) which has annoyed me for some time now. With $HOME on NFS, editing a desktop launcher with nautilus closes the window after nautilus tries to change the file. This was debugged and upstream thinks that atomic rename is buggy on NFS. Quote:

"Results from mv temp.txt foobar

On NFS:
Directory Monitor Event:
Child = /mnt/data/temp/foobar
Event = DELETED
Directory Monitor Event:
Child = /mnt/data/temp/temp.txt
Event = DELETED
Directory Monitor Event:
Child = /mnt/data/temp/foobar
Event = CREATED

On ext3:
Directory Monitor Event:
Child = /tmp/x/temp.txt
Event = DELETED
Directory Monitor Event:
Child = /tmp/x/foobar
Event = CREATED

This is IMHO bogus behaviour from NFS. At no time is the "foobar" file not
visible, so it should IMHO not be reported as deleted."


Or is it a feature that needs to be worked around in client apps?


* http://bugzilla.gnome.org/show_bug.cgi?id=575684


t
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux