From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC errors during raid1 rebalance
Date: Mon, 3 Mar 2014 18:16:01 +0000 (UTC) [thread overview]
Message-ID: <pan$b5b02$85505b$f53ee629$e32b9776@cox.net> (raw)
In-Reply-To: DF16C10AFF7F394A8C8A09C9405478890BCBE534@EXHOST.stardatecomputer.com
Mike Russo posted on Mon, 03 Mar 2014 17:23:43 +0000 as excerpted:
> I'm trying to convert a disk from single (/dev/sdc1) to RAID1
> (dev/sdd1), and the filesystem was previously ext4 but the conversion
> seemed to go just fine, and I have no snapshots. System and metadata
> convert, and almost all my data converts, but there are 70 stubborn GB
> (14 blocks of 5GB each) that refuse to convert and I get ENOSPC errors
> when trying to reallocate them.
While I created entirely new btrfs filesystems here and copied everything
over rather than converting so I've not had personal experience with the
conversion process...
The wiki[1] says[2] that while the conversion process uses the same data
blocks for both ext3/4 and btrfs, it duplicates the ext3/4 metadata,
creating a new btrfs copy (or two, for default metadata dup mode),
leaving the original ext3/4 copy untouched. Btrfs modifications are then
done using standard btrfs COW (copy-on-write) methods, so the ext3/4
data, while originally shared, remains untouched as well.
That allows rollback if desired, but does tie up some some space with the
automatically created btrfs "snapshot" that contains the ext3/4 metadata
and untouched data. While you say you have no snapshots, it's unclear
whether you mean none that you've created /since/ the conversion, but you
didn't delete that original snapshot so still have it, or whether you
deleted that automatically created btrfs snapshot of the old ext3/4
filesystem and simply didn't specifically mention it.
I'm guessing that it's the former, and that btrfs is refusing to balance/
restripe that old ext3/4 snapshot albeit with a very confusing ENOSPC
error message, since it'd kill the old ext3/4 filesystem and you could no
longer rollback.
If that's the case, the page at [2] explains how you get rid of the old
ext3/4 snapshot once you're sure you won't be rolling back and thus no
longer need it. With a bit of luck, that's all you need to do, and after
deleting that, you can finish your balance/restripe. =:^)
If you've already btrfs subvol delete-ed the ext2_saved subvolume, or if
you hadn't but doing so doesn't solve the problem, well, I went for the
low-hanging-fruit solution but obviously that wasn't it. =:^( Hopefully
someone else can help further.
---
[1] https://btrfs.wiki.kernel.org Bookmark it! =:^)
[2] https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3
--
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-03-03 18:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 17:23 ENOSPC errors during raid1 rebalance Mike Russo
2014-03-03 18:16 ` Duncan [this message]
2014-03-03 18:24 ` Michael Russo
2014-03-03 18:48 ` Chris Murphy
2014-03-03 19:24 ` Michael Russo
2014-03-03 20:41 ` Chris Murphy
2014-03-03 20:50 ` Michael Russo
2014-03-03 21:02 ` Chris Murphy
2014-03-03 18:39 ` Hugo Mills
2014-03-04 15:55 ` Michael Russo
2014-03-04 17:29 ` Chris Murphy
2014-03-04 18:54 ` Michael Russo
2014-03-04 19:30 ` Chris Murphy
2014-03-05 0:27 ` Mike Russo
2014-03-05 3:32 ` Chris Murphy
2014-03-05 22:13 ` Michael Russo
2014-03-06 7:41 ` Duncan
2014-03-07 1:13 ` Michael Russo
2014-03-07 8:02 ` Hugo Mills
2014-03-07 10:18 ` Duncan
2014-03-07 14:17 ` Mike Russo
2014-03-08 1:46 ` Mike Russo
2014-03-05 4:08 ` Chris Murphy
2014-03-05 22:13 ` Michael Russo
2014-03-06 17:07 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2014-03-13 22:38 Eugene Crosser
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$b5b02$85505b$f53ee629$e32b9776@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.