nilfs_readdir: bad page in #

nilfs_readdir: bad page in #

[Christopher Zimmermann]

[-- Attachment #1: Type: text/plain, Size: 12129 bytes --]

Hi,

this is what I saw today:

Oct 17 09:44:27 merari.gmerlin.de kernel: NILFS version 2 loaded
Oct 17 09:44:27 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
Oct 17 09:44:27 merari.gmerlin.de nilfs_cleanerd[715]: start
Oct 17 09:44:27 merari.gmerlin.de nilfs_cleanerd[715]: pause (clean check)
Oct 17 15:05:45 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #235406
Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:30 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:30 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:34 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:34 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:40 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:40 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:42 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:42 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
Oct 17 15:10:49 merari.gmerlin.de nilfs_cleanerd[715]: shutdown
Oct 17 15:10:52 merari.gmerlin.de kernel: NILFS (nvme0n1p5): disposed unprocessed dirty file(s) when detaching log writer

[reboot]

Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS version 2 loaded
Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting unchecked fs
Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): recovery complete
Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting fs with errors
Oct 17 15:11:09 merari.gmerlin.de nilfs_cleanerd[704]: start
Oct 17 15:11:09 merari.gmerlin.de nilfs_cleanerd[704]: pause (clean check)
Oct 17 15:51:11 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #488967
Oct 17 15:53:04 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:04 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:05 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:05 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:08 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:08 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:12 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:12 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:12 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:12 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:14 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:14 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:16 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:16 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:16 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:16 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:16 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:16 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:16 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:16 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:18 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
Oct 17 15:53:20 merari.gmerlin.de nilfs_cleanerd[704]: shutdown
Oct 17 15:53:20 merari.gmerlin.de kernel: NILFS (nvme0n1p5): disposed unprocessed dirty file(s) when detaching log writer

[reboot]

Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS version 2 loaded
Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting unchecked fs
Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): recovery complete
Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting fs with errors
Oct 17 15:53:39 merari.gmerlin.de nilfs_cleanerd[717]: start
Oct 17 15:53:39 merari.gmerlin.de nilfs_cleanerd[717]: pause (clean 
check)

Both, inode 257 and inode 258 were ~/.xsession-errors.old

What to think of "mounting fs with errors"?
Especially since there is no fsck?


Christopher

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: nilfs_readdir: bad page in #

[Ryusuke Konishi]

On Sat, Oct 18, 2025 at 7:01 AM Christopher Zimmermann wrote:
>
> Hi,
>
> this is what I saw today:
>
> Oct 17 09:44:27 merari.gmerlin.de kernel: NILFS version 2 loaded
> Oct 17 09:44:27 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
> Oct 17 09:44:27 merari.gmerlin.de nilfs_cleanerd[715]: start
> Oct 17 09:44:27 merari.gmerlin.de nilfs_cleanerd[715]: pause (clean check)
> Oct 17 15:05:45 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #235406
> Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
...
> Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
> Oct 17 15:10:49 merari.gmerlin.de nilfs_cleanerd[715]: shutdown
> Oct 17 15:10:52 merari.gmerlin.de kernel: NILFS (nvme0n1p5): disposed unprocessed dirty file(s) when detaching log writer
>
> [reboot]
>
> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS version 2 loaded
> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting unchecked fs
> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): recovery complete
> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting fs with errors
> Oct 17 15:11:09 merari.gmerlin.de nilfs_cleanerd[704]: start
> Oct 17 15:11:09 merari.gmerlin.de nilfs_cleanerd[704]: pause (clean check)
> Oct 17 15:51:11 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #488967
> Oct 17 15:53:04 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
...
> Oct 17 15:53:04 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
> Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
> Oct 17 15:53:20 merari.gmerlin.de nilfs_cleanerd[704]: shutdown
> Oct 17 15:53:20 merari.gmerlin.de kernel: NILFS (nvme0n1p5): disposed unprocessed dirty file(s) when detaching log writer
>
> [reboot]
>
> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS version 2 loaded
> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting unchecked fs
> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): recovery complete
> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting fs with errors
> Oct 17 15:53:39 merari.gmerlin.de nilfs_cleanerd[717]: start
> Oct 17 15:53:39 merari.gmerlin.de nilfs_cleanerd[717]: pause (clean
> check)
>
> Both, inode 257 and inode 258 were ~/.xsession-errors.old
>
> What to think of "mounting fs with errors"?
> Especially since there is no fsck?

Yes, this is a flag that should be repaired by fsck, but because fsck
is not available, it is in an unrecoverable state.
This is a flaw in this project and there is no excuse for it.

For reference, I would like to ask under what circumstances did this occur?

If this happens easily, I am concerned that there may be a new regression.

The error message suggests a corrupted btree, which is causing the
directory read to fail.

I'm also concerned about the problem with .xsession-errors, a file
that seems to have a short lifespan and involves rename.

For reference, what version of your kernel are you using?


Regards,
Ryusuke Konishi

Re: nilfs_readdir: bad page in #

[Christopher Zimmermann]

[-- Attachment #1: Type: text/plain, Size: 4958 bytes --]

On Sat, Oct 18, 2025 at 08:04:28PM +0900, Ryusuke Konishi wrote:
>On Sat, Oct 18, 2025 at 7:01 AM Christopher Zimmermann wrote:
>>
>> Hi,
>>
>> this is what I saw today:
>>
>> Oct 17 09:44:27 merari.gmerlin.de kernel: NILFS version 2 loaded
>> Oct 17 09:44:27 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
>> Oct 17 09:44:27 merari.gmerlin.de nilfs_cleanerd[715]: start
>> Oct 17 09:44:27 merari.gmerlin.de nilfs_cleanerd[715]: pause (clean check)
>> Oct 17 15:05:45 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #235406
>> Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
>...
>> Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
>> Oct 17 15:10:49 merari.gmerlin.de nilfs_cleanerd[715]: shutdown
>> Oct 17 15:10:52 merari.gmerlin.de kernel: NILFS (nvme0n1p5): disposed unprocessed dirty file(s) when detaching log writer
>>
>> [reboot]
>>
>> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS version 2 loaded
>> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting unchecked fs
>> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): recovery complete
>> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
>> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting fs with errors
>> Oct 17 15:11:09 merari.gmerlin.de nilfs_cleanerd[704]: start
>> Oct 17 15:11:09 merari.gmerlin.de nilfs_cleanerd[704]: pause (clean check)
>> Oct 17 15:51:11 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #488967
>> Oct 17 15:53:04 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
>...
>> Oct 17 15:53:04 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
>> Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
>> Oct 17 15:53:20 merari.gmerlin.de nilfs_cleanerd[704]: shutdown
>> Oct 17 15:53:20 merari.gmerlin.de kernel: NILFS (nvme0n1p5): disposed unprocessed dirty file(s) when detaching log writer
>>
>> [reboot]
>>
>> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS version 2 loaded
>> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting unchecked fs
>> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): recovery complete
>> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
>> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting fs with errors
>> Oct 17 15:53:39 merari.gmerlin.de nilfs_cleanerd[717]: start
>> Oct 17 15:53:39 merari.gmerlin.de nilfs_cleanerd[717]: pause (clean
>> check)
>>
>> Both, inode 257 and inode 258 were ~/.xsession-errors.old
>>
>> What to think of "mounting fs with errors"?
>> Especially since there is no fsck?
>
>For reference, I would like to ask under what circumstances did this 
>occur?

It occured running debian trixie kernel 6.12.48+deb13-amd64

/home was on a nilfs2 filesystem:
/dev/nvme0n1p5 on /home type nilfs2 (rw,noatime,nodiratime,discard)

>If this happens easily, I am concerned that there may be a new regression.

Now I had some weeks without the issue re-occuring. Now it happened 
again (after formatting the fs and restoring from backup a few weeks 
ago) :-(

Nov 04 14:31:01 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #170719
Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)

want to take a wild guess which file had inode 259 at the time of the 
error? - ~/.xsession-error again.

>The error message suggests a corrupted btree, which is causing the
>directory read to fail.
>
>I'm also concerned about the problem with .xsession-errors, a file
>that seems to have a short lifespan and involves rename.
>
>For reference, what version of your kernel are you using?

6.12.48+deb13-amd64

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: nilfs_readdir: bad page in #

[Ryusuke Konishi]

On Tue, Nov 4, 2025 at 11:00 PM Christopher Zimmermann wrote:
>
> On Sat, Oct 18, 2025 at 08:04:28PM +0900, Ryusuke Konishi wrote:
> >On Sat, Oct 18, 2025 at 7:01 AM Christopher Zimmermann wrote:
> >>
> >> Hi,
> >>
> >> this is what I saw today:
> >>
> >> Oct 17 09:44:27 merari.gmerlin.de kernel: NILFS version 2 loaded
> >> Oct 17 09:44:27 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
> >> Oct 17 09:44:27 merari.gmerlin.de nilfs_cleanerd[715]: start
> >> Oct 17 09:44:27 merari.gmerlin.de nilfs_cleanerd[715]: pause (clean check)
> >> Oct 17 15:05:45 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #235406
> >> Oct 17 15:10:06 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
> >...
> >> Oct 17 15:10:48 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
> >> Oct 17 15:10:49 merari.gmerlin.de nilfs_cleanerd[715]: shutdown
> >> Oct 17 15:10:52 merari.gmerlin.de kernel: NILFS (nvme0n1p5): disposed unprocessed dirty file(s) when detaching log writer
> >>
> >> [reboot]
> >>
> >> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS version 2 loaded
> >> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting unchecked fs
> >> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): recovery complete
> >> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
> >> Oct 17 15:11:09 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting fs with errors
> >> Oct 17 15:11:09 merari.gmerlin.de nilfs_cleanerd[704]: start
> >> Oct 17 15:11:09 merari.gmerlin.de nilfs_cleanerd[704]: pause (clean check)
> >> Oct 17 15:51:11 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #488967
> >> Oct 17 15:53:04 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
> >...
> >> Oct 17 15:53:04 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
> >> Oct 17 15:53:19 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=258)
> >> Oct 17 15:53:20 merari.gmerlin.de nilfs_cleanerd[704]: shutdown
> >> Oct 17 15:53:20 merari.gmerlin.de kernel: NILFS (nvme0n1p5): disposed unprocessed dirty file(s) when detaching log writer
> >>
> >> [reboot]
> >>
> >> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS version 2 loaded
> >> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting unchecked fs
> >> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): recovery complete
> >> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
> >> Oct 17 15:53:39 merari.gmerlin.de kernel: NILFS (nvme0n1p5): mounting fs with errors
> >> Oct 17 15:53:39 merari.gmerlin.de nilfs_cleanerd[717]: start
> >> Oct 17 15:53:39 merari.gmerlin.de nilfs_cleanerd[717]: pause (clean
> >> check)
> >>
> >> Both, inode 257 and inode 258 were ~/.xsession-errors.old
> >>
> >> What to think of "mounting fs with errors"?
> >> Especially since there is no fsck?
> >
> >For reference, I would like to ask under what circumstances did this
> >occur?
>
> It occured running debian trixie kernel 6.12.48+deb13-amd64
>
> /home was on a nilfs2 filesystem:
> /dev/nvme0n1p5 on /home type nilfs2 (rw,noatime,nodiratime,discard)
>
> >If this happens easily, I am concerned that there may be a new regression.
>
> Now I had some weeks without the issue re-occuring. Now it happened
> again (after formatting the fs and restoring from backup a few weeks
> ago) :-(
>
> Nov 04 14:31:01 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #170719
> Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
> Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
> Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
> Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
> Nov 04 14:34:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=259)
>
> want to take a wild guess which file had inode 259 at the time of the
> error? - ~/.xsession-error again.
>
> >The error message suggests a corrupted btree, which is causing the
> >directory read to fail.
> >
> >I'm also concerned about the problem with .xsession-errors, a file
> >that seems to have a short lifespan and involves rename.
> >
> >For reference, what version of your kernel are you using?
>
> 6.12.48+deb13-amd64

HI Christopher,

I appreciate your feedback despite the frustration caused by the
repeated issues.

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.

6.12 is a well-maintained kernel series, and 6.12.48 is fairly
up-to-date, except for two stable fixes that are unrelated to this
issue.

Therefore, it's likely that this issue can be reproduced even with the
latest mainline kernel.

6.12.48 has backported nearly a dozen stable patches for nilfs2,
including important bug fixes for rename, bmap/btree, and preventing
the reuse of deleted inodes. It's possible that one of these patches
is backfiring.

Based on what's happening with the .xsession-errors file, I guess that
the problem is indeed occurring with files that are renamed or have a
short lifespan.

I'll try to create an environment that reproduces these conditions.

Thanks,
Ryusuke Konishi

Re: nilfs_readdir: bad page in #

[Christopher Zimmermann]

[-- Attachment #1: Type: text/plain, Size: 5014 bytes --]

On Wed, Nov 05, 2025 at 12:28:54AM +0900, Ryusuke Konishi wrote:
>Based on what's happening with the .xsession-errors file, I guess that
>the problem is indeed occurring with files that are renamed or have a
>short lifespan.
>
>I'll try to create an environment that reproduces these conditions.

Not sure if this helps. Here are some more observations:

The nilfs_readdir: bad page in #170719 error was triggered by a
find ~/ -iname …

The following
nilfs_bmap_lookup_contig: broken bmap (inode number=259)
errors were then triggered by running a backup (restic) or simply 
reading ~/.xsession-errors. Some content of the broken 
~/.xsession-errors could then still be read.

What I noticed now while killing processes preventing the unmounting of 
the errored filesystem is that it is passed to many x-clients as 
stdout/stderr fd:

COMMAND    PID     USER FD   TYPE DEVICE SIZE/OFF NODE NAME
herbstluf 1506 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
herbstluf 1506 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
dunst     1642 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
dunst     1642 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
conky     1643 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
conky     1643 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
nm-applet 1644 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
nm-applet 1644 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
blueman-a 1645 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
blueman-a 1645 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
firefox-e 1655 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
firefox-e 1655 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
crashhelp 1727 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
crashhelp 1727 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
blueman-t 1821 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
blueman-t 1821 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
polybar   2069 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
polybar   2069 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Socket    2087 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Socket    2087 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Privilege 2122 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Privilege 2122 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
RDD\x20Pr 2129 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
RDD\x20Pr 2129 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Isolated  2167 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Isolated  2167 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
WebExtens 2230 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
WebExtens 2230 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Utility   2317 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Utility   2317 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Web\x20Co 2449 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Web\x20Co 2449 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Web\x20Co 2525 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Web\x20Co 2525 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Web\x20Co 2559 madroach 1w   REG  259,5     3637   11 /home/madroach/.xsession-errors
Web\x20Co 2559 madroach 2w   REG  259,5     3637   11 /home/madroach/.xsession-errors

Most content comes from herbstluftwm logging unbound keypresses, but 
that's not a huge amount of logs. A typical .xsession-errors on that 
machine has less than or a few hundred lines of content.

Logging the inode numbers reveals back-and-forth renameing of 
.xsession-errors and .xsession-errors.old:


     11 -rw------- 1 madroach users 5,0K  4. Nov 16:50 .xsession-errors
126604 -rw------- 1 madroach users  11K  4. Nov 15:03 .xsession-errors.old

120042 -rw------- 1 madroach users 3,2K  4. Nov 16:51 .xsession-errors
     11 -rw------- 1 madroach users 5,5K  4. Nov 16:51 .xsession-errors.old

     11 -rw------- 1 madroach users 3,2K  4. Nov 16:54 .xsession-errors
120042 -rw------- 1 madroach users 4,4K  4. Nov 16:52 .xsession-errors.old

118708 -rw------- 1 madroach users 3,0K  4. Nov 16:55 .xsession-errors
     11 -rw------- 1 madroach users 4,2K  4. Nov 16:55 .xsession-errors.old


Thanks for you efforts,

Christopher

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: nilfs_readdir: bad page in #

[Christopher Zimmermann]

On Tue, Nov 04, 2025 at 05:04:18PM +0100, Christopher Zimmermann wrote:

… and it hit again. This time not only .xsession-error, but two inodes:

Nov 04 17:30:52 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_readdir: bad page in #23280
Nov 04 17:30:57 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=112670)
Nov 04 17:31:07 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=112670)
Nov 04 17:34:44 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=112670)
Nov 04 17:34:53 merari.gmerlin.de kernel: NILFS error (device nvme0n1p5): nilfs_bmap_lookup_contig: broken bmap (inode number=126553)

find ~/ -inum 112670 -o -inum 126553
/home/madroach/.mozilla/firefox/jlon54e9.vanilla/storage/default/https+++web.whatsapp.com/idb/3166453069wcaw.sqlite-wal
/home/madroach/.xsession-errors.old

Well, restoring backups is mostly routine now :)


Christopher

Re: nilfs_readdir: bad page in #

[Hideki EIRAKU]

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