linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: rong zhao <zhaorbox@gmail.com>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: resize2fs hang at read function
Date: Wed, 7 Mar 2018 00:08:46 -0500	[thread overview]
Message-ID: <20180307050846.GC7507@thunk.org> (raw)
In-Reply-To: <CAOHr080Z_OO4VqTJFop4UFyQBWFJhe1-Z5xAkbPkx8J=SnG8Vw@mail.gmail.com>

On Wed, Mar 07, 2018 at 11:01:40AM +0800, rong zhao wrote:
> 
> I downloaded the latest e2fsprogs source code from kernel.org, it works.

I'm not sure what the difference is, but I'm *shocked* that RHEL 7.4
is still using e2fsprogs 1.42.x.  There are a very large number of
resize2fs bugs, especially with very large file systems, with
e2fsprogs 1.42.x.  Especially in the case of off-line resizes with a
lage ext4 file system, with a resize2fs from e2fsprogs 1.42.x, data
corruption is almost a certainty.

If you have used resize2fs 1.42.x on that file system, I would suggest
running e2fsck on your large ext4 file system unmounted when you have
a chance, to make sure it's in a good and healthy state.

Regards,

					- Ted

  reply	other threads:[~2018-03-07  5:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07  1:59 resize2fs hang at read function rong zhao
2018-03-07  3:01 ` rong zhao
2018-03-07  5:08   ` Theodore Y. Ts'o [this message]
2018-03-07  7:47     ` Lukas Czerner
2018-03-07  8:49     ` Jan Kara
2018-03-07 23:32       ` rong zhao
2018-03-08  2:20         ` rong zhao
2018-03-08 10:18           ` Lukas Czerner
2018-03-07  7:45 ` Lukas Czerner

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=20180307050846.GC7507@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zhaorbox@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).