From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: 3.13.5 kernel hangs some processes with btrfs
Date: Mon, 24 Feb 2014 15:18:51 +0800 [thread overview]
Message-ID: <530AF25B.5050004@cn.fujitsu.com> (raw)
In-Reply-To: <20140224065847.GE15937@merlins.org>
On 02/24/2014 02:58 PM, Marc MERLIN wrote:
> On Mon, Feb 24, 2014 at 06:42:30AM +0000, Duncan wrote:
>> I believe there's a fix coming (a cancel that blows away the tracking
>> file if it finds it and no actual running scrub is the most obvious fix),
>> but meanwhile, see the /var/lib/btrfs/scrub.status.* files. That's where
>> scrub state is stored, and manually blowing away the appropriate file
>> should clear btrfs' memory of the aborted scrub, so you can scrub start
>> properly.
> Ah, silly me, I thought this was all in the kernel and not in userspace.
>
> Yep, I cleared the stats, and that part is back to ok, thanks.
>
> I'm not getting btrfs hang on /mnt/btrfs_pool2 after reboot, so that's good.
>
> But I'm still seeing these, albeit less often.
> Any idea what they could be linked to?
> (I have a btrs send/receive going right now, it could hanging /mnt/btrfs_pool1
I noticed scrub for /mnt/btrfs_pool1 is running more than 10000s....
Not sure if it is related to send/receive, but if you are still runing
send/receive,
just terminate it and let's see if things will become better.
Also Josef gave a patch that can speed up send/receive a lot which has been
pused into btrfs-next, you can try it.
Thanks,
Wang
> in a way that affects smbd, but the array feels ok otherwise, weird...)
>
next prev parent reply other threads:[~2014-02-24 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 6:14 3.13.5 kernel hangs some processes with btrfs Marc MERLIN
2014-02-24 6:17 ` Marc MERLIN
2014-02-24 6:27 ` Wang Shilong
2014-02-24 6:42 ` Marc MERLIN
2014-02-24 6:42 ` Duncan
2014-02-24 6:58 ` Marc MERLIN
2014-02-24 7:18 ` Wang Shilong [this message]
2014-02-24 7:29 ` Duncan
2014-02-24 17:35 ` Marc MERLIN
2014-02-25 5:31 ` 3.14rc3 kernel also " Marc MERLIN
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=530AF25B.5050004@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.org \
/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).