From: Xavier Bassery <xavier@bartica.org>
To: Adam Khan <adam.s.khan@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Please advise on repair action
Date: Thu, 27 Mar 2014 14:22:49 +0100 [thread overview]
Message-ID: <20140327142249.63dffbb8@renoir.lan> (raw)
In-Reply-To: <5333287F.6000601@gmail.com>
On Wed, 26 Mar 2014 15:20:31 -0400
Adam Khan <adam.s.khan@gmail.com> wrote:
> >>
> >> btrfsck returns this:
> >>
> >> Checking filesystem on /dev/mapper/xyz_crypt
> >> UUID: ...
> >
> > Here you've omitted the interesting part (preceding the next line).
> > Weren't there lines looking like
> > "root 256 inode XXXX errors 400, nbytes wrong" ?
>
> There is not a detailed error returned by btrfsck. The only part I
> found interesting is 'used err is 1', but maybe that is because this
> was my first time running btrfsck. No inode errors are reported.
Could you please provide the full output of btrfs check?
Xavier
prev parent reply other threads:[~2014-03-27 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 5:57 Please advise on repair action Adam Khan
2014-03-20 18:14 ` Adam Khan
2014-03-21 10:17 ` Xavier Bassery
2014-03-26 19:20 ` Adam Khan
2014-03-27 13:22 ` Xavier Bassery [this message]
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=20140327142249.63dffbb8@renoir.lan \
--to=xavier@bartica.org \
--cc=adam.s.khan@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