From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-transacti causing IO problem to btrfs (skinny-metadata?)
Date: Fri, 27 Mar 2015 00:21:32 +0000 [thread overview]
Message-ID: <mf27qc$io$1@ger.gmane.org> (raw)
In-Reply-To: <metvnc$nmp$1@ger.gmane.org>
For anyone stumbling across this thread:
For my example, all was cleaned up by using the btrfs scrub:
btrfs scrub start /mountpoint
No data lost.
Good luck,
Martin
On 25/03/15 09:38, Martin wrote:
>
> Is that btrfs system formatted with a previous kernel (pre-
> skinny-metadata) and is now being used with a kernel that newly has
> skinny-metadata enabled by default?...
>
>
> I've stumbled across a bug/change/patch listed for a mixed pre/post
> skinny-metadata whereby you get to see lots of csum errors in the logs...
>
> For one 16TB btrfs raid1 system that brought things down to read-only...
>
>
> I'm now on kernel 3.18.9, and Btrfs v3.18.2. Presently copying the
> latest data onto a backup before trying a scrub! :-)
>
> LOTs of:
>
> kernel: parent transid verify failed on 5992676900864 wanted 70743 found
> 70709
> kernel: parent transid verify failed on 5992676900864 wanted 70743 found
> 70709
> kernel: BTRFS info (device sdj): no csum found for inode 50675726 start
> 16384
> kernel: BTRFS info (device sdj): csum failed ino 50675726 off 0 csum
> 42383870 expected csum 0
> kernel: BTRFS info (device sdj): csum failed ino 50675726 off 4096 csum
> 815939273 expected csum 0
>
> and variations seen.
>
> (Or advice for that one welcomed! ;-) )
prev parent reply other threads:[~2015-03-27 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 8:29 btrfs-transacti causing IO problem to btrfs Ian Gordon
2015-03-25 9:38 ` btrfs-transacti causing IO problem to btrfs (skinny-metadata?) Martin
2015-03-27 0:21 ` Martin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mf27qc$io$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.