[Lustre-discuss] how do you mount mountconf (i.e. 1.6) lustre on your servers?

[Christopher J. Morrone]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

We are using a home-grown set of init scripts.  There is an "lnet" init
script to bring up the lnet networking, and a "lustre" init script to
start lustre services.

We tend to be paranoid about the possibility of double mounting a
multi-homed LUNs, so failover for us requires a sysadmin to manually
issue the command to move a LUN to the failover node.

We have a custom udev script to detect any available LUNs on a node,
identify them as normal or backup lustre devices, and name them
accordingly under /dev/lustre.

The lustre init script runs an optional journal-replay-only fsck on each
device before issuing a mount command to start the lustre service.

Chris

Brian J. Murrell wrote:
> As any of you using version 1.6 of Lustre knows, Lustre servers can now
> be started simply my mounting the devices it is using.  Even
> an /etc/fstab entry can be used if you can have the mount delayed until
> the network is started.
> 
> Given this change, you have also notices that we have eliminated the
> initscript for Lustre that used to exist for releases prior to 1.6.
> 
> I'd like to take a small survey on how those of you using mountconf
> (1.6) are managing the mounting of your Lustre devices on the servers.
> The obvious choices are:
> 
>       * /etc/fstab
>       * home-grown initscript
>       * heartbeat managed
>       * other
> 
> If you are using /etc/fstab I'd be interested in seeing your /etc/fstab
> entries (you can omit obvious near-duplication in the case of many OSTs
> though) and knowing what distribution (make, version) you are using.
> 
> /etc/fstab entries provides an interesting wrinkle in that you cannot
> mount the devices until the network is up and yet most distributions
> do /etc/fstab (i.e. "local") mounting before the network unless some
> mechanism is used to filter out entries that need network connectivity
> first.  The traditional way of doing this has been to add _netdev to
> those entries and they are then delayed until the network is up.
> 
> Cheers,
> b.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHvjcyg40IeHfy1xIRCjSaAKCOVBqNlxhpdYghV30aTIUqUoITFQCggCcr
VRoSFlEIhSDTqwMsCML0dKs=
=GJRV
-----END PGP SIGNATURE-----