All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dilger, Andreas <andreas.dilger@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Fwd: llmount.sh does not use fs-specific paths to the ost(s) and mds it mounts
Date: Tue, 10 May 2016 19:42:44 +0000	[thread overview]
Message-ID: <D3579394.14730F%andreas.dilger@intel.com> (raw)
In-Reply-To: <5731ECDF.10801@cea.fr>

On 2016/05/10, 08:14, "Quentin BOUGET" <quentin.bouget.ocre@cea.fr> wrote:
>
>Hello!
>
>While trying to mount two different lustre filesystems on a local node
>with the "llmount.sh" script, I noticed that the path to mount mds and
>ost(s) was computed like this:
>
>eval mntpt=${!var:-${MOUNT%/*}/$facet} # var is not defined by default,
>so this removes
>                                                                     #
>everything after the last '/' of $MOUNT
>
>
>The code can be found at test-framework.sh in the function "facet_mntpt"
>around the line 3226.
>
>
>By default MOUNT is initialized like this:
>
>MOUNT=${MOUNT:-/mnt/${FSNAME}} # default: "/mnt/lustre"
>
>
>Thus the default mountpoints for mds and ost(s) are "/mnt/mds1" and
>"/mnt/ost1".
>Because of that, when trying to do two successive calls to "llmount.sh"
>with two different values for FSNAME, the second fs to be mounted will
>unmount the first's mds and ost(s) (paths are identical).
>
>
>Is there any reason to truncate the MOUNT variable like this ? Shouldn't
>the mountpoint path look more like "/mnt/<fsname>-mds1" and
>"/mnt/<fsname>-ost1"?

I don't think there is any particular reason it was implemented this way,
just that it has worked for many years without the need to include the
fsname into the MDT/OST mount points... :-)

If you want to expand it to allow exporting multiple filesystems from the
same MDS/OSS nodes then your suggestion to use $FSNAME-$facet in
facet_mntpt() is reasonable.  Please submit a patch to verify this is
working correctly.  There may be some places in the tests that aren't
using facet_mntpt() yet.

Cheers, Andreas
-- 
Andreas Dilger

Lustre Principal Architect
Intel High Performance Data Division

  reply	other threads:[~2016-05-10 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5731EAC3.5070207@cea.fr>
2016-05-10 14:14 ` [lustre-devel] Fwd: llmount.sh does not use fs-specific paths to the ost(s) and mds it mounts Quentin BOUGET
2016-05-10 19:42   ` Dilger, Andreas [this message]
2016-05-11  1:17     ` [lustre-devel] " Drokin, Oleg
2016-05-11  7:07       ` Quentin BOUGET
2016-05-11 15:58         ` James Simmons
2016-05-12  7:17           ` Quentin BOUGET

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=D3579394.14730F%andreas.dilger@intel.com \
    --to=andreas.dilger@intel.com \
    --cc=lustre-devel@lists.lustre.org \
    /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.