generic/650 leaves error messages in system log (~50% probability)

[dubeyko]

sudo ./check generic/650
FSTYP -- nilfs2
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 6.19.0-rc1+ #44 SMP PREEMPT_DYNAMIC Mon Dec 22 15:39:00 PST 2025
MKFS_OPTIONS -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

generic/650 57s ... 57s
Ran: generic/650
Passed all 1 tests

2025-12-23T17:14:32.281920-08:00 hfsplus-testing-0001 kernel: message repeated 2 times: [ NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=265)]
2025-12-23T17:14:32.281923-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=264)
2025-12-23T17:14:32.281939-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=265)
2025-12-23T17:14:32.282930-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
2025-12-23T17:14:32.283014-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=264)
2025-12-23T17:14:32.283015-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
2025-12-23T17:14:32.283016-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
2025-12-23T17:14:32.283017-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=265)
2025-12-23T17:14:32.283017-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=261)
2025-12-23T17:14:32.283917-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=257)
2025-12-23T17:14:32.283933-08:00 hfsplus-testing-0001 kernel: NILFS error (device loop50): nilfs_bmap_lookup_contig: broken bmap (inode number=261)