[4.1-rc] File was modified, but mtime stayed the same (according to unison)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

Today, I got strange warning from unison:

pavel/.config/chromium/Default/Extension State/LOG.old — transport
failure
• The source file /data/pavel/.config/chromium/Default/Extension
State/LOG.old
has been modified but the fast update detection mechanism
failed to detect it.  Try running once with the fastcheck
option set to 'no'.

Filesystem is plain ext4.
pavel@amd:~$ cat /proc/mounts  | grep /data
/dev/sda2 /data ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
pavel@amd:~$ uname -a
Linux amd 4.1.0-rc5 #23 SMP Wed May 27 09:19:18 CEST 2015 x86_64
GNU/Linux

Now, I know mount -oloop can do such "silent updates"... but that
should not be case for chromium. unison 2.40.102. Any ideas?

Thanks,
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux