From: Gionatan Danti <g.danti@assyoma.it>
To: Maurizio Lombardi <mlombard@redhat.com>, linux-btrfs@vger.kernel.org
Cc: Duncan <1i5t5.duncan@cox.net>, g.danti@assyoma.it
Subject: Re: Question about fallocate
Date: Wed, 02 Jul 2014 16:04:29 +0200 [thread overview]
Message-ID: <53B4116D.9090504@assyoma.it> (raw)
In-Reply-To: <53B3E471.2010101@redhat.com>
> I am unable to reproduce the problem on kernel version 3.16.0-rc2
> using nodatacow.
I all,
I can confirm that with Fedora 20 x86_64 (kernel 3.14.9-200.fc20.x86_64)
the problem do not occour: using the nodatacow option leads to
un-fragmented file.
Sorry for the noise.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2014-07-02 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140702014130.47a5ba75@ws>
2014-07-02 10:36 ` Question about fallocate Gionatan Danti
2014-07-02 10:52 ` Maurizio Lombardi
2014-07-02 14:04 ` Gionatan Danti [this message]
2014-07-01 10:16 Gionatan Danti
2014-07-02 8:04 ` Duncan
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=53B4116D.9090504@assyoma.it \
--to=g.danti@assyoma.it \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=mlombard@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox