All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Wolfgang Rohdewald <wolfgang.kde@rohdewald.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub can neither start nor cancel
Date: Tue, 8 Dec 2015 20:51:08 +0000	[thread overview]
Message-ID: <20151208205108.GD2376@carfax.org.uk> (raw)
In-Reply-To: <31519331.YQjdnfjTR6@i5>

[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]

On Tue, Dec 08, 2015 at 09:46:48PM +0100, Wolfgang Rohdewald wrote:
> I just tried this script:
> http://marc.merlins.org/perso/btrfs/2014-03.html#Btrfs-Tips_-Btrfs-Scrub-and-Btrfs-Filesystem-Repair
> 
> but I did not pass the directory where the filesystem is mounted.
> 
> Next I called it correctly: btrfs-scrub /t4
> I also tried btrfs scrub start / cancel directly, but 
> I am not really sure what I did in which order.
> 
> Anyway now I can neither cancel nor start btrfs scrub. Rebooting did not help.

   It might be that the userspace tools has got confused and left
behind a lock/pid/progress file in /var/lib/btrfs/

   Take a look in there and see if there's anything that you can
delete to good effect?

   Hugo.

> Running unmodified Linux 4.3
> 
> It seems like scrub stopped and did not clean up. Maybe because:
> Dec  8 21:07:41 s5 kernel: [17833.840868] btrfs[23746]: segfault at ffffffffffffff98 ip 00000000004079e1 sp 00007fffafa27510 error 5 in btrfs[400000+53000]
> 
> How can I now clean this up?
> 
> root@s5:~# btrfs --version
> Btrfs v3.12
> 
> root@s5:~# btrfs scrub status /t4
> scrub status for 700900de-e35f-4264-8f5d-1b2b249a5c3a
>         scrub started at Tue Dec  8 21:05:31 2015, running for 20 seconds
>         total bytes scrubbed: 3.09GiB with 0 errors
> 
> root@s5:~# btrfs scrub cancel /t4
> ERROR: scrub cancel failed on /t4: not running
> 
> root@s5:~# btrfs scrub start /t4
> ERROR: scrub is already running.
> To cancel use 'btrfs scrub cancel /t4'.
> To see the status use 'btrfs scrub status [-d] /t4'.
> 
> 

-- 
Hugo Mills             | Go not to the elves for counsel, for they will say
hugo@... carfax.org.uk | both no and yes.
http://carfax.org.uk/  |
PGP: E2AB1DE4          |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-12-08 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 20:46 btrfs scrub can neither start nor cancel Wolfgang Rohdewald
2015-12-08 20:51 ` Hugo Mills [this message]
2015-12-08 22:52   ` Wolfgang Rohdewald

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=20151208205108.GD2376@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wolfgang.kde@rohdewald.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.