From: Hugo Mills <hugo@carfax.org.uk>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>,
"Janos Toth F." <toth.f.janos@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: deleted subvols don't go away?
Date: Mon, 28 Aug 2017 12:16:12 +0000 [thread overview]
Message-ID: <20170828121612.GA30990@carfax.org.uk> (raw)
In-Reply-To: <83c6b0bb-a120-e0e3-dfc3-069ede63906f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Mon, Aug 28, 2017 at 03:03:47PM +0300, Nikolay Borisov wrote:
>
>
> On 28.08.2017 11:07, Christoph Anton Mitterer wrote:
> > Thanks...
> >
> > Still a bit strange that it displays that entry... especially with a
> > generation that seems newer than what I thought was the actually last
> > generation on the fs.
>
> Snapshot destroy is a 2-phase process. The first phase deletes just the
> root references. After it you see what you've described. Then, later,
> when the cleaner thread runs again the snapshot's root item is going to
> be deleted for good and you no longer will see it.
It's worth noting also that if the subvol is still used in some way
(still mounted, nested subvol, processes with CWD in it, open files),
then it won't be cleaned up until the usage stops. Basically the same
behaviour as deleting a file. This could also explain the more recent
than expected generation values.
Hugo.
--
Hugo Mills | "Big data" doesn't just mean increasing the font
hugo@... carfax.org.uk | size.
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-08-28 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 17:15 deleted subvols don't go away? Christoph Anton Mitterer
2017-08-28 3:43 ` 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 [this message]
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=20170828121612.GA30990@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=n.borisov.lkml@gmail.com \
--cc=toth.f.janos@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 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).