linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: superblock checksum mismatch after crash, cannot mount
Date: Sun, 24 Aug 2014 00:56:47 +0000 (UTC)	[thread overview]
Message-ID: <pan$101a9$d6ff1fb7$ae6d9b70$9c335a80@cox.net> (raw)
In-Reply-To: 20140823163803.GA9149@hungrycats.org

Zygo Blaxell posted on Sat, 23 Aug 2014 12:38:05 -0400 as excerpted:

> Consumer SD cards are /terrible/ storage devices.  Always back up all
> data written to an SD card as soon as possible after writing it, and
> develop a process to restore the backup to a new SD card conveniently
> when--not if--the card fails.
> 
> Over the years I've burned my way through dozens of SD cards in Pis,
> Beagles, x86 laptops, USB SD card readers, cameras and cell phones.
> I have more bad or failed cards than good ones in my collection, but no
> more than three of any specific model.  Brand, price, and specs don't
> correlate to success or failure.  Even the good cards wear out after
> heavy use.  The bad ones fail much faster, and are more likely to give
> you garbage data instead of properly formed I/O errors as they fail.

I had read that it was bad, but I didn't know it was /that/ bad.  The 
ones I've used have tended to be write-once, read for quite some time, 
often lose (or throw away as obsolete due to tiny size) before I write 
them again, or at least before I write them half a dozen times, and I've 
generally not has problems with them doing that, but I wouldn't tend to 
know about routine rewrite behavior.  Sounds like it's much worse than I 
might have thought.

Thanks.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-08-24  0:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 22:00 superblock checksum mismatch after crash, cannot mount Florian Gamböck
2014-08-22 22:17 ` Florian Gamböck
2014-08-23  5:27 ` Duncan
2014-08-23  8:38   ` Florian Gamböck
2014-08-23  9:34     ` Duncan
2014-08-23 14:14       ` Florian Gamböck
2014-08-24 20:29         ` Chris Murphy
2014-08-23 16:38       ` Zygo Blaxell
2014-08-24  0:56         ` Duncan [this message]
2014-08-24  2:57           ` Chris Murphy
2014-08-24 11:08           ` Leen Besselink
2014-08-24 12:49             ` Chris Samuel
2014-08-24 12:59             ` Duncan
2014-08-24 14:09             ` Florian Gamböck
  -- strict thread matches above, loose matches on Subject: below --
2014-08-24 16:59 Flash ROM
2014-08-24 18:41 ` Florian Gamböck
2014-08-24 19:48 ` Chris Murphy
2014-08-25 11:42   ` Austin S Hemmelgarn

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='pan$101a9$d6ff1fb7$ae6d9b70$9c335a80@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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 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).