From: Sean Greenslade <sean@seangreenslade.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: Chris Murphy <lists@colorremedies.com>,
David Sterba <dsterba@suse.cz>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Post ext3 conversion problems
Date: Mon, 19 Sep 2016 11:13:41 -0400 [thread overview]
Message-ID: <20160919151341.GA1431@coach.home> (raw)
In-Reply-To: <ae8fd0d5-0d38-aa8e-0114-36ef62b1a783@cn.fujitsu.com>
On Mon, Sep 19, 2016 at 02:30:28PM +0800, Qu Wenruo wrote:
> All chunks are completed convert to DUP, no small chunk, all to its maximum
> chunk size.
> So from chunk level, nothing related to convert yet.
>
> But for extent tree, I found several extents are heavily referred to.
> Like extent 158173081600 or 183996522496.
>
> If you're not using off-band dedupe, then it's quite possible that's the
> remaining structure of convert.
I never ran any sort of dedup on this partition.
> Not pretty sure if it's related to the bug, but did you do the
> balance/defrag operation just after removing ext_save subvolume?
That's quite possible. I did it in a live boot, so I don't have the bash
history to check. I checked it just now using "btrfs subvol list -d",
and there's nothing listed. I ran a full balance after that, but the
problem remains. So whatever the problem is, it can survive a full
balance after the ext_save subvol is completely deleted.
--Sean
next prev parent reply other threads:[~2016-09-19 15:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 19:25 Post ext3 conversion problems Sean Greenslade
2016-09-16 20:23 ` Chris Murphy
2016-09-16 23:25 ` Sean Greenslade
2016-09-16 23:45 ` Chris Murphy
2016-09-17 0:03 ` Sean Greenslade
2016-09-19 2:20 ` Qu Wenruo
2016-09-19 4:12 ` Sean Greenslade
2016-09-19 6:30 ` Qu Wenruo
2016-09-19 15:13 ` Sean Greenslade [this message]
2016-09-20 2:49 ` Qu Wenruo
2016-09-20 3:39 ` Sean Greenslade
2016-09-20 5:02 ` Qu Wenruo
2016-09-20 20:51 ` Sean Greenslade
2016-09-26 2:16 ` Sean Greenslade
2016-09-26 2:37 ` Qu Wenruo
2016-09-17 2:27 ` Liu Bo
2016-09-17 4:16 ` Sean Greenslade
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=20160919151341.GA1431@coach.home \
--to=sean@seangreenslade.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.