xfs
[Top] [All Lists]

Re: Unable to handle kernel NULL pointer dereference at virtual address

To: Timothy Shimmin <tes@xxxxxxx>
Subject: Re: Unable to handle kernel NULL pointer dereference at virtual address 00000000
From: Denis Nikiforov <denis@xxxxxxxx>
Date: Wed, 21 Jun 2006 09:17:44 +0600
Cc: xfs@xxxxxxxxxxx
In-reply-to: <200606211108.25096.tes@sgi.com> (Timothy Shimmin's message of "Wed, 21 Jun 2006 11:08:24 +1000")
References: <87hd2fsvsl.fsf@arietis.arietis> <200606211108.25096.tes@sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)
(transmit-message (Hello 'Timothy)
(You-wrote :on "Wed, 21 Jun 2006 11:08:24 +1000")
(Say '(

 TS> Hi Denis,
 TS> On Wednesday 21 June 2006 1:15 am, Denis Nikiforov wrote:
>>
>> I'd upgraded my computer from Celeron P4 to Athlon 64. And xfs partition
>> couldn't be mounted now ;( How can I fix it?
>>
>> .............
>>
>> | XFS mounting filesystem hdb3
>> | Starting XFS recovery on filesystem: hdb3 (logdev: internal)
>> | Unable to handle kernel NULL pointer dereference at virtual address
>> ...............
>> |  [<f8c5290e>] xfs_buf_offset+0x35/0x3a [xfs]
>> |  [<f8c3eb19>] xlog_recover_do_inode_trans+0x14a/0x718 [xfs]

 TS> Your problem is due to a bug in xfs.
 TS> A kernel from 2006/05/24 onwards will be able to support this filesystem.
 TS> The problem is that the ondisk format for a few log items in the ondisk 
log is 
 TS> different on 32 bits versus 64 bit systems. With the newer XFS it can 
decode 
 TS> both forms.
 TS> What can you do?
 TS> You can either mount and unmount the FS on a 32 bit os so that the log is 
 TS> clean and no recovery is needed.
 TS> Or you can get a new version of XFS.
 TS> (In the future, xfs_repair will probably be able to replay the log but not 
 TS> yet).

2.6.16-14 is the latest kernel in Debian. And I guess it's old
enough. Thanks, I'll wait for a new kernel :)

-- 
))) => t
(WBR '(Denis Nikiforov))


<Prev in Thread] Current Thread [Next in Thread>