All of lore.kernel.org
 help / color / mirror / Atom feed
From: Contact <neitsab@ovh.fr>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
	"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 16:37:54 +0200	[thread overview]
Message-ID: <5353DBC2.5080708@ovh.fr> (raw)
In-Reply-To: <alpine.LFD.2.00.1404181042200.2128@localhost.localdomain>

Le ven. 18 avril 2014 10:45:03 CEST, Lukáš Czerner a écrit :
>
> The way you're using dd for this purpose is wrong. I
> said that dd can write to the file without truncating it first, but
> it's not doing it by default. You have to use 'notrunc' see man
> page. But I think that it would not have made a difference anyway.
>
Thansk, I stand corrected. I'll try it to see whether I can get better 
results with it.

> And even though you can turn off backup superblock you
> can not turn off writing group descriptors.
>
While we're at it, how can I do this? I searched the 
mkfs.ext4/mke2fs.conf/ext4/tune2fs man pages for the option to turn off 
writing backup superblock you mentioned, however the closest I found is 
tune2fs -O ^sparse_super which is part of the defaults mke2fs.conf 
options... Could you point me at it so that I can try to get this 
source of non-contiguity away?

Thanks,
-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 14:37 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 [this message]
2014-04-20 19:01         ` Theodore Ts'o
2014-04-20 19:38           ` Contact
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=5353DBC2.5080708@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.