From owner-freebsd-fs@freebsd.org Mon Mar 26 20:39:51 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2791F69E09 for ; Mon, 26 Mar 2018 20:39:51 +0000 (UTC) (envelope-from chuck@tuffli.net) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5109472DFB for ; Mon, 26 Mar 2018 20:39:51 +0000 (UTC) (envelope-from chuck@tuffli.net) Received: by mail-io0-x22c.google.com with SMTP id d7so9508112ioc.11 for ; Mon, 26 Mar 2018 13:39:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuffli-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fzEkmAiBh5DiwlwTjTNXVesVUNA5TT4TvEBeT28AVVY=; b=sN72lSXPUapeD0BgwH4K44cHT/nAmdEECl3SQeGTqnRjqpgutDuErkDUcaOQ0TayYU Ef1uc4qdb7xAG1rYXvDFHPyZDLBD75v43PcLWvyhVChOtD8Wv2YmNt3cZ+xEN1qP4kiD Tp7/0MLs9pZKFhYjYSdBjj4ZFFcSyWyem6r2NlICfP4QOMtxl2W1cXEAwFmnvFSS37lb ufOShMwL8do4JdPnUyfzsvI2NLXAEMljxm/FxyWFIkwyLyqVjtV2lmonjRqC+DfIWM5f XS892AA9pJH1vZmOFqTqa9CwwhntIh74HV4Qs1m7p0dX7/rXI7lbRFn/XR2aQSuyDI6H sOEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fzEkmAiBh5DiwlwTjTNXVesVUNA5TT4TvEBeT28AVVY=; b=oW4TvIHFz47US6gY8edXwLSnPscShpg77qIDu5XpNCYggIAt90mAErBiAYIrZt2q/A bXdi9axDSyyBydAR8R1a6bxLARxVObBTuGQM3or17RjFWMeiuONA3eQtlByI3cwm9Rwm pOM+Oy3XPPWnMebXAZO38mLNpeWblr7U3oa/SJz+4l73qhhPZ6vt7+VXHaMvw875fhtH uGLQtoyUyN58tx3dgsC3JHPXzpj35KGcTYmo/AM6ycxNW2uWaUq35Vwww7i5aDDduC+z uC0arkl0IsW0j98a10i99L3uAyDrCr6g1SIiSobaqU4b35mEC8EgCeK0dAmhuWKcexeG WtyQ== X-Gm-Message-State: AElRT7G2tmC7vAJ3G8tNQGcWFILqU/MjpDL77teGGYO1JKY2mJFvc6RR NwrpAptz/Cq2na/fAF6YAU396pHpqoG1jnFZK9j37Uqc X-Google-Smtp-Source: AIpwx49fhyHVnHCEjzN0/VyxumkLfH/O8GlkwIlU/GaWRVfoaUGHlWeURf0zLSc6u7P+5QDrBMHlTQz5F9mVPFDzhc4= X-Received: by 10.107.183.65 with SMTP id h62mr13274723iof.204.1522096790394; Mon, 26 Mar 2018 13:39:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.6.10 with HTTP; Mon, 26 Mar 2018 13:39:50 -0700 (PDT) In-Reply-To: References: <4754cb2f-76bb-a69b-0cf5-eff4d621eb29@callfortesting.org> From: Chuck Tuffli Date: Mon, 26 Mar 2018 13:39:50 -0700 Message-ID: Subject: Re: smart(8) Call for Testing To: Mark Saad Cc: Michael Dexter , freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2018 20:39:51 -0000 On Mon, Mar 26, 2018 at 1:25 PM, Mark Saad 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