On Fri, Jul 08, 2016 at 08:21:16PM +0200, Adam Borowski wrote: > On Fri, Jul 08, 2016 at 12:02:35PM -0400, Chris Mason wrote: > > On 07/08/2016 11:02 AM, Gabriel C wrote: > > > [btrfs_destroy_inode again] > > > Can you please run the attached test program: > > > > gcc -o short-write short-write.c -lpthread > > ./short-write some-new-file-on-btrfs > > > > I want to see if you're triggering the same problem we've tried to fix, or > > something else. > > Looks like same, 4.6.3: [...] > ... and sda1 is goes ro. > Single device, noatime,compress=lzo,ssd. > > It's somewhat puzzling that back in the day applying 56244ef15 stopped this > reproducer for me, yet somehow it triggers again.
The above on 4.6.3 triggered pretty immediately. I then compiled fresh 4.7-rc6+ (today's Linus' master), which did trigger only after a lot of time and effort. First I tried on freshly formatted 2TB spinning rust, no luck. Then on 1GB rust, almost full of a mixture of crap. Then on my regular ssd -- it survived an hour of so with little concurrent use, then went boom only late of a kernel compile on that filesystem. Same backtrace. -- An imaginary friend squared is a real enemy. -- 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
