Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Vikram Goyal <vikigoyal@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: scub neither running nor canceling nor can be restarted.
Date: Mon, 9 Dec 2013 17:48:56 +0530	[thread overview]
Message-ID: <20131209121856.GA18083@mail2.smcindiaonline.com> (raw)
In-Reply-To: <52A59EF7.8050007@cn.fujitsu.com>

On Mon, Dec 09, 2013 at 06:44:07PM +0800, Wang Shilong wrote:
> Hello Vikram,
> 
> On 12/09/2013 05:51 PM, Vikram Goyal wrote:
> >Hello,
> >
> >I am having a problem where a stuck scrub on root FS cannot be
> >cancelled or restsrted.
> >
<snip>
> >To cancel use 'btrfs scrub cancel /'.
> >To see the status use 'btrfs scrub status [-d] /'.
> I came the same issue before and i sent a patch for this:
> https://patchwork.kernel.org/patch/3264051/
> 
> This patch has been merged into David's integration branch.
> You can pull from:
> 
> https://github.com/kdave/btrfs-progs.git integration-20131206
> 
> you can use:
> # btrfs scrub start -f /
> 
> This should help, -f will force us to skip check in userspace.
> 
> Thanks,
> Wang

Hello Wang,

I am on Fedora 19. I just checked, I don't have -f as option in
btrfs-progs. The installed version is:

btrfs-progs.x86_64                  3.12-1.fc18         @updates

current kernel is 3.11.9-100.fc18.x86_64

I just wanted to know if its not dangerous to have this state of FS
since I will wait for the update to come from the repo rather than build
package myself

Thanks!
-- 

  reply	other threads:[~2013-12-09 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09  9:51 scub neither running nor canceling nor can be restarted Vikram Goyal
2013-12-09 10:44 ` Wang Shilong
2013-12-09 12:18   ` Vikram Goyal [this message]
2013-12-09 12:23     ` Wang Shilong
2013-12-09 10:58 ` Wang Shilong

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=20131209121856.GA18083@mail2.smcindiaonline.com \
    --to=vikigoyal@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