On 09/10/2012 09:10 PM, Liu Bo wrote: > On 09/10/2012 08:19 PM, ching wrote: >> 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 <lschin...@gmail.com> wrote: >>>>> On 09/09/2012 08:30 AM, Jan Steffens wrote: >>>>>> On Sun, Sep 9, 2012 at 2:03 AM, ching <lschin...@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? >> > FYI, git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git > >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in >> the body of a message to majord...@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> >
may i ask a stupid question, if i remove my "compress-force=lzo" option, will compression disabled for new written data? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
