Thank you! I see a lot of really useful changes. I've just updated
Rockstor testing repo to use 4.2.
On Thu, Sep 3, 2015 at 5:39 AM, David Sterba wrote:
> Hi,
>
> here goes anoher release. There are many cleanups/bugfixes and just a handful
> of user-visible improvements.
>
>
We're also going to load the free space tree from caching_thread(), so
we should refactor some of the common code.
Signed-off-by: Omar Sandoval
---
fs/btrfs/ctree.h | 3 +++
fs/btrfs/extent-tree.c | 59 --
2 files changed,
The free space cache has turned out to be a scalability bottleneck on
large, busy filesystems. When the cache for a lot of block groups needs
to be written out, we can get extremely long commit times; if this
happens in the critical section, things are especially bad because we
block new
This tests the operations on the free space tree trying to excercise all
of the main cases for both formats. Between this and xfstests, the free
space tree should have pretty good coverage.
Signed-off-by: Omar Sandoval
---
fs/btrfs/Makefile | 3 +-
Sanity test the extent buffer bitmap operations (test, set, and clear)
against the equivalent standard kernel operations.
Signed-off-by: Omar Sandoval
---
fs/btrfs/extent_io.c | 34 ++
fs/btrfs/extent_io.h | 4 +-
The free space tree is updated in tandem with the extent tree. There are
only a handful of places where we need to hook in:
1. Block group creation
2. Block group deletion
3. Delayed refs (extent creation and deletion)
4. Block group caching
Signed-off-by: Omar Sandoval
---
Here's version 2 of the the free space B-tree patches, addressing
Josef's review from the last round, which you can find here:
http://www.spinics.net/lists/linux-btrfs/msg46713.html
Changes from v1->v2:
- Cleaned up a bunch of unnecessary instances of "if (ret) goto out; ret = 0"
- Added aborts
These are going to be used for the free space tree bitmap items.
Signed-off-by: Omar Sandoval
---
fs/btrfs/extent_io.c | 149 +++
fs/btrfs/extent_io.h | 6 +++
2 files changed, 155 insertions(+)
diff --git a/fs/btrfs/extent_io.c
The on-disk format for the free space tree is straightforward. Each
block group is represented in the free space tree by a free space info
item that stores accounting information: whether the free space for this
block group is stored as bitmaps or extents and how many extents of free
space exist
Now we can finally hook up everything so we can actually use free space
tree. On the first mount with the free_space_tree mount option, the free
space tree will be created and the FREE_SPACE_TREE read-only compat bit
will be set. Any time the filesystem is mounted from then on, we will
use the
Hi,
[447062.309251] Modules linked in: dm_mod netconsole ipt_REJECT
nf_reject_ipv4 xt_multiport iptable_filter ip_tables x_tables
cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative
bonding ext2 usbhid coretemp loop ehci_pci sb_edac ehci_hcd edac_core
i2c_i801 i2c_core usbcore
Hi, David and Zhao,
David Sterba wrote on 2015/09/03 15:17 +0200:
On Thu, Aug 27, 2015 at 09:44:05AM +0800, Zhao Lei wrote:
[...]
Thanks for the links and summary!
But it is still uncorrectable because neither kernel nor btrfsck can fix
it(only can report).
I'm curious if it' is possible
On Thu, Aug 27, 2015 at 09:44:05AM +0800, Zhao Lei wrote:
[...]
Thanks for the links and summary!
> But it is still uncorrectable because neither kernel nor btrfsck can fix
> it(only can report).
I'm curious if it' is possible to write code that would fix the problem,
eg. te relocate or shift
Hi,
here goes anoher release. There are many cleanups/bugfixes and just a handful
of user-visible improvements.
Thanks to all contributors!
enhancements:
* mkfs: do not create extra single chunks on multiple devices
* resize: try to guess the minimal size, 'inspect min-dev-size'
* qgroup
On Fri, Sep 04, 2015 at 09:29:45AM +0800, Zhao Lei wrote:
> Hi, Omar Sandoval
>
> [PATCH 7/9] have following compiler warning:
> fs/btrfs/tests/free-space-tree-tests.c: In function
> '__check_free_space_extents':
> fs/btrfs/tests/free-space-tree-tests.c:45: warning: 'offset' may be used
>
On Thu, Sep 03, 2015 at 12:44:26PM -0700, Omar Sandoval wrote:
> The free space tree is updated in tandem with the extent tree. There are
> only a handful of places where we need to hook in:
>
> 1. Block group creation
> 2. Block group deletion
> 3. Delayed refs (extent creation and deletion)
>
Hi, Omar Sandoval
[PATCH 7/9] have following compiler warning:
fs/btrfs/tests/free-space-tree-tests.c: In function
'__check_free_space_extents':
fs/btrfs/tests/free-space-tree-tests.c:45: warning: 'offset' may be used
uninitialized in this function
It is just a compiler warning, and
17 matches
Mail list logo