> Hey, just wanted to congratulate you all. I just got CVS XFS running on
> PowerPC (slightly modified kernel 2.4.5pre3). Most of my problems came from
> trying to apply a 2.4.4 patch to 2.4.5pre.
>
> I was also very impressed with the state of the documentation and the
> accompanying xfs utilities. I couldn't have asked for anything more; just
> compile the package and install the rpm.
>
> Did some quick banging on it and all looks well. One question though: I got
> this output on my new xfs partition (after overfilling it, deleting
> everything, and unmounting it):
>
> $ /usr/sbin/xfs_logprint /dev/hda9
> xfs_logprint:
> data device: 0x309
> log device: 0x309 daddr: 3072032 length: 9600
>
> Header 0x2 wanted 0xfeedbabe
> **********************************************************************
> * ERROR: header cycle=2 block=2646 *
> **********************************************************************
> Bad log record header
>
> I have no idea what this means. xfs_check doesn't find any problems, and I
> don't know this stuff well enough to investigate more (just experimenting).
>
> -Hollis
Try running xfs_logprint -t on the filesystem, xfs_logprint on its own
is not quite smart enough to work out which parts of the log have been
written to as part of the last mount, and which have not. After a clean
unmount you should get this type of output:
[root@laptop lord]# xfs_logprint -t /dev/hda8
xfs_logprint:
data device: 0x308
log device: 0x308 daddr: 7654976 length: 12000
log tail: 11364 head: 11364 state: <CLEAN>
Steve
|