From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: Florian Lohoff <flo@rfc822.org>, linux-kernel@vger.kernel.org
Subject: Re: [CRASH] gdth / __block_prepare_write: zeroing uptodate buffer! / NMI Watchdog detected LOCKUP
Date: Tue, 26 Feb 2002 20:32:35 +0100 [thread overview]
Message-ID: <20020226203235.A4036@inspiron.school.suse.de> (raw)
In-Reply-To: <20020226184043.GA10420@paradigm.rfc822.org> <3C7BDC57.A835D657@zip.com.au>, <3C7BDC57.A835D657@zip.com.au> <20020226191626.GA11283@paradigm.rfc822.org> <3C7BDFE6.313AA43D@zip.com.au>
In-Reply-To: <3C7BDFE6.313AA43D@zip.com.au>
On Tue, Feb 26, 2002 at 11:20:06AM -0800, Andrew Morton wrote:
> Florian Lohoff wrote:
> >
> > On Tue, Feb 26, 2002 at 11:04:55AM -0800, Andrew Morton wrote:
> > > > __block_prepare_write: zeroing uptodate buffer!
> > >
> > > Yup. This happens when the disk fills up. Andrea and I were
> > > discussing it over the weekend. There's a new patch in the -aa
> > > kernels which doesn't quite fix it :(
> > >
> > > We'll fix it in 2.4.19-pre somehow. It's possible that this problem
> > > causes a chnuk of zeroes to be written into the file when you hit
> > > ENOSPC, which is rather rude. But your file was truncated anyway.
> >
> > I dont think the machine had full filesystems at all.
>
> I/O error when reading filesystem metadata would also cause it.
Indeed. Looks like gdth gone wild and that triggered the cleanup slowpath.
Andrea
next prev parent reply other threads:[~2002-02-26 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 18:40 Florian Lohoff
2002-02-26 19:04 ` Andrew Morton
2002-02-26 19:16 ` Florian Lohoff
2002-02-26 19:20 ` Andrew Morton
2002-02-26 19:32 ` Andrea Arcangeli [this message]
2002-02-27 3:27 ` T. A.
2002-02-27 9:36 ` Florian Lohoff
2002-02-26 19:31 ` Andrea Arcangeli
2002-02-26 19:27 ` Andrea Arcangeli
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=20020226203235.A4036@inspiron.school.suse.de \
--to=andrea@suse.de \
--cc=akpm@zip.com.au \
--cc=flo@rfc822.org \
--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
all inboxes | Powered by JetHome®