linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Fwd: unable to delete files after kernel upgrade from 3.8.10 to 3.12
Date: Thu, 7 Nov 2013 14:04:20 +0000 (UTC)	[thread overview]
Message-ID: <pan$c4dc0$c3d4cfda$6d328ddf$2900aea8@cox.net> (raw)
In-Reply-To: CAMajw1O4-zrfxYgxeZaTNwtgY-_zTUpBbiLSExkcmwuyU5x+mw@mail.gmail.com

Bartosz Kulicki posted on Thu, 07 Nov 2013 11:43:15 +0000 as excerpted:

> FWIW - just before nuking the fs I have added a 3GB loopback device to
> btrfs.
> 
> This restored ability to delete the files but I could not remove the
> loopback after deleting some large files (if I remember correctly error
> I got was "block device required")

Having read the wiki and the list but not having (yet) gotten into that 
sort of situation myself, I'm following this with some interest, and
was just about to ask if you'd tried that.

OK, so you added the loop device and were then able to do deletes but 
afterward could not delete the device...

The device thus obviously added some room for the filesystem to work, so 
you could delete files.  After that file-delete, did you then try a 
balance again?

Because as documented, and as demonstrated by the initial now allowed 
file-delete, that should have given you just enough extra metadata space 
to get you out of the jam, allowing a balance to finish, which in theory 
at least would have freed up enough space due to the compaction of the 
balance, to then finally do a proper btrfs device delete on the temporary 
loop device.

But without that last balance attempt after the loop add and successful 
file delete, we'll never know if the temporary loop device could have 
then been successfully btrfs device deleted or not.

Which is a bit frustrating here, since that's exactly the bit omitted 
from your posting what you tried, but what I'm counting on to get me out 
of a similar jam, should I ever get in it...

-- 
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


  reply	other threads:[~2013-11-07 14:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMajw1N4bqFyHA4V8SkEzQFZF8adN0xQDShRq7bC2Of+nxsJGA@mail.gmail.com>
2013-11-06 21:53 ` Fwd: unable to delete files after kernel upgrade from 3.8.10 to 3.12 Bartosz Kulicki
2013-11-07  8:49   ` Stefan Behrens
2013-11-07 11:33     ` Bartosz Kulicki
2013-11-07 11:43       ` Bartosz Kulicki
2013-11-07 14:04         ` Duncan [this message]
2013-11-10 13:10         ` Russell Coker
2013-11-10 15:42           ` 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='pan$c4dc0$c3d4cfda$6d328ddf$2900aea8@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 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).