[LU-2480] divide error in ldiskfs_mb_normalize_request Created: 12/Dec/12  Updated: 09/Jan/20  Resolved: 09/Jan/20

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.3.0, Lustre 2.1.1, Lustre 2.1.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Alexander Oltu Assignee: Bruno Faccini (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

CPU: AMD Opteron(tm) Processor 6204
CentOS 6.3, kernels:
kernel-2.6.32-279.14.1.el6.x86_64
kernel-2.6.32-279.2.1.el6_lustre.gc46c389.x86_64
kernel-2.6.32-220.el6_lustre.g4554b65.x86_64
kernel-2.6.32-279.5.1.el6_lustre.gb16fe80.x86_64

Severity: 4
Rank (Obsolete): 5821

 Description   

We get OSS crash on any attempt to write data to our Lustre FS. The file system is created from scratch with version 2.1.3 package. We have tried all kernel version from the Env. field.

Initially I thought this was a kernel bug fixed in RHEL kernels-2.6.32-279.10.1.el6

  • [kernel] sched: fix divide by zero at {thread_group,task}

    _times (Stanislaw Gruszka) [856703 843771]

On write attempt we get OSS crashes with the following console message :

divide error: 0000 1 SMP
last sysfs file: /sys/devices/system/cpu/cpu7/cache/index2/shared_cpu_map
CPU 7
Modules linked in: obdfilter(U) fsfilt_ldiskfs(U) ost(U) mgc(U) ldiskfs(U) lustre(U) lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U) nfs fscache xt_multiport nfsd lockd nfs_acl auth_rpcgss exportfs autofs4 sunrpc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables ip6t_REJECT ip6table_filter ip6_tables ipv6 power_meter dcdbas microcode serio_raw ixgbe dca mdio k10temp amd64_edac_mod edac_core edac_mce_amd i2c_piix4 i2c_core sg ses enclosure bnx2 ext4 mbcache jbd2 sr_mod cdrom sd_mod crc_t10dif ahci qla2xxx scsi_transport_fc scsi_tgt megaraid_sas dm_mirror dm_region_hash dm_log dm_mod [last unloaded: mperf]

Pid: 29280, comm: ll_ost_io_127 Not tainted 2.6.32-279.14.1.el6.x86_64 #1 Dell Inc. PowerEdge R715/0C5MMK
RIP: 0010:[<ffffffffa0bb9c24>] [<ffffffffa0bb9c24>] ldiskfs_mb_normalize_request+0xf4/0x3d0 [ldiskfs]
RSP: 0018:ffff8804141a73e0 EFLAGS: 00010246
RAX: 0000000000020000 RBX: ffff88041c783898 RCX: 0000000000000003
RDX: 0000000000000000 RSI: 0000000000020100 RDI: 0000000000000000
RBP: ffff8804141a7430 R08: 0000000000000000 R09: 0000000000020000
R10: ffff88041c00e540 R11: 0000000000000000 R12: 0000000000000100
R13: ffff8804141a7500 R14: ffff88041c09dc00 R15: ffff8803908729c8
FS: 00007f5a66dde700(0000) GS:ffff880323c20000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000006dbf98 CR3: 000000041c04f000 CR4: 00000000000406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process ll_ost_io_127 (pid: 29280, threadinfo ffff8804141a6000, task ffff8804141a2aa0)
Stack:
ffff8804141a7400 ffffffffa0bb3c7f ffff8804141a7430 ffffffffa0bba212
<d> ffff8804141a7430 ffff8804141a7500 0000000000000100 ffff880418bfd000
<d> ffff88041c09dc00 ffff88041c783898 ffff8804141a74d0 ffffffffa0bc13aa
Call Trace:
[<ffffffffa0bb3c7f>] ? ldiskfs_dirty_inode+0x4f/0x60 [ldiskfs]
[<ffffffffa0bba212>] ? ldiskfs_mb_initialize_context+0x82/0x1f0 [ldiskfs]
[<ffffffffa0bc13aa>] ldiskfs_mb_new_blocks+0x42a/0x660 [ldiskfs]
[<ffffffff811adb49>] ? __find_get_block+0xa9/0x200
[<ffffffff811adccc>] ? __getblk+0x2c/0x2e0
[<ffffffff811639bc>] ? __kmalloc+0x20c/0x220
[<ffffffffa0c68fca>] ldiskfs_ext_new_extent_cb+0x59a/0x6d0 [fsfilt_ldiskfs]
[<ffffffffa0ba869f>] ldiskfs_ext_walk_space+0x14f/0x340 [ldiskfs]
[<ffffffffa0c68a30>] ? ldiskfs_ext_new_extent_cb+0x0/0x6d0 [fsfilt_ldiskfs]
[<ffffffffa0c68758>] fsfilt_map_nblocks+0xd8/0x100 [fsfilt_ldiskfs]
[<ffffffffa00fced5>] ? start_this_handle+0xe5/0x500 [jbd2]
[<ffffffffa0c68893>] fsfilt_ldiskfs_map_ext_inode_pages+0x113/0x220 [fsfilt_ldiskfs]
[<ffffffffa0c68a25>] fsfilt_ldiskfs_map_inode_pages+0x85/0x90 [fsfilt_ldiskfs]
[<ffffffffa0cae99b>] filter_do_bio+0xdcb/0x18f0 [obdfilter]
[<ffffffffa0c67580>] ? fsfilt_ldiskfs_brw_start+0x280/0x5a0 [fsfilt_ldiskfs]
[<ffffffffa0cb115e>] filter_commitrw_write+0x145e/0x2e78 [obdfilter]
[<ffffffffa04d8c1b>] ? lnet_send+0x29b/0xa60 [lnet]
[<ffffffff8107ebe2>] ? del_timer_sync+0x22/0x30
[<ffffffff814ff1ca>] ? schedule_timeout+0x19a/0x2e0
[<ffffffffa0ca4252>] filter_commitrw+0x272/0x290 [obdfilter]
[<ffffffffa0c35bdd>] obd_commitrw+0x11d/0x3c0 [ost]
[<ffffffffa0c3dd94>] ost_brw_write+0xcc4/0x1600 [ost]
[<ffffffffa06a2000>] ? target_bulk_timeout+0x0/0xc0 [ptlrpc]
[<ffffffffa0c42e37>] ost_handle+0x2b77/0x4270 [ost]
[<ffffffffa06e077c>] ? lustre_msg_get_transno+0x8c/0x100 [ptlrpc]
[<ffffffffa06e7bfb>] ? ptlrpc_update_export_timer+0x4b/0x470 [ptlrpc]
[<ffffffffa06ef7eb>] ptlrpc_main+0xc4b/0x1a40 [ptlrpc]
[<ffffffffa06eeba0>] ? ptlrpc_main+0x0/0x1a40 [ptlrpc]
[<ffffffff8100c14a>] child_rip+0xa/0x20
[<ffffffffa06eeba0>] ? ptlrpc_main+0x0/0x1a40 [ptlrpc]
[<ffffffffa06eeba0>] ? ptlrpc_main+0x0/0x1a40 [ptlrpc]
[<ffffffff8100c140>] ? child_rip+0x0/0x20
Code: 8b 04 ca 4c 39 c0 0f 86 2b 02 00 00 83 c7 01 48 63 cf 48 39 d1 72 e8 48 8d 04 cd f8 ff ff ff 4d 63 04 02 31 d2 44 89 c8 44 89 c7 <48> f7 f7 31 d2 89 c1 8d 46 ff 41 0f af c8 48 f7 f7 89 ca 48 83
RIP [<ffffffffa0bb9c24>] ldiskfs_mb_normalize_request+0xf4/0x3d0 [ldiskfs]
RSP <ffff8804141a73e0>

This error stops us from deploying new lustre setup. Any help is greatly appreciated.

 Comments   
Comment by Bruno Faccini (Inactive) [ 12/Dec/12 ]

Hello,
Did you get any other messages just prior this Oops ???
And also have you tried to [e2]fsck (with "-n" option for "no changes" !!) the OSTs on this OSS ??

Comment by Alexander Oltu [ 12/Dec/12 ]

No messages prior to crash.
This happens with any OST which gets data to be written.

Fsck is OK:
[root@eik-oss1 ~]# e2fsck LABEL=workcmn1-OST0000
e2fsck 1.42.3.wc3 (15-Aug-2012)
workcmn1-OST0000: recovering journal
Setting free blocks count to 1952053240 (was 1952104696)
workcmn1-OST0000: clean, 121/15261952 files, 1467400/1953520640 blocks
[root@eik-oss1 ~]# e2fsck -n LABEL=workcmn1-OST0000
e2fsck 1.42.3.wc3 (15-Aug-2012)
workcmn1-OST0000: clean, 121/15261952 files, 1467400/1953520640 blocks

e2fsck -f LABEL=workcmn1-OST0000
e2fsck 1.42.3.wc3 (15-Aug-2012)
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
workcmn1-OST0000: 121/15261952 files (1.7% non-contiguous), 1467400/1953520640 blocks

Comment by Bruno Faccini (Inactive) [ 12/Dec/12 ]

Ok, thank's, and BTW I forgot to ask if any crash-dump has been taken at the time of the crashes ??

Comment by Alexander Oltu [ 12/Dec/12 ]

Yes, I have crash dumps they are around 100 MB. I can make a new crash dump with whamcloud kernel so that you have all debug symbols and I can provide vmcore file. Plz let me know where I can upload the file.

BTW. I have tried mounting OST as an ext4 and writing files locally on the OSS is happening fine. But as soon as I mount it as ldiskfs it crashes.

Comment by Alexander Oltu [ 12/Dec/12 ]

Bruno, I have dd'ed with zeros begging of OST, reformatted with additional mkfs.options, disabled max_sectors optimizations and used mkfsoptions like stride and stripe_width with smaller values. The OST stopped crashing.

I am going to add optimizations and reformat with proper stride, stripe_width and see.

Comment by Bruno Faccini (Inactive) [ 12/Dec/12 ]

That was my next question, after your previous comment about ext4 mounts beeing ok but not ldiskfs mounts !!..., how did you format your OSTs ???

Comment by Alexander Oltu [ 12/Dec/12 ]

I didn't use any mkfsoptions initially, because I couldn't find real block size for our DDN S2A9550. And surprisingly the default is :
RAID stripe width: 16384 !!!

So now I am using our cache block size on DDNs of 1024k and RAID 8+2 so using the following options:
mkfs.lustre --mkfsoptions="-m0 -E stripe_width=2048,stride=256" --fsname=workcmn1 --ost --mgsnode=192.168.110.11@tcp0 --mgsnode=192.168.111.11@tcp1 /dev/sdb

It is not crashing now. So I will reformat all our OSTs and will make a try.
I am just afraid that the stride is too big (2048 Segments of 1024 Kbytes per controller) and we are going to have 6 OSTs per controller . Maybe I can use LUN block size of 4096 (-E stripe_width=8,stride=1). Bruno, can you advise?
thanks,
Alex.

Comment by Bruno Faccini (Inactive) [ 13/Dec/12 ]

Have a look to the "Lustre Operations Manual", chapter "Configuring Storage on a Lustre File System" and adapt with your DDN S2A9550 OST/LUN design. But just to answer your last comment/question, the "stride" should be the size/4K-blocks to be written at a time on each of the disks which makes your RAID6/8+2 OSTs, and the "stripe-width" should be the optimal IO-size to fit your RAID design, so 2048=256x8 appear ok for me.

Comment by Alexander Oltu [ 13/Dec/12 ]

Bruno, thank you for suggestions! I ended up using stripe_width=2048,stride=256.

The only 2 open questions are:

  • Why when I mkfs.lustre --ost without "stripe_width" and "stride" get "stripe_width" of 16384
  • Why ldiskfs crashes with "divide zero" when using such a big "stripe_width"
Comment by Andreas Dilger [ 09/Jan/20 ]

Close old ticket.

Generated at Sat Feb 10 06:16:51 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.