linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Russell Coker <russell+btrfs@coker.com.au>
Cc: "linux-btrfs@vger.kernel.org list" <linux-btrfs@vger.kernel.org>
Subject: Re: 2 errors on scrub
Date: Thu, 10 Jan 2013 08:55:23 +0000	[thread overview]
Message-ID: <20130110085523.GS19051@carfax.org.uk> (raw)
In-Reply-To: <201301101138.45428.russell+btrfs@coker.com.au>

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

On Thu, Jan 10, 2013 at 11:38:45AM +1100, Russell Coker wrote:
> The below is from a system running the Debian kernel 3.2.0-4-amd64 on a 120G 
> Intel SSD.  What would these 2 errors be?
> 
> scrub device /dev/disk/by-uuid/7939c405-c656-4e85-a6a0-29f17be09585 (id 1) 
> done
>         scrub started at Thu Jan 10 06:00:02 2013 and finished after 295 
> seconds
>         total bytes scrubbed: 25.42GB with 2 errors
>         error details: super=2
>         corrected errors: 0, uncorrectable errors: 0, unverified errors: 0

   Looks like broken superblocks, from that message. There's probably
more information in your kernel logs.

> I know you all recommend later kernels, I'm upgrading things as fast as I can.

   Glad to hear it. :)

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
       --- We believe in free will because we have no choice. ---        

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

  reply	other threads:[~2013-01-10  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10  0:38 2 errors on scrub Russell Coker
2013-01-10  8:55 ` Hugo Mills [this message]
2013-01-10 11:01   ` Russell Coker
2013-01-10 12:04 ` David Sterba
2013-01-12  1:56   ` Russell Coker

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=20130110085523.GS19051@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell+btrfs@coker.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).