From: ching <lsching17@gmail.com>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: enquiry about defrag
Date: Mon, 10 Sep 2012 20:19:33 +0800 [thread overview]
Message-ID: <504DDAD5.8010908@gmail.com> (raw)
In-Reply-To: <504C861D.2020009@gmail.com>
On 09/09/2012 08:05 PM, ching wrote:
> On 09/09/2012 05:11 PM, Fajar A. Nugraha wrote:
>> On Sun, Sep 9, 2012 at 2:49 PM, ching <lsching17@gmail.com> wrote:
>>> On 09/09/2012 08:30 AM, Jan Steffens wrote:
>>>> On Sun, Sep 9, 2012 at 2:03 AM, ching <lsching17@gmail.com> wrote:
>>>>> 2. Is there any command for the fragmentation status of a file/dir ? e.g. fragment size, number of fragments.
>>>> Use the "filefrag" command, part of e2fsprogs.
>>>>
>>> my image is a 16G sparse file, after defragment, it still has 101387 extents, is it normal?
>> Is compression enabled? If so, yes, it's normal.
>>
> compression with lzo.
>
> thanks. i will retry with compression disabled when 3.6 is stable.
i just realize that it is possible to control compression per file by file attribute
http://radudi.com/index.php/2011/08/31/using-btrfs-per-file-and-per-directory-compression/
when i try to follow example above, no file attribute is shown (my mount option is rw,noatime,compress-force=lzo,space_cache,inode_cache)
$lsattr -V Linux.raw_image
lsattr 1.42.5 (29-Jul-2012)
---------------- Linux.raw_image
is there any official resource/web page for control compression per file by file attribute?
next prev parent reply other threads:[~2012-09-10 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 0:03 enquiry about defrag ching
2012-09-09 0:30 ` Jan Steffens
2012-09-09 7:49 ` ching
2012-09-09 9:11 ` Fajar A. Nugraha
2012-09-09 12:05 ` ching
2012-09-10 12:19 ` ching [this message]
2012-09-10 13:10 ` Liu Bo
2012-09-10 23:21 ` ching
2012-09-11 1:28 ` Li Zefan
2012-09-11 11:12 ` ching
2012-09-10 9:23 ` Alex Lyakas
2012-09-11 11:12 ` ching
2012-09-11 11:45 ` David Sterba
2012-09-11 23:33 ` ching
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=504DDAD5.8010908@gmail.com \
--to=lsching17@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
/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;
as well as URLs for NNTP newsgroup(s).