xfs
[Top] [All Lists]

fallocate bug?

To: xfs@xxxxxxxxxxx
Subject: fallocate bug?
From: Zhu Han <schumi.han@xxxxxxxxx>
Date: Mon, 7 May 2012 20:44:17 +0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=F7cWlZjav0CjpkkPwKAOvMzSg7cjgwVRoFhZ1q2bzik=; b=vzo0u7IpvjzNd3fMsP4X9le25iCPjqRvD5tGRmCKAftAy3YpYB68MsJb+piXwcl1fs 4tvVNHpBYGcZx1umaUREIuiSllUo+kRkG7hirN5zfsxpboCee/0qiUiLQ7f3hJI0s4zm Fecv9Rta2of9Ui6u5Kl9r7VVGfhmpBjAqBYAdeV/B71+5FYInNttv3ph11imdE0HgX/u wSFymK63o7lcAc7AKYU8jTGaggly1nimzt9NSLcPi+yvFQEmfV4BUljCv+6NO0NqwZAw BWHvvl2pjzK9O7CNMUFmC83Ih/8WabqKqyAmW24AvksTV0ehVhPNVrQ/ktKXgZk5LkXD 3xUg==
Seems like xfs of CentOS 6.X occupies much more storage space than desired if fallocate is used against the file. Here is the step to reproduce it:

By the way, is it normal when the file is moved around after the preallocated region is filled with data?

$ uname -r
2.6.32-220.7.1.el6.x86_64

$fallocate -n --offset 0 -l 1G file    ---->Write a little more data than the preallocated size

$ xfs_bmap -p -vv file
file:
 EXT: FILE-OFFSET      BLOCK-RANGE            AG AG-OFFSET              TOTAL FLAGS
   0: [0..2097151]:    2593408088..2595505239 21 (29420144..31517295) 2097152 10000

$ dd if=/dev/zero of=/tmp/file bs=1M count=1026 conv=fsync

$ xfs_bmap -p -vv file
file:
 EXT: FILE-OFFSET      BLOCK-RANGE            AG AG-OFFSET              TOTAL FLAGS
   0: [0..4194303]:    2709184016..2713378319 22 (23101408..27295711) 4194304 00000

$ du -h --apparent-size file
1.1G    file

$du -h file
2.0G

best regards,
韩竹(Zhu Han)
<Prev in Thread] Current Thread [Next in Thread>