From: Andrew Morton <akpm@zip.com.au>
To: "Jakob Østergaard" <jakob@unthought.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bdflush and postgres stuck in D state
Date: Tue, 18 Sep 2001 10:49:10 -0700 [thread overview]
Message-ID: <3BA78916.2984B011@zip.com.au> (raw)
In-Reply-To: <20010918125605.F29908@unthought.net>, <20010918125605.F29908@unthought.net>; from jakob@unthought.net on Tue, Sep 18, 2001 at 12:56:05PM +0200 <20010918193023.P29908@unthought.net>
Jakob Østergaard wrote:
>
> Sorry for following up on my own post, I have a little extra
> information.
>
> I started a g++ job to try to force the machine to write out some dirty
> buffers before I reboot. g++ now hangs along with two sync's, bdflush
> and the postgres process.
>
Since 2.4.7 several bugs have been fixed in RAID1 which would
cause this, including a missing blockdevice unplug and failure
to hang onto the supposedly-reserved RAID1 buffer-heads.
-
next prev parent reply other threads:[~2001-09-18 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 10:56 bdflush and postgres stuck in D state Jakob Østergaard
2001-09-18 17:30 ` Jakob Østergaard
2001-09-18 17:49 ` Andrew Morton [this message]
2001-09-18 21:08 ` David Rees
2001-09-19 9:26 ` Jakob Østergaard
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=3BA78916.2984B011@zip.com.au \
--to=akpm@zip.com.au \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.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