Hello Roman, the FS is mountable. It just goes readonly when trying to write some data.
The kernel msgs are: BTRFS critical (device dm-2): corrupt leaf, bad key order: block=163316514816,root=1, slot=39 BTRFS critical (device dm-2): corrupt leaf, bad key order: block=163322413056,root=1, slot=74 BTRFS critical (device dm-2): corrupt leaf, bad key order: block=163325722624,root=1, slot=63 BTRFS critical (device dm-2): corrupt leaf, bad key order: block=163316514816,root=1, slot=39 BTRFS: error (device dm-2) in btrfs_drop_snapshot:8839: errno=-5 IO failure BTRFS info (device dm-2): forced readonly BTRFS info (device dm-2): delayed_refs has NO entry Greets, Stefan Am 10.05.2017 um 09:18 schrieb Roman Mamedov: > On Wed, 10 May 2017 09:02:46 +0200 > Stefan Priebe - Profihost AG <s.pri...@profihost.ag> wrote: > >> how to fix bad key ordering? > > You should clarify does the FS in question mount (read-write? read-only?) > and what are the kernel messages if it does not. > -- 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
