All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Scrub bug on kernel 3.13
Date: Mon, 07 Apr 2014 11:12:52 +0200	[thread overview]
Message-ID: <2486343.V0VCIWFSzf@zafu> (raw)
In-Reply-To: <20140407090236.GW7442@carfax.org.uk>

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

Le lundi 7 avril 2014 10:02:36 Hugo Mills a écrit :
>    There's a status file in /var/lib/btrfs (at least, it's somewhere
> near there -- I think that's it, though). Delete that

# rm /var/lib/btrfs/scrub.status.13c87f57-3a85-4daf-a4bf-ba777407c169

> and you should be OK.

I'm OK, thanks ! :-)

> What version of the tools are you using?

Latest Arch available version:

# pacman -Qi btrfs-progs
Name           : btrfs-progs
Version        : 3.12-1
Description    : btrfs filesystem utilities
Architecture   : x86_64
URL            : http://btrfs.wiki.kernel.org/
[...]
Provides       : btrfs-progs-unstable
[...]
Conflicts With : btrfs-progs-unstable
Replaces       : btrfs-progs-unstable
Installed Size : 2480,00 KiB
Packager       : Tom Gundersen <teg@jklm.no>
Build Date     : mer. 27 nov. 2013 12:24:33 CET
Install Date   : dim. 22 déc. 2013 09:48:58 CET
Install Reason : Explicitly installed
Install Script : Yes
Validated By   : Signature

Thanks again :-)

-- 
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

      reply	other threads:[~2014-04-07  9:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07  8:32 Scrub bug on kernel 2.13 Swâmi Petaramesh
2014-04-07  8:40 ` Swâmi Petaramesh
2014-04-07  9:02 ` Hugo Mills
2014-04-07  9:12   ` Swâmi Petaramesh [this message]

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=2486343.V0VCIWFSzf@zafu \
    --to=swami@petaramesh.org \
    --cc=hugo@carfax.org.uk \
    --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 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.