Re: Btrfs-progs static compile failure due to multiple uuid-tree.o in linking paratemeters

On Sat, 9 Nov 2013 11:22:01 +0200, Emil Karlson wrote: > Greetings > > Btrfs-progs static compile fails due to multiple uuid-tree.o in > linking paratemeters: > > build error: > gcc -g -O1 -ffunction-sections -fdata-sections -o btrfs.static > btrfs.static.o help.static.o cmds-subvolume.static.o

[PATCH] btrfs-progs: remove extra uuid-tree.o in objects

This fixes static compile target of btrfs-progs. Signed-off-by: Emil Karlson --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 4e33648..4604b1f 100644 --- a/Makefile +++ b/Makefile @@ -9,7 +9,7 @@ CFLAGS = -g -O1 objects = ctree.o disk-io

[PATCH v2] btrfs-progs: remove extra uuid-tree.o in objects

This fixes static compile target of btrfs-progs. Signed-off-by: Emil Karlson --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 4e33648..4604b1f 100644 --- a/Makefile +++ b/Makefile @@ -9,7 +9,7 @@ CFLAGS = -g -O1 objects = ctree.o disk-io

Re: btrfsck errors is it save to fix?

Hello, I re-post this: >> To answer the "is it safe to fix" question... > In that context, yes, it's safe to btrfsck --repair, because you're prepared to lose the entire filesystem if worse comes to worse in any case, so even if btrfsck --repair makes things worse instead of better, you've no

Re: [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked

On 07/11/13 01:25, Martin wrote: > On 28/10/13 15:11, Josef Bacik wrote: >> Ok I've sent >> >> [PATCH] Btrfs-progs: rework open_ctree to take flags, add a new one >> >> which should address your situation. Thanks, > > > Josef, > > Tried your patch: > > > Signed-off-by: Josef Bacik > >

Re: btrfsck errors is it save to fix?

Hendrik Friedel schrieb: > I re-post this: > [...] >> root 256 inode 9579 errors 100 >> root 256 inode 9580 errors 100 >> root 256 inode 14258 errors 100 >> root 256 inode 14259 errors 100 >> root inode 9579 errors 100 >> root inode 9580 errors 100 >> root inode 14258 errors 100 >

Re: btrfsck errors is it save to fix?

Kai Krakow posted on Tue, 12 Nov 2013 00:58:59 +0100 as excerpted: > Hendrik Friedel schrieb: > >> I re-post this: >> > [...] >>> root 256 inode 9579 errors 100 >>> root 256 inode 9580 errors 100 >>> root 256 inode 14258 errors 100 >>> root 256 inode 14259 errors 100 >>> root inode 9579 er

invalid opcode: 0000 [#1] SMP

Hi everyone, we are using a btrfs RAID 1 with four 2TB hard drives (WD Caviar green) on a Debian 7.2 with Kernel 3.11.6 Now we had an 'invalid opcode: [#1] SMP' when a sector fails in messages log. After that, access over smb and nfs wasn't possible. A restart solved the problem of inacces