From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: deleted subvols don't go away?
Date: Sun, 27 Aug 2017 19:15:46 +0200 [thread overview]
Message-ID: <1503854146.5155.2.camel@scientia.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Hey.
Just wondered...
On a number of filesystems I've removed several subvoumes (with -c)...
even called btrfs filesystem sync afterwards... and waited quite a
while (with the fs mounted rw) until no disk activity seems to happen
anymore.
Yet all these fs shows some deleted subvols e.g.:
btrfs subvolume list -pagud /thefs
ID 5 gen 10502 parent 0 top level 0 uuid - path <FS_TREE>/DELETED
Any ideas?
btw: seems (at least) the -d option is missing from the manpages at
least until progs version 4.12
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next reply other threads:[~2017-08-27 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 17:15 Christoph Anton Mitterer [this message]
2017-08-28 3:43 ` deleted subvols don't go away? Janos Toth F.
2017-08-28 6:43 ` Nikolay Borisov
2017-08-28 8:07 ` Christoph Anton Mitterer
2017-08-28 12:03 ` Nikolay Borisov
2017-08-28 12:16 ` Hugo Mills
2017-08-28 12:18 ` Roman Mamedov
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=1503854146.5155.2.camel@scientia.net \
--to=calestyo@scientia.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).