From: Christoph Hellwig <hch@infradead.org>
To: Andreas Dilger <aedilger@gmail.com>
Cc: Jeff liu <jeff.liu@oracle.com>,
Yongqiang Yang <xiaoqiangnk@gmail.com>,
Dave Young <hidave.darkstar@gmail.com>, Ted Ts'o <tytso@mit.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: [BUG] copy file result with zero
Date: Sun, 2 Oct 2011 07:54:38 -0400 [thread overview]
Message-ID: <20111002115438.GA24073@infradead.org> (raw)
In-Reply-To: <89E75765-AC24-4EF4-9547-6EE7A1A38B5A@dilger.ca>
On Sun, Oct 02, 2011 at 12:59:22AM -0700, Andreas Dilger wrote:
> My understanding is that cp uses the blocks count to determine whether the file is sparse or not. In the case of delayed allocation (where blocks are not yet allocated, if they are not reflected in the i_blocks count) it might mistakenly think that the file is sparse.
Ext4 fortunatley is smart enough to add the delalloc blocks to st_blocks
for state, just like all other filesystems implementing delayed
allocations.
next prev parent reply other threads:[~2011-10-02 11:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 14:01 [BUG] copy file result with zero Dave Young
2011-10-01 14:39 ` Ted Ts'o
2011-10-01 23:37 ` Dave Young
2011-10-02 6:41 ` Jeff liu
2011-10-02 7:59 ` Andreas Dilger
2011-10-02 7:14 ` Jeff liu
2011-10-02 8:46 ` Dave Young
2011-10-02 11:54 ` Christoph Hellwig [this message]
2011-10-03 9:26 ` Yongqiang Yang
2011-10-03 13:11 ` Lukas Czerner
2011-10-03 14:18 ` Ted Ts'o
2011-10-03 15:51 ` Lukas Czerner
2011-10-02 8:02 ` Andreas Dilger
2011-10-02 8:43 ` Dave Young
[not found] ` <CABqxG0eMarBn_8xHCOZPq3pae4K01C51Rmxdox7uZr0gWOHGGw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-03 11:08 ` Pádraig Brady
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=20111002115438.GA24073@infradead.org \
--to=hch@infradead.org \
--cc=aedilger@gmail.com \
--cc=hidave.darkstar@gmail.com \
--cc=jeff.liu@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xiaoqiangnk@gmail.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