From: Stephan van Hienen <raid@a2000.nu>
To: Helge Hafting <helgehaf@aitel.hist.no>
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, bernard@biesterbos.nl
Subject: Re:2TB+ fs ext3 (was fsck out of memory)
Date: Tue, 11 Feb 2003 17:14:31 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.53.0302111707530.15933@ddx.a2000.nu> (raw)
In-Reply-To: <3E479CC7.B170D5C7@aitel.hist.no>
On Mon, 10 Feb 2003, Helge Hafting wrote:
> For 1MB average filesize use -i 1048576
tried to mke2fs with '-i 1048576' :
----
]# mke2fs -i 1048576 /dev/md0 -R stride=16 -m 0 -j
mke2fs 1.32 (09-Nov-2002)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
2403840 inodes, 615381536 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
18780 block groups
32768 blocks per group, 32768 fragments per group
128 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616,
78675968,
102400000, 214990848, 512000000, 550731776
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
----
dmesg output :
md: mke2fs(pid 10600) used obsolete MD ioctl, upgrade your software to use
new ioctls.
----
then i try to mount :
----
]# mount /dev/md0 /raid/
mount: wrong fs type, bad option, bad superblock on /dev/md0,
or too many mounted file systems
---
dmesg output :
raid5: switching cache buffer size, 4096 --> 1024
raid5: switching cache buffer size, 1024 --> 4096
EXT3-fs error (device md(9,0)): ext3_check_descriptors: Block bitmap for
group 4480 not in group (block 15)!
EXT3-fs: group descriptors corrupted !
----
and e2fsck :
----
e2fsck /dev/md0
e2fsck 1.32 (09-Nov-2002)
Group descriptors look bad... trying backup blocks...
Block bitmap for group 6528 is not in group. (block 15)
Relocate<y>? yes
Inode bitmap for group 6528 is not in group. (block 3145728)
Relocate<y>? yes
Inode table for group 6528 is not in group. (block 0)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate<y>? yes
Block bitmap for group 6529 is not in group. (block 0)
Relocate<y>? yes
Inode bitmap for group 6529 is not in group. (block 0)
Relocate<y>? yes
Inode table for group 6529 is not in group. (block 0)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate<y>? yes
Block bitmap for group 6530 is not in group. (block 0)
Relocate<y>? yes
Inode bitmap for group 6530 is not in group. (block 0)
Relocate<y>? yes
Inode table for group 6530 is not in group. (block 0)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate<y>? yes
.....
next prev parent reply other threads:[~2003-02-11 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 15:17 fsck out of memory 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 ` Stephan van Hienen [this message]
2003-02-10 22:44 ` [Ext2-devel] " 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
2003-02-11 2:53 Marco C. Mason
2003-02-11 15:32 ` Re:2TB+ fs ext3 (was fsck out of memory) Stephan van Hienen
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.0302111707530.15933@ddx.a2000.nu \
--to=raid@a2000.nu \
--cc=adilger@clusterfs.com \
--cc=bernard@biesterbos.nl \
--cc=ext2-devel@lists.sourceforge.net \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--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®