From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 218011] ext4 root filesystem related hangs on 6.5 kernels
Date: Sun, 15 Oct 2023 06:05:43 +0000 [thread overview]
Message-ID: <bug-218011-13602-rS3oJf4YsL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218011-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218011
--- Comment #3 from jaak+bugzilla.kernel.org@ristioja.ee ---
The mount line for root I already posted was this:
/dev/nvme0n1p2 on / type ext4
(rw,noatime,nodiratime,nodioread_nolock,discard,nodelalloc)
I'm sorry, but I recreated the root partition for safety. However, here's the
dumpe2fs output on a binary copy of the old failing partition (only label
changed with tune2fs -L):
# dumpe2fs -h /dev/vg/root-old
dumpe2fs 1.47.0 (5-Feb-2023)
Filesystem volume name: root-old
Last mounted on: /
Filesystem UUID: febed35b-df13-4e6a-a9de-4ae17673322a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype
extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize
metadata_csum
Filesystem flags: signed_directory_hash
Default mount options: journal_data user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 2621440
Block count: 10485760
Reserved block count: 1048576
Free blocks: 5921591
Free inodes: 2208475
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: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Sat Apr 25 15:02:31 2020
Last mount time: Sat Oct 14 17:49:31 2023
Last write time: Sat Oct 14 17:49:24 2023
Mount count: 133
Maximum mount count: -1
Last checked: Thu Nov 11 15:55:30 2021
Check interval: 0 (<none>)
Lifetime writes: 79 TB
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 inode: 8
Default directory hash: half_md4
Directory Hash Seed: 764a85fe-24b0-4a45-96d7-7b43a75d90a2
Journal backup: inode blocks
Checksum type: crc32c
Checksum: 0xc4176fe3
Journal features: journal_64bit journal_checksum_v3
Total journal size: 256M
Total journal blocks: 65536
Max transaction length: 65536
Fast commit length: 0
Journal sequence: 0x0080d73c
Journal start: 0
Journal checksum type: crc32c
Journal checksum: 0x6d8e4ded
dumpe2fs: Superblock checksum does not match superblock while trying to open
/dev/vg/root-old
*** Run e2fsck now!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-10-15 6:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 19:33 [Bug 218011] New: ext4 root filesystem related hangs on 6.5 kernels bugzilla-daemon
2023-10-14 20:56 ` [Bug 218011] " bugzilla-daemon
2023-10-14 20:58 ` bugzilla-daemon
2023-10-15 6:05 ` bugzilla-daemon [this message]
2023-10-15 6:18 ` bugzilla-daemon
2023-10-15 6:20 ` bugzilla-daemon
2023-10-15 19:06 ` bugzilla-daemon
2023-10-18 20:45 ` bugzilla-daemon
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=bug-218011-13602-rS3oJf4YsL@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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).