From: Hanasaki Jiji <hanasaki@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: ext4 e2fsck error interpretation and howto fix? expecting 249045418 actual extent phys 249045427 log 1 len 2
Date: Thu, 4 Apr 2024 18:23:44 -0400 [thread overview]
Message-ID: <CAMr-kF3yY6zYi2ZBXG7g77zaG2qzA9B294cqL=B7HOtkXYhOeA@mail.gmail.com> (raw)
Hello all,
I have an ext4 filesystem with e2fsck reporting many of the below
lines. Neither e2fsck nor fsck fix the issue.
Repeated runs result in the same errors.
kernel version = linux-image-6.1.0-18-amd64 / Debian Bookworm
Your help understanding the output and help fixing are very much appreciated.
Thank you,
==== e2fsck output ====
62264184(d): expecting 249045418 actual extent phys 249045427 log 1 len 2
62264185(d): expecting 249045419 actual extent phys 249045429 log 1 len 2
62266954(d): expecting 249045453 actual extent phys 249045486 log 1 len 3
...
/dev/...: ***** FILE SYSTEM WAS MODIFIED *****
5123698 inodes used (8.01%, out of 64004096)
3791 non-contiguous files (0.1%)
3725 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 5112072/403
...
next reply other threads:[~2024-04-04 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 22:23 Hanasaki Jiji [this message]
2024-04-05 4:20 ` ext4 e2fsck error interpretation and howto fix? expecting 249045418 actual extent phys 249045427 log 1 len 2 Theodore Ts'o
2024-04-05 5:41 ` hanasaki
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='CAMr-kF3yY6zYi2ZBXG7g77zaG2qzA9B294cqL=B7HOtkXYhOeA@mail.gmail.com' \
--to=hanasaki@gmail.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).