xfs resize: primary superblock is not updated immediately
Dave Chinner
david at fromorbit.com
Thu Mar 3 15:31:08 CST 2016
On Thu, Mar 03, 2016 at 11:18:43AM +0200, Alex Lyakas wrote:
> Hello Dave,
> Thanks for the patch! I confirm that it fixes the scenario.
>
> At [1] please find all the blknos that are being used during the log
> recovery (if that's of any interest).
....
> Mar 3 11:17:41 vc-00-00-350-dev kernel: [ 68.129739]
> _xfs_buf_find: blkno=200705 eofs=204800 >m_sb.sb_dblocks=25600
> Mar 3 11:17:41 vc-00-00-350-dev kernel: [ 68.129746]
> _xfs_buf_find: blkno=200705 eofs=204800 >m_sb.sb_dblocks=25600
Where is the warning that this block is out of range?
And why didn't recovery fail at this point because the block
requested is out of range and so the buffer lookup should have
failed?
Cheers,
Dave.
--
Dave Chinner
david at fromorbit.com
More information about the xfs
mailing list