From: Mark Lord <lkml@rtr.ca>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <greg@kroah.com>,
Jeff Garzik <jeff@garzik.org>,
Linux USB kernel mailing list <linux-usb@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: USB storage no-boot regression (bisected)
Date: Thu, 16 Apr 2009 09:49:26 -0400 [thread overview]
Message-ID: <49E73766.9090205@rtr.ca> (raw)
In-Reply-To: <20090416063401.32ced22a@infradead.org>
Arjan van de Ven wrote:
> On Thu, 16 Apr 2009 11:51:53 +0100
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
>>>> Though it's an onboard USB SSD, not a pluggable stick.
>>> Wow, that's insane. Leave it to a hardware designer to use a bus
>>> that you never know if you have discovered all the devices to be
>>> the primary device to boot from.
>> Let me see:
>>
>> - Standardised small component
>> - Low pin count and low wire count bus
>> - Cheap
>>
>> In an embedded environment where you know the device is wired in at
>> software level that strikes me not as insane but very sensible.
>
> I'm not surprised usb is used for storage. What I am surprised at is
> that USB is used in such high end environments that rootwait is not
> sufficient and that the panic-rebooter is needed for the reliability.
..
Failover and redundancy are standard requirements for really reliable systems.
As good as a component may be, there's always anticipation that it will fail
someday, and multiple ways of detecting/overcoming failures must be built-in.
In this case, imagine *two* such SSDs.
next prev parent reply other threads:[~2009-04-16 13:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 21:06 USB storage no-boot regression (bisected) Jeff Garzik
2009-04-15 1:38 ` Arjan van de Ven
2009-04-15 2:30 ` Jeff Garzik
2009-04-15 2:44 ` Arjan van de Ven
2009-04-15 2:48 ` Jeff Garzik
2009-04-15 3:09 ` Arjan van de Ven
2009-04-15 8:40 ` Alan Cox
2009-04-15 1:49 ` Greg KH
2009-04-15 2:35 ` Jeff Garzik
2009-04-15 2:46 ` Arjan van de Ven
2009-04-15 5:09 ` Greg KH
2009-04-15 13:46 ` Jeff Garzik
2009-04-15 14:25 ` Mark Lord
2009-04-15 14:30 ` Arjan van de Ven
2009-04-15 15:37 ` Mark Lord
2009-04-15 19:58 ` Arjan van de Ven
2009-04-15 21:55 ` Mark Lord
2009-04-16 1:32 ` Arjan van de Ven
2009-04-16 2:14 ` Mark Lord
2009-04-16 2:54 ` Greg KH
2009-04-16 10:51 ` Alan Cox
2009-04-16 13:34 ` Arjan van de Ven
2009-04-16 13:49 ` Mark Lord [this message]
2009-04-16 2:17 ` Hal Murray
2009-04-16 3:42 ` Jeff Garzik
2009-04-15 15:01 ` Alan Cox
2009-04-15 15:47 ` Alan Stern
2009-04-15 15:49 ` Mark Lord
2009-04-15 17:06 ` VomLehn
2009-04-15 17:32 ` Alan Cox
2009-04-15 20:06 ` Arjan van de Ven
2009-04-15 20:20 ` VomLehn
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=49E73766.9090205@rtr.ca \
--to=lkml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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.