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@xxxxxxxxx> 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
