From: Jan Schubert <Jan.Schubert@GMX.li>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Broken btrfs?
Date: Fri, 22 Jul 2011 15:18:40 +0200 [thread overview]
Message-ID: <4E2978B0.9050501@GMX.li> (raw)
In-Reply-To: <4E292598.2090308@jan-o-sch.net>
On 07/22/2011 09:24 AM, Jan Schmidt wrote:
> Scrub should be printing inode numbers to your system log while
> detecting those errors. If you want to know the exact files corrupted,
> you can grab my patch set with subject "Btrfs scrub: print path to
> corrupted files and trigger nodatasum fixup" from the list and give it
> a try.
Cool Jan, this is exactly what I asked for in my original post.
Your patch set is against kernel sources (not btrfs-progs), right? I
took the opportunity to upgrade to official 3.0 where your patch applied
and compiled without any issues. I also did recompile
btrfs-progs-unstable and run a scrub.
This scrub completed without any errors:
# btrfs scrub status .
scrub status for 03201fc0-7695-4468-9a10-f61ad79f23ca
scrub started at Fri Jul 22 14:24:21 2011, running for 706 seconds
total bytes scrubbed: 158.01GB with 0 errors
Is'nt this strange? This message is generated after rebooting the box
(due to a crash, see below), I remember to have seen some more
information before the crash but also 0 errors.
While doing the scrub I still did see csum errors in my dmesg but no
files associated:
Jul 22 14:17:50 toral kernel: btrfs no csum found for inode 199934 start
729088
Jul 22 14:17:50 toral kernel: btrfs csum failed ino 199934 off 729088
csum 3390946210 private 0
Jul 22 14:17:51 toral kernel: btrfs no csum found for inode 199934 start
24096768
Jul 22 14:17:51 toral kernel: btrfs csum failed ino 199934 off 24096768
csum 439962552 private 0
Jul 22 14:17:51 toral kernel: btrfs no csum found for inode 199934 start
24801280
Jul 22 14:17:51 toral kernel: btrfs no csum found for inode 199934 start
24805376
Jul 22 14:17:51 toral kernel: btrfs csum failed ino 199934 off 24801280
csum 158010657 private 0
Jul 22 14:17:51 toral kernel: btrfs csum failed ino 199934 off 24805376
csum 127231121 private 0
And sorry to say, it also crashed my box throwing a kernel expception
and a reference to somtehing like scrub_print_warning_inode (or similar)
which I could not find after rebooting my box. Seems my kernel.log and
all others logs are empty for the last 30min, Sry.
What is the most current btrfs-progs git branch to use for further
investigation?
Thx,
Jan
prev parent reply other threads:[~2011-07-22 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 21:44 Broken btrfs? Jan Schubert
2011-07-17 14:01 ` Jan Schubert
2011-07-18 8:29 ` Jan Schmidt
2011-07-21 21:13 ` Jan Schubert
2011-07-22 7:24 ` Jan Schmidt
2011-07-22 13:18 ` Jan Schubert [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=4E2978B0.9050501@GMX.li \
--to=jan.schubert@gmx.li \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).