Re: runtime btrfsck

[Hugo Mills <hugo@carfax.org.uk>]

[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]

On Wed, May 10, 2017 at 09:36:30AM +0200, Stefan Priebe - Profihost AG wrote:
> 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

   Can you show the output of btrfs-debug-tree -b <blocknum>, where
<blocknum> is each of the three "block=" values above?

   Hugo.

> 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.priebe@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.
> > 

-- 
Hugo Mills             | Welcome to Hollywood, a land just off the coast of
hugo@... carfax.org.uk | Planet Earth
http://carfax.org.uk/  |
PGP: E2AB1DE4          |                                        The Cat's Meow

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]