From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Jan Schubert <Jan.Schubert@GMX.li>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Broken btrfs?
Date: Mon, 18 Jul 2011 10:29:07 +0200 [thread overview]
Message-ID: <4E23EED3.8000301@jan-o-sch.net> (raw)
In-Reply-To: <loom.20110717T160020-81@post.gmane.org>
On 17.07.2011 16:01, Jan Schubert wrote:
> Jan Schubert <jan.schubert <at> gmx.li> writes:
>> Please find some data and log below. Is there any chance to fix this?
>
> After playing around (incl. deleting the log) I get the strong feeling
> it has something todo with compression=lzo. Dunno why it started suddenly
> but I disabled compression and did reinstall everything which helped a
lot.
> I still have some broken configuration and other (non reinstalable) files
> which causes crashing the box when I try to access them. I detect them
> manually, is there any way to do this automagically?
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
next prev parent reply other threads:[~2011-07-18 8:29 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 [this message]
2011-07-21 21:13 ` Jan Schubert
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=4E23EED3.8000301@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=Jan.Schubert@GMX.li \
--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.