From: Jay Ashworth <jra@baylink.com>
To: xfs@oss.sgi.com
Subject: Re: A short digression on FOSS (Re: understanding speculative preallocation)
Date: Sat, 27 Jul 2013 21:50:43 -0400 (EDT) [thread overview]
Message-ID: <6559720.2408.1374976243593.JavaMail.root@benjamin.baylink.com> (raw)
In-Reply-To: <043835EA-08D4-4945-92F0-173BFE2C604C@gmail.com>
----- Original Message -----
> From: "aurfalien" <aurfalien@gmail.com>
> > If Dave thinks *that* question is out of bounds, then when I do my
> > rotating reformat to recover from my recent power supply induced
> > crash, XFS will not be the file system I pick off the pulldown menu
> > to reformat with.
>
> Well, you'll be missing out. Who cares what any one thinks in terms of
> Free vs Fee paradigms, XFS is simply a rockin FS.
You bet; we've put dozens of TB on and off it in 9 years of running
MythTV. And in the 2 instances where it's blown its brains out,
Dave, in particular, has been very helpful in putting it back together;
it's a little unnerving, actually, to look the handle up after an
IRC chat and discover you had the lead dev on the phone.
> I was really intrigued by his and Linus's back and forth not to long
> ago, some great knowledge for sure.
I was watching that; I didn't see it end. Did it?
> This list is great so filter whats applicable and toss the rest in a
> bit bucket.
As it happens, though, My Sister's DVR is *not* the only machine with
Really Big Filesystems on it*, and it really does matter to me what the
development policies are on critical subsystems like this; hence my
query above.
I really really *love* SuSE, after 8 years, but they've made a critical
change I simply can't tolerate for commercial use, and I'm going to have
to pick a new distro. (And anyone who says "well, just switch to SLES"
either forgets that that's $1200/server/year, or forgets where Linux came
from in the first place...)
CentOS is the only thing that's anywhere close.
* ... for which I'm responsible ...
Cheers
-- jra
--
Jay R. Ashworth Baylink jra@baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA #natog +1 727 647 1274
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-28 1:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 7:23 understanding speculative preallocation jbr
2013-07-26 11:50 ` Dave Chinner
2013-07-26 17:40 ` Jason Rosenberg
2013-07-26 19:27 ` Stan Hoeppner
2013-07-26 19:43 ` A short digression on FOSS (Re: understanding speculative preallocation) Jay Ashworth
2013-07-27 3:52 ` Stan Hoeppner
2013-07-27 21:00 ` Jay Ashworth
2013-07-28 1:38 ` aurfalien
2013-07-28 1:50 ` Jay Ashworth [this message]
2013-07-28 2:08 ` aurfalien
2013-07-28 2:21 ` Jay Ashworth
2013-07-28 5:09 ` Purpose of the XFS list -- was: " Stan Hoeppner
2013-07-28 15:45 ` Jay Ashworth
2013-08-14 17:01 ` Emmanuel Florac
2013-07-28 7:18 ` Stefan Ring
2013-07-28 15:48 ` Jay Ashworth
2013-07-29 0:02 ` Dave Chinner
2013-07-29 0:06 ` Jay Ashworth
2013-07-29 2:41 ` Dave Chinner
2013-07-29 3:12 ` Eric Sandeen
2013-07-29 4:11 ` Stan Hoeppner
2013-07-29 14:33 ` Jay Ashworth
2013-07-29 15:25 ` Dave Howorth
2013-07-29 3:38 ` Keith Keller
2013-07-29 4:32 ` Eric Sandeen
2013-07-29 4:57 ` Keith Keller
2013-07-29 13:38 ` Eric Sandeen
2013-07-29 18:15 ` Keith Keller
2013-07-29 14:24 ` Jay Ashworth
2013-07-29 14:36 ` Jay Ashworth
2013-07-29 14:57 ` Eric Sandeen
2013-07-29 15:30 ` Jay Ashworth
2013-07-29 17:05 ` Eric Sandeen
2013-07-29 0:00 ` Dave Chinner
2013-07-28 5:15 ` Michael L. Semon
2013-07-26 20:38 ` understanding speculative preallocation Jason Rosenberg
2013-07-26 20:50 ` Ben Myers
2013-07-26 21:04 ` Jason Rosenberg
2013-07-26 21:11 ` Jason Rosenberg
2013-07-26 21:42 ` Ben Myers
2013-07-27 1:30 ` Dave Chinner
2013-07-28 2:19 ` Jason Rosenberg
2013-07-29 0:04 ` Dave Chinner
2013-07-26 21:45 ` Eric Sandeen
2013-07-27 4:26 ` Keith Keller
2013-07-27 1:26 ` 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=6559720.2408.1374976243593.JavaMail.root@benjamin.baylink.com \
--to=jra@baylink.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.