From: Justin Maggard <jmaggard10@gmail.com>
To: Valerie Aurora <vaurora@redhat.com>
Cc: Andreas Dilger <adilger@sun.com>, linux-ext4@vger.kernel.org
Subject: Re: >16TB issues
Date: Fri, 31 Jul 2009 18:24:50 -0700 [thread overview]
Message-ID: <150c16850907311824n71e36f66i86b508bc25d0c4bb@mail.gmail.com> (raw)
In-Reply-To: <20090730222349.GC31141@shell>
On Thu, Jul 30, 2009 at 3:23 PM, Valerie Aurora<vaurora@redhat.com> wrote:
> Any chance you can give us the exact mke2fs command lines, outputs,
> and device sizes you are using? dumpe2fs -h would be bonus.
>
Sure thing. Here's the output using an x86_64 kernel with all 32-bit userland:
2TB-Monster:~# uname -a
Linux 2TB-Monster 2.6.30.1 #1 SMP Fri Jul 17 15:43:57 PDT 2009 x86_64 GNU/Linux
2TB-Monster:~# cat /etc/mke2fs.conf
[defaults]
base_features = sparse_super,filetype,resize_inode,dir_index,ext_attr
blocksize = 4096
inode_size = 128
inode_ratio = 65536
[fs_types]
ext4 = {
features = has_journal,extents,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
inode_size = 256
}
2TB-Monster:~# mkfs.ext4 /dev/md2
mke2fs 1.41.8 (20-Jul-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
365400064 inodes, 5846380224 blocks
292319011 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3699376128
178418 block groups
32768 blocks per group, 32768 fragments per group
2048 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, 644972544, 1934917632,
2560000000, 3855122432, 5804752896
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
2TB-Monster:~# dumpe2fs -h /dev/md2
dumpe2fs 1.41.8 (20-Jul-2009)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 482b503d-68e0-481e-906e-52eb70e7842c
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype extent 64bit flex_bg sparse_super large_file huge_file
uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 365400064
Block count: 5846380224
Reserved block count: 292319011
Free blocks: 5823053972
Free inodes: 365400053
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1024
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 2048
Inode blocks per group: 128
Flex block group size: 16
Filesystem created: Fri Jul 31 16:23:29 2009
Last mount time: n/a
Last write time: Fri Jul 31 16:26:45 2009
Mount count: 0
Maximum mount count: 36
Last checked: Fri Jul 31 16:23:29 2009
Check interval: 15552000 (6 months)
Next check after: Wed Jan 27 15:23:29 2010
Lifetime writes: 88 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: d92d80aa-9c24-4d1c-a452-9ddadd1ebc94
Journal backup: inode blocks
Journal size: 128M
2TB-Monster:~# e2fsck -C0 -fy /dev/md2
e2fsck 1.41.8 (20-Jul-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +(1551368194--1551368207)
+(1551368210--1551368223) +(1551368480--1551370271)
+(4294967296--4294969375) +(4295491584--4295491599) +4295491601
+(4295491609--4295491610)
... tons more like this ...
-(5846368341--5846368342) -5846368345 -5846368347 -5846368350
-5846368384 -(5846368386--5846368387) -5846368391 -5846368399
-5846368401
Fix? yes
/dev/md2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/md2: 11/365400064 files (0.0% non-contiguous), 23326252/5846380224 blocks
2TB-Monster:~# e2fsck -C0 -fy /dev/md2
e2fsck 1.41.8 (20-Jul-2009)
e2fsck: Superblock invalid, trying backup blocks...
Group descriptor 0 checksum is invalid. Fix? yes
Group descriptor 1 checksum is invalid. Fix? yes
... every number sequentially ...
Group descriptor 89208 checksum is invalid. Fix? yes
Pass 1: Checking inodes, blocks, and sizes
Block bitmap differences: -1081356 -(1081362--1081363) -1081366
-(1081369--1081370) -1081372 -1081374 -1081410 -1081412
-(1081414--1081416) -1081419 -1081421 -(1081423--1081426)
-(1081429--1081430) -1081433
... tons more like this ...
(182679623--182679625) -182679628 -182679630 -(182679632--182679635)
-(182679638--182679639) -182679642 -182679644 -182679647
-(182679681--182679683) -182679687 -182679690 -182679697
Fix? yes
/dev/md2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/md2: 11/365400064 files (0.0% non-contiguous), 23326252/5846380224 blocks
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-01 1:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 22:23 >16TB issues Justin Maggard
2009-07-03 14:38 ` Andreas Dilger
2009-07-16 18:04 ` Justin Maggard
2009-07-16 18:59 ` Valerie Aurora
2009-07-21 16:10 ` Andreas Dilger
2009-07-21 18:52 ` Justin Maggard
2009-07-21 18:57 ` Eric Sandeen
2009-07-21 19:21 ` Andreas Dilger
2009-07-22 22:27 ` Justin Maggard
2009-07-27 22:03 ` Valerie Aurora
2009-07-30 22:23 ` Valerie Aurora
2009-08-01 1:24 ` Justin Maggard [this message]
2009-08-03 17:20 ` Valerie Aurora
2009-08-11 21:39 ` Valerie Aurora
2009-08-11 22:05 ` Theodore Tso
2009-08-12 1:25 ` Valerie Aurora
2009-08-12 2:04 ` Theodore Tso
2009-08-12 17:59 ` Valerie Aurora
2009-08-28 2:30 ` Justin Maggard
2009-08-28 12:40 ` Theodore Tso
2009-08-28 20:27 ` Justin Maggard
2009-08-12 4:21 ` Eric Sandeen
2009-08-12 5:35 ` Justin Maggard
2009-08-12 14:12 ` Eric Sandeen
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=150c16850907311824n71e36f66i86b508bc25d0c4bb@mail.gmail.com \
--to=jmaggard10@gmail.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=vaurora@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).