Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: regression, can't mount subvol if default subvol is changed
Date: Tue, 15 Oct 2013 22:50:19 +0200	[thread overview]
Message-ID: <20131015205019.GO5787@twin.jikos.cz> (raw)
In-Reply-To: <4D0EBD9B-30A2-44CB-89E2-CD028BECF1C2@colorremedies.com>

On Tue, Oct 15, 2013 at 01:23:44PM -0600, Chris Murphy wrote:
> After changing the default subvolume, I can't mount a nested subvolume
> with a correct relative pathname to the default subvolume; it can only
> be mounted by absolute path or subvolid.

The path to subvol= is always taken as absolute, no matter if the path
starts with / or not.

david

  parent reply	other threads:[~2013-10-15 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 19:23 regression, can't mount subvol if default subvol is changed Chris Murphy
2013-10-15 19:32 ` Chris Murphy
2013-10-15 20:06 ` Chris Murphy
2013-10-15 20:50 ` David Sterba [this message]
2013-10-15 20:58   ` Chris Murphy
2013-10-15 21:48     ` David Sterba
2013-10-15 21:52       ` Chris Murphy

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=20131015205019.GO5787@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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