All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Doug Hunley <doug@hunley.homeip.net>, linux-ext4@vger.kernel.org
Subject: Re: changing stride and stripe_width post-fs-creation?
Date: Tue, 20 Oct 2009 16:16:47 -0500	[thread overview]
Message-ID: <4ADE28BF.6000605@redhat.com> (raw)
In-Reply-To: <EA1A7036-FD43-4996-9665-E04FD32A449F@sun.com>

Andreas Dilger wrote:
> On 20-Oct-09, at 11:32, Doug Hunley wrote:
>> Is it safe to use tune2fs to alter stride and stripe_width on an ext4
>> fs once it has been created? Any caveats I should know about? Thanks
> 
> 
> The stride is mostly used at fs creation time, but there is no problem
> with changing it.  The stripe_width is used by the allocator to align
> file allocations with the RAID layout.
> 
> One question for Eric is whether the new libdisk patches he made will set
> the stripe_width to something ridiculous like 512 or 4096 bytes, or if it
> just leaves that field unset in that case.  I suspect it would be bad for
> mballoc to see the stripe_width be such a small value.

well... yes, it does set it to whatever is reported:

+       min_io = blkid_topology_get_minimum_io_size(tp);
+       opt_io = blkid_topology_get_optimal_io_size(tp);
+       blocksize = EXT2_BLOCK_SIZE(fs_param);
+
+       fs_param->s_raid_stride = min_io / blocksize;
+       fs_param->s_raid_stripe_width = opt_io / blocksize;


if mballoc can't handle certain values then maybe the kernel code should 
be changed to ignore it?  Small values could just as easily come from a 
user too ...

-Eric

  reply	other threads:[~2009-10-20 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 17:32 changing stride and stripe_width post-fs-creation? Doug Hunley
2009-10-20 21:08 ` Andreas Dilger
2009-10-20 21:16   ` Eric Sandeen [this message]
2009-10-20 21:30     ` Andreas Dilger

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=4ADE28BF.6000605@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=doug@hunley.homeip.net \
    --cc=linux-ext4@vger.kernel.org \
    /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.