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] [day] [month] [year] [list]
Date:	Mon, 27 Apr 2015 10:06:22 +0200
From:	Richard Weinberger <richard@....at>
To:	Dolev Raviv <draviv@...eaurora.org>
CC:	linux-mtd@...ts.infradead.org, linux-ext4@...r.kernel.org,
	'Tanya Brokhman' <tlinder@...eaurora.org>
Subject: Re: planning general storage capacity for y fs

Am 27.04.2015 um 09:55 schrieb Dolev Raviv:
> Thanks Richard!
> Let me rephrase the question: In the past I knew there was a rule of thumb, 'leave free 30% of the storage space'. Nowadays I couldn't find any reference to this.

Most likely because this is and was always kind of superstition. ;)
An almost full filesystems has to do more to find free space, but I don't dare to
give rules of thumb.

> I was wondering, is there a known point in UBIFS (or ext4), where leaving less free storage space, that performance is dropping? Maybe a ratio of free-occupied is not the right way to look at it, but to leave a certain size free (e.g. 50MB)?

I don't think so. Maybe Ted can give you more details on ext4.
For UBIFS I'd say, figure yourself. i.e. run benchmarks...

Thanks,
//richard
--
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