From: Corey Hickey <bugfood-ml@fatooh.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Marko Berg <marko.berg@iki.fi>, linux-raid@vger.kernel.org
Subject: Re: RAID 5: weird size results after Grow
Date: Sat, 13 Oct 2007 10:59:51 -0700 [thread overview]
Message-ID: <47110797.2050009@fatooh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710131342040.32548@p34.internal.lan>
Justin Piszcz wrote:
>
> On Sat, 13 Oct 2007, Marko Berg wrote:
>
>> Corey Hickey wrote:
>>> Marko Berg wrote:
>>>> Bill Davidsen wrote:
>>>>> Marko Berg wrote:
>>>>>> Any suggestions on how to fix this, or what to investigate next, would
>>>>>> be appreciated!
>>>>>>
>>>>> I'm not sure what you're trying to "fix" here, everything you posted
>>>>> looks sane.
>>>> I'm trying to find the missing 300 GB that, as df reports, are not
>>>> available. I ought to have a 900 GB array, consisting of four 300 GB
>>>> devices, while only 600 GB are available. Adding the fourth device didn't
>>>> increase the capacity of the array (visible, at least). E.g. fdisk reports
>>>> the array size to be 900 G, but df still claims 600 capacity. Any clues
>>>> why?
>>> df reports the size of the filesystem, which is still about 600GB--the
>>> filesystem doesn't resize automatically when the size of the underlying
>>> device changes.
>>>
>>> You'll need to use resize2fs, resize_reiserfs, or whatever other tool is
>>> appropriate for your type of filesystem.
>>>
>>> -Corey
>> Right, so this isn't one of my sharpest days... Thanks a bunch, Corey!
No problem.
> Ah, already answered.
vger.kernel.org greylisted my smtp server, so it took my message a while
to get to the list.
-Corey
next prev parent reply other threads:[~2007-10-13 17:59 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 [this message]
2007-10-13 17:41 ` Justin Piszcz
2007-10-14 5:05 ` Bill Davidsen
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=47110797.2050009@fatooh.org \
--to=bugfood-ml@fatooh.org \
--cc=jpiszcz@lucidpixels.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).