From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH RHEL6] mount.gfs2: Fix mounting of regular files with -o loop
Date: Wed, 17 Aug 2011 17:51:45 +0100 [thread overview]
Message-ID: <4E4BF1A1.5050701@redhat.com> (raw)
In-Reply-To: <1313598779.2697.14.camel@menhir>
On 17/08/11 17:32, Steven Whitehouse wrote:
> Hi,
>
> Looks good to me. Did you test it with -o remount to be sure it does the
> right thing for that too?
Yep, testing with -o remount looks fine:
(I added the loop option when testing with remount just to check that it
was completely ignored in the remount case and wasn't doubled up)
[root at rhel6-01 mount]# mount -o rw,loop,noatime sparse-file /mnt
[root at rhel6-01 mount]# mount | grep gfs2
/dev/loop0 on /mnt type gfs2
(rw,noatime,localflocks,localcaching,loop=/dev/loop0)
[root at rhel6-01 mount]# mount -vv -o remount,ro,loop /mnt
mount /dev/loop0 /mnt
parse_opts: opts =
"ro,remount,noatime,loop=/dev/loop0,localflocks,localcaching"
set flag 1 for "ro", flags = 1
set flag 20 for "remount", flags = 21
set flag 400 for "noatime", flags = 421
add extra localflocks
add extra localcaching
parse_opts: flags = 421
parse_opts: extra = "localflocks,localcaching"
parse_opts: hostdata = ""
parse_opts: lockproto = ""
parse_opts: locktable = ""
mount(2) ok
read_proc_mounts: device = "/dev/loop0"
read_proc_mounts: dm device = "/dev/loop0"
read_proc_mounts: opts = "ro,noatime,localflocks,localcaching"
read_proc_mounts: proc_entry = "/dev/loop0 /mnt gfs2
ro,noatime,localflocks,localcaching,loop=/dev/loop0 0 0
"
[root at rhel6-01 mount]# mount | grep gfs2
/dev/loop0 on /mnt type gfs2
(ro,noatime,localflocks,localcaching,loop=/dev/loop0)
Andy
prev parent reply other threads:[~2011-08-17 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 16:25 [Cluster-devel] [PATCH RHEL6] mount.gfs2: Fix mounting of regular files with -o loop Andrew Price
2011-08-17 16:32 ` Steven Whitehouse
2011-08-17 16:51 ` Andrew Price [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=4E4BF1A1.5050701@redhat.com \
--to=anprice@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.