linux-ext4 - Re: mke2fs options for large media archive filesystem

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 05 Feb 2014 17:45:34 +0100
From:	Bastien Traverse <bastien.traverse@...il.com>
To:	Andreas Dilger <adilger@...ger.ca>,
	Vitaliy Filippov <vitalif@...rcmc.ru>
CC:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: mke2fs options for large media archive filesystem

Le 02/02/2014 17:35, Vitaliy Filippov a écrit :
> I personally don't think you'll really benefit from bigalloc on a
> 1TB archive partition.

Le 03/02/2014 02:30, Andreas Dilger a écrit :
> I would say that bigalloc is probably not what you want for an
> archival system.

Thanks for the enlightenment! I'll leave bigalloc aside for this usage,
but I'll definitely keep it around for another use case that I wanted to
submit to the list (in a later message).

> Since you already know the average file size, using -i {average size}
> is what you want. The -N option is just a different way of specifying
> the same thing, the underlying filesystem ends up being the same.
>
> I would also recommend to allocate about 2x the inodes you think you >
will need. If there are suddenly thumbnails of the photos or key      >
photos for videos then you don't want to run out of inodes.

Thanks a lot, this is much helpful. It confirms my intent to go for a 2M
bytes-per-inode ratio so as to reach ~460k inodes (or twice as much as
I'll probably need).

Cheers, Bastien


--
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