Re: Question: Does XFS journal data or only metadata?

[Steve Lord <lord@xxxxxxx>]

Anders Saaby wrote:
> On Thursday 03 February 2005 17:24, Anders Saaby wrote:
>
> > On Thursday 03 February 2005 17:16, Anders Saaby wrote:
> >
> > > On Thursday 03 February 2005 16:15, Steve Lord wrote:
> > >
> > > > The bit about setting the values twice should not be necessary, I
> > > > think that endian bug should be ancient history.
> > > >
> > > > You may need to run xfs_repair before mount will work nowadays too,
> > > > try it and see.
> > > >
> > > > Steve
> > >
> > > Yup - This is fixed:
> > >
> > > xfs_db> write logblocks 8750
> > > logblocks = 8750
> > >
> > > Actually the move works, I am able to move the log from internal to
> > > external and back again. - And able to mount the filesystem in both
> > > cituations, but xfs_repair doesen't agree. When running xfs_repair on the
> > > filesystem after I have moved the log to an external device the following
> > > error occurs:
> > >
> > > <XFS_REPAIR ERROR>
> > > st3:~# xfs_repair -L -l /dev/sda4 /dev/sdc1
> > > Phase 1 - find and verify superblock...
> > >
> > > fatal error -- could not read superblock
> > > </XFS_REPAIR ERROR>
> >
> > Don't know if this is relevant, but this strace looks interesting:
>
>
> OK - After looking at the strace I checked the _other_ superblocks. As I only 
> altered SB0, the other superblocks SB1+ still contains the old logstart 
> value.
>
> Wrote "logfile 0" to SB 0 - SB 15, and it all works! :)
>
> It this the way to do it, or am I missing something obvious?

That is the way to do it, the tools are more picky than they used
to be about this. Which is why getting the facility built into
the tools would help a lot - since it would do the fixup of all
superblocks itself.

Steve