From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS cannot remove empry directory pretending it is not empty
Date: Fri, 21 Aug 2015 10:19:54 +0200 [thread overview]
Message-ID: <2017000.AEG9PyVY17@zafu> (raw)
Hello,
BTRFS refuses to remove an empty dir and pretends it is not empty (and there
is no BTRFS subvolume involved in there...)
# uname -r
4.1.5-1-ARCH
# ls -alnR .dropbox-old/
.dropbox-old/:
total 0
drwx------ 1 1000 1000 18 21 août 09:59 .
drwxr-x--- 1 1000 1000 2624 21 août 10:09 ..
drwx------ 1 1000 1000 416 21 août 09:59 instance1
.dropbox-old/instance1:
total 0
drwx------ 1 1000 1000 416 21 août 09:59 .
drwx------ 1 1000 1000 18 21 août 09:59 ..
# rm -rf .dropbox-old
rm: cannot remove ‘.dropbox-old/instance1’: Directory not empty
# ls -alnR .dropbox-old/instance1/
.dropbox-old/instance1/:
total 0
drwx------ 1 1000 1000 416 21 août 09:59 .
drwx------ 1 1000 1000 18 21 août 09:59 ..
# rm -rf .dropbox-old/instance1/
rm: cannot remove ‘.dropbox-old/instance1/’: Directory not empty
How could this be fixed ?
TIA, kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org>
next reply other threads:[~2015-08-21 8:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 8:19 Swâmi Petaramesh [this message]
2015-08-21 8:47 ` BTRFS cannot remove empry directory pretending it is not empty 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
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=2017000.AEG9PyVY17@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;
as well as URLs for NNTP newsgroup(s).