From: Lachlan McIlroy <lachlan@sgi.com>
To: xfs@oss.sgi.com
Subject: Re: 2.6.24-rc3 oopses while mounting fs
Date: Mon, 03 Dec 2007 14:24:57 +1100 [thread overview]
Message-ID: <47537709.9040406@sgi.com> (raw)
In-Reply-To: <20071130223154.GB13589@luba>
Okay, sounds like it might be a corrupt log.
Can you run xfs_logprint on the device or saved log?
Also give xfs_logprint -t -i a go.
You've saved the log into a file? You can get the
filesystem mounted again by deleting the log with
xfs_repair -L <dev>. You'll probably need to run
xfs_repair over the filesystem to be safe.
KELEMEN Peter wrote:
> * Lachlan Mcilroy (lachlan@sgi.com) [20071129 10:56]:
>
> Lachlan,
>
>> This looks like a problem we've just fixed, try this patch.
>> We'll get this to mainline soon.
>
> Thanks for the patch. Unfortunately, it does not seem to fix my
> problem. Attempting to mount the filesystem still results in an
> oops.
>
> Peter
>
> -----8<---
> SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
> SGI XFS Quota Management subsystem
> XFS mounting filesystem sdc
> Starting XFS recovery on filesystem: sdc (logdev: internal)
> Unable to handle kernel paging request at ffffc20001c9b000 RIP:
> [<ffffffff881c6175>] :xfs:xlog_recover_add_to_trans+0x64/0xef
> PGD 15781d067 PUD 15781c067 PMD 130fd3067 PTE 0
> Oops: 0000 [1] SMP
> CPU 1
> Modules linked in: xfs sd_mod 3w_9xxx scsi_mod ohci_hcd uhci_hcd ehci_hcd ipv6 bnx2 sky2 r8169 ns838
> 20 dl2k acenic e100 tg3 e1000 mii
> Pid: 2431, comm: mount Not tainted 2.6.24-rc3-xfsbuf #2
> RIP: 0010:[<ffffffff881c6175>] [<ffffffff881c6175>] :xfs:xlog_recover_add_to_trans+0x64/0xef
> RSP: 0018:ffff8101320d9728 EFLAGS: 00010286
> RAX: ffffc20001c9c000 RBX: 000000000020bd78 RCX: 00000000001cc280
> RDX: 0000000000000000 RSI: ffffc20001c9b000 RDI: ffffc20001cdbaf8
> RBP: ffff8101320d9758 R08: ffff810157801652 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000002 R12: ffff8101324633b8
> R13: ffffc20001c5b508 R14: ffff810132463110 R15: ffffc20001c5b4fc
> FS: 00002abba6e87b00(0000) GS:ffff810157801708(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffc20001c9b000 CR3: 000000013252a000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process mount (pid: 2431, threadinfo ffff8101320d8000, task ffff810131972000)
> Stack: 0020bd785769c5e8 000000005769c5e8 000000000000000a ffffc20001c5b508
> 000000000000011e ffffc20001c5b4fc ffff8101320d97b8 ffffffff881c79db
> ffffc20001c6a000 00000001881da0bc ffff81013188f000 ffff8101320d9828
> Call Trace:
> [<ffffffff881c79db>] :xfs:xlog_recover_process_data+0x184/0x1d9
> [<ffffffff881c89cb>] :xfs:xlog_do_recovery_pass+0x74b/0x795
> [<ffffffff881c8a52>] :xfs:xlog_do_log_recovery+0x3d/0x82
> [<ffffffff881c8aa9>] :xfs:xlog_do_recover+0x12/0x11c
> [<ffffffff881c8c37>] :xfs:xlog_recover+0x84/0x92
> [<ffffffff881c3125>] :xfs:xfs_log_mount+0x8c/0xe4
> [<ffffffff881cad92>] :xfs:xfs_mountfs+0x67d/0x97b
> [<ffffffff881cbcb7>] :xfs:xfs_mru_cache_create+0x170/0x1d5
> [<ffffffff881b2f04>] :xfs:xfs_fstrm_free_func+0x0/0x81
> [<ffffffff881be67c>] :xfs:xfs_ioinit+0xb/0xd
> [<ffffffff881d0cfa>] :xfs:xfs_mount+0x2bb/0x36b
> [<ffffffff881e12d9>] :xfs:xfs_fs_fill_super+0xd2/0x245
> [<ffffffff802b7b9f>] get_filesystem+0x17/0x39
> [<ffffffff802a4659>] sget+0x3fb/0x418
> [<ffffffff802a4661>] sget+0x403/0x418
> [<ffffffff802a4d79>] set_bdev_super+0x0/0x14
> [<ffffffff802a4ec2>] get_sb_bdev+0x123/0x16f
> [<ffffffff881e1207>] :xfs:xfs_fs_fill_super+0x0/0x245
> [<ffffffff881e145f>] :xfs:xfs_fs_get_sb+0x13/0x18
> [<ffffffff802a5107>] vfs_kern_mount+0x8f/0x11c
> [<ffffffff802a51d8>] do_kern_mount+0x44/0xf4
> [<ffffffff802ba0d3>] do_mount+0x6d8/0x71e
> [<ffffffff80335682>] __up_read+0x93/0x9b
> [<ffffffff80252261>] up_read+0x23/0x27
> [<ffffffff8047a679>] do_page_fault+0x42e/0x7c7
> [<ffffffff80284d61>] zone_statistics+0x64/0x69
> [<ffffffff8027e4e0>] __alloc_pages+0x6b/0x311
> [<ffffffff802ba3c8>] sys_mount+0x8a/0xcc
> [<ffffffff8020bf8e>] system_call+0x7e/0x83
>
> Code: f3 a4 49 89 c7 49 8b 54 24 08 8b 42 18 85 c0 74 0e 3b 42 14
>
next prev parent reply other threads:[~2007-12-03 3:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 13:45 2.6.24-rc3 oopses while mounting fs KELEMEN Peter
2007-11-28 23:56 ` Lachlan McIlroy
2007-11-30 22:31 ` KELEMEN Peter
2007-12-03 3:24 ` Lachlan McIlroy [this message]
2007-12-03 22:02 ` KELEMEN Peter
2007-12-04 0:11 ` Timothy Shimmin
2007-12-04 7:08 ` Lachlan McIlroy
2007-12-04 9:57 ` KELEMEN Peter
2007-12-05 5:47 ` Lachlan McIlroy
2007-12-05 6:38 ` Timothy Shimmin
2007-12-05 7:04 ` Lachlan McIlroy
2007-12-04 9:42 ` KELEMEN Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47537709.9040406@sgi.com \
--to=lachlan@sgi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox