public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Avuton Olrich <avuton@gmail.com>, "Tony. Ho" <linux@idccenter.cn>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078
Date: Mon, 14 Aug 2006 12:00:32 +1000	[thread overview]
Message-ID: <20060814120032.E2698880@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <9a8748490608110325k25c340e2yac925eb226d1fe4f@mail.gmail.com>; from jesper.juhl@gmail.com on Fri, Aug 11, 2006 at 12:25:03PM +0200

On Fri, Aug 11, 2006 at 12:25:03PM +0200, Jesper Juhl wrote:
> I didn't capture all of the xfs_repair output, but I did get this :
> ...
> Phase 4 - check for duplicate blocks...
>         - setting up duplicate extent list...
>         - clear lost+found (if it exists) ...
>         - clearing existing "lost+found" inode
>         - deleting existing "lost+found" entry
>         - check for inodes claiming duplicate blocks...
>         - agno = 0
>         - agno = 1
>         - agno = 2
>         - agno = 3
>         - agno = 4
>         - agno = 5
>         - agno = 6
> LEAFN node level is 1 inode 412035424 bno = 8388608

Ooh.  Can you describe this test case you're using?  Something with
a bunch of renames in it, obviously, but I'd also like to be able to
reproduce locally with the exact data set (file names in particular),
if at all possible.

thanks!

-- 
Nathan

       reply	other threads:[~2006-08-14  2:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3aa654a40608072039r2b5c5a19hbd3e68e4fee40869@mail.gmail.com>
     [not found] ` <20060808134438.E2526901@wobbly.melbourne.sgi.com>
     [not found]   ` <9a8748490608080137k596a6290r3567096668449a64@mail.gmail.com>
     [not found]     ` <20060808185405.B2528231@wobbly.melbourne.sgi.com>
     [not found]       ` <9a8748490608100431m244207b1v9c9c5087233fcf3a@mail.gmail.com>
     [not found]         ` <20060811083546.B2596458@wobbly.melbourne.sgi.com>
     [not found]           ` <9a8748490608101544n29f863e7o7584ac64f1d4c210@mail.gmail.com>
     [not found]             ` <9a8748490608101552w12822fa6m415a5fb5537c744d@mail.gmail.com>
     [not found]               ` <9a8748490608110133v5f973cf6w1af340f59bb229ec@mail.gmail.com>
     [not found]                 ` <9a8748490608110325k25c340e2yac925eb226d1fe4f@mail.gmail.com>
2006-08-14  2:00                   ` Nathan Scott [this message]
2006-08-14  7:49                     ` 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078 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
     [not found] <9a8748490608040122l69ff139dtaae27e8981022dae@mail.gmail.com>
2006-08-04 10:05 ` Nathan Scott
2006-08-04 10:43   ` Jesper Juhl

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=20060814120032.E2698880@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=avuton@gmail.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@idccenter.cn \
    --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