From: Stephan van Hienen <raid@a2000.nu>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: 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: fsck out of memory
Date: Sun, 9 Feb 2003 11:32:22 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.53.0302091120280.3114@ddx.a2000.nu> (raw)
In-Reply-To: <Pine.LNX.4.53.0302090953440.1039@ddx.a2000.nu>
and yesterday had another crash (i was using the /dev/md0 mounted without
fsck(running ok for about 24h, only 1 dir was not accessable(was
created at time previous crash)
at this time a bit more info in /var/log/messages :
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871063
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871065
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871071
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871079
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871081
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871083
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871085
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871087
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871095
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871103
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871108
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871114
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871119
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871121
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871123
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871127
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871129
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871135
Feb 8 20:11:27 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 536871143
..
..(few minutes about the same msg's (only diffent block)
..
Feb 8 20:19:12 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 540606715
Feb 8 20:19:12 storage kernel: EXT2-fs error (device md(9,0)):
ext2_new_block: Allocating block in system zone - block = 540606717
Feb 8 20:19:36 storage kernel: raid5: multiple 1 requests for sector
2064432
Feb 8 20:22:17 storage kernel: raid5: multiple 0 requests for sector
14094488
Feb 8 20:29:12 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:12 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:13 storage last message repeated 4 times
Feb 8 20:29:13 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:13 storage last message repeated 2 times
Feb 8 20:29:13 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:13 storage last message repeated 6 times
Feb 8 20:29:13 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:13 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:13 storage kernel: raid5: multiple 0 requests for sector 6496
Feb 8 20:29:13 storage last message repeated 5 times
Feb 8 20:29:13 storage kernel: raid5: multiple 0 requests for sector
25792
Feb 8 20:29:13 storage last message repeated 5 times
Feb 8 20:29:14 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:14 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:14 storage last message repeated 2 times
Feb 8 20:29:14 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:14 storage last message repeated 4 times
Feb 8 20:29:15 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:15 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:15 storage last message repeated 2 times
Feb 8 20:29:16 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:16 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:16 storage last message repeated 2 times
Feb 8 20:29:16 storage kernel: raid5: multiple 0 requests for sector 6496
Feb 8 20:29:16 storage last message repeated 2 times
Feb 8 20:29:16 storage kernel: raid5: multiple 0 requests for sector
25792
Feb 8 20:29:16 storage last message repeated 2 times
Feb 8 20:29:16 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:16 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:16 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:16 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:16 storage last message repeated 6 times
Feb 8 20:29:17 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:17 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:18 storage last message repeated 4 times
Feb 8 20:29:18 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:18 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:18 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:18 storage last message repeated 2 times
Feb 8 20:29:19 storage kernel: raid5: multiple 0 requests for sector
306783232
Feb 8 20:29:19 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:19 storage last message repeated 2 times
Feb 8 20:29:19 storage kernel: raid5: multiple 0 requests for sector
9587064
Feb 8 20:29:19 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:19 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:19 storage last message repeated 8 times
Feb 8 20:29:19 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:19 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:19 storage last message repeated 2 times
Feb 8 20:29:21 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:21 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:21 storage last message repeated 4 times
Feb 8 20:29:21 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:31 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:31 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:32 storage kernel: raid5: multiple 0 requests for sector
3670152
Feb 8 20:29:32 storage kernel: raid5: multiple 0 requests for sector
306783480
Feb 8 20:29:32 storage kernel: raid5: multiple 0 requests for sector 6496
Feb 8 20:29:32 storage last message repeated 5 times
Feb 8 20:29:32 storage kernel: raid5: multiple 0 requests for sector
25792
(at that time i did a powerdown (reboot was not possible))
next prev parent reply other threads:[~2003-02-09 10:23 UTC|newest]
Thread overview: 21+ 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 [this message]
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 ` [Ext2-devel] Re: fsck out of memory Stephen C. Tweedie
2003-02-11 13:11 ` 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] <Pine.LNX.4.33.0302071637050.11484-100000@nooks.wimpunk.com>
2003-02-07 15:50 ` kernel
2003-02-07 16:09 ` Wim Vinckier
2003-02-07 16:15 ` Stephan van Hienen
2003-02-07 16:20 ` Wim Vinckier
2003-02-07 17:08 ` Stephan van Hienen
2003-02-11 2:53 Marco C. Mason
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=Pine.LNX.4.53.0302091120280.3114@ddx.a2000.nu \
--to=raid@a2000.nu \
--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=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®