From: Karel Zak <kzak@redhat.com>
To: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
Cc: linux-btrfs@vger.kernel.org, systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] is mounting subvolumes with a read-only root subvolume allowed?
Date: Fri, 15 Nov 2013 00:43:51 +0100 [thread overview]
Message-ID: <20131114234351.GI13330@x2.net.home> (raw)
In-Reply-To: <20131114233210.GU30929@in.waw.pl>
On Fri, Nov 15, 2013 at 12:32:10AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
> I have a box with / and /home being subvolumes from the same btrfs filesystem.
>
> /etc/fstab:
> UUID=c0686... / btrfs subvol=root,x-systemd.device-timeout=0 1 1
> UUID=c0686... /home btrfs subvol=home,x-systemd.device-timeout=0 1 1
> ...
>
> / is initially mounted readonly by the initramfs, and then after switching
> to the real system, /home is attempted to be mounted in parallel with /
> being remounted rw. If remounting rw happens first, boot proceeds. If
> mounting /home is attempted to realy, it fails.
>
> $ /bin/mount /home
> mount: /dev/mapper/luks-765... is already mounted or /home busy
> /dev/mapper/luks-765... is already mounted on /
> $ /bin/mount -o remount,rw /
> $ /bin/mount /home
> $
>
> So, is this expected that the other subvolume must be mounted rw?
This is known and pretty stupid issue:
http://www.spinics.net/lists/linux-btrfs/msg25502.html
... but it seems that btrfs guys are fine with this "feature".
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2013-11-14 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 23:32 is mounting subvolumes with a read-only root subvolume allowed? Zbigniew Jędrzejewski-Szmek
2013-11-14 23:43 ` Karel Zak [this message]
2013-11-15 0:04 ` [systemd-devel] " Zbigniew Jędrzejewski-Szmek
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=20131114234351.GI13330@x2.net.home \
--to=kzak@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=systemd-devel@lists.freedesktop.org \
--cc=zbyszek@in.waw.pl \
/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).