From: Jan Kiszka <jan.kiszka@siemens.com>
To: linux-btrfs@vger.kernel.org
Cc: aaron@merfinllc.com
Subject: Removal of snapshots (and subvolumes)
Date: Mon, 15 Jun 2009 18:54:30 +0200 [thread overview]
Message-ID: <4A367CC6.1000302@siemens.com> (raw)
Hi,
obviously btrfs is yet lacking any means to delete snapshots and
subvolumes, well, at least their names (I read something about deleting
their content...). We wanted to start playing with circular snapshots
over btrfs driven by an application, so this limitation is a bit unhandy
- even if everything is highly experimental here anyway.
Browsing the archive, I found Aaron's first patches to fill this gap.
What happened to them? Besides likely a few remaining bugs, the biggest
seems to have been some lacking references in btrfs' tree roots. Did
this situation change meanwhile? What is the schedule for this feature?
If it's just lacking someone to pick up already existing bits and bring
them in shape, I could offer a hand. Just hacking on btrfs with broader
scope is currently not possible.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next reply other threads:[~2009-06-15 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 16:54 Jan Kiszka [this message]
2009-06-15 18:19 ` Removal of snapshots (and subvolumes) Josef Bacik
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=4A367CC6.1000302@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aaron@merfinllc.com \
--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