Btrfs devel - Dec 2013 - scub neither running nor canceling nor can be restarted.

Hello,

I am having a problem where a stuck scrub on root FS cannot be
cancelled or restsrted.

Please See:
[root@mail2 ~]# btrfs filesystem show
Label: fedora_mail2  uuid: d2b3420c-99c1-44cc-a922-ac266072c7fb
Total devices 2 FS bytes used 58.88GiB
devid    2 size 73.51GiB used 31.03GiB path /dev/sdb6
devid    3 size 73.30GiB used 32.03GiB path /dev/sda2

Label: Vikram  uuid: 0809b072-35f3-4866-92b8-af4772b23ed6
Total devices 2 FS bytes used 98.05GiB
devid    1 size 158.03GiB used 99.04GiB path /dev/mapper/sda3
devid    2 size 157.00GiB used 99.03GiB path /dev/dm-1

Btrfs v3.12
[root@mail2 ~]# btrfs scrub status -d /
scrub status for d2b3420c-99c1-44cc-a922-ac266072c7fb
scrub device /dev/sdb6 (id 2) status
scrub started at Thu Apr 18 13:51:13 2013, running for 105 seconds
total bytes scrubbed: 3.81GiB with 0 errors
scrub device /dev/sda2 (id 3) status
scrub started at Thu Apr 18 13:51:13 2013, running for 105 seconds
total bytes scrubbed: 4.34GiB with 0 errors

[root@mail2 ~]# btrfs scrub cancel /
ERROR: scrub cancel failed on /: not running

[root@mail2 ~]# btrfs scrub start -Bd /
ERROR: scrub is already running.
To cancel use ''btrfs scrub cancel /''.
To see the status use ''btrfs scrub status [-d] /''.

Thanks!
-- 
--
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

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.
>
> Please See:
> [root@mail2 ~]# btrfs filesystem show
> Label: fedora_mail2  uuid: d2b3420c-99c1-44cc-a922-ac266072c7fb
> Total devices 2 FS bytes used 58.88GiB
> devid    2 size 73.51GiB used 31.03GiB path /dev/sdb6
> devid    3 size 73.30GiB used 32.03GiB path /dev/sda2
>
> Label: Vikram  uuid: 0809b072-35f3-4866-92b8-af4772b23ed6
> Total devices 2 FS bytes used 98.05GiB
> devid    1 size 158.03GiB used 99.04GiB path /dev/mapper/sda3
> devid    2 size 157.00GiB used 99.03GiB path /dev/dm-1
>
> Btrfs v3.12
> [root@mail2 ~]# btrfs scrub status -d /
> scrub status for d2b3420c-99c1-44cc-a922-ac266072c7fb
> scrub device /dev/sdb6 (id 2) status
> scrub started at Thu Apr 18 13:51:13 2013, running for 105 seconds
> total bytes scrubbed: 3.81GiB with 0 errors
> scrub device /dev/sda2 (id 3) status
> scrub started at Thu Apr 18 13:51:13 2013, running for 105 seconds
> total bytes scrubbed: 4.34GiB with 0 errors
>
> [root@mail2 ~]# btrfs scrub cancel /
> ERROR: scrub cancel failed on /: not running
>
> [root@mail2 ~]# btrfs scrub start -Bd /
> ERROR: scrub is already running.
> 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
> Thanks!
--
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

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.
>
> Please See:
> [root@mail2 ~]# btrfs filesystem show
> Label: fedora_mail2  uuid: d2b3420c-99c1-44cc-a922-ac266072c7fb
> Total devices 2 FS bytes used 58.88GiB
> devid    2 size 73.51GiB used 31.03GiB path /dev/sdb6
> devid    3 size 73.30GiB used 32.03GiB path /dev/sda2
>
> Label: Vikram  uuid: 0809b072-35f3-4866-92b8-af4772b23ed6
> Total devices 2 FS bytes used 98.05GiB
> devid    1 size 158.03GiB used 99.04GiB path /dev/mapper/sda3
> devid    2 size 157.00GiB used 99.03GiB path /dev/dm-1
>
> Btrfs v3.12
> [root@mail2 ~]# btrfs scrub status -d /
> scrub status for d2b3420c-99c1-44cc-a922-ac266072c7fb
> scrub device /dev/sdb6 (id 2) status
> scrub started at Thu Apr 18 13:51:13 2013, running for 105 seconds
> total bytes scrubbed: 3.81GiB with 0 errors
> scrub device /dev/sda2 (id 3) status
> scrub started at Thu Apr 18 13:51:13 2013, running for 105 seconds
> total bytes scrubbed: 4.34GiB with 0 errors
>
> [root@mail2 ~]# btrfs scrub cancel /
> ERROR: scrub cancel failed on /: not running
>
> [root@mail2 ~]# btrfs scrub start -Bd /
> ERROR: scrub is already running.
> 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
> Thanks!
--
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

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!
-- 
--
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

On 12/09/2013 08:18 PM, Vikram Goyal wrote:
> 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
I think one way to slove this problms is:

# rm -f  /var/lib/btrfs/*

This will remove scrub status record file, and then you can start scrub 
again.

Thanks,
Wang
>
> Thanks!
--
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