From: Heilige Gheist <hgheist@yahoo.com>
To: Dave Lloyd <dlloyd@exegy.com>
Cc: xfs@oss.sgi.com
Subject: Re: Concurrent mount of XFS over SAN
Date: Mon, 7 Aug 2006 01:48:30 -0700 (PDT) [thread overview]
Message-ID: <20060807084830.58133.qmail@web31713.mail.mud.yahoo.com> (raw)
In-Reply-To: <44D26D3E.5010708@exegy.com>
Dave,
That's 100% correct assuming you prohibit a shared access between the
nodes. I didn't point out that we're dealing with filesystem failover
setup.
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.
Thanks,
Alan
--- Dave Lloyd <dlloyd@exegy.com> wrote:
> Heilige Gheist wrote:
> > Is there a way to prevent and/or detect concurrent mount of same
> XFS
> > SAN-based partition from several nodes?
> > I had to fsck a filesystem losing some data after two nodes
> happily
> > mounted a filesystem from same SAN-based partition at the same
> time and
> > wrote into it.
> > Thanks!
> >
> > --alan
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> >
>
> I think that the generally accepted way is to zone at the switch or
> the
> storage array.
>
> --
> Dave Lloyd
> Test Engineer, Exegy, Inc.
> 314.450.5342
> dlloyd@exegy.com
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-08-07 8:49 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 [this message]
2006-08-07 10:13 ` Jan-Frode Myklebust
2006-08-07 11:01 ` kris buggenhout
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=20060807084830.58133.qmail@web31713.mail.mud.yahoo.com \
--to=hgheist@yahoo.com \
--cc=dlloyd@exegy.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox