All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: tytso@mit.edu, adilger.kernel@dilger.ca,
	linux-ext4@vger.kernel.org,
	kernel list <linux-kernel@vger.kernel.org>,
	jack@suse.cz
Subject: [4.1-rc] File was modified, but mtime stayed the same (according to unison)
Date: Tue, 9 Jun 2015 12:43:30 +0200	[thread overview]
Message-ID: <20150609104330.GA29980@amd> (raw)


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

             reply	other threads:[~2015-06-09 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 10:43 Pavel Machek [this message]
2015-06-09 15:12 ` [4.1-rc] File was modified, but mtime stayed the same (according to unison) Theodore Ts'o
2015-06-09 15:34   ` Pavel Machek
2015-06-09 16:04     ` Theodore Ts'o
2015-06-09 22:13   ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150609104330.GA29980@amd \
    --to=pavel@ucw.cz \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.