From: David Greaves <david@dgreaves.com>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc3: XFS internal error xlog_clear_stale_blocks(1)
Date: Sun, 04 Jun 2006 11:10:23 +0100 [thread overview]
Message-ID: <4482B18F.1050606@dgreaves.com> (raw)
In-Reply-To: <4482AB6A.9010105@dgreaves.com>
David Greaves wrote:
> Hi
>
> vanilla 2.6.17-rc3
>
> mounting onto an lvm2 ontop of raid5 on top of sata
>
> Filesystem "dm-0": Disabling barriers, not supported by the underlying
> device
> XFS mounting filesystem dm-0
> Filesystem "dm-0": XFS internal error xlog_clear_stale_blocks(1) at line
> 1225 of file fs/xfs/xfs_log_recover.c. Caller 0xb01fca2f
> <b01fb8d9> xlog_find_tail+0xa39/0xeb0 <b01fca2f> xlog_recover+0x2f/0x2f0
> <b01fca2f> xlog_recover+0x2f/0x2f0 <b01f5566> xfs_log_mount+0x256/0x650
> <b01fec19> xfs_mountfs+0xd09/0x1260 <b021b199>
> xfs_mountfs_check_barriers+0x39/0x120
> <b0207cef> xfs_mount+0xa2f/0xbf0 <b021c130> xfs_fs_fill_super+0xa0/0x250
> <b0237e8b> snprintf+0x2b/0x30 <b0198095> disk_name+0xd5/0xf0
> <b016644f> sb_set_blocksize+0x1f/0x50 <b0165407> get_sb_bdev+0x117/0x155
> <b021b6ff> xfs_fs_get_sb+0x2f/0x40 <b021c090> xfs_fs_fill_super+0x0/0x250
> <b0164882> do_kern_mount+0x52/0xe0 <b017cd1d> do_mount+0x29d/0x770
> <b016eb8e> do_path_lookup+0x10e/0x270 <b016c35a> getname+0xda/0x100
> <b014219e> __alloc_pages+0x5e/0x2f0 <b01426e4> __get_free_pages+0x34/0x60
> <b017b824> copy_mount_options+0x44/0x140 <b017d28d> sys_mount+0x9d/0xe0
> <b010304b> syscall_call+0x7/0xb
> XFS: failed to locate log tail
> XFS: log mount/recovery failed: error 990
> XFS: log mount failed
>
>
> Anything else I can do?
> (is it worth trying -rc5?)
>
> I'm building 2.6.16.19 and I'll try that shortly...
>
> David
>
So I tried 2.6.17-rc5 and the problem resolved itself.
David
--
prev parent reply other threads:[~2006-06-04 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 9:44 2.6.17-rc3: XFS internal error xlog_clear_stale_blocks(1) David Greaves
2006-06-04 10:10 ` David Greaves [this message]
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=4482B18F.1050606@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.