[ale] invisible mounting points on RHEL 5.1

[Jim Kinney]

?????
So machine A has a disk image.
Machine B has a NFS served directory that is mounted by machine A.
The machine A disk image is loopback mounted to a point inside the NFS mount
provided by machine B?!?!
????????

Why????? This seems very, very bad. Which machine handles the lock on the
mount - the source of the image file or the NFS server that handles the
shared files? Nested NFS mounts are a nightmare as it is (and usually broke
things up until NFSv4).

On Tue, Oct 14, 2008 at 11:48 AM, Jerry Yu <jjj863 at gmail.com> wrote:

> /mnt/m1 is on the NFS server.
> It was created as such by a 3rd-party tool:
> Mkdir /mnt/m1
> Mount -t ext3 -o loop img1 /mnt/m1
>
> We have 200 such directories.
>
> On 10/14/08, Tim Meanor <timothy at meanor.net> wrote:
> > Sounds like automounter behavior to me, too.  Does m1 show up in the
> > output of "ls -la /mnt/*"?  If so, then most likely it's an
> > automounted fs (via autofs or maybe amd).
> >
> > -Tim
> >
> > On Mon, Oct 13, 2008 at 5:35 PM, Jerry Yu <jjj863 at gmail.com> wrote:
> >> They are regular NFS exports. The /mnt/m1 is my attempt to simplify my
> >> question. They are under /opt/mnt/appName1/m1 for client #1.
> >>
> >> On 10/13/08, Jeff Lightner <jlightner at water.com> wrote:
> >>> I'm confused by this.  You must have added the "/mnt/m1" as it is NOT a
> >>> stock part of RHEL5.
> >>>
> >>>
> >>>
> >>> Are you sure this isn't something you've configured in /etc/fstab or in
> >>> automounter?  I've seen some very strange behavior when attempting to
> >>> manually do things with filesystems put under automounter control.
> >>>
> >>>
> >>>
> >>> ________________________________
> >>>
> >>> From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of
> >>> Jerry Yu
> >>> Sent: Monday, October 13, 2008 4:21 PM
> >>> To: ALE
> >>> Subject: [ale] invisible mounting points on RHEL 5.1
> >>>
> >>>
> >>>
> >>> On a stock RHEL 5.1 server, an ext3 fs image (i1) is mounted as
> loopback
> >>> at /mnt/m1. /mnt/m1 is exported as NFS share to be used by a RHEL 5.1
> >>> client.
> >>>
> >>> Not sure since when, on the NFS server,
> >>>
> >>> *     one can not see m1 when ls /mnt anymore.   Meanwhile,
> >>> *     'cd /mnt/m1' and 'ls /mnt/m1' and  file creation under /mnt/m1
> >>> all work just fine under /mnt/m1.
> >>> *     mkdir /mnt/m1 fails saying '/mnt/m1 is present'
> >>> *     /proc/mounts still have /mnt/m1 listed as mounted loopback.
> >>> *     umounting /mnt/m1 & mounting it back works just fine.  still
> >>> cannot see 'm1' under /mnt.
> >>> *     /mnt/m1 is under constant use by the NFS clients, so 'rm -rf' or
> >>> 'umount' of /mnt/m1 from the server actually fails.
> >>> ----------------------------------
> >>> CONFIDENTIALITY NOTICE: This e-mail may contain privileged or
> >>> confidential
> >>> information and is for the sole use of the intended recipient(s). If
> you
> >>> are
> >>> not the intended recipient, any disclosure, copying, distribution, or
> use
> >>> of
> >>> the contents of this information is prohibited and may be unlawful. If
> >>> you
> >>> have received this electronic transmission in error, please reply
> >>> immediately to the sender that you have received the message in error,
> >>> and
> >>> delete it. Thank you.
> >>> ----------------------------------
> >>>
> >> _______________________________________________
> >> Ale mailing list
> >> Ale at ale.org
> >> http://mail.ale.org/mailman/listinfo/ale
> >>
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://mail.ale.org/mailman/listinfo/ale
> >
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>



-- 
-- 
James P. Kinney III
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20081014/ebe1bccb/attachment.html