http://bugzilla.kernel.org/show_bug.cgi?id=5821
------- Additional Comments From sandeen-xfs@xxxxxxxxxxx 2006-09-21 07:40
-------
Hm, well, it still shouldn't oops, it should recognize an invalid log format if
one is found.
However, there were some bugs in this area which have been fixed. See
http://oss.sgi.com/archives/xfs/2006-05/msg00051.html
I can't remember for sure if this led to an oops (Tim?) (feel free to search the
archives)
Can the original reporter try with a recent kernel? 2.6.15 predates that fix.
Also Tim says this:
> Log replay is certainly not endian independent but it can handle
> different word-size machines nowadays (didn't in the past).
> So you can go between i386 and x86_64 for example, with a dirty log.
> The log formats will be different between the two for some items
> but in recovery with a newer kernel we do conversion on the fly.
> It certainly does sound like that is the issue here, Chris.
> The back trace is just like a typical different log format problem.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|