Re: e2scrub finds corruption immediately after mounting

["Brian J. Murrell" <brian@interlinx.bc.ca>]

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Wed, 2024-01-10 at 16:43 -0700, Andreas Dilger wrote:
> 
> Hello Brian, long time no see!

Hi Andreas.  Indeed, it has been a while.  :-)

> I was wondering if this might be a case where e2fsck removed the
> journal
> on an ext4 filesystem, and then it wasn't recreated (e.g. if e2fsck
> was
> killed before it finished cleanly).
> 
> However, looking at the features enabled on the filesystem, it
> definitely
> looks like this was originally formatted as ext4.

I suspect you mean s/4/2/ above?

> Many of these features can be enabled on an existing filesystem, like
> has_journal (ext3/4 journal), extents (improved large file
> allocation),
> huge_file (> 2TB files), dir_nlink (> 32000 subdirs) if you want
> them.
> I _think_ uninit_bg (e2fsck skip unused metadata may) is included
> here.
> 
> Some cannot be enabled on an existing filesystem like flex_bg
> (localized
> metadata), and extra_isize (fast xattrs).
> 
> Whether that is worthwhile for you to enable, or just
> backup/reformat/sync
> is up to you.

Indeed.  I did simply re-create and copy as suggested by the wiki
entry.

Cheers,
b.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]