All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Traverse <bastien.traverse@gmail.com>
To: Andreas Dilger <adilger@dilger.ca>,
	Vitaliy Filippov <vitalif@yourcmc.ru>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: mke2fs options for large media archive filesystem
Date: Wed, 05 Feb 2014 17:45:34 +0100	[thread overview]
Message-ID: <52F26AAE.9010608@gmail.com> (raw)
In-Reply-To: <7A86A0B9-5C08-42C9-A136-010CAAE384A1@dilger.ca>

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-02-05 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02 16:20 mke2fs options for large media archive filesystem Bastien Traverse
2014-02-02 16:35 ` Vitaliy Filippov
2014-02-03  1:30   ` Andreas Dilger
2014-02-03  7:15     ` Vitaliy Filippov
2014-02-03 21:09       ` Andreas Dilger
2014-02-05 16:45         ` Bastien Traverse [this message]

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=52F26AAE.9010608@gmail.com \
    --to=bastien.traverse@gmail.com \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=vitalif@yourcmc.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.