Hello,

I've currently run into strange problem with BTRFS. I'm using it as my daily driver as root FS. Nothing complicated, just few subvolumes and incremental backups using btrbk.

Now I've noticed that my btrfs root volume (absolute top, ID 5) is in "deleting" state. As I've done some testing and googling it seems that this should not be possible.

I've tried scrubbing and checking, but nothing changed. Volume is not being deleted in reality. It just sits there in this state.

Is there anything I can do to fix this?

# btrfs sub list -a /mnt/btrfs_root/
ID 1339 gen 262150 top level 5 path rootfs
ID 1340 gen 262101 top level 5 path .btrbk
ID 1987 gen 262149 top level 5 path no_backup
ID 4206 gen 255869 top level 1340 path <FS_TREE>/.btrbk/rootfs.20170121T1829
ID 4272 gen 257460 top level 1340 path <FS_TREE>/.btrbk/rootfs.20170123T0933
ID 4468 gen 259194 top level 1340 path <FS_TREE>/.btrbk/rootfs.20170131T1132
ID 4474 gen 260911 top level 1340 path <FS_TREE>/.btrbk/rootfs.20170207T0927
ID 4476 gen 261712 top level 1340 path <FS_TREE>/.btrbk/rootfs.20170211T0000
ID 4477 gen 261970 top level 1340 path <FS_TREE>/.btrbk/rootfs.20170212T1331
ID 4478 gen 262102 top level 1340 path <FS_TREE>/.btrbk/rootfs.20170213T0000

# btrfs sub list -ad /mnt/btrfs_root/
ID 5 gen 257505 top level 0 path <FS_TREE>/DELETED

# mount | grep btr
/dev/mapper/vg0-btrfsroot on / type btrfs (rw,noatime,nodatasum,nodatacow,ssd,discard,space_cache,subvolid=1339,subvol=/rootfs) /dev/mapper/vg0-btrfsroot on /mnt/btrfs_root type btrfs (rw,noatime,nodatasum,nodatacow,ssd,discard,space_cache,subvolid=5,subvol=/)

# uname -a
Linux interceptor 4.9.6-1-ARCH #1 SMP PREEMPT Thu Jan 26 09:22:26 CET 2017 x86_64 GNU/Linux

# btrfs fi show  /
Label: none  uuid: 859dec5c-850c-4660-ad99-bc87456aa309
    Total devices 1 FS bytes used 132.89GiB
    devid    1 size 200.00GiB used 200.00GiB path /dev/mapper/vg0-btrfsroot


Thank you for your time,


Best regards

--

Martin Mlynář

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to