From: Ric Wheeler <ricwheeler@gmail.com>
To: Sandon Van Ness <sandon@van-ness.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Is >16TB support considered stable?
Date: Tue, 01 Jun 2010 10:18:42 -0400 [thread overview]
Message-ID: <4C0516C2.8070007@gmail.com> (raw)
In-Reply-To: <4C017BAC.2000000@van-ness.com>
On 05/29/2010 04:40 PM, Sandon Van Ness wrote:
> On 05/28/2010 09:32 PM, Stewart Smith wrote:
>
>> On Fri, 28 May 2010 19:47:41 -0700, Sandon Van Ness<sandon@van-ness.com> wrote:
>>
>>
>>> able to allocate blocks or memory (it was a while back so I forget). I
>>> spent 24 hours defraging it getting the fragmentation down from like
>>> 99.9995% to 99.2% and the problem went away. XFS seems to excessively
>>> fragment (that horribly fragmented system was running mythtv and after
>>> switching to JFS I see way less fragmented files).
>>>
>>>
>> MythTV's IO path is well... hacked to get around all of ext3's quirks.
>>
>> You can:
>> - mount XFS with allocsize=64m (or similar)
>> - possibly use the XFS filestreams allocator
>> - comment out the fsync() in the mythtv tree
>> - LD_PRELOAD libeatmydata for myth.
>>
>> it turns out that writing a rather small amount of data and fsync()ing
>> (and repeating 1,000,000 times) makes the allocator cry a bit with
>> default settings. Especially if you were recording a few things at once.
>>
>>
> Well JFS has absolutely no problems with files created via mythtv. I
> also am not going to be using mythtv on this system at all and I was
> just giving some examples of my past experience with XFS and why I will
> never use it. Anyway please no more XFS discussion or suggestions for
> other file-systems I was mainly curious on what the stability or peoples
> experiences are with ext4 and 64-bit addressing. I have long since
> decided I will never run XFS again as I can't ever trust it with my data
> again. I mainly wrote this list to try to find out what the opinions
> were on ext4 with>16 TiB file-systems.
>
>
The short answer is no.
Ric
next prev parent reply other threads:[~2010-06-01 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 16:52 Is >16TB support considered stable? Sandon Van Ness
2010-05-28 19:39 ` Ric Wheeler
2010-05-29 2:47 ` Sandon Van Ness
2010-05-29 4:32 ` Stewart Smith
2010-05-29 20:40 ` Sandon Van Ness
2010-06-01 14:18 ` Ric Wheeler [this message]
2010-06-01 16:30 ` Eric Sandeen
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=4C0516C2.8070007@gmail.com \
--to=ricwheeler@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandon@van-ness.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;
as well as URLs for NNTP newsgroup(s).