Displaying 5 results from an estimated 5 matches for "opt_recoveri".
Did you mean:
opt_recovery
2011 Nov 11
1
[PATCH] btrfs: rename the option to nospace_cache
Rename no_space_cache option to nospace_cache to be more consistent with
the rest, where the simple prefix ''no'' is used to negate an option.
The option has been introduced during the -rc1 cycle and there are has not been
widely used, so it''s safe.
Signed-off-by: David Sterba <dsterba@suse.cz>
---
fs/btrfs/super.c | 4 ++--
1 files changed, 2 insertions(+), 2
2012 May 07
0
[PATCH V2] btrfs: fix message printing
Fix various messages to include newline and module prefix.
Signed-off-by: Daniel J Blueman <daniel@quora.org>
---
fs/btrfs/super.c | 8 ++++----
fs/btrfs/volumes.c | 6 +++---
fs/btrfs/zlib.c | 8 ++++----
3 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index c5f8fca..c0b8727 100644
--- a/fs/btrfs/super.c
+++
2013 Feb 07
8
[RFC] Btrfs: Allow the compressed extent size limit to be modified v2
Provide for modification of the limit of compressed extent size
utilizing mount-time configuration settings.
The size of compressed extents was limited to 128K, which
leads to fragmentation of the extents (although the extents
themselves may still be located contiguously). This limit is
put in place to ease the RAM required when spreading compression
across several CPUs, and to make sure the
2012 Jun 15
6
[PATCH] Btrfs: add "nocompress" mount option
In btrfs if we mount with "compress" we have no way to disable
compressing by remounting
(mount -o remount /mnt/btrfs), only by unmounting and mounting without
"compress".
This patch adds "nocompress" mount option which can be used to remount
the filesystem without compression:
# mount -o remount,nocompress /mnt/btrfs
This option is usefull in cases when we have a
2012 May 27
0
[RFC PATCH] Decrease Metadata Fragment Using A Caterpillar Band Method
I made an attempt to partly decrease fragment by using a preallocated
area of multiple size of a std blocksize for a tree block when it is COWed.
The basic idea is that if any a tree block need to be created,
we offer, say, 2 or 4 multiples of a std blocksize for it, then use the
first block in the continuous blocks. When this block need a cow in the
future, a new free block in these continuous