xfs
[Top] [All Lists]

Re: [REVIEW] Don't make lazy counters default for mkfs

To: Russell Cattelan <cattelan@xxxxxxxxxxx>
Subject: Re: [REVIEW] Don't make lazy counters default for mkfs
From: Nathan Scott <nscott@xxxxxxxxxx>
Date: Mon, 03 Mar 2008 10:34:55 +1100
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, Barry Naujok <bnaujok@xxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <47C89303.7070902@xxxxxxxxxxx>
Organization: Aconex
References: <op.t67mtawg3jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1204166101.13569.102.camel@xxxxxxxxxxxxxxxxx> <47C87775.2010007@xxxxxxxxxxx> <47C89137.3070805@xxxxxxxxxxx> <47C89303.7070902@xxxxxxxxxxx>
Reply-to: nscott@xxxxxxxxxx
Sender: xfs-bounce@xxxxxxxxxxx
On Fri, 2008-02-29 at 17:19 -0600, Russell Cattelan wrote:
> 
> > I thought about that; xfs *could* stick someting in /proc/fs/xfs
> with
> > supported features or somesuch.
> >
> > But, the kernel you mkfs under isn't necessarily the one you're
> going to
> > need to fall back to tomorrow, though...
> >
> >   
> True but at least it could make a bit of a intelligent decision.
> and maybe a warning for a while about potentially incompatible flags. 

Might also be a good idea to require -f to force a mkfs of a filesystem
which the kernel doesn't support.

Would be good to get blocksize > pagesize into this scheme too btw, and
unfortunately that one isn't a superblock flag) - so this scheme might
need to go beyond those flags, if anyone decides to implement it.

cheers.

-- 
Nathan


<Prev in Thread] Current Thread [Next in Thread>