From: Adam Borowski <kilobyte@angband.pl>
To: Chris Mason <clm@fb.com>
Cc: Gabriel C <nix.or.die@gmail.com>,
linux-btrfs@vger.kernel.org, quwenruo@cn.fujitsu.com
Subject: Re: A lot warnings in dmesg while running thunderbird
Date: Fri, 8 Jul 2016 23:47:11 +0200 [thread overview]
Message-ID: <20160708214711.GA10544@angband.pl> (raw)
In-Reply-To: <20160708182116.GA30214@angband.pl>
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.
next prev parent reply other threads:[~2016-07-08 21:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 10:24 A lot warnings in dmesg while running thunderbird Gabriel C
2016-07-07 19:21 ` Chris Mason
2016-07-08 9:57 ` Gabriel C
2016-07-08 12:41 ` Chris Mason
2016-07-08 14:05 ` Gabriel C
2016-07-08 15:02 ` Gabriel C
2016-07-08 16:02 ` Chris Mason
2016-07-08 18:21 ` Adam Borowski
2016-07-08 21:47 ` Adam Borowski [this message]
2016-07-08 18:23 ` Duncan
2016-07-11 5:58 ` Chandan Rajendra
2016-07-11 10:51 ` Chris Mason
2016-07-19 11:05 ` Chris Mason
2016-07-20 0:11 ` Gabriel C
2016-07-20 13:50 ` Chris Mason
2016-07-20 17:50 ` Gabriel C
2016-07-21 12:56 ` Chris Mason
2016-07-21 21:25 ` Gabriel C
2016-07-22 0:53 ` Adam Borowski
2016-07-25 0:36 ` Dave Chinner
2016-08-01 15:23 ` Chris Mason
2016-07-15 19:35 ` Chris Mason
2016-07-15 21:08 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160708214711.GA10544@angband.pl \
--to=kilobyte@angband.pl \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--cc=quwenruo@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).