From: Lachlan McIlroy <lmcilroy@redhat.com>
To: Eddy Zhao <eddy.y.zhao@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM
Date: Mon, 27 Jul 2009 01:17:32 -0400 (EDT) [thread overview]
Message-ID: <1938435153.1010831248671852499.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <362522677.1010811248671789619.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
----- "Eddy Zhao" <eddy.y.zhao@gmail.com> wrote:
> >
> > 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 :(
We all start somewhere!
>
> >
> > 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?
Easy? Not exactly. Diff'ing 2.6.10 version of fs/xfs/xfs_log_recover.c
with mainline shows over 300 differences. If you really want to be able
to replay the log on a different system it really has to be running the
same version of XFS for there to be any chance of it working properly.
It should also be the same architecture too - is it possible you have a
32 bit kernel on the 2.6.10 system and a 64 bit kernel on the 2.6.28
system? If so then this fix might help
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6d192a9b82212abf1e0e89da6e3a952afba7e4d6
I think it went into 2.6.18.
>
> Thanks
> Eddy
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2009-07-27 5:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <362522677.1010811248671789619.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-07-27 5:17 ` Lachlan McIlroy [this message]
2009-07-28 12:50 ` BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM Eddy Zhao
2009-07-28 14:21 ` Eric Sandeen
2009-07-28 14:59 ` Eddy Zhao
2009-07-28 16:01 ` Eric Sandeen
2009-07-29 12:12 ` Eddy Zhao
2009-07-29 13:03 ` Eddy Zhao
2009-07-29 13:11 ` Eddy Zhao
2009-07-29 13:45 ` Eddy Zhao
2009-07-29 15:14 ` Eric Sandeen
2009-07-30 1:25 ` Eddy Zhao
[not found] <1983390176.948321248423442558.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-07-24 8:22 ` Lachlan McIlroy
2009-07-24 11:04 ` Eddy Zhao
2009-07-24 13:42 ` Eric Sandeen
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=1938435153.1010831248671852499.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
--to=lmcilroy@redhat.com \
--cc=eddy.y.zhao@gmail.com \
--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