[PATCH v2 2/3] btrfs: typo: 'btrfS' -> 'btrfs'

Signed-off-by: Sergei Trofimovich --- fs/btrfs/dir-item.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fs/btrfs/dir-item.c b/fs/btrfs/dir-item.c index c62f02f..dec9348 100644 --- a/fs/btrfs/dir-item.c +++ b/fs/btrfs/dir-item.c @@ -452,7 +452,7 @@ int verify_dir_item(s

[PATCH v2 3/3] btrfs: fix typo 'testeing' -> 'testing'

Signed-off-by: Sergei Trofimovich --- fs/btrfs/inode.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 7cd8ab0..72650ce 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -1310,7 +1310,7 @@ static int btrfs_set_bit_hook(st

[PATCH v2 1/3] btrfs: don't spin in shrink_delalloc if there is nothing to free

Observed as a large delay when --mixed filesystem is filled up. Test example: 1. create tiny --mixed FS: $ dd if=/dev/zero of=2G.img seek=$((2048 * 1024 * 1024 - 1)) count=1 bs=1 $ mkfs.btrfs --mixed 2G.img $ mount -oloop 2G.img /mnt/ut/ 2. Try to fill it up: $ dd if=/dev/urandom of=10M

[PATCH v2 0/3] btrfs: don't spin in shrink_delalloc if there is nothing to free

The really interesting commit is [PATCH 1/3] btrfs: don't spin in shrink_delalloc if there is nothing to free which fixes hogs on ENOSPC for me. The rest of patches are cleanup. Change since v1: - Added Josef's Reviewed-by - Fixed my MTA and patch numbering Thanks! -- To unsubscribe from thi

[PATCH v2 3/3] btrfs: fix typo 'testeing' -> 'testing'

From: Sergei Trofimovich Signed-off-by: Sergei Trofimovich --- fs/btrfs/inode.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 7cd8ab0..72650ce 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -1310,7 +1310,7 @@ stati

[PATCH v2 2/3] btrfs: typo: 'btrfS' -> 'btrfs'

From: Sergei Trofimovich Signed-off-by: Sergei Trofimovich --- fs/btrfs/dir-item.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fs/btrfs/dir-item.c b/fs/btrfs/dir-item.c index c62f02f..dec9348 100644 --- a/fs/btrfs/dir-item.c +++ b/fs/btrfs/dir-item.c @@ -452,7 +452

[PATCH v2 1/3] btrfs: don't spin in shrink_delalloc if there is nothing to free

From: Sergei Trofimovich Observed as a large delay when --mixed filesystem is filled up. Test example: 1. create tiny --mixed FS: $ dd if=/dev/zero of=2G.img seek=$((2048 * 1024 * 1024 - 1)) count=1 bs=1 $ mkfs.btrfs --mixed 2G.img $ mount -oloop 2G.img /mnt/ut/ 2. Try to fill it up:

[PATCH v2 0/3] btrfs: don't spin in shrink_delalloc if there is nothing to free

From: Sergei Trofimovich The really interesting commit is [PATCH 1/3] btrfs: don't spin in shrink_delalloc if there is nothing to free which fixes hogs on ENOSPC for me. The rest of patches are cleanup. Change since v1: - Added Josef's Reviewed-by - Fixed my MTA and patch numbering Thanks!

Re: [PATCH 3/4] btrfs: don't spin in shrink_delalloc if there is nothing to free

On Mon, 09 May 2011 12:00:28 -0400 Josef Bacik wrote: > On 05/07/2011 05:29 PM, sly...@gmail.com wrote: > > Observed as a large delay when --mixed filesystem is filled up. > > Test example: > > 1. create tiny --mixed FS: > > $ dd if=/dev/zero of=2G.img seek=$((2048 * 1024 * 1024 - 1)) count=1

Re: "btrfs filesystem label" command

Hi, I suppose that you are familiar with 'git' and the standard unix command (like cd, make...). The quick way is the following: $ cd /tmp $ git clone -b label \ http://cassiopea.homelinux.net/git/btrfs-progs-unstable.git $ cd btrfs-progs-unstable.git $ make $ ./btrfs Hoping that this m

Lockdep warning in btrfs_clear_lock_blocking

Hi, I've hit this lockdep warning, 2.6.39rc6. Single btrfs partition, 30GB, filled with 2GB, "compress-force=lzo", warning trigered after normal copy+du. Happened only once. [Might be a false positive.] david [14547.128565] = [14547.132010] [ INFO: po

Re: [PATCH, fixed] Prevent oopsing in posix_acl_valid()

Excerpts from Daniel J Blueman's message of 2011-05-10 01:42:45 -0400: > Hi Chris, > > On 4 May 2011 22:40, Josef Bacik wrote: > > On 05/03/2011 10:54 PM, Daniel J Blueman wrote: > >> > >> If posix_acl_from_xattr() returns an error code, a negative address is > >> dereferenced causing an oops; fi

Re: Compression: per filesystem, or per subvolume?

On Sun, May 8, 2011 at 8:38 PM, cwillu wrote: > It's by not-implemented-yet.  Mount options are still currently global to > the filesystem. Thanks for the info. I was testing combination of grub2, btrfs "/" without separate /boot, and lzo. Using lzo feels much faster compared to zlib, so right no