On Thu, 22 Oct 2015, Jan Kara wrote: > Date: Thu, 22 Oct 2015 11:10:17 +0200 > From: Jan Kara <jack@xxxxxxx> > To: linux-ext4@xxxxxxxxxxxxxxx > Cc: fstests@xxxxxxxxxxxxxxx > Subject: Test ext4/001 > > Hi, > > I've checked why test ext4/001 fails for me with DAX and after some > investigation I've realized that the test assumes that > extent_max_zeroout_kb is 32 KB and thus unwritten extent will get converted > to written as a whole and not split. With DAX that doesn't happen (because > of difference between EXT4_GET_BLOCKS_ flags passed in writeback path and > DAX write path) and so the result differs. > > So I was wondering how to best fix this. Either we could switch > extent_max_zeroout_kb to 0 to make the result same (but that has a slight > disadvantage that we would lose testing of the zeroout logic) or we could > increase file size so that zeroout doesn't trigger or something else? > Anyone has some idea? > > Honza I'd rather still keep the test to exercise the zeroout logic, because we've already had problems there and they may occur in the future as well. The easiest solution would be to create new test with zeroout turned off and skip the old test for DAX and keep the current test as it is. Thanks! -Lukas -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
