docx files gone from share when edited from Windows PC
Posted: Fri Jan 14, 2011 1:16 pm
I'm new to Amahi and Linux, having switched over from WHS1. You know how it is. I'm using Greyhole with 3 2TB drives, formatted with the ext3 filesystem. All shares are accessible from Windows PCs. So far so good.
Recently on a Windows 7 PC I opened a docx file from a share in Word 2010 and worked on it for a while, saving as I went. It acted normally until I closed the file, whereafter at some point the file was gone, replaced by a *.tmp file. (Not the temp file Word creates while a doc is open, either.) I tested this twice more, to the same effect. Other (non-edited) docx files reside in the same share but remain there without incident, no other files or file types have gone disappearing, and reading any file directly from a share causes no problems (e.g. PDF, MP3, etc.).
The server and shares have been up about a week, and since the problem described above I have treated the shares as static file stores only. That is, I have only updated files by copying them to the Windows PC, then copying the update back up.
So my question is: is this aberrant behaviour, or the normal state of affairs with Windows-to-Linux filesystems, or a Greyhole issue? Or something else?
Thanks for any help.
EDIT: Wouldn't you know it, I found some helpful info in the Greyhole forum right after posting. A "greyhole --debug" on the relevant filename revealed that Greyhole renamed the *.tmp file to *.docx multiple times during the period I was editing it, and that finally it failed to resolve the last rename. Manually renaming *.tmp to *.docx restored the "missing" file. Obviously this is a Greyhole issue, and I note that Guillaume acknowledges it as such.
Recently on a Windows 7 PC I opened a docx file from a share in Word 2010 and worked on it for a while, saving as I went. It acted normally until I closed the file, whereafter at some point the file was gone, replaced by a *.tmp file. (Not the temp file Word creates while a doc is open, either.) I tested this twice more, to the same effect. Other (non-edited) docx files reside in the same share but remain there without incident, no other files or file types have gone disappearing, and reading any file directly from a share causes no problems (e.g. PDF, MP3, etc.).
The server and shares have been up about a week, and since the problem described above I have treated the shares as static file stores only. That is, I have only updated files by copying them to the Windows PC, then copying the update back up.
So my question is: is this aberrant behaviour, or the normal state of affairs with Windows-to-Linux filesystems, or a Greyhole issue? Or something else?
Thanks for any help.
EDIT: Wouldn't you know it, I found some helpful info in the Greyhole forum right after posting. A "greyhole --debug" on the relevant filename revealed that Greyhole renamed the *.tmp file to *.docx multiple times during the period I was editing it, and that finally it failed to resolve the last rename. Manually renaming *.tmp to *.docx restored the "missing" file. Obviously this is a Greyhole issue, and I note that Guillaume acknowledges it as such.
