From owner-freebsd-fs@FreeBSD.ORG Sun Apr 3 08:38:52 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D0701065672; Sun, 3 Apr 2011 08:38:52 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 131EA8FC12; Sun, 3 Apr 2011 08:38:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p338cp3V050647; Sun, 3 Apr 2011 08:38:51 GMT (envelope-from jh@freefall.freebsd.org) Received: (from jh@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p338cpbi050643; Sun, 3 Apr 2011 08:38:51 GMT (envelope-from jh) Date: Sun, 3 Apr 2011 08:38:51 GMT Message-Id: <201104030838.p338cpbi050643@freefall.freebsd.org> To: giffunip@tutopia.com, jh@FreeBSD.org, freebsd-fs@FreeBSD.org From: jh@FreeBSD.org Cc: Subject: Re: kern/152079: [msdosfs] [patch] Small cleanups from the other NetBSD/OpenBSD 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: Sun, 03 Apr 2011 08:38:52 -0000 Synopsis: [msdosfs] [patch] Small cleanups from the other NetBSD/OpenBSD State-Changed-From-To: open->closed State-Changed-By: jh State-Changed-When: Sun Apr 3 08:38:51 UTC 2011 State-Changed-Why: Closed at submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=152079 From owner-freebsd-fs@FreeBSD.ORG Sun Apr 3 08:39:25 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CB281065676; Sun, 3 Apr 2011 08:39:25 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2340E8FC1E; Sun, 3 Apr 2011 08:39:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p338dPHg050785; Sun, 3 Apr 2011 08:39:25 GMT (envelope-from jh@freefall.freebsd.org) Received: (from jh@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p338dPGH050781; Sun, 3 Apr 2011 08:39:25 GMT (envelope-from jh) Date: Sun, 3 Apr 2011 08:39:25 GMT Message-Id: <201104030839.p338dPGH050781@freefall.freebsd.org> To: giffunip@tutopia.com, jh@FreeBSD.org, freebsd-fs@FreeBSD.org From: jh@FreeBSD.org Cc: Subject: Re: kern/142401: [ntfs] [patch] Minor updates to NTFS from NetBSD 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: Sun, 03 Apr 2011 08:39:25 -0000 Synopsis: [ntfs] [patch] Minor updates to NTFS from NetBSD State-Changed-From-To: open->closed State-Changed-By: jh State-Changed-When: Sun Apr 3 08:39:24 UTC 2011 State-Changed-Why: Closed at submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=142401 From owner-freebsd-fs@FreeBSD.ORG Sun Apr 3 09:05:17 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 1346F106567D for ; Sun, 3 Apr 2011 09:05:17 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 92B6D8FC15 for ; Sun, 3 Apr 2011 09:05:16 +0000 (UTC) Received: by wwc33 with SMTP id 33so5273379wwc.31 for ; Sun, 03 Apr 2011 02:05:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1sa9lmIGjGf1W4cDw624cQmJX1PMzdbCiLyN443+6hQ=; b=G4v5R7y3UetGL2V815nDj1Iw9WyzcOYZdUkTGZ1/dyNZtOpiZlza9n4PqicoIGJEqi 8PYmHOrmyEdCh26T3hz9vcg6SeeqzrJqp43nMnnttelfXgwUZdy7LG73AjtXXEJRIhBD 0C9OsrFAwHx1Xrd8ZmMJpmIeSubN7tYtDO8ks= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IFUaNm4rlzCJO3gddjPt/qQK0QW61kHS/pyNxJyozDJajL/I2h6xWk2fnl4InLoSRf D76jLDR9/Ctn3zmwO7cW6jDWNNiZUXgbQvpVtgfSpLbkenR2NgzcvP40IORtZgtvstFc wWrWKv50V8W8R4pyQfU5tRDkyCCJy8u/uovPg= MIME-Version: 1.0 Received: by 10.216.142.85 with SMTP id h63mr683272wej.84.1301821515344; Sun, 03 Apr 2011 02:05:15 -0700 (PDT) Received: by 10.216.187.16 with HTTP; Sun, 3 Apr 2011 02:05:15 -0700 (PDT) In-Reply-To: References: <20110401013603.GA31034@icarus.home.lan> <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> Date: Sun, 3 Apr 2011 10:05:15 +0100 Message-ID: From: krad To: Daryl Richards Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS failed after hard power off 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: Sun, 03 Apr 2011 09:05:17 -0000 On 2 April 2011 23:55, Daryl Richards wrote: > On 2011-04-02, at 6:50 PM, Piotr Paczynski wrote: > > > Emergency over. I didn't managed to make Solaris see my pool. Instead, > > I've installed FreeBSD-8.2 on a separate disk, fetched latest sources > > of FreeBSD9, rebuilt world, and then used "zpool import -fF zroot" to > > recover the pool. Worked like charm. Thank you for the help. > > _______________________________________________ > > 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" > > Good that you got it! > > For list reference, this is because Solaris doesn't understand FreeBSD's > slice table, so can't see the ZFS slice. > > _______________________________________________ > 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" > assuming you didnt use gpt From owner-freebsd-fs@FreeBSD.ORG Sun Apr 3 22:13:29 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 2D97D1065673; Sun, 3 Apr 2011 22:13:29 +0000 (UTC) (envelope-from christopher-ml@telting.org) Received: from mail.telting.org (mail.telting.org [204.109.56.249]) by mx1.freebsd.org (Postfix) with ESMTP id C94E08FC12; Sun, 3 Apr 2011 22:13:28 +0000 (UTC) Received: from apollo.local (cpe-76-168-204-255.socal.res.rr.com [76.168.204.255]) by mail.telting.org (Postfix) with ESMTP id C47542A702; Sun, 3 Apr 2011 21:55:09 +0000 (UTC) Message-ID: <4D98ECBE.2090306@telting.org> Date: Sun, 03 Apr 2011 14:55:10 -0700 From: Chris Telting User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.15) Gecko/20110305 Thunderbird/3.1.9 MIME-Version: 1.0 To: Rick Macklem References: <996838892.118259.1298065089198.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <996838892.118259.1298065089198.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Lawrence Stewart Subject: Re: Mounting NFSv4 as root fs 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: Sun, 03 Apr 2011 22:13:29 -0000 On 02/18/2011 13:38, Rick Macklem wrote: > Yep. I didn't see an easy way to set up the diskless root so that it would > work for both clients concurrently, so I was planning on switching it if/when > "newnfs" becomes the default client. (You can switch fairly easily. Just > crib the code across, as it sounds like you have and then make sure the > xxx_mountroot() in "newnfs" gets called instead of nfs_mountroot() in the > other one. > > However, that will just get a "newnfs" NFSv3 root mount to work. > Sounds like it should be a kernel option as to which NFS implementation is default on a pxeboot. > I have never intended to try and make an NFSv4 root mount work. > (Someone said NFSv4 is NFS in name only:-) > That's a shame. It seems logical to me that that's a critical feature to it's acceptance. I'm still new to nfsv4 so please forgive what I don't understand. The kernel boots the a normal disk filesystem only knowing uid/gid numbers. It only understands what is root accessible or suid and what isn't. Once the filesystem is mounted it can consult whatever database is used for further information. Why can't we make nfsv4 tolerant of running without nfsuserd information at least initially? Have a special filesystem option to run it in crippled mode. And once we have networking and nfsuserd loaded we can remount the filesystem..? Chris From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 09:36:45 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 64EEE106564A for ; Mon, 4 Apr 2011 09:36:45 +0000 (UTC) (envelope-from ppaczyn@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 225728FC0A for ; Mon, 4 Apr 2011 09:36:44 +0000 (UTC) Received: by iyj12 with SMTP id 12so7179897iyj.13 for ; Mon, 04 Apr 2011 02:36:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Jbrurc7kJEuewqbhj7ZjwMH3chhZALBf+jR8+dgvpaY=; b=wpMdGoBGgnGDBbkc8pNgxuwXBIYv9vUgnEhofxu57Cbw/VIqVcOKoz76X8LGsGtNBt A+nOcmm6PD4WQkGLDMV7aCkVcHo4JxYpi2e6c1EyDzyLDP1FLgunUCuz8F71p4CEwyOr 9cJO7pP++iBkl31aG8QxaqKptR2Waza3nxsLA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=AdDzG0xh1sd3A4SUR1Gxk1N+TTzpWebnOYYspT2f6cjR6/duJ6mxWP1S77jkJbLsH4 1XGVQ1rJm6WgLtNrkCH4n8MeEUDeHzUc8bBYSpM5l9fRaVNylfGBx8tPlO0TUXBVig9Z FeEI5grnI2GBqzl7z6ATgQfcvstBYTiBRPOF0= MIME-Version: 1.0 Received: by 10.42.161.197 with SMTP id u5mr5200885icx.466.1301909804551; Mon, 04 Apr 2011 02:36:44 -0700 (PDT) Received: by 10.42.172.201 with HTTP; Mon, 4 Apr 2011 02:36:44 -0700 (PDT) In-Reply-To: References: <20110401013603.GA31034@icarus.home.lan> <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> Date: Mon, 4 Apr 2011 11:36:44 +0200 Message-ID: From: Piotr Paczynski To: krad Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, Daryl Richards Subject: Re: ZFS failed after hard power off 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: Mon, 04 Apr 2011 09:36:45 -0000 >> For list reference, this is because Solaris doesn't understand FreeBSD's >> slice table, so can't see the ZFS slice. > > assuming you didnt use gpt The thing is I did use gpart to partition the disk, and the partition was visible in Solaris as /dev/dsk/c4t0d0s2. It was also properly seen and analyzed by zdb, which showed correct pool name. So for the reference, I still don't know why it wasn't seen by import :) From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 10:13:26 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 440C6106566B for ; Mon, 4 Apr 2011 10:13:26 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id C1AD08FC12 for ; Mon, 4 Apr 2011 10:13:25 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id DFACEE8136; Mon, 4 Apr 2011 11:13:24 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=subject :from:to:cc:in-reply-to:references:content-type:date:message-id :mime-version:content-transfer-encoding; s=mail; bh=1iO6mHZE6XxS LHxv/4UL8g2fog8=; b=k7YuapO/LO/sY6TLHbepYJY2OH6s/uSJHP3biMiateG9 WWxhBp1P8dBE+MtVp7tAtFk2MVkVQekvloJ2Bq4DstTwHhd2OCHHV05B5xdNHF9a xE+khU8JJdfUly8Unz6aGl+LVJ6ARncpU11gaqaWUa2DU1qVu7hiZA1F7aJvCEw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=subject:from :to:cc:in-reply-to:references:content-type:date:message-id :mime-version:content-transfer-encoding; q=dns; s=mail; b=FXg4EL ddvSQdx1DlZIh9t7EssM7jjV7BZ6GWZ7Yit/Jrio0OqZc1z9qtBUhD2kOfJPGnBy ke41DWJkLXo+YAYa4oSoR0wjf6lQh5KQ8s4s/kGhRQ4C+mE4R4LJKrynGNZNvGjJ Zr6/oolh0668ZNS4DlhqzmFxeVrWavZOQZ0YQ= Received: from [192.168.1.69] (188-222-18-231.zone13.bethere.co.uk [188.222.18.231]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id A44B4E77AB; Mon, 4 Apr 2011 11:13:24 +0100 (BST) From: Bruce Cran To: Piotr Paczynski In-Reply-To: References: <20110401013603.GA31034@icarus.home.lan> <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Apr 2011 11:13:13 +0100 Message-ID: <1301911993.17884.4.camel@core.nessbank> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Daryl Richards Subject: Re: ZFS failed after hard power off 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: Mon, 04 Apr 2011 10:13:26 -0000 On Mon, 2011-04-04 at 11:36 +0200, Piotr Paczynski wrote: > > assuming you didnt use gpt > > The thing is I did use gpart to partition the disk, and the partition > was visible in Solaris as /dev/dsk/c4t0d0s2. gpt, not gpart. gpt - Guid Partition Table - is the table format, gpart is the tool. gpart can also create mbr partition tables. -- Bruce Cran From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 10:48:36 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 78AE6106564A for ; Mon, 4 Apr 2011 10:48:36 +0000 (UTC) (envelope-from ppaczyn@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 354B58FC1D for ; Mon, 4 Apr 2011 10:48:35 +0000 (UTC) Received: by iyj12 with SMTP id 12so7242075iyj.13 for ; Mon, 04 Apr 2011 03:48:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=6yINnibFOX7sajWom2ioSivZYmd4eugbWmttkOYGigo=; b=quBdp9xR1EAA9eUI80aEIbNC7H737tuL2w4JBIEjuJu4W+1SErb2dZeJbIOmkMCRAq a5lV8eOr/bAIsu+vWCpsSB2xZiHXALhr2YdN8JdYqQk+lbDz8yPO193JxNXWBcTpEU31 k5h/48m7WX7Dxur8Lav4HPIXFx7qygFaYXi0g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fL48CZsbiWV3lJl0SKdRGwvf/e9eKxkpF3ec/q5mK0roQhnAlNErRHaaMER5TJ893B bM1eobRjejzxc6GKsuYYfmBM9ZiHTa7iesLPVY0mDb1YeMJBFgciIuy37ZwZMy3T1Nxc hu8IOsLlONmHOOqBs8AHliv9tie0VWTke9uGU= MIME-Version: 1.0 Received: by 10.43.63.212 with SMTP id xf20mr3749204icb.265.1301914115663; Mon, 04 Apr 2011 03:48:35 -0700 (PDT) Received: by 10.42.172.201 with HTTP; Mon, 4 Apr 2011 03:48:35 -0700 (PDT) In-Reply-To: <1301911993.17884.4.camel@core.nessbank> References: <20110401013603.GA31034@icarus.home.lan> <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> <1301911993.17884.4.camel@core.nessbank> Date: Mon, 4 Apr 2011 12:48:35 +0200 Message-ID: From: Piotr Paczynski To: Bruce Cran Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, Daryl Richards Subject: Re: ZFS failed after hard power off 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: Mon, 04 Apr 2011 10:48:36 -0000 > gpt, not gpart. gpt - Guid Partition Table - is the table format, gpart > is the tool. gpart can also create mbr partition tables. Let me paste the partition table of my boot disk: $ gpart show da0 => 34 3906207677 da0 GPT (1.8T) 34 128 1 freebsd-boot (64K) 162 8388608 2 freebsd-swap (4.0G) 8388770 3897818941 3 freebsd-zfs (1.8T) It looks like an ordinary GPT, which should work ok on Solaris, no? Disks in my second pool do not use any partition table at all (raw disk device is added directly to zpool) and this was imported ok in Solaris. -- Piotr Paczynski From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 11:06:59 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 AFD26106566B for ; Mon, 4 Apr 2011 11:06:59 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 80A218FC0C for ; Mon, 4 Apr 2011 11:06:59 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p34B6xpG028601 for ; Mon, 4 Apr 2011 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p34B6wgf028599 for freebsd-fs@FreeBSD.org; Mon, 4 Apr 2011 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Apr 2011 11:06:58 GMT Message-Id: <201104041106.p34B6wgf028599@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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: Mon, 04 Apr 2011 11:06:59 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs o kern/155484 fs [ufs] GPT + UFS boot don't work well together o kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 o kern/154447 fs [zfs] [panic] Occasional panics - solaris assert somew f kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153847 fs [nfs] [panic] Kernel panic from incorrect m_free in nf o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small p kern/152488 fs [tmpfs] [patch] mtime of file updated when only inode o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o kern/151845 fs [smbfs] [patch] smbfs should be upgraded to support Un o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/150207 fs zpool(1): zpool import -d /dev tries to open weird dev o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa f kern/149022 fs [hang] File system operations hangs with suspfs state o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o bin/148296 fs [zfs] [loader] [patch] Very slow probe in /usr/src/sys o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [ffs] [snapshot] System crashes when manipulat o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 218 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 11:48:54 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E42FD106566C for ; Mon, 4 Apr 2011 11:48:54 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [193.34.186.230]) by mx1.freebsd.org (Postfix) with ESMTP id 807948FC08 for ; Mon, 4 Apr 2011 11:48:54 +0000 (UTC) Received: from higson.cam.lispworks.com (higson [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.3/8.14.3) with ESMTP id p34BckNM091258; Mon, 4 Apr 2011 12:38:46 +0100 (BST) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id p34BckZq029805; Mon, 4 Apr 2011 12:38:46 +0100 Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id p34BckHS029801; Mon, 4 Apr 2011 12:38:46 +0100 Date: Mon, 4 Apr 2011 12:38:46 +0100 Message-Id: <201104041138.p34BckHS029801@higson.cam.lispworks.com> From: Martin Simmons To: fs@freebsd.org In-reply-to: <4D973400.9060404@networktest.com> (message from David Newman on Sat, 02 Apr 2011 07:34:40 -0700) References: <4C51ECAA.2070707@networktest.com> <4C51FE41.8030906@FreeBSD.org> <4D941BFF.6050807@networktest.com> <4D973400.9060404@networktest.com> Cc: Subject: Re: fixing a busted ZFS upgrade 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: Mon, 04 Apr 2011 11:48:55 -0000 >>>>> On Sat, 02 Apr 2011 07:34:40 -0700, David Newman said: > > Thanks for this script. Problem is, I can't get to the point where I can > run it. The script is used to perform the upgrade, so it would be too late for you anyway (it would probably make things worse). > I've tried booting from 8.1 and 8.2 mfsBSD ISOs but both hang at > loader.conf. Have you tried the regular FreeBSD installation ISO? That doesn't know about ZFS by default, but you can enter Fixit mode with "Use the live filesystem CDROM/DVD" and load the modules using kldload /dist/boot/kernel/opensolaris.ko kldload /dist/boot/kernel/zfs.ko __Martin From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 12:54:52 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 F237D106566C for ; Mon, 4 Apr 2011 12:54:52 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: from a.smtpout.corp.3g-net.net (a.smtpout.corp.3g-net.net [202.127.97.231]) by mx1.freebsd.org (Postfix) with ESMTP id A41FA8FC0C for ; Mon, 4 Apr 2011 12:54:52 +0000 (UTC) Received: from smtp.corp.3g-net.net (smtp.corp.3g-net.net [202.127.97.230]) by a.smtpout.corp.3g-net.net (Postfix) with ESMTP id C4AA260DFB for ; Mon, 4 Apr 2011 19:39:09 +0700 (WIT) Received: from smtp.triplegate.net.id (smtp.triplegate.net.id [202.127.97.100]) by smtp.corp.3g-net.net (Postfix) with ESMTP id 7DDC6214DB for ; Mon, 4 Apr 2011 19:39:39 +0700 (WIT) Received: from DBLJSW1S (Hotel-SAHID-Ckr.triplegate.net.id [202.127.110.59]) by lb1.3gate.net (Postfix) with SMTP id AB0D021103C for ; Mon, 4 Apr 2011 19:15:53 +0700 (WIT) Message-ID: <009701cbf2bc$f3e9cb70$140124c0@DBLJSW1S> From: "binto" To: Date: Mon, 4 Apr 2011 19:39:25 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: what is g_vfs_done() and error = 6?? how to fix it?? 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: Mon, 04 Apr 2011 12:54:53 -0000 I got error message & my server suddenly drop : g_vfs_done() error =3D 6 g_vfs_done(): ad10s2a[READ(offset=3D1348599808, length=3D16384)]error = =3D 6 anyone can help me please?? Thank you=20 binto From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 12:55:53 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 0590E1065674 for ; Mon, 4 Apr 2011 12:55:53 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: from a.smtpout.corp.3g-net.net (a.smtpout.corp.3g-net.net [202.127.97.231]) by mx1.freebsd.org (Postfix) with ESMTP id A9F1B8FC0A for ; Mon, 4 Apr 2011 12:55:52 +0000 (UTC) Received: from smtp.corp.3g-net.net (smtp.corp.3g-net.net [202.127.97.230]) by a.smtpout.corp.3g-net.net (Postfix) with ESMTP id BFD5F60DFB for ; Mon, 4 Apr 2011 19:55:51 +0700 (WIT) Received: from smtp.triplegate.net.id (smtp.triplegate.net.id [202.127.97.100]) by smtp.corp.3g-net.net (Postfix) with ESMTP id 79EEA214DB for ; Mon, 4 Apr 2011 19:56:21 +0700 (WIT) Received: from DBLJSW1S (Hotel-SAHID-Ckr.triplegate.net.id [202.127.110.59]) by lb1.3gate.net (Postfix) with SMTP id 1F76F21109A for ; Mon, 4 Apr 2011 19:32:34 +0700 (WIT) Message-ID: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S> From: "binto" To: Date: Mon, 4 Apr 2011 19:56:11 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? 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: Mon, 04 Apr 2011 12:55:53 -0000 Also i got before it's reboot suddenly: panic: initiate_write_inodeblock_ufs2: already started Thanks Binto ----- Original Message -----=20 From: binto=20 To: freebsd-fs@freebsd.org=20 Sent: Monday, April 04, 2011 7:39 PM Subject: what is g_vfs_done() and error =3D 6?? how to fix it?? I got error message & my server suddenly drop : g_vfs_done() error =3D 6 g_vfs_done(): ad10s2a[READ(offset=3D1348599808, length=3D16384)]error = =3D 6 anyone can help me please?? Thank you=20 binto From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 15:27:47 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 46A5B1065746 for ; Mon, 4 Apr 2011 15:27:47 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 02C528FC0C for ; Mon, 4 Apr 2011 15:27:46 +0000 (UTC) Received: by vws18 with SMTP id 18so5147338vws.13 for ; Mon, 04 Apr 2011 08:27:46 -0700 (PDT) Received: by 10.52.169.39 with SMTP id ab7mr9745315vdc.230.1301929557643; Mon, 04 Apr 2011 08:05:57 -0700 (PDT) Received: from wawanesa.iciti.ca (CPE0080c8f208a5-CM001371173cf8.cpe.net.cable.rogers.com [99.246.61.82]) by mx.google.com with ESMTPS id b6sm1122525vci.0.2011.04.04.08.05.55 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2011 08:05:56 -0700 (PDT) Message-ID: <4D99DE50.1030607@bellanet.org> Date: Mon, 04 Apr 2011 11:05:52 -0400 From: Graham Todd User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110118 Thunderbird/3.1.7 MIME-Version: 1.0 To: binto , freebsd-fs@freebsd.org References: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S> In-Reply-To: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? 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: Mon, 04 Apr 2011 15:27:47 -0000 On 04/04/2011 07:56, binto wrote: > Also i got before it's reboot suddenly: > panic: initiate_write_inodeblock_ufs2: already started I think you're getting a panic from ufs2 and softdep somewhere because for whatever reason geom is saying the drive has disappeared (bad cabling, bad hardware, bad sector, electrical glitch, etc.)? Someone more knowledgeable than me can explain the code path and error 6. If it is hardware and the drive that has your / or /usr filesystems then panic'ing is "correct" behaviour I believe. If it is a USB drive being pulled without umounting then I think FreeBSD is supposed to handle that incorrect operation more gracefully since 7.* Was there data loss? Did the server reboot properly? Have you run any hardware tests? cheers > Thanks > Binto > ----- Original Message ----- > From: binto > To: freebsd-fs@freebsd.org > Sent: Monday, April 04, 2011 7:39 PM > Subject: what is g_vfs_done() and error = 6?? how to fix it?? > > > I got error message& my server suddenly drop : > > g_vfs_done() error = 6 > > g_vfs_done(): ad10s2a[READ(offset=1348599808, length=16384)]error = 6 anyone can help me please?? > > Thank you > binto From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 15:32:38 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 3C97B1065676 for ; Mon, 4 Apr 2011 15:32:38 +0000 (UTC) (envelope-from pontomedon@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id C35E98FC1F for ; Mon, 4 Apr 2011 15:32:37 +0000 (UTC) Received: by fxm11 with SMTP id 11so5256443fxm.13 for ; Mon, 04 Apr 2011 08:32:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=TSxo8EGIA0MQq15EDw/uIKI75OaLnb8jClyRklNFScw=; b=AW54ZWmA1Y0CX1QCwRxcghotdXLCtY7ZzyQvo44x3us5Jg9YngHoMAwOCDSSaJYvWZ FJPJw+cyaW+KK67Vzd+o++qR4xnTjuR7slkixgsMgVo78TrAUt8ij4AQ5XSewAOKsLOP H+afAEjO3JHkYYfytmzR6L6AEwOa14K+WFLyM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=ufVWek7nnV/GtHAla78Cd3jrqMlsJwtFhTe79iCQbxqMuPSEmnO12mbMxS3ArnwwCk mtZv9gAhLGexegJztXfLZ9P0QF8+flt41B5WaGckpGdnVLR1brrTfGOJl7cElEhu1293 t33DpYLweT/pQMjdYHvEUMaicFQqOWOJLOfpw= Received: by 10.223.25.197 with SMTP id a5mr2043830fac.29.1301929394701; Mon, 04 Apr 2011 08:03:14 -0700 (PDT) Received: from [192.168.1.3] (chello062178135187.2.14.univie.teleweb.at [62.178.135.187]) by mx.google.com with ESMTPS id j12sm1768814fax.9.2011.04.04.08.03.13 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2011 08:03:14 -0700 (PDT) Message-ID: <4D99DDB0.9090307@googlemail.com> Date: Mon, 04 Apr 2011 17:03:12 +0200 From: "=?ISO-8859-15?Q?Lukas_R=F6ssler?=" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: zfs porting roadmap? 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: Mon, 04 Apr 2011 15:32:38 -0000 I browsed through the archives of the past few months and saw that zfs is already ported up to v28 atm (thanks a lot at pjd - you do awesome work!). Don't get me wrong here, i don't want to sound demanding in any way, i'm just interested - are there plans to port it up to the current version (31, i believe)? The killer feature for me is encryption, which was added in v30... Thanks again for all your efforts, and thank you in advance for answering a noobs question :) Lukas From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 16:05:27 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 22BCE1065780 for ; Mon, 4 Apr 2011 16:05:27 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: from smtp7.3g-net.net (smtp7.3g-net.net [202.127.97.245]) by mx1.freebsd.org (Postfix) with ESMTP id 9DD618FC17 for ; Mon, 4 Apr 2011 16:05:26 +0000 (UTC) Received: from lb1.3gate.net (smtp.triplegate.net.id [202.127.97.100]) by smtp2.3g-net.net (Postfix) with ESMTP id C8A98848057; Mon, 4 Apr 2011 22:45:56 +0700 (WIT) Received: from DBLJSW1S (Hotel-SAHID-Ckr.triplegate.net.id [202.127.110.59]) by lb1.3gate.net (Postfix) with SMTP id 9030621103C; Mon, 4 Apr 2011 22:22:32 +0700 (WIT) Message-ID: <00f201cbf2d7$29816f30$140124c0@DBLJSW1S> From: "binto" To: "Graham Todd" , References: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S> <4D99DE50.1030607@bellanet.org> Date: Mon, 4 Apr 2011 22:47:02 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350 Cc: Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? 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: Mon, 04 Apr 2011 16:05:27 -0000 if cabling, i wonder why in single mode there's no problem especially about filesystem . But in normal login when i use root user, then i got so many warn about that error 6. reboot after that. ??? [ can u explain?] now i'm still troubleshoot in configuration. i haven't try run hardware test yet. such as to switch HDD with another board or something. so far i haven't found missing data, except files that i remove..:D thanks ----- Original Message ----- From: "Graham Todd" To: "binto" ; Sent: Monday, April 04, 2011 11:05 PM Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > On 04/04/2011 07:56, binto wrote: >> Also i got before it's reboot suddenly: >> panic: initiate_write_inodeblock_ufs2: already started > > I think you're getting a panic from ufs2 and softdep somewhere because for > whatever reason geom is saying the drive has disappeared (bad cabling, bad > hardware, bad sector, electrical glitch, etc.)? Someone more knowledgeable > than me can explain the code path and error 6. > > If it is hardware and the drive that has your / or /usr filesystems then > panic'ing is "correct" behaviour I believe. If it is a USB drive being > pulled without umounting then I think FreeBSD is supposed to handle that > incorrect operation more gracefully since 7.* > > Was there data loss? Did the server reboot properly? Have you run any > hardware tests? > > cheers > >> Thanks >> Binto >> ----- Original Message ----- >> From: binto >> To: freebsd-fs@freebsd.org >> Sent: Monday, April 04, 2011 7:39 PM >> Subject: what is g_vfs_done() and error = 6?? how to fix it?? >> >> >> I got error message& my server suddenly drop : >> >> g_vfs_done() error = 6 >> >> g_vfs_done(): ad10s2a[READ(offset=1348599808, length=16384)]error = 6 >> anyone can help me please?? >> >> Thank you >> binto > > > From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 16:10:35 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 45FD6106566C for ; Mon, 4 Apr 2011 16:10:35 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: from smtp22.3g-net.net (smtp22.3g-net.net [202.127.97.61]) by mx1.freebsd.org (Postfix) with ESMTP id BFED68FC08 for ; Mon, 4 Apr 2011 16:10:34 +0000 (UTC) Received: from lb1.3gate.net (smtp.triplegate.net.id [202.127.97.100]) by smtp2.3g-net.net (Postfix) with ESMTP id EB242848057; Mon, 4 Apr 2011 23:10:28 +0700 (WIT) Received: from DBLJSW1S (Hotel-SAHID-Ckr.triplegate.net.id [202.127.110.59]) by lb1.3gate.net (Postfix) with SMTP id BCA2C21103C; Mon, 4 Apr 2011 22:47:00 +0700 (WIT) Message-ID: <011901cbf2da$672f0c40$140124c0@DBLJSW1S> From: "binto" To: "Graham Todd" , References: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S><4D99DE50.1030607@bellanet.org> <00f201cbf2d7$29816f30$140124c0@DBLJSW1S> Date: Mon, 4 Apr 2011 23:10:14 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350 Cc: Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? 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: Mon, 04 Apr 2011 16:10:35 -0000 suspicious one is..bad sector.. ----- Original Message ----- From: "binto" To: "Graham Todd" ; Sent: Monday, April 04, 2011 10:47 PM Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > if cabling, i wonder why in single mode there's no problem especially > about filesystem . > But in normal login when i use root user, then i got so many warn about > that error 6. > reboot after that. > ??? [ can u explain?] > > now i'm still troubleshoot in configuration. > i haven't try run hardware test yet. such as to switch HDD with another > board or something. > > so far i haven't found missing data, except files that i remove..:D > > thanks > > ----- Original Message ----- > From: "Graham Todd" > To: "binto" ; > Sent: Monday, April 04, 2011 11:05 PM > Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > > >> On 04/04/2011 07:56, binto wrote: >>> Also i got before it's reboot suddenly: >>> panic: initiate_write_inodeblock_ufs2: already started >> >> I think you're getting a panic from ufs2 and softdep somewhere because >> for whatever reason geom is saying the drive has disappeared (bad >> cabling, bad hardware, bad sector, electrical glitch, etc.)? Someone more >> knowledgeable than me can explain the code path and error 6. >> >> If it is hardware and the drive that has your / or /usr filesystems then >> panic'ing is "correct" behaviour I believe. If it is a USB drive being >> pulled without umounting then I think FreeBSD is supposed to handle that >> incorrect operation more gracefully since 7.* >> >> Was there data loss? Did the server reboot properly? Have you run any >> hardware tests? >> >> cheers >> >>> Thanks >>> Binto >>> ----- Original Message ----- >>> From: binto >>> To: freebsd-fs@freebsd.org >>> Sent: Monday, April 04, 2011 7:39 PM >>> Subject: what is g_vfs_done() and error = 6?? how to fix it?? >>> >>> >>> I got error message& my server suddenly drop : >>> >>> g_vfs_done() error = 6 >>> >>> g_vfs_done(): ad10s2a[READ(offset=1348599808, length=16384)]error = 6 >>> anyone can help me please?? >>> >>> Thank you >>> binto >> >> >> > > _______________________________________________ > 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" > From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 16:55:27 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 E70F9106564A for ; Mon, 4 Apr 2011 16:55:26 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 933278FC12 for ; Mon, 4 Apr 2011 16:55:26 +0000 (UTC) Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta05.westchester.pa.mail.comcast.net with comcast id TTjf1g0080QuhwU55UvSpn; Mon, 04 Apr 2011 16:55:26 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta02.westchester.pa.mail.comcast.net with comcast id TUvN1g01X1t3BNj3NUvPk8; Mon, 04 Apr 2011 16:55:26 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 5959E9B429; Mon, 4 Apr 2011 09:55:21 -0700 (PDT) Date: Mon, 4 Apr 2011 09:55:21 -0700 From: Jeremy Chadwick To: binto Message-ID: <20110404165521.GA59495@icarus.home.lan> References: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S> <4D99DE50.1030607@bellanet.org> <00f201cbf2d7$29816f30$140124c0@DBLJSW1S> <011901cbf2da$672f0c40$140124c0@DBLJSW1S> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <011901cbf2da$672f0c40$140124c0@DBLJSW1S> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? 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: Mon, 04 Apr 2011 16:55:27 -0000 On Mon, Apr 04, 2011 at 11:10:14PM +0800, binto wrote: > suspicious one is..bad sector.. > > ----- Original Message ----- From: "binto" > To: "Graham Todd" ; > Sent: Monday, April 04, 2011 10:47 PM > Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > > > >if cabling, i wonder why in single mode there's no problem > >especially about filesystem . > >But in normal login when i use root user, then i got so many warn > >about that error 6. > >reboot after that. > >??? [ can u explain?] > > > >now i'm still troubleshoot in configuration. > >i haven't try run hardware test yet. such as to switch HDD with > >another board or something. > > > >so far i haven't found missing data, except files that i remove..:D > > > >thanks > > > >----- Original Message ----- From: "Graham Todd" > > > >To: "binto" ; > >Sent: Monday, April 04, 2011 11:05 PM > >Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > > > > > >>On 04/04/2011 07:56, binto wrote: > >>>Also i got before it's reboot suddenly: > >>>panic: initiate_write_inodeblock_ufs2: already started > >> > >>I think you're getting a panic from ufs2 and softdep somewhere > >>because for whatever reason geom is saying the drive has > >>disappeared (bad cabling, bad hardware, bad sector, electrical > >>glitch, etc.)? Someone more knowledgeable than me can explain > >>the code path and error 6. > >> > >>If it is hardware and the drive that has your / or /usr > >>filesystems then panic'ing is "correct" behaviour I believe. If > >>it is a USB drive being pulled without umounting then I think > >>FreeBSD is supposed to handle that incorrect operation more > >>gracefully since 7.* > >> > >>Was there data loss? Did the server reboot properly? Have you > >>run any hardware tests? > >> > >>cheers > >> > >>>Thanks > >>>Binto > >>> ----- Original Message ----- > >>> From: binto > >>> To: freebsd-fs@freebsd.org > >>> Sent: Monday, April 04, 2011 7:39 PM > >>> Subject: what is g_vfs_done() and error = 6?? how to fix it?? > >>> > >>> > >>> I got error message& my server suddenly drop : > >>> > >>> g_vfs_done() error = 6 > >>> > >>> g_vfs_done(): ad10s2a[READ(offset=1348599808, > >>>length=16384)]error = 6 anyone can help me please?? > >>> > >>> Thank you > >>> binto Install /usr/ports/sysutils/smartmontools and provide output from "smartctl -a /dev/ad10" (assuming the questionable hard disk is still installed there); I can help decode the output. You might also want to run "fsck -f /dev/ad10". There are known cases where backgrounded fsck can't fix some errors, but I'm not sure if the kernel would return errno=6 (Device not configured) to userland in this situation. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 16:58:10 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 542C3106564A for ; Mon, 4 Apr 2011 16:58:10 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 024C18FC14 for ; Mon, 4 Apr 2011 16:58:09 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 8EFFE45CA0; Mon, 4 Apr 2011 18:58:07 +0200 (CEST) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 5262845B36; Mon, 4 Apr 2011 18:58:02 +0200 (CEST) Date: Mon, 4 Apr 2011 18:57:59 +0200 From: Pawel Jakub Dawidek To: Lukas =?iso-8859-1?Q?R=F6ssler?= Message-ID: <20110404165759.GA2007@garage.freebsd.pl> References: <4D99DDB0.9090307@googlemail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: <4D99DDB0.9090307@googlemail.com> X-OS: FreeBSD 9.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: zfs porting roadmap? 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: Mon, 04 Apr 2011 16:58:10 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 04, 2011 at 05:03:12PM +0200, Lukas R=F6ssler wrote: > I browsed through the archives of the past few months and saw that > zfs is already ported up to v28 atm (thanks a lot at pjd - you do > awesome work!). >=20 > Don't get me wrong here, i don't want to sound demanding in any way, > i'm just interested - are there plans to port it up to the current > version (31, i believe)? The killer feature for me is encryption, > which was added in v30... >=20 > Thanks again for all your efforts, and thank you in advance for > answering a noobs question :) ZFS v28 is the last open-source ZFS version so far. I'd expect new features to be added by the top secret ZFS working group rather than ported. :) --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk2Z+JYACgkQForvXbEpPzR58ACfV9dIWWvAiLLSk/5oQ1DV9cKq RlAAoJZfXBvl8lSx01a1JtqPUAMmOeDt =OT7x -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 17:34:35 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 D4B571065673 for ; Mon, 4 Apr 2011 17:34:35 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 635148FC0C for ; Mon, 4 Apr 2011 17:34:35 +0000 (UTC) Received: by fxm11 with SMTP id 11so5370783fxm.13 for ; Mon, 04 Apr 2011 10:34:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:x-mailer:mime-version:content-type :content-transfer-encoding; bh=QeOzyZ5SmKVU/RxOMjIrjvWDivBH5ZCdv7E95/RAD3Q=; b=Qzn2xwby8cCsNdM1CsVbD6OuQsMjysHMPI1qk+n7QDv4FEdPSTtXCuOU++EoGJd5yq bK2Q/eFeXzNbf0bAwtxxkwxJGApBGRDmCiRcj+uhQPy5B0egq7Ec6qghc+xWWk0A47Uv hZW3gRftj22u8niNFFGNrDfF8mwqMNJjiR11c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=bGwAScKSkNaU8tWMvtnApUZgbn2pwQ27PUGlkm0l5modWKfAVHBKKgAbxq2HF6s3+T f41LEPapPzbqLdFXoFqMmOvTYHCxZdun1kiSnDkr8sph+M1rqNSRaBSVq45mIeDvLkSv hEEpHhHZsp+G1aO7NKbjpoYA8lJsn9ma+3f5U= Received: by 10.223.7.73 with SMTP id c9mr233612fac.117.1301937109488; Mon, 04 Apr 2011 10:11:49 -0700 (PDT) Received: from ernst.jennejohn.org (p578E19D1.dip.t-dialin.net [87.142.25.209]) by mx.google.com with ESMTPS id 21sm1812990fav.17.2011.04.04.10.11.47 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2011 10:11:48 -0700 (PDT) Date: Mon, 4 Apr 2011 19:11:45 +0200 From: Gary Jennejohn To: "binto" Message-ID: <20110404191145.23d5e93a@ernst.jennejohn.org> In-Reply-To: <011901cbf2da$672f0c40$140124c0@DBLJSW1S> References: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S> <4D99DE50.1030607@bellanet.org> <00f201cbf2d7$29816f30$140124c0@DBLJSW1S> <011901cbf2da$672f0c40$140124c0@DBLJSW1S> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2011 17:34:35 -0000 On Mon, 4 Apr 2011 23:10:14 +0800 "binto" wrote: > suspicious one is..bad sector.. > Error 6 is ENXIO, which basically means that the device suddenly disappeared, as far as geom is concerned. Are you using RAID or a mirror? ENXIO seems to only be set in geom/geom_fox.c, geom/mirror/g_mirror.c and geom/raid/g_raid.c. That is, bio_error, which is what is being reported, is only set to ENXIO in these files AFAICT. > ----- Original Message ----- > From: "binto" > To: "Graham Todd" ; > Sent: Monday, April 04, 2011 10:47 PM > Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > > > > if cabling, i wonder why in single mode there's no problem especially > > about filesystem . > > But in normal login when i use root user, then i got so many warn about > > that error 6. > > reboot after that. > > ??? [ can u explain?] > > > > now i'm still troubleshoot in configuration. > > i haven't try run hardware test yet. such as to switch HDD with another > > board or something. > > > > so far i haven't found missing data, except files that i remove..:D > > > > thanks > > > > ----- Original Message ----- > > From: "Graham Todd" > > To: "binto" ; > > Sent: Monday, April 04, 2011 11:05 PM > > Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > > > > > >> On 04/04/2011 07:56, binto wrote: > >>> Also i got before it's reboot suddenly: > >>> panic: initiate_write_inodeblock_ufs2: already started > >> > >> I think you're getting a panic from ufs2 and softdep somewhere because > >> for whatever reason geom is saying the drive has disappeared (bad > >> cabling, bad hardware, bad sector, electrical glitch, etc.)? Someone more > >> knowledgeable than me can explain the code path and error 6. > >> > >> If it is hardware and the drive that has your / or /usr filesystems then > >> panic'ing is "correct" behaviour I believe. If it is a USB drive being > >> pulled without umounting then I think FreeBSD is supposed to handle that > >> incorrect operation more gracefully since 7.* > >> > >> Was there data loss? Did the server reboot properly? Have you run any > >> hardware tests? > >> > >> cheers > >> > >>> Thanks > >>> Binto > >>> ----- Original Message ----- > >>> From: binto > >>> To: freebsd-fs@freebsd.org > >>> Sent: Monday, April 04, 2011 7:39 PM > >>> Subject: what is g_vfs_done() and error = 6?? how to fix it?? > >>> > >>> > >>> I got error message& my server suddenly drop : > >>> > >>> g_vfs_done() error = 6 > >>> > >>> g_vfs_done(): ad10s2a[READ(offset=1348599808, length=16384)]error = 6 > >>> anyone can help me please?? > >>> > >>> Thank you > >>> binto > >> > >> > >> > > > > _______________________________________________ > > 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" > > > > _______________________________________________ > 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" -- Gary Jennejohn From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 18:05:15 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 B51D31065676 for ; Mon, 4 Apr 2011 18:05:15 +0000 (UTC) (envelope-from pontomedon@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 477768FC1B for ; Mon, 4 Apr 2011 18:05:14 +0000 (UTC) Received: by fxm11 with SMTP id 11so5396730fxm.13 for ; Mon, 04 Apr 2011 11:05:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=04D15e0BKqgSXouRSBMP5EJwSGg3Rdh2cpWoNrtdASE=; b=wKuGubCioETeQRY6A20f42Dhc3WPU2Ur9LtpYIKi+PSiJk4/BQFmHtRG7Exh6XisFO L0qPDtPGojaG6/F31cRx1q44Lx/GG5XVzfyE4Aq3rNAf4mq42q4ALCwAJHxDD4h5wvqJ BZHhKrR0ac8tmAbmRynyuFoKP7E1mSQBPLYSs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=W5+wF9285DlkUHiK1boFaFi1f5h5Y3zlXbqbqwHYZVa9kjHCG1p8mtcrSVNd6xVSeb w0n1mpy0LGIImDo/srg4RDwU4zxCJnBoiZv9T2h7asr3ZGbHSFGAkOLytLBto5sZeiqF siTVonYE7Ykr/W4xagaPwfg4dWlefrPHOe5rU= Received: by 10.223.85.196 with SMTP id p4mr2592455fal.5.1301940313290; Mon, 04 Apr 2011 11:05:13 -0700 (PDT) Received: from [192.168.1.3] (chello062178135187.2.14.univie.teleweb.at [62.178.135.187]) by mx.google.com with ESMTPS id n15sm1827037fam.12.2011.04.04.11.05.12 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2011 11:05:12 -0700 (PDT) Message-ID: <4D9A0856.40709@googlemail.com> Date: Mon, 04 Apr 2011 20:05:10 +0200 From: "=?ISO-8859-15?Q?Lukas_R=F6ssler?=" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4D99DDB0.9090307@googlemail.com> <20110404165759.GA2007@garage.freebsd.pl> In-Reply-To: <20110404165759.GA2007@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: zfs porting roadmap? 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: Mon, 04 Apr 2011 18:05:15 -0000 Am 04.04.2011 18:57, schrieb Pawel Jakub Dawidek: > On Mon, Apr 04, 2011 at 05:03:12PM +0200, Lukas Rössler wrote: >> I browsed through the archives of the past few months and saw that >> zfs is already ported up to v28 atm (thanks a lot at pjd - you do >> awesome work!). >> >> Don't get me wrong here, i don't want to sound demanding in any way, >> i'm just interested - are there plans to port it up to the current >> version (31, i believe)? The killer feature for me is encryption, >> which was added in v30... >> >> Thanks again for all your efforts, and thank you in advance for >> answering a noobs question :) > > ZFS v28 is the last open-source ZFS version so far. I'd expect new > features to be added by the top secret ZFS working group rather than > ported. :) > hm do you mean "top secret working group" @ oracle? I'm fairly new to all that stuff.. http://hub.opensolaris.org/bin/view/Community+Group+zfs/30 here it says available in "Nevada, build 149", whereas here http://hub.opensolaris.org/bin/view/Project+zfs-crypto/ it says "Solaris 11 Express". I know that Oracle basically renamed OpenSolaris to Solaris Express, but how das "Nevada" fit into that picture? Funnily enough there seems to be source for zfs-crypto: http://src.opensolaris.org/source/xref/zfs-crypto/ I also read that Oracle continues to release Solaris (is that the right term here?) source under the CDDL license, but only after the binary release, so there should be source for versions higher than 28 sooner or later? Sorry for being offtopic, but all the info i find on the net just increases my confusion... Probably someone could answer my questions (via direct mail if it doesn't fit on the list..) Thanks, Lukas From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 18:08:18 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 3233A1065670; Mon, 4 Apr 2011 18:08:18 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id AAAF78FC15; Mon, 4 Apr 2011 18:08:17 +0000 (UTC) Received: by gwb15 with SMTP id 15so2676328gwb.13 for ; Mon, 04 Apr 2011 11:08:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EfLMaC/AC8XXDP+HKtYpN1Z/ELniFgXm5K1acXZv2rs=; b=bAXSY0zIBAuXiKxHLQ0k6PY27CZ4rTEBxtHVRY/5W1vasifLwpMFFlbY1l6jqeofj9 tzRBbnFvWjeaxB/ScfbigxL0ILFlT9lkh8CcKxtueJ0R3187y9njWRbrfXmTv7cZKC9S iLXk9hUbxfufV8yP4SuDr0c4Vt8RBosannMao= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=GkkPKX+LCkVq8lM1AM3B4EY08TKLTSch/Cej/mMXtTqaNLTJRd1GxaUZmtKq376T1S N1olonMvaJIyLkufy4YL9B23zmSup6hAtkrMSowQv9vj/RtZhV2FJCwLo4tc+IojV7Vw 4FeGcrhGE3qJ3cVcrWxO2LN6rtvl8k7nddvBY= MIME-Version: 1.0 Received: by 10.90.14.39 with SMTP id 39mr4164095agn.127.1301940496804; Mon, 04 Apr 2011 11:08:16 -0700 (PDT) Received: by 10.90.51.14 with HTTP; Mon, 4 Apr 2011 11:08:16 -0700 (PDT) In-Reply-To: <20110402084431.GB1849@garage.freebsd.pl> References: <20110402084431.GB1849@garage.freebsd.pl> Date: Mon, 4 Apr 2011 11:08:16 -0700 Message-ID: From: Freddie Cash To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Filesystems , FreeBSD-Current , FreeBSD Stable Subject: Re: Any success stories for HAST + ZFS? 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: Mon, 04 Apr 2011 18:08:18 -0000 On Sat, Apr 2, 2011 at 1:44 AM, Pawel Jakub Dawidek wrote= : > On Thu, Mar 24, 2011 at 01:36:32PM -0700, Freddie Cash wrote: >> [Not sure which list is most appropriate since it's using HAST + ZFS >> on -RELEASE, -STABLE, and -CURRENT. =C2=A0Feel free to trim the CC: on >> replies.] >> >> I'm having a hell of a time making this work on real hardware, and am >> not ruling out hardware issues as yet, but wanted to get some >> reassurance that someone out there is using this combination (FreeBSD >> + HAST + ZFS) successfully, without kernel panics, without core dumps, >> without deadlocks, without issues, etc. =C2=A0I need to know I'm not >> chasing a dead rabbit. > > I just committed a fix for a problem that might look like a deadlock. > With trociny@ patch and my last fix (to GEOM GATE and hastd) do you > still have any issues? Just to confirm, this is commit r220264, 220265, 220266 to -CURRENT? Looking through the commit logs, I don't see any of these MFC'd to -STABLE yet, so I can't test them directly. The storage box that was having the issues is running 8-STABLE r219754 at the moment (with ZFSv28 and Mikolag's ggate patches). I see there have been a lot of hast/ggate-related MFCs in the past week, but they don't include the deadlock patches. Once the deadlock patches above are MFC'd to -STABLE, I can do an upgrade cycle and test them. I do have the previous 9-CURRENT install saved, just nothing to run it on a= tm. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 18:10:50 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 AF84E1065675 for ; Mon, 4 Apr 2011 18:10:50 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6C6808FC08 for ; Mon, 4 Apr 2011 18:10:50 +0000 (UTC) Received: by gyg13 with SMTP id 13so2676802gyg.13 for ; Mon, 04 Apr 2011 11:10:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9tim0MQzWkLWONL8ISBV8i3nLrMAb4uFWW4vftPlOnU=; b=W3L3d/6DgNX0AmCaWIN9J7L4LzoTLy8TeXOgFgUPNWh11GCqRRL8w/nt4jR4gy96fM Wku+/La0tPXMrEMYx4w61OstRb2HgpkFgvUR4LkMViUnKhBKViQei2N+hZgFCVf0JYDE nVkQ1Q4Fz1C1XpfNP+zohoGJI5yzuDkInEkfE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SKFu0/mCyAarlmSE57MdcxqtSIdVzHM4s7caeYHhOxceVdWdbcP4hGEpq1kNX6Xse2 /y+YjpCegUQY6j90OYfk6wlTy/DTQT9SfRvLNL58Bs0xv+V69hPP5wh2+pTsm8Pjr5do M9NLvH96uRldJ4Y5rr8SpxFGtJr/HALDGl0q0= MIME-Version: 1.0 Received: by 10.91.160.15 with SMTP id m15mr7412806ago.181.1301940649599; Mon, 04 Apr 2011 11:10:49 -0700 (PDT) Received: by 10.90.51.14 with HTTP; Mon, 4 Apr 2011 11:10:49 -0700 (PDT) In-Reply-To: <4D9A0856.40709@googlemail.com> References: <4D99DDB0.9090307@googlemail.com> <20110404165759.GA2007@garage.freebsd.pl> <4D9A0856.40709@googlemail.com> Date: Mon, 4 Apr 2011 11:10:49 -0700 Message-ID: From: Freddie Cash To: =?UTF-8?Q?Lukas_R=C3=B6ssler?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: zfs porting roadmap? 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: Mon, 04 Apr 2011 18:10:50 -0000 On Mon, Apr 4, 2011 at 11:05 AM, Lukas R=C3=B6ssler = wrote: > hm do you mean "top secret working group" @ oracle? Search the zfs-discuss mailing list (or forums) for a thread with subject: "ZFS Going forward after Oracle - Let's get organized, let's get started." That has all the info about the "top-secret working group", which is *not* part of Oracle. Basically, it's FreeBSD, Linux, Illumos, OpenIndiana, and other non-Oracle developers working together to advance the open-source version of ZFS. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 18:59:40 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 9C7D11065675 for ; Mon, 4 Apr 2011 18:59:40 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4AC018FC27 for ; Mon, 4 Apr 2011 18:59:39 +0000 (UTC) Received: by iyj12 with SMTP id 12so7758075iyj.13 for ; Mon, 04 Apr 2011 11:59:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:x-openpgp-key-id:x-openpgp-key-fingerprint :x-openpgp-key-url; bh=GccO2Sv/VPa7oP4hHdZPtf/u1vk3tyxJAzbvpjwOmCI=; b=mYanVFJHYtUmeFOyTtjQaBXpJShy17myEX8QcC2RjJC8iQaYIQ2uvhl2XsHDSzvLmO cOijRxRUxUmEMwfWtC6ii+4KJCHPmCb8cG5lep+dhMp56G0ng8dX+8PPlGNWjpPmwzV7 egsJv4sqCqbUuMpjCGovtXV9L6qZMvfE8a42w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-openpgp-key-id :x-openpgp-key-fingerprint:x-openpgp-key-url; b=N5jZG+lyXUMPKw9m/uNNKFqbyRzhK++uHn9B+3VfvhdSu8DBDEqts4lgAAwsGFGEyb ci2nrX8GZ5wWOZpvSJhHYz+oNUqvb0cblCt2prtoJITijhafpTpNIDtsl9/ty9x5EKa0 31HlBfly/uJODl7M4oej0EB85Gc7eW44Uql8U= Received: by 10.42.145.71 with SMTP id e7mr1381148icv.314.1301943579514; Mon, 04 Apr 2011 11:59:39 -0700 (PDT) Received: from DataIX.net (adsl-99-181-155-201.dsl.klmzmi.sbcglobal.net [99.181.155.201]) by mx.google.com with ESMTPS id d9sm2243318ibb.36.2011.04.04.11.59.34 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2011 11:59:35 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p34IxV1e021479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Apr 2011 14:59:32 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p34IxUoq021478; Mon, 4 Apr 2011 14:59:30 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Mon, 4 Apr 2011 14:59:30 -0400 From: jhell To: Piotr Paczynski Message-ID: <20110404185930.GA96734@DataIX.net> References: <20110401013603.GA31034@icarus.home.lan> <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> <1301911993.17884.4.camel@core.nessbank> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E X-OpenPGP-Key-URL: http://bit.ly/0x89D8547E Cc: freebsd-fs@freebsd.org, Daryl Richards Subject: Re: ZFS failed after hard power off 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: Mon, 04 Apr 2011 18:59:40 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 04, 2011 at 12:48:35PM +0200, Piotr Paczynski wrote: > > gpt, not gpart. gpt - Guid Partition Table - is the table format, gpart > > is the tool. gpart can also create mbr partition tables. >=20 > Let me paste the partition table of my boot disk: >=20 > $ gpart show da0 > =3D> 34 3906207677 da0 GPT (1.8T) > 34 128 1 freebsd-boot (64K) > 162 8388608 2 freebsd-swap (4.0G) > 8388770 3897818941 3 freebsd-zfs (1.8T) >=20 > It looks like an ordinary GPT, which should work ok on Solaris, no? >=20 > Disks in my second pool do not use any partition table at all (raw > disk device is added directly to zpool) and this was imported ok in > Solaris. >=20 Just to put a final NOTE on this: Yes! ( *Solaris, OpenIndiana, IllumOS ) 1. Can... from FreeBSD... A. Import B. Destroy C. Scrub D. Export E. Send/Recieve F. Most anything else ZFS can do... ( *Solaris, OpenIndiana, IllumOS ) Recognizes pools from FreeBSD for... 2. A. Versions 6-28 MBR slice partitions from FreeBSD on ( *Solaris, OpenIndiana, IllumOS ) 3. A. Will relocate adNsN{x} to adNsN if imported on on any of the above resulting in the pool to be resized to entire length of slice. B. Does not see adNsN{x} and thus any other {x} will be lost on import. (3A) GPT partitions (adNpX) or (adaNpX) (daNpX) 4. A. Are interchangeable between both Solaris & FreeBSD upto v28 B. Usually results in using whole_disk enabling use of write cache. Labels, FreeBSD & ( *Solaris, OpenIndiana, IllumOS ) 5. A. Generic labels are not reccognized but the pool itself will be and will result in a loss of the label and a resize to the full length of the partition or slice if imported. B. GPT labels are not recognized but the disk still is. C. GPT labels can be used on FreeBSD while Solaris still uses the disk partition or slice. D. Labels as provided by glabel(8) are not found on other OS's do not expect them to show up anywhere but FreeBSD. Especially the generic labels. If your setting up a pool and you plan on using *Solaris for repair you should plan appropriately and setup your pool on a whole slice(sN) or partition(pN) and forget about using generic labels. That being said, Martin Matuska has created mfsBSD[6] images that have an available v28 module that can be used to repair your current install and can also be used to repair older pools without an upgrade of the on-disk versions. FreeBSD 9-CURRENT should also have snapshots available that will have ZFSv28 too! so relying on another OS is not entirely a must. At this time the URL to where those are located is not available from my location. Google ( site:ftp.freebsd.org snapshots ) for a list. 6. http://mfsbsd.vx.sk Good God, Good ZFS, Good Luck, Great Pawel! --=20 Regards, J. Hellenthal JJH48-ARIN 0x89D8547E --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJNmhUSAAoJEJBXh4mJ2FR+xbUH/RX1YFKa0nswes/LP168zNFy rGB3igfCrFoitS/9jD7bbp9zBBv+3AScgnGBd7ulaSCbdFTI1MMeZDyRRc2lSiXA oyKAyZ1LXa7EXqI5PndQPtuxsEBoWNMiyPHgi2FY5dDQ5oqnk7QUwPfHl/q0kCfI f8dlIsgxXVubjUp+9G70nNebTnamINXgWX4opF3+nG/lvdlof1oW6hUj0g1BSX6a hfnE4T/DlPmEFyKaTumqVon+r9H+0NNV1SmGhBkcriFpHSD5zrzQQodzd6qe7G2Q xcR/wLac6Savv6bPwQLO4ThS4OlKlpVIMm62SwrACOd7xFqiA8pc+btBK1uXT88= =YiC1 -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw-- From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 21:28:50 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 12641106566B for ; Mon, 4 Apr 2011 21:28:50 +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 C291C8FC21 for ; Mon, 4 Apr 2011 21:28:49 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Q6rKJ-0005to-BX for freebsd-fs@freebsd.org; Mon, 04 Apr 2011 23:28:47 +0200 Received: from 195.225.157.86 ([195.225.157.86]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 04 Apr 2011 23:28:47 +0200 Received: from c.kworr by 195.225.157.86 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 04 Apr 2011 23:28:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Volodymyr Kostyrko Date: Tue, 05 Apr 2011 00:28:31 +0300 Lines: 19 Message-ID: References: <4D99DDB0.9090307@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 195.225.157.86 User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; uk-UA; rv:1.9.2.15) Gecko/20110306 Thunderbird/3.1.9 In-Reply-To: <4D99DDB0.9090307@googlemail.com> Subject: Re: zfs porting roadmap? 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: Mon, 04 Apr 2011 21:28:50 -0000 04.04.2011 18:03, Lukas Rössler напиÑав(ла): > I browsed through the archives of the past few months and saw that zfs > is already ported up to v28 atm (thanks a lot at pjd - you do awesome > work!). > > Don't get me wrong here, i don't want to sound demanding in any way, i'm > just interested - are there plans to port it up to the current version > (31, i believe)? The killer feature for me is encryption, which was > added in v30... For me the real killing feature would be import of better compressor like snappy or bmdiff. I'd really vote for snappy, because: 1. It beats LZO at compression speed holding tight on decompression. It also beats all other compression algorithms we currently have for ZFS. 2. It has BSD-style license. -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 02:37:34 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 7BEF3106566B for ; Tue, 5 Apr 2011 02:37:34 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: from smtp28.3g-net.net (smtp28.3g-net.net [202.127.97.67]) by mx1.freebsd.org (Postfix) with ESMTP id F22878FC19 for ; Tue, 5 Apr 2011 02:37:33 +0000 (UTC) Received: from lb1.3gate.net (smtp.triplegate.net.id [202.127.97.100]) by smtp2.3g-net.net (Postfix) with ESMTP id EBBEE848057; Tue, 5 Apr 2011 09:37:29 +0700 (WIT) Received: from DBLJSW1S (tebet.triplegate.net.id [202.127.98.144]) by lb1.3gate.net (Postfix) with SMTP id EE3642110E7; Tue, 5 Apr 2011 09:13:56 +0700 (WIT) Message-ID: <000401cbf332$059a8c40$7ac8a8c0@DBLJSW1S> From: "binto" To: References: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S><4D99DE50.1030607@bellanet.org><00f201cbf2d7$29816f30$140124c0@DBLJSW1S><011901cbf2da$672f0c40$140124c0@DBLJSW1S> <20110404191145.23d5e93a@ernst.jennejohn.org> Date: Tue, 5 Apr 2011 02:36:32 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350 Cc: freebsd-fs@freebsd.org Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? 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, 05 Apr 2011 02:37:34 -0000 I'm not using both, RAID or a mirror. Hmm...Geom..i'm gonna find out about that. Ok thanks for all advices.. I'm gonna try all those suggestion. Even, all are new experience for me. Meanwhile i switch all services into secondary machine, Thanks a lot guys. ----- Original Message ----- From: "Gary Jennejohn" To: "binto" Cc: "Graham Todd" ; Sent: Tuesday, April 05, 2011 1:11 AM Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > On Mon, 4 Apr 2011 23:10:14 +0800 > "binto" wrote: > >> suspicious one is..bad sector.. >> > > Error 6 is ENXIO, which basically means that the device suddenly > disappeared, as far as geom is concerned. > > Are you using RAID or a mirror? ENXIO seems to only be set in > geom/geom_fox.c, geom/mirror/g_mirror.c and geom/raid/g_raid.c. > That is, bio_error, which is what is being reported, is only set > to ENXIO in these files AFAICT. > >> ----- Original Message ----- >> From: "binto" >> To: "Graham Todd" ; >> Sent: Monday, April 04, 2011 10:47 PM >> Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? >> >> >> > if cabling, i wonder why in single mode there's no problem especially >> > about filesystem . >> > But in normal login when i use root user, then i got so many warn about >> > that error 6. >> > reboot after that. >> > ??? [ can u explain?] >> > >> > now i'm still troubleshoot in configuration. >> > i haven't try run hardware test yet. such as to switch HDD with another >> > board or something. >> > >> > so far i haven't found missing data, except files that i remove..:D >> > >> > thanks >> > >> > ----- Original Message ----- >> > From: "Graham Todd" >> > To: "binto" ; >> > Sent: Monday, April 04, 2011 11:05 PM >> > Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? >> > >> > >> >> On 04/04/2011 07:56, binto wrote: >> >>> Also i got before it's reboot suddenly: >> >>> panic: initiate_write_inodeblock_ufs2: already started >> >> >> >> I think you're getting a panic from ufs2 and softdep somewhere because >> >> for whatever reason geom is saying the drive has disappeared (bad >> >> cabling, bad hardware, bad sector, electrical glitch, etc.)? Someone >> >> more >> >> knowledgeable than me can explain the code path and error 6. >> >> >> >> If it is hardware and the drive that has your / or /usr filesystems >> >> then >> >> panic'ing is "correct" behaviour I believe. If it is a USB drive being >> >> pulled without umounting then I think FreeBSD is supposed to handle >> >> that >> >> incorrect operation more gracefully since 7.* >> >> >> >> Was there data loss? Did the server reboot properly? Have you run >> >> any >> >> hardware tests? >> >> >> >> cheers >> >> >> >>> Thanks >> >>> Binto >> >>> ----- Original Message ----- >> >>> From: binto >> >>> To: freebsd-fs@freebsd.org >> >>> Sent: Monday, April 04, 2011 7:39 PM >> >>> Subject: what is g_vfs_done() and error = 6?? how to fix it?? >> >>> >> >>> >> >>> I got error message& my server suddenly drop : >> >>> >> >>> g_vfs_done() error = 6 >> >>> >> >>> g_vfs_done(): ad10s2a[READ(offset=1348599808, length=16384)]error >> >>> = 6 >> >>> anyone can help me please?? >> >>> >> >>> Thank you >> >>> binto >> >> >> >> >> >> >> > >> > _______________________________________________ >> > 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" >> > >> >> _______________________________________________ >> 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" > > > -- > Gary Jennejohn > From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 08:22:37 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 790BC106566B for ; Tue, 5 Apr 2011 08:22:37 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 03F658FC17 for ; Tue, 5 Apr 2011 08:22:36 +0000 (UTC) Received: by wyf23 with SMTP id 23so111737wyf.13 for ; Tue, 05 Apr 2011 01:22:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=RV/J9koPHtKnVl5ue76n+F78mWrIT9zopTaSioM/46A=; b=hmaCRDhkz7THpf9/siS4SJsQ6SY7Ik/MYZa2eHr/8ailu3l6rxPjDu8HkkmzIF5W8K 2PWo8saXrh1oIXvv5C2aXUh3ou+Iee8BZQnVO2vSWXgCHwIm/TTcnv2gmXeVeBQVMY2o X0fbGgzaGT9XK2vubFk8xt/wh7g3zkDY+/Yj0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cr1iSNbbgR+XZoZjLfQZA5lCZBYKtdZTxqaXlTRmSF0qxf4mlrFSEZZrHhXeIs7/jK CtdU/N3iYwYwD1sbx0dzVBbD8ZhD+Rq9k6bgc7yZ5ISR6W9YvC03vkAx9wjo85lk6DQm u1vEJdig+sokekRBkDjyKua6aDRbCr8bM1uZY= MIME-Version: 1.0 Received: by 10.216.82.142 with SMTP id o14mr654702wee.114.1301991755697; Tue, 05 Apr 2011 01:22:35 -0700 (PDT) Received: by 10.216.187.16 with HTTP; Tue, 5 Apr 2011 01:22:35 -0700 (PDT) In-Reply-To: <20110404185930.GA96734@DataIX.net> References: <20110401013603.GA31034@icarus.home.lan> <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> <1301911993.17884.4.camel@core.nessbank> <20110404185930.GA96734@DataIX.net> Date: Tue, 5 Apr 2011 09:22:35 +0100 Message-ID: From: krad To: jhell Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Daryl Richards Subject: Re: ZFS failed after hard power off 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, 05 Apr 2011 08:22:37 -0000 On 4 April 2011 19:59, jhell wrote: > On Mon, Apr 04, 2011 at 12:48:35PM +0200, Piotr Paczynski wrote: > > > gpt, not gpart. gpt - Guid Partition Table - is the table format, gpart > > > is the tool. gpart can also create mbr partition tables. > > > > Let me paste the partition table of my boot disk: > > > > $ gpart show da0 > > => 34 3906207677 da0 GPT (1.8T) > > 34 128 1 freebsd-boot (64K) > > 162 8388608 2 freebsd-swap (4.0G) > > 8388770 3897818941 3 freebsd-zfs (1.8T) > > > > It looks like an ordinary GPT, which should work ok on Solaris, no? > > > > Disks in my second pool do not use any partition table at all (raw > > disk device is added directly to zpool) and this was imported ok in > > Solaris. > > > > Just to put a final NOTE on this: > > Yes! ( *Solaris, OpenIndiana, IllumOS ) > 1. Can... from FreeBSD... > A. Import > B. Destroy > C. Scrub > D. Export > E. Send/Recieve > F. Most anything else ZFS can do... > > ( *Solaris, OpenIndiana, IllumOS ) Recognizes pools from FreeBSD for... > 2. > A. Versions 6-28 > > MBR slice partitions from FreeBSD on ( *Solaris, OpenIndiana, IllumOS ) > 3. > A. Will relocate adNsN{x} to adNsN if imported on on any of the above > resulting in the pool to be resized to entire length of slice. > B. Does not see adNsN{x} and thus any other {x} will be lost on > import. (3A) > > GPT partitions (adNpX) or (adaNpX) (daNpX) > 4. > A. Are interchangeable between both Solaris & FreeBSD upto v28 > B. Usually results in using whole_disk enabling use of write cache. > > Labels, FreeBSD & ( *Solaris, OpenIndiana, IllumOS ) > 5. > A. Generic labels are not reccognized but the pool itself will be and > will result in a loss of the label and a resize to the full length of > the partition or slice if imported. > B. GPT labels are not recognized but the disk still is. > C. GPT labels can be used on FreeBSD while Solaris still uses the > disk partition or slice. > D. Labels as provided by glabel(8) are not found on other OS's do not > expect them to show up anywhere but FreeBSD. Especially the generic > labels. > > > If your setting up a pool and you plan on using *Solaris for repair you > should plan appropriately and setup your pool on a whole slice(sN) or > partition(pN) and forget about using generic labels. > > That being said, Martin Matuska has created mfsBSD[6] images that have an > available v28 module that can be used to repair your current install and > can also be used to repair older pools without an upgrade of the on-disk > versions. > > FreeBSD 9-CURRENT should also have snapshots available that will have > ZFSv28 too! so relying on another OS is not entirely a must. At this > time the URL to where those are located is not available from my > location. Google ( site:ftp.freebsd.org snapshots ) for a list. > > > 6. http://mfsbsd.vx.sk > > > > Good God, Good ZFS, Good Luck, Great Pawel! > > -- > > Regards, > > J. Hellenthal > JJH48-ARIN > 0x89D8547E > > you will need to force import if it wasn't exported as the hostid will be different on the solaris box than the freebsd one From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 09:28:09 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 BBEED106564A for ; Tue, 5 Apr 2011 09:28:09 +0000 (UTC) (envelope-from sec@42.org) Received: from ice.42.org (v6.42.org [IPv6:2001:608:9::1]) by mx1.freebsd.org (Postfix) with ESMTP id 754AE8FC0A for ; Tue, 5 Apr 2011 09:28:09 +0000 (UTC) Received: by ice.42.org (Postfix, from userid 1000) id 9D88F28555; Tue, 5 Apr 2011 11:28:08 +0200 (CEST) Date: Tue, 5 Apr 2011 11:28:08 +0200 From: Stefan `Sec` Zehl To: freebsd-fs@freebsd.org Message-ID: <20110405092808.GI37730@ice.42.org> X-Current-Backlog: 3813 messages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i I-love-doing-this: really X-Modeline: vim:set ts=8 sw=4 smarttab tw=72 si noic notitle: Accept-Languages: de, en X-URL: http://sec.42.org/ Subject: Snapshot deadlock debugging 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, 05 Apr 2011 09:28:09 -0000 Hi, On my FreebBSD (amd64, geli, daily ufs snapshots) box, the snapshot process and my rtorrent client somehow deadlocked. I've filed a PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=156193 Can someone with more knowledge here take a look at it, and see if there is any more intresting info to be gotten from the (still running) system before I reboot it? Thanks, Sec -- Ich dachte immer, Microsoft realisiert das Autosave im Anwender: Jeder weiss doch, dass ein Zeilenende in Unix Control-J ist und in Windows Control-M Control-J Control-S. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 12:05:09 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 ED327106566B; Tue, 5 Apr 2011 12:05:09 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id AF8C48FC18; Tue, 5 Apr 2011 12:05:08 +0000 (UTC) Received: by wwc33 with SMTP id 33so328233wwc.31 for ; Tue, 05 Apr 2011 05:05:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:organization:references :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=Ug//cj8gOU7r+ZBzLxHLlM/jpS1tdTg1rmEJuXBLH0M=; b=XPhIxNPoY/e/Iq3fgHivi0QtEEVRUFHNKDsy9D+DEwCQ4iQT1HCP5WqPm5LWxGuZAS 03dhLm8tPz8YaLglOZB1MKZVcpRkYA2jD4adHRDy+OzW19QLeIGz/87uNvUZZjXMhIlc I0yjKPHr5H2GHpAcT7iLC7xTu0ygeyfVRmduU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:organization:references:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=KY4YPv8Gxr+RfycpX+td8nlSA+uaqmZAZVslWW2/PfuCh+3CTuGUxXQoQlKMBhJ0Fr ekQd/zRk4be8E1Z6zaZQsbrx/1d0BWHWV9ZzehM7DS7xkYuKWcpGZgTOTIeeJKJ7r54c fKSO9hT/WYAidtfh9sFN3e1t4Rq/6Is1bRdFo= Received: by 10.227.151.15 with SMTP id a15mr8258351wbw.184.1302005107660; Tue, 05 Apr 2011 05:05:07 -0700 (PDT) Received: from localhost ([94.27.39.186]) by mx.google.com with ESMTPS id y29sm3514096wbd.55.2011.04.05.05.05.04 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 05 Apr 2011 05:05:05 -0700 (PDT) From: Mikolaj Golub To: Freddie Cash Organization: TOA Ukraine References: <20110402084431.GB1849@garage.freebsd.pl> Sender: Mikolaj Golub Date: Tue, 05 Apr 2011 15:05:02 +0300 In-Reply-To: (Freddie Cash's message of "Mon, 4 Apr 2011 11:08:16 -0700") Message-ID: <86tyecnbtd.fsf@in138.ua3> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: FreeBSD Filesystems , FreeBSD Stable , FreeBSD-Current , Pawel Jakub Dawidek Subject: Re: Any success stories for HAST + ZFS? 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, 05 Apr 2011 12:05:10 -0000 On Mon, 4 Apr 2011 11:08:16 -0700 Freddie Cash wrote: FC> On Sat, Apr 2, 2011 at 1:44 AM, Pawel Jakub Dawidek wrote: >> >> I just committed a fix for a problem that might look like a deadlock. >> With trociny@ patch and my last fix (to GEOM GATE and hastd) do you >> still have any issues? FC> Just to confirm, this is commit r220264, 220265, 220266 to -CURRENT? Yes, r220264 and 220266. As it is stated in the commit log MFC is planned after 1 week. -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 14:16:36 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 E0E6A1065679 for ; Tue, 5 Apr 2011 14:16:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 64FF08FC08 for ; Tue, 5 Apr 2011 14:16:34 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p35EGV6E062465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 5 Apr 2011 17:16:31 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p35EGVja032212 for ; Tue, 5 Apr 2011 17:16:31 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p35EGVp9032211 for freebsd-fs@freebsd.org; Tue, 5 Apr 2011 17:16:31 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 5 Apr 2011 17:16:31 +0300 From: Kostik Belousov To: freebsd-fs@freebsd.org Message-ID: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FYjy/y/1gvMuB097" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Subject: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 14:16:36 -0000 --FYjy/y/1gvMuB097 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =46rom very old and gloomy SysV times I remembered filesystem behaviour that silently truncated the file name components to the NAME_MAX limit, that was, AFAIR, 14. To much of my dismay, I met some usermode software recently that blindly tried to create the file from externally provided name, and sometimes failed with ENAMETOOLONG in similar situation. The authors are not cooperative. I ended up with the following hack, which almost turns off the _POSIX_NO_TRUNC behaviour, globally on the system. Patch allowed me to proceed. The cost in the default case is a single check, which is performed only on ENAMETOOLONG path. I am too chicken to commit it without prior discussion. diff --git a/sys/kern/vfs_lookup.c b/sys/kern/vfs_lookup.c index 50a2570..e9e7697 100644 --- a/sys/kern/vfs_lookup.c +++ b/sys/kern/vfs_lookup.c @@ -99,6 +99,11 @@ SYSCTL_INT(_vfs, OID_AUTO, lookup_shared, CTLFLAG_RW, &l= ookup_shared, 0, "Enables/Disables shared locks for path name translation"); TUNABLE_INT("vfs.lookup_shared", &lookup_shared); =20 +static int lookup_trim; +SYSCTL_INT(_vfs, OID_AUTO, lookup_trim, CTLFLAG_RW, &lookup_trim, 0, + "Enables/Disables trim of the long path component instead of ENAMETOOL= ONG"); +TUNABLE_INT("vfs.lookup_trim", &lookup_trim); + /* * Convert a pathname into a pointer to a locked vnode. * @@ -514,8 +519,14 @@ dirloop: continue; cnp->cn_namelen =3D cp - cnp->cn_nameptr; if (cnp->cn_namelen > NAME_MAX) { - error =3D ENAMETOOLONG; - goto bad; + if (!lookup_trim) { + error =3D ENAMETOOLONG; + goto bad; + } + ndp->ni_pathlen -=3D cnp->cn_namelen - NAME_MAX; + cnp->cn_namelen =3D NAME_MAX; + strcpy(cnp->cn_nameptr + cnp->cn_namelen, cp); + cp =3D cnp->cn_nameptr + cnp->cn_namelen; } #ifdef NAMEI_DIAGNOSTIC { char c =3D *cp; --FYjy/y/1gvMuB097 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk2bJD4ACgkQC3+MBN1Mb4j8JgCdHDI6bfeegkO1rSFiIf8RblPC YnoAoNl3bJkPaEcn07P6xUaurYrxo3PW =Ntd5 -----END PGP SIGNATURE----- --FYjy/y/1gvMuB097-- From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 14:35:52 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 0E11F1065672 for ; Tue, 5 Apr 2011 14:35:52 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from relay0.exonetric.net (relay0.exonetric.net [82.138.248.161]) by mx1.freebsd.org (Postfix) with ESMTP id 9F8B88FC16 for ; Tue, 5 Apr 2011 14:35:51 +0000 (UTC) Received: from [192.168.111.107] (unknown [62.244.179.66]) by relay0.exonetric.net (Postfix) with ESMTP id 8A66557232; Tue, 5 Apr 2011 15:35:50 +0100 (BST) Mime-Version: 1.0 (Apple Message framework v1084) From: Mark Blackman In-Reply-To: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> Date: Tue, 5 Apr 2011 15:35:49 +0100 Message-Id: <7696AAE3-E04B-492F-9D96-3B526CFDFEE6@exonetric.com> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> To: Kostik Belousov X-Mailer: Apple Mail (2.1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 14:35:52 -0000 On 5 Apr 2011, at 15:16, Kostik Belousov wrote: > From very old and gloomy SysV times I remembered filesystem behaviour > that silently truncated the file name components to the NAME_MAX limit, > that was, AFAIR, 14. To much of my dismay, I met some usermode software > recently that blindly tried to create the file from externally provided > name, and sometimes failed with ENAMETOOLONG in similar situation. > The authors are not cooperative. > > I ended up with the following hack, which almost turns off the > _POSIX_NO_TRUNC behaviour, globally on the system. Patch allowed me > to proceed. The cost in the default case is a single check, which is > performed only on ENAMETOOLONG path. If this is global, it might deal with a failing test when building Perl on a ZFS-only system which also tests this property. In particular, I believe ZFS neither truncates nor returns an error for any pathname length, so I'm not sure what the right test result should be. Building perl produces something like.. Only one test fails: ok 25 - calling pathconf("/tmp", _PC_NO_TRUNC) not ok 26 - checking that the returned value is defined (it isn't) or that errno is clear (it isn't, it's Invalid argument) # Failed test ' checking that the returned value is defined # (it isn't) or that errno is clear (it isn't, it's Invalid argument)' # at t/sysconf.t line 63. This thread.. http://lists.freebsd.org/pipermail/freebsd-fs/2010-November/010069.html talked about the NO_TRUNC behaviour in the context of ZFS. - Mark From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 14:58:43 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 DF632106566B for ; Tue, 5 Apr 2011 14:58:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 7E26C8FC14 for ; Tue, 5 Apr 2011 14:58:43 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p35EwRAv065419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Apr 2011 17:58:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p35EwRWL039227; Tue, 5 Apr 2011 17:58:27 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p35EwPul039226; Tue, 5 Apr 2011 17:58:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 5 Apr 2011 17:58:25 +0300 From: Kostik Belousov To: Mark Blackman Message-ID: <20110405145825.GC78089@deviant.kiev.zoral.com.ua> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <7696AAE3-E04B-492F-9D96-3B526CFDFEE6@exonetric.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="b0HMt6CF7yv0Ir1M" Content-Disposition: inline In-Reply-To: <7696AAE3-E04B-492F-9D96-3B526CFDFEE6@exonetric.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 14:58:44 -0000 --b0HMt6CF7yv0Ir1M Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 05, 2011 at 03:35:49PM +0100, Mark Blackman wrote: >=20 > On 5 Apr 2011, at 15:16, Kostik Belousov wrote: >=20 > > From very old and gloomy SysV times I remembered filesystem behaviour > > that silently truncated the file name components to the NAME_MAX limit, > > that was, AFAIR, 14. To much of my dismay, I met some usermode software > > recently that blindly tried to create the file from externally provided > > name, and sometimes failed with ENAMETOOLONG in similar situation. > > The authors are not cooperative. > >=20 > > I ended up with the following hack, which almost turns off the > > _POSIX_NO_TRUNC behaviour, globally on the system. Patch allowed me > > to proceed. The cost in the default case is a single check, which is > > performed only on ENAMETOOLONG path. >=20 > If this is global, it might deal with a failing test when building Perl > on a ZFS-only system which also tests this property. >=20 > In particular, I believe ZFS neither truncates nor returns an error for a= ny=20 > pathname length, so I'm not sure what the right test result should be. >=20 > Building perl produces something like.. >=20 > Only one test fails: > ok 25 - calling pathconf("/tmp", _PC_NO_TRUNC) > not ok 26 - checking that the returned value is defined (it isn't) > or that errno is clear (it isn't, it's Invalid argument) > # Failed test ' checking that the returned value is defined > # (it isn't) or that errno is clear (it isn't, it's Invalid argument)' > # at t/sysconf.t line 63. >=20 > This thread.. >=20 > http://lists.freebsd.org/pipermail/freebsd-fs/2010-November/010069.html >=20 > talked about the NO_TRUNC behaviour in the context of ZFS. >=20 Reporting _PC_NO_TRUNC from zfs is easy, I think Pawel just had no time to care about this detail. Anyway, it is not directly relevant to what the posted patch did. Patch below incorporates zfs change, and also reporting of the vfs.lookup_trim from pathconf(2), just in case. diff --git a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c b/s= ys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c index 17eedee..9985716 100644 --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c @@ -5127,6 +5130,10 @@ zfs_pathconf(vnode_t *vp, int cmd, ulong_t *valp, cr= ed_t *cr, *valp =3D ACL_MAX_ENTRIES; return (0); =20 + case _PC_NO_TRUNC: + *valp =3D 1; + return (0); + default: return (EOPNOTSUPP); } diff --git a/sys/kern/vfs_lookup.c b/sys/kern/vfs_lookup.c index 50a2570..9ecf4e0 100644 --- a/sys/kern/vfs_lookup.c +++ b/sys/kern/vfs_lookup.c @@ -99,6 +99,11 @@ SYSCTL_INT(_vfs, OID_AUTO, lookup_shared, CTLFLAG_RW, &l= ookup_shared, 0, "Enables/Disables shared locks for path name translation"); TUNABLE_INT("vfs.lookup_shared", &lookup_shared); =20 +int lookup_trim; +SYSCTL_INT(_vfs, OID_AUTO, lookup_trim, CTLFLAG_RW, &lookup_trim, 0, + "Enables/Disables trim of the long path component instead of ENAMETOOL= ONG"); +TUNABLE_INT("vfs.lookup_trim", &lookup_trim); + /* * Convert a pathname into a pointer to a locked vnode. * @@ -514,8 +519,14 @@ dirloop: continue; cnp->cn_namelen =3D cp - cnp->cn_nameptr; if (cnp->cn_namelen > NAME_MAX) { - error =3D ENAMETOOLONG; - goto bad; + if (!lookup_trim) { + error =3D ENAMETOOLONG; + goto bad; + } + ndp->ni_pathlen -=3D cnp->cn_namelen - NAME_MAX; + cnp->cn_namelen =3D NAME_MAX; + strcpy(cnp->cn_nameptr + cnp->cn_namelen, cp); + cp =3D cnp->cn_nameptr + cnp->cn_namelen; } #ifdef NAMEI_DIAGNOSTIC { char c =3D *cp; diff --git a/sys/kern/vfs_syscalls.c b/sys/kern/vfs_syscalls.c index 4fc198e..9020223 100644 --- a/sys/kern/vfs_syscalls.c +++ b/sys/kern/vfs_syscalls.c @@ -2528,6 +2528,8 @@ lpathconf(td, uap) return (kern_pathconf(td, uap->path, UIO_USERSPACE, uap->name, NOFOLLOW)); } =20 +extern int lookup_trim; + int kern_pathconf(struct thread *td, char *path, enum uio_seg pathseg, int nam= e, u_long flags) @@ -2549,6 +2551,8 @@ kern_pathconf(struct thread *td, char *path, enum uio= _seg pathseg, int name, error =3D VOP_PATHCONF(nd.ni_vp, name, td->td_retval); vput(nd.ni_vp); VFS_UNLOCK_GIANT(vfslocked); + if (name =3D=3D _PC_NO_TRUNC && error =3D=3D 0 && td->td_retval !=3D 0) + td->td_retval[0] =3D !lookup_trim; return (error); } =20 --b0HMt6CF7yv0Ir1M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk2bLhEACgkQC3+MBN1Mb4gyNACfQFQbxY7udUrWpRvVKSw7r8FS vg8AoLGN2Vq2Hlar8Vr8Egc+clwzZ+TG =3hom -----END PGP SIGNATURE----- --b0HMt6CF7yv0Ir1M-- From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 15:27:51 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 9752A106567F for ; Tue, 5 Apr 2011 15:27:51 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 287348FC1A for ; Tue, 5 Apr 2011 15:27:50 +0000 (UTC) Received: by wyf23 with SMTP id 23so483828wyf.13 for ; Tue, 05 Apr 2011 08:27:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:x-mailer:mime-version:content-type :content-transfer-encoding; bh=Qr8F+n/BOROgiQpKXB+baGVyZ/2Kf+xR9D8quzYSxwk=; b=hP/QjDMlIE+Ziw0kkNcvj3BQSBLCOayTjDoOQZbkjE72WtqBnCT9ruhODBcMttSAlm PC0HIOzO31rl492ujO8IC2l0uTPN7Nb5typWlr93hjcG5jVsZU8d7WCX4/TeM6sa4jQE u5Jj//MQCgGrQEY1GQ2jBAQIlbefq8cBsl76M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=GUC8NB2jA38mahPyOmGj5/sn0yWaw42cvj79mnGa031M1QTiiJxR1FW4+jwvuMbb8E PgYWJ+wbWd4Qg5s/vKixrAr9qllV3L/k3LklljnpeB+p3LdBtqHMV5R3QApvpqnItJMw AD8J6asqNX84gceyxLywyqjqbM+5rlZ4junks= Received: by 10.227.147.196 with SMTP id m4mr8515652wbv.179.1302017270024; Tue, 05 Apr 2011 08:27:50 -0700 (PDT) Received: from ernst.jennejohn.org (p578E33EC.dip.t-dialin.net [87.142.51.236]) by mx.google.com with ESMTPS id ed10sm3635314wbb.32.2011.04.05.08.27.48 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 05 Apr 2011 08:27:49 -0700 (PDT) Date: Tue, 5 Apr 2011 17:27:46 +0200 From: Gary Jennejohn To: Kostik Belousov Message-ID: <20110405172746.4a02fe42@ernst.jennejohn.org> In-Reply-To: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2011 15:27:51 -0000 On Tue, 5 Apr 2011 17:16:31 +0300 Kostik Belousov wrote: > From very old and gloomy SysV times I remembered filesystem behaviour > that silently truncated the file name components to the NAME_MAX limit, > that was, AFAIR, 14. To much of my dismay, I met some usermode software > recently that blindly tried to create the file from externally provided > name, and sometimes failed with ENAMETOOLONG in similar situation. > The authors are not cooperative. > > I ended up with the following hack, which almost turns off the > _POSIX_NO_TRUNC behaviour, globally on the system. Patch allowed me > to proceed. The cost in the default case is a single check, which is > performed only on ENAMETOOLONG path. > > I am too chicken to commit it without prior discussion. > > diff --git a/sys/kern/vfs_lookup.c b/sys/kern/vfs_lookup.c > index 50a2570..e9e7697 100644 > --- a/sys/kern/vfs_lookup.c > +++ b/sys/kern/vfs_lookup.c > @@ -99,6 +99,11 @@ SYSCTL_INT(_vfs, OID_AUTO, lookup_shared, CTLFLAG_RW, &lookup_shared, 0, > "Enables/Disables shared locks for path name translation"); > TUNABLE_INT("vfs.lookup_shared", &lookup_shared); > > +static int lookup_trim; > +SYSCTL_INT(_vfs, OID_AUTO, lookup_trim, CTLFLAG_RW, &lookup_trim, 0, > + "Enables/Disables trim of the long path component instead of ENAMETOOLONG"); > +TUNABLE_INT("vfs.lookup_trim", &lookup_trim); > + > /* > * Convert a pathname into a pointer to a locked vnode. > * > @@ -514,8 +519,14 @@ dirloop: > continue; > cnp->cn_namelen = cp - cnp->cn_nameptr; > if (cnp->cn_namelen > NAME_MAX) { > - error = ENAMETOOLONG; > - goto bad; > + if (!lookup_trim) { I would intuitively expect trimming to be enabled when the sysctl is set to 1, but this is exactly the opposite of that. I personally would initialize it to 1. > + error = ENAMETOOLONG; > + goto bad; > + } > + ndp->ni_pathlen -= cnp->cn_namelen - NAME_MAX; > + cnp->cn_namelen = NAME_MAX; > + strcpy(cnp->cn_nameptr + cnp->cn_namelen, cp); > + cp = cnp->cn_nameptr + cnp->cn_namelen; > } > #ifdef NAMEI_DIAGNOSTIC > { char c = *cp; I must admit that I don't care for hacks like this to suit the vagaries of some idiot software developers who never heard of POSIX. But as long as it's off by default, then I guess it would be acceptable. -- Gary Jennejohn (gj@) From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 15:40:12 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 1A927106567A for ; Tue, 5 Apr 2011 15:40:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id AB7D48FC13 for ; Tue, 5 Apr 2011 15:40:05 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p35Fe257068471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Apr 2011 18:40:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p35Fe2xV050769; Tue, 5 Apr 2011 18:40:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p35Fe2UD050768; Tue, 5 Apr 2011 18:40:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 5 Apr 2011 18:40:02 +0300 From: Kostik Belousov To: Gary Jennejohn Message-ID: <20110405154002.GD78089@deviant.kiev.zoral.com.ua> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405172746.4a02fe42@ernst.jennejohn.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UrGwiw6HlSHyGEfa" Content-Disposition: inline In-Reply-To: <20110405172746.4a02fe42@ernst.jennejohn.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 15:40:12 -0000 --UrGwiw6HlSHyGEfa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 05, 2011 at 05:27:46PM +0200, Gary Jennejohn wrote: > On Tue, 5 Apr 2011 17:16:31 +0300 > Kostik Belousov wrote: > > @@ -514,8 +519,14 @@ dirloop: > > continue; > > cnp->cn_namelen =3D cp - cnp->cn_nameptr; > > if (cnp->cn_namelen > NAME_MAX) { > > - error =3D ENAMETOOLONG; > > - goto bad; > > + if (!lookup_trim) { >=20 > I would intuitively expect trimming to be enabled when the sysctl is set > to 1, but this is exactly the opposite of that. I personally would > initialize it to 1. Trimming is indeed enabled when lookup_trim is set to 1. If lookup_trim is 0, you get ENAMETOOLONG. --UrGwiw6HlSHyGEfa Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk2bN9EACgkQC3+MBN1Mb4j0EwCdGEBIUVNh3ITDTgWAxg/SFmRV CfsAoIL831WAsgy382/4ut1dMXkFYoTz =Rqd3 -----END PGP SIGNATURE----- --UrGwiw6HlSHyGEfa-- From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 16:31:10 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 7D1A9106566C for ; Tue, 5 Apr 2011 16:31:10 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0C8C18FC1B for ; Tue, 5 Apr 2011 16:31:08 +0000 (UTC) Received: by wwk4 with SMTP id 4so2946931wwk.1 for ; Tue, 05 Apr 2011 09:31:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:x-mailer:mime-version:content-type :content-transfer-encoding; bh=Q+4FxFFb7rXzILS+LVevj7XGUDnDdAs0Gpj00Q9r6yg=; b=uxAVAC/An3qO7OwrF6CL6B2OOiUR0Wpl3sJ4wqmDhaZtwcbCjxuCU6d3W7/m2Sivhh kC5VYxhf+LMH3bQEvn0QP9Ur3/+lzvVuswIn04DMXZChde3zEF6WVugHw4gzO8ksbjZZ CdKstdK1e8NhrDAnhfbfkfYjF2iyiNh3eGjgk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=Rovom1K9b04ETPoPScnqzH467kJ7VwokbpplcKNrYF0LPoE85tmjvJyXVeVRU/H0VL Q3/fRnrOkU9i8uldb1nHpGy28FlWDeGDpzX1AjXOWEO+eK0HqeSLF6lydR1DZ4Y6HDeo pzQBO5zD7ppg/2NuWB+y9pGHlbTN8soIDjv3A= Received: by 10.227.39.88 with SMTP id f24mr1085507wbe.88.1302021068034; Tue, 05 Apr 2011 09:31:08 -0700 (PDT) Received: from ernst.jennejohn.org (p578E33EC.dip.t-dialin.net [87.142.51.236]) by mx.google.com with ESMTPS id g7sm3670325wby.65.2011.04.05.09.31.06 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 05 Apr 2011 09:31:07 -0700 (PDT) Date: Tue, 5 Apr 2011 18:31:04 +0200 From: Gary Jennejohn To: Kostik Belousov Message-ID: <20110405183104.2304d94e@ernst.jennejohn.org> In-Reply-To: <20110405154002.GD78089@deviant.kiev.zoral.com.ua> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405172746.4a02fe42@ernst.jennejohn.org> <20110405154002.GD78089@deviant.kiev.zoral.com.ua> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2011 16:31:10 -0000 On Tue, 5 Apr 2011 18:40:02 +0300 Kostik Belousov wrote: > On Tue, Apr 05, 2011 at 05:27:46PM +0200, Gary Jennejohn wrote: > > On Tue, 5 Apr 2011 17:16:31 +0300 > > Kostik Belousov wrote: > > > @@ -514,8 +519,14 @@ dirloop: > > > continue; > > > cnp->cn_namelen = cp - cnp->cn_nameptr; > > > if (cnp->cn_namelen > NAME_MAX) { > > > - error = ENAMETOOLONG; > > > - goto bad; > > > + if (!lookup_trim) { > > > > I would intuitively expect trimming to be enabled when the sysctl is set > > to 1, but this is exactly the opposite of that. I personally would > > initialize it to 1. > Trimming is indeed enabled when lookup_trim is set to 1. > If lookup_trim is 0, you get ENAMETOOLONG. OK, but trimming to me as a native english speaker means returning ENAMETOOLONG rather than allowing names longer than NAME_MAX. That is, after all, what trimming means - cutting off. -- Gary Jennejohn From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 17:16:34 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 14F6F106566B for ; Tue, 5 Apr 2011 17:16:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DEF288FC0C for ; Tue, 5 Apr 2011 17:16:33 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 92DB146B06; Tue, 5 Apr 2011 13:16:33 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 311098A01B; Tue, 5 Apr 2011 13:16:33 -0400 (EDT) From: John Baldwin To: freebsd-fs@freebsd.org, gljennjohn@googlemail.com Date: Tue, 5 Apr 2011 13:16:32 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405154002.GD78089@deviant.kiev.zoral.com.ua> <20110405183104.2304d94e@ernst.jennejohn.org> In-Reply-To: <20110405183104.2304d94e@ernst.jennejohn.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104051316.32704.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 05 Apr 2011 13:16:33 -0400 (EDT) Cc: Subject: Re: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 17:16:34 -0000 On Tuesday, April 05, 2011 12:31:04 pm Gary Jennejohn wrote: > On Tue, 5 Apr 2011 18:40:02 +0300 > Kostik Belousov wrote: > > > On Tue, Apr 05, 2011 at 05:27:46PM +0200, Gary Jennejohn wrote: > > > On Tue, 5 Apr 2011 17:16:31 +0300 > > > Kostik Belousov wrote: > > > > @@ -514,8 +519,14 @@ dirloop: > > > > continue; > > > > cnp->cn_namelen = cp - cnp->cn_nameptr; > > > > if (cnp->cn_namelen > NAME_MAX) { > > > > - error = ENAMETOOLONG; > > > > - goto bad; > > > > + if (!lookup_trim) { > > > > > > I would intuitively expect trimming to be enabled when the sysctl is set > > > to 1, but this is exactly the opposite of that. I personally would > > > initialize it to 1. > > Trimming is indeed enabled when lookup_trim is set to 1. > > If lookup_trim is 0, you get ENAMETOOLONG. > > OK, but trimming to me as a native english speaker means returning ENAMETOOLONG > rather than allowing names longer than NAME_MAX. That is, after all, what trimming > means - cutting off. Err, it shortens the name by chopping off the part beyond NAME_MAX ("trimming") when enabled. You could perhaps call it 'truncate_long_pathnames' instead of 'lookup_trim' if you wanted it to be very descriptive. Personally, I find this a bit hackish. You could always "fix" the 3rd party software by using LD_PRELOAD() to implement a wrapper around open() that trimmed the name if open() fails with ENAMETOOLONG. -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 17:32:39 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 74811106566B for ; Tue, 5 Apr 2011 17:32:39 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 04E9A8FC18 for ; Tue, 5 Apr 2011 17:32:38 +0000 (UTC) Received: by ewy1 with SMTP id 1so217570ewy.13 for ; Tue, 05 Apr 2011 10:32:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bJ6yfpL1Im/oxD/LnPfw8EOXtEKnNWSpoqkx2/2htJw=; b=xpmA3Q3iQ4aPOihcvRCy4Dvbkn+PTC3OBQauDKSLdmQkkRY13E1/KQmydijtcbqPzr x0dtH3spRgoWBDKZl0XOlxKzAaa1A0HWjBEKd26J4EWLg/Ejq2XuN++CApvkelXd86Ki IR7THu069xF5oNuly4olS6mzII9kw1SiihMu4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=nsv9xgsfKJ3A8lEJSNdwaE1jMCEBqn1Ow2bZYmosWmYwfkQD4yzY2orDjrA03RBmvo /4PO41+saFggJN2DgUH5W49C4OyhDfrIEPiDpkMCBaqXVaNavMCLq1eS59NEiJngXOMo tHetu6ByHDY8sGBOdCkgFoZ5iQXqrLSIatoZs= MIME-Version: 1.0 Received: by 10.14.53.207 with SMTP id g55mr4360652eec.148.1302023206919; Tue, 05 Apr 2011 10:06:46 -0700 (PDT) Received: by 10.213.112.212 with HTTP; Tue, 5 Apr 2011 10:06:46 -0700 (PDT) In-Reply-To: <20110405183104.2304d94e@ernst.jennejohn.org> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405172746.4a02fe42@ernst.jennejohn.org> <20110405154002.GD78089@deviant.kiev.zoral.com.ua> <20110405183104.2304d94e@ernst.jennejohn.org> Date: Tue, 5 Apr 2011 13:06:46 -0400 Message-ID: From: Ryan Stone To: gljennjohn@googlemail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 17:32:39 -0000 On Tue, Apr 5, 2011 at 12:31 PM, Gary Jennejohn wrote: > OK, but trimming to me as a native english speaker means returning ENAMET= OOLONG > rather than allowing names longer than NAME_MAX. =A0That is, after all, w= hat trimming > means - cutting off. The two behaviours here are: lookup_trim =3D=3D 1 -- filenames are silently truncated(i.e. trimmed) if longer than NAME_MAX lookup_trim =3D=3D 0 -- filenames longer than NAME_MAX are rejected with ENAMETOOLONG The name makes perfect sense to me, personally. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 18:57:56 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 1375F106567A; Tue, 5 Apr 2011 18:57:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 65AB58FC12; Tue, 5 Apr 2011 18:57:54 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p35Ivpux083450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Apr 2011 21:57:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p35IvpwJ051522; Tue, 5 Apr 2011 21:57:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p35IvpMs051521; Tue, 5 Apr 2011 21:57:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 5 Apr 2011 21:57:51 +0300 From: Kostik Belousov To: John Baldwin Message-ID: <20110405185751.GE78089@deviant.kiev.zoral.com.ua> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405154002.GD78089@deviant.kiev.zoral.com.ua> <20110405183104.2304d94e@ernst.jennejohn.org> <201104051316.32704.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="V5miJjP81WSXKLM2" Content-Disposition: inline In-Reply-To: <201104051316.32704.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 18:57:56 -0000 --V5miJjP81WSXKLM2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 05, 2011 at 01:16:32PM -0400, John Baldwin wrote: > On Tuesday, April 05, 2011 12:31:04 pm Gary Jennejohn wrote: > > On Tue, 5 Apr 2011 18:40:02 +0300 > > Kostik Belousov wrote: > >=20 > > > On Tue, Apr 05, 2011 at 05:27:46PM +0200, Gary Jennejohn wrote: > > > > On Tue, 5 Apr 2011 17:16:31 +0300 > > > > Kostik Belousov wrote: > > > > > @@ -514,8 +519,14 @@ dirloop: > > > > > continue; > > > > > cnp->cn_namelen =3D cp - cnp->cn_nameptr; > > > > > if (cnp->cn_namelen > NAME_MAX) { > > > > > - error =3D ENAMETOOLONG; > > > > > - goto bad; > > > > > + if (!lookup_trim) { > > > >=20 > > > > I would intuitively expect trimming to be enabled when the sysctl i= s set > > > > to 1, but this is exactly the opposite of that. I personally would > > > > initialize it to 1. > > > Trimming is indeed enabled when lookup_trim is set to 1. > > > If lookup_trim is 0, you get ENAMETOOLONG. > >=20 > > OK, but trimming to me as a native english speaker means returning ENAM= ETOOLONG > > rather than allowing names longer than NAME_MAX. That is, after all, w= hat trimming > > means - cutting off. >=20 > Err, it shortens the name by chopping off the part beyond > NAME_MAX ("trimming") when enabled. You could perhaps call it > 'truncate_long_pathnames' instead of 'lookup_trim' if you wanted it to > be very descriptive. > > Personally, I find this a bit hackish. You could always "fix" the 3rd > party software by using LD_PRELOAD() to implement a wrapper around > open() that trimmed the name if open() fails with ENAMETOOLONG. Ok, I am taking the patch aside then. Please note that the change as is allowed any vfs syscall taking the path, to proceed. Also, the arbitrary path element, not only the last one, was handled. But this is only a question of amount of code in the preloaded library. --V5miJjP81WSXKLM2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk2bZi8ACgkQC3+MBN1Mb4iYrACeO6dDwg+u3yZJb07NXgOi+9OJ fv0AoMH11CKJ0RPUp6vmY5533M5MC9ax =vnqU -----END PGP SIGNATURE----- --V5miJjP81WSXKLM2-- From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 19:03:33 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 D9187106566B for ; Tue, 5 Apr 2011 19:03:33 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.freebsd.org (Postfix) with ESMTP id 634D18FC0A for ; Tue, 5 Apr 2011 19:03:32 +0000 (UTC) Received: from c122-106-155-58.carlnfd1.nsw.optusnet.com.au (c122-106-155-58.carlnfd1.nsw.optusnet.com.au [122.106.155.58]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p35J3TeU017000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Apr 2011 05:03:30 +1000 Date: Wed, 6 Apr 2011 05:03:29 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Kostik Belousov In-Reply-To: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> Message-ID: <20110406034131.L2689@besplex.bde.org> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 19:03:33 -0000 On Tue, 5 Apr 2011, Kostik Belousov wrote: > From very old and gloomy SysV times I remembered filesystem behaviour > that silently truncated the file name components to the NAME_MAX limit, > that was, AFAIR, 14. To much of my dismay, I met some usermode software > recently that blindly tried to create the file from externally provided > name, and sometimes failed with ENAMETOOLONG in similar situation. > The authors are not cooperative. Apply rmrf. > I ended up with the following hack, which almost turns off the > _POSIX_NO_TRUNC behaviour, globally on the system. Patch allowed me > to proceed. The cost in the default case is a single check, which is > performed only on ENAMETOOLONG path. Please don't commit this. This is already handled correctly for gloomy file systems by returning 0 from pathconf(path, _PC_NO_TRUNC) for ones that have short names, although the global definitions of _POSIX_NO_TRUNC and NAME_MAX have always been broken in FreeBSD. msdosfs does this even when it has long names. The main other file systems that do it are hpfs and ntfs, which I think shouldn't do it since they always have long names. Perhaps they do this for compatibility with WinDOS. FreeBSD defines _POSIX_NO_TRUNC as 1, which means that file names are _never_ truncated and is inconsistent what actual file systems like msdsofs do. FreeBSD defines NAME_MAX as a certain value, which means that the name length limit is _always_ this value and is inconsistent with the limit that actual file systems like msdosfs have. > diff --git a/sys/kern/vfs_lookup.c b/sys/kern/vfs_lookup.c > index 50a2570..e9e7697 100644 > --- a/sys/kern/vfs_lookup.c > +++ b/sys/kern/vfs_lookup.c > @@ -99,6 +99,11 @@ SYSCTL_INT(_vfs, OID_AUTO, lookup_shared, CTLFLAG_RW, &lookup_shared, 0, > "Enables/Disables shared locks for path name translation"); > TUNABLE_INT("vfs.lookup_shared", &lookup_shared); > > +static int lookup_trim; > +SYSCTL_INT(_vfs, OID_AUTO, lookup_trim, CTLFLAG_RW, &lookup_trim, 0, > + "Enables/Disables trim of the long path component instead of ENAMETOOLONG"); Enabling this is another way of breaking the guarantee that the compile-time constant _POSIX_NO_TRUNC gives the run-time behaviour. > +TUNABLE_INT("vfs.lookup_trim", &lookup_trim); It is a style bug (bloat) to have a tunable for something that doesn't need to be set for booting. > + > /* > * Convert a pathname into a pointer to a locked vnode. > * > @@ -514,8 +519,14 @@ dirloop: > continue; > cnp->cn_namelen = cp - cnp->cn_nameptr; > if (cnp->cn_namelen > NAME_MAX) { This hard coding of NAME_MAX gives various bugs which are now larger than before. Before, the only bug was that file systems that could support a {NAME_MAX} (= pathconf(path, _PC_NAME_MAX) longer than the compile-time constant NAME_MAX can't do it, since the vfs level rejects such names here. Some check is needed here to avoid overrunning the buffer, but the limit on the buffer size shouldn't the one for a broken implementation of the user API. With a non-broken implementation, NAME_MAX cannot be defined (except possibly visibly only in the kernel) and the limit here should be the maximum needed by all file systems. This can then be increased if a new file system needs it without breaking the user API, or it can be made larger than necessary to allow for expansion with incomplete coordination with new file systems. > - error = ENAMETOOLONG; > - goto bad; Even if the name length is not > NAME_MAX, the ENAMETOOLONG error or truncation may still occur in inidividualy file systems. I doubt that all file systems handle this correctly. For example, msdosfs never returns ENAMETOOLONG, and this is correct since msdosfs advertises {_PC_NO_TRUNC} = 0. But {_PC_NO_TRUNC} = 0 is wrong since the above implements _PC_NO_TRUNC = 1 unconditionally if the the name length exceeds NAME_MAX. > + if (!lookup_trim) { > + error = ENAMETOOLONG; > + goto bad; > + } > + ndp->ni_pathlen -= cnp->cn_namelen - NAME_MAX; > + cnp->cn_namelen = NAME_MAX; > + strcpy(cnp->cn_nameptr + cnp->cn_namelen, cp); > + cp = cnp->cn_nameptr + cnp->cn_namelen; This makes {_PC_NO_TRUNC} as perfectly broken as _POSIX_NO_TRUNC for file systems that implement _POSIX_NO_TRUNC, since the patch doesn't touch individual file systems so all the ones that return 1 for pathconf(path, _PC_NO_TRUNC) become inconsistent with their actual behavior. If you fix this, then the patch becomes correct but uglier. > } > #ifdef NAMEI_DIAGNOSTIC > { char c = *cp; > The code for the pathconf() vop in individual file systems has considerable ugliness related to this. Most file systems want the defaults for everything related to pathnames, but the implementation provides no way to get the defaults from another layer, so most vops duplicate a not-so-big case statement. OTOH vop_stdpathconf() provides a "default" for the whole vop which is very nonstandard and unsuitable as a default for almost everything in it that is not related to pathnames. It also has large style bugs (indentation errors) which were not present in the place it was copied from. It is essentially devfs's patconf vop, and it now seems to be used only by coda, devfs, fdescfs, portalfs and zfs. The use of it in coda, devfs and zfs shows how it can be be used as a default after all: start with an fs-specific vop and only use vop_stdpathconf() for cases that you don't want to override. But vop_stdpathconf() is unsuitable for this, since it provides many cases that are correct for at most devfs or only for a few file systems. These are: _PC_LINK_MAX = LINK_MAX: wrong because most file systems don't support hard links _PC_MAX_CANON = MAX_CANON _PC_MAX_INPUT = MAX_INPUT _PC_VDISABLE = POSIX_VDISABLE: wrong because only devfs supports device files wrong for most devfs files too, since most device files are not ttys MAX_CANON and MAX_INPUT are also wrong _PC_PIPE_BUF = PIPE_BUF: wrong because most file systems don't support named pipes or sockets PIPE_BUF may also be wrong for sockets (I think it is a variable depending on watermarks which can be set by ioctls) After removing these, only the pathname-related cases _PC_NAME_MAX and _PC_NO_TRUNC, and _PC_CHOWN_RESTRICTED are left. Perhaps it's not worth having a default for just these. ufs_pathconf() is now quite large and ugly, with many ufs-specific cases that can't be defaulted, and almost total disorder for the cases. It wouldn't benefit from defaulting just 3 cases. It has complications related to fifos. This seems to result in the pathconf selectors for pathnames failing for pathnames that refer to a fifo. Whether they work is implementation-defined (they are only required to work for pathnames that refer to directories), but FreeBSD normally makes them work for all types of files. Bruce From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 19:13:58 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 8A152106566C; Tue, 5 Apr 2011 19:13:58 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id E9A408FC13; Tue, 5 Apr 2011 19:13:57 +0000 (UTC) Received: by gxk28 with SMTP id 28so328952gxk.13 for ; Tue, 05 Apr 2011 12:13:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=KIJYwFEg5+6yEFkgBTlCy2o3RQ7tedqCIu25RT91Ts4=; b=FhKGmJE3BStG8udaH8AjCrMz6L6SS90Z01rxhBcxPhAqtx/PIi4sg/2xgBg8pIOtNE aGz2VYDaArs3nAJuQsNBXl+Dkhb0cndcrz4k09xNGdhkYniWGt3chamSL/XcMyDpziV8 jBL+0pQuQ+RGgBcU1ZWugO294RKRY2ECxM7nI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FNHXK39QXdonQEYEjpav511iqHCMvflOtsGWe1GujXFiykJBmqsXwCtF6JmFHEg5vR qmW4AaEsfy/lo1KTvlIgRP8SeB5uwG04Y3SaNrMcb68FMmfPZAwVteDsEnJ0qdvOcH1/ NQYa3dl01HUFypjPM2IQ2+pkVmE/Ep/L3TXDo= MIME-Version: 1.0 Received: by 10.90.14.39 with SMTP id 39mr928443agn.127.1302030837143; Tue, 05 Apr 2011 12:13:57 -0700 (PDT) Received: by 10.90.51.14 with HTTP; Tue, 5 Apr 2011 12:13:57 -0700 (PDT) In-Reply-To: <86tyecnbtd.fsf@in138.ua3> References: <20110402084431.GB1849@garage.freebsd.pl> <86tyecnbtd.fsf@in138.ua3> Date: Tue, 5 Apr 2011 12:13:57 -0700 Message-ID: From: Freddie Cash To: Mikolaj Golub Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Filesystems , FreeBSD Stable , FreeBSD-Current , Pawel Jakub Dawidek Subject: Re: Any success stories for HAST + ZFS? 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, 05 Apr 2011 19:13:58 -0000 On Tue, Apr 5, 2011 at 5:05 AM, Mikolaj Golub wrote: > On Mon, 4 Apr 2011 11:08:16 -0700 Freddie Cash wrote: > > =C2=A0FC> On Sat, Apr 2, 2011 at 1:44 AM, Pawel Jakub Dawidek wrote: > =C2=A0>> > =C2=A0>> I just committed a fix for a problem that might look like a dead= lock. > =C2=A0>> With trociny@ patch and my last fix (to GEOM GATE and hastd) do = you > =C2=A0>> still have any issues? > > =C2=A0FC> Just to confirm, this is commit r220264, 220265, 220266 to -CUR= RENT? > > Yes, r220264 and 220266. As it is stated in the commit log MFC is planned > after 1 week. Okay. I'll keep an eye out next week for the MFC of those patches to hit -STABLE, and do an upgrade/test cycle after that point. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 19:18:59 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 E91C6106566C for ; Tue, 5 Apr 2011 19:18:59 +0000 (UTC) (envelope-from dnewman@networktest.com) Received: from mail3.networktest.com (mail3.networktest.com [69.55.234.104]) by mx1.freebsd.org (Postfix) with ESMTP id C51C88FC19 for ; Tue, 5 Apr 2011 19:18:59 +0000 (UTC) Received: from localhost (localhost [69.55.234.104]) by mail3.networktest.com (Postfix) with ESMTP id 5BDD92560D3 for ; Tue, 5 Apr 2011 12:01:40 -0700 (PDT) Received: from mail3.networktest.com ([69.55.234.104]) by localhost (mail3.networktest.com [69.55.234.104]) (amavisd-maia, port 10024) with ESMTP id 02358-02 for ; Tue, 5 Apr 2011 12:01:40 -0700 (PDT) Received: from dhcp207.eng.networktest.com (ns.networktest.com [205.147.16.129]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dnewman@networktest.com) by mail3.networktest.com (Postfix) with ESMTPSA id 23F4D2560D2 for ; Tue, 5 Apr 2011 12:01:40 -0700 (PDT) Message-ID: <4D9B6713.4050107@networktest.com> Date: Tue, 05 Apr 2011 12:01:39 -0700 From: David Newman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4C51ECAA.2070707@networktest.com> <4C51FE41.8030906@FreeBSD.org> <4D941BFF.6050807@networktest.com> <4D973400.9060404@networktest.com> <201104041138.p34BckHS029801@higson.cam.lispworks.com> In-Reply-To: <201104041138.p34BckHS029801@higson.cam.lispworks.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: new ZFS install (was: Re: fixing a busted ZFS upgrade) 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, 05 Apr 2011 19:19:00 -0000 On 4/4/11 4:38 AM, Martin Simmons wrote: >>>>>> On Sat, 02 Apr 2011 07:34:40 -0700, David Newman said: >> >> Thanks for this script. Problem is, I can't get to the point where I can >> run it. > > The script is used to perform the upgrade, so it would be too late for you > anyway (it would probably make things worse). > > >> I've tried booting from 8.1 and 8.2 mfsBSD ISOs but both hang at >> loader.conf. > > Have you tried the regular FreeBSD installation ISO? That doesn't know about > ZFS by default, but you can enter Fixit mode with "Use the live filesystem > CDROM/DVD" and load the modules using > > kldload /dist/boot/kernel/opensolaris.ko > kldload /dist/boot/kernel/zfs.ko Thanks, that did the trick, along with repairing the boot records on each disk. This server is showing some evidence of flaky hardware, and I'm looking to move its data onto a new server running FreeBSD 8.2 and ZFS in all partitions. I understand the guide I used to build the old server has been deprecated. What's the recommended setup these days? Thanks again! dn > > __Martin > _______________________________________________ > 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" From owner-freebsd-fs@FreeBSD.ORG Tue Apr 5 19:41:42 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 07410106566C; Tue, 5 Apr 2011 19:41:42 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.freebsd.org (Postfix) with ESMTP id 8008D8FC1F; Tue, 5 Apr 2011 19:41:40 +0000 (UTC) Received: from c122-106-155-58.carlnfd1.nsw.optusnet.com.au (c122-106-155-58.carlnfd1.nsw.optusnet.com.au [122.106.155.58]) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p35JfbL5025183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Apr 2011 05:41:38 +1000 Date: Wed, 6 Apr 2011 05:41:37 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Kostik Belousov In-Reply-To: <20110405185751.GE78089@deviant.kiev.zoral.com.ua> Message-ID: <20110406053603.F3067@besplex.bde.org> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405154002.GD78089@deviant.kiev.zoral.com.ua> <20110405183104.2304d94e@ernst.jennejohn.org> <201104051316.32704.jhb@freebsd.org> <20110405185751.GE78089@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC 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, 05 Apr 2011 19:41:42 -0000 On Tue, 5 Apr 2011, Kostik Belousov wrote: > On Tue, Apr 05, 2011 at 01:16:32PM -0400, John Baldwin wrote: >> Personally, I find this a bit hackish. You could always "fix" the 3rd >> party software by using LD_PRELOAD() to implement a wrapper around >> open() that trimmed the name if open() fails with ENAMETOOLONG. Or install it on one of the file systems that has {_PC_NO_TRUNC} = 0 (might need a chroot, and the following fix). > Ok, I am taking the patch aside then. Please note that the change > as is allowed any vfs syscall taking the path, to proceed. Also, > the arbitrary path element, not only the last one, was handled. > But this is only a question of amount of code in the preloaded > library. There is one thing that can be changed without incrementing the bug count: make {_PC_NO_TRUNC} = 0 actually work. Currently, this fails for pathnames larger than NAME_MAX, since vfs doesn't know what either {NAME_MAX} or {_PC_NO_TRUNC} are and always assumes the global values. Bruce From owner-freebsd-fs@FreeBSD.ORG Wed Apr 6 07:14:51 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 CAFFE106564A for ; Wed, 6 Apr 2011 07:14:51 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 52B568FC08 for ; Wed, 6 Apr 2011 07:14:50 +0000 (UTC) Received: by fxm11 with SMTP id 11so986065fxm.13 for ; Wed, 06 Apr 2011 00:14:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:date:from:to:subject:message-id:in-reply-to :references:reply-to:x-mailer:mime-version:content-type :content-transfer-encoding; bh=oJguafHp7PzV73UUDnAhtot1EiVdY6DVn31f0/dJYzs=; b=Wxn/scX59wiVscYq6WsuV4dbnqqYwtDc03kJ+4LYO+mBwwwVXcrtjH7OLrTZUxg4vW FE/SPrt6eDxvcRNfQCQrVHveaZptdaLUf/36nmqc0sx/aXkrR1/L1k/ukRMUEBLmv+h+ lilDotUa5Q5/tXdxUbhInmoKroStISNp3F2rY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=ff1KZUxVIoEU9sn1jdVnd1/uKY5Rqj7BeNdQkMv8+hnDqj5UZhyZGQVcjzv4RxiqpG q3ZDlfBWCM1dmLPokQboC1PEQQ2ONOOh+fvo7tb+BFM02LXZguSMU9nVVZJPhzwLgz/q dLl2rRGfHjTeISjjPsBCXO0mDRcZhxetdQGXQ= Received: by 10.223.63.212 with SMTP id c20mr667832fai.37.1302074090193; Wed, 06 Apr 2011 00:14:50 -0700 (PDT) Received: from ernst.jennejohn.org (p578E31D4.dip.t-dialin.net [87.142.49.212]) by mx.google.com with ESMTPS id n9sm80528fax.27.2011.04.06.00.14.48 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Apr 2011 00:14:49 -0700 (PDT) Date: Wed, 6 Apr 2011 09:14:47 +0200 From: Gary Jennejohn To: freebsd-fs@freebsd.org Message-ID: <20110406091447.0205de17@ernst.jennejohn.org> In-Reply-To: References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405172746.4a02fe42@ernst.jennejohn.org> <20110405154002.GD78089@deviant.kiev.zoral.com.ua> <20110405183104.2304d94e@ernst.jennejohn.org> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Knob to turn off _POSIX_NO_TRUNC X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2011 07:14:51 -0000 On Tue, 5 Apr 2011 13:06:46 -0400 Ryan Stone wrote: > On Tue, Apr 5, 2011 at 12:31 PM, Gary Jennejohn > wrote: > > OK, but trimming to me as a native english speaker means returning ENAMETOOLONG > > rather than allowing names longer than NAME_MAX.  That is, after all, what trimming > > means - cutting off. > > The two behaviours here are: > > lookup_trim == 1 -- filenames are silently truncated(i.e. trimmed) if > longer than NAME_MAX > lookup_trim == 0 -- filenames longer than NAME_MAX are rejected with > ENAMETOOLONG > > The name makes perfect sense to me, personally. After sending off this e-mail the penny dropped and I finally realized just exactly what the patch is doing. Obviously, the way the sysctl is being used is correct. So, sorry for the noise. -- Gary Jennejohn From owner-freebsd-fs@FreeBSD.ORG Wed Apr 6 08:13:29 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 CBAFA106564A; Wed, 6 Apr 2011 08:13:29 +0000 (UTC) (envelope-from nwf@cs.jhu.edu) Received: from blaze.cs.jhu.edu (blaze.cs.jhu.edu [128.220.13.50]) by mx1.freebsd.org (Postfix) with ESMTP id 825EF8FC12; Wed, 6 Apr 2011 08:13:29 +0000 (UTC) Received: from gradx.cs.jhu.edu (gradx.cs.jhu.edu [128.220.13.52]) by blaze.cs.jhu.edu (8.14.3/8.14.3) with ESMTP id p3680hhV021057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 6 Apr 2011 04:00:43 -0400 (EDT) Received: from gradx.cs.jhu.edu (localhost [127.0.0.1]) by gradx.cs.jhu.edu (8.14.3/8.13.1) with ESMTP id p3680h1d009359; Wed, 6 Apr 2011 04:00:43 -0400 Received: (from nwf@localhost) by gradx.cs.jhu.edu (8.14.3/8.13.8/Submit) id p3680hCM009358; Wed, 6 Apr 2011 04:00:43 -0400 Date: Wed, 6 Apr 2011 04:00:43 -0400 From: Nathaniel W Filardo To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Message-ID: <20110406080043.GQ609@gradx.cs.jhu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NEvmWj2iiHf6S+l1" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-08-17) Cc: Subject: ZFS panic with concurrent recv and read-heavy workload 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: Wed, 06 Apr 2011 08:13:30 -0000 --NEvmWj2iiHf6S+l1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable When racing two workloads, one doing > zfs recv -v -d testpool and the other > find /testpool -type f -print0 | xargs -0 sha1 I can (seemingly reliably) trigger this panic: panic: Lock buf_hash_table.ht_locks[i].ht_lock not exclusively locked @ /us= r/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/arc.= c:1869 =20 = =20 cpuid =3D 1 = =20 KDB: stack backtrace: = =20 panic() at panic+0x1c8 = =20 _sx_assert() at _sx_assert+0xc4 = =20 _sx_xunlock() at _sx_xunlock+0x98 = =20 arc_evict() at arc_evict+0x614 = =20 arc_get_data_buf() at arc_get_data_buf+0x360 = =20 arc_buf_alloc() at arc_buf_alloc+0x94 = =20 dmu_buf_will_fill() at dmu_buf_will_fill+0xfc dmu_write() at dmu_write+0xec dmu_recv_stream() at dmu_recv_stream+0x8a8 = =20 zfs_ioc_recv() at zfs_ioc_recv+0x354 = =20 zfsdev_ioctl() at zfsdev_ioctl+0xe0 = =20 devfs_ioctl_f() at devfs_ioctl_f+0xe8 = =20 kern_ioctl() at kern_ioctl+0x294 = =20 ioctl() at ioctl+0x198 syscallenter() at syscallenter+0x270 syscall() at syscall+0x74 = =20 -- syscall (54, FreeBSD ELF64, ioctl) %o7=3D0x40c13e24 -- = =20 userland() at 0x40e72cc8 = =20 user trace: trap %o7=3D0x40c13e24 = =20 pc 0x40e72cc8, sp 0x7fdffff4641 pc 0x40c158f4, sp 0x7fdffff4721 = =20 pc 0x40c1e878, sp 0x7fdffff47f1 = =20 pc 0x40c1ce54, sp 0x7fdffff8b01 = =20 pc 0x40c1dbe0, sp 0x7fdffff9431 = =20 pc 0x40c1f718, sp 0x7fdffffd741 = =20 pc 0x10731c, sp 0x7fdffffd831 = =20 pc 0x10c90c, sp 0x7fdffffd8f1 = =20 pc 0x103ef0, sp 0x7fdffffe1d1 = =20 pc 0x4021aff4, sp 0x7fdffffe291 = =20 done The machine is a freshly installed and built sparc64 2-way SMP, running today's -CURRENT with http://people.freebsd.org/~mm/patches/zfs/zfs_ioctl_compat_bugfix.patch applied. Of note, it has only 1G of RAM in it, so kmem_max <=3D 512M. Thoughts? More information? Thanks in advance. --nwf; --NEvmWj2iiHf6S+l1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk2cHasACgkQTeQabvr9Tc+K4QCeOE6VM+JEoPVsvgDXPpIhSuG/ Nq4Ani1uL00nzKfhxpAQRxWCc51hWxw2 =ep5z -----END PGP SIGNATURE----- --NEvmWj2iiHf6S+l1-- From owner-freebsd-fs@FreeBSD.ORG Wed Apr 6 17:29:54 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02EDA1065780 for ; Wed, 6 Apr 2011 17:29:54 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B691C8FC1B for ; Wed, 6 Apr 2011 17:29:53 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 5D11746B58 for ; Wed, 6 Apr 2011 13:29:53 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D0A158A027 for ; Wed, 6 Apr 2011 13:29:52 -0400 (EDT) From: John Baldwin To: fs@freebsd.org Date: Wed, 6 Apr 2011 13:29:51 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201104061329.51170.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 06 Apr 2011 13:29:52 -0400 (EDT) Cc: Subject: zfsboot cleanup patch to remove use of xread 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: Wed, 06 Apr 2011 17:29:54 -0000 boot2 has a gross hack where it calls back into boot1 to do disk I/O due to size constraints. zfsboot copied this code, but zfsboot does not suffer from the same size restrictions, so I'd like to remove it. I have a patch that should do this, but I don't currently have a test system setup to test this. If someone has an easy way to test a modified zfsboot (including a way to recover easily in case it fails to boot), please test this patch: Index: boot/i386/boot2/Makefile =================================================================== --- boot/i386/boot2/Makefile (revision 220383) +++ boot/i386/boot2/Makefile (working copy) @@ -32,6 +32,7 @@ -mno-align-long-strings \ -mrtd \ -mregparm=3 \ + -DUSE_XREAD \ -D${BOOT2_UFS} \ -DFLAGS=${BOOT_BOOT1_FLAGS} \ -DSIOPRT=${BOOT_COMCONSOLE_PORT} \ Index: boot/i386/zfsboot/zfsldr.S =================================================================== --- boot/i386/zfsboot/zfsldr.S (revision 220383) +++ boot/i386/zfsboot/zfsldr.S (working copy) @@ -30,16 +30,12 @@ .set PRT_NUM,0x4 # Partitions .set PRT_BSD,0xa5 # Partition type -/* Flag Bits */ - .set FL_PACKET,0x80 # Packet mode - /* Misc. Constants */ .set SIZ_PAG,0x1000 # Page size .set SIZ_SEC,0x200 # Sector size .set NSECT,0x80 .globl start - .globl xread .code16 start: jmp main # Start recognizably @@ -49,7 +45,7 @@ * FAT disks have this at the start of their MBR. While normal BIOS's will * work fine without this section, IBM's El Torito emulation "fixes" up the * BPB by writing into the memory copy of the MBR. Rather than have data - * written into our xread routine, we'll define a BPB to work around it. + * written into our code, we'll define a BPB to work around it. * The data marked with (T) indicates a field required for a ThinkPad to * recognize the disk and (W) indicates fields written from IBM BIOS code. * The use of the BPB is based on what OpenBSD and NetBSD implemented in @@ -80,34 +76,7 @@ .org 0x25,0x90 /* - * Trampoline used by boot2 to call read to read data from the disk via - * the BIOS. Call with: - * - * %ecx:%eax - long - LBA to read in - * %es:(%bx) - caddr_t - buffer to read data into - * %dl - byte - drive to read from - * %dh - byte - num sectors to read - */ - -xread: push %ss # Address - pop %ds # data -/* - * Setup an EDD disk packet and pass it to read - */ -xread.1: pushl %ecx # Starting absolute block - pushl %eax # block number - push %es # Address of - push %bx # transfer buffer - xor %ax,%ax # Number of - movb %dh,%al # blocks to - push %ax # transfer - push $0x10 # Size of packet - mov %sp,%bp # Packet pointer - callw read # Read from disk - lea 0x10(%bp),%sp # Clear stack - lret # To far caller -/* - * Load the rest of boot2 and BTX up, copy the parts to the right locations, + * Load the rest of zfsboot2 and BTX up, copy the parts to the right locations, * and start it all up. */ @@ -181,7 +150,7 @@ * itself to 0x9000 - doing it in this order means that none of the * memcpy regions overlap which would corrupt the copy. Normally, BTX * clients start at MEM_USR, or 0xa000, but when we use btxld to - * create boot2, we use an entry point of 0x2000. That entry point is + * create zfsboot2, we use an entry point of 0x2000. That entry point is * relative to MEM_USR; thus boot2.bin starts at 0xc000. * * The load area and the target area for the client overlap so we have @@ -241,15 +210,29 @@ /* - * Trampoline used to call read from within boot1. + * Trampoline used to call read from within zfsldr. Sets up an EDD + * packet on the stack and passes it to read. + * + * %eax - int - LBA to read in relative to partition start + * %dl - byte - drive to read from + * %dh - byte - num sectors to read + * %si - ptr - MBR partition entry */ nread: xor %eax,%eax # Sector offset in partition -nread.1: mov $MEM_BUF,%bx # Transfer buffer - xor %ecx,%ecx # Get +nread.1: xor %ecx,%ecx # Get addl 0x8(%si),%eax # LBA adc $0,%ecx - push %cs # Read from - callw xread.1 # disk + pushl %ecx # Starting absolute block + pushl %eax # block number + push %es # Address of + push $MEM_BUF # transfer buffer + xor %ax,%ax # Number of + movb %dh,%al # blocks to + push %ax # transfer + push $0x10 # Size of packet + mov %sp,%bp # Packet pointer + callw read # Read from disk + lea 0x10(%bp),%sp # Clear stack jnc return # If success, return mov $msg_read,%si # Otherwise, set the error # message and fall through to @@ -293,9 +276,7 @@ * %dl - byte - drive number * stack - 10 bytes - EDD Packet */ -read: testb $FL_PACKET,%cs:MEM_REL+flags-start # LBA support enabled? - jz read.1 # No, use CHS - cmpb $0x80,%dl # Hard drive? +read: cmpb $0x80,%dl # Hard drive? jb read.1 # No, use CHS mov $0x55aa,%bx # Magic push %dx # Save @@ -311,73 +292,9 @@ movb $0x42,%ah # BIOS: Extended int $0x13 # read retw # To caller -#if 0 -read.1: push %dx # Save - movb $0x8,%ah # BIOS: Get drive - int $0x13 # parameters - movb %dh,%ch # Max head number - pop %dx # Restore - jc return # If error - andb $0x3f,%cl # Sectors per track - jz ereturn # If zero - cli # Disable interrupts - mov 0x8(%bp),%eax # Get LBA - push %dx # Save - movzbl %cl,%ebx # Divide by - xor %edx,%edx # sectors - div %ebx # per track - movb %ch,%bl # Max head number - movb %dl,%ch # Sector number - inc %bx # Divide by - xorb %dl,%dl # number - div %ebx # of heads - movb %dl,%bh # Head number - pop %dx # Restore - cmpl $0x3ff,%eax # Cylinder number supportable? - sti # Enable interrupts - ja ereturn # No, return an error - xchgb %al,%ah # Set up cylinder - rorb $0x2,%al # number - orb %ch,%al # Merge - inc %ax # sector - xchg %ax,%cx # number - movb %bh,%dh # Head number - subb %ah,%al # Sectors this track - mov 0x2(%bp),%ah # Blocks to read - cmpb %ah,%al # To read - jb read.2 # this -#ifdef TRACK_AT_A_TIME - movb %ah,%al # track -#else - movb $1,%al # one sector -#endif -read.2: mov $0x5,%di # Try count -read.3: les 0x4(%bp),%bx # Transfer buffer - push %ax # Save - movb $0x2,%ah # BIOS: Read - int $0x13 # from disk - pop %bx # Restore - jnc read.4 # If success - dec %di # Retry? - jz read.6 # No - xorb %ah,%ah # BIOS: Reset - int $0x13 # disk system - xchg %bx,%ax # Block count - jmp read.3 # Continue -read.4: movzbw %bl,%ax # Sectors read - add %ax,0x8(%bp) # Adjust - jnc read.5 # LBA, - incw 0xa(%bp) # transfer -read.5: shlb %bl # buffer - add %bl,0x5(%bp) # pointer, - sub %al,0x2(%bp) # block count - ja read.1 # If not done -read.6: retw # To caller -#else read.1: mov $msg_chs,%si jmp error msg_chs: .asciz "CHS not supported" -#endif /* Messages */ @@ -386,8 +303,6 @@ prompt: .asciz " error\r\n" -flags: .byte FLAGS # Flags - .org PRT_OFF,0x90 /* Partition table */ Index: boot/i386/zfsboot/Makefile =================================================================== --- boot/i386/zfsboot/Makefile (revision 220383) +++ boot/i386/zfsboot/Makefile (working copy) @@ -6,9 +6,6 @@ NM?= nm -# A value of 0x80 enables LBA support. -BOOT_BOOT1_FLAGS?= 0x80 - BOOT_COMCONSOLE_PORT?= 0x3f8 BOOT_COMCONSOLE_SPEED?= 9600 B2SIOFMT?= 0x3 @@ -25,7 +22,6 @@ -mno-align-long-strings \ -mrtd \ -DBOOT2 \ - -DFLAGS=${BOOT_BOOT1_FLAGS} \ -DSIOPRT=${BOOT_COMCONSOLE_PORT} \ -DSIOFMT=${B2SIOFMT} \ -DSIOSPD=${BOOT_COMCONSOLE_SPEED} \ @@ -64,7 +60,7 @@ ${LD} ${LDFLAGS} -e start -Ttext ${ORG1} -o ${.TARGET} zfsldr.o CLEANFILES+= zfsboot2 zfsboot.ld zfsboot.ldr zfsboot.bin zfsboot.out \ - zfsboot.o zfsboot.s zfsboot.s.tmp xreadorg.h sio.o + zfsboot.o zfsboot.s zfsboot.s.tmp sio.o # We currently allow 65536 bytes for zfsboot - in practice it could be # any size up to 3.5Mb but keeping it fixed size simplifies zfsldr. @@ -91,20 +87,13 @@ zfsboot.o: zfsboot.s -SRCS= zfsboot.c xreadorg.h +SRCS= zfsboot.c -zfsboot.s: zfsboot.c xreadorg.h ${.CURDIR}/../../zfs/zfsimpl.c +zfsboot.s: zfsboot.c ${.CURDIR}/../../zfs/zfsimpl.c ${CC} ${CFLAGS} -S -o zfsboot.s.tmp ${.CURDIR}/zfsboot.c sed -e '/align/d' -e '/nop/d' < zfsboot.s.tmp > zfsboot.s rm -f zfsboot.s.tmp -xreadorg.h: zfsldr.out - ${NM} -t d ${.ALLSRC} | awk '/([0-9])+ T xread/ \ - { x = $$1 - ORG1; \ - printf("#define XREADORG %#x\n", REL1 + x) }' \ - ORG1=`printf "%d" ${ORG1}` \ - REL1=`printf "%d" ${REL1}` > ${.TARGET} - .if ${MACHINE_CPUARCH} == "amd64" beforedepend zfsboot.s: machine CLEANFILES+= machine Index: boot/i386/common/drv.c =================================================================== --- boot/i386/common/drv.c (revision 220383) +++ boot/i386/common/drv.c (working copy) @@ -26,7 +26,7 @@ #include "rbx.h" #include "util.h" #include "drv.h" -#ifndef GPT +#ifdef USE_XREAD #include "xreadorg.h" #endif @@ -58,7 +58,7 @@ } #endif /* GPT */ -#ifdef GPT +#ifndef USE_XREAD static struct { uint16_t len; uint16_t count; @@ -66,7 +66,7 @@ uint16_t seg; uint64_t lba; } packet; -#endif /* GPT */ +#endif int drvread(struct dsk *dskp, void *buf, daddr_t lba, unsigned nblk) @@ -75,7 +75,7 @@ if (!OPT_CHECK(RBX_QUIET)) printf("%c\b", c = c << 8 | c >> 24); -#ifdef GPT +#ifndef USE_XREAD packet.len = 0x10; packet.count = nblk; packet.off = VTOPOFF(buf); @@ -87,7 +87,7 @@ v86.edx = dskp->drive; v86.ds = VTOPSEG(&packet); v86.esi = VTOPOFF(&packet); -#else /* !GPT */ +#else /* USE_XREAD */ v86.ctl = V86_ADDR | V86_CALLF | V86_FLAGS; v86.addr = XREADORG; /* call to xread in boot1 */ v86.es = VTOPSEG(buf); @@ -95,7 +95,7 @@ v86.ebx = VTOPOFF(buf); v86.ecx = lba >> 32; v86.edx = nblk << 8 | dskp->drive; -#endif /* !GPT */ +#endif /* USE_XREAD */ v86int(); if (V86_CY(v86.efl)) { printf("%s: error %u lba %u\n", -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Wed Apr 6 18:26:04 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 5BDD31065673 for ; Wed, 6 Apr 2011 18:26:04 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [193.34.186.230]) by mx1.freebsd.org (Postfix) with ESMTP id EDA6B8FC17 for ; Wed, 6 Apr 2011 18:26:03 +0000 (UTC) Received: from higson.cam.lispworks.com (higson [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.3/8.14.3) with ESMTP id p36IFDWn056315; Wed, 6 Apr 2011 19:15:13 +0100 (BST) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id p36IFDY7024762; Wed, 6 Apr 2011 19:15:13 +0100 Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id p36IFDUd024758; Wed, 6 Apr 2011 19:15:13 +0100 Date: Wed, 6 Apr 2011 19:15:13 +0100 Message-Id: <201104061815.p36IFDUd024758@higson.cam.lispworks.com> From: Martin Simmons To: freebsd-fs@freebsd.org In-reply-to: <4D9B6713.4050107@networktest.com> (message from David Newman on Tue, 05 Apr 2011 12:01:39 -0700) References: <4C51ECAA.2070707@networktest.com> <4C51FE41.8030906@FreeBSD.org> <4D941BFF.6050807@networktest.com> <4D973400.9060404@networktest.com> <201104041138.p34BckHS029801@higson.cam.lispworks.com> <4D9B6713.4050107@networktest.com> Subject: Re: new ZFS install (was: Re: fixing a busted ZFS upgrade) 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: Wed, 06 Apr 2011 18:26:04 -0000 >>>>> On Tue, 05 Apr 2011 12:01:39 -0700, David Newman said: > > On 4/4/11 4:38 AM, Martin Simmons wrote: > >>>>>> On Sat, 02 Apr 2011 07:34:40 -0700, David Newman said: > >> > >> I've tried booting from 8.1 and 8.2 mfsBSD ISOs but both hang at > >> loader.conf. > > > > Have you tried the regular FreeBSD installation ISO? That doesn't know about > > ZFS by default, but you can enter Fixit mode with "Use the live filesystem > > CDROM/DVD" and load the modules using > > > > kldload /dist/boot/kernel/opensolaris.ko > > kldload /dist/boot/kernel/zfs.ko > > Thanks, that did the trick, along with repairing the boot records on > each disk. Good -- though it is strange the mfsBSD hung. Does it still hang, now that you have repaired the system? > This server is showing some evidence of flaky hardware, and I'm looking > to move its data onto a new server running FreeBSD 8.2 and ZFS in all > partitions. Maybe that is the cause of mfsBSD hanging too? > I understand the guide I used to build the old server has been > deprecated. What's the recommended setup these days? I don't know -- AFAIK http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 is still accurate. __Martin From owner-freebsd-fs@FreeBSD.ORG Thu Apr 7 06:34:05 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 148141065670 for ; Thu, 7 Apr 2011 06:34:05 +0000 (UTC) (envelope-from tj@tjvarghese.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9CE678FC0A for ; Thu, 7 Apr 2011 06:34:04 +0000 (UTC) Received: by bwz12 with SMTP id 12so2223124bwz.13 for ; Wed, 06 Apr 2011 23:34:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.82.143 with SMTP id b15mr390534bkl.118.1302156687017; Wed, 06 Apr 2011 23:11:27 -0700 (PDT) Received: by 10.204.79.196 with HTTP; Wed, 6 Apr 2011 23:11:26 -0700 (PDT) In-Reply-To: <20110404185930.GA96734@DataIX.net> References: <20110401013603.GA31034@icarus.home.lan> <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> <1301911993.17884.4.camel@core.nessbank> <20110404185930.GA96734@DataIX.net> Date: Thu, 7 Apr 2011 14:11:26 +0800 Message-ID: From: TJ Varghese To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS failed after hard power off 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: Thu, 07 Apr 2011 06:34:05 -0000 > > > > FreeBSD 9-CURRENT should also have snapshots available that will have > ZFSv28 too! so relying on another OS is not entirely a must. At this > time the URL to where those are located is not available from my > location. Google ( site:ftp.freebsd.org snapshots ) for a list. > > > At present the ftp sites only have Jan snapshot ISOs/memstick images, which aren't on v28 yet. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 7 07:07:25 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 C74B2106564A for ; Thu, 7 Apr 2011 07:07:25 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 5BB498FC17 for ; Thu, 7 Apr 2011 07:07:25 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 7F711E6178; Thu, 7 Apr 2011 08:07:24 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=from:to :subject:date:cc:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; s=mail; bh=Y Q8ck61x9H7DiVcdS/oj1OVjXUs=; b=rkliuC40eT2dsA+7Fw+b3Twwjbcke+xQD ZuWERWJAX13ksXsCuAR2iKoq4cPfM0GLD34U1bmgoPcyfBTn5gQbxpIkueTvX2ra 23S5HzBdH6NiSdkb4KgBeNLvihbXvJN4ABQJyV2ljXCFp24ktq4+/6LpGuLtCLJM 3CFVjwWy9c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=from:to :subject:date:cc:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; q=dns; s= mail; b=SKyS+qXfW1W8XY2W2Z+dSFqSSYevdqXW41RPGJYXViEHgKW3sVXQbJ6q XTyvk2HOeTKErQE1WSO6nEar7MVRYMUX/Gcvq/0gXaSDsxk58DQUM+g/PAzbysre HL9BCiR+ZxY1t/wuKDBRqM66VSzMmbTsd7QvrFPYya0pGcJ5qXI= Received: from core.localnet (188-222-18-231.zone13.bethere.co.uk [188.222.18.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 680C0E6177; Thu, 7 Apr 2011 08:07:24 +0100 (BST) From: Bruce Cran To: freebsd-fs@freebsd.org Date: Thu, 7 Apr 2011 08:07:23 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.35-28-generic; KDE/4.5.1; x86_64; ; ) References: <20110404185930.GA96734@DataIX.net> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104070807.24017.bruce@cran.org.uk> Cc: TJ Varghese Subject: Re: ZFS failed after hard power off 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: Thu, 07 Apr 2011 07:07:25 -0000 On Thursday 07 Apr 2011 07:11:26 TJ Varghese wrote: > > FreeBSD 9-CURRENT should also have snapshots available that will have > > ZFSv28 too! so relying on another OS is not entirely a must. At this > > time the URL to where those are located is not available from my > > location. Google ( site:ftp.freebsd.org snapshots ) for a list. > > At present the ftp sites only have Jan snapshot ISOs/memstick images, which > aren't on v28 yet. You can get a copy of 8.2 with v28 from http://mfsbsd.vx.sk/ . -- Bruce Cran From owner-freebsd-fs@FreeBSD.ORG Thu Apr 7 17:01:46 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 BE3C9106566C; Thu, 7 Apr 2011 17:01:46 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9D95D8FC14; Thu, 7 Apr 2011 17:01:45 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA19790; Thu, 07 Apr 2011 20:01:43 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D9DEDF7.2070107@FreeBSD.org> Date: Thu, 07 Apr 2011 20:01:43 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.org, freebsd-fs@FreeBSD.org, freebsd-hardware@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: retry mounting with ro when rw fails 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: Thu, 07 Apr 2011 17:01:46 -0000 Guys, could you please review and comment on the following patch? http://people.freebsd.org/~avg/mount-retry-ro.diff Thank you! The patch consists of two parts. The first part is in CAM/SCSI to make sure that ENODEV is consistently returned to signal that an operation is not supported by a device (in accordance to intro(2)) and specifically to return ENODEV on write attempt to a read-only or write-protected media. Making this change in SCSI should cover real SCSI devices, as well as ATAPI through ahci/siis/atapicam or similar, plus majority (all?) of USB Mass Storage devices. The second part is in vfs_mount code. The idea is to re-try a mount call if we get the ENODEV error, and mounting was not already in read-only mode, and there was no explicit rw or noro option; the second try is changed to ro. I did only basic testing with an SD card in write-protected mode and a USB card-reader. Since I am not very familiar with vfs_mount code I might have missed some important details. A sample test log, just in case: ugen2.2: at usbus2 umass0: on usbus2 da0 at umass-sim0 bus 0 scbus7 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 488MB (1000448 512 byte sectors: 64H 32S/T 488C) da1 at umass-sim0 bus 0 scbus7 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da2 at umass-sim0 bus 0 scbus7 target 0 lun 2 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 scbus7 target 0 lun 3 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present GEOM: da0s1: EBR has non empty bootcode. (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 0 0 0 0 ea 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: DATA PROTECT csi:0,aa,55,61 asc:27,0 (Write protected) field replaceable unit: 1 g_vfs_done():da0s1[WRITE(offset=512, length=4096)]error = 19 (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 0 0 0 0 ea 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: DATA PROTECT csi:0,aa,55,61 asc:27,0 (Write protected) field replaceable unit: 1 g_vfs_done():da0s1[WRITE(offset=512, length=4096)]error = 19 vfs_donmount: R/W mount failed, possibly R/O media, falling back to R/O mount -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Thu Apr 7 17:25:13 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 3B92A1065689; Thu, 7 Apr 2011 17:25:13 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 557978FC0A; Thu, 7 Apr 2011 17:25:10 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA20232; Thu, 07 Apr 2011 20:25:09 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D9DF375.4080506@FreeBSD.org> Date: Thu, 07 Apr 2011 20:25:09 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.org, freebsd-fs@FreeBSD.org, FreeBSD Hackers X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: retry mounting with ro when rw fails 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: Thu, 07 Apr 2011 17:25:13 -0000 [sorry for double post, it should have been "hackers" not "hardware"] Guys, could you please review and comment on the following patch? http://people.freebsd.org/~avg/mount-retry-ro.diff Thank you! The patch consists of two parts. The first part is in CAM/SCSI to make sure that ENODEV is consistently returned to signal that an operation is not supported by a device (in accordance to intro(2)) and specifically to return ENODEV on write attempt to a read-only or write-protected media. Making this change in SCSI should cover real SCSI devices, as well as ATAPI through ahci/siis/atapicam or similar, plus majority (all?) of USB Mass Storage devices. The second part is in vfs_mount code. The idea is to re-try a mount call if we get the ENODEV error, and mounting was not already in read-only mode, and there was no explicit rw or noro option; the second try is changed to ro. I did only basic testing with an SD card in write-protected mode and a USB card-reader. Since I am not very familiar with vfs_mount code I might have missed some important details. A sample test log, just in case: ugen2.2: at usbus2 umass0: on usbus2 da0 at umass-sim0 bus 0 scbus7 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 488MB (1000448 512 byte sectors: 64H 32S/T 488C) da1 at umass-sim0 bus 0 scbus7 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da2 at umass-sim0 bus 0 scbus7 target 0 lun 2 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 scbus7 target 0 lun 3 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present GEOM: da0s1: EBR has non empty bootcode. (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 0 0 0 0 ea 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: DATA PROTECT csi:0,aa,55,61 asc:27,0 (Write protected) field replaceable unit: 1 g_vfs_done():da0s1[WRITE(offset=512, length=4096)]error = 19 (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 0 0 0 0 ea 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: DATA PROTECT csi:0,aa,55,61 asc:27,0 (Write protected) field replaceable unit: 1 g_vfs_done():da0s1[WRITE(offset=512, length=4096)]error = 19 vfs_donmount: R/W mount failed, possibly R/O media, falling back to R/O mount -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Thu Apr 7 17:42:50 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 4ACD6106564A for ; Thu, 7 Apr 2011 17:42:50 +0000 (UTC) (envelope-from sunpoet@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id D79A08FC15 for ; Thu, 7 Apr 2011 17:42:49 +0000 (UTC) Received: by fxm11 with SMTP id 11so2333483fxm.13 for ; Thu, 07 Apr 2011 10:42:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=EZwcahmE1X0PtQQuQiVUM7Y/zWdyYVuGe0MyqlohykY=; b=YFT8LsyzqDPjkZE5jSt+/u7XlcgmJaKyIxs5wdpxYKd/75Fx1Sq25axTWVOmenxqx/ YIyTy4oVOvS6+NRmveTiK/3geLowuFtUn+EubY2RH//l0J82TyFFvV7m2CfiDJlqkNS3 LE8Qw+KqBpwpjsBUysCWQ0F9RxT+BvBk4JfsU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=QoxWU3tFVmhsy814xEHN6WyYlIzZWMR1uzCWoCMLtfKnt3Vfp0w1CmChz4spiK4dhY cp18hb4Ne52Vq8B+QMNFsMUW2faoL5o6cjkm6rDomsBkbRUqz7pzIDTgUSrOJ5RQrbXR z8DSPES38+8pqAiqtZdktpHRTzp0Iq9vCGNhY= Received: by 10.223.66.70 with SMTP id m6mr1169332fai.34.1302196584213; Thu, 07 Apr 2011 10:16:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.79.11 with HTTP; Thu, 7 Apr 2011 10:16:04 -0700 (PDT) From: Sunpoet Hsieh Date: Fri, 8 Apr 2011 01:16:04 +0800 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [ZFS] fail to mount root from ZFS in ZFS-only booting 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: Thu, 07 Apr 2011 17:42:50 -0000 Howdy, I've done moving my machine from UFS to ZFS using mfsBSD (v28 special edition) [1]. It provides "zfsinstall" [2] script to simplify the steps. =C3=8D've compared it with other "Root on ZFS using GPT" documents [3][4] and they are compatible. I created zpool using 4 disks (ada0-ada3). However, it cannot boot from ZFS now. The zfs pool setting: - v28, raidz1 (ada0-ada3) - pool name: IRIS - ada*p1: gpart add -t freebsd-boot -s 128 ada*p2: gpart add -t freebsd-swap -s 2G ada*p3: gpart add -t freebsd-zfs - root: IRIS/root My steps are as follows: 1. Boot from mfsBSD mount -t cd9660 /dev/acd0 /cdrom zfsinstall -d ada0 -d ada1 -d ada2 -d ada3 -t /cdrom/8.2-RELEASE-amd64.tar.xz -s 2G -p IRIS remove the disc and boot from harddisk 2. update src tree (tag: RELENG_8) apply mm@'s v28 patch [5] make kernel, world and mergemaster gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0..ada3 shutdown, attach datadisk (UFS) and power on 3. build ports and restore configuration files shutdown, detach datadisk (UFS) and power on 4. move data back (from UFS) shutdown, detach datadisk (UFS) and power on 5. I cannot boot from ZFS now! The error message is: "Trying to mount root from zfs:IRIS/root start_init: trying /sbin/init" or "MOUNT FROM ERROR:" It seems the gptzfsboot fails to mount IRIS/root during boot process I've tried the following tests. 1. In the boot prompt, "lsdev" shows zfs0 2. boot from mfsBSD and "zpool import IRIS". It's OK. 3. zpool get bootfs IRIS0 the result is "IRIS/root". It's correct. 4. When "MOUNT FROM ERROR:" occurs, "?" lists ada[0-3], ada[0-3]p[0-2] and gptid/* but no zpool (IRIS). I have no idea what happened. Did I miss any steps to upgrade system? Does anyone know how to solve this problem? Thanks in advance!! Regards, sunpoet /boot/loader.conf: zfs_load=3D"YES" vfs.root.mountfrom=3D"zfs:IRIS/root" References: [1] http://mfsbsd.vx.sk/ http://mfsbsd.vx.sk/iso/mfsbsd-se-8.2-zfsv28-amd64.iso [2] http://box.vx.sk/wsvn/mfsbsd/trunk/tools/zfsinstall [3] http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 [4] http://www.keltia.net/howtos/zfsboot [5] http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20110317.= patch.xz From owner-freebsd-fs@FreeBSD.ORG Thu Apr 7 20:43:38 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 0E189106566B; Thu, 7 Apr 2011 20:43:38 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id D3DBA8FC15; Thu, 7 Apr 2011 20:43:37 +0000 (UTC) Received: by pvg11 with SMTP id 11so1297419pvg.13 for ; Thu, 07 Apr 2011 13:43:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JX+fEMf/0gprv0XxszezUm4x3vq6rUMb2kC0B7E8C8o=; b=Hzgbeo2qKBMWoeW/1vZKQfTQ7UTwU+Tqq/kaOHYRuYnPP87vcM36ltak931OBX/Kz/ FYn/KsOa7kg5mlyXYgmlTm/FcLjqWKSRGPlZCav5aKMFbH6hQKc0vA6BpLKtmV611ZeT oxZcueCen43LkNE0fd6sX0KfR7LlDYfttsKvo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=pwrrDY5AguWvPp5dhR77gMc9VYODZJL3d70dzgqdO5k+7OOaqCfkOqt9e4hkJuz5Yr ISW+fU725NeZKGpfO4wWE4XN/4SUsO+QwyZe64zvFFe7HHPOkiCBtJSn0H9NnmsJzp3S /6n2Mt6F1/5B8YI6RfyKRFLM7Dh5vjOFQ7wtY= MIME-Version: 1.0 Received: by 10.143.39.17 with SMTP id r17mr964391wfj.113.1302207653707; Thu, 07 Apr 2011 13:20:53 -0700 (PDT) Received: by 10.68.42.3 with HTTP; Thu, 7 Apr 2011 13:20:53 -0700 (PDT) In-Reply-To: <4D9DF375.4080506@FreeBSD.org> References: <4D9DF375.4080506@FreeBSD.org> Date: Thu, 7 Apr 2011 13:20:53 -0700 Message-ID: From: Garrett Cooper To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-scsi@freebsd.org, FreeBSD Hackers Subject: Re: retry mounting with ro when rw fails 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: Thu, 07 Apr 2011 20:43:38 -0000 On Thu, Apr 7, 2011 at 10:25 AM, Andriy Gapon wrote: > > [sorry for double post, it should have been "hackers" not "hardware"] > > Guys, > could you please review and comment on the following patch? > http://people.freebsd.org/~avg/mount-retry-ro.diff > Thank you! > > The patch consists of two parts. > > The first part is in CAM/SCSI to make sure that ENODEV is consistently re= turned to > signal that an operation is not supported by a device (in accordance to i= ntro(2)) > and specifically to return ENODEV on write attempt to a read-only or > write-protected media. =A0Making this change in SCSI should cover real SC= SI devices, > as well as ATAPI through ahci/siis/atapicam or similar, plus majority (al= l?) of > USB Mass Storage devices. > > The second part is in vfs_mount code. =A0The idea is to re-try a mount ca= ll if we > get the ENODEV error, and mounting was not already in read-only mode, and= there > was no explicit rw or noro option; the second try is changed to ro. > > I did only basic testing with an SD card in write-protected mode and a US= B > card-reader. =A0Since I am not very familiar with vfs_mount code I might = have missed > some important details. As a generic question / observation, maybe we should just implement 'errors=3Dremount-ro' (or a reasonable facsimile) like Linux has in our mount(8) command? Doesn't look like NetBSD, OpenBSD, or [Open]Solaris sported similar functionality. Thanks, -Garrett From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 00:00:33 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 41B30106567B for ; Fri, 8 Apr 2011 00:00:33 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by mx1.freebsd.org (Postfix) with ESMTP id 28CD08FC1F for ; Fri, 8 Apr 2011 00:00:33 +0000 (UTC) Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta01.emeryville.ca.mail.comcast.net with comcast id Uo0Y1g0031HpZEsA1o0YPn; Fri, 08 Apr 2011 00:00:32 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta14.emeryville.ca.mail.comcast.net with comcast id Uo0R1g00s1t3BNj8ao0S19; Fri, 08 Apr 2011 00:00:31 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7AEEB9B422; Thu, 7 Apr 2011 17:00:25 -0700 (PDT) Date: Thu, 7 Apr 2011 17:00:25 -0700 From: Jeremy Chadwick To: Garrett Cooper Message-ID: <20110408000025.GA16252@icarus.home.lan> References: <4D9DF375.4080506@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, freebsd-scsi@freebsd.org, Andriy Gapon , FreeBSD Hackers Subject: Re: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 00:00:33 -0000 On Thu, Apr 07, 2011 at 01:20:53PM -0700, Garrett Cooper wrote: > On Thu, Apr 7, 2011 at 10:25 AM, Andriy Gapon wrote: > > > > [sorry for double post, it should have been "hackers" not "hardware"] > > > > Guys, > > could you please review and comment on the following patch? > > http://people.freebsd.org/~avg/mount-retry-ro.diff > > Thank you! > > > > The patch consists of two parts. > > > > The first part is in CAM/SCSI to make sure that ENODEV is consistently returned to > > signal that an operation is not supported by a device (in accordance to intro(2)) > > and specifically to return ENODEV on write attempt to a read-only or > > write-protected media. ?Making this change in SCSI should cover real SCSI devices, > > as well as ATAPI through ahci/siis/atapicam or similar, plus majority (all?) of > > USB Mass Storage devices. > > > > The second part is in vfs_mount code. ?The idea is to re-try a mount call if we > > get the ENODEV error, and mounting was not already in read-only mode, and there > > was no explicit rw or noro option; the second try is changed to ro. > > > > I did only basic testing with an SD card in write-protected mode and a USB > > card-reader. ?Since I am not very familiar with vfs_mount code I might have missed > > some important details. > > As a generic question / observation, maybe we should just > implement 'errors=remount-ro' (or a reasonable facsimile) like Linux > has in our mount(8) command? Doesn't look like NetBSD, OpenBSD, or > [Open]Solaris sported similar functionality. I was going to recommend exactly this. :-) I like the idea of Andriy's patch, but would feel more comfortable if it were only used if a mount option was specified (-o errors=remount-ro"). Why: Are there any conditions where ENODEV is returned to the underlying vfs layer for things like unexpected hardware issues? I would imagine the latter would be ENXIO, but I'm not certain. An example situation: 1. User inserts USB flash drive/etc. 2. User tries to mount disk R/W manually 3. Weird/bizarre hardware issue happens mid-mount (drive falling off the bus, or maybe even the user yanking the drive right in the middle) -- could this ever return ENODEV? 4. Kernel attempts re-mount, which also fails, or possibly panics due to some underlying condition which nobody predicted 5. User mails mailing list If I'm worrying over nothing, then perfect. :-) My other concern is whether or not this mechanism change could caused some sort of "infinite loop" within devd(8)/devctl(4) where the daemon gets very confused as to what's going on or some automated commands get run when they shouldn't. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 02:16:46 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 DBAA81065670; Fri, 8 Apr 2011 02:16:45 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 76C1A8FC0A; Fri, 8 Apr 2011 02:16:45 +0000 (UTC) Received: by pwj8 with SMTP id 8so1425939pwj.13 for ; Thu, 07 Apr 2011 19:16:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kpT/2d4MXnsBu5MHzOKiNh1Wg0A3NsW/hoJOXYlrNoQ=; b=u73BnxZejx0aPjIJuOE2VXYFDjfY7Dl8AIFgcWQfsM8hhrbhZy3cpVEFpp5ouzNZ6e r76WL8aSf7Aou18dceFayW0xpUKF4O0uGP1QvQD/uM/j7Mpd0W5i7dgVUy/4npezERBH ldm/T/Mik9DRue+qNU4cZHhkBBfHBuOa7UjL4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VW8Jc1rPHHqFbpFm5oeR/3x/ep0w9jBF4iAcyJzK+U+Yuegletww0Q/RXvYplNnOmm a/tdWxK7ZZNaOrgifdmnorwot7KEXzKnvDzWsGj2GzMPam9/Sp8w/9vAeBmMzcIdnTUl AoS8HSIk3IWJz95c+MhPI6mooutKPxEQvAGlc= MIME-Version: 1.0 Received: by 10.143.24.39 with SMTP id b39mr1225326wfj.341.1302229004786; Thu, 07 Apr 2011 19:16:44 -0700 (PDT) Received: by 10.68.42.3 with HTTP; Thu, 7 Apr 2011 19:16:44 -0700 (PDT) In-Reply-To: <20110408000025.GA16252@icarus.home.lan> References: <4D9DF375.4080506@FreeBSD.org> <20110408000025.GA16252@icarus.home.lan> Date: Thu, 7 Apr 2011 19:16:44 -0700 Message-ID: From: Garrett Cooper To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-scsi@freebsd.org, Andriy Gapon , FreeBSD Hackers Subject: Re: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 02:16:46 -0000 On Thu, Apr 7, 2011 at 5:00 PM, Jeremy Chadwick wrote: > On Thu, Apr 07, 2011 at 01:20:53PM -0700, Garrett Cooper wrote: >> On Thu, Apr 7, 2011 at 10:25 AM, Andriy Gapon wrote: >> > >> > [sorry for double post, it should have been "hackers" not "hardware"] >> > >> > Guys, >> > could you please review and comment on the following patch? >> > http://people.freebsd.org/~avg/mount-retry-ro.diff >> > Thank you! >> > >> > The patch consists of two parts. >> > >> > The first part is in CAM/SCSI to make sure that ENODEV is consistently= returned to >> > signal that an operation is not supported by a device (in accordance t= o intro(2)) >> > and specifically to return ENODEV on write attempt to a read-only or >> > write-protected media. ?Making this change in SCSI should cover real S= CSI devices, >> > as well as ATAPI through ahci/siis/atapicam or similar, plus majority = (all?) of >> > USB Mass Storage devices. >> > >> > The second part is in vfs_mount code. ?The idea is to re-try a mount c= all if we >> > get the ENODEV error, and mounting was not already in read-only mode, = and there >> > was no explicit rw or noro option; the second try is changed to ro. >> > >> > I did only basic testing with an SD card in write-protected mode and a= USB >> > card-reader. ?Since I am not very familiar with vfs_mount code I might= have missed >> > some important details. >> >> =A0 =A0 As a generic question / observation, maybe we should just >> implement 'errors=3Dremount-ro' (or a reasonable facsimile) like Linux >> has in our mount(8) command? Doesn't look like NetBSD, OpenBSD, or >> [Open]Solaris sported similar functionality. > > I was going to recommend exactly this. =A0:-) > > I like the idea of Andriy's patch, but would feel more comfortable if it > were only used if a mount option was specified (-o errors=3Dremount-ro"). > Why: > > Are there any conditions where ENODEV is returned to the underlying vfs > layer for things like unexpected hardware issues? =A0I would imagine the > latter would be ENXIO, but I'm not certain. =A0An example situation: > > 1. User inserts USB flash drive/etc. > 2. User tries to mount disk R/W manually > 3. Weird/bizarre hardware issue happens mid-mount (drive falling off > =A0 the bus, or maybe even the user yanking the drive right in the > =A0 middle) -- could this ever return ENODEV? > 4. Kernel attempts re-mount, which also fails, or possibly panics > =A0 due to some underlying condition which nobody predicted > 5. User mails mailing list > > If I'm worrying over nothing, then perfect. =A0:-) =A0My other concern is > whether or not this mechanism change could caused some sort of "infinite > loop" within devd(8)/devctl(4) where the daemon gets very confused as to > what's going on or some automated commands get run when they shouldn't. Yeah. It seems like something else like EINVAL (just an example -- probably a bad one) would be better. Also, please be careful as returning ENODEV seems to be UFS-specific: The following errors can occur for a ufs file system mount: [ENODEV] A component of ufs_args fspec does not exist. Also, Tom Rhodes has a similar change to what I suggested on the backburner, but it hasn't been 100% fleshed out yet. Thanks, -Garrett From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 04:43:58 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 69359106566B for ; Fri, 8 Apr 2011 04:43:58 +0000 (UTC) (envelope-from dnewman@networktest.com) Received: from mail3.networktest.com (mail3.networktest.com [69.55.234.104]) by mx1.freebsd.org (Postfix) with ESMTP id 4777A8FC0C for ; Fri, 8 Apr 2011 04:43:58 +0000 (UTC) Received: from localhost (localhost [69.55.234.104]) by mail3.networktest.com (Postfix) with ESMTP id 3F2D32560D3 for ; Thu, 7 Apr 2011 21:43:58 -0700 (PDT) Received: from mail3.networktest.com ([69.55.234.104]) by localhost (mail3.networktest.com [69.55.234.104]) (amavisd-maia, port 10024) with ESMTP id 59648-02 for ; Thu, 7 Apr 2011 21:43:58 -0700 (PDT) Received: from sagan.local (cpe-76-95-196-192.socal.res.rr.com [76.95.196.192]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dnewman@networktest.com) by mail3.networktest.com (Postfix) with ESMTPSA id D22112560D2 for ; Thu, 7 Apr 2011 21:43:57 -0700 (PDT) Message-ID: <4D9E928C.5020109@networktest.com> Date: Thu, 07 Apr 2011 21:43:56 -0700 From: David Newman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4C51ECAA.2070707@networktest.com> <4C51FE41.8030906@FreeBSD.org> <4D941BFF.6050807@networktest.com> <4D973400.9060404@networktest.com> <201104041138.p34BckHS029801@higson.cam.lispworks.com> <4D9B6713.4050107@networktest.com> <201104061815.p36IFDUd024758@higson.cam.lispworks.com> In-Reply-To: <201104061815.p36IFDUd024758@higson.cam.lispworks.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: new ZFS install 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: Fri, 08 Apr 2011 04:43:58 -0000 On 4/6/11 11:15 AM, Martin Simmons wrote: >>>>>> On Tue, 05 Apr 2011 12:01:39 -0700, David Newman said: >> >> On 4/4/11 4:38 AM, Martin Simmons wrote: >>>>>>>> On Sat, 02 Apr 2011 07:34:40 -0700, David Newman said: >>>> >>>> I've tried booting from 8.1 and 8.2 mfsBSD ISOs but both hang at >>>> loader.conf. >>> >>> Have you tried the regular FreeBSD installation ISO? That doesn't know about >>> ZFS by default, but you can enter Fixit mode with "Use the live filesystem >>> CDROM/DVD" and load the modules using >>> >>> kldload /dist/boot/kernel/opensolaris.ko >>> kldload /dist/boot/kernel/zfs.ko >> >> Thanks, that did the trick, along with repairing the boot records on >> each disk. > > Good -- though it is strange the mfsBSD hung. Does it still hang, now that > you have repaired the system? > > >> This server is showing some evidence of flaky hardware, and I'm looking >> to move its data onto a new server running FreeBSD 8.2 and ZFS in all >> partitions. > > Maybe that is the cause of mfsBSD hanging too? > > >> I understand the guide I used to build the old server has been >> deprecated. What's the recommended setup these days? > > I don't know -- AFAIK http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 is > still accurate. Thanks. Yes, bum hardware was the culprit. That guide has worked well for me in the past. The only gotcha is that upgrading between versions using freebsd-update clobbers the boot records on each disk, and requires repair. Not a big deal but I have to remember this issue each time a new release comes out. dn > > __Martin > _______________________________________________ > 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" From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 11:45:40 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 5238B106566B; Fri, 8 Apr 2011 11:45:40 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 63A218FC1B; Fri, 8 Apr 2011 11:45:38 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA05250; Fri, 08 Apr 2011 14:45:32 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D9EF55C.5070300@FreeBSD.org> Date: Fri, 08 Apr 2011 14:45:32 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Jeremy Chadwick References: <4D9DF375.4080506@FreeBSD.org> <20110408000025.GA16252@icarus.home.lan> In-Reply-To: <20110408000025.GA16252@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , freebsd-fs@FreeBSD.org, FreeBSD Hackers Subject: Re: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 11:45:40 -0000 on 08/04/2011 03:00 Jeremy Chadwick said the following: > On Thu, Apr 07, 2011 at 01:20:53PM -0700, Garrett Cooper wrote: >> On Thu, Apr 7, 2011 at 10:25 AM, Andriy Gapon wrote: >>> >>> [sorry for double post, it should have been "hackers" not "hardware"] >>> >>> Guys, >>> could you please review and comment on the following patch? >>> http://people.freebsd.org/~avg/mount-retry-ro.diff >>> Thank you! >>> >>> The patch consists of two parts. >>> >>> The first part is in CAM/SCSI to make sure that ENODEV is consistently returned to >>> signal that an operation is not supported by a device (in accordance to intro(2)) >>> and specifically to return ENODEV on write attempt to a read-only or >>> write-protected media. ?Making this change in SCSI should cover real SCSI devices, >>> as well as ATAPI through ahci/siis/atapicam or similar, plus majority (all?) of >>> USB Mass Storage devices. >>> >>> The second part is in vfs_mount code. ?The idea is to re-try a mount call if we >>> get the ENODEV error, and mounting was not already in read-only mode, and there >>> was no explicit rw or noro option; the second try is changed to ro. >>> >>> I did only basic testing with an SD card in write-protected mode and a USB >>> card-reader. ?Since I am not very familiar with vfs_mount code I might have missed >>> some important details. >> >> As a generic question / observation, maybe we should just >> implement 'errors=remount-ro' (or a reasonable facsimile) like Linux >> has in our mount(8) command? Doesn't look like NetBSD, OpenBSD, or >> [Open]Solaris sported similar functionality. > > I was going to recommend exactly this. :-) > > I like the idea of Andriy's patch, but would feel more comfortable if it > were only used if a mount option was specified (-o errors=remount-ro"). Having the option is appealing, but my main motivation was the simplicity that comes from having that enabled by default. That is, you absolutely want an R/W mount then use -o rw, you need R/O then explicitly -o ro, you "just want" to get that media mounted then the default behavior tries its best. > Why: > > Are there any conditions where ENODEV is returned to the underlying vfs > layer for things like unexpected hardware issues? I would imagine the > latter would be ENXIO, but I'm not certain. An example situation: > > 1. User inserts USB flash drive/etc. > 2. User tries to mount disk R/W manually > 3. Weird/bizarre hardware issue happens mid-mount (drive falling off > the bus, or maybe even the user yanking the drive right in the > middle) -- could this ever return ENODEV? It shouldn't. If that happens then the underlying layers should be fixed. > 4. Kernel attempts re-mount, which also fails, or possibly panics > due to some underlying condition which nobody predicted > 5. User mails mailing list > > If I'm worrying over nothing, then perfect. :-) My other concern is > whether or not this mechanism change could caused some sort of "infinite > loop" within devd(8)/devctl(4) where the daemon gets very confused as to > what's going on or some automated commands get run when they shouldn't. I can't see how that can happen. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 11:48:36 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 E82DB1065676; Fri, 8 Apr 2011 11:48:36 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 05ED38FC17; Fri, 8 Apr 2011 11:48:35 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA05282; Fri, 08 Apr 2011 14:48:31 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D9EF60F.1010704@FreeBSD.org> Date: Fri, 08 Apr 2011 14:48:31 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Garrett Cooper References: <4D9DF375.4080506@FreeBSD.org> <20110408000025.GA16252@icarus.home.lan> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, FreeBSD Hackers Subject: Re: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 11:48:37 -0000 on 08/04/2011 05:16 Garrett Cooper said the following: > Yeah. It seems like something else like EINVAL (just an example -- > probably a bad one) would be better. Also, please be careful as > returning ENODEV seems to be UFS-specific: I wonder how you arrived at that conclusion. See intro(2) or grep the sources. > > The following errors can occur for a ufs file system mount: > > [ENODEV] A component of ufs_args fspec does not exist. That documented specific use of ENODEV in UFS doesn't make ENODEV UFS-specific. Besides I don't ENODEV anywhere under sys/ufs. > Also, Tom Rhodes has a similar change to what I suggested on the > backburner, but it hasn't been 100% fleshed out yet. I like that approach too. It has its advantages. But I don't give up yet on my suggestion. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 12:11:06 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 250A61065674; Fri, 8 Apr 2011 12:11:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 37B2B8FC15; Fri, 8 Apr 2011 12:11:04 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA05618; Fri, 08 Apr 2011 15:11:01 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D9EFB55.1000706@FreeBSD.org> Date: Fri, 08 Apr 2011 15:11:01 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Garrett Cooper References: <4D9DF375.4080506@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, FreeBSD Hackers Subject: Re: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 12:11:06 -0000 on 07/04/2011 23:20 Garrett Cooper said the following: > > As a generic question / observation, maybe we should just > implement 'errors=remount-ro' (or a reasonable facsimile) like Linux > has in our mount(8) command? Doesn't look like NetBSD, OpenBSD, or > [Open]Solaris sported similar functionality. No problem, I am OK with being first. Then, I only want to deal with media that is "semi-permanently" or permanetly read-only. That's why I handle only failure to mount media as R/W. But from what I read 'errors=remount-ro' in Linux has to do with errors that happen after filesystem is mounted. That is, you mounted a filesystem, you work with it, you get some error (e.g. because of bad blocks), you auto-downgrade the filesystem to readonly. This may be a nice feature, but this is something different from what I proposed. And, AFAIK, Linux does what I propose by default, without any additional options. Google for "block device ... is write-protected, mounting read-only". But yes, it seems that they handle this situation entirely in userland. And I am not against it. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 12:20:23 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 E78DE1065673; Fri, 8 Apr 2011 12:20:23 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by mx1.freebsd.org (Postfix) with ESMTP id 83EBE8FC12; Fri, 8 Apr 2011 12:20:23 +0000 (UTC) Received: from c122-106-155-58.carlnfd1.nsw.optusnet.com.au (c122-106-155-58.carlnfd1.nsw.optusnet.com.au [122.106.155.58]) by mail08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p38CKJ8w026370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2011 22:20:20 +1000 Date: Fri, 8 Apr 2011 22:20:19 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Andriy Gapon In-Reply-To: <4D9EF55C.5070300@FreeBSD.org> Message-ID: <20110408214920.I1265@besplex.bde.org> References: <4D9DF375.4080506@FreeBSD.org> <20110408000025.GA16252@icarus.home.lan> <4D9EF55C.5070300@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Garrett Cooper , freebsd-fs@freebsd.org, FreeBSD Hackers Subject: Re: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 12:20:24 -0000 On Fri, 8 Apr 2011, Andriy Gapon wrote: > on 08/04/2011 03:00 Jeremy Chadwick said the following: >> On Thu, Apr 07, 2011 at 01:20:53PM -0700, Garrett Cooper wrote: >>> As a generic question / observation, maybe we should just >>> implement 'errors=remount-ro' (or a reasonable facsimile) like Linux >>> has in our mount(8) command? Doesn't look like NetBSD, OpenBSD, or >>> [Open]Solaris sported similar functionality. >> >> I was going to recommend exactly this. :-) >> >> I like the idea of Andriy's patch, but would feel more comfortable if it >> were only used if a mount option was specified (-o errors=remount-ro"). > > Having the option is appealing, but my main motivation was the simplicity that > comes from having that enabled by default. > That is, you absolutely want an R/W mount then use -o rw, you need R/O then > explicitly -o ro, you "just want" to get that media mounted then the default > behavior tries its best. But the default behaviour is backwards, especially for read-mostly removable media. The default should be ro, possibly with an automagic upgrade to rw iff the media really needs to be written too. Writing timestamps for file system and inode access times doesn't count as "really needs to be written to". I think I prefer requiring an explicit upgrade to rw. rw implies writing access times unless you also use noatime, and I wouldn't want noatime to be set automagically depending on whether rw is set explicitly, so I would want noatime to be set explicitly, and once you do that then you can easily set rw or ro at the same time. A new rm (read mostly) or "rwa" (read or write automagically) flag could give automatic upgrade from ro to rw. I'd also like automatic downgrade to ro after a file system has not been written to for some time (this would avoid fscks in most cases for read-mostly file systems. The ro flag should be per-cylinder-group in ffs so that on big disks, most parts are read-only most of the time and don't need to be checked). Bruce From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 12:43:41 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 7D02C106564A for ; Fri, 8 Apr 2011 12:43:41 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [193.34.186.230]) by mx1.freebsd.org (Postfix) with ESMTP id 169318FC08 for ; Fri, 8 Apr 2011 12:43:40 +0000 (UTC) Received: from higson.cam.lispworks.com (higson [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.3/8.14.3) with ESMTP id p38ChXxm093071; Fri, 8 Apr 2011 13:43:33 +0100 (BST) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id p38ChWnL011027; Fri, 8 Apr 2011 13:43:33 +0100 Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id p38ChWtp011023; Fri, 8 Apr 2011 13:43:32 +0100 Date: Fri, 8 Apr 2011 13:43:32 +0100 Message-Id: <201104081243.p38ChWtp011023@higson.cam.lispworks.com> From: Martin Simmons To: freebsd-fs@freebsd.org In-reply-to: <4D9E928C.5020109@networktest.com> (message from David Newman on Thu, 07 Apr 2011 21:43:56 -0700) References: <4C51ECAA.2070707@networktest.com> <4C51FE41.8030906@FreeBSD.org> <4D941BFF.6050807@networktest.com> <4D973400.9060404@networktest.com> <201104041138.p34BckHS029801@higson.cam.lispworks.com> <4D9B6713.4050107@networktest.com> <201104061815.p36IFDUd024758@higson.cam.lispworks.com> <4D9E928C.5020109@networktest.com> Subject: Re: new ZFS install 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: Fri, 08 Apr 2011 12:43:41 -0000 >>>>> On Thu, 07 Apr 2011 21:43:56 -0700, David Newman said: > > That guide has worked well for me in the past. The only gotcha is that > upgrading between versions using freebsd-update clobbers the boot > records on each disk, and requires repair. Not a big deal but I have to > remember this issue each time a new release comes out. I'm rather surprised that it clobbers the boot records. __Martin From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 12:48:58 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 A1E3F106566B for ; Fri, 8 Apr 2011 12:48:58 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3C10B8FC15 for ; Fri, 8 Apr 2011 12:48:57 +0000 (UTC) Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKTZ8EOSNVMk/GEKtw0FArl9VC+NI3+I1Y@postini.com; Fri, 08 Apr 2011 05:48:58 PDT Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 8 Apr 2011 05:34:50 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 8 Apr 2011 08:36:35 -0400 From: Andrew Duane To: Bruce Evans , Andriy Gapon Date: Fri, 8 Apr 2011 08:36:33 -0400 Thread-Topic: retry mounting with ro when rw fails Thread-Index: Acv15/dwjMS1LW5+RZe5mMMKTZtQ9gAAMwHw Message-ID: References: <4D9DF375.4080506@FreeBSD.org> <20110408000025.GA16252@icarus.home.lan> <4D9EF55C.5070300@FreeBSD.org> <20110408214920.I1265@besplex.bde.org> In-Reply-To: <20110408214920.I1265@besplex.bde.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Garrett Cooper , "freebsd-fs@freebsd.org" , FreeBSD, Hackers Subject: RE: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 12:48:58 -0000 I had been letting this discussion settle a little bit before jumping in, b= ut we've done some work in this area for a few of our platforms. The work w= as rather ham-fisted, but I've been looking for a way to try to get it clea= ned up and back to FreeBSD. Basically, we have a way of detecting that our disk is physically write-pro= tected, a pretty common scenario. Given that, I made some surgical changes = to the mount path to prevent read-write mounts of the disk at all. You can'= t allow that, because even attempts to update the superblock or timestamp w= ill fail and leave buffers outstanding. Over time, this eventually panics t= he system. My implementation simply drops the read-write flag and mounts th= e FS readonly, rather than return a failure (which stopped the startup RC s= cripts). What I was hoping to do was design a better mechanism for passing that R/O = detection from the device to the filesystem code. Our implementation uses a= platform sysctl that checks the incoming device name against some hardware= or software settings. Ick. I don't know enough about device/GEOM calls to = do it better though. =A0................................... Andrew Duane Juniper Networks o=A0=A0=A0+1 978 589 0551 m=A0 +1 603-770-7088 aduane@juniper.net =A0 -----Original Message----- From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd-hackers@freeb= sd.org] On Behalf Of Bruce Evans Sent: Friday, April 08, 2011 8:20 AM To: Andriy Gapon Cc: Garrett Cooper; freebsd-fs@freebsd.org; Jeremy Chadwick; FreeBSD Hacker= s Subject: Re: retry mounting with ro when rw fails On Fri, 8 Apr 2011, Andriy Gapon wrote: > on 08/04/2011 03:00 Jeremy Chadwick said the following: >> On Thu, Apr 07, 2011 at 01:20:53PM -0700, Garrett Cooper wrote: >>> As a generic question / observation, maybe we should just >>> implement 'errors=3Dremount-ro' (or a reasonable facsimile) like Linux >>> has in our mount(8) command? Doesn't look like NetBSD, OpenBSD, or >>> [Open]Solaris sported similar functionality. >> >> I was going to recommend exactly this. :-) >> >> I like the idea of Andriy's patch, but would feel more comfortable if it >> were only used if a mount option was specified (-o errors=3Dremount-ro")= . > > Having the option is appealing, but my main motivation was the simplicity= that > comes from having that enabled by default. > That is, you absolutely want an R/W mount then use -o rw, you need R/O th= en > explicitly -o ro, you "just want" to get that media mounted then the defa= ult > behavior tries its best. But the default behaviour is backwards, especially for read-mostly removable media. The default should be ro, possibly with an automagic upgrade to rw iff the media really needs to be written too. Writing timestamps for file system and inode access times doesn't count as "really needs to be written to". I think I prefer requiring an explicit upgrade to rw. rw implies writing access times unless you also use noatime, and I wouldn't want noatime to be set automagically depending on whether rw is set explicitly, so I would want noatime to be set explicitly, and once you do that then you can easily set rw or ro at the same time. A new rm (read mostly) or "rwa" (read or write automagically) flag could give automatic upgrade from ro to rw. I'd also like automatic downgrade to ro after a file system has not been written to for some time (this would avoid fscks in most cases for read-mostly file systems. The ro flag should be per-cylinder-group in ffs so that on big disks, most parts are read-only most of the time and don't need to be checked). Bruce _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 15:20:51 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 44EA51065670; Fri, 8 Apr 2011 15:20:51 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5E47C8FC0A; Fri, 8 Apr 2011 15:20:49 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA07956; Fri, 08 Apr 2011 18:20:35 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D9F27C3.5030306@FreeBSD.org> Date: Fri, 08 Apr 2011 18:20:35 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Bruce Evans References: <4D9DF375.4080506@FreeBSD.org> <20110408000025.GA16252@icarus.home.lan> <4D9EF55C.5070300@FreeBSD.org> <20110408214920.I1265@besplex.bde.org> In-Reply-To: <20110408214920.I1265@besplex.bde.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, FreeBSD Hackers Subject: Re: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 15:20:51 -0000 on 08/04/2011 15:20 Bruce Evans said the following: > But the default behaviour is backwards, especially for read-mostly > removable media. The default should be ro, possibly with an automagic > upgrade to rw iff the media really needs to be written too. Writing > timestamps for file system and inode access times doesn't count as > "really needs to be written to". > > I think I prefer requiring an explicit upgrade to rw. rw implies > writing access times unless you also use noatime, and I wouldn't want > noatime to be set automagically depending on whether rw is set explicitly, > so I would want noatime to be set explicitly, and once you do that > then you can easily set rw or ro at the same time. A new rm (read mostly) > or "rwa" (read or write automagically) flag could give automatic upgrade > from ro to rw. I'd also like automatic downgrade to ro after a file > system has not been written to for some time (this would avoid fscks > in most cases for read-mostly file systems. The ro flag should be > per-cylinder-group in ffs so that on big disks, most parts are read-only > most of the time and don't need to be checked). This is a very good idea, I would like to get that too, but it's a bit more work than the "auto"-mounting. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 15:23:43 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 7BF8E106567D; Fri, 8 Apr 2011 15:23:43 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D9CB08FC16; Fri, 8 Apr 2011 15:23:41 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA07973; Fri, 08 Apr 2011 18:23:24 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D9F286B.4010102@FreeBSD.org> Date: Fri, 08 Apr 2011 18:23:23 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Andrew Duane References: <4D9DF375.4080506@FreeBSD.org> <20110408000025.GA16252@icarus.home.lan> <4D9EF55C.5070300@FreeBSD.org> <20110408214920.I1265@besplex.bde.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: "freebsd-fs@freebsd.org" , FreeBSD Hackers , freebsd-scsi@FreeBSD.org Subject: Re: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 15:23:43 -0000 on 08/04/2011 15:36 Andrew Duane said the following: > What I was hoping to do was design a better mechanism for passing that R/O > detection from the device to the filesystem code. Our implementation uses a > platform sysctl that checks the incoming device name against some hardware or > software settings. Ick. I don't know enough about device/GEOM calls to do it > better though. I am actually not aware of any way to inquiry write-protection status from hardware. There are distinct SCSI sense codes for that, but you get them only after a failed write attempt. But there are many things that I don't know about... -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Apr 8 16:47:20 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 4F3E7106568A; Fri, 8 Apr 2011 16:47:20 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by mx1.freebsd.org (Postfix) with ESMTP id C8D278FC16; Fri, 8 Apr 2011 16:47:13 +0000 (UTC) Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTZ88EFo/4nuoeLgyiOrLkJ9ea9lbxtpc@postini.com; Fri, 08 Apr 2011 09:47:19 PDT Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 8 Apr 2011 09:43:39 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 8 Apr 2011 12:45:24 -0400 From: Andrew Duane To: Andriy Gapon Date: Fri, 8 Apr 2011 12:45:23 -0400 Thread-Topic: retry mounting with ro when rw fails Thread-Index: Acv2AO1qThMsSukkTE2FDMO0vOVbogAC01og Message-ID: References: <4D9DF375.4080506@FreeBSD.org> <20110408000025.GA16252@icarus.home.lan> <4D9EF55C.5070300@FreeBSD.org> <20110408214920.I1265@besplex.bde.org> <4D9F286B.4010102@FreeBSD.org> In-Reply-To: <4D9F286B.4010102@FreeBSD.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-fs@freebsd.org" , FreeBSD Hackers , "freebsd-scsi@FreeBSD.org" Subject: RE: retry mounting with ro when rw fails 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: Fri, 08 Apr 2011 16:47:20 -0000 For SCSI-attached disks, yes. But other hardware has write-protect sensing = (SD cards, CD-roms, our platform). So if you can do that, you should Cleaning up after a failed write is a real problem, one that I needed to av= oid.=20 /Andrew =20 -----Original Message----- From: Andriy Gapon [mailto:avg@FreeBSD.org]=20 Sent: Friday, April 08, 2011 11:23 AM To: Andrew Duane Cc: Bruce Evans; freebsd-fs@freebsd.org; FreeBSD Hackers; freebsd-scsi@Free= BSD.org Subject: Re: retry mounting with ro when rw fails on 08/04/2011 15:36 Andrew Duane said the following: > What I was hoping to do was design a better mechanism for passing that R/= O > detection from the device to the filesystem code. Our implementation uses= a > platform sysctl that checks the incoming device name against some hardwar= e or > software settings. Ick. I don't know enough about device/GEOM calls to do= it > better though. I am actually not aware of any way to inquiry write-protection status from hardware. There are distinct SCSI sense codes for that, but you get them o= nly after a failed write attempt. But there are many things that I don't know about... --=20 Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 16:49:02 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 1F2D0106566B for ; Sat, 9 Apr 2011 16:49:02 +0000 (UTC) (envelope-from cforgeron@acsi.ca) Received: from mta04.eastlink.ca (mta04.eastlink.ca [24.224.136.10]) by mx1.freebsd.org (Postfix) with ESMTP id DD2DB8FC0A for ; Sat, 9 Apr 2011 16:49:01 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from ip06.eastlink.ca ([unknown] [24.222.39.84]) by mta04.eastlink.ca (Sun Java(tm) System Messaging Server 7.3-11.01 64bit (built Sep 1 2009)) with ESMTP id <0LJE00H3O9DO8D22@mta04.eastlink.ca> for freebsd-fs@freebsd.org; Sat, 09 Apr 2011 13:49:00 -0300 (ADT) X-CMAE-Score: 0 X-CMAE-Analysis: v=1.1 cv=mORQtGzMSGJSBwuMSvVfB0MKjPGmXehAuj88Uvu04o4= c=1 sm=1 a=IkcTkHD0fZMA:10 a=6I5d2MoRAAAA:8 a=SXEu0QIm4NJrHHTi4m4A:9 a=QEXdDO2ut3YA:10 a=hwXlaahgGAwA:10 a=12M4PSijgPY/TTHpO+5bpg==:117 Received: from blk-222-10-85.eastlink.ca (HELO server7.acsi.ca) ([24.222.10.85]) by ip06.eastlink.ca with ESMTP; Sat, 09 Apr 2011 13:48:57 -0300 Received: from server7.acsi.ca ([192.168.9.7]) by server7.acsi.ca ([192.168.9.7]) with mapi; Sat, 09 Apr 2011 13:48:56 -0300 From: Chris Forgeron To: Freddie Cash , =?utf-8?B?THVrYXMgUsO2c3NsZXI=?= Date: Sat, 09 Apr 2011 13:48:56 -0300 Thread-topic: zfs porting roadmap? Thread-index: Acvy86k15gEj1Wx9RQuWwbgn3UURWAD4IYRQ Message-id: References: <4D99DDB0.9090307@googlemail.com> <20110404165759.GA2007@garage.freebsd.pl> <4D9A0856.40709@googlemail.com> In-reply-to: Accept-Language: en-US Content-language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Cc: "freebsd-fs@freebsd.org" Subject: RE: zfs porting roadmap? 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: Sat, 09 Apr 2011 16:49:02 -0000 Yes, hopefully pjd, mm, and some of the other FreeBSD contributors are in that secret working group. I was impressed with Solaris during the few months that I was running it as my primary ZFS OS, but I'd prefer to see ZFS mutate into something less OS specific, for easier future porting. I was the thread starter on OpenSolaris, because I was concerned about ZFS development after speaking with a few other ex-Oracle people who couldn't see anything happening in the open-source side of ZFS. It appears the group is secret enough that even Sun/Oracle employees who had put code into ZFS didn't know about it. :-) Hopefully that fact that it exists is more open now, and more of those developers can join. I'm sure it will become open to the public fairly soon - I can understand their need to keep it semi-private at the moment. We all run ZFS and have a lot of opinions about it, but only a very small number of us will put in the time to develop solid code for it. Too many opinions means nothing will get done. Lukas: Why don't you enable encryption via geom; http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html - You can make the geom disks the base that you feed to ZFS. One of the tasty things in v31 is mirrored copies of metadata, allowing for striped read access to that data. I believe they were quoting 15% increase in metadata access speed. From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 19:34:19 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AED4106566B; Sat, 9 Apr 2011 19:34:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 313608FC0C; Sat, 9 Apr 2011 19:34:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p39JYJSF002006; Sat, 9 Apr 2011 19:34:19 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p39JYJ8a002002; Sat, 9 Apr 2011 19:34:19 GMT (envelope-from linimon) Date: Sat, 9 Apr 2011 19:34:19 GMT Message-Id: <201104091934.p39JYJ8a002002@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/155940: [libzfs] [patch] zfs list /filesystem does not work. 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: Sat, 09 Apr 2011 19:34:19 -0000 Old Synopsis: zfs list /filesystem does not work. New Synopsis: [libzfs] [patch] zfs list /filesystem does not work. Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Apr 9 19:34:06 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=155940 From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 19:51:04 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDA651065675; Sat, 9 Apr 2011 19:51:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B32D98FC0C; Sat, 9 Apr 2011 19:51:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p39Jp4bV017823; Sat, 9 Apr 2011 19:51:04 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p39Jp49C017814; Sat, 9 Apr 2011 19:51:04 GMT (envelope-from linimon) Date: Sat, 9 Apr 2011 19:51:04 GMT Message-Id: <201104091951.p39Jp49C017814@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/156039: [nullfs] [unionfs] nullfs + unionfs do not compose, result in unlocking unlocked lock 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: Sat, 09 Apr 2011 19:51:05 -0000 Old Synopsis: nullfs + unionfs do not compose, result in unlocking unlocked lock New Synopsis: [nullfs] [unionfs] nullfs + unionfs do not compose, result in unlocking unlocked lock Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Apr 9 19:50:48 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=156039 From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 19:59:49 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1188010656D8; Sat, 9 Apr 2011 19:59:49 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DBC3C8FC13; Sat, 9 Apr 2011 19:59:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p39JxmIv019911; Sat, 9 Apr 2011 19:59:48 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p39Jxmxp019907; Sat, 9 Apr 2011 19:59:48 GMT (envelope-from linimon) Date: Sat, 9 Apr 2011 19:59:48 GMT Message-Id: <201104091959.p39Jxmxp019907@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/156168: [nfs] [panic] Kernel panic under concurrent access over NFS 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: Sat, 09 Apr 2011 19:59:49 -0000 Old Synopsis: Kernel panic under concurrent access over NFS New Synopsis: [nfs] [panic] Kernel panic under concurrent access over NFS Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Apr 9 19:59:33 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=156168 From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 20:00:33 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D55301065673; Sat, 9 Apr 2011 20:00:33 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AB65B8FC1B; Sat, 9 Apr 2011 20:00:33 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p39K0Xuo020147; Sat, 9 Apr 2011 20:00:33 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p39K0XZJ020143; Sat, 9 Apr 2011 20:00:33 GMT (envelope-from linimon) Date: Sat, 9 Apr 2011 20:00:33 GMT Message-Id: <201104092000.p39K0XZJ020143@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/156177: [fdescfs] [patch] linuxulator + fdescfs panic 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: Sat, 09 Apr 2011 20:00:33 -0000 Old Synopsis: [patch] linuxulator + fdescfs panic New Synopsis: [fdescfs] [patch] linuxulator + fdescfs panic Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Apr 9 19:59:57 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=156177 From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 20:01:17 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 626721065672; Sat, 9 Apr 2011 20:01:17 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 384648FC1A; Sat, 9 Apr 2011 20:01:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p39K1Hf8024498; Sat, 9 Apr 2011 20:01:17 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p39K1H7u024485; Sat, 9 Apr 2011 20:01:17 GMT (envelope-from linimon) Date: Sat, 9 Apr 2011 20:01:17 GMT Message-Id: <201104092001.p39K1H7u024485@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/156193: [ufs] [hang] UFS snapshot hangs && deadlocks processes 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: Sat, 09 Apr 2011 20:01:17 -0000 Old Synopsis: UFS snapshot hangs && deadlocks processes New Synopsis: [ufs] [hang] UFS snapshot hangs && deadlocks processes Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Apr 9 20:01:05 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=156193 From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 20:10:12 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5A7510656E0; Sat, 9 Apr 2011 20:10:12 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BC1F98FC25; Sat, 9 Apr 2011 20:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p39KACdc029147; Sat, 9 Apr 2011 20:10:12 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p39KACms029143; Sat, 9 Apr 2011 20:10:12 GMT (envelope-from linimon) Date: Sat, 9 Apr 2011 20:10:12 GMT Message-Id: <201104092010.p39KACms029143@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/156241: [zfs] 'zfs send' does not prevents disks to suspend if no other activity 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: Sat, 09 Apr 2011 20:10:13 -0000 Old Synopsis: 'zfs send' does not prevents disks to suspend if no other activity New Synopsis: [zfs] 'zfs send' does not prevents disks to suspend if no other activity Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Apr 9 20:09:50 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=156241 From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 20:32:52 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 1E4D1106566C for ; Sat, 9 Apr 2011 20:32:52 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id A7B008FC08 for ; Sat, 9 Apr 2011 20:32:51 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id C725CE61AA for ; Sat, 9 Apr 2011 21:32:50 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=date:from :to:subject:message-id:mime-version:content-type :content-transfer-encoding; s=mail; bh=x7oGP0BKx+Oq94i+Zx4qT2agw Dg=; b=s+97oU+XoEpqJkUtROq9e0+hR++fH3E7U5UqI591r0NjuTgvb36H72Bt9 amFjdtMV//HzYzGqZ6hknz79aV8GYFul8Bpga62073k8VdTPxBhJYVW4HTmxBcSa E9UvHM/f0bIGS0d9TojmutaQevNfN3+98wn6LW9cSsGS3t4hBM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=date:from:to :subject:message-id:mime-version:content-type :content-transfer-encoding; q=dns; s=mail; b=VZRLFblosIc94Mb8KEk tZH/+EAG8mnvo8cXw7igZMjVYGKHeEHwYdZKx3UyBySF4pwvg0QkZo8RtCxVikoy X4/03mps7PIJ309cmU403p5ZvC1ZphuoV0v3p2OIXoDdB/gd5hzvb9foRp8th1ZV q8+R/2PNHXm6ayzIbP8yeWOc= Received: from unknown (188-222-18-231.zone13.bethere.co.uk [188.222.18.231]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 8C131E61A9 for ; Sat, 9 Apr 2011 21:32:50 +0100 (BST) Date: Sat, 9 Apr 2011 21:32:50 +0100 From: Bruce Cran To: freebsd-fs@freebsd.org Message-ID: <20110409213250.00007ea9@unknown> X-Mailer: Claws Mail 3.7.8cvs9 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Booting from freebsd-boot on gpt using zfs root on mbr 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: Sat, 09 Apr 2011 20:32:52 -0000 Hi, I'm trying to boot from gpt but with the zfs root on a mbr disk so I can avoid overwriting the mbr bootcode on ada0. The layout is: ada0s4: freebsd-zfs 80 GB (zroot) ada1p1: freebsd-boot 128 kB When I enter "zroot:/boot/kernel/kernel" at the boot: prompt I get a register dump followed by "BTX halted". Is there some way to get this configuration to work? -- Bruce Cran From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 21:47:45 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A94B1065676; Sat, 9 Apr 2011 21:47:45 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F53B8FC08; Sat, 9 Apr 2011 21:47:45 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p39Lljhw020095; Sat, 9 Apr 2011 21:47:45 GMT (envelope-from kib@freefall.freebsd.org) Received: (from kib@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p39LljVT020090; Sat, 9 Apr 2011 21:47:45 GMT (envelope-from kib) Date: Sat, 9 Apr 2011 21:47:45 GMT Message-Id: <201104092147.p39LljVT020090@freefall.freebsd.org> To: vladislav.movchan@gmail.com, kib@FreeBSD.org, freebsd-fs@FreeBSD.org, kib@FreeBSD.org From: kib@FreeBSD.org Cc: Subject: Re: kern/156177: [fdescfs] [patch] linuxulator + fdescfs panic 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: Sat, 09 Apr 2011 21:47:45 -0000 Synopsis: [fdescfs] [patch] linuxulator + fdescfs panic State-Changed-From-To: open->patched State-Changed-By: kib State-Changed-When: Sat Apr 9 21:47:15 UTC 2011 State-Changed-Why: Patched in HEAD. Responsible-Changed-From-To: freebsd-fs->kib Responsible-Changed-By: kib Responsible-Changed-When: Sat Apr 9 21:47:15 UTC 2011 Responsible-Changed-Why: Patched in HEAD. http://www.freebsd.org/cgi/query-pr.cgi?pr=156177 From owner-freebsd-fs@FreeBSD.ORG Sat Apr 9 21:06:01 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 CBA891065673 for ; Sat, 9 Apr 2011 21:06:01 +0000 (UTC) (envelope-from warchild@clash.no-ip.org) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 8D7688FC12 for ; Sat, 9 Apr 2011 21:06:01 +0000 (UTC) Received: from [10.29.65.2] (port=49574) by fish.ish.com.au with esmtpa (Exim 4.69) (envelope-from ) id 1Q8fB0-0006nu-0V for freebsd-fs@freebsd.org; Sun, 10 Apr 2011 06:54:38 +1000 X-CTCH-RefID: str=0001.0A150203.4DA0C78E.0097,ss=1,fgs=0 Message-ID: <4DA0C78E.5020900@clash.no-ip.org> Date: Sun, 10 Apr 2011 06:54:38 +1000 From: Jurgen / WAR_CH|LD User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 09 Apr 2011 23:04:00 +0000 Subject: ZFS: Booting problem with zfsboot and MBR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: warchild@space-marine.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2011 21:06:01 -0000 Hello Did you ever find a resolution to this problem? I have it and I really need to fix it. Thanks Jurgen