diff options
author | Steven Whitehouse <swhiteho@redhat.com> | 2008-08-08 13:45:13 +0100 |
---|---|---|
committer | Steven Whitehouse <swhiteho@redhat.com> | 2008-08-13 09:59:40 +0100 |
commit | 9b8df98fc8973ad1c5f0d7c4cf71c7fb84fe22c5 (patch) | |
tree | 6a0445afd83d0f7a63a301c2e146647abf59ad82 /net/802 | |
parent | c1e817d03a7de57a963654c35e6e80af9a5dbff5 (diff) | |
download | linux-3.10-9b8df98fc8973ad1c5f0d7c4cf71c7fb84fe22c5.tar.gz linux-3.10-9b8df98fc8973ad1c5f0d7c4cf71c7fb84fe22c5.tar.bz2 linux-3.10-9b8df98fc8973ad1c5f0d7c4cf71c7fb84fe22c5.zip |
GFS2: Fix metafs mounts
This patch is intended to fix the issues reported in bz #457798. Instead
of having the metafs as a separate filesystem, it becomes a second root
of gfs2. As a result it will appear as type gfs2 in /proc/mounts, but it
is still possible (for backwards compatibility purposes) to mount it as
type gfs2meta. A new mount flag "meta" is introduced so that its possible
to tell the two cases apart in /proc/mounts.
As a result it becomes possible to mount type gfs2 with -o meta and
get the same result as mounting type gfs2meta. So it is possible to
mount just the metafs on its own. Currently if you do this, its then
impossible to mount the "normal" root of the gfs2 filesystem without
first unmounting the metafs root. I'm not sure if thats a feature or
a bug :-)
Either way, this is a great improvement on the previous scheme and I've
verified that it works ok with bind mounts on both the "normal" root
and the metafs root in various combinations.
There were also a bunch of functions in super.c which didn't belong there,
so this moves them into ops_fstype.c where they can be static. Hopefully
the mount/umount sequence is now more obvious as a result.
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Cc: Alexander Viro <aviro@redhat.com>
Diffstat (limited to 'net/802')
0 files changed, 0 insertions, 0 deletions