mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Lord <lord@sgi.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Mike Black <mblack@csihq.com>, Andrew Morton <andrewm@uow.edu.au>,
	"linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>,
	ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: 2.4.6 and ext3-2.4-0.9.1-246
Date: Fri, 13 Jul 2001 12:27:33 -0500	[thread overview]
Message-ID: <200107131727.f6DHRXp08659@jen.americas.sgi.com> (raw)
In-Reply-To: Message from "Stephen C. Tweedie" <sct@redhat.com>  of "Fri, 13 Jul 2001 17:30:07 BST." <20010713173007.G13419@redhat.com>

> Hi,
> 
> On Fri, Jul 13, 2001 at 09:54:56AM -0400, Mike Black wrote:
> > I give up!  I'm getting file system corruption now on the ext3 partition...
> > and I've got a kernel oops (soon to be decoded)
> 
> Please, do send details.  We already know that the VM has a hard job
> under load, and journaling exacerbates that --- ext3 cannot always
> write to disk without first allocating more memory, and the VM simply
> doesn't have a mechanism for dealing with that reliably.  It seems to
> be compounded by (a) 2.4 having less write throttling than 2.2 had,
> and (b) the zoned allocator getting confused about which zones
> actually need to be recycled.

We seem to have managed to keep XFS going without the memory reservation
scheme - and the way we do I/O on metadata right now means there is always
a memory allocation in that path. At the moment the only thing I can kill
the system with is make -j bzImage it eventually grinds to a halt with
the swapper waiting for a request slot in the block layer but the system
is in such a mess that I have not been able to diagnose it further than
that.

A lot of careful use of GFP flags on memory allocation was necessary to
get to this point, the GFP_NOIO and GFP_NOFS finally made this deadlock
clean.

Steve


> 
> It's not just ext3 --- highmem bounce buffering and soft raid buffers
> have the same problem, and work around it by doing their own internal
> preallocation of emergency buffers.  Loop devices and nbd will have a
> similar problem if you use those for swap or writable mmaps, as will
> NFS.
> 
> One proposed suggestion is to do per-zone memory reservations for the
> VM's use: Ben LaHaise has prototype code for that and we'll be testing
> to see if it makes for an improvement when used with ext3.
> 
> Cheers,
>  Stephen
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



  reply	other threads:[~2001-07-13 17:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-10  9:47 Mike Black
2001-07-10 17:52 ` Andreas Dilger
     [not found]   ` <018101c1096a$17e2afc0$b6562341@cfl.rr.com>
2001-07-10 18:17     ` [Ext2-devel] " Stephen C. Tweedie
2001-07-10 18:27       ` Mike Black
2001-07-10 18:29         ` Stephen C. Tweedie
2001-07-10 18:51     ` Andreas Dilger
2001-07-11  4:08 ` Andrew Morton
2001-07-11 12:16   ` Mike Black
2001-07-11 15:36     ` Andrew Morton
2001-07-12 10:54       ` Mike Black
2001-07-12 11:34         ` Andrew Morton
2001-07-13 12:22           ` Mike Black
2001-07-13 13:54             ` Mike Black
2001-07-13 14:15               ` Andrew Morton
2001-07-13 17:30                 ` Mike Black
2001-07-13 17:38                   ` [Ext2-devel] " Stephen C. Tweedie
2001-07-14 10:42                     ` Mike Black
2001-07-14 10:53                       ` Andrew Morton
2001-07-14 11:58                       ` Andrew Morton
2001-07-16 18:23                         ` Stephen C. Tweedie
2001-07-13 16:30               ` Stephen C. Tweedie
2001-07-13 17:27                 ` Steve Lord [this message]
2001-07-13 17:33                   ` Stephen C. Tweedie

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=200107131727.f6DHRXp08659@jen.americas.sgi.com \
    --to=lord@sgi.com \
    --cc=andrewm@uow.edu.au \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mblack@csihq.com \
    --cc=sct@redhat.com \
    /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

all inboxes | Powered by JetHome®