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:20:44 +0000 [thread overview]
Message-ID: <bug-218011-13602-0R7d32lSdz@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 #5 from jaak+bugzilla.kernel.org@ristioja.ee ---
The new root filesystem was created with mkfs.ext4 with no special options.
Here is the relevant /etc/mke2fs.conf:
[defaults]
base_features =
sparse_super,large_file,filetype,resize_inode,dir_index,ext_attr
default_mntopts = acl,user_xattr,journal_data
enable_periodic_fsck = 0
blocksize = 4096
inode_size = 256
inode_ratio = 16384
[fs_types]
ext3 = {
features = has_journal
}
ext4 = {
features =
has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize
}
small = {
blocksize = 1024
inode_ratio = 4096
}
floppy = {
blocksize = 1024
inode_ratio = 8192
}
big = {
inode_ratio = 32768
}
huge = {
inode_ratio = 65536
}
news = {
inode_ratio = 4096
}
largefile = {
inode_ratio = 1048576
blocksize = -1
}
largefile4 = {
inode_ratio = 4194304
blocksize = -1
}
hurd = {
blocksize = 4096
inode_size = 128
warn_y2038_dates = 0
}
And the dumpe2fs -h output from the currently failing system:
dumpe2fs 1.47.0 (5-Feb-2023)
Filesystem volume name: root
Last mounted on: /
Filesystem UUID: b7112037-b835-45ac-b3b3-4d9250c53503
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype
needs_recovery 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: 524288
Overhead clusters: 242376
Free blocks: 6899974
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 Oct 14 18:03:49 2023
Last mount time: Sat Oct 14 18:16:50 2023
Last write time: Sat Oct 14 18:16:48 2023
Mount count: 2
Maximum mount count: -1
Last checked: Sat Oct 14 18:03:49 2023
Check interval: 0 (<none>)
Lifetime writes: 26 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 inode: 8
Default directory hash: half_md4
Directory Hash Seed: bf662df3-a40b-4276-905e-70bb51bfd867
Journal backup: inode blocks
Checksum type: crc32c
Checksum: 0xdf22e900
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: 0x00001f33
Journal start: 18150
Journal checksum type: crc32c
Journal checksum: 0x70a695b1
--
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:20 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
2023-10-15 6:18 ` bugzilla-daemon
2023-10-15 6:20 ` bugzilla-daemon [this message]
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-0R7d32lSdz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.