From owner-freebsd-fs@FreeBSD.ORG Tue Dec 13 14:53:55 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E3FE106566B for ; Tue, 13 Dec 2011 14:53:55 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 8E1FE8FC15 for ; Tue, 13 Dec 2011 14:53:54 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RaTjt-0004gs-DR for freebsd-fs@freebsd.org; Tue, 13 Dec 2011 15:53:53 +0100 Received: from ib-jtotz.ib.ic.ac.uk ([155.198.110.220]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Dec 2011 15:53:53 +0100 Received: from johannes by ib-jtotz.ib.ic.ac.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Dec 2011 15:53:53 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Johannes Totz Date: Tue, 13 Dec 2011 14:53:34 +0000 Lines: 57 Message-ID: References: <4EE764DA.4030206@brockmann-consult.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ib-jtotz.ib.ic.ac.uk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 In-Reply-To: <4EE764DA.4030206@brockmann-consult.de> Subject: Re: zpool failmode=continue X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2011 14:53:55 -0000 On 13/12/2011 14:44, Peter Maloney wrote: > Are you using NFS or ZVOLs? Neither, see below. > My zfs hangs (all IO) if I go into the .zfs/snapshots directory over > NFS. (planning to file a PR after I find a way to reproduce it reliably, > but it depends on specific snapshots). My workaround is to mount > /var/empty on top of the .zfs directory on the nfs client, and give > nobody else access. Another workaround I thought of is to have another > parent directory in the dataset, and share the 2nd level down which > doesn't contain the .zfs directory. My pool is not exported to any clients. My situation is actually the other way around, should have been more clear: the block device on which I created the pool is a on the network. It's kind of a crazy setup: - sshfs to another (Linux) machine - create big image file - create pool from file vdev mounted via sshfs Eventually the network drops out, zpool shows read and write errors, fine so far. But all new io just hangs instead of failing with an error. > And a single dataset hangs if I rename a ZVOL snapshot (likely not the > only way to cause this): http://www.freebsd.org/cgi/query-pr.cgi?pr=161968 > > I am using: > FreeBSD bcnas1.bc.local 8.2-STABLE FreeBSD 8.2-STABLE #0: Thu Sep 29 > 15:06:03 CEST 2011 > root@bcnas1.bc.local:/usr/obj/usr/src/sys/GENERIC amd64 > > > > On 12/13/2011 03:34 PM, Johannes Totz wrote: >> Hi! >> >> Is failmode=continue for zpool working correctly? >> >> I have a test pool sitting on the network (which drops out every few >> hours) but all io eventually just hangs instead of failing. >> >> To get the pool back up running (and get rid of all the hung >> processes) I always need to reboot the machine. This is on: >> FreeBSD XXX 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #1 r227793M: Mon Dec >> 5 22:57:54 GMT 2011 root@XXX:/usr/obj/usr/src/sys/GENERIC amd64 >> >> >> >> Johannes >> >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > >