Re: Mount failure with 5.2.7 but mounts with 5.1.4

[Nikolay Borisov <nborisov@suse.com>]

On 10.08.19 г. 18:54 ч., Peter Chant wrote:
> I attempted update an i5 machine today with kernel 5.2.7.  Unfortunately
> I could not mount the file system.  However, reverting the kernel back
> to 5.1.4 allowed it to mount with no issue.
> 
> This issue is not critical to me, machine boots with older kernel, I
> have a backup and the machine is only lightly used anyway.  However, I
> wonder whether this info is useful to anyone?
> 
> I have a spare ext4 root partition on the hard drive of the affected
> machine, so I booted to that, with 5.2.7, and got the following behaviour.
> 
> dmesg:
> 
> [   55.139154] BTRFS: device fsid 5128caf4-b518-4b65-ae46-b5505281e500
> devid 1 transid 66785 /dev/sda4
> [   55.139623] BTRFS info (device sda4): disk space caching is enabled
> [   55.813959] BTRFS critical (device sda4): corrupt leaf: root=5
> block=38884884480 slot=1 ino=45745394, invalid inode generation: has
> 18446744073709551492 expect [0, 66786]

It seems you have triggered one of the enhanced checks. Looks like the
generation (i.e transaction id) of inode 45745394 seems to be larger
than the inode of the super block. This doesn't make sense. Looking at
the number of this inode it seems to have overflown.


A possible work around will be to copy the file that this inode
describes and delete the original(corrupted one) then your fs should be
mountable on the newer kernel.

> [   55.817296] BTRFS error (device sda4): block=38884884480 read time
> tree block corruption detected
> [   55.817342] BTRFS warning (device sda4): failed to read fs tree: -5
> [   55.834802] BTRFS error (device sda4): open_ctree failed
> 
> /var/log/messages:
> Aug 10 11:59:05 retreat dbus[903]: [system] Activating service
> name='org.freedesktop.PolicyKit1' (using servicehelper)
> Aug 10 11:59:05 retreat polkitd[975]: started daemon version 0.105 using
> authority implementation `local' version `0.105'
> Aug 10 11:59:05 retreat dbus[903]: [system] Successfully activated
> service 'org.freedesktop.PolicyKit1'
> Aug 10 11:59:31 retreat kernel: [   55.139154] BTRFS: device fsid
> 5128caf4-b518-4b65-ae46-b5505281e500 devid 1 transid 66785 /dev/sda4
> Aug 10 11:59:31 retreat kernel: [   55.139623] BTRFS info (device sda4):
> disk space caching is enabled
> 
> uname -a:
> Linux retreat 5.2.7 #1 SMP Wed Aug 7 23:53:42 BST 2019 x86_64 Intel(R)
> Core(TM) i5-4430 CPU @ 3.00GHz GenuineIntel GNU/Linux
> 
> Rebooting with 5.1.4 showed no problems.
> 
> 
> A very similar kernel, with AMD rather than Intel processor options, is
> running on the Ryzen machine I am typing this on.  I did have my hdd
> file system seem to hang, but not sure if that is related.
> 
> I have not tried the intel kernel on my laptop, but the laptop is a lot
> older, as it is a core2duo.
> 
> Seems a bit odd to me that 5.2.7 should show such an issue but 5.1.4 be
> OK with it.
> 
> Pete
> 
>