Date: Sat, 6 Dec 2014 19:16:55 -0800 From: Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> To: Drew Tomlinson <drew@mykitchentable.net> Cc: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: Probably Hardware Trouble But What Is It? Message-ID: <CAOgwaMsoVQj8%2B=ic3P8RQ7ze9q-3_Uxp6pKX-hOc8Oa1AU%2BEdQ@mail.gmail.com> In-Reply-To: <5483A639.2050704@mykitchentable.net> References: <5483A639.2050704@mykitchentable.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 6, 2014 at 4:58 PM, Drew Tomlinson <drew@mykitchentable.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOgwaMsoVQj8%2B=ic3P8RQ7ze9q-3_Uxp6pKX-hOc8Oa1AU%2BEdQ>