xfs
[Top] [All Lists]

Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM

To: Lachlan McIlroy <lmcilroy@xxxxxxxxxx>
Subject: Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM
From: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Fri, 24 Jul 2009 19:04:05 +0800
Cc: xfs@xxxxxxxxxxx, felixb@xxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=qzNWXFtMX0hEt2A+UKnd5+WvyR45+I0408PPj3BA5O4=; b=Xv9ZsI+rXQpIPOrwMR/00IE8YB8fk0Q0VfdkMp1RYTw1CLBhqjXnbG95B6I1jCx0EI dGlxi2JihzPi8ej9NGvt3fvPm1+cvcOFPzUJSmxzat4aY+pd29xTQ43ejuEk+zKJJIDj DLWeCoTqmzG2cZkpVJzEpz6NSGRTUqZuK6SUE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LeYsBQRDpbt9laepo6d/YqzZl/sXY83rVGAcFCK74/nbjPE8anJzKInO1CpUTKM/Ip seql1O5D7bSQU71xTsMoi1ezzi2MY+pOiX+C8Joe108LcF4duqM9aaGYxgEJNBqlPVhq 6IzWhLlbWEOjQtK9a5WL8f7OIzJCchwPCKz7c=
In-reply-to: <1301281514.948741248423723710.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <1983390176.948321248423442558.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1301281514.948741248423723710.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>

>
> I don't recommend you pull the usb disk out while the filesystem is still
> mounted (if you can avoid it).
>

Doing that to emulate power loss scenario our device might experience.

>
> I would start by looking through the change history for fs/xfs/xfs_log_recover.c
> and paying particular attention to anything to do with inode transactions. 
>

Not quite familiar with XFS code :(

>
> Or try some intermediate kernels and see if you can narrow the fix down to a set of
> changes.
>

I'll try to bisect (It will take some time...)

>
> # mount /dev/sda1 /mnt/
> UDF-fs: No VRS found
> XFS mounting filesystem sda1
> Starting XFS recovery on filesystem: sda1 (dev: sda1)
> Filesystem "sda1": xfs_inode_recover: Bad inode magic number, dino ptr
> = 0xc8266700, dino bp = 0xc8281b40, ino = 0

Because XFS log is OK to 2.6.28 system, which means the log is correct in itself.
Would it be easy for you to debug the problem by compare 2.6.10 log recovery code fail point and the corresponding 2.6.28 log record?

Thanks
Eddy

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