From: Hannes Reinecke <hare@suse.de>
To: Tim Walker <tim.t.walker@seagate.com>
Cc: Christoph Hellwig <hch@infradead.org>,
dgilbert <dgilbert@interlog.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: Re: Multi-Actuator SAS HDD First Look
Date: Fri, 6 Apr 2018 08:24:18 +0200 [thread overview]
Message-ID: <20180406082418.127a0ec6@pentland.suse.de> (raw)
In-Reply-To: <CANo=J15RFeMiqudiS_+dAuyVsgoPYn2U=iJZh3EhamtX56atWw@mail.gmail.com>
On Thu, 5 Apr 2018 17:43:46 -0600
Tim Walker <tim.t.walker@seagate.com> wrote:
> On Tue, Apr 3, 2018 at 1:46 AM, Christoph Hellwig <hch@infradead.org>
> wrote:
> > On Sat, Mar 31, 2018 at 01:03:46PM +0200, Hannes Reinecke wrote:
> >> Actually I would propose to have a 'management' LUN at LUN0, who
> >> could handle all the device-wide commands (eg things like START
> >> STOP UNIT, firmware update, or even SMART commands), and ignoring
> >> them for the remaining LUNs.
> >
> > That is in fact the only workable option at all. Everything else
> > completly breaks the scsi architecture.
>
> Here's an update: Seagate will eliminate the inter-LU actions from
> FORMAT UNIT and SANITIZE. Probably SANITIZE will be per-LUN, but
> FORMAT UNIT is trickier due to internal drive architecture, and how
> FORMAT UNIT initializes on-disk metadata. Likely it will require some
> sort of synchronization across LUNs, such as the command being sent to
> both LUNs sequentially or something similar. We are also considering
> not supporting FORMAT UNIT at all - would anybody object? Any other
> suggestions?
>
Ah. Far better.
What about delegating FORMAT UNIT to the control LUN, and not
implementing it for the individual disk LUNs?
That would make an even stronger case for having a control LUN;
with that there wouldn't be any problem with having to synchronize
across LUNs etc.
Cheers,
Hannes
next prev parent reply other threads:[~2018-04-06 6:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 14:57 Multi-Actuator SAS HDD First Look Tim Walker
2018-03-26 15:08 ` Hannes Reinecke
2018-03-29 18:03 ` Douglas Gilbert
2018-03-30 13:07 ` Tim Walker
2018-03-30 18:07 ` Tim Walker
2018-03-30 18:17 ` Bart Van Assche
2018-03-30 18:21 ` Tim Walker
2018-03-30 18:31 ` Bart Van Assche
2018-03-30 18:36 ` Tim Walker
2018-03-30 20:01 ` Bart Van Assche
2018-03-31 16:52 ` Douglas Gilbert
2018-04-02 15:34 ` Tim Walker
2018-04-02 16:29 ` Douglas Gilbert
2018-04-02 16:44 ` Tim Walker
2018-03-31 12:21 ` Hannes Reinecke
2018-03-31 11:03 ` Hannes Reinecke
2018-04-03 7:46 ` Christoph Hellwig
2018-04-05 23:43 ` Tim Walker
2018-04-06 0:51 ` Douglas Gilbert
2018-04-06 6:24 ` Hannes Reinecke [this message]
2018-04-06 6:42 ` Christoph Hellwig
2018-04-06 17:09 ` Douglas Gilbert
2018-04-09 2:08 ` Tim Walker
2018-04-09 6:17 ` Hannes Reinecke
2018-04-09 16:02 ` Douglas Gilbert
2018-04-16 1:35 ` Tim Walker
2018-04-16 4:31 ` Bart Van Assche
2018-04-18 11:16 ` Tim Walker
2018-04-18 16:20 ` Bart Van Assche
2018-04-18 16:25 ` Tim Walker
2018-04-09 9:25 ` Christoph Hellwig
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=20180406082418.127a0ec6@pentland.suse.de \
--to=hare@suse.de \
--cc=dgilbert@interlog.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tim.t.walker@seagate.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.