| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87ljb3gwee.fsf@willster.local.flamingspork.com> Date: Sat, 29 May 2010 14:32:57 +1000 From: Stewart Smith <stewart@...mingspork.com> To: Sandon Van Ness <sandon@...-ness.com> Cc: linux-ext4@...r.kernel.org Subject: Re: Is >16TB support considered stable? On Fri, 28 May 2010 19:47:41 -0700, Sandon Van Ness <sandon@...-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. -- Stewart Smith -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists