From: Josef Bacik <jbacik@fusionio.com>
To: "Stéphane Mutz" <stephane.mutz@gmail.com>
Cc: Josef Bacik <jbacik@fusionio.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Problem with btrfsck / couurpted filesystem
Date: Thu, 27 Jun 2013 10:33:55 -0400 [thread overview]
Message-ID: <20130627143355.GR4288@localhost.localdomain> (raw)
In-Reply-To: <51CC4AF1.2090209@gmail.com>
On Thu, Jun 27, 2013 at 04:23:45PM +0200, Stéphane Mutz wrote:
> Hi,
>
> I've built the GIT tools and run btrfsck (without options) following the
> wiki page.
> I got the following log:
> Checking filesystem on /dev/VG_NL-SAS/LV_snap
> UUID: de300fd0-1251-4767-9d80-84ce7ebfba9a
> checking extents
> checking free space cache
> free space inode generation (0) did not match free space cache
> generation (16583)
> free space inode generation (0) did not match free space cache
> generation (16579)
> checking fs roots
> checking csums
> checking root refs
> found 120489896006 bytes used err is 0
> total csum bytes: 380818020
> total tree bytes: 10396295168
> total fs tree bytes: 9423839232
> total extent tree bytes: 473616384
> btree space waste bytes: 1923163802
> file data blocks allocated: 455172272128
> referenced 564086325248
> Btrfs v0.20-rc1-335-gf00dd83
>
> It does not report any extends error.
> Can I consider all is fine now?
>
Yup. If you still have problems its likely just a kernel bug and not a
corruption problem. And if that's the case dmesg would be nice so we can see
whats going on. Thanks,
Josef
next prev parent reply other threads:[~2013-06-27 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 13:54 Problem with btrfsck / couurpted filesystem Stéphane Mutz
2013-06-27 13:58 ` Josef Bacik
2013-06-27 14:23 ` Stéphane Mutz
2013-06-27 14:33 ` Josef Bacik [this message]
2013-06-27 15:01 ` Stéphane Mutz
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=20130627143355.GR4288@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stephane.mutz@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 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.