From: Jan Schubert <Jan.Schubert@GMX.li>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>, linux-btrfs@vger.kernel.org
Subject: Re: Broken btrfs?
Date: Thu, 21 Jul 2011 23:13:03 +0200 [thread overview]
Message-ID: <4E28965F.1010508@GMX.li> (raw)
In-Reply-To: <4E23EED3.8000301@jan-o-sch.net>
On 07/18/2011 10:29 AM, Jan Schmidt wrote:
> If you are on a 3.0 kernel, get the most current version of btrfs
> tools from Hugo's integration-20110705 branch at
> http://git.darksatanic.net/repo/btrfs-progs-unstable.git/ and do a
> scrub. -Jan
Thx Jan, I did. This is the result:
scrub status for 03201fc0-7695-4468-9a10-f61ad79f23ca
scrub started at Thu Jul 21 22:27:31 2011 and finished after 787
seconds
total bytes scrubbed: 173.91GB with 2211 errors
error details: csum=2211
corrected errors: 0, uncorrectable errors: 2211
Any help what to do now? Should I stick with this filesystem or create a
new one?
The good thing is, running 3.0 does not crash the system anymore while
accessing corrupt data but just printing an I/O error.
TiA,
Jan
next prev parent reply other threads:[~2011-07-21 21:13 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 [this message]
2011-07-22 7:24 ` Jan Schmidt
2011-07-22 13:18 ` Jan Schubert
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=4E28965F.1010508@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 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.