From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: 2.6.38.4: xfs speed problem?
Date: Mon, 9 May 2011 09:53:34 +0200 [thread overview]
Message-ID: <201105090953.35090@zmi.at> (raw)
In-Reply-To: <4DC6D067.1080208@hardwarefreak.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 847 bytes --]
[removed some recipients]
On Sonntag, 8. Mai 2011 Stan Hoeppner wrote:
> remake the fs on the above device with 'sw=16' or remount with
> appropriate sunit and swidth values?
A remount wouldn't help the existing metadata layout. Would it be
sufficient to remount with sw=16 and then create a top-level dir,
wherein you recreate all existing dirs new, then hard-link each file and
remove the old directory structure?
Or would it be needed to copy the files too to get advantage of the new
sw?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
//
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-05-09 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 16:09 2.6.38.4: xfs speed problem? Justin Piszcz
2011-05-07 16:09 ` Justin Piszcz
2011-05-08 0:33 ` Dave Chinner
2011-05-08 0:33 ` Dave Chinner
2011-05-08 17:18 ` Stan Hoeppner
2011-05-08 17:18 ` Stan Hoeppner
2011-05-09 7:53 ` Michael Monnerie [this message]
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=201105090953.35090@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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.