Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Justin Brown <justin.brown@fandingo.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Fwd: Deleting a Subvol from a Cancelled Btrfs-Send
Date: Thu, 2 Oct 2014 07:53:02 +0100	[thread overview]
Message-ID: <20141002065302.GF11747@carfax.org.uk> (raw)
In-Reply-To: <CAKZK7uwWDQa_7LThjW_58+DpNQogkepuwvPhg-9bzsgyQjn14Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]

On Thu, Oct 02, 2014 at 12:05:39AM -0500, Justin Brown wrote:
> I'm experimenting with btrfs-send. Previously (2014-09-26), I did my
> first btrfs-send on a subvol, and that worked fine. Today, I tried to
> send a new snapshot. Unfortunately, I realized part way through that I
> forgot to specify the parent to only send a delta, and killed the send
> with ^C.
> 
> On the destination, I'm left with:
> 
> ~$ sudo btrfs subvol list /var/media/backups/venus/home/
> ID 2820 gen 57717 top level 5 path media
> ID 2821 gen 57402 top level 5 path ovirt
> ID 4169 gen 57703 top level 2820 path media/backups/venus/home
> ID 4170 gen 57575 top level 4169 path home-2014-09-26
> ID 4243 gen 57707 top level 4169 path home-2014-10-01
> 
> Home-2014-10-01 was the partial send that was cancelled. I figured
> that I could delete this partial subvol and try again.
> 
> ~$ sudo btrfs subvol del home-2014-10-01
> Transaction commit: none (default)
> ERROR: error accessing 'home-2014-10-01'

   If you're not doing this from /var/media/backups/venus/home/ it
won't succeed. You need to specify (either via a relative path or an
absolute one) where the subvol is, not just what its name is.

   (Consider what happens if you have two filesystems, each with a
home-2014-09-26 subvol.)

   Hugo.

> Obviously, trying to delete the subvol directory fails too:
> 
> ~$ sudo rm -rf /var/media/backups/venus/home/home-2014-10-01/
> rm: cannot remove ‘/var/media/backups/venus/home/home-2014-10-01/’:
> Operation not permitted
> 
> Is there anyway to delete this partial subvol?
> 
> Thanks,
> Justin

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
           --- All hope abandon,  Ye who press Enter here. ---           

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

  reply	other threads:[~2014-10-02  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKZK7uzNJWSQAmaem4eZj-dcSJOvmT=-Mn53rjCbb=fNY9zEhw@mail.gmail.com>
2014-10-02  5:05 ` Fwd: Deleting a Subvol from a Cancelled Btrfs-Send Justin Brown
2014-10-02  6:53   ` Hugo Mills [this message]
2014-10-02  7:44     ` Justin Brown

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=20141002065302.GF11747@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=justin.brown@fandingo.org \
    --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