From: Pavel Machek <pavel@ucw.cz>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Ming Lei <tom.leiming@gmail.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Simon Arlott <simon@octiron.net>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] scsi: sd: stop SSD (non-rotational) disks before reboot
Date: Sat, 4 Jul 2020 13:49:17 +0200 [thread overview]
Message-ID: <20200704114917.GB16083@amd> (raw)
In-Reply-To: <2c38b7cd0aad46ec9f8bf03715109f10@AcuMS.aculab.com>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
Hi!
> > Sent: 02 July 2020 22:17
> > > > during a FLASH write or erase can cause from weakened cells, to much
> > > > larger damage. It is possible to harden the chip or the design against
> > > > this, but it is *expensive*. And even if warded off by hardening and no
> > > > FLASH damage happens, an erase/program cycle must be done on the whole
> > > > erase block to clean up the incomplete program cycle.
> > >
> > > It should have been SSD's(including FW) responsibility to avoid data loss when
> > > the SSD is doing its own BG writing, because power cut can happen any time
> > > from SSD's viewpoint.
> >
> > It should be their responsibility. But we know how well that works
> > (not well), so we try hard (and should try hard) to power SSDs down
> > cleanly.
>
> I hope modern SSD disks are better than very old CF drives.
Testing showed there were not few yars ago.
> I had one where the entire contents got scrambled after an unexpected
> power removal.
If you have SSD you are willing to kill, I believe you can get to same
result with a bit of patience.
Best regards,
Pavel--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-07-04 11:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 18:49 [PATCH] scsi: sd: stop SSD (non-rotational) disks before reboot Simon Arlott
2020-06-17 19:19 ` Bart Van Assche
2020-06-17 19:32 ` Simon Arlott
2020-06-18 7:21 ` Christoph Hellwig
2020-06-18 12:25 ` Simon Arlott
2020-06-18 13:49 ` Christoph Hellwig
2020-07-05 21:31 ` Henrique de Moraes Holschuh
2020-07-07 10:18 ` Christoph Hellwig
2020-06-18 8:36 ` Damien Le Moal
2020-06-18 12:25 ` Simon Arlott
2020-06-18 23:31 ` Damien Le Moal
2020-06-28 18:23 ` Simon Arlott
2020-06-30 1:05 ` Damien Le Moal
2020-06-23 13:36 ` Pavel Machek
2020-06-28 18:22 ` Simon Arlott
2020-06-23 20:42 ` Henrique de Moraes Holschuh
2020-06-28 18:31 ` Simon Arlott
2020-06-28 19:42 ` Henrique de Moraes Holschuh
2020-06-30 3:31 ` Ming Lei
2020-07-02 21:16 ` Pavel Machek
2020-07-03 14:13 ` David Laight
2020-07-04 11:49 ` Pavel Machek [this message]
2020-07-05 22:19 ` Henrique de Moraes Holschuh
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=20200704114917.GB16083@amd \
--to=pavel@ucw.cz \
--cc=Damien.LeMoal@wdc.com \
--cc=David.Laight@ACULAB.COM \
--cc=corbet@lwn.net \
--cc=hmh@hmh.eng.br \
--cc=jejb@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=simon@octiron.net \
--cc=tom.leiming@gmail.com \
/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).