linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jogi Hofmüller" <jogi@mur.at>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs 3.16.2 does not recognize subvolumes correctly
Date: Fri, 03 Oct 2014 12:40:33 +0200	[thread overview]
Message-ID: <542E7D21.2030905@mur.at> (raw)
In-Reply-To: <542D100F.9050502@mur.at>

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

Hi all,

First of all, I am talking about btrfs-progs 3.16.2 if there was any doubt.

I did some more checking and found the following disturbing results.

I can still create snapshots of subvolumes and the default subvolume (/)
without problems.  But sending the snapshot fails with the error:

ERROR: /.SNAPSHOT doesn't belong to btrfs mount point

btrfs subvolume list -a /

ID 259 gen 21444 top level 5 path home
ID 260 gen 21443 top level 5 path var
ID 742 gen 18830 top level 5 path .SNAPSHOT
ID 743 gen 18832 top level 259 path home/.SNAPSHOT

But then again e.g.

btrfs subvolume show /home
ERROR: /home doesn't belong to btrfs mount point

All this is happening on my laptop running kernel 3.16.3. (Debian).

Interestingly enough I have another machine where only the default
subvolume makes problems but another subvolume can be snapshotted and
the snapshot send.  This machine uses kernel 3.14.15.

Please let me know what I can do to fix this.

Regards,
-- 
J.Hofmüller

ich zitiere wie Espenlaub.

https://twitter.com/TheGurkenkaiser/status/463444397678690304


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2014-10-03 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02  8:42 btrfs 3.16.2 does not recognize subvolumes correctly Jogi Hofmüller
2014-10-03 10:40 ` Jogi Hofmüller [this message]
2014-10-03 16:53   ` Omar Sandoval
2014-10-03 18:10     ` Jogi Hofmüller

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=542E7D21.2030905@mur.at \
    --to=jogi@mur.at \
    --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;
as well as URLs for NNTP newsgroup(s).