public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yan, Zheng" <zheng.yan@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: snapshot/subvol deletion
Date: Tue, 25 Aug 2009 22:38:01 +0800	[thread overview]
Message-ID: <4A93F749.3010708@oracle.com> (raw)

Hi,

I will send a series patches that add snapshot/subvol deletion soon.
But the way to delete snapshot/subvol is far from people's expectancy.
To delete a snapshot/subvol, we need four steps: 1) snapshot/subvol
deletion ioctl or rmdir; 2) umount; 3) btrfsck; 4) mount the fs.

The reason for this is bug in root back & forward references. In simple
terms, the bug prevents us from knowing how many places a snapshot/subvol
is referenced. So it's unsafe delete corresponding fs tree immediately
after a link to snapshot/subvol is removed.

Regards
Yan, Zheng

             reply	other threads:[~2009-08-25 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 14:38 Yan, Zheng [this message]
2009-08-25 15:03 ` snapshot/subvol deletion Chris Mason
2009-08-25 15:53   ` Josef Bacik
2009-08-25 16:04     ` Chris Mason
2009-08-27  3:47       ` Andy Lutomirski
2009-08-26  5:25   ` Yan, Zheng
2009-08-26  6:50     ` Chris Mason
2009-08-26  9:19       ` Yan, Zheng

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=4A93F749.3010708@oracle.com \
    --to=zheng.yan@oracle.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