xfs
[Top] [All Lists]

Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM

To: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Subject: Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 29 Jul 2009 10:14:51 -0500
Cc: Lachlan McIlroy <lmcilroy@xxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <b094161c0907290512q26efb74jc31f72ff7971210b@xxxxxxxxxxxxxx>
References: <362522677.1010811248671789619.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1938435153.1010831248671852499.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <b094161c0907280550y58cde45fja97b2c413c92a8d4@xxxxxxxxxxxxxx> <4A6F0978.4070709@xxxxxxxxxxx> <b094161c0907280759w6c525201vd4a17e22a8c1d582@xxxxxxxxxxxxxx> <4A6F20D0.4050303@xxxxxxxxxxx> <b094161c0907290512q26efb74jc31f72ff7971210b@xxxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
Eddy Zhao wrote:

...

> During fixing the problem, I find it is difficult to change the code to
> commit packed log item (restricted by xfs_log_iovec_t mechanism). If we
> could somehow change this piece of code to use packed structure. The
> endianess problem could be solved by add an byte-swap option to
> xfs_repair (like e2fsck "-s"). Then we solve the
> xfs-log-cant-migrate-between-archs problem.

Well, to be honest, the restriction of a clean log when migrating an xfs
filesystem between systems of differing endianness was design decision.
 And xfs userspace can't replay any log, native endian or not.  If it
could, then perhaps doing the swapping in userspace would be a migration
option.  If you're signing up to make xfs_repair replay logs, I'm sure
we'd welcome the patch.  :)

-Eric

> Thanks
> Eddy

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