On Mon, May 11, 2015 at 06:50:00PM -0500, Eric Sandeen wrote:
> On 5/11/15 4:49 PM, Dave Chinner wrote:
> > On Mon, May 11, 2015 at 11:52:52AM -0500, Eric Sandeen wrote:
> >> On 5/11/15 11:14 AM, Brian Foster wrote:
> >>> On Fri, May 08, 2015 at 03:48:16PM -0500, Eric Sandeen wrote:
> >>> I suppose I could be convinced otherwise if there's context I'm missing,
> >>> but otherwise this seems a bit confusing to me...
> >>> Brian
> >> Yeah, I'm sympathetic to that argument. I can look into using sb_meta_uuid
> >> for the log too, if the incompat flag is set.
> > The log uuid is user facing, like the superblock uuid. i.e. there
> > are tools that identify external log devices by checking that the
> > uuid in the log matches the user facing uuid in the superblock.
> > Hence the log uuid needs to use the uuid that is reported to
> > userspace.
> None that are external to xfsprogs, I think, are there? (1) - but still.
> I'm happy to leave it as it is ... I don't think it really matters either way.
> (1) at one point I wanted to teach blkid to find an external log by UUID,
> but there is no "log superblock" so I gave up on that idea.
Well, we don't know, really, do we? It's best to play it safe and
keep it the same as the user visible filesytem uuid, as that is
what is currently expected by anything poking at block dev UUIDs...