From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs suddenly unmountable, open_ctree failed
Date: Tue, 24 Jun 2014 10:00:14 +0000 (UTC) [thread overview]
Message-ID: <pan$240f5$66208982$352d3c2d$120cf64f@cox.net> (raw)
In-Reply-To: 27F042E8-CC94-497D-96B7-283AA1CBD296@colorremedies.com
Chris Murphy posted on Mon, 23 Jun 2014 23:19:37 -0600 as excerpted:
>> I zeroed out the drive and ran every smartctl test on it I could find
>> and it never threw any more errors.
>
> Zeroing SSDs isn't a good way to do it. Use ATA Secure Erase instead.
> The drive is overprovisioned, so there are pages without LBAs assigned,
> which means they can't be written to by software. Plus "zeros" make SSD
> pages full of zeros, rather than being empty and ready to be written to.
> ATA Secure Erase is supposed to make them empty (write ready) and does
> it for all pages.
>
> http://mackonsti.wordpress.com/2011/11/22/ssd-secure-erase-ata-command/
Tho in this case, the bad section was obviously assigned as it was
triggering errors, and writing zeros to the entire thing might just have
triggered the drive to cycle the bad area out of use, replacing it from
the reserves.
So while zeroing an SSD is a bad idea in general, it still might be
worthwhile to try in a case like this, particularly if after a a secure-
erase command the media is still giving errors.
IOW, YMMV. =:^)
--
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
prev parent reply other threads:[~2014-06-24 10:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 22:18 Btrfs suddenly unmountable, open_ctree failed Mike Hartman
2014-06-24 1:17 ` Chris Murphy
2014-06-24 2:20 ` Wang Shilong
2014-06-24 3:04 ` Mike Hartman
2014-06-24 3:09 ` Wang Shilong
2014-06-24 5:39 ` Mike Hartman
2014-06-24 15:40 ` Chris Murphy
2014-06-24 2:58 ` Mike Hartman
2014-06-24 4:15 ` Chris Murphy
2014-06-24 4:49 ` Mike Hartman
[not found] ` <CAB=7dhms_ehP4y+L_tMBrdUnJiwXAOn7E4Fa9u3euVBwBKHOKA@mail.gmail.com>
2014-06-24 5:19 ` Chris Murphy
2014-06-24 5:49 ` Mike Hartman
2014-06-24 16:15 ` Chris Murphy
2014-06-25 5:53 ` Mike Hartman
2014-06-25 18:38 ` Chris Murphy
2014-06-25 19:32 ` Mike Hartman
2014-06-25 19:50 ` Chris Murphy
2014-06-24 10:00 ` Duncan [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='pan$240f5$66208982$352d3c2d$120cf64f@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).