Bug#593964: gedit: save error on NTFS in VBox with shared folders

[Josselin Mouette]

clone 593964 -1
retitle 593964 [glocalfileoutputstream] Fallback for filesystems that don’t support renames on open files
severity 593964 wishlist
reassign 593964 libglib2.0-0
retitle -1 [vboxsf] Cannot rename an open file
reassign -1 virtualbox-ose-guest-utils
thanks

Le lundi 23 août 2010 à 23:17 +0200, Matthijs Melchior a écrit :
> >> Could not save the file /C/Temp/test-gedit.
> >> Unexpected error: Error renaming temporary file: Text file busy
> >    
> >> 20724 rename("/C/Temp/.goutputstream-P3PXHV", "/C/Temp/test-gedit"
> >> <unfinished ...>
> >> 20724<... rename resumed>  )            = -1 ETXTBSY (Text file busy)
> >> 20724 close(26<unfinished ...>
> >>
> >> This suggests the reason for the problem:
> >> The .goutputstream-P3PXHV file is being renamed before it is closed.
> >> I believe this is a problem on NTFS...

> It is a VBox shared folder:
> $ df -hT /C
> Filesystem    Type    Size  Used Avail Use% Mounted on
> C_DRIVE     vboxsf    233G   46G  188G  20% /C
> 
> The error can be handled more graceful:
> After the ETXTBSY error, the file can be saved to its original name
> (which has been moved away to its backup name already) and after that
> is successful remove the temporary file. This is not an efficient way
> to save a file, but it does not change behavior on sane filesystems
> and is expected work on the VBox shared folders...

Feel free to raise the issue to upstream developers. I personally
consider this is an issue in the vboxsf implementation.

Note that SUSv3 allows rename() to fail when the directory is busy, but
not when the file itself is busy. The ETXTBUSY error code is for another
case which is irrelevant on Linux: “The file to be renamed is a pure
procedure (shared text) file that is being executed.”

Cheers,
-- 
 .''`.
: :' :     “You would need to ask a lawyer if you don't know
`. `'       that a handshake of course makes a valid contract.”
  `-        --  J???rg Schilling