linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arun Persaud <apersaud@lbl.gov>
To: linux-btrfs@vger.kernel.org
Subject: Re: error 2001, no inode item
Date: Mon, 05 May 2014 15:22:17 -0700	[thread overview]
Message-ID: <lk92uq$j8n$1@ger.gmane.org> (raw)
In-Reply-To: <li19og$m51$1@ger.gmane.org>

Hi

tried with a newer version of btrfs, but still getting the same error.

checking extents
checking free space cache
checking fs roots
root 5 inode 5769204 errors 2001, no inode item, link count wrong
        unresolved ref dir 5783881 index 3 namelen 38 name
61bd2ed1fba8bc8d2f12766c7e4b3dafff6350 filetype 1 error 4, no inode ref
root 5 inode 5899187 errors 2001, no inode item, link count wrong
        unresolved ref dir 5906761 index 3 namelen 38 name
61bd2ed1fba8bc8d2f12766c7e4b3dafff6350 filetype 1 error 0
Checking filesystem on /dev/sda4
UUID: 98190f1e-426f-433d-8335-1216b9a63d16
found 28521431809 bytes used err is 1
total csum bytes: 124070732
total tree bytes: 722415616
total fs tree bytes: 552411136
total extent tree bytes: 32673792
btree space waste bytes: 171189111
file data blocks allocated: 188149448704
 referenced 126695161856
Btrfs v3.14.1+20140502

# uname -a
Linux apersaud 3.14.2-25.g1474ea5-desktop #1 SMP PREEMPT Sun Apr 27
14:35:22 UTC 2014 (1474ea5) x86_64 x86_64 x86_64 GNU/Linux

Any idea how I can fix the missing inode problem?

Arun


      reply	other threads:[~2014-05-06 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 23:14 error 2001, no inode item Arun Persaud
2014-04-08 12:10 ` Duncan
2014-04-08 16:56   ` Arun Persaud
2014-05-05 22:22     ` Arun Persaud [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='lk92uq$j8n$1@ger.gmane.org' \
    --to=apersaud@lbl.gov \
    --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).