Hi,<br>
<br>
fsck has finished and does not find any more errors to correct. However
when I try to mount the device as ldiskfs kernel panics with following
message:<br>
<br>
Assertion failure in cleanup_journal_tail() at fs/jbd/checkpoint.c:459: "blocknr != 0"<br>
----------- [cut here ] --------- [please bite here ] ---------<br>
Kernel BUG at fs/jbd/checkpoint.c:459<br>
invalid opcode: 0000 [1] SMP<br>
last sysfs file: /class/infiniband_mad/umad0/
<div id=":1em">port<br>CPU 2<br>Modules
linked in: obdfilter(U) fsfilt_ldiskfs(U) ost(U) mgc(U) ldiskfs(U)
crc16(U) lustre(U) lov(U) mdc(U) lquota(U) osc(U) ksocklnd(U)
ko2iblnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U) autofs4(U)
hidp(U) l2cap(U) bluetooth(U) rdma_ucm(U) rdma_cm(U) iw_cm(U) ib_addr(U)
ib_ipoib(U) ipoib_helper(U) ib_cm(U) ipv6(U) xfrm_nalgo(U)
crypto_api(U) ib_uverbs(U) ib_umad(U) mlx4_vnic(U) mlx4_vnic_helper(U)
ib_sa(U) ib_mthca(U) mptctl(U) dm_mirror(U) video(U) backlight(U) sbs(U)
power_meter(U) hwmon(U) i2c_ec(U) i2c_core(U) dell_wmi(U) wmi(U)
button(U) battery(U) asus_acpi(U) acpi_memhotplug(U) ac(U) parport_pc(U)
lp(U) parport(U) sr_mod(U) cdrom(U) mlx4_ib(U) ib_mad(U) ib_core(U)
joydev(U) mlx4_core(U) usb_storage(U) shpchp(U) i5000_edac(U) edac_mc(U)
serio_raw(U) pcspkr(U) dm_raid45(U) dm_message(U) dm_region_hash(U)
dm_log(U) dm_mod(U) dm_mem_cache(U) nfs(U) lockd(U) fscache(U)
nfs_acl(U) sunrpc(U) mptsas(U) mptscsih(U) mptbase(U)
scsi_transport_sas(U) mppVhba(U) megaraid_sas(U) mppUpper(U) sg(U)
sd_mod(U) scsi_mod(U) bnx2(U) ext3(U) jbd(U) uhci_hcd(U) ohci_hcd(U)
ehci_hcd(U)<br>
Pid: 13891, comm: mount Tainted: G 2.6.18-194.3.1.el5_lustre.1.8.4 #1<br>RIP: 0010:[<ffffffff88034a95>] [<ffffffff88034a95>] :jbd:cleanup_journal_tail+0x9d/0x118<br>RSP: 0018:ffff81016f00da68 EFLAGS: 00010286<br>
RAX: 000000000000005a RBX: ffff81012ca12c00 RCX: ffffffff80311da8<br>RDX: ffffffff80311da8 RSI: 0000000000000000 RDI: ffffffff80311da0<br>RBP: 0000000000000000 R08: ffffffff80311da8 R09: 0000000000000001<br>R10: 0000000000000000 R11: 0000000000000080 R12: 0000000000000002<br>
R13: ffff81012ca12d4c R14: ffff81012ca12c24 R15: ffff81017a8d7400<br>FS: 00002abd7cef1f70(0000) GS:ffff810107b9acc0(0000) knlGS:0000000000000000<br>CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b<br>CR2: 000000000042b000 CR3: 000000012813f000 CR4: 00000000000006e0<br>
Process mount (pid: 13891, threadinfo ffff81016f00c000, task ffff81022e1b7820)<br>Stack: 0000000000000000 ffff81012ca12c00 ffff81017a8d7400 ffffffff88037690<br>ffff81012ca12c00 ffff8102034ff000 ffff81017a8d7400 0000000000000000<br>
ffff8102034ff000 ffffffff88a9be56 0000000001000000 ffff8101bf788000<br>Call Trace:<br>[<ffffffff88037690>] :jbd:journal_flush+0xbe/0x248<br>[<ffffffff88a9be56>] :ldiskfs:ldiskfs_mark_recovery_complete+0x36/0x90<br>
[<ffffffff88aa02e0>] :ldiskfs:ldiskfs_fill_super+0x1790/0x1950<br>[<ffffffff800eccd2>] get_filesystem+0x12/0x3b<br>[<ffffffff800e343e>] test_bdev_super+0x0/0xd<br>[<ffffffff88a9eb50>] :ldiskfs:ldiskfs_fill_super+0x0/0x1950<br>
[<ffffffff800e43fd>] get_sb_bdev+0x10a/0x16c<br>[<ffffffff800e3d9a>] vfs_kern_mount+0x93/0x11a<br>[<ffffffff800e3e63>] do_kern_mount+0x36/0x4d<br>[<ffffffff800ee601>] do_mount+0x6a9/0x719<br>[<ffffffff800090d2>] __handle_mm_fault+0x96f/0xfaa<br>
[<ffffffff8002c9e0>] mntput_no_expire+0x19/0x89<br>[<ffffffff8000a72a>] __link_path_walk+0xf1e/0xf42<br>[<ffffffff800220ce>] __up_read+0x19/0x7f<br>[<ffffffff80066b88>] do_page_fault+0x4fe/0x874<br>
[<ffffffff8002c9e0>] mntput_no_expire+0x19/0x89<br>[<ffffffff8000ea45>] link_path_walk+0xa6/0xb2<br>[<ffffffff800cc329>] zone_statistics+0x3e/0x6d<br>[<ffffffff8000f2cf>] __alloc_pages+0x78/0x308<br>
[<ffffffff8004c68e>] sys_mount+0x8a/0xcd<br>[<ffffffff8005d28d>] tracesys+0xd5/0xe0<br><br><br>Code: 0f 0b 68 3a 94 03 88 c2 cb 01 44 39 a3 58 01 00 00 75 0e c7<br>RIP [<ffffffff88034a95>] :jbd:cleanup_journal_tail+0x9d/0x118<br>
RSP <ffff81016f00da68><br><0>Kernel panic - not syncing: Fatal exception<br>
<br>
Any idea how to fix this?<br>
<br>
Many thanks<br>
<br>
Wojciech<br>
</div>
<br><br><div class="gmail_quote">On 21 October 2010 17:54, Wojciech Turek <span dir="ltr"><<a href="mailto:wjt27@cam.ac.uk">wjt27@cam.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Thanks Ken, that worked.<div><div></div><div class="h5"><br><br><div class="gmail_quote">On 21 October 2010 17:39, Ken Hornstein <span dir="ltr"><<a href="mailto:kenh@cmf.nrl.navy.mil" target="_blank">kenh@cmf.nrl.navy.mil</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>>Now I have another problem. After last segfault I can not restart the fsck<br>
>due to MMP.<br>
</div>>[...]<br>
<div>>Also when I try to access filesystem via debugfs it fails:<br>
><br>
>debugfs -c -R 'ls' /dev/scratch2_ost16vg/ost16lv<br>
>debugfs 1.41.10.sun2 (24-Feb-2010)<br>
>/dev/scratch2_ost16vg/ost16lv: MMP: fsck being run while opening filesystem<br>
>ls: Filesystem not open<br>
><br>
>Is there a way to clear teh MMP flag so it allows fsck to run?<br>
<br>
</div>You want tune2fs -f -E clear-mmp<br>
<font color="#888888"><br>
--Ken<br>
</font></blockquote></div><br><br>
</div></div></blockquote></div><br>