From: Bill Davidsen <davidsen@tmr.com>
To: Marko Berg <marko.berg@iki.fi>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 5: weird size results after Grow
Date: Sun, 14 Oct 2007 01:05:43 -0400 [thread overview]
Message-ID: <4711A3A7.8060900@tmr.com> (raw)
In-Reply-To: <4710F021.30508@iki.fi>
Marko Berg wrote:
> Bill Davidsen wrote:
>> Marko Berg wrote:
>>> I added a fourth drive to a RAID 5 array. After some complications
>>> related to adding a new HD controller at the same time, and thus
>>> changing some device names, I re-created the array and got it
>>> working (in the sense "nothing degraded"). But size results are
>>> weird. Each component partition is 320 G, does anyone have an
>>> explanation for the "Used Dev Size" field value below? The 960 G
>>> total size is as it should be, but in practice Linux reports the
>>> array only having 625,019,608 blocks.
>>
>> I don't see that number below, what command reported this?
>
> For instance df:
>
> $ df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/md0 625019608 358223356 235539408 61% /usr/pub
>
>>> How can this be, even though the array should be clean with 4 active
>>> devices?
df reports the size of the filesystem, mdadm reports the size of the array.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2007-10-14 5:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 8:11 RAID 5: weird size results after Grow Marko Berg
2007-10-13 13:08 ` Bill Davidsen
2007-10-13 16:19 ` Marko Berg
2007-10-13 17:17 ` Corey Hickey
2007-10-13 17:32 ` Marko Berg
2007-10-13 17:42 ` Justin Piszcz
2007-10-13 17:59 ` Corey Hickey
2007-10-13 17:41 ` Justin Piszcz
2007-10-14 5:05 ` Bill Davidsen [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=4711A3A7.8060900@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=marko.berg@iki.fi \
/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).