Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*BUG\s+REPORT\:\s+XFS\s+LOG\s+FORWARD\s+COMPATIBILITY\s+PROBLEM\s*$/: 14 ]

Total 14 documents matching your query.

1. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Lachlan McIlroy <lmcilroy@xxxxxxxxxx>
Date: Fri, 24 Jul 2009 04:22:03 -0400 (EDT)
Hi Eddy, CC'ing this to the xfs list. I don't recommend you pull the usb disk out while the filesystem is still mounted (if you can avoid it). Okay good. Looks like whatever the problem is it has bee
/archives/xfs/2009-07/msg00244.html (13,680 bytes)

2. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Fri, 24 Jul 2009 19:04:05 +0800
Doing that to emulate power loss scenario our device might experience. Not quite familiar with XFS code :( I'll try to bisect (It will take some time...) Because XFS log is OK to 2.6.28 system, whic
/archives/xfs/2009-07/msg00246.html (9,397 bytes)

3. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 24 Jul 2009 08:42:59 -0500
Unless you have write barriers enabled and passing through to the USB device, or write cache turned off on the USB device, this test may well just be corrupting the log to an unreplayable state. Alth
/archives/xfs/2009-07/msg00249.html (8,524 bytes)

4. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Lachlan McIlroy <lmcilroy@xxxxxxxxxx>
Date: Mon, 27 Jul 2009 01:17:32 -0400 (EDT)
We all start somewhere! 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
/archives/xfs/2009-07/msg00273.html (10,083 bytes)

5. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Tue, 28 Jul 2009 20:50:25 +0800
Hello Lachlan: Yes. I'll start from this problem :) The two systems are all 32bit. Enlightened by your suggestion, I find problem lies in the two systems are different architecture. One is arm, on is
/archives/xfs/2009-07/msg00289.html (11,024 bytes)

6. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 28 Jul 2009 09:21:44 -0500
Well, the fact that you have 2 arches would have been highly relevant in your first email. ;) Is this the old abi or the new? Guessing old, based on the alignment issues. Well, packing structures lik
/archives/xfs/2009-07/msg00290.html (12,279 bytes)

7. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Tue, 28 Jul 2009 22:59:49 +0800
Hello Eric: ARM compiler is producing eabi. The problem lies in: "long long" on arm is 8 bytes aligned, on x86 is 4 bytes aligned. So 4 more bytes are padded before xfs_inode_log_format::ilf_ino on a
/archives/xfs/2009-07/msg00291.html (12,005 bytes)

8. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 28 Jul 2009 11:01:20 -0500
A tool that can be very helpful here is "pahole" found in the dwarves package: struct xfs_inode_log_format { __uint16_t ilf_type; /* 0 2 */ __uint16_t ilf_size; /* 2 2 */ __uint32_t ilf_fields; /* 4
/archives/xfs/2009-07/msg00292.html (12,594 bytes)

9. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Wed, 29 Jul 2009 20:12:22 +0800
Hello Eric:   Nice tool. I don't have x86_64 machine at hand. Replay arm eabi log on ia32 machine "seems" success (mount "successfully" returns). Actually I guess that's because 2.6.28 XFS running on
/archives/xfs/2009-07/msg00298.html (11,941 bytes)

10. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Wed, 29 Jul 2009 21:03:45 +0800
  Forget this. I didn't get it right.
/archives/xfs/2009-07/msg00299.html (11,328 bytes)

11. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Wed, 29 Jul 2009 21:11:29 +0800
  Forget this. Nothing on disk will goes wrong even under the misinterpretation.
/archives/xfs/2009-07/msg00300.html (11,339 bytes)

12. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Wed, 29 Jul 2009 21:45:25 +0800
  Forget this. There's no misinterpretation. Should be   "Replay arm eabi log on ia32 machine success (mount successfully returns). 2.6.28 XFS running on ia32 interprets unpacked xfs_inode_log_forma
/archives/xfs/2009-07/msg00302.html (11,838 bytes)

13. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 29 Jul 2009 10:14:51 -0500
... 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 end
/archives/xfs/2009-07/msg00305.html (10,868 bytes)

14. Re: BUG REPORT: XFS LOG FORWARD COMPATIBILITY PROBLEM (score: 1)
Author: Eddy Zhao <eddy.y.zhao@xxxxxxxxx>
Date: Thu, 30 Jul 2009 09:25:00 +0800
  I'll think twice and try.   Thanks for the help! Eric, Lachlan
/archives/xfs/2009-07/msg00310.html (11,076 bytes)


This search system is powered by Namazu