Your message dated Mon, 28 Apr 2025 19:49:01 +0200
with message-id <5f3c663d-9eb2-492c-bd98-5ec4469e4...@debian.org>
and subject line Re: Bug#1083220: Please close BR
has caused the Debian Bug report #1083220,
regarding Metadata corruption detected, fatal error -- error couldn't iget
realtime bitmap inode, err = 117
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1083220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfsprogs
Version: 6.10.1-1
After upgrading to 6.10 linux image, the boot process stops telling me
I should do a disk fs check. The xfs_repair though, gives me the above
title message. Booting the older 6.9.10 kernel works fine.
[ 5.217166] SGI XFS with ACLs, security attributes, realtime,
quota, no debug enabled
[ 5.230086] XFS (sda3): Deprecated V4 format (crc=0) will not be
supported after September 2030.
[ 5.230461] XFS (sda3): Mounting V4 Filesystem
45a538e4-4139-40a3-a437-38b75ea4af5c
[ 5.320433] XFS (sda3): Ending clean mount
...
[ 22.241638] XFS (sda7): Mounting V4 Filesystem
f368fd33-92da-42dc-9eee-93cf3ebb4211
[ 22.388893] XFS (sda5): Ending clean mount
[ 22.446780] XFS (sda2): Ending clean mount
[ 22.470139] XFS (sda7): Ending clean mount
Also other xfs partitions can't be mounted, with the exception of a
newly created one.
It's a rather old installation (2008), incrementally updated debian/testing.
Not sure if it is related, but I noticed that updating udisks2 umounts
my /boot partition w/o remounting it. Which basically more or less
corrupts any following kernel updates. Reinstalling the linux-image,
update-grub afterwards is needed.
Also ssh connections are closed when updating udisks2. So a rather odd
thing that might point to something ...
Cheers,
Koos Vriezen
--- End Message ---
--- Begin Message ---
Thanks for updating the report.
--- End Message ---
