From: Paul Slootman <paul@wurtel.net>
To: linux-ext4@vger.kernel.org
Subject: #blocks per group too big: 37265
Date: Thu, 3 Apr 2008 18:19:04 +0200 [thread overview]
Message-ID: <20080403161904.GA31670@msgid.wurtel.net> (raw)
Hi,
I wanted to try out ext4 on my shiny new 9+TB RAID5 device
(11 x 1TB disks in md raid5).
I obtained the 1.39-tyt3 version of e2fsprogs, and did:
./mkfs.ext3 -j -m 0 -N 1000000000 -O dir_index,filetype,resize_inode -E stride=65536,resize=5120000000 -J device=/dev/mapper/vg11-md15--journal -L data2 /dev/md15
(If using a separate device for the journal is inadvisable, please let
me know; this is on a different set of spindles that md15 is running on.)
The stride was calculated from the 64k chunk of the raid5 device.
Mainly a guess, as I couldn't find any clear reference on how to plug in
the values to fill this in.
Anyway, that did:
| mke2fs 1.38 (30-Jun-2005)
| Filesystem label=data2
| OS type: Linux
| Block size=4096 (log=2)
| Fragment size=4096 (log=2)
| 1000204128 inodes, 2441859680 blocks
| 0 blocks (0.00%) reserved for the super user
| First data block=0
| Maximum filesystem blocks=5485408000
| 65527 block groups
| 37265 blocks per group, 37265 fragments per group
| 15264 inodes per group
| Superblock backups stored on blocks:
| 37265, 111795, 186325, 260855, 335385, 931625, 1006155, 1825985,
| 3018465, 4658125, 9055395, 12781895, 23290625, 27166185, 81498555,
| 89473265, 116453125, 244495665, 582265625, 626312855, 733486995,
| 2200460985
|
| Writing inode tables: done
| Adding journal to device /dev/mapper/vg11-md15--journal: done
| Writing superblocks and filesystem accounting information: done
|
| This filesystem will be automatically checked every 27 mounts or
| 180 days, whichever comes first. Use tune2fs -c or -i to override.
Note the "37265 blocks per group".
Trying to mount this (after of course "tune2fs -E test_fs /dev/md15",
which BTW didn't work with the 1.39-tyt3 version) gave a kernel error:
| EXT4-fs: #blocks per group too big: 37265
I then tried adding "-g 16384" to the mkfs.ext3 invocation, but that
apparently got ignored and still showed "37265 blocks per group".
Removing the stride option didn't help. Removing all options didn't
help...
Is it impossible to create ext4 on such a device? I must be overlooking
something... the Documentation/filesystems/ext4.txt file doesn't help
(2.6.25-rc8).
thanks,
Paul Slootman
next reply other threads:[~2008-04-03 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 16:19 Paul Slootman [this message]
2008-04-03 17:58 ` #blocks per group too big: 37265 Eric Sandeen
2008-04-03 19:12 ` Theodore Tso
2008-04-03 19:24 ` Eric Sandeen
2008-04-03 18:39 ` Theodore Tso
[not found] ` <20080403183929.GE13486@40mit.edu>
2008-04-04 9:21 ` Paul Slootman
2008-04-04 12:08 ` Theodore Tso
2008-04-04 12:56 ` Paul Slootman
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=20080403161904.GA31670@msgid.wurtel.net \
--to=paul@wurtel.net \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.