From: Ric Wheeler <rwheeler@redhat.com>
To: Roland Dreier <roland@purestorage.com>
Cc: linux-fsdevel@vger.kernel.org,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] linux servers as a storage server - what's missing?
Date: Wed, 18 Jan 2012 12:51:41 -0500 [thread overview]
Message-ID: <4F1706AD.3080405@redhat.com> (raw)
In-Reply-To: <CAL1RGDVvSbOjvCFWDSYLm4xRvKftM5OhwEf9pMGrJhjJHxzsaA@mail.gmail.com>
On 01/18/2012 12:00 PM, Roland Dreier wrote:
> On Wed, Dec 21, 2011 at 7:59 AM, Ric Wheeler<rwheeler@redhat.com> wrote:
>> One common thing that I see a lot of these days is an increasing number of
>> platforms that are built on our stack as storage servers. Ranging from the
>> common linux based storage/NAS devices up to various distributed systems.
>> Almost all of them use our common stack - software RAID, LVM, XFS/ext4 and
>> samba.
>>
>> At last year's SNIA developers conference, it was clear that Microsoft is
>> putting a lot of effort into enhancing windows 8 server as a storage server
>> with both support for a pNFS server and of course SMB. I think that linux
>> (+samba) is ahead of the windows based storage appliances today, but they
>> are putting together a very aggressive list of features.
>>
>> I think that it would be useful and interesting to take a slot at this
>> year's LSF to see how we are doing in this space. How large do we need to
>> scale for an appliance? What kind of work is needed (support for the copy
>> offload system call? better support for out of band notifications like those
>> used in "thinly provisioned" SCSI devices? management API's? Ease of use CLI
>> work? SMB2.2 support?).
>>
>> The goal would be to see what technical gaps we have that need more active
>> development in, not just a wish list :)
> I see a technical gap in the robustness of our basic SCSI/block stack. In a
> pretty standard low to midrange setup, ie standard server with a couple of SAS
> HBAs connected to an external SAS JBOD, it's quite easy to run into problems
> like oopses or other issues that kill the whole system, even from faults that
> should affect only part of the system. For example losing one path to the JBOD,
> or losing one drive, or having a SCSI reservation conflict can lead to the whole
> system crashing.
>
> Which is not good for an HA storage server built on redundant hardware.
>
> - R.
Why would you crash is you have device mapper multipath configured to handle
path fail over? We have tons of enterprise customers that use that...
On the broader topic of error handling and so on, I do agree that is always an
area of concern (how many times to retry, how long time outs need to be, when to
panic/reboot or propagate up an error code)
ric
next prev parent reply other threads:[~2012-01-18 17:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 15:59 [LSF/MM TOPIC] linux servers as a storage server - what's missing? Ric Wheeler
2011-12-22 8:14 ` Shyam_Iyer
2011-12-22 15:58 ` Vivek Goyal
2011-12-22 20:54 ` Shyam_Iyer
2011-12-23 3:06 ` Vivek Goyal
2011-12-23 4:35 ` Shyam_Iyer
2012-01-09 12:18 ` Hannes Reinecke
2012-01-09 12:59 ` Tom Coughlan
2012-01-10 6:53 ` Ric Wheeler
2012-01-20 8:55 ` Hannes Reinecke
2012-01-19 16:17 ` [LSF/MM TOPIC] linux servers as a storage server - what'smissing? Loke, Chetan
2012-01-19 16:19 ` Ric Wheeler
2012-01-19 16:26 ` Loke, Chetan
2012-01-19 16:29 ` Ric Wheeler
2012-01-19 17:32 ` Loke, Chetan
2012-01-19 17:44 ` Ric Wheeler
2012-01-19 21:30 ` Loke, Chetan
2012-01-19 21:39 ` Ric Wheeler
2012-01-24 17:05 ` Loke, Chetan
2012-01-24 18:13 ` Ric Wheeler
2012-01-26 22:24 ` Dave Chinner
2012-01-26 22:29 ` Ric Wheeler
2012-01-03 19:26 ` [LSF/MM TOPIC][ATTEND] linux servers as a storage server - what's missing? Jeff Layton
2012-01-03 19:32 ` Chuck Lever
2012-01-17 21:16 ` J. Bruce Fields
2012-01-17 21:25 ` Chuck Lever
2012-01-24 21:36 ` J. Bruce Fields
2012-01-24 23:13 ` Ric Wheeler
2012-01-25 19:05 ` Christopher R. Hertel
2012-01-25 20:25 ` Christopher R. Hertel
2012-01-25 21:56 ` Roland Dreier
2012-01-25 22:09 ` Christopher R. Hertel
2012-01-26 21:52 ` Andy Grover
2012-01-26 11:15 ` Bart Van Assche
2012-01-18 17:00 ` [LSF/MM TOPIC] " Roland Dreier
2012-01-18 17:51 ` Ric Wheeler [this message]
2012-01-18 18:46 ` Roland Dreier
2012-01-18 18:51 ` Bart Van Assche
2012-01-18 19:00 ` Roland Dreier
2012-01-19 8:16 ` Rolf Eike Beer
2012-01-19 17:50 ` Loke, Chetan
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=4F1706AD.3080405@redhat.com \
--to=rwheeler@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=roland@purestorage.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;
as well as URLs for NNTP newsgroup(s).