Uploading files to remote Windows server - Modified timestamps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: samba
Hello,
When I upload a file to a remote Windows share from either Ubuntu Dapper, Edgy or Feisty (running on VMware) the "last modified" timestamp on the file created on the Windows share is changed to the current time.
This happens whether I use Nautilus to upload to the share or I mount it using smbmount and the console cp command. cp -p does not appear to work and returns an error.
This bug is very annoying because if I want to backup some photos or other files by uploading it to a remote Windows share they will have their original timestamps wiped out, causing the loss of valuable data that could make the image vastly easier to find later.
Users are given no warning that their timestamps will be unnecessarily destroyed either. This behaviour does not exist when uploading a file from a Windows machine.
Files downloaded from a Windows share still have their original timestamps intact. Only uploaded files seem to be effected.
Here is an example using a share mounted with smbmount.
root@jabiru-
`./Desktop/
`/mnt/tmpsmbfs/
-rw------- 1 andrew andrew 0 2006-11-27 21:55 ./Desktop/
-rwxr-xr-x 1 root root 0 2006-11-27 22:01 /mnt/tmpsmbfs/
-rwxr-xr-x 1 root root 0 2006-11-27 22:01 ./Desktop/
root@jabiru-
`./Desktop/
cp: failed to preserve ownership for `/mnt/tmpsmbfs/
Thank you for your time.
Changed in samba: | |
importance: | Undecided → Low |
status: | New → Confirmed |
I think this is the same as bug #122302 because when I asked on the #samba channel I was told
that the client has to care about setting the correct modified time.
So it is (in my opinion) no bug in the server (windows or samba), but in the linux clients (smbcilent, smbmount, nautilus.
My first comment :)