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: 0000 [#3] SMP
See attached log file for more details. I’m trying to delete the device 
/dev/sdb from my filesystem.

Steps I tried so far are:
1. mount with the clear_cache option
2. balance the filesystem (results in the same kernel error)
3. scrub the filesystem
4. btrfsck —repair

During scrubbing and btrfsck some error where found and fixed. But I think 
these where error caused by system lockups during copying data to the new btrfs 
filesystem. These lockups where caused by an extraordinary amount of hard 
links, since I was using rsnapshot to create hourly snapshots on my old 
filesystem that I am migrating towards btrfs. Removing these hard links solved 
the lockup problems.

Something I also noted was that after the btrfsck run, the command ‘btrfs fi 
show’ reported “devid    4 size 0.0GiB used 98.00GiB path /dev/sdb” (mind the 
0.0GB).

I’m ready to run any diagnostics necessary, but the filesystem is 4.7T so it 
won’t be able to provide an image.

System details:
        $ uname -a
        Linux nasbak 3.14.1-031401-generic #201404141220 SMP Mon Apr 14 
16:21:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
        $ btrfs --version
        Btrfs v3.12
        $ sudo btrfs fi show
        Label: btrfs_storage  uuid: 7ca5f38e-308f-43ab-b3ea-31b3bcd11a0d
                Total devices 6 FS bytes used 4.57TiB
                devid    1 size 1.82TiB used 1.32TiB path /dev/sde
                devid    2 size 1.82TiB used 1.32TiB path /dev/sdf
                devid    3 size 1.82TiB used 1.32TiB path /dev/sdg
                devid    4 size 931.51GiB used 88.00GiB path /dev/sdb
                devid    6 size 2.73TiB used 947.03GiB path /dev/sdh
                devid    7 size 2.73TiB used 947.03GiB path /dev/sdi
        
        Btrfs v3.12

Attachment: dmesg.log
Description: Binary data

Reply via email to