The file system on my big server threw a warning which scares me a little bit.
Warning text:
[1251692.004673] EXT4-fs warning (device sdb1): ext4_da_update_reserve_space:363: ino 353370121, allocated 1 with only 0 reserved metadata blocks (releasing 5 blocks with reserved 5 data blocks)
[1251692.004679] ------------[ cut here ]------------
[1251692.004691] WARNING: CPU: 0 PID: 2023 at /home/abuild/rpmbuild/BUILD/kernel-default-3.11.10/linux-3.11/fs/ext4/inode.c:364 ext4_da_update_reserve_space+0x21e/0x240()
[1251692.004694] Modules linked in: fuse ufs qnx4 hfsplus hfs minix vfat msdos fat jfs xfs reiserfs xt_LOG xt_limit xt_pkttype xt_tcpudp nfsd lockd nfs_acl auth_rpcgss sunrpc oid_registry nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT ipt_REJECT ip6table_raw iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables iTCO_wdt igb ptp pps_core isci libsas scsi_transport_sas ses enclosure iTCO_vendor_support shpchp gpio_ich mxm_wmi x86_pkg_temp_thermal coretemp kvm_intel kvm crc32_pclmul ghash_clmulni_intel aesni_intel ablk_helper cryptd lrw gf128mul glue_helper aes_x86_64 ioatdma mei_me lpc_ich mei mfd_core pcspkr i2c_i801 dca wmi acpi_cpufreq mperf button joydev hid_generic
[1251692.004773] usbhid sg dm_mod autofs4 btrfs raid6_pq zlib_deflate xor libcrc32c crc32c_intel megaraid_sas mgag200 ttm drm_kms_helper drm i2c_algo_bit sysimgblt ehci_pci sysfillrect xhci_hcd ehci_hcd syscopyarea usbcore usb_common processor thermal_sys scsi_dh_emc scsi_dh_alua scsi_dh_rdac scsi_dh_hp_sw scsi_dh
[1251692.004807] CPU: 0 PID: 2023 Comm: nfsd Not tainted 3.11.10-11-default #1
[1251692.004810] Hardware name: Thomas-Krenn.AG X9DR3-F/X9DR3-F, BIOS 3.0a 07/31/2013
[1251692.004813] 0000000000000009 ffffffff8155750b 0000000000000000 ffffffff8104fb82
[1251692.004821] ffff880058aae4a8 ffff880058aae4a8 0000000000000005 0000000000000001
[1251692.004828] ffff88202cf25800 ffffffff811f25ee ffff882000000000 0000002500000005
[1251692.004834] Call Trace:
[1251692.004855] [<ffffffff81004878>] dump_trace+0x78/0x2c0
[1251692.004862] [<ffffffff81004b4f>] show_stack_log_lvl+0x8f/0x170
[1251692.004869] [<ffffffff81005e0c>] show_stack+0x1c/0x50
[1251692.004879] [<ffffffff8155750b>] dump_stack+0x41/0x51
[1251692.004889] [<ffffffff8104fb82>] warn_slowpath_common+0x72/0x90
[1251692.004898] [<ffffffff811f25ee>] ext4_da_update_reserve_space+0x21e/0x240
[1251692.004911] [<ffffffff8121b467>] ext4_ext_map_blocks+0xb97/0xfa0
[1251692.004920] [<ffffffff811f28c5>] ext4_map_blocks+0x2b5/0x520
[1251692.004927] [<ffffffff811f5554>] ext4_writepages+0x514/0xc40
[1251692.004936] [<ffffffff81119ad9>] __filemap_fdatawrite_range+0x49/0x50
[1251692.004942] [<ffffffff81119ba0>] filemap_write_and_wait_range+0x20/0x60
[1251692.004950] [<ffffffff811ed6a9>] ext4_sync_file+0xa9/0x300
[1251692.004969] [<ffffffffa05e5da2>] nfsd_commit+0x92/0xb0 [nfsd]
[1251692.005014] [<ffffffffa05eec45>] nfsd3_proc_commit+0x85/0xe0 [nfsd]
[1251692.005051] [<ffffffffa05e0c6a>] nfsd_dispatch+0xaa/0x1f0 [nfsd]
[1251692.005080] [<ffffffffa057542b>] svc_process_common+0x43b/0x680 [sunrpc]
[1251692.005130] [<ffffffffa0575777>] svc_process+0x107/0x160 [sunrpc]
[1251692.005168] [<ffffffffa05e069f>] nfsd+0xaf/0x120 [nfsd]
[1251692.005180] [<ffffffff8106f8ef>] kthread+0xaf/0xc0
[1251692.005189] [<ffffffff815654fc>] ret_from_fork+0x7c/0xb0
[1251692.005195] ---[ end trace 60606dcc91b5f45f ]---
Version information:
rozrhintt12:/install # uname -a
Linux rozrhintt12 3.11.10-11-default #1 SMP Mon May 12 13:37:06 UTC 2014 (3d22b5f) x86_64 x86_64 x86_64 GNU/Linux
System configuration:
2* Xeon 2500v2 2.5GHz (10 core)
128GB RAM
LSI Logic 9260 or 9270 RAID controller (with battery)
RAID config
disk 0+1: SSD boot disk (RAID 1)
disk 2-15: WD 4TB disks (RAID 6) with ext4 (~44TB capacity) --> yes, we really need so much space! The volume is shared via NFS
The warning occurred while being under very light load (about 2-4 MBytes/s).
It seems that it occurred only once.
Do I have to expect data loss?
Is there a workaround or fix?
Thanks!
Jochen
Warning text:
[1251692.004673] EXT4-fs warning (device sdb1): ext4_da_update_reserve_space:363: ino 353370121, allocated 1 with only 0 reserved metadata blocks (releasing 5 blocks with reserved 5 data blocks)
[1251692.004679] ------------[ cut here ]------------
[1251692.004691] WARNING: CPU: 0 PID: 2023 at /home/abuild/rpmbuild/BUILD/kernel-default-3.11.10/linux-3.11/fs/ext4/inode.c:364 ext4_da_update_reserve_space+0x21e/0x240()
[1251692.004694] Modules linked in: fuse ufs qnx4 hfsplus hfs minix vfat msdos fat jfs xfs reiserfs xt_LOG xt_limit xt_pkttype xt_tcpudp nfsd lockd nfs_acl auth_rpcgss sunrpc oid_registry nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT ipt_REJECT ip6table_raw iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables iTCO_wdt igb ptp pps_core isci libsas scsi_transport_sas ses enclosure iTCO_vendor_support shpchp gpio_ich mxm_wmi x86_pkg_temp_thermal coretemp kvm_intel kvm crc32_pclmul ghash_clmulni_intel aesni_intel ablk_helper cryptd lrw gf128mul glue_helper aes_x86_64 ioatdma mei_me lpc_ich mei mfd_core pcspkr i2c_i801 dca wmi acpi_cpufreq mperf button joydev hid_generic
[1251692.004773] usbhid sg dm_mod autofs4 btrfs raid6_pq zlib_deflate xor libcrc32c crc32c_intel megaraid_sas mgag200 ttm drm_kms_helper drm i2c_algo_bit sysimgblt ehci_pci sysfillrect xhci_hcd ehci_hcd syscopyarea usbcore usb_common processor thermal_sys scsi_dh_emc scsi_dh_alua scsi_dh_rdac scsi_dh_hp_sw scsi_dh
[1251692.004807] CPU: 0 PID: 2023 Comm: nfsd Not tainted 3.11.10-11-default #1
[1251692.004810] Hardware name: Thomas-Krenn.AG X9DR3-F/X9DR3-F, BIOS 3.0a 07/31/2013
[1251692.004813] 0000000000000009 ffffffff8155750b 0000000000000000 ffffffff8104fb82
[1251692.004821] ffff880058aae4a8 ffff880058aae4a8 0000000000000005 0000000000000001
[1251692.004828] ffff88202cf25800 ffffffff811f25ee ffff882000000000 0000002500000005
[1251692.004834] Call Trace:
[1251692.004855] [<ffffffff81004878>] dump_trace+0x78/0x2c0
[1251692.004862] [<ffffffff81004b4f>] show_stack_log_lvl+0x8f/0x170
[1251692.004869] [<ffffffff81005e0c>] show_stack+0x1c/0x50
[1251692.004879] [<ffffffff8155750b>] dump_stack+0x41/0x51
[1251692.004889] [<ffffffff8104fb82>] warn_slowpath_common+0x72/0x90
[1251692.004898] [<ffffffff811f25ee>] ext4_da_update_reserve_space+0x21e/0x240
[1251692.004911] [<ffffffff8121b467>] ext4_ext_map_blocks+0xb97/0xfa0
[1251692.004920] [<ffffffff811f28c5>] ext4_map_blocks+0x2b5/0x520
[1251692.004927] [<ffffffff811f5554>] ext4_writepages+0x514/0xc40
[1251692.004936] [<ffffffff81119ad9>] __filemap_fdatawrite_range+0x49/0x50
[1251692.004942] [<ffffffff81119ba0>] filemap_write_and_wait_range+0x20/0x60
[1251692.004950] [<ffffffff811ed6a9>] ext4_sync_file+0xa9/0x300
[1251692.004969] [<ffffffffa05e5da2>] nfsd_commit+0x92/0xb0 [nfsd]
[1251692.005014] [<ffffffffa05eec45>] nfsd3_proc_commit+0x85/0xe0 [nfsd]
[1251692.005051] [<ffffffffa05e0c6a>] nfsd_dispatch+0xaa/0x1f0 [nfsd]
[1251692.005080] [<ffffffffa057542b>] svc_process_common+0x43b/0x680 [sunrpc]
[1251692.005130] [<ffffffffa0575777>] svc_process+0x107/0x160 [sunrpc]
[1251692.005168] [<ffffffffa05e069f>] nfsd+0xaf/0x120 [nfsd]
[1251692.005180] [<ffffffff8106f8ef>] kthread+0xaf/0xc0
[1251692.005189] [<ffffffff815654fc>] ret_from_fork+0x7c/0xb0
[1251692.005195] ---[ end trace 60606dcc91b5f45f ]---
Version information:
rozrhintt12:/install # uname -a
Linux rozrhintt12 3.11.10-11-default #1 SMP Mon May 12 13:37:06 UTC 2014 (3d22b5f) x86_64 x86_64 x86_64 GNU/Linux
System configuration:
2* Xeon 2500v2 2.5GHz (10 core)
128GB RAM
LSI Logic 9260 or 9270 RAID controller (with battery)
RAID config
disk 0+1: SSD boot disk (RAID 1)
disk 2-15: WD 4TB disks (RAID 6) with ext4 (~44TB capacity) --> yes, we really need so much space! The volume is shared via NFS
The warning occurred while being under very light load (about 2-4 MBytes/s).
It seems that it occurred only once.
Do I have to expect data loss?
Is there a workaround or fix?
Thanks!
Jochen