linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Calvin Walton <calvin.walton@kepstin.ca>
Cc: Nikolaus Rath <Nikolaus@rath.org>, linux-btrfs@vger.kernel.org
Subject: Re: File system stuck in scrub
Date: Mon, 11 Aug 2014 08:53:19 -0700	[thread overview]
Message-ID: <20140811155319.GD25324@merlins.org> (raw)
In-Reply-To: <1407771945.6404.1.camel@kepstin.ca>

On Mon, Aug 11, 2014 at 11:45:45AM -0400, Calvin Walton wrote:
> > $ sudo btrfs scrub start /home/nikratio/
> > ERROR: scrub is already running.
> > To cancel use 'btrfs scrub cancel /home/nikratio/'.
> > To see the status use 'btrfs scrub status [-d] /home/nikratio/'.
> My guess is that this is a mismatch between some state stored by the 
> userspace tools and the state in the kernel. One of the things you can 
> try is to delete the files /var/lib/btrfs/scrub.status.* - that will 
> force the btrfs tools to get the current status from the kernel (you 
> will lose some statistics and scrub history.)

No need to really delete it, just changing one character will do :)

http://marc.merlins.org/perso/btrfs/post_2014-04-26_Btrfs-Tips_-Cancel-A-Btrfs-Scrub-That-Is-Already-Stopped.html

Cheers,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

      reply	other threads:[~2014-08-11 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 15:12 File system stuck in scrub Nikolaus Rath
2014-08-11 15:37 ` Hugo Mills
2014-08-11 15:45 ` Calvin Walton
2014-08-11 15:53   ` Marc MERLIN [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=20140811155319.GD25324@merlins.org \
    --to=marc@merlins.org \
    --cc=Nikolaus@rath.org \
    --cc=calvin.walton@kepstin.ca \
    --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).