lose original file modification date in samba share

[Arnold Somogyi]

Hello,

I have an issue while copying files with Krusader to a samba share. During the copy, Krusader somehow just overwrite the original file modification date with the current time.

The samba server runs on a Ubuntu and the client with Krusader is also Ubuntu.

When I do the same copy with the standard Ubuntu file manager (Files), then everything works fine, the date and the time are kept properly.

I think there is nothing to modify on the server-side because as I mentioned the default Files application does this copy well without any issue.

Maybe the mount that Krusader creates is not working properly, but I am not sure.

Is there any way to fix this annoying issue? I like to use the "Synchronize Folter" Krusader tool, but I need to turn off the date checking, because of this issue. And for me to keep the original file date is crucial.

Thx,

A.

[Gengis Dave]

Hi Arnold,

can you try the same operations with Dolphin? Smb connections are provided by
KIO-extras, while file operations comes from KIO. The "Files" file manager
comes from the Gnome suite and it is different in the background.

Thanks

[Arnold Somogyi]

I executed some tests. Please find below the results.

Samba server: Linux Mint 20 Cinnamon

$ sudo smbstatus

Samba version 4.11.6-Ubuntu

PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing              

----------------------------------------------------------------------------------------------------------------------------------------

343250  nobody       nogroup      hp (ipv4:10.42.0.213:53576)               SMB3_11           -                    -                    

344078  myuser       myuser       10.42.0.213 (ipv4:10.42.0.213:47010)      SMB3_11           -                    partial(AES-128-CMAC)

343496  myuser       myuser       10.42.0.213 (ipv4:10.42.0.213:46946)      SMB3_11           -                    partial(AES-128-CMAC)

343429  myuser       myuser       10.42.0.213 (ipv4:10.42.0.213:46868)      SMB3_11           -                    partial(AES-128-CMAC)

Service      pid     Machine       Connected at                     Encryption   Signing     

---------------------------------------------------------------------------------------------

backup       343429  10.42.0.213   Mon Oct 26 10:14:03 PM 2020 CET  -            -           

backup       344078  10.42.0.213   Mon Oct 26 10:29:36 PM 2020 CET  -            -           

IPC$         343250  hp            Mon Oct 26 10:08:36 PM 2020 CET  -            -           

backup       343496  10.42.0.213   Mon Oct 26 10:16:34 PM 2020 CET  -            -           

Samba Client: Ubuntu 18.04 LTS

• The original file locates here, file date: 30/Mar/2015
• I opened Krusader, Dolphin, and Ubuntu's internal file browser the Files (you can see these three connections above)

Result of copy the same file from the client to the server:

• Files copy: date is okay
• Dolphin: not ok, date on the server is the date of the copy (now)
• Krusader: not ok, date on the server is the date of the copy (now)

So only the Files application copy the file correctly.

Do you have any idea what I need to check on my client machine?

Thanks,

A.

[Toni Asensi Esteve]

> I executed some tests. Please find below the results.

> [...]

>

> *Samba Client: Ubuntu 18.04 LTS*

> [...]

> So only the Files application copy the file correctly.

> Do you have any idea what I need to check on my client machine?

>

> > [...]

> > Hi Arnold,

> >

> > can you try the same operations with Dolphin? Smb connections are

> > provided by

> > KIO-extras, while file operations comes from KIO. The "Files" file

> > manager comes from the Gnome suite and it is different in the

> > background.

> >

> > Thanks

 

This year this bug was solved:

Moving files onto a smb network share sets the files' access/modify times to the current date/time.

https://bugs.kde.org/show_bug.cgi?id=356651

 

so you could try it with a new version of Ubuntu/Kubuntu/etc.

 

 

 

[Arnold Somogyi]

Thanks for the info!

As I can see the version where the bug was fixed is 19.12.3.

Mine is 4:17.12.3-0ubuntu2.

sudo apt-get install kio-extras

Reading package lists... Done

Building dependency tree       

Reading state information... Done

kio-extras is already the newest version (4:17.12.3-0ubuntu2).

0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.

It seems that updating this package is not so easy.

I am checking the internet, but have not found too much info :(