On Tue, Feb 23, 2016 at 02:25:38PM +0200, Alex Lyakas wrote: > Hi Dave, > > Below is a detailed reproduction scenario of the problem. Can you package this for xfstests and send to fstests@xxxxxxxxxxxxxxx, please? > No > snapshots involved, only XFS. The scenario is performed on a VM, > running kernel 3.18.19. And a current kernel (e.g. 4.5-rc5) behaves how? > 9) mount > # mount -o sync /dev/mapper/xfs_base /mnt/xfs/ > > Kernel panics with [2]. It tried to read a buffer beyond the current end of filesystem that log recoery knows about. Given the on-disk superblock had not been updated by the growfs operation, this should have been detected by _xfs_buf_find() and errored out, not tried to look up a per-ag structure that is beyond the current end of filesystem. i.e. the code I pointed out in my previous email failed to detect the situation is it supposed to be protecting against. Why did that "block beyond the end of the filesystem" detection fail? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
