From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Nathan Scott" <nathans@sgi.com>
Cc: "Avuton Olrich" <avuton@gmail.com>,
"Tony. Ho" <linux@idccenter.cn>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078
Date: Fri, 11 Aug 2006 01:01:23 +0200 [thread overview]
Message-ID: <9a8748490608101601t18ea4a30xa467b44feeeb6b5@mail.gmail.com> (raw)
In-Reply-To: <9a8748490608101544n29f863e7o7584ac64f1d4c210@mail.gmail.com>
On 11/08/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 11/08/06, Nathan Scott <nathans@sgi.com> wrote:
> > On Thu, Aug 10, 2006 at 01:31:35PM +0200, Jesper Juhl wrote:
> > > On 08/08/06, Nathan Scott <nathans@sgi.com> wrote:
> > > ...
> > > Ok, I booted the server with 2.6.18-rc4 + your patch. Things went well
> > > for ~3 hours and then blew up - not in the same way though.
> > >
> > > The machine was under pretty heavy load recieving data via rsync when
> > > the following happened :
> > >
> > > Filesystem "dm-51": XFS internal error xfs_trans_cancel at line 1138
> > > of file fs/xfs/xfs_trans.c. Caller 0xc0210e3f
> > > [<c0103a3c>] show_trace_log_lvl+0x152/0x165
> > > [<c0103a5e>] show_trace+0xf/0x13
> > > [<c0103b59>] dump_stack+0x15/0x19
> > > [<c0213474>] xfs_trans_cancel+0xcf/0xf8
> > > [<c0210e3f>] xfs_rename+0x64d/0x936
> > > [<c0226286>] xfs_vn_rename+0x48/0x9f
> > > [<c016584e>] vfs_rename_other+0x99/0xcb
> > > [<c0165a36>] vfs_rename+0x1b6/0x1eb
> > > [<c0165bda>] do_rename+0x16f/0x193
> > > [<c0165c45>] sys_renameat+0x47/0x73
> >
> > Thanks Jesper. Hmm, lessee - this is a cancelled dirty rename
> > transaction ... could be ondisk dir2 corruption (any chance this
> > filesystem was affected by 2.6.17's endian bug?)
>
> No. The machine in question never ran any 2.6.17.* kernels. Its old
> kernel was 2.6.11.11 (UP), then I tried 2.6.18-rc3-git3 (SMP) as
> previously reported, then I tried 2.6.18-rc4 + your XFS patch.
>
Small correction; The above is not 100% true. A single attempt was
made to boot the server with a 2.6.17.7 kernel but the e1000 driver
blew up with that kernel version and hung the box before any of these
filesystems were mounted (at least that's how it appeared since it
didn't *seem* to get any further than loading the e1000 driver - which
happens before these fs mounts). Then the machine was powercycled and
went back to 2.6.11.11
So I very much doubt that that single attempted 2.6.17.7 boot caused
any damage to this XFS filesystem.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2006-08-10 23:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 8:22 Jesper Juhl
2006-08-04 10:05 ` Nathan Scott
2006-08-04 10:43 ` Jesper Juhl
2006-08-06 3:07 ` Tony.Ho
2006-08-06 4:05 ` Tony.Ho
2006-08-07 4:34 ` Nathan Scott
[not found] ` <3aa654a40608072039r2b5c5a19hbd3e68e4fee40869@mail.gmail.com>
2006-08-08 3:44 ` Nathan Scott
[not found] ` <9a8748490608080137k596a6290r3567096668449a64@mail.gmail.com>
2006-08-08 8:54 ` Nathan Scott
[not found] ` <9a8748490608100431m244207b1v9c9c5087233fcf3a@mail.gmail.com>
2006-08-10 12:25 ` Jesper Juhl
2006-08-10 22:35 ` Nathan Scott
[not found] ` <9a8748490608101544n29f863e7o7584ac64f1d4c210@mail.gmail.com>
2006-08-10 22:52 ` Jesper Juhl
2006-08-11 8:33 ` Jesper Juhl
2006-08-11 10:25 ` Jesper Juhl
2006-08-14 2:00 ` Nathan Scott
2006-08-14 7:49 ` Jesper Juhl
2006-08-15 9:03 ` Nathan Scott
2006-08-15 11:42 ` Jesper Juhl
2006-08-16 1:26 ` Nathan Scott
2006-08-17 21:23 ` Jesper Juhl
2006-08-15 14:37 ` Chris Wedgwood
2006-08-15 14:47 ` Jan Engelhardt
2006-08-16 12:38 ` Paul Slootman
2006-08-16 22:47 ` Nathan Scott
2006-08-17 9:01 ` Paul Slootman
2006-08-23 8:42 ` Paul Slootman
2006-08-24 6:55 ` Nathan Scott
2006-08-24 9:07 ` Paul Slootman
2006-08-10 23:01 ` Jesper Juhl [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=9a8748490608101601t18ea4a30xa467b44feeeb6b5@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=avuton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@idccenter.cn \
--cc=nathans@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
all inboxes | Powered by JetHome®