From: Eric Sandeen <sandeen@redhat.com>
To: bo.li.liu@oracle.com, Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BUGS: bogus out of space reported when mounted raid1 degraded, btrfs replace failure, then oops
Date: Tue, 22 Jul 2014 23:16:14 -0500 [thread overview]
Message-ID: <53CF370E.1090707@redhat.com> (raw)
In-Reply-To: <20140723033649.GB4955@localhost.localdomain>
On 7/22/14, 10:36 PM, Liu Bo wrote:
> On Tue, Jul 22, 2014 at 09:28:52PM -0600, Chris Murphy wrote:
>>
>> On Jul 22, 2014, at 8:52 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>>
>>> This one (your bug #4) was likely caused by:
>>>
>>> commit 99994cde9c59c2b8bb67d46d531b26cc73e39747
>>> Author: Anand Jain <Anand.Jain@oracle.com>
>>> Date: Tue Jun 3 11:36:00 2014 +0800
>>>
>>> btrfs: dev delete should remove sysfs entry
>>>
>>> and hopefully fixed by:
>>>
>>> commit 0bfaa9c5cb479cebc24979b384374fe47500b4c9
>>> Author: Eric Sandeen <sandeen@redhat.com>
>>> Date: Mon Jul 7 12:34:49 2014 -0500
>>>
>>> btrfs: test for valid bdev before kobj removal in btrfs_rm_device
>>
>> OK good. Hopefully the first one is reverted or the second one is accepted before 3.16 is released, replace appears to be broken at the moment.
>>
>
> Looks that they are not the same one, since you didn't use a btrfs_rm_device,
Oh, you're right - I'm sorry, I didn't look closely enough.
-Eric
next prev parent reply other threads:[~2014-07-23 4:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 1:34 BUGS: bogus out of space reported when mounted raid1 degraded, btrfs replace failure, then oops Chris Murphy
2014-07-23 1:52 ` Chris Murphy
2014-07-23 2:36 ` [BUG] bogus out of space reported when mounted raid1 degraded Chris Murphy
2014-07-23 5:24 ` Duncan
2014-07-24 1:13 ` Chris Murphy
2014-07-24 8:15 ` Duncan
2014-07-23 2:52 ` BUGS: bogus out of space reported when mounted raid1 degraded, btrfs replace failure, then oops Eric Sandeen
2014-07-23 3:28 ` Chris Murphy
2014-07-23 3:36 ` Liu Bo
2014-07-23 4:03 ` Chris Murphy
2014-07-23 4:16 ` Eric Sandeen [this message]
2014-07-23 3:01 ` Liu Bo
2014-07-23 3:21 ` Chris Murphy
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=53CF370E.1090707@redhat.com \
--to=sandeen@redhat.com \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.