Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Tom Hunt <tomdicksonhunt@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing
Date: Sun, 24 Jan 2016 15:16:14 -0700	[thread overview]
Message-ID: <20160124221614.GH908@breitenfeld.lan> (raw)
In-Reply-To: <CAJCQCtQjCgvHqfbuKF+E0xhEydu1SdwZ3uLyq+aDL=+Yrrkm4w@mail.gmail.com>

I get "currently mounted, aborting".

If I must bring down the machine over this, I can, but I'd prefer not to.

On Sun, Jan 24, 2016 at 03:04:25PM -0700, Chris Murphy wrote:
> On Sun, Jan 24, 2016 at 2:17 PM, Tom Hunt <tomdicksonhunt@gmail.com> wrote:
> > My arrangement is two subvolumes, 'root' and 'home', directly under the root
> > subvolume. The 'root' subvolume is mounted on /, the 'home' subvolume on /home.
> > I've tried both pointing the find command at /, and mounting the root subvolume
> > on a mount directory and pointing it there. Neither show any file or directory
> > with inum 515.
> 
> Inode 515 isn't special as far as I can tell. That you get zero
> results for 'find <mp> -inum 515' and yet it appears with an error
> during a scrub is weird.
> 
> What do you get for btrfs check without --repair?
> 
> 
> 
> -- 
> Chris Murphy

-- 
Tom Hunt

  reply	other threads:[~2016-01-24 22:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 17:52 Chicken-egg: uncorrectable checksum error prevents RAID1 rebalancing Tom Hunt
2016-01-24 20:34 ` Chris Murphy
2016-01-24 20:58   ` Tom Hunt
2016-01-24 21:07     ` Chris Murphy
2016-01-24 21:17       ` Tom Hunt
2016-01-24 22:04         ` Chris Murphy
2016-01-24 22:16           ` Tom Hunt [this message]
2016-01-24 22:45             ` Chris Murphy
2016-01-25  1:06               ` Chris Murphy
2016-01-25  1:28               ` Duncan
2016-01-25  3:21               ` Tom Hunt
2016-01-25  5:58                 ` Chris Murphy

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=20160124221614.GH908@breitenfeld.lan \
    --to=tomdicksonhunt@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox