From: "Stephen C. Tweedie" <sct@redhat.com>
To: Stephan van Hienen <raid@a2000.nu>
Cc: Andreas Dilger <adilger@clusterfs.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
ext2-devel@lists.sourceforge.net, "Theodore Ts'o" <tytso@mit.edu>,
peter@chubb.wattle.id.au, tbm@a2000.nu
Subject: Re: [Ext2-devel] Re: fsck out of memory
Date: 10 Feb 2003 22:44:20 +0000 [thread overview]
Message-ID: <1044917060.11838.108.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0302090953440.1039@ddx.a2000.nu>
Hi,
On Sun, 2003-02-09 at 10:08, Stephan van Hienen wrote:
> Feb 7 04:18:15 storage kernel: EXT3-fs error (device md(9,0)):
> ext3_new_block:
> Allocating block in system zone - block = 536875638
That looks like it could be a block wrap, amongst other possible causes.
> makes me wonder if this can have todo with the lbd (to allow 2TB+ devices)
> patch ? or is this something else?
Well, that's the most likely candidate, because it's the least tested
component. Are you using Ben LaHaise's LBD fixes for the md devices?
Without those, md and lvm are not LBD-safe.
Cheers,
Stephen
next prev parent reply other threads:[~2003-02-10 22:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 15:17 kernel
2003-02-07 17:07 ` Stephan van Hienen
2003-02-07 17:28 ` Andreas Dilger
2003-02-09 10:08 ` Stephan van Hienen
2003-02-09 10:32 ` Stephan van Hienen
2003-02-09 20:08 ` Peter Chubb
2003-02-10 11:28 ` Stephan van Hienen
2003-02-09 20:31 ` Andreas Dilger
2003-02-10 12:01 ` Stephan van Hienen
[not found] ` <3E479CC7.B170D5C7@aitel.hist.no>
2003-02-11 16:14 ` Re:2TB+ fs ext3 (was fsck out of memory) Stephan van Hienen
2003-02-10 22:44 ` Stephen C. Tweedie [this message]
2003-02-11 13:11 ` [Ext2-devel] Re: fsck out of memory Stephan van Hienen
2003-02-11 14:33 ` Stephen C. Tweedie
[not found] ` <1044993857.6640.7.camel@plokta.s8.com>
2003-02-11 20:32 ` Re:2TB+ fs ext3 (was fsck out of memory) Stephan van Hienen
2003-02-07 17:24 ` fsck out of memory Andreas Dilger
[not found] <5250726@toto.iv>
2003-02-13 3:30 ` [Ext2-devel] " Peter Chubb
2003-02-13 4:01 ` Randy.Dunlap
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=1044917060.11838.108.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=adilger@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=raid@a2000.nu \
--cc=tbm@a2000.nu \
--cc=tytso@mit.edu \
/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®