public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: "Graham Cobb" <g.btrfs@cobb.uk.net>,
	"Sebastian Döring" <moralapostel@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub: cancel + resume not resuming?
Date: Thu, 9 Jan 2020 12:16:49 +0100	[thread overview]
Message-ID: <5a54869e-e268-2423-3a51-a8752d355c92@applied-asynchrony.com> (raw)
In-Reply-To: <bafe1610-914b-c9b4-3f04-a0fdcc97d256@applied-asynchrony.com>

On 1/9/20 12:05 PM, Holger Hoffstätte wrote:
> $cat test-scrub
> #!/bin/sh
> btrfs scrub start /mnt/backup
> sleep 30
> btrfs scrub status -R /mnt/backup
> btrfs scrub cancel /mnt/backup
> btrfs scrub resume /mnt/backup
> sleep 10
> btrfs scrub status -R /mnt/backup
> 
[snip]
>      last_physical: 3591372800
>          ^^^^^^^^^^^^^^^^^^^^^^^^^
[snip]
>      last_physical: 923205632
>          ^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Not sure what I'm doing wrong ;)

AARGH. What I'm doing wrong is that I can't read and that it indeed seems
to start from the beginning. Nice catch!

-h

  parent reply	other threads:[~2020-01-09 11:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 10:03 btrfs scrub: cancel + resume not resuming? Sebastian Döring
2020-01-09 10:19 ` Graham Cobb
2020-01-09 17:06   ` Graham Cobb
2020-01-09 20:35     ` Graham Cobb
2020-01-13 13:57       ` btrfs scrub: cancel + resume not resuming - kernel regression Graham Cobb
2020-01-09 10:34 ` btrfs scrub: cancel + resume not resuming? Holger Hoffstätte
2020-01-09 10:52   ` Graham Cobb
2020-01-09 11:05     ` Holger Hoffstätte
2020-01-09 11:13       ` Graham Cobb
2020-01-09 11:16       ` Holger Hoffstätte [this message]
2020-01-22 15:52 ` David Sterba

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=5a54869e-e268-2423-3a51-a8752d355c92@applied-asynchrony.com \
    --to=holger@applied-asynchrony.com \
    --cc=g.btrfs@cobb.uk.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=moralapostel@gmail.com \
    /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