From: Michael Russo <mike@papersolve.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC errors during raid1 rebalance
Date: Mon, 3 Mar 2014 18:24:41 +0000 (UTC) [thread overview]
Message-ID: <loom.20140303T191959-983@post.gmane.org> (raw)
In-Reply-To: pan$b5b02$85505b$f53ee629$e32b9776@cox.net
Duncan <1i5t5.duncan <at> cox.net> writes:
>
> 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.
Nope, I definitely deleted the snapshots, running btrfs sub list
gives me nothing back:
root@ossy:/usr/src/btrfs-progs# /usr/src/btrfs-progs/btrfs sub list /mymedia
root@ossy:/usr/src/btrfs-progs#
Thanks for the detailed reply though. While doing this operation I
wanted to not have any snapshots so that I needed the minimum
amount of space to do the rebalance.
But this all does seem strange right? Why the heck would it refuse
to move these 70GB and think there are 0 blocks of free space?
next prev parent reply other threads:[~2014-03-03 18:30 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
2014-03-03 18:24 ` Michael Russo [this message]
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=loom.20140303T191959-983@post.gmane.org \
--to=mike@papersolve.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