From: Olivier Bonvalet <btrfs.list@daevel.fr>
To: Hubert Kario <hka@qbs.com.pl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-convert processing time
Date: Mon, 20 Feb 2012 14:41:33 +0100 [thread overview]
Message-ID: <4F424D8D.4030802@daevel.fr> (raw)
In-Reply-To: <20458953.qbO19NXijp@k85hala03>
On 20/02/2012 14:20, Hubert Kario wrote:
> On Monday 20 of February 2012 13:51:29 Olivier Bonvalet wrote:
>> Hi,
>>
>> I'm trying to convert two ext4 FS to btrfs, but I'm surprised by the
>> time needed to do that conversion.
>>
>> The first FS is on a 500GiB block device, and btrfs-convert is running
>> since more than 48h :
>> root 1978 25.6 47.7 748308 732556 ? D Feb18 944:44
>> btrfs-convert /dev/vg-backup/backup
>>
>> The second is on a 340GiB block device, and the processing time is similar :
>> root 30192 5.2 3.0 73180 61520 pts/0 R Feb18 121:04
>> btrfs-convert /dev/vg-balor/backup
>>
>>
>> Is it "normal", or is there a problem during the processing ?
>>
>> Thanks,
>> Olivier
>
> How much free space did those FS have? How many files were on them (was they
> dominated by small or large files)?
>
> Regards,
Lot of small files (like compressed email from Maildir), and lot of
hardlinks, and probably low free space (near 15% I suppose).
So I think I have my answer :)
Thanks
next prev parent reply other threads:[~2012-02-20 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 12:51 btrfs-convert processing time Olivier Bonvalet
2012-02-20 13:20 ` Hubert Kario
2012-02-20 13:41 ` Olivier Bonvalet [this message]
2012-02-20 13:50 ` Hubert Kario
2012-02-20 14:00 ` Fajar A. Nugraha
2012-02-20 14:12 ` Hubert Kario
2012-02-20 14:29 ` Olivier Bonvalet
2012-02-21 5:51 ` Fajar A. Nugraha
2012-02-22 16:55 ` Olivier Bonvalet
2012-03-30 19:23 ` Olivier Bonvalet
2012-03-31 20:50 ` Hubert Kario
2012-02-20 13:21 ` Hubert Kario
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=4F424D8D.4030802@daevel.fr \
--to=btrfs.list@daevel.fr \
--cc=hka@qbs.com.pl \
--cc=linux-btrfs@vger.kernel.org \
/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.