From: Ram Ramesh <rramesh2400@gmail.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: My MD is too big to resize ext4.
Date: Sat, 8 Jul 2017 13:37:58 -0500 [thread overview]
Message-ID: <05c7f3c8-8eb1-a7c2-a3d3-125b00215aba@gmail.com> (raw)
In-Reply-To: <20170708161513.37b09dbc@natsu>
On 07/08/2017 06:15 AM, Roman Mamedov wrote:
> On Fri, 7 Jul 2017 19:41:13 -0500
> Ram Ramesh <rramesh2400@gmail.com> wrote:
>
>> 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.
> Considering the other possible options that have been mentioned, using the
> Ext4 built-in larger devices support (which has been implemented recently)
> seems to be your best bet.
> https://askubuntu.com/questions/779754/how-do-i-resize-an-ext4-partition-beyond-the-16tb-limit
>
> The required e2fsprogs version 1.43 is included in Ubuntu 16.10 by now, so you
> don't even need to build it from the source.
> https://packages.ubuntu.com/yakkety/e2fsprogs
>
> But really, if you have everything on one array with a single huge filesystem
> and no backups, that's just asking for trouble and a complete data loss.
>
Thanks. This is exactly the one that I was talking about as a web
solution. Did not know it is available in 16.10.
Besides the above, I hear your last caution well. I do have backup by
distributing files using rsync over multiple (old) disks (4+4+3+3TB). I
just don't trust my back up and thus pretend that I do not have one.
However, for a short one week trial, I think, I am ok.
Going forward, I will not be able to backup 24TB volume (if I succeed in
building one big MD) as I will not have enough drives to distribute
data. So, there is going to be a problem. So, I am thinking seriously
building several smaller MD devices out of my 6x6TB drives. Look at my
reply to Andreas. Let me know your thoughts on that. If I build smaller
MDs each can be temporarily backed up for updates etc. So, I will still
be ok with data as long as I work only on one MD at a time that fits my
set of backup disks.
Ramesh
prev parent reply other threads:[~2017-07-08 18:37 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
2017-07-08 18:28 ` Ram Ramesh
2017-07-08 11:15 ` Roman Mamedov
2017-07-08 18:37 ` Ram Ramesh [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=05c7f3c8-8eb1-a7c2-a3d3-125b00215aba@gmail.com \
--to=rramesh2400@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
/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).