From: Stan Hoeppner <stan@hardwarefreak.com>
To: Peter Vajgel <pv@fb.com>
Cc: Jef Fox <jef.fox@kinetx.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS Preallocation
Date: Tue, 01 Feb 2011 14:12:12 -0600 [thread overview]
Message-ID: <4D48691C.8000006@hardwarefreak.com> (raw)
In-Reply-To: <3F5ACD12257C714E9C0535D0A839171802AB01@SC-MBX02-2.TheFacebook.com>
Peter Vajgel put forth on 2/1/2011 1:20 PM:
> At the scale we operate it does. We have multiple variables so the number of combinations is large. We have hit every single possible hardware and software problem and problem resolution can take months if it takes days to reproduce the problem. Hardware vendors (disk, controller, motherboard manufacturers) are much more responsive when you can reproduce a problem on the fly in seconds (especially in comparative benchmarking). The tests usually run only couple of minutes. With 12x3TB (possibly multiplied by a factor of X with our new platform) it would be unacceptable to wait for writes to finish.
Hi Peter,
When you mention scale, you're referring to the storage back end at
facebook.com, your employer, correct?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-01 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 2:05 XFS Preallocation Jef Fox
2011-01-28 4:52 ` Dave Chinner
2011-01-28 15:15 ` Jef Fox
2011-01-28 17:33 ` Jef Fox
2011-01-29 0:17 ` Dave Chinner
2011-02-01 4:45 ` Peter Vajgel
2011-02-01 8:03 ` Dave Chinner
2011-02-01 19:20 ` Peter Vajgel
2011-02-01 20:12 ` Stan Hoeppner [this message]
2011-02-01 22:47 ` Peter Vajgel
2011-02-02 0:07 ` Dave Chinner
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=4D48691C.8000006@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=jef.fox@kinetx.com \
--cc=pv@fb.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