On Sun, May 08, 2016 at 04:12:59PM +0200, Issa Gorissen wrote: > Hello, > > After I have upgraded my htpc from openSuse 12.3 running kernel > 3.7.10 to openSuse Tumbleweed running kernel 4.5.2; I am unable to > mount my XFS filesystem anymore. .... > Avail Dev Size : 5860529896 (2794.52 GiB 3000.59 GB) > Array Size : 2930264896 (2794.52 GiB 3000.59 GB) > Used Dev Size : 5860529792 (2794.52 GiB 3000.59 GB) > Super Offset : 5860530160 sectors > Unused Space : before=0 sectors, after=344 sectors Both devices are reporting 344 unused sectors. Which may be important, because.... ..... > tv:/ # xfs_db /dev/md0 > xfs_db: error - read only 0 of 512 bytes ... something is wrong with the RAID device for this error to be emitted. XFS checks to see if it can access the last sector of the filesystem before it starts using it, and this is indicative of a that read being beyond the end of the device. > tv:/ # mount -t xfs /dev/md0 /data > mount: /dev/md0: can't read superblock > > dmesg outputs > > > [ 5525.861750] SGI XFS with ACLs, security attributes, realtime, no > debug enabled > [ 5525.862231] attempt to access beyond end of device > [ 5525.862232] md0: rw=32, want=5860529904, limit=5860529792 > [ 5525.862234] XFS (md0): last sector read failed Yup, the kernel also emits the same error on the same check - most likely during your upgrade the MD RAID device has changed size and is now 112 sectors smaller than before, hence the filesystem will refuse to mount. > Any pointers to fix this ? It seems the disks still contains a XFS > filesystem but for some reason, I cannot access it. Unlikely to be an XFS problem, more likely a MD device/upgrade issue. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
