From: Mark Goodwin <markgw@sgi.com>
To: Russell Cattelan <cattelan@thebarn.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
nscott@aconex.com, Barry Naujok <bnaujok@sgi.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [REVIEW] Don't make lazy counters default for mkfs
Date: Sat, 01 Mar 2008 10:47:06 +1100 [thread overview]
Message-ID: <47C8997A.9030804@sgi.com> (raw)
In-Reply-To: <47C89303.7070902@thebarn.com>
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?
>> But, the kernel you mkfs under isn't necessarily the one you're going to
>> need to fall back to tomorrow, though...
nor the one you just installed but haven't rebooted into yet
> True but at least it could make a bit of a intelligent decision.
> and maybe a warning for a while about potentially incompatible flags.
yes agree
Cheers
--
Mark Goodwin markgw@sgi.com
Engineering Manager for XFS and PCP Phone: +61-3-99631937
SGI Australian Software Group Cell: +61-4-18969583
-------------------------------------------------------------
next prev parent reply other threads:[~2008-02-29 23:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 1:09 [REVIEW] Don't make lazy counters default for mkfs Barry Naujok
2008-02-28 2:35 ` Nathan Scott
2008-02-29 21:21 ` Russell Cattelan
2008-02-29 23:11 ` Eric Sandeen
2008-02-29 23:19 ` Russell Cattelan
2008-02-29 23:47 ` Mark Goodwin [this message]
2008-02-29 23:56 ` Eric Sandeen
2008-03-01 0:11 ` Eric Sandeen
2008-03-02 23:59 ` Barry Naujok
2008-03-01 0:02 ` Josef 'Jeff' Sipek
2008-03-02 23:34 ` Nathan Scott
2008-03-03 0:16 ` Timothy Shimmin
2008-03-03 0:30 ` Mark Goodwin
2008-03-03 1:15 ` Josef 'Jeff' Sipek
2008-03-03 3:56 ` Eric Sandeen
2008-03-03 4:14 ` Josef 'Jeff' Sipek
2008-03-03 4:19 ` Eric Sandeen
2008-03-03 4:47 ` Niv Sardi
2008-03-03 0:18 ` Donald Douwsma
2008-03-03 0:24 ` Nathan Scott
2008-03-02 10:26 ` Andi Kleen
2008-03-02 10:41 ` Josef 'Jeff' Sipek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47C8997A.9030804@sgi.com \
--to=markgw@sgi.com \
--cc=bnaujok@sgi.com \
--cc=cattelan@thebarn.com \
--cc=nscott@aconex.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.