All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel got struck while scrubbing BTRFS with node- and leafsize 32768
Date: Sun, 17 Jun 2012 10:52:52 +0200	[thread overview]
Message-ID: <201206171052.52542.Martin@lichtvoll.de> (raw)
In-Reply-To: <201206162223.20392.Martin@lichtvoll.de>

Am Samstag, 16. Juni 2012 schrieb Martin Steigerwald:
> [246028.219701] btrfs csum failed ino 151001 off 9441280 csum
> 3484644058 private 2813574800 
> [246028.368763] btrfs csum failed ino
> 151001 off 9441280 csum 3484644058 private 2813574800
[…]
> I have no idea where these checksum errors might come from. 2 TB disk
> steigerwald reports good SMART status, no recent errors and is quite
> new.

I think I now have an idea where they might come from:

Bug 43511 - Partitions: Amiga RDB partition on 2 TB disk way too big, 
while OK in AmigaOS 4.1
https://bugzilla.kernel.org/show_bug.cgi?id=43511

Bug 43521 - Amiga RDB partitions: truncates miscalculated partition size 
instead of refusing to use it
https://bugzilla.kernel.org/show_bug.cgi?id=43521


This in unrelated to BTRFS.

BTRFS checksumming has made me aware of a serious issues with my Amiga RDB 
formatted backup harddisk.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  parent reply	other threads:[~2012-06-17  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 20:23 kernel got struck while scrubbing BTRFS with node- and leafsize 32768 Martin Steigerwald
2012-06-16 20:38 ` Martin Steigerwald
2012-06-16 20:39   ` Martin Steigerwald
2012-06-24 15:02     ` Martin Steigerwald
2012-06-17  8:52 ` Martin Steigerwald [this message]
2012-06-25  3:27 ` Chester
2012-06-25  7:14   ` Martin Steigerwald

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=201206171052.52542.Martin@lichtvoll.de \
    --to=martin@lichtvoll.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.