All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arne Jansen <sensille@gmx.net>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: what does "scrub" mean?
Date: Wed, 02 Nov 2011 19:00:32 +0100	[thread overview]
Message-ID: <4EB18540.8060105@gmx.net> (raw)
In-Reply-To: <Bx5IeZ5y1uB@helmut.hullen.de>

On 11/02/2011 06:41 PM, Helmut Hullen wrote:
> Hallo,
> 
> I'd like to get some explanations ...
> 
> 
> # btrfs filesystem show
> 
> Label: 'MMedia'  uuid: 120b036a-883f-46aa-bd9a-cb6a1897c8d2
> 	Total devices 3 FS bytes used 3.80TB
> 	devid    1 size 1.82TB used 1.29TB path /dev/sdg1
> 	devid    3 size 1.81TB used 1.29TB path /dev/sdc1
> 	devid    2 size 1.81TB used 1.28TB path /dev/sdb1
> 
> Btrfs Btrfs v0.19
> 
> # btrfs filesystem df /srv/MM
> 
> Data, RAID0: total=3.83TB, used=3.80TB
> System, RAID1: total=16.00MB, used=248.00KB
> System: total=4.00MB, used=0.00
> Metadata, RAID1: total=16.25GB, used=4.93GB
> 
> # btrfs scrub status /srv/MM
> 
> scrub status for 120b036a-883f-46aa-bd9a-cb6a1897c8d2
> 	scrub resumed at Wed Nov  2 17:02:07 2011 and was aborted after 16519 seconds
> 	total bytes scrubbed: 1.79TB with 61 errors
> 	error details: read=4 verify=21 csum=36
> 	corrected errors: 28, uncorrectable errors: 24, unverified errors: 0
> 

can you also show the output in dmesg? Maybe the extent tree is
damaged to a point where it can't be fully traversed.

> # ------------------------------------------------------------
> 
> Why has "scrub" finished its work after less than 1/3 of the bundle?
> 

  reply	other threads:[~2011-11-02 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 17:41 what does "scrub" mean? Helmut Hullen
2011-11-02 18:00 ` Arne Jansen [this message]
2011-11-02 18:37   ` Helmut Hullen

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=4EB18540.8060105@gmx.net \
    --to=sensille@gmx.net \
    --cc=Hullen@t-online.de \
    --cc=helmut@hullen.de \
    --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.