On Mon, Apr 2, 2018 at 9:24 AM, Filipe Manana <[email protected]> wrote: > On Thu, Mar 29, 2018 at 7:55 PM, Jayashree Mohan > <[email protected]> wrote: >> Hi Filipe, >> >> I tried running the xfstest above on kernel 4.15.0 and I haven't been >> able to hit the bug. The xfstest passes clean for me. I compared the >> btrfs-debug-tree in my case with the one attached by Eryu, and I see I >> do not have any xattr as he does. However, for every run of the >> xfstest, the extent tree info that I get from btrfs-debug-tree has >> varying number of items in the first leaf node. (I have attached two >> dump files for your reference.) >> >> I also tried changing the offset at which fpunch is performed to match >> the offset of the last extent in the first leaf of the extent tree - >> however the md5 before and after crash was the same. >> >> Could you give more details on this? > > You are getting extents smaller then 256Kb, because writeback is being > triggered by the kernel (likely due to memory pressure). > The second version of the test uses direct IO instead to avoid that. > Thanks.
Thanks for the clarification. I am able to reproduce the bug with the new version of the test that uses direct writes. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
