linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Thursfield <sam.thursfield@codethink.co.uk>
To: Anand Jain <Anand.Jain@oracle.com>, linux-btrfs@vger.kernel.org
Cc: baserock-dev@baserock.org, johannes.hirte@datenkhaos.de,
	xavier.gnata@gmail.com, 1i5t5.duncan@cox.net
Subject: Re: Unable to mount multiple subvolumes of a single disk
Date: Mon, 15 Sep 2014 18:15:50 +0100	[thread overview]
Message-ID: <54171EC6.7040704@codethink.co.uk> (raw)
In-Reply-To: <54171711.8010107@oracle.com>

On 15/09/14 17:42, Anand Jain wrote:
>
>   Logs from Sam, tells the problem clearly.  mount is using
>   /dev/sda, but mount error message and kernel is using /dev/vda.
>
> ----------------------
> $ mount /dev/sda /home -t btrfs -o subvol=/state/home,defaults,rw,noatime
> mount: /dev/vda is already mounted or /home busy
>         /dev/vda is already mounted on /

Sorry for the confusion here. I typed in the shell commands into the log 
manually and obviously put /dev/sda when I meant /dev/vda.

I've retested with /dev/vda and the same error occurs.

> On 15/09/2014 23:13, Sam Thursfield wrote:
>> Hi!
>>
>> I'm having an issue with the 3.17rc5 kernel which prevents having
>> multiple subvolumes of the same disk mounted.
>>
>> I'm not sure exactly the cause. I thought it might be because in my
>> system the root file system is itself a subvolume of the disk I'm trying
>> to mount. But if I create a second disk image with two subvolumes, the
>> same thing occurs -- I can only mount one of them at a time.
>>
>> I've attached the output of a few commands, please let me know if you
>> want more info (I'm not subscribed to the list, please keep me in To:).
>>
>> We've bisected and found that the exact commit that changed the
>> behaviour is this one:
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b96de000bc8bc9688b3a2abea4332bd57648a49f
>>
>>
>>
>> I'm afraid I'm not familiar with the Btrfs code base and so I don't
>> understand the exact meaning of the comments in that commit.
>>
>> Thanks
>> Sam
>>


-- 
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575

      reply	other threads:[~2014-09-15 17:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 15:13 Unable to mount multiple subvolumes of a single disk Sam Thursfield
2014-09-15 15:54 ` Chris Mason
2014-09-15 16:09   ` Anand Jain
2014-09-15 17:13     ` Sam Thursfield
2014-09-15 17:21       ` Anand Jain
2014-09-15 17:42         ` Anand Jain
2014-09-16  7:46           ` Paul Sherwood
2014-09-16 21:08           ` Stefan G. Weichinger
2014-09-16 21:53             ` Anand Jain
2014-09-17  4:41               ` Anand Jain
2014-09-15 20:38         ` xavier.gnata
2014-09-16 13:23     ` Chris Mason
2014-09-17  9:47       ` Anand Jain
2014-09-17 13:21         ` Chris Mason
2014-09-22 12:04           ` Stefan G. Weichinger
2014-09-15 16:42 ` Anand Jain
2014-09-15 17:15   ` Sam Thursfield [this message]

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=54171EC6.7040704@codethink.co.uk \
    --to=sam.thursfield@codethink.co.uk \
    --cc=1i5t5.duncan@cox.net \
    --cc=Anand.Jain@oracle.com \
    --cc=baserock-dev@baserock.org \
    --cc=johannes.hirte@datenkhaos.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=xavier.gnata@gmail.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;
as well as URLs for NNTP newsgroup(s).