From: Andrew Morton <akpm@osdl.org>
To: Nico Schottelius <nico-kernel@schottelius.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is one sync() not enough?
Date: Wed, 15 Jun 2005 12:41:39 -0700 [thread overview]
Message-ID: <20050615124139.6859bf07.akpm@osdl.org> (raw)
In-Reply-To: <20050615105537.GO1467@schottelius.org>
Nico Schottelius <nico-kernel@schottelius.org> wrote:
>
> Hello Andrew,
>
> you wrote:
> > What filesystem?
>
> jfs
It would be useful to test with a different filesystem (ext3 mounted with
data=writeback is close to equivalent). That'll help us identify the bug.
> > What kernel version?
>
> 2.6.11.11
>
> > Any unusual bind mounts, loopback
> > mounts, etc? There must be something there...>
>
> Yes, dm-crypt-mounted-jfs.
Again, if you can temporarily eliminate dm-crypt as well it will help
narrow it down.
> So if I understood everything correctly, a simple umount() without
> a sync() before should be enough?
Yes.
> If so, I'll try that, I am happy about every less function call
> I need to do.
OK. sync()+umount() shouldn't take any longer than a bare umount() (which
has to do a sync too). Unless you have multiple disks, in which case
there's no point in syncing the disks which aren't being umounted. But
then, I have a feeling that standard util-linux umount(8) does a global
sync anyway.
next prev parent reply other threads:[~2005-06-15 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 9:41 Why is one sync() not enough? Nico Schottelius
2005-06-14 12:58 ` Martin Waitz
2005-06-14 15:58 ` Jesper Juhl
2005-06-14 18:36 ` Valdis.Kletnieks
2005-06-15 6:19 ` Nico Schottelius
2005-06-15 4:50 ` Andrew Morton
2005-06-15 3:39 ` jmerkey
2005-06-15 8:20 ` Bernd Eckenfels
2005-06-15 10:55 ` Nico Schottelius
2005-06-15 19:41 ` Andrew Morton [this message]
2005-06-15 8:17 ` Helge Hafting
2005-06-15 9:28 ` Denis Vlasenko
2005-06-15 9:43 ` Coywolf Qi Hunt
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=20050615124139.6859bf07.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-kernel@schottelius.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