From: "Peter C. Norton" <spacey@lenin.nu>
To: Tracy R Reed <treed@ultraviolet.org>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] Re: (reiserfs) Re: AIX JFS dual-mount
Date: Sat, 29 Jan 2000 12:32:15 -0800 [thread overview]
Message-ID: <20000129123215.B24375@lenin.nu> (raw)
In-Reply-To: <20000129122614.C13523@ultraviolet.org>; from treed@ultraviolet.org on Sat, Jan 29, 2000 at 12:26:14PM -0800
There does seem to be a seagate scsi drive listed that does some kind of
dlocks. Dlocks may not be FC only.
-Peter
On Sat, Jan 29, 2000 at 12:26:14PM -0800, Tracy R Reed wrote:
> On Sat, Jan 29, 2000 at 09:54:03AM -0800, Peter C. Norton wrote:
> > GFS seems to require some support from hardware in the way of "dlocks", a
> > not-too widely supported standard. I think you'd need to have drives that
> > implement dlocks, and that the lvm would have to know about them. What
> > would need to be done to the volume stuff to support dlocks? Could any
> > filesystem be built on top of a volume manager with dlock support?
>
> There are two options: You can use dlocks with special drive firmware or you
> can use a global lock manager over TCP with one of the hosts running the lock
> manager. I was thinking the latter way might be possible for non-fibrechannel
> setups.
>
> --
> Tracy Reed http://www.ultraviolet.org
> "She moves in mysterious ways"
--
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.
prev parent reply other threads:[~2000-01-29 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10001280539550.13561-100000@home.suse.com>
2000-01-29 8:14 ` [linux-lvm] Re: (reiserfs) Re: AIX JFS dual-mount Tracy R Reed
2000-01-29 18:36 ` Heinz Mauelshagen
2000-01-29 20:27 ` Tracy R Reed
2000-01-30 0:37 ` Heinz Mauelshagen
[not found] ` <20000129095403.A24375@lenin.nu>
2000-01-29 20:26 ` Tracy R Reed
2000-01-29 20:32 ` Peter C. Norton [this message]
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=20000129123215.B24375@lenin.nu \
--to=spacey@lenin.nu \
--cc=linux-lvm@msede.com \
--cc=treed@ultraviolet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox