From: Adam Brenner <adam@aeb.io>
To: Marc MERLIN <marc@merlins.org>, linux-btrfs@vger.kernel.org
Subject: Re: Which companies are using Btrfs in production?
Date: Thu, 24 Apr 2014 00:13:26 -0700 [thread overview]
Message-ID: <5358B996.4060102@aeb.io> (raw)
In-Reply-To: <20140424011952.GO26949@merlins.org>
On 04/23/2014 06:19 PM, Marc MERLIN wrote:
> Oh while we're at it, are there companies that can say they are using btrfs
> in production?
>
> Marc
>
On the Gluster Listsrv a few brave souls have used it on as a
distributive filesystem[1]. Here at UCI's HPC Cluster we *might* use it
on a scratch filesystem ... if we upgrade to a newer kernel....
[1]: http://www.gluster.org/pipermail/gluster-users/2014-April/039896.html
--
Adam Brenner <adam@aeb.io>
next prev parent reply other threads:[~2014-04-24 7:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 1:18 Which companies contribute to Btrfs? Marc MERLIN
2014-04-24 1:19 ` Which companies are using Btrfs in production? Marc MERLIN
2014-04-24 7:13 ` Adam Brenner [this message]
2014-04-24 12:34 ` Austin S. Hemmelgarn
2014-04-24 12:52 ` Tomasz Torcz
2014-04-24 13:34 ` Daniel Lee
2014-04-24 21:41 ` Marc MERLIN
2014-04-24 22:03 ` Justin Maggard
2014-04-24 23:14 ` Marc MERLIN
2014-04-25 14:47 ` David Sterba
2014-04-25 15:01 ` Chris Mason
2014-04-25 15:20 ` Marc MERLIN
2014-04-25 15:32 ` ronnie sahlberg
2014-04-28 14:16 ` David Sterba
2014-04-28 15:01 ` Eric Sandeen
2014-04-24 2:29 ` Which companies contribute to Btrfs? Eric Sandeen
2014-04-24 2:30 ` Eric Sandeen
2014-04-24 3:45 ` Marc MERLIN
2014-04-24 4:32 ` Eric Sandeen
2014-04-24 10:31 ` Filipe David Manana
2014-04-24 17:07 ` Marc MERLIN
2014-04-24 11:39 ` David Sterba
2014-04-24 12:55 ` Fajar A. Nugraha
2014-04-24 21:41 ` Marc MERLIN
2014-04-28 19:00 ` Jonathan Corbet
2014-04-28 21:06 ` Chris Mason
2014-04-29 0:06 ` Chester
2014-04-29 0:08 ` Marc MERLIN
2014-04-29 0:55 ` Chris Mason
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=5358B996.4060102@aeb.io \
--to=adam@aeb.io \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).