From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <npiggin@kernel.dk>
Cc: Chris Mason <chris.mason@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Jan Kara <jack@suse.cz>, Eric Sandeen <sandeen@redhat.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [patch] fs: fix deadlocks in writeback_if_idle
Date: Wed, 24 Nov 2010 14:51:57 -0800 [thread overview]
Message-ID: <20101124145157.c999b1e8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101124010343.GD3168@amd>
On Wed, 24 Nov 2010 12:03:43 +1100
Nick Piggin <npiggin@kernel.dk> wrote:
> On Tue, Nov 23, 2010 at 01:58:24PM -0500, Chris Mason wrote:
> > > > My original btrfs patch just exported the bdi_ funcs so that btrfs could
> > > > do the above internally. But Christoph objected, and I think he's
> > > > right. We should either give everyone a bdi or make sure the writeback
> > > > func kicks only one filesystem.
> > >
> > > Well it's just kicking the writeback thread, and it will writeback
> > > from that particular sb.
> >
> > Hmmm? It will writeback for all the SBs on that bdi. In the current
> > form that ext4 uses, that gets pretty expensive if you have a bunch of
> > large partitions and you're only running out of space on one of them.
>
> Right. But if the bdi has writeback in progress (which would be most
> of the time, on a busy filesystem), writeback_if_idle doesn't do
> anything, and it is happy just for the background writeback to
> eventually get around to writing out for us.
That doesn't work if you're running btfs (apparently short for
"busticated filesystem") because the bdi-per-sb thing carefully hid the
information which you're looking for.
We still don't have a fix for this bug yet, it appears, btw.
next prev parent reply other threads:[~2010-11-24 22:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 10:02 [patch] fs: fix deadlocks in writeback_if_idle Nick Piggin
2010-11-23 10:11 ` Nick Piggin
2010-11-23 13:18 ` Jan Kara
2010-11-25 3:52 ` Nick Piggin
2010-11-23 10:26 ` Boaz Harrosh
2010-11-23 10:54 ` Nick Piggin
2010-11-23 12:00 ` Boaz Harrosh
2010-11-23 12:34 ` Chris Mason
2010-11-23 12:52 ` Nick Piggin
2010-11-23 18:58 ` Chris Mason
2010-11-24 1:03 ` Nick Piggin
2010-11-24 13:10 ` Jan Kara
2010-11-25 3:53 ` Nick Piggin
2010-11-29 22:26 ` Andrew Morton
2010-11-30 0:01 ` Nick Piggin
2010-12-16 3:12 ` Nick Piggin
2010-11-24 22:51 ` Andrew Morton [this message]
2010-11-25 4:07 ` Nick Piggin
2010-11-24 22:47 ` Andrew Morton
2010-11-25 9:41 ` Boaz Harrosh
2010-11-25 20:30 ` Andrew Morton
2010-11-30 0:50 ` Chris Mason
2010-11-23 12:54 ` Dmitry
2010-11-23 12:54 ` Dmitry
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=20101124145157.c999b1e8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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.