All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Florian Lindner <mailinglists@xgm.de>, <linux-btrfs@vger.kernel.org>
Subject: Re: Scrub being stuck
Date: Mon, 30 Jun 2014 14:37:49 +0800	[thread overview]
Message-ID: <53B105BD.4010907@cn.fujitsu.com> (raw)
In-Reply-To: <lophhk$nj1$2@ger.gmane.org>

On 06/30/2014 01:14 AM, Florian Lindner wrote:
> Hello,
>
> I've just completed a scrub on my home filesystem and now I wanted to start
> on my Archiv btrfs RAID 0.
>
> root@horus ~ # uname -
> a
> Linux horus 3.15.2-1-ARCH #1 SMP PREEMPT Fri Jun 27 07:41:19 CEST 2014
> x86_64 GNU/Linux
>
> root@horus ~ # btrfs --version
> Btrfs v3.14.2-dirty
>
> root@horus ~ # btrfs fi show
> Label: 'home'  uuid: 571009c0-6cc4-4598-a77b-f175501d23fd
>          Total devices 1 FS bytes used 2.03TiB
>          devid    1 size 2.73TiB used 2.04TiB path /dev/sdb1
>
> Label: 'Archiv'  uuid: b2504193-efeb-4ef3-8797-a8d73536a416
>          Total devices 2 FS bytes used 5.14TiB
>          devid    1 size 2.73TiB used 2.73TiB path /dev/sdd1
>          devid    2 size 2.73TiB used 2.73TiB path /dev/sde1
>
> Btrfs v3.14.2-dirty
>
> root@horus ~ # btrfs fi df /mnt/Archiv
> Data, RAID0: total=5.44TiB, used=5.13TiB
> Data, single: total=8.00MiB, used=244.00KiB
> System, RAID1: total=32.00MiB, used=396.00KiB
> System, single: total=4.00MiB, used=0.00
> Metadata, RAID1: total=10.94GiB, used=8.71GiB
> unknown, single: total=512.00MiB, used=0.00
>
> root@horus ~ # btrfs scrub status /mnt/Archiv
> scrub status for b2504193-efeb-4ef3-8797-a8d73536a416
>          scrub started at Thu Jan  2 21:13:35 2014, running for 1336 seconds
>          total bytes scrubbed: 473.28GiB with 0 errors
>
> root@horus ~ # btrfs scrub cancel /mnt/Archiv
> ERROR: scrub cancel failed on /mnt/Archiv: not running
>
> root@horus ~ # btrfs scrub resume
> /mnt/Archiv
> ERROR: scrub is already running.
> To cancel use 'btrfs scrub cancel /mnt/Archiv'.
> To see the status use 'btrfs scrub status [-d] /mnt/Archiv'.
>
> root@horus ~ # btrfs scrub start
> /mnt/Archiv
> ERROR: scrub is already running.
> To cancel use 'btrfs scrub cancel /mnt/Archiv'.
> To see the status use 'btrfs scrub status [-d] /mnt/Archiv'.
>
>
> A scrub I started at Jan 02 seems to be stuck somehow. The command outputs
> above were generated right now.
>
> I'll be hapy to provide any more information.
>
> Thx!
>
> Florian
Scrub log record file seems corrupted sometimes, if you use latest 
btrfs-progs version.
There should be an option '-f' for 'btrfs scrub start' which will allow 
scrub to skip check in userspace.

Actually, i am thinking whether it would be better to remove userspace 
check about
scrub status since log record file is not so reliable.

Thanks,
Wang
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> .
>


  parent reply	other threads:[~2014-06-30  6:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 17:14 Scrub being stuck Florian Lindner
2014-06-29 17:17 ` Florian Lindner
2014-06-29 23:06 ` Holger Hoffstätte
2014-06-30  6:37 ` Wang Shilong [this message]
2014-07-01  8:53 ` Florian Lindner

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=53B105BD.4010907@cn.fujitsu.com \
    --to=wangsl.fnst@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mailinglists@xgm.de \
    /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.