From: Li Zefan <lizf@cn.fujitsu.com>
To: Stephane Chazelas <stephane_chazelas@yahoo.fr>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs fi defrag -c
Date: Fri, 28 Oct 2011 10:25:54 +0800 [thread overview]
Message-ID: <4EAA12B2.8070007@cn.fujitsu.com> (raw)
In-Reply-To: <20111027192022.GD4389@yahoo.fr>
Stephane Chazelas wrote:
> I don't quite understand the behavior of "btrfs fi defrag"
>
> ~# truncate -s2G ~/a
> ~# mkfs.btrfs ~/a
> nodesize 4096 leafsize 4096 sectorsize 4096 size 2.00GB
> ~# mount -o loop ~/a /mnt/1
> /mnt/1# cd x
> /mnt/1# df -h .
> Filesystem Size Used Avail Use% Mounted on
> /dev/loop1 2.0G 64K 1.8G 1% /mnt/1
> /mnt/1# yes | head -c400M > a
> /mnt/1# df -h .
> Filesystem Size Used Avail Use% Mounted on
> /dev/loop1 2.0G 64K 1.8G 1% /mnt/1
> /mnt/1# sync
> /mnt/1# df -h .
> Filesystem Size Used Avail Use% Mounted on
> /dev/loop1 2.0G 402M 1.4G 23% /mnt/1
> /mnt/1# btrfs fi defrag -c a
>
> (exit status == 20 BTW).
>
int do_defrag(int ac, char **av)
{
...
return errors + 20;
}
This doesn't make sense to me.
> (20)/mnt/1# sync
> /mnt/1# df -h .
> Filesystem Size Used Avail Use% Mounted on
> /dev/loop1 2.0G 415M 994M 30% /mnt/1
>
> No space gain, even lost 15M or 400M depending on how you look at it.
>
Here's mine:
# df . -h
Filesystem Size Used Avail Use% Mounted on
/home/lizf/tmp/a 2.0G 409M 1.4G 23% /mnt
And I was not suprised, as there's a regression.
With this fix:
http://marc.info/?l=linux-btrfs&m=131495014823121&w=2
# df . -h
Filesystem Size Used Avail Use% Mounted on
/home/lizf/tmp/a 2.0G 14M 1.8G 1% /mnt
next prev parent reply other threads:[~2011-10-28 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 19:20 btrfs fi defrag -c Stephane Chazelas
2011-10-28 2:25 ` Li Zefan [this message]
2011-10-28 10:23 ` Stephane CHAZELAS
2011-10-28 3:02 ` Li Zefan
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=4EAA12B2.8070007@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stephane_chazelas@yahoo.fr \
/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.