linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Marcus <nexuslite@gmail.com>
Cc: NeilBrown <neilb@suse.de>, Roberto Spadim <roberto@spadim.com.br>,
	Simon Mcnair <simonmcnair@gmail.com>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Raid 5 Array
Date: Sun, 3 Apr 2011 23:50:49 +0600	[thread overview]
Message-ID: <20110403235049.5c940295@natsu> (raw)
In-Reply-To: <BANLkTik7XHyOCK8SwhPTaWxQ+K=2FRowng@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

On Sun, 3 Apr 2011 10:46:23 -0700
Marcus <nexuslite@gmail.com> wrote:

> I provided you all relevant information if you payed attention to
> sizes and the fact that I stated that I can add a new partition to the
> device you would have realized that I have already applied grow to the
> raid.
> 
> 1465159552 raid size
> 976767808 partition size
> 
> See how partition is smaller than raid by about 500GB?

Then why not run "cfdisk /dev/md2" (I recommend the version from "GNU fdisk"),
notice that you have a 900GB partition there and 500 GB of free space, then
resize the partition?

> nexuslite@ubuntu:~$ resize2fs -p /dev/md2p1
> resize2fs 1.41.11 (14-Mar-2010)
> The filesystem is already 244191952 blocks long.  Nothing to do!
> 
> There is the exact message resize2fs is returning. 244191968 is the
> current end block of the partition. parted also shows 244191968 as the
> maximum block size for a partition. There are no related dmesg because
> it is not an error it is just undesired results.

You don't seem to understand the difference between /dev/md2 and /dev/md2p1.
And also that resize2fs will not resize md2p1, it will only amend the
ext* filesystem so that it takes all of md2p1.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-04-03 17:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02 18:51 Raid 5 Array Marcus
2011-04-02 19:01 ` Simon McNair
     [not found]   ` <BANLkTimJfUhvkpkkAH=NLJOvLL-Jotrwqg@mail.gmail.com>
2011-04-02 20:09     ` Simon McNair
     [not found]       ` <BANLkTim3uOiF7Qdir_Vou3rSp1zJmgf6iA@mail.gmail.com>
2011-04-02 21:27         ` Simon Mcnair
2011-04-02 21:45       ` Simon Mcnair
2011-04-02 22:01         ` Roman Mamedov
2011-04-02 22:04           ` Roberto Spadim
2011-04-02 23:06             ` Marcus
2011-04-03  0:22               ` Marcus
2011-04-03  6:41                 ` Marcus
2011-04-03  7:49                   ` NeilBrown
2011-04-03  8:02                     ` Marcus
2011-04-03 11:01                       ` NeilBrown
2011-04-03 17:46                         ` Marcus
2011-04-03 17:50                           ` Roman Mamedov [this message]
     [not found]                             ` <BANLkTinzOpR-pgR1GYxgxaJhNoOUxc0D_w@mail.gmail.com>
2011-04-03 19:57                               ` Roman Mamedov

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=20110403235049.5c940295@natsu \
    --to=rm@romanrm.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nexuslite@gmail.com \
    --cc=roberto@spadim.com.br \
    --cc=simonmcnair@gmail.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;
as well as URLs for NNTP newsgroup(s).