From: Andrew Lutomirski <luto@mit.edu>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 2.6.37: bash is looping unkillably in btrfs
Date: Sat, 12 Feb 2011 16:29:41 -0500 [thread overview]
Message-ID: <AANLkTi=oBvsjxichNbAFGND05XG8GVMds5PwRLL5Amco@mail.gmail.com> (raw)
In-Reply-To: <20110212212249.GB19533@dhcp231-156.rdu.redhat.com>
On Sat, Feb 12, 2011 at 4:22 PM, Josef Bacik <josef@redhat.com> wrote:
> On Sat, Feb 12, 2011 at 02:53:31PM -0500, Andrew Lutomirski wrote:
>> I have two processes that are unkillable and taking about 50% of a C=
PU
>> each. =A0There is no actual I/O happening (disk light is off and the
>> disk even spun down after awhile). =A0This may or may not be related=
to
>> unmounting a filesystem. =A0(I'm not sure -- I have two btrfs
>> failesystems and I unmounted one before I noticed the problem).
>>
>> [...]
> It will finish eventually, fixes for this went into -rc4. =A0Thanks,
Any plans for -stable? (Upgrading to a -rc kernel to make a
filesystem work seems scary.)
Is it same to assume that my data is all ok? (I have a backup and I'd
like to know whether I should restore from it right now...)
--Andy
>
> Josef
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-12 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 19:53 2.6.37: bash is looping unkillably in btrfs Andrew Lutomirski
2011-02-12 21:22 ` Josef Bacik
2011-02-12 21:29 ` Andrew Lutomirski [this message]
2011-02-13 1:13 ` Josef Bacik
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='AANLkTi=oBvsjxichNbAFGND05XG8GVMds5PwRLL5Amco@mail.gmail.com' \
--to=luto@mit.edu \
--cc=josef@redhat.com \
--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 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).