All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Vedran Vucic <vedran.vucic@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: illegal snapshot, cannot be deleted
Date: Fri, 13 Nov 2015 13:10:12 -0500	[thread overview]
Message-ID: <56462784.2060601@gmail.com> (raw)
In-Reply-To: <CAHTEL3m0uGWZGWUH_SLmg8TqMe4DcXU77p+S=4Aebukr1BZ-Bg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]

On 2015-11-13 12:30, Vedran Vucic wrote:
> Hello,
>
> Here are outputs of commands as you requested:
>   btrfs fi df /
> Data, single: total=8.00GiB, used=7.71GiB
> System, DUP: total=32.00MiB, used=16.00KiB
> Metadata, DUP: total=1.12GiB, used=377.25MiB
> GlobalReserve, single: total=128.00MiB, used=0.00B
>
> btrfs fi show
> Label: none  uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
>          Total devices 1 FS bytes used 8.08GiB
>          devid    1 size 18.71GiB used 10.31GiB path /dev/sda6
>
> btrfs-progs v4.0+20150429
>
Hmm, that's odd, based on these numbers, you should be having no issue 
at all trying to run a balance. You might be hitting some other bug in 
the kernel, however, but I don't remember if there were any known bugs 
related to ENOSPC or balance in the version you're running.  You might 
see if trying to re-run the balance with '-dusage=40 -musage=40' works 
correctly (I've seen cases where the first run fails, but subsequent 
ones work because the first one made some progress despite failing).
> On Fri, Nov 13, 2015 at 5:30 PM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>> On 2015-11-13 11:12, Vedran Vucic wrote:
>>>
>>> Hello,
>>>
>>> I succeeded to delete illegal snapshot with command:
>>> btrfs subvolume delete /.snapshots/741/snapshot
>>> When I have done
>>> btrfs balance / -dusage=0 -musage=0
>>> increasing value up to 4o I did not have issues.
>>> But on value 4- for-dusage= and -musage=
>>> I got message that there is no space left on disk.
>>> Do you have any advice how to manage that?
>>
>>
>> Can you post the output of 'btrfs fi df' and 'btrfs fi show' again? Both
>> should have changed after the balance, and I'd need to see what it looks
>> like now to be able to give any reasonable advice.
>>
>>



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

  parent reply	other threads:[~2015-11-13 18:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 22:11 illegal snapshot, cannot be deleted Vedran Vucic
2015-11-12 12:32 ` Austin S Hemmelgarn
2015-11-13 16:12   ` Vedran Vucic
2015-11-13 16:30     ` Austin S Hemmelgarn
2015-11-13 17:30       ` Vedran Vucic
2015-11-13 17:55         ` Henk Slager
2015-11-13 17:57           ` Vedran Vucic
2015-11-13 18:10         ` Austin S Hemmelgarn [this message]
2015-11-13 18:42           ` Hugo Mills
2015-11-13 19:40             ` Austin S Hemmelgarn
2015-11-13 19:55               ` Hugo Mills
2015-11-13 20:20                 ` Austin S Hemmelgarn
2015-11-13 21:11                 ` Duncan
2015-11-13 21:13                   ` Hugo Mills
2015-11-13 23:53                     ` Duncan
2015-11-13 20:15             ` Vedran Vucic
2015-11-13 20:18               ` Vedran Vucic

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=56462784.2060601@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=vedran.vucic@gmail.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.