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
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A63A1F1.9040703@cox.net>
Date:	Sun, 19 Jul 2009 17:45:05 -0500
From:	Ron Johnson <ron.l.johnson@....net>
To:	linux-ext4@...r.kernel.org
Subject: Re: file allocation problem

On 2009-07-17 16:14, Andreas Dilger wrote:
[snip]
> 
> Well, this isn't quite correct.  The mballoc code only tries to allocate
> "large" files on power-of-two boundaries, where large is 64kB by default,
> but is tunable in /proc.  For smaller files it tries to pack them together
> into the same block, or into gaps that are exactly the size of the file.

How does ext4 act on growing files?  I.e., creating a tarball that, 
obviously, starts at 0 bytes and then grows to multi-GB?

-- 
Scooty Puff, Sr
The Doom-Bringer
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ