From: Daniel Patton <djp101@ecs.soton.ac.uk>
To: linux-scsi@vger.kernel.org
Subject: Newbie: multiple initiator contention resolution?
Date: Thu, 01 Apr 2004 19:48:23 +0100 [thread overview]
Message-ID: <406C63F7.3060009@ecs.soton.ac.uk> (raw)
Hello all,
I'm an undergraduate at a UK university, and I'm very much a newbie to
kernel development, so my apologies in advance if my questions sound
daft or have been answered before, etc.
I'm doing a project on something which involves writing a LLD for a
"fake" disk, similar to scsi_debug. However, the LLD may loaded on
multiple hosts, and they all see the same fake disk. Does the sd driver
have any kind of built-in contention resolution mechanism for such
multiple initiator setups? That is, if I mount a partition on my fake
disk simultaneously on more than one host, how do I stop the filesystem
from getting corrupted?
Many thanks in advance.
Dan Patton
djp101@ecs.soton.ac.uk
next reply other threads:[~2004-04-01 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 18:48 Daniel Patton [this message]
2004-04-01 20:58 ` Newbie: multiple initiator contention resolution? Steven Dake
2004-04-02 20:00 ` Daniel Patton
2004-04-03 0:05 ` Bryan Henderson
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=406C63F7.3060009@ecs.soton.ac.uk \
--to=djp101@ecs.soton.ac.uk \
--cc=linux-scsi@vger.kernel.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