On Sun, May 29, 2016 at 1:48 PM, Anand Jain <anand.j...@oracle.com> wrote:
> Originally a seed FS becomes a writeable sprout FS after a
> device is added to it, however as at 4.6 I don't see this
> behavior anymore.
I think the old behavior where it's possible to use -o remount,rw is
actually confusing.
Strictly speaking what is mounted is the seed volume with that
particular volume UUID. Doing a remount to effectively cause a behind
the scene umount then a mount of a different volume and volume UUID is
not obvious. What if there's more than one sprout? It seems really
ambiguous what the user wants with an -o remount so I'm wondering if
this operation should fail instead?
>From mount man page:
remount
Attempt to remount an already-mounted filesystem. This
is commonly used to change the mount flags for a filesystem,
especially to make a readonly filesystem writable. It does not change
device or mount point.
Two problems: 1. the seed and sprout are two filesystems, and one of
them is not already mounted. So remount should not mean switch from a
mounted filesystem to an unmounted one. 2. The former remount behavior
did change device, from that of the seed to that of the sprout.
So both of those seem to depart from the remount definition rather
significantly.
--
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
