On Wed, Nov 08, 2017 at 12:56:36PM -0800, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > It turns out that we only started zeroing a new da btree node's block > header on v5 filesystems. Prior to that, we just wouldn't set anything > at all, which means that the pad field never got set and would retain > whatever happened to be in memory. > > Therefore, we can only check the pad for zeroness on v5 filesystems. > shared/006 on a v4 filesystem exposes this scrub bug. > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> looks good. Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx> -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
