Re: Mounted compress-force=zlib, compresses when files copied in, but not when written directly by application

On Wed, Dec 05, 2012 at 05:42:51PM +, Thorn Roby wrote: > My previous reply was incorrect in one point - the data is never copied from > the transaction log into the sparse datafiles, instead the application writes > the same data independently to both locations. > Also, I failed to mention t

Re: Question about btrfs snapshot delay and rm -rf delay

On Wed, Dec 05, 2012 at 11:56:27PM -0500, Sylvain Alain wrote: > Hi everyone, I'm running btrfs since octobre 2012 and I would like to > understand 2 behavior that I noticed. > > 1. When I delete a big directory, sometimes it can hang my box for 1 > minutes or so, it seems that's the btrfs lock my

Re: Question about btrfs snapshot delay and rm -rf delay

Maybe you can use systemtap to track what's going on. 2012/12/6 Sylvain Alain : > Hi everyone, I'm running btrfs since octobre 2012 and I would like to > understand 2 behavior that I noticed. > > 1. When I delete a big directory, sometimes it can hang my box for 1 > minutes or so, it seems that's

Re: send/receive questions

What the emacs sendrecv.el does? 2012/12/6 james northrup : > more important, when will the emacs sendrecv.el be ready? > > > On Tue, Dec 4, 2012 at 9:29 PM, Ins wrote: >> >> Hello all, >> >> The implementation of send/receive is very cool. >> >> But I wonder whether there are any plans t

Re: send/receive questions

more important, when will the emacs sendrecv.el be ready? On Tue, Dec 4, 2012 at 9:29 PM, Ins wrote: > Hello all, > > The implementation of send/receive is very cool. > > But I wonder whether there are any plans to support these features > below or not, > > 1. support writable subvolu

segmentation-fault in btrfsck (git-version)

Dear all, thanks for developing btrfsck! Now, I'd like to contribute -as far as I can. I'm not a developer, but I do have some linux-experience. I've been using btrfsck on two 3TB HDDs (mirrored) for a while now under Kernel 3.0. Now it's corrupt. I had some hard resets of the machine -which m

RE: Mounted compress-force=zlib, compresses when files copied in, but not when written directly by application

My previous reply was incorrect in one point - the data is never copied from the transaction log into the sparse datafiles, instead the application writes the same data independently to both locations. Also, I failed to mention that the files are memmapped, and it's possible that the write opera

RE: Mounted compress-force=zlib, compresses when files copied in, but not when written directly by application

Thanks for your response. Yes, the rsync copies a number of the 2GB files written by the same database software on another system on XFS, and compression is successful. These files consist mostly of plain text log output and are highly compressible (4:1 via zlib). When the database is running lo

3.7.0-rc8 btrfs locking issue

Hi, I'm hitting a btrfs locking issue with 3.7.0-rc8. The btrfs filesystem in question is backing a Ceph OSD under a heavy write load from many cephfs clients. I reported this issue a while ago: http://www.spinics.net/lists/linux-btrfs/msg19370.html when I was testing what I thought might be

MDaemon Notification -- Attachment Removed

--- MDaemon has detected restricted attachments within an email message --- >From : linux-btrfs@vger.kernel.org To: bomsa...@bird.in Subject : Returned mai

[PATCH 6/6] Btrfs: fix wrong return value of btrfs_truncate_page()

ret variant may be set to 0 if we read page successfully, but it might be released before we lock it again. On this case, if we fail to allocate a new page, we will return 0, it is wrong, fix it. Signed-off-by: Miao Xie --- fs/btrfs/inode.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 5/6] Btrfs: punch hole past the end of the file

Since we can pre-allocate the space past EOF, we should be able to reclaim that space if we need. This patch implements it by removing the EOF check. Though the manual of fallocate command says we can use truncate command to reclaim the pre-allocated space which past EOF, but because truncate comm

[PATCH 4/6] Btrfs: fix the page that is beyond EOF

Steps to reproduce: # mkfs.btrfs # mount # dd if=/dev/zero of=/ bs=512 seek=5 count=8 # fallocate -p -o 2048 -l 16384 / # dd if=/dev/zero of=/ bs=4096 seek=3 count=8 conv=notrunc,nocreat # umount # dmesg WARNING: at fs/btrfs/inode.c:7140 btrfs_destroy_inode+0x2eb/0x330 The reason is th

[PATCH 3/6] Btrfs: fix off-by-one error of the same page check in btrfs_punch_hole()

(start + len) is the start of the adjacent extent, not the end of the current extent, so we should not use it to check the hole is on the same page or not. Signed-off-by: Miao Xie --- fs/btrfs/file.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/file.c b/fs/btr

[PATCH 2/6] Btrfs: fix missing reserved space release in error path of delalloc reservation

We forget to release the reserved space in the error path of delalloc reservatiom, fix it. Signed-off-by: Miao Xie --- fs/btrfs/extent-tree.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index 3d3e2c1..1cd71b2 100644 --- a/fs/btrfs/ex

[PATCH 1/6] Btrfs: don't auto defrag a file when doing directIO

If we runt the direct IO, we should not run auto defrag, because it may introduce buffered IO vs direcIO problem, and make direct IO slow down. Signed-off-by: Miao Xie --- fs/btrfs/inode.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 5fc0990..b0