From: Chris Mason <chris.mason@oracle.com>
To: Michael Raskin <a0091f122@rambler.ru>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: cleanup after a small data loss on incorrect shutdown.
Date: Fri, 12 Jun 2009 07:42:30 -0400 [thread overview]
Message-ID: <20090612114230.GH3834@think> (raw)
In-Reply-To: <4A32374A.6080900@rambler.ru>
On Fri, Jun 12, 2009 at 03:08:58PM +0400, Michael Raskin wrote:
> Chris Mason wrote:
> >> 2. I found a file which is listed in the directory, but stat on it
> >> returns "No such file or directory". Certainly, rm and unlink cannot
> >> remove it. The partition has 14G in use. What can I do to provide a
> >> useful piece of FS structure information? How can I remove the file
> >> afterwards.
> >
> > I'd say to send us the btrfsck output, it will help answer these
> > questions.
>
> Oh, easily. "Bad block <number way beyond partition block count>".
Btrfs deals in byte numbers not block numbers ;)
> That's all. Reading one of the damaged file actually returned
> "Input/output error" - probably it tried to read beyond end-of-device. I
> had to kill this file (practical testing means that to continue to use
> my notebook normally I had to nuke the damaged file and get intact
> copies). The "no such file except in readdir" is still there right now.
Ok, btrfsck will give us more output when it finishes, but it hasn't
finished. It would help to use btrfs-image to send us a coyp of the
metadata so we can fix the btrfsck bug.
-chris
next prev parent reply other threads:[~2009-06-12 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 12:44 cleanup after a small data loss on incorrect shutdown Michael Raskin
2009-06-12 10:53 ` Chris Mason
2009-06-12 11:08 ` Michael Raskin
2009-06-12 11:42 ` Chris Mason [this message]
2009-06-12 11:56 ` Michael Raskin
2009-06-12 18:52 ` Michael Raskin
2009-06-12 11:48 ` Michael Raskin
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=20090612114230.GH3834@think \
--to=chris.mason@oracle.com \
--cc=a0091f122@rambler.ru \
--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