It's still running. Is this the normal behaviour? Is there any other way to fix the bad key ordering?
Greets, Stefan Am 02.05.2017 um 08:29 schrieb Stefan Priebe - Profihost AG: > Hello list, > > i wanted to check an fs cause it has bad key ordering. > > But btrfscheck is now running since 7 days. Current output: > # btrfsck -p --repair /dev/mapper/crypt_md0 > enabling repair mode > Checking filesystem on /dev/mapper/crypt_md0 > UUID: 37b15dd8-b2e1-4585-98d0-cc0fa2a5a7c9 > bad key ordering 39 40 > checking extents [O] > > FS is a 12TB BTRFS Raid 0 over 3 mdadm Raid 5 devices. How long should > btrfsck run and is there any way to speed it up? btrfs tools is 4.8.5 > > Thanks! > > Greets, > Stefan > -- 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
