Excerpts from brandon lansing's message of 2011-04-19 11:42:26 -0400: > On Tue, Apr 19, 2011 at 05:58, Chris Mason <chris.mason@xxxxxxxxxx> wrote: > > Excerpts from brandon lansing's message of 2011-04-18 23:13:06 -0400: > >> Hello, > >> > >> Distro: Ubuntu 10.10 > >> Kernel:ÂLinux 2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC > >> 2011 x86_64 GNU/Linux > >> Btrfs tools version:ÂBtrfs Btrfs v0.19 > >> > >> I currently have 2 X 500GB hard drives in 'raid1' mode with about > >> 400GB used. ÂRecently one of the hard drives crashed (but I have a > >> backup) but I'd like to help out if I can because I'm currently > >> getting an error when trying to 'rebuild' the filesystem. > >> I've mounted the array in degraded mode and added the new hard drive. > >> Finally I issued the command to delete the missing device. ÂThe dmesg > >> looks normal for a while with messages such as:Âbtrfs: relocating > >> block group 466167529472 flags 17. ÂHowever, after a few minutes of > >> running I get the following: > >> > >> [ 1770.041623] ------------[ cut here ]------------ > >> [ 1770.041655] kernel BUG at /build/buildd/linux-2.6.35/fs/btrfs/volumes.c:3037! > >> [ 1770.041684] invalid opcode: 0000 [#1] SMP > >> [ 1770.041707] last sysfs file: /sys/devices/virtual/bdi/btrfs-3/uevent > >> [ 1770.041734] CPU 1 > >> [ 1770.041744] Modules linked in: btrfs sha256_generic cryptd > > > > Could you please attached the fs/btrfs/volumes.c from this distro > > kernel? ÂIt'll help us figure out what is going wrong. > > > > -chris > > > > Chris, > > Thanks for the prompt response, however, I think it may have had > something to do with the version of btrfs I was running with the > kernel 2.6.35-28-generic in Ubuntu. I upgraded to Ubuntu 11.04 > (natty) and kernel 2.6.38-8-generic and this solved my problem. I was > able to rebuild all 374GB without error. Great to hear, thanks for the update. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
