From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: Sebastian Riemer <sebastian.riemer@profitbricks.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>,
Jeff Johnson <jeff.johnson@aeoncomputing.com>
Subject: Re: Best practice for large storage?
Date: Sat, 16 Feb 2013 13:48:20 +0100 (CET) [thread overview]
Message-ID: <10665743.0.1361018900938.JavaMail.root@zimbra> (raw)
In-Reply-To: <511E051A.9080004@profitbricks.com>
> On 14.02.2013 18:48, Jeff Johnson wrote:
> > Stable enough where it is being used at Lawrence Livermore Nat'l
> > Labs on
> > a 55PB Lustre resource.
> >
> > I've been using it on a pre-release Lustre 2.4 and I have not had
> > any
> > issues.
>
> ZFS completely fragments if you've got massive parallel write IO -
> especially with Solaris 11. You'll get only 2..3 MiB/s after some time
> as everything is stored completely random then. So if you don't really
> need these snapshots you shouldn't use ZFS. NILFS is also good for
> snapshots.
This won't be massive parallel I/O, just a fileserver with a limited amount of users. Also, can you document this claim?
Vennlige hilsener / Best regards
roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-02-16 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 17:28 Best practice for large storage? Roy Sigurd Karlsbakk
2013-02-14 17:33 ` Jeff Johnson
2013-02-14 17:39 ` Roy Sigurd Karlsbakk
2013-02-14 17:48 ` Jeff Johnson
2013-02-15 9:51 ` Sebastian Riemer
2013-02-16 12:48 ` Roy Sigurd Karlsbakk [this message]
2013-02-18 10:35 ` Sebastian Riemer
2013-02-16 5:40 ` Stan Hoeppner
2013-02-15 2:18 ` Chris Murphy
2013-02-16 7:09 ` Stan Hoeppner
[not found] <CAH3kUhFbR3coJSwPvqqOGrqcsvoJpdAPgAAiAgc_th1ym33DzA@mail.gmail.com>
2013-02-14 18:27 ` Roy Sigurd Karlsbakk
[not found] <CAH3kUhGVt1iyn9tt=2-+f6H++obOGSK3x0pBBPZV8CFUXjp5yw@mail.gmail.com>
2013-02-14 23:23 ` Roy Sigurd Karlsbakk
2013-02-14 23:42 ` Roberto Spadim
2013-02-15 1:01 ` Adam Goryachev
2013-02-15 1:13 ` Roberto Spadim
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=10665743.0.1361018900938.JavaMail.root@zimbra \
--to=roy@karlsbakk.net \
--cc=jeff.johnson@aeoncomputing.com \
--cc=linux-raid@vger.kernel.org \
--cc=sebastian.riemer@profitbricks.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