Is there anyone who are tracking this issue? 2012/12/19 Rock Lee <[email protected]>: > Hi, > > I just try to write the testcase a few hours before. So there will be > some problems. > > Maybe you can ignore the unimplemented and the ugly parts. > > Welcome any feedback. :) > > I have uploaded the test source file to Github. Please open this link: > > > https://github.com/Zimilo/btrfs-testing-suites/blob/master/fallocate/fallocate.c > > Latest kernel commit is 752451f01c4567b506bf4343082682dbb8fb30dd in > linus git tree. > > Testing on a 20GB loop device. > > When running the second case, try to do the sync command manually at > the some time several times. Always could be reproduced. > > You will get hit the WARN_ON, dmesg will report them. > > > Except this problem, there's another bug, btrfs_fallocate doesn't > guarantee subsequent write to that range not to fail because of disk > space. > > > > 2012/12/19 Josef Bacik <[email protected]>: >> On Wed, Dec 19, 2012 at 08:12:01AM -0700, Rock Lee wrote: >>> Hi all, >>> >>> Did someone have met this problem before. When doing the tests, I hit >>> >>> the WARN_ON. Is this log make sense or someone had fixed the problem. >>> >>> If needed, I can supply the detail log and the testcase source file. >>> >>> Version: the latest codes at linus git tree. >>> >> >> If you can give me your testcase I will love you forever. Thanks, >> >> Josef
-- 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
