From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>,
"Janos Toth F." <toth.f.janos@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: deleted subvols don't go away?
Date: Mon, 28 Aug 2017 10:07:01 +0200 [thread overview]
Message-ID: <1503907621.1671.5.camel@scientia.net> (raw)
In-Reply-To: <cab790fa-22f7-b05d-b18e-000c7d1a81cd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
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.
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2017-08-28 8:07 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 [this message]
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=1503907621.1671.5.camel@scientia.net \
--to=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).