similar to: Requirements for btrfs

Hi, i've just tested btrfs-0.10. when i copyed my portage on btrfs volume, a have such bug: ------------[ cut here ]------------ kernel BUG at /home/muller/btrfs/btrfs-0.10/extent-tree.c:1651! invalid opcode: 0000 [#1] PREEMPT SMP Modules linked in: btrfs xt_mac xt_limit xt_multiport ipt_owner ipaq usbserial nvidia(P) Pid: 23376, comm: btrfs/0 Tainted: P (2.6.24-rc8-fly #1) EIP:

Hi there, Just gave 0.13 a spin against XFS (both with default mkfs options) on my SATA tower and was impressed by how much performance has improved since last time I played with it (v0.5)! It pretty much matched XFS for I/O performance and had much better file creation/deletion performance. http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks cheers, Chris -- Chris Samuel :

Unfortunately my laptop deadlocks from time to time, and too often it triggers this bug in btrfs which is quite hard to recover from. The bigger problem is that all the user sees (if anything) is seemingly unrelated info, namely, "RIP: btrfs_num_copies+0x42/0x0b" or somesuch http://marc.merlins.org/tmp/btrfs_num_copies.jpg It''s only if you have serial console, or netconsole,

I''ve enabled "extended inode refs" and "skinny metadata extent refs" with btrfstune. Then, I''ve tried running "btrfs filesystem balance" - unfortunately it segfaulted. (not sure if I should run balance operation after using btrfstune with -r and -x)? This is with 3.10 kernel with "Btrfs: make backref walking code handle skinny metadata"

Hello Josef, FYI build failure occured in fs/btrfs/ctree.h. CC fs/btrfs/super.o In file included from fs/btrfs/delayed-inode.h:30:0, from fs/btrfs/super.c:45: fs/btrfs/ctree.h:3235:1: error: expected identifier or ‘(’ before ‘<<’ token make[3]: *** [fs/btrfs/super.o] Error 1 make[2]: *** [fs/btrfs] Error 2 make[1]: *** [fs] Error 2 make[1]: Leaving directory ` make:

I''ve filed this bug under util-linux, because I think wipefs isn''t deleting all btrfs metadata it could. But ultimately it appears to be a btrfs bug because nothing else sees the stale volume. https://bugzilla.redhat.com/show_bug.cgi?id=889888#c15 btrfs-progs-0.20.rc1.20121017git92d9eec-1.fc18.x86_64 e2fs-progs-1.42.5-1.fc18.x86_64 kernel 3.7.1-2 Brand new 80GB virtual disk,

Hi, My company is testing btrfs (kernel 2.6.38) on a slave MySQL database server with a 195Gb filesystem (of which about 123Gb is used). So far, we''re quite impressed with the performance. Our database loads are high, and if filesystem performance wasn''t good, MySQL replication wouldn''t be able to keep up and the slave latency would begin to climb. This though, is

'btrfs qgroup show' used to output bytes in raw, but in btrfs-progs v3.18.2 it outputs bytes with suffix KiB, MiB or like by default, which causes error when parsing the output. Fix it by adding '--raw' to let 'btrfs qgroup show' output raw numbers always. Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- daemon/btrfs.c | 4 ++++ 1 file changed, 4 insertions(+)

Hi, I try to format a USB memory with a Btrfs. I can format it with mkfs.btrfs without problems. But; when I try to mount it, it fails to mount with the below error messages. But the USB memory works fine with other filesystems (ext4, XFS etc.). So, the hardware is not faulty. tarkane@tarkane:~$ sudo mkfs.btrfs -d single -n 4096 /dev/sdb1 WARNING! - Btrfs v0.18-26-g0030f1d IS EXPERIMENTAL

Since 2.6.29-rc1 contains btrfs I had to try it. However the loopback mount of my btrfs formatted file fails: user@host:~$ dd if=/dev/zero of=btrfs.img bs=1MB count=512 user@host:~$ mkfs.btrfs btrfs.img fs created label (null) on btrfs.img nodesize 4096 leafsize 4096 sectorsize 4096 size 488.28MB Btrfs v0.16+da35ab2b0b54 user@host:~$ sudo mount -t btrfs -o loop btrfs.img /mnt/btrfs mount:

From: Hugo Mills <h.r.mills@reading.ac.uk> btrfs-find-root isn''t yet integrated into the main btrfs tool, and is an important recovery tool, so it deserves to be built as a static binary. Signed-off-by: Hugo Mills <hugo@carfax.org.uk> --- Makefile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index d102dee..c519d21 100644

Currently there are 3 different capitalisations of btrfs: used in printk()''s, BTRFS: (3 occurences), Btrfs: (1 occurence) and btrfs: (77 occurences). It''s best to have them all the same for consistency, so we canonicalise the two minority cases to btrfs:. Signed-off-by: Chris Samuel <chris@csamuel.org> --- fs/btrfs/disk-io.c | 4 ++-- fs/btrfs/inode.c | 4 ++-- 2

Check for the return value of ''open_ctree()'' before dereferencing it. Signed-off-by: Nageswara R Sastry <nasastry@in.ibm.com> --- btrfs-image.c | 1 + 1 file changed, 1 insertion(+) diff --git a/btrfs-image.c b/btrfs-image.c index f2bbcc8..2a33a55 100644 --- a/btrfs-image.c +++ b/btrfs-image.c @@ -491,6 +491,7 @@ static int create_metadump(const char *input, FILE *out,

In trfs-progs 4.4 the error message has been changed, and our check did not work anymore. Yes, parsing user messages really sucks... --- daemon/btrfs.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index 85dbe00..c67af83 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@ -1029,9 +1029,12 @@ do_btrfs_subvolume_show (const char

This patch adds the flag, BTRFS_SEND_FLAG_NO_FILE_DATA to the btrfs send ioctl code. When this flag is set, the btrfs send code will never write file data into the stream (thus also avoiding expensive reads of that data in the first place). BTRFS_SEND_C_UPDATE_EXTENT commands will be sent (instead of BTRFS_SEND_C_WRITE) with an offset, length pair indicating the extent in question. This patch

blkid(1) (or actually, libblkid) seems to handle file system labels up to 127 characters. Considering that btrfs labels can be up to 255 characters, this means long labels are not read correctly (i.e. get truncated) by blkid. Get the file system type, and if btrfs is available invoke `btrfs filesystem` to get the label of btrfs file systems. --- daemon/blkid.c | 6 ++++++ daemon/btrfs.c | 24

When using "-U" option with btrfs-corrupt-block, it will cause a segfault due to a missing break in getopt switch. Reported-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com> --- btrfs-corrupt-block.c | 1 + 1 file changed, 1 insertion(+) diff --git a/btrfs-corrupt-block.c b/btrfs-corrupt-block.c index f0c14a9..a2828d4 100644

Not sure how this happened, but filter.btrfs including itself leads to immense sadness for any file that includes it. (I got a segfault when I tried to run 307) Signed-off-by: Eric Sandeen <sandeen@redhat.com> --- diff --git a/common/filter.btrfs b/common/filter.btrfs index b1aa733..99d04a6 100644 --- a/common/filter.btrfs +++ b/common/filter.btrfs @@ -1,7 +1,5 @@ # Filters for btrfs

An old version of btrfs-progs (3.17 in this case) has a different version string, so adapt our filtering to include this line as well. Related to/updates commit 839ae5bcd537b3dc4f13bbea6fe40091ebc2b7f0. --- daemon/btrfs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index d18f518..23513a9 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@

From: Sergei Trofimovich <slyfox@gentoo.org> $ LDFLAGS=-static make gcc -lpthread -g -O0 -o btrfs btrfs.o btrfs_cmds.o scrub.o \ ctree.o disk-io.o radix-tree.o extent-tree.o print-tree.o root-tree.o dir-item.o file-item.o inode-item.o inode-map.o crc32c.o rbtree.o extent-cache.o extent_io.o volumes.o utils.o btrfs-list.o btrfslabel.o -static -luuid scrub.o: In function