From: Lubos Kolouch <lubos.kolouch@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: mkfs or wait?
Date: Tue, 7 Sep 2010 05:55:12 +0000 (UTC) [thread overview]
Message-ID: <i64k40$ur1$1@dough.gmane.org> (raw)
Hello,
I have on one computer damaged btrfs filesystem... it was a strange
crash, it showed about 30% free space, however then the volume crashed
with 'no space left' messages and after reboot it is unusable.
I can mount it, I can df it but when I try for example ls,
ls gets stuck (does not display anything) and I get
- in the syslog
verify_parent_transid: 22336 callbacks suppressed
parent transid verify failed on 1066975232 wanted 125077 found 125075
parent transid verify failed on 974635008 wanted 125077 found 125075
parent transid verify failed on 1066975232 wanted 125077 found 125075
parent transid verify failed on 974635008 wanted 125077 found 125075
parent transid verify failed on 1066975232 wanted 125077 found 125075
parent transid verify failed on 974635008 wanted 125077 found 125075
parent transid verify failed on 1066975232 wanted 125077 found 125075
parent transid verify failed on 974635008 wanted 125077 found 125075
parent transid verify failed on 1066975232 wanted 125077 found 125075
parent transid verify failed on 974635008 wanted 125077 found 125075
- top shows
ls
[btrfs-endio-met]
[btrfs-cache-293]
- btrfs segfaults
It is like this over a day. Should I just mkfs it or is there anything
sensible I could try?
kernel 2.6.35-gentoo-r5, latest git btrfs-progs
Thank you for your advice.
Lubos
next reply other threads:[~2010-09-07 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 5:55 Lubos Kolouch [this message]
2010-09-07 9:41 ` Btrfs troubles Konstantinos Skarlatos
2010-09-07 13:45 ` mkfs or wait? Lubos Kolouch
2010-09-07 13:48 ` Daniel Kozlowski
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='i64k40$ur1$1@dough.gmane.org' \
--to=lubos.kolouch@gmail.com \
--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).