From owner-freebsd-questions@FreeBSD.ORG Sun Dec 7 03:16:56 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D2706F92 for ; Sun, 7 Dec 2014 03:16:56 +0000 (UTC) Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DCF86DB for ; Sun, 7 Dec 2014 03:16:56 +0000 (UTC) Received: by mail-yk0-f176.google.com with SMTP id q200so1376738ykb.7 for ; Sat, 06 Dec 2014 19:16:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KmzkTnMKC40QqOz+uVbscnSKCO7LQeNt467MOPB4oOw=; b=yxdz5DqD2vKidsd5+EVlLGsNUVEz8LO5HpdqiXriotyIhV2Z4UWfSNNi2wQ6bqpfEc TuQ2Ph/ssHPlMK41INMcsTLt1T1Y8BenuQQZXYXQrLgd2BYe+8F+t58uENxi5b23z+uj wO9bE9YjzfqjJNCgkRzfgGf0oZVAyEEGSaMR1pLbExzF/oAh9j1m0GbgQBC9ncmTEdIt Z2ZnXDFWYUck2SMd7czUTykSCYZmRx/uqEhRfe15NeYSUfOrGLXAtzik2JAHuu/qhPa8 FFLAT9XmOUlzx8KYD/QfsPvC0C30yZisYCNog3bVeuozKfvagGvNBba5ZTkx6bL2P+8o jM0w== MIME-Version: 1.0 X-Received: by 10.236.26.138 with SMTP id c10mr25394800yha.192.1417922215826; Sat, 06 Dec 2014 19:16:55 -0800 (PST) Received: by 10.170.90.131 with HTTP; Sat, 6 Dec 2014 19:16:55 -0800 (PST) In-Reply-To: <5483A639.2050704@mykitchentable.net> References: <5483A639.2050704@mykitchentable.net> Date: Sat, 6 Dec 2014 19:16:55 -0800 Message-ID: Subject: Re: Probably Hardware Trouble But What Is It? From: Mehmet Erol Sanliturk To: Drew Tomlinson Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Questions Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 03:16:56 -0000 On Sat, Dec 6, 2014 at 4:58 PM, Drew Tomlinson wrote: > I'm running FBS 9.1 RELEASE that I built several years ago. It's mostly a > Samba server and has "just worked" so I've never done much more with it. > However recently, I find it "locked up" with thousands of these messages on > the console: > > kernel: kern.maxfiles limit exceeded by uid 0, please see tuning(7) > > I've looked in /var/log/messages and also see lots of messages like these: > > Dec 6 13:55:53 vm kernel: siisch0: ... waiting for slots 18000000 > Dec 6 13:55:53 vm kernel: siisch0: Timeout on slot 28 > Dec 6 13:55:53 vm kernel: siisch0: siis_timeout is 00040000 ss 78000000 > rs 78000000 es 00000000 sts 801b0000 serr 00000000 > Dec 6 13:55:53 vm kernel: siisch0: ... waiting for slots 08000000 > Dec 6 13:55:55 vm kernel: siisch0: Timeout on slot 27 > Dec 6 13:55:55 vm kernel: siisch0: siis_timeout is 00040000 ss 78000000 > rs 78000000 es 00000000 sts 801b0000 serr 00000000 > Dec 6 13:55:55 vm kernel: (ada0:siisch0:0:0:0): FLUSHCACHE48. ACB: ea 00 > 00 00 00 40 00 00 00 00 00 00 > Dec 6 13:55:55 vm kernel: (ada0:siisch0:0:0:0): CAM status: Command > timeout > Dec 6 13:55:55 vm kernel: (ada0:siisch0:0:0:0): Retrying command > Dec 6 13:55:55 vm kernel: (ada0:siisch0:0:0:0): READ_FPDMA_QUEUED. ACB: > 60 01 fe d8 74 40 39 00 00 00 00 00 > Dec 6 13:55:55 vm kernel: (ada0:siisch0:0:0:0): CAM status: Command > timeout > Dec 6 13:55:55 vm kernel: (ada0:siisch0:0:0:0): Retrying command > Dec 6 13:55:55 vm kernel: (ada0:siisch0:0:0:0): READ_FPDMA_QUEUED. ACB: > 60 0a a5 7f 00 40 4c 00 00 00 00 00 > > This machine uses zfs. I have two pools: > > # zpool list > NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT > zback 1.81T 848G 1008G 45% 1.00x ONLINE - > zroot 1.81T 1.16T 666G 64% 1.00x ONLINE - > > Then I tried this and my ssh window is now stuck: > > # zpool status > pool: zback > state: ONLINE > status: One or more devices are faulted in response to IO failures. > action: Make sure the affected devices are connected, then run 'zpool > clear'. > see: http://illumos.org/msg/ZFS-8000-HC > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > zback ONLINE 3 0 0 > ada0 ONLINE 4 0 0 > > I opened another ssh window and tried 'zpool clear zback' as suggested but > it appears stuck too. > > I'm sure I haven't provided all the relevant information so please ask and > I will do so. I'd appreciate any guidance on how to take a proper backup > of ada0 and what I should do next. I think this zback pool is just the one > disk which is a 2TB drive. I'd like to know how to confirm that if > possible since it seems the zpool commands aren't able to complete. > > I appreciate any suggestions or guidance. > > Thanks, > > Drew > > -- > Like card tricks? > > Visit The Alchemist's Warehouse to > learn card magic secrets for free! > > http://alchemistswarehouse.com > > > _______________________________________________ > > Cable connectors may be oxidized and lost signal transmission capability . Please check by replacing connection cables with new and good quality ones . Thank you very much . Mehmet Erol Sanliturk