xfs
[Top] [All Lists]

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

To: markgw@xxxxxxx
Subject: Re: [REVIEW] Don't make lazy counters default for mkfs
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 29 Feb 2008 17:56:04 -0600
Cc: Russell Cattelan <cattelan@xxxxxxxxxxx>, nscott@xxxxxxxxxx, Barry Naujok <bnaujok@xxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <47C8997A.9030804@sgi.com>
References: <op.t67mtawg3jf8g2@pc-bnaujok.melbourne.sgi.com> <1204166101.13569.102.camel@edge.scott.net.au> <47C87775.2010007@thebarn.com> <47C89137.3070805@sandeen.net> <47C89303.7070902@thebarn.com> <47C8997A.9030804@sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
Mark Goodwin wrote:
> 
> Russell Cattelan wrote:
>> Eric Sandeen wrote:
>>> Russell Cattelan wrote:
>>>
>>>
>>>
>>>>> Hmm, that still seems pretty soon to me.  I'd have thought you'd at
>>>>> least want to wait until most of the distributions (esp. SUSE for you
>>>>> guys) have released versions that have kernels sufficiently recent
>>>>> that the default mkfs will work.  Otherwise this will be a recurring
>>>>> problem.
>>>>>
>>>> I don't suppose there is an easy way to query xfs and find out if it
>>>> can support
>>>> the lazy SB option?
>>> I thought about that; xfs *could* stick someting in /proc/fs/xfs with
>>> supported features or somesuch.
> 
> how about /proc/fs/xfs/features
> .. any format suggestions?

maybe just 2 values, with the actual supported features (& features2)
values anded together?  Easy enough to parse in the code.

i.e.

# cat /proc/fs/xfs/features
0xffffffff
0x00000001


?

-Eric


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