From: Hideki EIRAKU <hdk1983@gmail.com>
To: konishi.ryusuke@gmail.com
Cc: christopher@gmerlin.de, linux-nilfs@vger.kernel.org
Subject: Re: nilfs_readdir: bad page in #
Date: Thu, 06 Nov 2025 00:01:10 +0900 (JST) [thread overview]
Message-ID: <20251106.000110.54762674.hdk1983@gmail.com> (raw)
In-Reply-To: <CAKFNMonYLKSikthtoGP9z6Loetu0LxrUsGC6vMSAwaCPE6muqQ@mail.gmail.com>
Hi,
From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Subject: Re: nilfs_readdir: bad page in #
Date: Wed, 5 Nov 2025 00:28:54 +0900
> It's becoming more likely that what I feared is occurring.
> I suspect that an issue (probably a regression) that shouldn't occur
> during normal operation has occurred.
I have seen similar errors since last year with a kernel provided by
Debian 12 as follows:
6.1.0-17-686-pae: 2024-06-15T17:57:31.618788+09:00 nojima kernel: [13858689.003220] NILFS error (device sdb2): nilfs_readdir: bad page in #114046
6.1.0-21-686-pae: 2024-07-15T17:02:30.630090+09:00 nojima kernel: [1915188.018182] NILFS error (device sdb2): nilfs_readdir: bad page in #618331
6.1.0-26-686-pae: 2024-11-09T21:44:58.562985+09:00 nojima kernel: [307159.828834] NILFS error (device sdb2): nilfs_readdir: bad page in #884
6.1.0-34-686-pae: 2025-06-04T21:58:36.641306+09:00 nojima kernel: [2953327.992010] NILFS error (device dm-0): nilfs_readdir: bad page in #29039
When I saw these errors, I thought it might be caused by the SSD
issue, because the sdb2 drive is data storage (since mainly used as
read-only, sometimes write, but many sectors are rarely accessed), and
the dm-0 drive is too old (used as root fs and NILFS home directory
since 2011 & Power_On_Hours is >120k). However, if these were caused
by software bugs, the above versions might be good hints to find
whether recent regression or not.
The kernel package information including changelog is available at
Debian web site, like
https://packages.debian.org/bookworm/linux-image-6.1.0-34-686 .
Regards,
Hideki EIRAKU
prev parent reply other threads:[~2025-11-05 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 14:06 nilfs_readdir: bad page in # Christopher Zimmermann
2025-10-18 11:04 ` Ryusuke Konishi
2025-11-04 14:00 ` Christopher Zimmermann
2025-11-04 15:28 ` Ryusuke Konishi
2025-11-04 16:04 ` Christopher Zimmermann
2025-11-04 16:43 ` Christopher Zimmermann
2025-11-05 15:01 ` Hideki EIRAKU [this message]
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=20251106.000110.54762674.hdk1983@gmail.com \
--to=hdk1983@gmail.com \
--cc=christopher@gmerlin.de \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-nilfs@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).