From: Andreas Dilger <adilger@dilger.ca>
To: listac@nebelschwaden.de
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck fails on non journalled partition
Date: Fri, 15 Mar 2019 20:57:08 -0600 [thread overview]
Message-ID: <22AA9175-3D96-424E-BC91-6232100B170D@dilger.ca> (raw)
In-Reply-To: <bfa8103e-cf07-ca8d-f1f2-df60ea5bd915@nebelschwaden.de>
It looks like you have some superblock corruption, since the journal UUID is non-zero, and the journal inode is also non-zero. You can probably use debugfs "ssv" command to clear these fields so that e2fsck doesn't think there is a journal somewhere.
Cheers, Andreas
> On Mar 15, 2019, at 13:28, Ede Wolf <listac@nebelschwaden.de> wrote:
>
> I have to check an ext4 partition, that has been created without a journal. But, as it seems, e2fsck is refusing to check this drive, failing with a "no external journal has been found" error, code 12. That of course is correct, no journal does imply no external journal.
>
> I am wondering, ^has_journal is well documented in both the mkfs.ext4 manpage as well as tune2fs. So by omitting the journal nothing obscure, hacky or obviously unsupported has been done.
>
> Why is e2fsck refusing to check the partition? Or what else may I have be doing wrong?
>
>
> ~ # e2fsck -fv /dev/sde1
> e2fsck 1.44.5 (15-Dec-2018)
> Can't find external journal
>
> USERDATA: ********** WARNING: Filesystem still has errors **********
>
> ~ # echo $?
> 12
> ~ #
>
> Filesystem has been created similar to this:
>
> mkfs -m 0 -O "^has_journal,dir_index,^metadata_csum,64bit,^ext_attr,^huge_file,large_dir,^metadata_csum_seed,^quota,extent" -b 4096 -i 32768 -L USERDATA
>
>
>
> ~ # tune2fs -l /dev/sde1
> tune2fs 1.44.5 (15-Dec-2018)
> Filesystem volume name: USERDATA
> Last mounted on: /mnt/userdata
> Filesystem UUID: 241d6272-a004-44ef-9998-7fbc3ef98672
> Filesystem magic number: 0xEF53
> Filesystem revision #: 1 (dynamic)
> Filesystem features: ext_attr resize_inode dir_index filetype extent 64bit large_dir sparse_super large_file
> Filesystem flags: signed_directory_hash
> Default mount options: user_xattr acl
> Filesystem state: not clean with errors
> Errors behavior: Continue
> Filesystem OS type: Linux
> Inode count: 4669440
> Block count: 9338880
> Reserved block count: 0
> Overhead blocks: 1536
> Free blocks: 5602781
> Free inodes: 4247845
> First block: 0
> Block size: 4096
> Fragment size: 4096
> Group descriptor size: 64
> Reserved GDT blocks: 1024
> Blocks per group: 32768
> Fragments per group: 32768
> Inodes per group: 16384
> Inode blocks per group: 1024
> Filesystem created: Wed Jan 30 18:42:35 2019
> Last mount time: Fri Mar 15 20:16:26 2019
> Last write time: Fri Mar 15 20:16:26 2019
> Mount count: 90
> Maximum mount count: -1
> Last checked: Thu Jan 31 18:49:12 2019
> Check interval: 0 (<none>)
> Lifetime writes: 204 GB
> Reserved blocks uid: 0 (user root)
> Reserved blocks gid: 0 (group root)
> First inode: 11
> Inode size: 256
> Required extra isize: 32
> Desired extra isize: 32
> Journal UUID: 00000000-1b00-0000-0000-000000000000
> Journal inode: 131072
> Default directory hash: half_md4
> Directory Hash Seed: 2416ec00-bef9-437a-a3b1-f626303d72a2
> FS Error count: 41
> First error time: Sun Mar 3 13:15:39 2019
> First error function: ext4_readdir
> First error line #: 182
> First error inode #: 3673403
> First error block #: 0
> Last error time: Mon Mar 11 18:22:09 2019
> Last error function: ext4_empty_dir
> Last error line #: 2712
> Last error inode #: 639817
> Last error block #: 1
>
next prev parent reply other threads:[~2019-03-16 2:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 19:28 e2fsck fails on non journalled partition Ede Wolf
2019-03-16 2:57 ` Andreas Dilger [this message]
2019-03-16 9:10 ` Ede Wolf
2019-03-17 21:53 ` Theodore Ts'o
2019-03-17 22:51 ` Ede Wolf
2019-03-18 14:35 ` Ede Wolf
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=22AA9175-3D96-424E-BC91-6232100B170D@dilger.ca \
--to=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=listac@nebelschwaden.de \
/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