[LU-17017] sanity test_133f: server crashes in start_this_handle in jbd2 Created: 07/Aug/23  Updated: 07/Aug/23  Resolved: 07/Aug/23

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates LU-16982 Crash lustre after umount -d -f /mnt/... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for Neil Brown <neilb@suse.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/2f981161-1a86-4f78-8cdf-440aa8653390

test_133f failed with the following error:

trevis-71vm3 crashed during sanity test_133f

Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/96595 - 4.18.0-477.15.1.el8_8.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/96595 - 4.18.0-477.15.1.el8_lustre.x86_64

<<Please provide additional information about the failure here>>

[ 7772.862639] -----------[ cut here ]-----------
[ 7772.863692] kernel BUG at fs/jbd2/transaction.c:378!
[ 7772.864730] invalid opcode: 0000 1 SMP PTI
[ 7772.865618] CPU: 0 PID: 277903 Comm: kworker/0:0 Kdump: loaded Tainted: G OE --------- - - 4.18.0-477.15.1.el8_lustre.x86_64 #1
[ 7772.867920] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
[ 7772.869012] Workqueue: events flush_stashed_stats_work [ldiskfs]
[ 7772.870294] RIP: 0010:start_this_handle+0x22c/0x520 [jbd2]
[ 7772.871376] Code: 24 30 4c 89 74 24 38 41 83 78 0c 02 74 1e 0f 0b 44 89 e8 f0 0f c1 03 48 89 df e8 1f 89 39 e8 49 8b 07 a8 01 0f 84 83 fe ff ff <0f> 0b 4d 8d 87 88 00 00 00 ba 02 00 00 00 48 8d 74 24 18 4c 89 c7
[ 7772.874738] RSP: 0018:ffffac2c0648bdb0 EFLAGS: 00010202
[ 7772.875726] RAX: 0000000000000031 RBX: ffff97bbb2768044 RCX: 0000000000000000
[ 7772.877049] RDX: 0000000000608840 RSI: 0000000000000000 RDI: ffff97bbb2768044
[ 7772.878369] RBP: ffff97bc04e63e00 R08: ffffac2c0648bd68 R09: ffff97bc04e63e00
[ 7772.879696] R10: ffff97bbca975000 R11: ffff97bb83120150 R12: ffff97bb82461770
[ 7772.881017] R13: 00000000fffffe00 R14: ffffac2c0648bde0 R15: ffff97bbb2768000
[ 7772.882332] FS: 0000000000000000(0000) GS:ffff97bc3cc00000(0000) knlGS:0000000000000000
[ 7772.883814] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7772.884898] CR2: 00007f9160af3000 CR3: 00000000b4410003 CR4: 00000000000606f0
[ 7772.886211] Call Trace:
[ 7772.886753] ? jbd2__journal_start+0x8f/0x1f0 [jbd2]
[ 7772.887722] ? kmem_cache_alloc+0x13f/0x280
[ 7772.888577] jbd2__journal_start+0xee/0x1f0 [jbd2]
[ 7772.889514] jbd2_journal_start+0x19/0x20 [jbd2]
[ 7772.890418] flush_stashed_stats_work+0x36/0x90 [ldiskfs]

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_133f - trevis-71vm3 crashed during sanity test_133f



 Comments   
Comment by Andreas Dilger [ 07/Aug/23 ]

This was already fixed by LU-16982 and the patch just landed today.

Generated at Sat Feb 10 09:47:23 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.