From: Christian Herzog <horeizo@phys.ethz.ch>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS errors on large Infiniband fileserver setup
Date: Fri, 24 Sep 2010 07:41:53 +0200 [thread overview]
Message-ID: <2276da2491527ca8044fa1daec496b48@phys.ethz.ch> (raw)
In-Reply-To: <20100923235355.GO2614@dastard>
Hi Dave,
thanks for your feedback.
>> 2 disk backends, each: Quad-Xeon X5550, 12G of RAM, 28T HW
>> SATA-RAID6 sliced into 2T chunks by LVM2 and exported via tgt
>> 1.0.0-2, Ubuntu 10.04 LTS, connected via Mellanox MHRH19B-XTR
>> Infiniband + ISER to
>>
>> 1 frontend Octo-Xeon E5520, 12G of RAM, open-iscsi 2.0.871
>> initiator, Ubuntu 10.04 LTS. LMV2 stitches together the
>> 2T-iSCSI-LUNs and provides a 10T test XFS filesystem
>
> Out of curiousity, why are you using such a complex storage
> configuration?
>
> IMO, it is unneccessarily complex - you could easily do this (~30
> drives) with a single server with a couple of external SAS JBOD
> arrays and SAS RAID controllers. That would give you the same
> performance (or better), with many fewer points of failure (both
> hardware and software), use less rack space, and probably be
> significantly cheaper....
basically, our situation is this: we have to supply our astrophysicists
(not just them, but they consume 95%) with large and ever-increasing
amounts of disk space. Up to now we bought individual file servers
whenever space was needed, which is an administrative nightmare as you
can imagine. Hence we decided to come up with a more scalable solution
that would grow with the space needed - and grow it will. We start off
with 52T and can easily add additional disk units to the Infiniband
switch.
It is well possible we have overlooked an easier/cheaper solution, but
what we have now is very flexible and has emerged from discussions we've
had with several 'storage experts'. Do you have any particular/typical
device in mind? I'd like to check it out nonetheless.
thanks,
-Christian
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-24 5:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 7:22 XFS errors on large Infiniband fileserver setup Christian Herzog
2010-09-23 10:01 ` Christian Herzog
2010-09-23 10:38 ` Christoph Hellwig
2010-09-23 11:52 ` Christian Herzog
2010-09-23 13:54 ` Christoph Hellwig
2010-09-23 14:10 ` Christian Herzog
2010-09-23 23:53 ` Dave Chinner
2010-09-24 5:41 ` Christian Herzog [this message]
2010-09-24 8:56 ` Stan Hoeppner
2010-09-24 13:19 ` Emmanuel Florac
2010-09-24 13:19 ` Emmanuel Florac
2010-09-27 5:49 ` Christian Herzog
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=2276da2491527ca8044fa1daec496b48@phys.ethz.ch \
--to=horeizo@phys.ethz.ch \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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