After this, the system started logging a lot of this same message:
| EXT4-fs error (device vdb): ext4_find_extent:900: inode #84149503: comm deluged:
| pblk 225181822 bad header/extent: invalid magic - magic 53fd, entries 37907,
| max 27407(0), depth 50401(0)
Ran e2fsck and got:
| Pass 5: Checking group summary information
| Block bitmap differences: +(1431556444--1431556445) +(2469410748-2469410749)
| Free blocks count wrong (134030133, counted=57970467).
| Free inodes count wrong (670746893, counted=670746452).
Which is usually the same output for fsck in these situations.
This server is a QEMU KVM virtual machine running on Intel x64 hardware.
This bug report is about ext4 metadata corruption on large (>=10TB) ext4 volumes. marc.info/ ?l=linux- ext4&m= 139878494527370 &w=2 ]
This was also reported in 2014 [ http://
I'm getting sporadic FS errors like this one: /8n1.org/ 10745/cc34)
(More of these i've pasted at https:/
| EXT4-fs error (device vdb): ext4_mb_ generate_ buddy:757:
| group 79842, block bitmap and bg descriptor inconsistent: 10073 vs 10071
| free clusters
| Aborting journal on device vdb-8.
An e2fsck run then shows: -2616281447)
| Pass 5: Checking group summary information
| Block bitmap differences: +(2616281446-
| Free blocks count wrong (170942497, counted=129906218).
| Free inodes count wrong (670863012, counted=670860975).
I've patched my kernel with WARN_ON(1); inserted in tactical places and caught
one such situation:
| EXT4-fs (vdb): pa ffff880016544888: logic 982168, phys. 2469410748, len 104 release_ inode_pa: 3773: group 75360, free 38, pa_free 36 mballoc. c:3774 ext4_mb_ release_ inode_pa. isra.27+ 0x1cb/0x2c0( ) 760>] dump_stack+ 0x45/0x57 96a>] warn_slowpath_ common+ 0x8a/0xc0 a5a>] warn_slowpath_ null+0x1a/ 0x20 1bb>] ext4_mb_ release_ inode_pa. isra.27+ 0x1cb/0x2c0 9df>] ? ext4_read_ block_bitmap_ nowait+ 0x26f/0x5f0 c6a>] ext4_discard_ preallocations+ 0x30a/0x490 578>] ext4_da_ update_ reserve_ space+0x178/ 0x1b0 129>] ext4_ext_ map_blocks+ 0xcd9/0xe50 6d9>] ext4_map_ blocks+ 0x129/0x570 89d>] ? ext4_writepages +0x35d/ 0xca0 3a9>] ? __ext4_ journal_ start_sb+ 0x69/0xe0 ac2>] ext4_writepages +0x582/ 0xca0 a4e>] do_writepages+ 0x1e/0x30 be9>] __filemap_ fdatawrite_ range+0x59/ 0x60 c4c>] filemap_ write_and_ wait+0x2c/ 0x60 03d>] do_vfs_ ioctl+0x3fd/ 0x4e0 1a1>] SyS_ioctl+0x81/0xa0 84d>] system_ call_fastpath+ 0x16/0x1b :2412: IO failure
| EXT4-fs error (device vdb): ext4_mb_
| Aborting journal on device vdb-8.
| EXT4-fs (vdb): Remounting filesystem read-only
| ------------[ cut here ]------------
| WARNING: CPU: 1 PID: 1706 at fs/ext4/
| Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter xt_tcpudp ip6_tables
| nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables
| x_tables cirrus ttm drm_kms_helper drm kvm_intel kvm ppdev syscopyarea sysfillrect
| 8250_fintek serio_raw i2c_piix4 sysimgblt pvpanic parport_pc mac_hid nfsd auth_rpcgss nfs_acl
| lockd grace sunrpc lp parport autofs4 psmouse floppy pata_acpi
| CPU: 1 PID: 1706 Comm: deluged Not tainted 3.19.8-ckt4 #1
| Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
| ffffffff81ab4fef ffff8800da1bb978 ffffffff817c3760 0000000000000007
| 0000000000000000 ffff8800da1bb9b8 ffffffff8107696a ffff8800da1bb9a8
| 0000000000000026 0000000000003825 0000000000003824 ffff880016544888
| Call Trace:
| [<ffffffff817c3
| [<ffffffff81076
| [<ffffffff81076
| [<ffffffff812b0
| [<ffffffff81273
| [<ffffffff812b3
| [<ffffffff8127b
| [<ffffffff812a9
| [<ffffffff8127b
| [<ffffffff8127e
| [<ffffffff812ab
| [<ffffffff8127e
| [<ffffffff81187
| [<ffffffff8117b
| [<ffffffff8117b
| [<ffffffff81209
| [<ffffffff81209
| [<ffffffff817ca
| ---[ end trace c7de4d0d78cb95b6 ]---
| EXT4-fs error (device vdb) in ext4_writepages
| EXT4-fs (vdb): ext4_writepages: jbd2_start: 9223372036854775751 pages, ino 84149503; err -30
After this, the system started logging a lot of this same message: extent: 900: inode #84149503: comm deluged:
| EXT4-fs error (device vdb): ext4_find_
| pblk 225181822 bad header/extent: invalid magic - magic 53fd, entries 37907,
| max 27407(0), depth 50401(0)
Ran e2fsck and got: -1431556445) +(2469410748- 2469410749)
| Pass 5: Checking group summary information
| Block bitmap differences: +(1431556444-
| Free blocks count wrong (134030133, counted=57970467).
| Free inodes count wrong (670746893, counted=670746452).
Which is usually the same output for fsck in these situations.
This server is a QEMU KVM virtual machine running on Intel x64 hardware.