uninit block group/mballoc and fsstress
I am hitting this with the below config
mke2fs -j -I 256 -O lazy_bg $dev
mount -t ext4dev $dev /mnt/tmp -o "extents,mballoc"
and running fsstress on /mnt/tmp/
jbd2_journal_bmap: journal block not found at offset 31780 on sda7
Aborting journal on device sda7.
ext4_abort called.
EXT4-fs error (device sda7): ext4_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_ordered_commit_write: IO failure
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_ordered_writepage: IO failure
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_orphan_del: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
Quoted 8 lines · Aneesh Kumar K.V
I am hitting this with the below config
mke2fs -j -I 256 -O
lazy_bg$devmount -t ext4dev $dev
/mnt/tmp-o "extents,mballoc"and running fsstress on
/mnt/tmp/
I re-ran the test without the mballoc mount option, but with lazy_bg enabled, and saw the same error. Error messages and stack are below.
mke2fs -j -I 256 -O lazy_bg $dev
mount -t ext4dev $dev /mnt/tmp -o "extents"
...
EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted
Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xc0000000001af07c
cpu 0x2: Vector: 300 (Data Access) at [c0000000fdf4b9b0]
pc: c0000000001af07c: .jbd2_journal_commit_transaction+0x11e8/0x1af4
lr: c0000000001af05c: .jbd2_journal_commit_transaction+0x11c8/0x1af4
sp: c0000000fdf4bc30
msr: 8000000000009032
dar: 0
dsisr: 40000000
current = 0xc0000000fc0f47f0
paca = 0xc000000000537880
pid = 5895, comm = kjournald2
enter ? for help
[c0000000fdf4be00] c0000000001b2994 .kjournald2+0xf4/0x2ac
[c0000000fdf4bf00] c00000000007afcc .kthread+0x84/0xd0
[c0000000fdf4bf90] c000000000027548 .kernel_thread+0x4c/0x68
2:mon>-- 0:conmux-control -- time-stamp -- Oct/10/07 11:28:02 -- -- 0:conmux-control -- time-stamp -- Oct/10/07 14:49:26 -- (bot:conmon-payload) disconnected
Quoted 3 lines · Aneesh Kumar K.V
I am hitting this with the below config
mke2fs -j -I 256 -O
lazy_bg$dev
Note that "-O lazy_bg" has nothing really to do with the uninit_groups feature. Also, if you don't have the CFS e2fsprogs patches for uninit_groups then mke2fs creates an invalid filesystem if the journal is large (this was an unrelated bug we fixed while testing uninit_groups). Try running e2fsck right after the above mke2fs and you will likely see errors.
Quoted 1 line
jbd2_journal_bmap: journal block not found at offset 31780 on sda7
The problem is that lazy_bg allocates the journal blocks incorrectly, IIRC.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
Quoted 12 lines · Andreas Dilger
Quoted 3 lines · Aneesh Kumar K.V
I am hitting this with the below config
mke2fs -j -I 256 -O
lazy_bg$devNote that "-O
lazy_bg" has nothing really to do with theuninit_groupsfeature. Also, if you don't have the CFS e2fsprogs patches foruninit_groupsthen mke2fs creates an invalid filesystem if the journal is large (this was an unrelated bug we fixed while testinguninit_groups). Try running e2fsck right after the above mke2fs and you will likely see errors.
e2fsprogs found at
ftp://ftp.clusterfs.com/pub/lustre/other/e2fsprogs
sets unint with -O lazy_bg. Is there any other option that i can use to set the uninit block group feature ?
Quoted 11 lines
Quoted 1 line
jbd2_journal_bmap: journal block not found at offset 31780 on sda7The problem is that
lazy_bgallocates the journal blocks incorrectly, IIRC.Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
Quoted 14 lines · Aneesh Kumar K.V
Quoted 12 lines · Andreas Dilger
Quoted 3 lines · Aneesh Kumar K.V
I am hitting this with the below config
mke2fs -j -I 256 -O
lazy_bg$devNote that "-O
lazy_bg" has nothing really to do with theuninit_groupsfeature. Also, if you don't have the CFS e2fsprogs patches foruninit_groupsthen mke2fs creates an invalid filesystem if the journal is large (this was an unrelated bug we fixed while testinguninit_groups). Try running e2fsck right after the above mke2fs and you will likely see errors.
Quoted 6 lines
e2fsprogs found at
ftp://ftp.clusterfs.com/pub/lustre/other/e2fsprogs
sets unint with -O
lazy_bg. Is there any other option that i can use to set the uninit block group feature ?
Yes, "-O uninit_groups". Note that while "-O lazy_bg" does set the UNINIT flags on the groups (this is a COMPAT feature that marks all of the groups full in the group descriptors), it does NOT handle the inode high watermark or in-kernel initialization of the bitmaps.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.