linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-raid@vger.kernel.org
Subject: Re: very degraded RAID5, or increasing capacity by adding discs
Date: Tue, 23 Oct 2007 18:41:15 -0400	[thread overview]
Message-ID: <471E788B.7000001@tmr.com> (raw)
In-Reply-To: <20071022090300.GA22588@apartia.fr>

Louis-David Mitterrand wrote:
> On Tue, Oct 09, 2007 at 01:48:50PM +0400, Michael Tokarev wrote:
>   
>> There still is - at least for ext[23].  Even offline resizers
>> can't do resizes from any to any size, extfs developers recommend
>> to recreate filesystem anyway if size changes significantly.
>> I'm too lazy to find a reference now, it has been mentioned here
>> on linux-raid at least this year.  It's sorta like fat (yea, that
>> ms-dog filesystem) - when you resize it from, say, 501Mb to 999Mb,
>> everything is ok, but if you want to go from 501Mb to 1Gb+1, you
>> have to recreate almost all data structures because sizes of
>> all internal fields changes - and here it's much safer to just
>> re-create it from scratch than trying to modify it in place.
>> Sure it's much better for extfs, but the point is still the same.
>>     
>
> I'll just mention that I once resized a multi-Tera ext3 filesystem and 
> it took 8hours +, a comparable XFS online resize lasted all of 10 
> seconds! 

Because of the different way these file systems do things, there is no 
comparable resize, at least in terms of work to be done. For many 
systems R/W operations are more common than resize, so the F/S type is 
selected to optimize that. ;-)

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  reply	other threads:[~2007-10-23 22:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 19:13 very degraded RAID5, or increasing capacity by adding discs Janek Kozicki
2007-10-08 19:17 ` Justin Piszcz
2007-10-08 19:26 ` Richard Scobie
2007-10-08 20:08   ` Guy Watkins
2007-10-08 22:25   ` Janek Kozicki
2007-10-08 22:46     ` Janek Kozicki
2007-10-09  1:53       ` Guy Watkins
2007-10-09  3:32       ` Neil Brown
2007-10-09 14:44         ` Janek Kozicki
2007-10-09 14:56         ` Mr. James W. Laferriere
2007-10-09 21:52           ` Neil Brown
2007-10-08 22:52 ` Michael Tokarev
2007-10-09  3:24   ` Neil Brown
2007-10-09  9:48     ` Michael Tokarev
2007-10-22  9:03       ` Louis-David Mitterrand
2007-10-23 22:41         ` Bill Davidsen [this message]
2007-10-09 14:42   ` Janek Kozicki

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=471E788B.7000001@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).