linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sébastien ROHAUT" <sebastien.rohaut@free.fr>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Can't mount subvolume with ro option
Date: Sat, 28 Jun 2014 13:02:43 +0200	[thread overview]
Message-ID: <53AEA0D3.8080905@free.fr> (raw)
In-Reply-To: <54D8214E-1C00-43AB-A68A-D450069D878C@colorremedies.com>

Le 28/06/2014 00:12, Chris Murphy a écrit :
> On Jun 27, 2014, at 4:08 PM, Chris Murphy <lists@colorremedies.com> wrote:
>
>> On Jun 27, 2014, at 2:07 PM, Sébastien ROHAUT <sebastien.rohaut@free.fr> wrote:
>>
>>> Hi,
>>>
>>> In the wiki, it's said we can mount subvolumes with different mount options. nosuid, nodev, rw and ro are listed, as valid generic mount options.
>> This might require 3.15. I don't recall it working with early 3.14 kernels, but by 3.14.3 I'd moved onto testing 3.15.
>
> [root@f20v ~]# mount /dev/sda3 /mnt
> [root@f20v ~]# btrfs subvol create /mnt/test
> Create subvolume '/mnt/test'
> [root@f20v ~]# umount /mnt
> [root@f20v ~]# mount -o ro,subvol=test /dev/sda3 /mnt
> mount: /dev/sda3 is already mounted or /mnt busy
>         /dev/sda3 is already mounted on /
>         /dev/sda3 is already mounted on /home
>         /dev/sda3 is already mounted on /var
>         /dev/sda3 is already mounted on /boot
> [root@f20v ~]# uname -r
> 3.14.6-200.fc20.x86_64
>
>
> I don't know if this feature will be backported to stable kernels. If not, then probably the wiki should say it's a 3.15+ feature.
> Chris Murphy
>
>
Thank you for your answer. I'm actually moving to a Fedora Rawhide (3.16 
kernel).

Sebastien Rohaut

  reply	other threads:[~2014-06-28 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 20:07 Can't mount subvolume with ro option Sébastien ROHAUT
2014-06-27 22:08 ` Chris Murphy
2014-06-27 22:12   ` Chris Murphy
2014-06-28 11:02     ` Sébastien ROHAUT [this message]
2014-06-30  2:19       ` Qu Wenruo
2014-06-30  2:57         ` Qu Wenruo
2014-06-30  3:31           ` 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=53AEA0D3.8080905@free.fr \
    --to=sebastien.rohaut@free.fr \
    --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;
as well as URLs for NNTP newsgroup(s).