Date: Thu, 5 Jul 2018 12:31:20 -0600 From: Warner Losh <imp@bsdimp.com> To: Stefan Blachmann <sblachmann@gmail.com> Cc: Wojciech Puchar <wojtek@puchar.net>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, George Mitchell <george+freebsd@m5p.com>, Lev Serebryakov <lev@freebsd.org> Subject: Re: Confusing smartd messages Message-ID: <CANCZdfo6NTf9W_9xF-ucpBi6Ju8_kx7=rT03FbwDHDdzMdxrZw@mail.gmail.com> In-Reply-To: <CACc-My36jbL=WWpxOB24D_YLDMofSHAk9JgrP86LKd4MEct1mg@mail.gmail.com> References: <dfccd275-954c-11da-1790-e75878f89ad1@m5p.com> <51eb8232-49a7-0b3a-2d0f-9882ebfbfa1d@FreeBSD.org> <alpine.BSF.2.20.1807051642090.17082@puchar.net> <CACc-My36jbL=WWpxOB24D_YLDMofSHAk9JgrP86LKd4MEct1mg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 5, 2018, 11:13 AM Stefan Blachmann <sblachmann@gmail.com> wrote: > Another problem issue is that flash memories also exhibit the charge > drain problem. > They cannot be read indefinitely without occasional rewrite, as every > read drains a minuscule amount of the charge. > It usually takes ~500k reads to hit this issue. I often wished I knew of some OS/driver function/mechanism which can > rewrite respective refresh media on a mounted+running system and could > be, for example, run via cron. > The FTL is supposed to take care of that. They typically have a scanning function that moves the data when it decays enough to be of concern... doing it at the LBA later is unlikely to produce satisfactory results. Such would not only be very useful to fix pending sectors without > stopping a running machine, but also for keeping embedded machines' > flash memories reliably charged over the years. > Not really.. Warner > On 7/5/18, Wojciech Puchar <wojtek@puchar.net> wrote: > >>> okay. What's the recommended action at this point? -- George > >> > >> In my experience it is begin of disk death, even if overall status is > >> PASSED. It could work for month or may be half a year after first > >> Offline_Uncorrectable is detected (it depends on load), but you best bet > >> to replace it ASAP and throw away. > > well my disk had this and live happily for 3 years. > > > > It JUST means that some sectors are unreadable which may be a reason that > > at some some write got wrong because of hardware problem. But this > problem > > may be - and possibly were - powerdown while writing, or power spike. > > > > the media itself could be fine. the best action in such case is to force > > rewrite whole drive with some data. > > > > with gmirror it is as easy as first checking second drive for no errors, > > then forcing remirror. > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfo6NTf9W_9xF-ucpBi6Ju8_kx7=rT03FbwDHDdzMdxrZw>