All of lore.kernel.org
 help / color / mirror / Atom feed
From: kris buggenhout <kris.buggenhout@skynet.be>
To: Jan-Frode Myklebust <mykleb@no.ibm.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Concurrent mount of XFS over SAN
Date: Mon, 07 Aug 2006 13:01:54 +0200	[thread overview]
Message-ID: <44D71DA2.2020409@skynet.be> (raw)
In-Reply-To: <slrnede4hl.bg1.mykleb@99RXZYP.ibm.com>

afaik, the node was stored in xlv, which was an extra option in IRIX, ( 
extra license) but this could later be used in CXFS which allows 
multiple machines to mount the same FS read write from a SAN, made for 
clusters, HA and HPC...

knowledge of the node "owning" the device was in there for protection. 
but can be overridden with an xlv command.

kind regards, Kris

Jan-Frode Myklebust wrote:
> On 2006-08-07, Heilige Gheist <hgheist@yahoo.com> wrote:
>   
>> It's obvious that I can always fall back to the inter-node heart-beat
>> to ensure that only one node is mounting the filesystem.
>> I'm just wondering if there's any facility or accepted practice to
>> enforce it.
>>     
>
> STONITH (Shoot The Other Node In The Head) trough smart power switches
> or management adapters in the node. 
>
> SCSI reserve/release ... No idea how reliable this is on a SAN, but the
> ServeRAID-version works great. http://www.linux-ha.org/ServeRAID
>
> Export the volume group, or scsi device on the first node, before
> importing/attaching it on the second .. Probably best to use together
> with STONITH, in case the first node fails on unmounting/exporting.
>
> BTW: I think XFS on IRIX had the owning node name in the file system header, 
> and only would allow this node to mount the fs. But I can't find this now...
> Maybe it's gone, or maybe it was in xlv.. ?
>
>
>   -jf
>
>
>
>
>   

  reply	other threads:[~2006-08-07 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 14:33 Concurrent mount of XFS over SAN Heilige Gheist
2006-08-03 21:40 ` Dave Lloyd
2006-08-07  8:48   ` Heilige Gheist
2006-08-07 10:13     ` Jan-Frode Myklebust
2006-08-07 11:01       ` kris buggenhout [this message]
2006-08-07 13:12         ` Sebastian Brings

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=44D71DA2.2020409@skynet.be \
    --to=kris.buggenhout@skynet.be \
    --cc=linux-xfs@oss.sgi.com \
    --cc=mykleb@no.ibm.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.