From: Christoph Hellwig <hch@infradead.org>
To: "aluno3@poczta.onet.pl" <aluno3@poczta.onet.pl>
Cc: xfs@oss.sgi.com
Subject: Re: [xfs] Calltrace in 2.6.27 kernel
Date: Thu, 13 Nov 2008 09:32:33 -0500 [thread overview]
Message-ID: <20081113143233.GA7977@infradead.org> (raw)
In-Reply-To: <491C3842.4090902@poczta.onet.pl>
On Thu, Nov 13, 2008 at 03:22:58PM +0100, aluno3@poczta.onet.pl wrote:
> Hi
>
> I tested kernel 2.6.27 with stress test using fsstress,dd,LVM and
> snapshots. After a few hours and overflow of snapshot I got call trace:
>
> device-mapper: snapshots: Invalidating snapshot: Unable to allocate
> exception.
This is a message from device mapper telling your that it got an EIO
in pending_complete()
> I/O error in filesystem ("dm-49") meta-data dev dm-49 block
> 0x1d4c3b0 ("xlog_recover_do..(read#2)")
> error 5 buf count 8192
> XFS: log mount/recovery failed: error 5
> XFS: log mount failed
And now XFS complains that it got this error passed up, so far so good.
> BUG: unable to handle kernel NULL pointer dereference at 0000002c
> IP: [<c029553d>] xfs_log_force_umount+0x3d/0x170
> *pdpt = 00000000345cf001 *pde = 0000000000000000
But ut should not crash. Can you run
addr2line -e /path/to/your/kernel xfs_log_force_umount+0x3d/0x170
(you'll need a kernel with debuginfo for that)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-11-13 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 14:22 [xfs] Calltrace in 2.6.27 kernel aluno3
2008-11-13 14:32 ` Christoph Hellwig [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=20081113143233.GA7977@infradead.org \
--to=hch@infradead.org \
--cc=aluno3@poczta.onet.pl \
--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.