From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Questions for Storage Engineers
Date: Tue, 19 Aug 2014 15:22:42 -0400 [thread overview]
Message-ID: <17674.1408476162@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 19 Aug 2014 23:49:48 +0530." <CAK25hWOKALTiBkAYJfY9j=UyZkgHWQ+mfnvX9mGEGnuf+eH82Q@mail.gmail.com>
On Tue, 19 Aug 2014 23:49:48 +0530, Saket Sinha said:
> Each filesystem has its own use-case. Like XFS is for big data, btrfs
> with its COW and other features meets some specific use-cases like
> facebook where they have a scenario(refer
> http://lwn.net/Articles/591780/ ) where btrfs suites then perfectly.
Right. The point I was making is that although btrfs has some *really*
nice use-cases, they are by and large places where IBM is *not* going
to engage one of their storage engineers. A "use btrfs" recommendation
is going to come from a different engineering group, and a "here's
how to tune btrfs" is probably going to come from somebody in their
Professional Services (at $200/hour and up).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140819/fd8272e3/attachment.bin
next prev parent reply other threads:[~2014-08-19 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 17:33 Questions for Storage Engineers Nick Krause
2014-08-19 17:58 ` Valdis.Kletnieks at vt.edu
2014-08-19 18:05 ` Nick Krause
2014-08-19 18:19 ` Saket Sinha
2014-08-19 19:22 ` Valdis.Kletnieks at vt.edu [this message]
2014-08-19 19:27 ` Saket Sinha
2014-08-19 19:32 ` Valdis.Kletnieks at vt.edu
2014-08-19 21:28 ` Nick Krause
2014-08-20 6:26 ` Andrew Bourhill
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=17674.1408476162@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).