From: Jan Schubert <Jan.Schubert@GMX.li>
To: linux-btrfs@vger.kernel.org
Subject: Re: Broken btrfs?
Date: Sun, 17 Jul 2011 14:01:08 +0000 (UTC) [thread overview]
Message-ID: <loom.20110717T160020-81@post.gmane.org> (raw)
In-Reply-To: 20110716214404.50480@gmx.net
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?
Of course I'm still interessted in knowing the initial reason for this and
how to prevent this in the future...
Thx,
Jan
next prev parent reply other threads:[~2011-07-17 14:01 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 [this message]
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
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=loom.20110717T160020-81@post.gmane.org \
--to=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 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).