I forgot the attachment. Here it is.
# btrfs-debug-tree -b 13415158087680 /dev/sdh
leaf 13415158087680 items 90 free space 8577 generation 140065 owner 5007
fs uuid 20ccaf09-54ea-486e-9495-9dc91b933e9c
chunk uuid f5a0dea1-b250-4ea4-bf7f-50d30401a708
item 0 key (7516 DIR_INDEX 102) itemoff
Duncan 1i5t5.duncan at cox.net writes:
- How can I salvage this situation and convert to raid1?
Unfortunately I have little spare drives left. Not enough to contain
4.7TiB of data.. :(
[OK, this goes a bit philosophical, but it's something to think about...]
...
Anyway, at least
Hi all,
I completed a full scrub:
root@nasbak:/home/jpieroen# btrfs scrub status /home/
scrub status for 7ca5f38e-308f-43ab-b3ea-31b3bcd11a0d
scrub started at Wed Apr 30 08:30:19 2014 and finished after 144131 seconds
total bytes scrubbed: 4.76TiB with 0 errors
Then tried to remove a device:
Duncan 1i5t5.duncan at cox.net writes:
To those that know the details, this tells the story.
Btrfs raid5/6 modes are not yet code-complete, and scrub is one of the
incomplete bits. btrfs scrub doesn't know how to deal with raid5/6
properly just yet.
While the operational bits of
Shilong Wang wangshilong1991 at gmail.com writes:
Hello,
There is a known RAID5/6 bug, i sent a patch to address this problem.
Could you please double check if your kernel source includes the
following commit:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?
Duncan 1i5t5.duncan at cox.net writes:
Jaap Pieroen posted on Sun, 27 Apr 2014 18:30:19 +0200 as excerpted:
... snip
Never use btrfsck (or btrfs check) with the --repair option, unless
you're about ready to give up on the filesystem and do a mkfs, in which
case you aren't risking
Hello,
When I try to delete a device from my btrfs filesystem I always get the
following kernel bug error:
[ 809.161020] kernel BUG at
/home/apw/COD/linux/fs/btrfs/extent_io.c:2116!
[ 809.166761] invalid opcode: [#3] SMP
See attached log file for more details. I’m trying
