From: Asdo <asdo@shiftmail.org>
To: Phil Turmel <philip@turmel.org>
Cc: NeilBrown <neilb@suse.de>,
linux-raid <linux-raid@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: Sync does not flush to disk!?
Date: Fri, 08 Jun 2012 15:57:04 +0200 [thread overview]
Message-ID: <4FD204B0.3000204@shiftmail.org> (raw)
In-Reply-To: <4FD202CD.7000309@turmel.org>
On 06/08/12 15:49, Phil Turmel wrote:
>
> To put it another way: You can't safely access ext filesystems via
> raw devices in two systems. The kernel cache won't be synchronized,
> and you almost certainly *will* corrupt the contents.
Thanks both of you for your explanations
I might say that it seems to me a bad design: never before I saw a cache
that is not updated by writes.
Here the cache content is *older* than the data on the real devices!?
if it was *newer*, there are known cases (writeback cache not flushed
yet), but *older*... never seen.
Thanks
next prev parent reply other threads:[~2012-06-08 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 9:53 Sync does not flush to disk!? Asdo
2012-06-08 11:39 ` Asdo
2012-06-08 12:33 ` NeilBrown
2012-06-08 13:49 ` Phil Turmel
2012-06-08 13:57 ` Asdo [this message]
2012-06-08 14:11 ` Jan Kara
2012-06-08 14:16 ` Jan Kara
2012-06-08 18:28 ` Ted Ts'o
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=4FD204B0.3000204@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=philip@turmel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).