On Wed, Feb 02, 2005 at 02:31:55PM -0800, Douglass Judd wrote:
> Another thing I forgot to mention is
> that the log was corrupt. xfs_logprint produces:
>
> xfs_logprint:
> data device: 0x801
> log device: 0x801 daddr: 1708906272 length: 262144
>
> Header 0x4 wanted 0xfeedbabe
> **********************************************************************
> * ERROR: header cycle=4 block=88181 *
> **********************************************************************
> Bad log record header
>
FYI
It's best to use the -t option to xfs_logprint.
The -t option will ensure it starts printing from the tail of
the log to the head of the log i.e. the items which get processed
on recovery. Also, it prints the higher level transactions.
If you don't use -t then you print out the lower level log-ops
and it starts printing at the start of the log, which may in fact
be midway thru a log record created when the log was last wrapped -
and thus one is likely not to start with a header (one could use -s
to start from somehere else).
--Tim
|