From: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
To: nscott@aconex.com
Cc: xfs@oss.sgi.com
Subject: Re: changing xfs file system tunnings(sunit,swidth) after mkfs.xfs
Date: Tue, 27 Mar 2007 09:04:33 +0200 [thread overview]
Message-ID: <5d96567b0703270004j72d89618xe27bbf3d5e44eea1@mail.gmail.com> (raw)
In-Reply-To: <1174947030.5051.586.camel@edge>
ahha...
but did you ever tried to set an sunit value bigger than the one
set during the mkfs.xfs ?
On 3/27/07, Nathan Scott <nscott@aconex.com> wrote:
> On Mon, 2007-03-26 at 22:25 +0200, Raz Ben-Jehuda(caro) wrote:
> > I want to change the sunit,swidth of a file system which
> > was already created with a different tunnings, or at least
> > mount it with a different values.
> > Is it possible ?
>
> >From the XFS section in mount(8) ...
>
> sunit=value and swidth=value
> Used to specify the stripe unit and width for a RAID device or a
> stripe volume. value must be specified in 512-byte block units.
> If this option is not specified and the filesystem was made on a
> stripe volume or the stripe width or unit were specified for the
> RAID device at mkfs time, then the mount system call will
> restore the value from the superblock. For filesystems that are
> made directly on RAID devices, these options can be used to
> override the information in the superblock if the underlying
> disk layout changes after the filesystem has been created. The
> swidth option is required if the sunit option has been speci‐
> fied, and must be a multiple of the sunit value.
>
>
> cheers.
>
> --
> Nathan
>
>
--
Raz
next prev parent reply other threads:[~2007-03-27 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 20:25 changing xfs file system tunnings(sunit,swidth) after mkfs.xfs Raz Ben-Jehuda(caro)
2007-03-26 22:10 ` Nathan Scott
2007-03-27 7:04 ` Raz Ben-Jehuda(caro) [this message]
2007-03-27 9:48 ` Shailendra Tripathi
2007-03-27 12:20 ` David Chinner
2007-03-27 23:50 ` Nathan Scott
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=5d96567b0703270004j72d89618xe27bbf3d5e44eea1@mail.gmail.com \
--to=raziebe@gmail.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