When I ran xfstests, 251 got failed cause cp -axT did not work as wish:
cp: cannot overwrite directory `/mnt/scratch/1' with non-directory
With this patch, 251 has passed.
Signed-off-by: Liu Bo liubo2...@cn.fujitsu.com
---
251 |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
Hi,
I have problems with a btrfs filesystem, and am holding on to it for
some more days before reformat.
What I am interested about is two things:
1. Is there any way to restore more stuff from the filesystem then
already fetched (it would help to get the system up faster, but nothing
really of
Hi,
I have problems with a btrfs filesystem, and am holding on to it for
some more days before reformat.
What I am interested about is two things:
1. Is there any way to restore more stuff from the filesystem then
already fetched (it would help to get the system up faster, but nothing
really of
moved the node-,leaf-,sectorsize from btrfs_root to btrfs_fs_info
since we don't intend to allow different sizes between trees
also removed sectorsize from btrfs_block_group_cache because it now
can use the one in fs_info
updated all uses accordingly
please note in disk-io.c:
-static int
Hello
we are currently investigating performance issue on system runing
above btrs filesystem. Is it possible, that performance is impacted by
lack of free space? Also, how to get info about real free space on btrfs
volume?
# btrfs-show /dev/sdb1
Label: opt uuid:
[Note : this is a resent of a mail I send to linux-btrfs earlier, this
time tested with the lastest git kernel]
Hi,
One of my disks, partitioned into a single btrfs partition, is showing
media errors. The problem is that these errors lead to kernel panic from
btrfs - that make the filesystem
On Mon, Jan 09, 2012 at 03:44:18PM +0200, Ilya Dryomov wrote:
On Mon, Jan 09, 2012 at 01:50:34AM -0500, Marios Titas wrote:
I tried this for many different scenarios and it seems to work pretty
well. I only ran into one problematic case: If you remove a device
from a multidevice filesystem
2012/1/10 Michal Suba michal.s...@pantheon.sk:
Hello
we are currently investigating performance issue on system runing above
btrs filesystem. Is it possible, that performance is impacted by lack of
free space? Also, how to get info about real free space on btrfs volume?
# btrfs-show
On Tue, Jan 10, 2012 at 12:40 PM, Mitch Harder
mitch.har...@sabayonlinux.org wrote:
2012/1/10 Michal Suba michal.s...@pantheon.sk:
Hello
we are currently investigating performance issue on system runing above
btrs filesystem. Is it possible, that performance is impacted by lack of
free
If updating the inode gave us an ENOSPC we were just returning in page_mkwrite,
which is a problem since we make our reservation right before trying to update
the inode, so fix the out label so that we actually free our reservation.
Thanks,
Signed-off-by: Josef Bacik jo...@redhat.com
---
Hello!
bt...@spiritvideo.com bt...@spiritvideo.com schrieb:
The plan that occurs to me is to make a snapshot of the system in the
state that I want to always boot. Then, I would rewrite the init
script in the initrd to (a) delete any old tmp copy of the snapshot;
(b) copy the static
On Tue, Jan 10, 2012 at 03:31:34PM +0800, Liu Bo wrote:
+static inline int generate_node_level(u64 randseed)
+{
+ int level = 0;
+
+ while (randseed !(randseed 3)) {
+ randseed = 2;
+ level++;
+ }
+
+ return (level MAXLEVEL ? MAXLEVEL : level);
On 01/11/2012 08:37 AM, David Sterba wrote:
Hi, a few thoughts and comments below:
On Tue, Jan 10, 2012 at 03:31:34PM +0800, Liu Bo wrote:
c) The level limit may need to be adjusted.
I know it is a magic number, but now for simplicity we just keep it at 16,
and then each skiplist is
Upcoming btrfs autosnap feature might help your problem-solution.
But the main part in your case which is to replace the root
with its snapshot is something beyond the scope of autosnap
project.
What is being developed is a set of btrfs-prog sub-command to
create and manage snapshots
For btrfs raid, while discarding a range of space, we'll need to know
the start offset and length to discard for each device, and it's done
in btrfs_map_block().
However the calculation is a bit complex for raid0 and raid10, so I
reimplement it based on a fact that:
dev1 dev2
There are various bugs in block group trimming:
- It may trim from offset smaller than user-specified offset.
- It may trim beyond user-specified range.
- It may leak free space for extents smaller than specified minlen.
- It may truncate the last trimmed extent thus leak free space.
- With mixed
A bug was triggered while using seed device:
# mkfs.btrfs /dev/loop1
# btrfstune -S 1 /dev/loop1
# mount -o /dev/loop1 /mnt
# btrfs dev add /dev/loop2 /mnt
btrfs: block rsv returned -28
[ cut here ]
WARNING: at fs/btrfs/extent-tree.c:5969
The correct lock order is uuid_mutex - volume_mutex - chunk_mutex,
but when we mount a filesystem which has backing seed devices, we have
this lock chain:
open_ctree()
lock(chunk_mutex);
read_chunk_tree();
read_one_dev();
open_seed_devices();
Check and reserve space for btrfs_update_inode().
Signed-off-by: Li Zefan l...@cn.fujitsu.com
---
fs/btrfs/ioctl.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index 9619fb0..fe8a60c 100644
--- a/fs/btrfs/ioctl.c
+++
It can return -ENOMEM.
Signed-off-by: Li Zefan l...@cn.fujitsu.com
---
fs/btrfs/free-space-cache.c |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c
index 4e55af3..e4eb222 100644
---
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
If we run into some failure path in io_ctl_prepare_pages(),
io_ctl-pages[] array may have some NULL pointers.
Signed-off-by: Li Zefan l...@cn.fujitsu.com
---
fs/btrfs/free-space-cache.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/free-space-cache.c
Some functions never use the transaction handle passed to them.
Signed-off-by: Li Zefan l...@cn.fujitsu.com
---
fs/btrfs/extent-tree.c |2 +-
fs/btrfs/volumes.c | 18 +++---
fs/btrfs/volumes.h |3 +--
3 files changed, 9 insertions(+), 14 deletions(-)
diff --git
I got this while running xfstests:
[24256.836098] block group 317849600 has an wrong amount of free space
[24256.836100] btrfs: failed to load free space cache for block group 317849600
We should clamp the extent returned by find_first_extent_bit(),
so the start of the extent won't smaller than
We pre-allocate a btrfs bio with fixed size, and then may re-allocate
memory if we find stripes are bigger than the fixed size. But this
pre-allocation is not necessary.
Also we don't have to calcuate the stripe number twice.
Signed-off-by: Li Zefan l...@cn.fujitsu.com
---
fs/btrfs/volumes.c |
We can recover from errors and return -errno to user space.
Signed-off-by: Li Zefan l...@cn.fujitsu.com
---
fs/btrfs/ioctl.c | 18 ++
1 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index c04f02c..9619fb0 100644
---
26 matches
Mail list logo
