From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: 3.13.5 kernel hangs some processes with btrfs
Date: Mon, 24 Feb 2014 07:29:58 +0000 (UTC) [thread overview]
Message-ID: <pan$2c66d$b9df9232$d5e4e0c4$992cc0f6@cox.net> (raw)
In-Reply-To: 20140224065847.GE15937@merlins.org
Marc MERLIN posted on Sun, 23 Feb 2014 22:58:47 -0800 as excerpted:
> On Mon, Feb 24, 2014 at 06:42:30AM +0000, Duncan wrote:
>> [S]ee 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.
That was a bit eye opening for me too. =:^)
> Yep, I cleared the stats, and that part is back to ok, thanks.
=:^)
> 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 in a way that affects smbd, but the array feels ok
> otherwise, weird...)
>
> [ 1332.548370] INFO: task smbd:21882 blocked for more than 120 seconds.
> [ 1332.587455] Not tainted 3.13.5-ia32-i915-preempt-20140216 #1
> [ 1332.625478] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
I've not seen anything like that here, but there are several kernel
3.13/3.14-rc reports of similar behavior on the list.
>From what I've seen reported, the problem /might/ be large-internal-write-
file related, multi-gig vm images, database files, etc, actively being
written, the sort of thing NOCOW *SHOULD* fix, at least in the absence of
frequent snapshots, but in at least one case, NOCOW had been properly
activated before the file content was written and the user was NOT doing
major snapshotting of any kind, so that rules out those triggers.
So I've no idea, except that in every reported case I've seen, people did
have large VMs or the like going as well, so that's a possible connection
despite the above.
Hopefully the devs are having more success at assembling this puzzle than
I am, but I've no suggestions for fixing it ATM, except the possibility
of putting your VMs, etc, on a dedicated non-btrfs filesystem for the
time being, assuming of course that apparent connection is a valid one.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-02-24 7:30 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
2014-02-24 7:29 ` Duncan [this message]
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='pan$2c66d$b9df9232$d5e4e0c4$992cc0f6@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.