From: Wols Lists <antlists@youngman.org.uk>
To: Ram Ramesh <rramesh2400@gmail.com>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: My MD is too big to resize ext4.
Date: Sat, 8 Jul 2017 09:30:20 +0100 [thread overview]
Message-ID: <5960981C.9040906@youngman.org.uk> (raw)
In-Reply-To: <6c827d07-19d8-017b-ca95-5e6f84b7821a@gmail.com>
On 08/07/17 01:41, Ram Ramesh wrote:
> Hi,
>
> I asked in other linux forums and did not get enough info. So I come
> here even though this is not mdadm/RAID issue.
>
> I replaced 3TB disks in my 6-disk RAID6 with 6TB and now my md0 is 24TB.
> I had 32bit version of ext4 on it which can only be grown to 16TB. Any
> one had this issue before and any _/inplace/_ good solution to grow ext4
> to full 24TB? It is unlikely that I will be able to back up and recreate
> file system.
>
> My filesystem is on md0 drive so I guess partitioning and making into 2x
> 12TB ext4 will not work. I am not even sure if we can partition md like
> any other disk.
You can partition an array and create partitions in it - caveat I
haven't done it, and I've never seen anyone here mention that they've
done it - lvm seems to be the more popular version.
>
> On the web, I only found one solution that required upgrading kernel to
> some very recent one (not in my distro) and getting the bleeding edge
> resize2fs. This makes me nervous. Is there a solution that avoids this.
>
resize2fs is bleeding edge? I suspect it's v0.99 quality, ie nobody has
the nerve to upgrade it to v1, despite it being rock solid. I know I've
used it without trouble. Most of these utilities are pretty solid
(unless the underlying filesystem itself is experimental ...)
Cheers,
Wol
next prev parent reply other threads:[~2017-07-08 8:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:41 My MD is too big to resize ext4 Ram Ramesh
2017-07-08 6:50 ` Andreas Klauer
2017-07-08 18:12 ` Ram Ramesh
2017-07-08 19:44 ` Andreas Klauer
2017-07-08 22:22 ` Ram Ramesh
2017-07-09 23:09 ` Ram Ramesh
2017-07-08 7:34 ` Brad Campbell
2017-07-08 7:40 ` Reindl Harald
2017-07-08 8:12 ` Brad Campbell
2017-07-08 18:19 ` Ram Ramesh
2017-07-08 18:48 ` Ram Ramesh
2017-07-08 8:30 ` Wols Lists [this message]
2017-07-08 18:28 ` Ram Ramesh
2017-07-08 11:15 ` Roman Mamedov
2017-07-08 18:37 ` Ram Ramesh
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=5960981C.9040906@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=rramesh2400@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 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.