public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Cattelan <cattelan@thebarn.com>
To: nscott@aconex.com
Cc: 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: Fri, 29 Feb 2008 15:21:57 -0600	[thread overview]
Message-ID: <47C87775.2010007@thebarn.com> (raw)
In-Reply-To: <1204166101.13569.102.camel@edge.scott.net.au>

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

Nathan Scott wrote:
> On Thu, 2008-02-28 at 12:09 +1100, Barry Naujok wrote:
>   
>> Lazy superblock counters was released into mainline in 2.6.23-rc1.
>> Some  
>> distros are still running an older kernel (2.6.22 for example) and
>> with  
>>     
>
> (many distros?  RHEL5 and SLES10 wont have such recent kernels yet,
> right?)
>
>   
>> the latest xfsprogs, cannot mount a freshly made filesystem with
>> default  
>> options.
>>
>> This patch make lazy counters default back to off now.
>>     
>
> Looks good, thanks.
>
>   
>> Users who have a more recent kernel can easily enable them with mkfs
>> or  
>> xfs_admin -c1 (in a patch posted out a few days ago which will be in
>> the  
>> same xfsprogs release as this patch).
>>
>> Lazy counters will default to on again in xfsprogs 2.10.0 (when CI
>> support  
>> is released). This should give enough time for distro kernels to catch
>> up.
>>     
>
> 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?

> cheers.
>
>   


[-- Attachment #2: cattelan.vcf --]
[-- Type: text/x-vcard, Size: 131 bytes --]

begin:vcard
fn:Russell Cattelan
n:Cattelan;Russell
email;internet:cattelan@thebarn.com
x-mozilla-html:FALSE
version:2.1
end:vcard


  reply	other threads:[~2008-02-29 21:21 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 [this message]
2008-02-29 23:11     ` Eric Sandeen
2008-02-29 23:19       ` Russell Cattelan
2008-02-29 23:47         ` Mark Goodwin
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=47C87775.2010007@thebarn.com \
    --to=cattelan@thebarn.com \
    --cc=bnaujok@sgi.com \
    --cc=nscott@aconex.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox