Date: Mon, 26 Mar 2018 13:39:50 -0700 From: Chuck Tuffli <chuck@tuffli.net> To: Mark Saad <nonesuch@longcount.org> Cc: Michael Dexter <editor@callfortesting.org>, freebsd-fs@freebsd.org Subject: Re: smart(8) Call for Testing Message-ID: <CAM0tzX1oTWTa0Nes11yXg5x4c30MmxdUyT6M1_c4-PWv2%2BQbhw@mail.gmail.com> In-Reply-To: <CAMXt9NbdN119RrHnZHOJD1T%2BHNLLpzgkKVStyTm=49dopBMoAQ@mail.gmail.com> References: <4754cb2f-76bb-a69b-0cf5-eff4d621eb29@callfortesting.org> <CAMXt9NbdN119RrHnZHOJD1T%2BHNLLpzgkKVStyTm=49dopBMoAQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 26, 2018 at 1:25 PM, Mark Saad <nonesuch@longcount.org> wrote: > Mike / Chuck > Silly question , how does it handle a failed disk ? It depends on how failed the device is. The application uses CAM to send pass-through commands. So, if the device doesn't appear in camcontrol devlist, you'd get "no such device" or a message from CAM indicating you might need to load a module. If the device is still registered with the system but not processing commands, I'd expect (hope?) the commands to timeout. In either case, there may not be any out put, but the exit status should be non-zero. On the other hand, if the disk is in some sort of Monty Python-eske "I'm not dead" state and responds to SMART / admin commands, you could see the output. --chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM0tzX1oTWTa0Nes11yXg5x4c30MmxdUyT6M1_c4-PWv2%2BQbhw>