Date: Mon, 2 Oct 2017 22:02:23 +0200 From: Ben RUBSON <ben.rubson@gmail.com> To: Freebsd fs <freebsd-fs@freebsd.org> Subject: Re: ZFS stalled after some mirror disks were lost Message-ID: <DFB581DA-E2C7-4D4C-87FD-19E81C2FA343@gmail.com> In-Reply-To: <7fb4c99b-f3a0-1dda-691c-35f25769ed5c@multiplay.co.uk> References: <4A0E9EB8-57EA-4E76-9D7E-3E344B2037D2@gmail.com> <71d4416a-3454-df36-adae-34c0b70cd84e@multiplay.co.uk> <8A189756-028A-465E-9962-D0181FAEBB79@gmail.com> <953DD379-C03A-4737-BAD8-14BB2DB4AB05@gmail.com> <4f725113-bac3-64bb-9858-690811e73153@multiplay.co.uk> <54AD0000-AF0B-4682-9047-6E6C1B82506C@gmail.com> <7fb4c99b-f3a0-1dda-691c-35f25769ed5c@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 02 Oct 2017, at 21:47, Steven Hartland <killing@multiplay.co.uk> = wrote: >=20 > On 02/10/2017 20:10, Ben RUBSON wrote: >>> On 02 Oct 2017, at 20:41, Steven Hartland <killing@multiplay.co.uk> = wrote: >>>=20 >>> I'm guessing that the devices haven't disconnected cleanly so are = just stalling all requests to them and hence the pool. >> I even tried to ifconfig down the network interface serving the iscsi = targets, it did not help. >>=20 >>> I'm not that familiar with iscsi, does it still show under under = camcontrol or geom? >> # geom disk list >> (...) >> Geom name: da13 >> Providers: >> 1. Name: da13 >> Mediasize: 3999688294912 (3.6T) >> Sectorsize: 512 >> Mode: r1w1e2 >> wither: (null) >>=20 >> Geom name: da15 >> Providers: >> 1. Name: da15 >> Mediasize: 3999688294912 (3.6T) >> Sectorsize: 512 >> Mode: r1w1e2 >> wither: (null) >>=20 >> Geom name: da16 >> Providers: >> 1. Name: da16 >> Mediasize: 3999688294912 (3.6T) >> Sectorsize: 512 >> Mode: r1w1e2 >> wither: (null) >>=20 >> Geom name: da19 >> Providers: >> 1. Name: da19 >> Mediasize: 3999688294912 (3.6T) >> Sectorsize: 512 >> Mode: r1w1e2 >> wither: (null) >>=20 >> # camcontrol devlist >> // does not show the above disks > So these daXX devices represent your iscsi devices? Yes, and only one is still visible under /dev/, with its label under /dev/label/. So I may have one problematic drive among 4. > If so looks like your problem is at the iscsi layer, as its not = disconnected properly, so as far ZFS is concerned its still waiting for = them. Certainly procstat will talk ! I have switched production to another server, so feel free if any other trace is needed. Thank you again, Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DFB581DA-E2C7-4D4C-87FD-19E81C2FA343>