From: Lukas Czerner <lczerner@redhat.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Andreas Dilger <adilger@dilger.ca>,
Alok Jain <jain.alok103@gmail.com>,
linux-ext4@vger.kernel.org
Subject: Re: Issue with extension of ext4 filesystem on Rhel7
Date: Fri, 1 Oct 2021 16:42:39 +0200 [thread overview]
Message-ID: <20211001144239.fgizeucgzhingeio@work> (raw)
In-Reply-To: <YVcOqNktN4GgFFab@mit.edu>
On Fri, Oct 01, 2021 at 09:35:36AM -0400, Theodore Ts'o wrote:
> On Thu, Sep 30, 2021 at 11:52:20PM -0600, Andreas Dilger wrote:
> > On Sep 30, 2021, at 23:43, Alok Jain <jain.alok103@gmail.com> wrote:
> > >
> > > I have a problem while extending the ext4 filesystem on my block
> > > device which was 12Tb now extended to 32tb. I uses growpart then
> > > e2fsck followed by resize which failed, Any idea how to address
> > > this?
> > >
> > > [root@prod-dev1 ~]# resize2fs /dev/sdj1
> > >
> > > resize2fs 1.42.9 (28-Dec-2013)
> > >
> > > resize2fs: New size too large to be expressed in 32 bits
Hi,
as others have already mentioned, unfortunatelly your file system does
not have 64-bit feature enabled and so you won't be able to simply
resize past 16TB. This feature was made default after RHEL7 GA, but sadly
it was likely too late for you, sorry about that.
You can try the advice given here, or you can contact RH support as they
might have some solution for you. However I am affraid it will always
involve backup for the reasons already mentioned.
>
> Finally, in addtion to e2fsprogs 1.42.9 being Very, Very Old, if you
> are using such a prehistoric version of e2fsprogs, it's likely that
> the Linux kernel, and other portions of your Linux userspace, are
> antedeluvian as well. That means not only are you missing bug fixes,
> you are likely missing many security bug fixes as well.
As I am sure you know RH is regularly fixing bugs and security bugs
especially and supporting RHEL releases for a very long time. As long as
10 years or even longer with ELS, that's much longer than say meager 3
years.
You can find more details here
https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates
-Lukas
next prev parent reply other threads:[~2021-10-01 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG-6nk9DKKw2RHiXx_kWN1B5xcTrctTCypUPaicaaW1Ag0jDzw@mail.gmail.com>
[not found] ` <81899623-90FE-4AFA-AAB6-5ABB21903CBB@dilger.ca>
2021-10-01 13:35 ` Issue with extension of ext4 filesystem on Rhel7 Theodore Ts'o
2021-10-01 14:42 ` Lukas Czerner [this message]
2021-10-01 16:40 ` Theodore Ts'o
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=20211001144239.fgizeucgzhingeio@work \
--to=lczerner@redhat.com \
--cc=adilger@dilger.ca \
--cc=jain.alok103@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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