+++ This bug was initially created as a clone of Bug #832622 +++ Description of problem: End user complained that since upgrading to 3.3.0 every time they edit a MS Office file it leaves behind a temp file. How reproducible: Every time Steps to Reproduce: 1. Re-share a glusterfs fuse mount with samba 2. Put an excel spreadsheet on that share 3. Open that excel spreadsheet in MS Excel 4. Make a small edit 5. Close the file, saving changes Actual results: The ${FILENAME}~${SOME_RANDOM_BITS}.TMP will remain behind. Expected results: That TMP file is opened via samba with a flag set to delete on close. Samba declines to delete the file because it detects that the inode has changed. Additional info: A loglevel=15 log from samba shows the error where samba detects that the inode has changed. The change is that the 64 bit inode has been truncated to 32 bits. Mounting by running glusterfs from the command line and setting --attribute-timeout=0 works around this problem.
need to check the behavior on RHS. (considering there is a work around available). and also 32bit inode numbers are involved here. May not be applicable to RHS version. Would be great if QE team helps here by confirming the behavior on RHS nodes.
I tested it with the following setup: RHS 2.0.z update2 - 4 node cluster, Dis-rep volume windows 7 64-bit client MS Office 2007 Steps Followed: 1. Fuse mount the gluster volume 2. Put a MS excel file created on MS office 2007 on the mount point 3. Map the share on windows 7 64-bit machine 4. Open the MS excel file. 5. edit it, save it and close it. 6. Create a new excel file on the win 7 client, put some data and save it. 7. Opened the above 2 files from a 2nd win 7 client and edited it Results: Did not see and .tmp file creation in the above steps mentioned. Also checked the users temp folder. Can we get info on which MS office version, this behavior was seen.
closing as per comment #3