All of lore.kernel.org
 help / color / mirror / Atom feed
From: Contact <neitsab@ovh.fr>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Make huge files strictly contiguous (fallocate, bigalloc, e4defrag...)
Date: Sun, 20 Apr 2014 21:38:30 +0200	[thread overview]
Message-ID: <53542236.9030201@ovh.fr> (raw)
In-Reply-To: <20140420190146.GB29727@thunk.org>

Le dim. 20 avril 2014 21:01:46 CEST, Theodore Ts'o a écrit :
>
> This requires recompiling e2fsprogs using the tip of the maint branch,
> as I had suggested earlier (and which you had ruled out because you
> didn't want to build your own e2fsprogs from source).
>
Thanks, that explains why I wasn't able to find this option in regular 
e2fsprogs.

> Once you do this, and you put the following in
>
> 	hugefiles = {
> 		features = extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize,^resize_inode,sparse_super2
> 		hash_alg = half_md4
> 		num_backup_sb = 0
> 		packed_meta_blocks = 1
> 		flex_bg_size = 262144
> 		inode_ratio = 4194304
> 		make_hugefiles = 1
> 		hugefiles_dir = /boot
> 		hugefiles_name = contig-files
> 		hugefiles_digits = 1
> 		hugefiles_size = 256M
> 		num_hugefiles = 3
> 	}
>
> Using the sparse_super2 feature and setting num_backup_sb=0 disables
> the backup superblocks.  Then setting flex_bg_size to a very large
> value (262144 in this case), will force all of the allocation bitmaps
> and inodetables to the very beginning of the file system.
>
The tip and stanza look very useful though, I'll reconsider retrieving 
and compiling maint branch to try, thanks.

> Note that because this uses a new compat feature, "sparse_super2", if
> you use the new mke2fs to create such a file system, you will also
> need to make sure the file system is checked using a version of e2fsck
> that supports this new feature as well.  No kernel changes are
> required to support this, though.
>
Any plans to get this feature into master at some point in the 
development?

--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-04-20 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17  2:18 Make huge files strictly contiguous (fallocate, bigalloc, e4defrag...) Contact
2014-04-17 12:04 ` Lukáš Czerner
2014-04-17 15:24 ` Theodore Ts'o
2014-04-17 18:41   ` Contact
2014-04-17 20:11     ` Contact
2014-04-18  8:45     ` Lukáš Czerner
2014-04-20 14:37       ` Contact
2014-04-20 19:01         ` Theodore Ts'o
2014-04-20 19:38           ` Contact [this message]
2014-04-20 20:00             ` Theodore Ts'o

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=53542236.9030201@ovh.fr \
    --to=neitsab@ovh.fr \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.