From: Simon King <simon.king@uni-koeln.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: How to delete this snapshot, and how to succeed with balancing?
Date: Sat, 31 Oct 2015 21:56:10 +0100 [thread overview]
Message-ID: <56352AEA.7040907@uni-koeln.de> (raw)
In-Reply-To: <20151031183337.GG21103@carfax.org.uk>
Hi!
Am 31.10.2015 um 19:33 schrieb Hugo Mills:
>> I combined the two, since -dlimit on its own won't work:
>>
>> linux-va3e:~ # btrfs balance start -dlimit=2 /
>> ERROR: error during balancing '/' - No space left on device
>> There may be more info in syslog - try dmesg | tail
>
> And this is with a filesystem that's not fully allocated?
> (i.e. btrfs fi show indicates that used and total are different for
> each device). If that's the case, then you may have hit a known but
> unfixed bug to do with space allocation.
linux-va3e:~ # btrfs fi show
Label: none uuid: 656dc65f-240b-4137-a490-0175717dd7fa
Total devices 1 FS bytes used 13.71GiB
devid 1 size 20.00GiB used 16.88GiB path /dev/sda2
btrfs-progs v4.0+20150429
Is there a manual work-around?
>> Can I do this in the running system? Or would that only be an option
>> during upgrade of openSuse Harlequin to Tumbleweed/Leap? Or even worse:
>> Only an option after nuking the old installation and installing a new
>> one from scratch?
>
> You'd have to recreate the FS, so it's a matter of a reinstall, or
> nuking it and restoring from your backups.
OK. So, I'll try to find out whether it is better to move on to
Tumbleweed or to Leap (btw, I found out that the latter is based on the
4.1 kernel).
Best regards,
Simon
next prev parent reply other threads:[~2015-10-31 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 15:26 How to delete this snapshot, and how to succeed with balancing? Simon King
2015-10-31 16:41 ` Hugo Mills
2015-10-31 17:31 ` Simon King
2015-10-31 18:33 ` Hugo Mills
2015-10-31 20:56 ` Simon King [this message]
2015-10-31 22:45 ` Henk Slager
2015-10-31 22:51 ` Hugo Mills
2015-11-01 3:05 ` Duncan
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=56352AEA.7040907@uni-koeln.de \
--to=simon.king@uni-koeln.de \
--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).