From: Chris Mason <chris.mason@oracle.com>
To: Yee-Ting Li <yee379@gmail.com>
Cc: The development of BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: volume broken? btrfsck fails
Date: Sun, 11 Jul 2010 20:43:15 -0400 [thread overview]
Message-ID: <20100712004315.GN3032@think> (raw)
In-Reply-To: <BC6F2F1C-B57E-4FCB-9B25-ACD9C35858C2@gmail.com>
On Sun, Jul 11, 2010 at 01:19:34AM -0700, Yee-Ting Li wrote:
> so after leaving the array for a while, with the disk churning away for a few days, it stopped. i copied some files off the disk (everything seems okay) and decided to unmount and run btrfsck again - this time i get a different error:
>
> $ sudo /usr/local/bin/btrfsck /dev/sdf
[ ... ick ... ]
> failed to find block number 364457984
> Aborted
Was this after a fresh mkfs? Clearly things are very corrupt on this
original drive. It would be a good test case for Yan Zhengs new fsck
code, but first I'd like to figure out if you're still seeing the old
corruption of if you've started over.
-chris
next prev parent reply other threads:[~2010-07-12 0:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 22:15 volume broken? btrfsck fails Yee-Ting Li
2010-07-01 12:51 ` Daniel Kozlowski
2010-07-04 6:57 ` Yee-Ting Li
2010-07-07 0:19 ` Chris Mason
2010-07-08 0:21 ` Daniel Kozlowski
2010-07-08 2:39 ` Daniel Kozlowski
2010-07-12 0:50 ` Chris Mason
2010-07-08 8:43 ` Daniel J Blueman
2010-07-07 0:16 ` Chris Mason
2010-07-07 5:23 ` Yee-Ting Li
2010-08-04 18:48 ` Thomas Kuther
2010-08-05 1:30 ` Chris Mason
2010-08-14 11:08 ` Thomas Kuther
2010-07-11 8:19 ` Yee-Ting Li
2010-07-12 0:43 ` Chris Mason [this message]
2010-07-12 4:05 ` Yee-Ting Li
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=20100712004315.GN3032@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yee379@gmail.com \
/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).