search for: lizf

Hello, I have a doubt about the plotting position of the theoretical quantile for the qqnorm command in R. Let F be the theoretical distribution of Y, we observed a sample of size n, y1,y2, ..., yn. We then sort it and comspare these empirical quantiles to the expected ones from F. For the plotting poition, there are several options: 1. i/(n+1) 2. (i-.375)/(n+.25) 3. (i- .3175)/ (n + .365) etc.

The biggest one is a fix for fstrim, and there''s a fix for on-disk free space cache. Others are small fixes and cleanups. The last three have been sent weeks ago. The patchset is also available in this repo: git://repo.or.cz/linux-btrfs-devel.git for-chris Note there''s a small confict with Al Viro''s vfs changes. Li Zefan (11): Btrfs: add pinned extents to

Kernel 3.1-rc8 btrfs-progs-0.19 mount options: noatime,autodefrag (space_cache is enabled) There are snapshots present on the filesystem. When I do a btrfs fi defrag on a file, the file becomes much more fragmented. The end result can be a file with 20k times more fragments than before. Initially I thought the extents were just smaller but were next to each other, so I checked with both

It''s safe and easy to do so, provided the ranges don''t overlap. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- fs/btrfs/ioctl.c | 23 ++++++++++++++++------- 1 files changed, 16 insertions(+), 7 deletions(-) diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c index 0b06a5c..8fcd671 100644 --- a/fs/btrfs/ioctl.c +++ b/fs/btrfs/ioctl.c @@ -2223,8 +2223,6 @@ static noinline long btrfs_i...

...ction() was triggered while balancing. The cause is btrfs_relocate_chunk() started a transaction and then called iput() on the inode that stores free space cache, and iput() called btrfs_start_transaction() again. Reported-by: Tsutomu Itoh <t-itoh@jp.fujitsu.com> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- fs/btrfs/inode.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 02ff4a1..4e9aa28 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -3646,7 +3646,7 @@ void btrfs_evict_inode(struct inode *inode) btrf...

...plement snapshow-aware defrag: We set the EXTENT_DEFRAG flag when dirtying the extents that need defragmented, so later on writeback thread can differentiate between normal writeback and writeback started by defragmentation. This patch is used for the latter one. Originally patch by Li Zefan <lizf@cn.fujitsu.com> Signed-off-by: Liu Bo <bo.li.liu@oracle.com> --- fs/btrfs/extent_io.c | 8 ++++++++ fs/btrfs/extent_io.h | 2 ++ fs/btrfs/file.c | 4 ++-- fs/btrfs/inode.c | 20 ++++++++++++-------- fs/btrfs/ioctl.c | 8 ++++---- 5 files changed, 28 insertions(+...

...# dd if=/dev/zero of=/mnt/tmp bs=4K count=1 conv=notrunc oflag=direct dd: writing `/mnt/tmp'': Input/output error 1+0 records in 0+0 records out btrfs_ordered_update_i_size() may return 1, but btrfs_endio_direct_write() mistakenly takes it as an error. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- fs/btrfs/inode.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 0ccc743..3bd35fe 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -5785,8 +5785,7 @@ again: if (test_bit(BTRFS_ORDERED_NOCOW, &o...

...btrfs filesystems mounted with lzo option. - Allow to turn on lzo compression for defrag operation: # btrfs filesystem defragment -c[zlib, lzo] <file> Note: "-c zlib" will fail, because that''s how getopt() works for optional arguments. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- The lzo patchset for kernel code can be found here: http://marc.info/?l=linux-btrfs&m=128799063215123&w=2 --- btrfs.c | 2 +- btrfs_cmds.c | 24 ++++++++++++++++++++---- ctree.h | 18 +++++++++++------- ioctl.h | 9 ++++++++- 4 files chang...

Hi Li, >----Messaggio originale---- >Da: lizf@cn.fujitsu.com >Data: 30/11/2010 8.03 >A: <kreijack@libero.it> >Cc: <linux-btrfs@vger.kernel.org> >Ogg: Re: [PATCH 5/5] btrfs: Add ioctl to set snapshot readonly/writable > >Goffredo Baroncelli wrote: >> Hi Li, >> >> On Monday, 29 November, 2010, Li...

Hi! With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it trimmed: merkaba:~> fstrim -v /boot /boot: 224657408 bytes were trimmed merkaba:~> fstrim -v /boot /boot: 0 bytes were trimmed But BTRFS does not: merkaba:~> fstrim -v / /: 4431613952 bytes were trimmed merkaba:~> fstrim -v / /: 4341846016 bytes were trimmed Is it planned to add this feature to BTRFS

The first four bytes is the length of all data chunks, and the first four bytes of each chunk is the length of compressed chunk data, even when there''s only one chunk, which is the case for inline extents. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- fs/btrfs/snappy.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/fs/btrfs/snappy.c b/fs/btrfs/snappy.c index d6bd607..35b877e 100644 --- a/fs/btrfs/snappy.c +++ b/fs/btrfs/snappy.c @@ -392,12 +392,16 @@ static int btrfs_snappy_decompress(struct l...

...7905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <liang.li@windriver.com> Liang Tang...

...intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <liang.li@windriver.com> Liang Tang...

...intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <liang.li@windriver.com> Liang Tang...

...intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <liang.li@windriver.com> Liang Tang...

...intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <liang.li@windriver.com> Liang Tang...

...intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zefan <lizfan@huawei.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <lia...

...intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zefan <lizfan@huawei.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <lia...

...intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zefan <lizfan@huawei.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <lia...

...intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com> Li Zefan <lizefan@huawei.com> Li Zefan <lizf@cn.fujitsu.com> Li Zefan <lizfan@huawei.com> Li Zhong <zhong@linux.vnet.ibm.com> Li, Zhen-Hua <zhen-hual@hp.com> Liam Girdwood <liam.r.girdwood@intel.com> Liam Girdwood <liam.r.girdwood@linux.intel.com> Liam Girdwood <lrg@ti.com> Liang Li <lia...