public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: Jeff Breidenbach <jeff@jab.org>
Cc: Hannes Dorbath <light@theendofthetunnel.de>, xfs@oss.sgi.com
Subject: Re: tuning, many small files, small blocksize
Date: Tue, 19 Feb 2008 11:48:53 +1100	[thread overview]
Message-ID: <47BA2775.1060109@sgi.com> (raw)
In-Reply-To: <e03b90ae0802160224v600bd94exb2a1007ca7af7b65@mail.gmail.com>

Jeff Breidenbach wrote:
> the kernel before April is painful but I'll do it if important. Presumably
> there's no simple way to migrate a non-lazy xfs filesytem to a lazy one.
> 

Dave would know that answer.

But on IRIX we used xfs_chver...
>      Using the +c option one can enable a filesystem to use lazy counters.
>      Note that you must run xfs_repair(1M) after setting this option to build
>      the internal state that is required to support this functionality.
> 
>      Using the -c option one can disable lazy counters if it is enabled. Note
>      that you must run xfs_repair(1M) after clearing this option to ensure
>      that the internal state of the filesystem is consistent.

On Linux we have xfs_admin (wrapper around db) and the "version" command in xfs_db.
However, it looks like "version" only does: extflg, v2-logs, attr1, attr2,
but not lazy sb counters.

--Tim

  parent reply	other threads:[~2008-02-19  0:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16  5:01 tuning, many small files, small blocksize Jeff Breidenbach
2008-02-16  9:28 ` Hannes Dorbath
2008-02-16 10:24   ` Jeff Breidenbach
2008-02-16 20:30     ` Jeff Breidenbach
2008-02-19  0:48     ` Timothy Shimmin [this message]
2008-02-16 12:23 ` pg_xfs2
2008-02-18 22:53 ` David Chinner
2008-02-18 23:12 ` Linda Walsh
2008-02-18 23:51   ` David Chinner
2008-02-19  1:03     ` Linda Walsh
2008-02-19  2:49       ` David Chinner
2008-02-19  4:58         ` Jeff Breidenbach
2008-02-19  8:27           ` Peter Grandi
2008-02-19 11:44             ` Hannes Dorbath
2008-02-19 21:24               ` Peter Grandi

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=47BA2775.1060109@sgi.com \
    --to=tes@sgi.com \
    --cc=jeff@jab.org \
    --cc=light@theendofthetunnel.de \
    --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