Re: Mount failure with 5.2.7 but mounts with 5.1.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8/10/19 6:53 PM, Nikolay Borisov wrote:

> 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.
> 

OK, I'm not a dev so that is rather lost on me...

> 
> 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.

Thanks. I've searched how to find a file by inode number, I can try
that.  I presume I'll need to do this in 5.1.4 since 5.2.7 does not mount.







[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux