Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jolly Roger Newsgroups: comp.sys.mac.system Subject: Re: How does OS-X behave with a dead SSD ? Date: 4 Dec 2016 06:02:36 GMT Organization: People for the Ethical Treatment of Pirates Lines: 50 Message-ID: References: <583b3a29$0$1567$c3e8da3$12bcf670@news.astraweb.com> <583b85ff$0$10986$c3e8da3$f017e9df@news.astraweb.com> <583bd7a6$0$1557$c3e8da3$12bcf670@news.astraweb.com> <291120161456080223%JimSGibson@gmail.com> <291120161828475976%nospam@nospam.invalid> <583e6990$0$51650$c3e8da3$f6268168@news.astraweb.com> X-Trace: individual.net rwHjDTYYSV9JYJVW2fVmGwQ24IUqLeu/JdFEphOVTan9OTgCk8 Cancel-Lock: sha1:Kvvqn1K4G49oPwzM74F3T45Avqo= Mail-Copies-To: nobody User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:97528 On 2016-12-04, billy@MIX.COM wrote: > JF Mezei writes: > >> You're assuming that you will notice it crapping out. Unlike spinning >> rust discs, an SSD will continue to remain readable after writes become >> a problem. > > There is so much bullshit in this thread. I'm not going to read it all, > but here is an example of writes not failing but a read does (an OWC SSD, > although that's relevant only because I have dozens of them and this is > only the second one to have a problem) (pardon my not wrapping the text, > viewing with a 132 column wide screen is suggested) - > > disk0s2: I/O error. > 0 [Level 3] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 73046760] [LBlkNum 176045] > 0 [Level 3] [Facility com.apple.system.fs] [DevNode /dev/disk0s2] [MountPt /] [Path /private/var/db/systemstats/snapshots.db] > disk0s2: I/O error. > 0 [Level 3] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 73046760] [LBlkNum 176045] > 0 [Level 3] [Facility com.apple.system.fs] [DevNode /dev/disk0s2] [MountPt /] [Path /private/var/db/systemstats/snapshots.db] > disk0s2: I/O error. > 0 [Level 3] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 73046760] [LBlkNum 176045] > 0 [Level 3] [Facility com.apple.system.fs] [DevNode /dev/disk0s2] [MountPt /] [Path /private/var/db/systemstats/snapshots.db] > > I'm now at 15,855 of these errors. The system remains quite usable - I'm > posting this note with it, email is fine, etc. I'm guessing the defect > managemant (bad block replacement) is failing coz the bad block here can't > be read. > >> But you may encounter a situation where after saving a document, the >> middle 4 blocks contain invalid data because the SSD was unable to write >> those 4 blocks and nobody noticed. > > That'd only be because you ignored the error message thrown into the middle > of your screen. > >> This isn't FUD > > Sure it is. > > Imagining shit that does not exist is... Ummm... F.U.D. No shit. Anyone who thinks a modern OS *won't* let you know when a read or write fails is an idiot. There's nothing new to see here folks. Move along. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR