All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Thomas Koch <thomas@koch.ro>
Cc: Josef Bacik <JBacik@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Stale NFS file handle after power loss
Date: Thu, 13 Jun 2013 21:27:56 -0400	[thread overview]
Message-ID: <20130614012756.GF658@localhost.localdomain> (raw)
In-Reply-To: <201306132145.29326.thomas@koch.ro>

On Thu, Jun 13, 2013 at 01:45:29PM -0600, Thomas Koch wrote:
> Thomas Koch:
> > On Monday, June 10, 2013 09:00:47 AM Josef Bacik wrote:
> > > On Sat, Jun 08, 2013 at 01:14:35PM -0600, Thomas Koch wrote:
> > > > Hi,
> > > > 
> > > > I had a power loss on my btrfs file system during package installation
> > > > and now I found this:
> > > > 
> > > > <code>
> > > > % ls -l /var/lib/dpkg/tmp.ci
> > > > ls: cannot access /var/lib/dpkg/tmp.ci/conffiles: Stale NFS file handle
> > > > ls: cannot access /var/lib/dpkg/tmp.ci/md5sums: Stale NFS file handle
> > > > total 0
> > > > -????????? ? ? ? ?            ? conffiles
> > > > -????????? ? ? ? ?            ? md5sums
> > > > % sudo rm -rf /var/lib/dpkg/tmp.ci/conffiles
> > > > rm: cannot remove ‘/var/lib/dpkg/tmp.ci/conffiles’: Stale NFS file
> > > > handle </code>
> > > > 
> > > > I booted with a live system and ran btrfsck (without --repair!) but
> > > > this did not change the situation. Unfortunately I wasn't clever
> > > > enough to save the output of btrfsck somehow. Do you need it?
> > > > 
> > > > Could you help me to get rid of these bogus files, please?
> > > 
> > > Don't run with --repair, but please capture the output so I can see
> > > what's going wrong.  Thanks,
> > > 
> > > Josef
> > 
> > sudo btrfsck /dev/x121e/root
> > checking extents
> > checking fs roots
> > root 5 inode 9319255 errors 1040
> > root 5 inode 9698560 errors 1000
> > root 5 inode 11591532 errors 2001
> >         unresolved ref dir 11591531 index 2 namelen 9 name conffiles
> > filetype 1 error 4
> > root 5 inode 11591534 errors 2001
> >         unresolved ref dir 11591531 index 4 namelen 7 name md5sums filetype
> > 1 error 4
> > found 270172975104 bytes used err is 1
> > total csum bytes: 261797296
> > total tree bytes: 2063106048
> > total fs tree bytes: 1575575552
> > btree space waste bytes: 561459705
> > file data blocks allocated: 386128334848
> >  referenced 262981738496
> > Btrfs Btrfs v0.19
> 
> Hi Josef,
> 
> do you think that you might find some solution to this problem or should I plan 
> to re-setup my machine?
> 

Yup sorry I just got sidetracked, I'll see what can be done tomorrow, but your
best bet it so pull down the latest btrfs-progs and build it and run

./btrfs-image /dev/whatever blah.img

and put the image up somewhere I can pull it down so I can fix btrfsck to fix
your file system and test it locally before I send you the patch.  Thanks,

Josef

  reply	other threads:[~2013-06-14  1:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08 19:14 Stale NFS file handle after power loss Thomas Koch
2013-06-10 13:00 ` Josef Bacik
2013-06-10 18:18   ` Thomas Koch
2013-06-13 19:45     ` Thomas Koch
2013-06-14  1:27       ` Josef Bacik [this message]
2013-06-15 10:33         ` Russell Coker

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=20130614012756.GF658@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=thomas@koch.ro \
    /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.