Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS cannot remove empry directory pretending it is not empty
Date: Fri, 21 Aug 2015 17:39:49 +0200	[thread overview]
Message-ID: <1563126.2Gc1A7GJcV@zafu> (raw)
In-Reply-To: <pan$3546e$3dbd1a66$4b200cff$9537e206@cox.net>

Hi list,

Thank you all for your replies and suggestions, please see below.

Le vendredi 21 août 2015 11:23:19 Duncan a écrit :
> AFAIK, the bug is now fixed, but for those affected, the bad-refcounts 
> remain.  I believe btrfs check should detect the problem and with
> --repair should fix it, but of course caution is urged in using --repair 
> as there's still a chance it'll do damage if there's other problems it 
> doesn't understand and thus tries to fix in the wrong way.
> 
> So I'd suggest running btrfs check, without --repair, first, and see what 
> it says.  If the only reported problems have to do with inode refcounts, 
> then (assuming your backups are current, just in case, admin's rule of 
> backups, if you don't have them, you don't care about losing the data) 
> I'd then go ahead and run it with --repair.
> 
> Of course to do that you'll have to have the filesystem unmounted, and 
> have access to a reasonably new btrfs command on the initr* or from your 
> emergency boot, if it's the root filesystem.  Could be fun... but it 
> should correct the issue.

I hadn't considered using btrfsck, as I has understood that BTRFS was 
typically supposed to be self-repairing and that btrfsck was a last-resort 
tool to be used only when the filesystem would be unmountable, and furthermore 
that using it *might* be kind of trying to do precision surgery using a 
chainsaw ;-)

But I might give it a shot, taking in account that yes, this is a subvolume of 
my root filesystem (which I would obviously prefer not to break even though I 
have backups...) and that I should seek a live distro image having a recent 
kernel and BTRFS tools...

In the past, the output of btrfsck was completely meaningless to me, so I'm 
not sure if I could figure out anything from it (and understand if I'd better 
try the repair option or not...) by running it a first time.

Even though I have backups, I don't have too much time and desire for breaking 
and restoring my system, and I'd rather keep this "dead" directory forever 
rather than taking any risk of frying my root FS...

Kind regards.

-- 
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E


  reply	other threads:[~2015-08-21 15:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  8:19 BTRFS cannot remove empry directory pretending it is not empty Swâmi Petaramesh
2015-08-21  8:47 ` Karsten Heymann
2015-08-21  9:15   ` Swâmi Petaramesh
2015-08-21  9:16     ` Roman Mamedov
2015-08-21  9:45 ` Hugo Mills
2015-08-21 11:23 ` Duncan
2015-08-21 15:39   ` Swâmi Petaramesh [this message]
2015-08-21 18:07     ` Duncan
2015-08-25  8:18   ` BTRFS cannot remove empty " Swâmi Petaramesh
2015-08-25  8:37     ` Duncan
2015-08-25 13:25       ` Swâmi Petaramesh
2015-08-25 14:03         ` Swâmi Petaramesh
2015-08-25 22:29           ` Duncan
2015-08-25 22:38             ` Hugo Mills
     [not found]             ` <9Aea1r00U2Q6ekd01Aebva>
2015-08-25 23:32               ` 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=1563126.2Gc1A7GJcV@zafu \
    --to=swami@petaramesh.org \
    --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