On Dec 14, 2014 11:01 AM, "Niamh Holding" niamh@fullbore.co.uk wrote:

Hello Keith,

Sunday, December 14, 2014, 6:31:20 PM, you wrote:

KK> Anyway, you want some combination of the -v and --progress switches. KK> Try each separately, and both together, and see which you like best.

Neither!

Both switches list the folders being checked even if the contents are unchanged

Folders should only be listed if timestamps or permissions are different.

-- Les Mikesell Les@gmail.com

Hello Kahlil,

Sunday, December 14, 2014, 8:54:45 PM, you wrote:

KH> -i, --itemize-changes output a change-summary for all updates

Lists every file here

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2014-12-15 14:43, Niamh Holding wrote:

LM> Folders should only be listed if timestamps or permissions are LM> different.

Further experimentation shows this to be the case IF the destination is another local drive.

Unfortunately the required destination is a CIFS share, which might change things.

Sounds like it might be differences in precision of the timestamp. Check out the `--modify-window` option.

- -- AF24 6DE9 D1DF DFB8 3A74 A7AC F457 B7A3 5DF1 4240

When you use --itemize-changes, does it indicate that the timestamps of the directories have changed?

K

Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd

On Tue, Dec 16, 2014 at 7:39 PM, Niamh Holding niamh@fullbore.co.uk wrote:

KH> When you use --itemize-changes, does it indicate that the timestamps of the KH> directories have changed?

Not uless the sequence of dots and letters before the folder name indicates that

-- Best regards, Niamh mailto:niamh@fullbore.co.uk

​Indeed: the sequence of dots and letters before the name indicates why rsync wants to update a file.

From the '--itemize-changes' entry in the rsync man page:

"A t means the modification time is different and is being updated to the sender’s value"

"A p means the permissions are different and are being updated to the sender’s value"

​See the man page for the meaning of other symbols.

​Kal​

Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd

Suite 1416 401 Docklands Drive Docklands VIC 3008 Australia

"All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use a hammer." -- IBM maintenance manual, 1925

On Wed, Dec 17, 2014 at 3:21 AM, Niamh Holding niamh@fullbore.co.uk wrote:

KH> Indeed: the sequence of dots and letters before the name indicates why KH> rsync wants to update a file.

Ah, not time but owner and group are different, and not being changed on the NAS.

Is this a CIFS "thing"?

CIFS mounts are normally done as one user, with user-level credentials. If this user is the owner of all the files and directories on the source side, they should match - but otherwise an attempt to change ownership will fail. Samba offers a user mapping option that might help but if the NAS offers nfs (or ssh and rsync), that might be a better approach.

On Mon, Dec 15, 2014 at 10:41 AM, Niamh Holding niamh@fullbore.co.uk wrote:

Hello Elias,

Monday, December 15, 2014, 4:13:20 PM, you wrote:

EP> Sounds like it might be differences in precision of the timestamp.

Could be, thoght the NAS box has the sending system as it's NTP server so their times should be in sync.

EP> Check out the `--modify-window` option.

Doesn't seem to stop all the folders being listed even though nothing is transferred.

/usr/bin/rsync -av --modify-window=20 --no-whole-file --delete /music /NSA320-music/

What happens if you use --modify-window=3601 to allow up to an hour of difference? Your NAS may have windows-like behavior in terms of storing timestamps in local time and fudging them for DST.

On Tue, Dec 16, 2014 at 12:56 PM, Niamh Holding niamh@fullbore.co.uk wrote:

Hello Les,

Tuesday, December 16, 2014, 4:09:43 PM, you wrote:

LM> What happens if you use --modify-window=3601 to allow up to an hour of LM> difference? Your NAS may have windows-like behavior in terms of LM> storing timestamps in local time and fudging them for DST.

Exactly the same :(

What about the ownership/permissions? There must be something in the attributes that appears different between the source/destination that makes rsync want to attempt to fix it - and fail, since you still see it the next time. Not sure why this would be different between files and directories, though. If you can find the difference you might work around it by unbundling the -a option and omitting trying to sync whatever attribute that isn't working.

Hello Stuart,

Tuesday, December 16, 2014, 9:33:29 PM, you wrote:

SB> If this is a CIFS or other DOSish filesystem you may also need --no-o SB> --no-p and/or --no-g to ignore other file attributes.

Looks like this may be the case to solve that problem.