From owner-freebsd-fs@FreeBSD.ORG Sun Aug 26 05:26:08 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E594106564A for ; Sun, 26 Aug 2012 05:26:08 +0000 (UTC) (envelope-from dan@3geeks.org) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 052668FC0C for ; Sun, 26 Aug 2012 05:26:07 +0000 (UTC) Received: by obbun3 with SMTP id un3so8566978obb.13 for ; Sat, 25 Aug 2012 22:26:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=3geeks.org; s=google; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=OISE7b5okafi6CWUa1GnJ3tfdQLY8+znmi4OstyQdyM=; b=L7qeiDVce4eKktmSC1j4AK5cfp2CHJ1HcwV33UY+vkLgdZZmMswjLP3qXbk2GZJia0 /2XRP0GQpUmRgQJ4VCawp4jdbAUZHSSxdJMY4KI7z75of5pyrAFgAmNZat/QKlWygiwx 03lis+He5bYkoMX1LhwqiG1+AdGlG8PTmq4sk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer:x-gm-message-state; bh=OISE7b5okafi6CWUa1GnJ3tfdQLY8+znmi4OstyQdyM=; b=DKedJccNPFG9sIc6xSidI50ECGveNlGTnJw6VydqpFEn01PTpKQua2sPC1d7DtbOkk PYqDTaQ77uC4MOYjLleE07tZuo2SRIYm9q2DV6v0MtJF3fMCmC1jTJdF20AXbT/jCSUA AMJVOHN+ubxzdKgbmrlbtbCy8WOiOyPTTN/oVloC/xMrranBqXhgR0C1wpfhhASiDwKy vuf6M5eA8oSOvw46ybDEU/+V8NyWsQxVhtoCFQ024OWa6s526QPXl9Nnd8cQEpZY98Mk vchTvYljp/pw7w/LiDiyw6Mfd0SSPSpOJZ8ohgXGWia6+AMa69E1kO0uOjwc1MCUboyR 3rbw== Received: by 10.60.30.168 with SMTP id t8mr7577425oeh.89.1345958767341; Sat, 25 Aug 2012 22:26:07 -0700 (PDT) Received: from las1111-4kdb2q1.northamerica.corporate-domain.net ([65.210.205.254]) by mx.google.com with ESMTPS id qk5sm13762683obc.10.2012.08.25.22.26.06 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 25 Aug 2012 22:26:06 -0700 (PDT) From: Daniel Mayfield Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 26 Aug 2012 00:19:40 -0500 Message-Id: <4E305393-A1BF-4425-BF11-286A045B7136@3geeks.org> To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQmp/FUTMdWdh07g4pmmAc6DpBDL0hWTzeGAWfIP8dHdnBi/g2LhIjSvANNP6Hiv6YLG5AW+ Subject: import a pool with a bad vdev config 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, 26 Aug 2012 05:26:08 -0000 I have a zpool on a SAN that came from a solaris machine running EMC = Powerpath. When I try to import this, zpool tells me I have an invalid = vdev config. Running a "zdb -l" on the device shows powerpath specific = devices. Any idea =10how I can alter that enough to get the pool = imported? Daniel= From owner-freebsd-fs@FreeBSD.ORG Sun Aug 26 18:49:51 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CBADF106564A for ; Sun, 26 Aug 2012 18:49:51 +0000 (UTC) (envelope-from mailinglists@nobaq.net) Received: from mail.nobaq.net (mail.nobaq.net [IPv6:2001:7b8:3cd:3::172]) by mx1.freebsd.org (Postfix) with ESMTP id 24A148FC16 for ; Sun, 26 Aug 2012 18:49:48 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=mail.nobaq.net) by mail.nobaq.net with esmtp (Exim 4.72) (envelope-from ) id 1T5htz-0007U7-LK for freebsd-fs@freebsd.org; Sun, 26 Aug 2012 20:49:39 +0200 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=nobaq.net; h=message-id :date:from:mime-version:to:content-type :content-transfer-encoding:subject; s=n200908; bh=2KpaQ0a0/IVy8s Zb9dxXhIHJbq4=; b=WTBF9Q/zDuSvkQMIomOseaRdpN/t9YB5mbEv3t3RCId5Ut 1J9LloFGrIHtl8qAS4UD7q50LmxijMireYgyOhHeVgGlxeSD/p7O6JtqkbuMPvUK 3cU9Je3yE1xxAgrPr8trZ/vXMEgZxoRxpNdRKRHG4OyWgyL0+J57ZO83S9p1E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=nobaq.net; h=message-id:date :from:mime-version:to:content-type:content-transfer-encoding :subject; q=dns; s=n200908; b=NIhm1m8QTowmiSA3Ocuj031oLNw1PNoIB7 hpyj53dT4O8vG2p4TbmFqr2yB0GRBaReAbaBYPzObuP6kP5T3IEET6l7BHiLYujz HL6UGC1A9eShhshSj5zG0qOAErBgwutUmovhHEmBjkKfidORPf6RFsiW6LZr5N5c 6/dm4oOmQ= Received: from 1360029737.d-dsl.at ([81.16.104.41] helo=[10.69.11.215]) by mail.nobaq.net with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1T5htS-0007U0-MB for freebsd-fs@freebsd.org; Sun, 26 Aug 2012 20:49:39 +0200 Message-ID: <503A6F9F.7070801@nobaq.net> Date: Sun, 26 Aug 2012 20:49:03 +0200 From: Niki Hammler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.nobaq.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.1 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: mailinglists@nobaq.net X-SA-Exim-Scanned: No (on mail.nobaq.net); SAEximRunCond expanded to false Subject: zvol + raidz issue? 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, 26 Aug 2012 18:49:52 -0000 Hi, Given: new HP Proliant Microserver N40L (4 GB RAM) and 3x2TB SATA drives (SAMSUNG HD204UI, ST32000542AS, WDC WD20EARX-00PASB0). Goal: RAIDz1 containg datasets and zvols to be exported via iSCSI. Issue: When I create a zvol on a RAIDz1 I get horrible performance (few MB/s or less). First test: 500G zvol on a mirror (freshly created): # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT plvl1i0 1.81T 1.97G 1.81T 0% ONLINE /mnt # zfs list NAME USED AVAIL REFER MOUNTPOINT plvl1i0 500G 1.30T 112K /mnt/plvl1i0 plvl1i0/zvtest 500G 1.78T 1.97G - # dd if=/dev/zero of=/dev/zvol/plvl1i0/zvtest bs=2048k count=1000 1000+0 records in 1000+0 records out 2097152000 bytes transferred in 17.318348 secs (121094230 bytes/sec) # Corresponds to 115,48 MB/s which is good (similar results for a single drive). Second test: 500G zvol on the 3x2TB raidz1 (freshly created): # dd if=/dev/zero of=/dev/zvol/plvl5i0/zvtest bs=2048k count=1000 1000+0 records in 1000+0 records out 2097152000 bytes transferred in 700.126725 secs (2995389 bytes/sec) # which is only 2,85 MB/s. Remark: Both pools are created with the force 4096 alignment option (since I have 512 and 4096 drives mixed). Now is the point where you might say the problem is related to the raidz1. But it is not: I created a 500G dataset in the same RAIDz pool and copied about 100G data onto it with rsync+ssh. Result: about 28MB/s end2end performance which is reasonable. Are there any issues with zvol + raidz1? Google resulted in empty result set. I run a minimal FreeBSD 8.2 (FreeNAS): # uname -a FreeBSD zetta 8.2-RELEASE-p9 FreeBSD 8.2-RELEASE-p9 #0: Thu Jul 19 12:39:10 PDT 2012 root@build.ixsystems.com:/build/home/jpaetzel/8.2.0/os-base/amd64/build/home/jpaetzel/8.2.0/FreeBSD/src/sys/FREENAS.amd64 amd64 Regards, Niki PS: This is also posted on http://forums.freenas.org/showthread.php?p=35590 From owner-freebsd-fs@FreeBSD.ORG Sun Aug 26 20:13:52 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E619A106564A for ; Sun, 26 Aug 2012 20:13:52 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 643948FC1B for ; Sun, 26 Aug 2012 20:13:51 +0000 (UTC) Received: by lage12 with SMTP id e12so2468624lag.13 for ; Sun, 26 Aug 2012 13:13:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=J4cmwtKUbviZ3JLP4AYSh6Cmp4G3xoh+JSWQDxQtB4A=; b=EFLG5Zaemxnq0xZUsghPJ9PA+ritrkTYaJtDqMQg/voQj//8M3mjs6p8evw2Uz2zHY cPqw62C/WTLzXJF0KBvENfI5v81NxlYVC9h7VdIXHdPOrvCZnWmlfemWnQMHxYvBDeVl rcbbEXeZLvy4u4SUfGcQXo/co/+sLo22yN4T97AwcNrUi4q7bxGU6FYNanABzdWP+iY6 V5ngLYf3d6Ezw7d26JQpsVcTsDmZRcq5dt6fBgqa7/XYLpXcmDKQx5Y+SU6jkbW/S9Qy fHIhcJoTLPTNx8oCokV+JQsUHJeJQUOh3CF2vw+B/6PeQQKin/ZPmLOdSFIyApbeRVLe uYpg== MIME-Version: 1.0 Received: by 10.112.102.8 with SMTP id fk8mr5379234lbb.71.1346012030928; Sun, 26 Aug 2012 13:13:50 -0700 (PDT) Received: by 10.114.24.101 with HTTP; Sun, 26 Aug 2012 13:13:50 -0700 (PDT) Received: by 10.114.24.101 with HTTP; Sun, 26 Aug 2012 13:13:50 -0700 (PDT) In-Reply-To: <503A6F9F.7070801@nobaq.net> References: <503A6F9F.7070801@nobaq.net> Date: Sun, 26 Aug 2012 13:13:50 -0700 Message-ID: From: Freddie Cash To: Niki Hammler Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: zvol + raidz issue? 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, 26 Aug 2012 20:13:53 -0000 (Sorry for top-post, sending from phone.) Please show the command-line used to create the zvol. Especially the recordsize option. When using zvols, you have to make sure to match the recordsize of the zvol to that of the filesystem used above it. Otherwise, performance will be atrocious. On Aug 26, 2012 11:50 AM, "Niki Hammler" wrote: > Hi, > > Given: new HP Proliant Microserver N40L (4 GB RAM) and 3x2TB SATA drives > (SAMSUNG HD204UI, ST32000542AS, WDC WD20EARX-00PASB0). > > Goal: RAIDz1 containg datasets and zvols to be exported via iSCSI. > > Issue: When I create a zvol on a RAIDz1 I get horrible performance (few > MB/s or less). > > First test: 500G zvol on a mirror (freshly created): > > # zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > plvl1i0 1.81T 1.97G 1.81T 0% ONLINE /mnt > # zfs list > NAME USED AVAIL REFER MOUNTPOINT > plvl1i0 500G 1.30T 112K /mnt/plvl1i0 > plvl1i0/zvtest 500G 1.78T 1.97G - > # dd if=/dev/zero of=/dev/zvol/plvl1i0/zvtest bs=2048k count=1000 > 1000+0 records in > 1000+0 records out > 2097152000 bytes transferred in 17.318348 secs (121094230 bytes/sec) > # > > Corresponds to 115,48 MB/s which is good (similar results for a single > drive). > > Second test: 500G zvol on the 3x2TB raidz1 (freshly created): > > # dd if=/dev/zero of=/dev/zvol/plvl5i0/zvtest bs=2048k count=1000 > > 1000+0 records in > 1000+0 records out > 2097152000 bytes transferred in 700.126725 secs (2995389 bytes/sec) > # > > which is only 2,85 MB/s. > > Remark: Both pools are created with the force 4096 alignment option > (since I have 512 and 4096 drives mixed). > > Now is the point where you might say the problem is related to the > raidz1. But it is not: I created a 500G dataset in the same RAIDz pool > and copied about 100G data onto it with rsync+ssh. Result: about 28MB/s > end2end performance which is reasonable. > > Are there any issues with zvol + raidz1? Google resulted in empty result > set. > > I run a minimal FreeBSD 8.2 (FreeNAS): > > # uname -a > FreeBSD zetta 8.2-RELEASE-p9 FreeBSD 8.2-RELEASE-p9 #0: Thu Jul 19 > 12:39:10 PDT 2012 > root@build.ixsystems.com: > /build/home/jpaetzel/8.2.0/os-base/amd64/build/home/jpaetzel/8.2.0/FreeBSD/src/sys/FREENAS.amd64 > amd64 > > Regards, > Niki > > > PS: This is also posted on > http://forums.freenas.org/showthread.php?p=35590 > _______________________________________________ > 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 Sun Aug 26 20:40:19 2012 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 D6C18106564A for ; Sun, 26 Aug 2012 20:40:19 +0000 (UTC) (envelope-from antonintessier@live.fr) Received: from dub0-omc4-s8.dub0.hotmail.com (dub0-omc4-s8.dub0.hotmail.com [157.55.2.83]) by mx1.freebsd.org (Postfix) with ESMTP id 6E9A28FC0C for ; Sun, 26 Aug 2012 20:40:18 +0000 (UTC) Received: from DUB109-W58 ([157.55.2.73]) by dub0-omc4-s8.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 26 Aug 2012 13:39:11 -0700 Message-ID: X-Originating-IP: [93.182.219.16] From: antonin tessier To: Date: Sun, 26 Aug 2012 22:39:11 +0200 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 26 Aug 2012 20:39:11.0768 (UTC) FILETIME=[D9677180:01CD83CA] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Recover ZFS pool after having deleted zfs configuration file in /boot 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, 26 Aug 2012 20:40:19 -0000 >> Or try 'zpool import -D'. -D Lists destroyed pools only. It can help if you mail the output from the commands you run. That migh= t give other people clues you don't recognize. Actually=2C these commands both produce the same result: they simply stop w= ithout printing anything ...I noticed that /boot/zfs/ was deleted. Thank you. = From owner-freebsd-fs@FreeBSD.ORG Sun Aug 26 21:39:49 2012 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 29310106564A for ; Sun, 26 Aug 2012 21:39:49 +0000 (UTC) (envelope-from mailinglists@nobaq.net) Received: from mail.nobaq.net (mail.nobaq.net [IPv6:2001:7b8:3cd:3::172]) by mx1.freebsd.org (Postfix) with ESMTP id D36648FC08 for ; Sun, 26 Aug 2012 21:39:47 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=mail.nobaq.net) by mail.nobaq.net with esmtp (Exim 4.72) (envelope-from ) id 1T5kYS-0007oC-DH; Sun, 26 Aug 2012 23:39:36 +0200 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=nobaq.net; h=message-id :date:from:mime-version:to:cc:references:in-reply-to :content-type:content-transfer-encoding:subject; s=n200908; bh=H QDVJX7iMMNPxYNxuscSl1Eerwk=; b=0IhM4prC6wXNHOxNO9vmulB7cOqKd6eib HtzUlWUj02Xrbe6yULQJq/XGLX5n/U3x1HYErN8I64Tsp4z/15QJX5vfmkGBxNW5 XlGGJjuQWPBVru1rWtz7hALZqyh6kTJjIs6uTgEz+4ls55ha9EUTXUEqTgy6KWFj VnSJ1yXhDw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=nobaq.net; h=message-id:date :from:mime-version:to:cc:references:in-reply-to:content-type :content-transfer-encoding:subject; q=dns; s=n200908; b=qroZWyzq MgXT8fYwMCghzy4AY/GYO6j4SIG9z/03plr2QrRcHqefSO8QDa372QJeMy6ZHjqj nekQbBVm9LJrINk5I4mEcOdxBg4wU/UHIS/zVQDmE6NezUrfVfViGi6735EVnvKS i/7D7IFYDGQlGCq5zAKp5AJtbPZDWWTI+6Q= Received: from 1360029737.d-dsl.at ([81.16.104.41] helo=[10.69.11.203]) by mail.nobaq.net with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1T5kXw-0007o7-Kt; Sun, 26 Aug 2012 23:39:36 +0200 Message-ID: <503A9773.2000604@nobaq.net> Date: Sun, 26 Aug 2012 23:38:59 +0200 From: Niki Hammler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Freddie Cash References: <503A6F9F.7070801@nobaq.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.nobaq.net X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50 autolearn=ham version=3.3.1 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: mailinglists@nobaq.net X-SA-Exim-Scanned: No (on mail.nobaq.net); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org Subject: Re: zvol + raidz issue? 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, 26 Aug 2012 21:39:49 -0000 Hi Freddie, Thank you for the reply. Am 26.08.2012 22:13, schrieb Freddie Cash: > Please show the command-line used to create the zvol. Nothing special: zfs create -V 500g plvl1i0/zvtest1 > Especially the recordsize option. I guess you mean the '-b' option? Because recordsize is only valid for datasets, not for zvols. > When using zvols, you have to make sure to match the > recordsize of the zvol to that of the filesystem used above it. With above, you mean the pool containg it or the file system which will be created inside the zvol? For the first case: This should match if no blocksize is explicitely given: [root@zetta] ~# zfs get volblocksize plvl1i0/zvtest NAME PROPERTY VALUE SOURCE plvl1i0/zvtest volblocksize 8K - [root@zetta] ~# zfs get recordsize plvl1i0 NAME PROPERTY VALUE SOURCE plvl1i0 recordsize 128K default 128K MOD 8K = 0, furthermore, 16 zvol blocks reside within one record of the zpool. For the second case: I access the zvol directly via /dev/zvol/plvl1i0/zvtest (dd benchmark) so there is not yet a file system on top. Furthermore, I use bs=2048k with dd which is again divisible by volblocksize of the zvol and by recordsize of the pool. > Otherwise, performance will be atrocious. I understand. But still: What is the difference to a zpool with a single drive or to a mirror? I do not have the problem there ... Thank you. Regards, Niki > On Aug 26, 2012 11:50 AM, "Niki Hammler" > wrote: > > Hi, > > Given: new HP Proliant Microserver N40L (4 GB RAM) and 3x2TB SATA drives > (SAMSUNG HD204UI, ST32000542AS, WDC WD20EARX-00PASB0). > > Goal: RAIDz1 containg datasets and zvols to be exported via iSCSI. > > Issue: When I create a zvol on a RAIDz1 I get horrible performance (few > MB/s or less). > > First test: 500G zvol on a mirror (freshly created): > > # zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > plvl1i0 1.81T 1.97G 1.81T 0% ONLINE /mnt > # zfs list > NAME USED AVAIL REFER MOUNTPOINT > plvl1i0 500G 1.30T 112K /mnt/plvl1i0 > plvl1i0/zvtest 500G 1.78T 1.97G - > # dd if=/dev/zero of=/dev/zvol/plvl1i0/zvtest bs=2048k count=1000 > 1000+0 records in > 1000+0 records out > 2097152000 bytes transferred in 17.318348 secs (121094230 bytes/sec) > # > > Corresponds to 115,48 MB/s which is good (similar results for a single > drive). > > Second test: 500G zvol on the 3x2TB raidz1 (freshly created): > > # dd if=/dev/zero of=/dev/zvol/plvl5i0/zvtest bs=2048k count=1000 > > 1000+0 records in > 1000+0 records out > 2097152000 bytes transferred in 700.126725 secs (2995389 bytes/sec) > # > > which is only 2,85 MB/s. > > Remark: Both pools are created with the force 4096 alignment option > (since I have 512 and 4096 drives mixed). > > Now is the point where you might say the problem is related to the > raidz1. But it is not: I created a 500G dataset in the same RAIDz pool > and copied about 100G data onto it with rsync+ssh. Result: about 28MB/s > end2end performance which is reasonable. > > Are there any issues with zvol + raidz1? Google resulted in empty result > set. > > I run a minimal FreeBSD 8.2 (FreeNAS): > > # uname -a > FreeBSD zetta 8.2-RELEASE-p9 FreeBSD 8.2-RELEASE-p9 #0: Thu Jul 19 > 12:39:10 PDT 2012 > root@build.ixsystems.com:/build/home/jpaetzel/8.2.0/os-base/amd64/build/home/jpaetzel/8.2.0/FreeBSD/src/sys/FREENAS.amd64 > amd64 > > Regards, > Niki > > > PS: This is also posted on > http://forums.freenas.org/showthread.php?p=35590 > _______________________________________________ > 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 Aug 27 07:02:19 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E371106564A; Mon, 27 Aug 2012 07:02:19 +0000 (UTC) (envelope-from jlh@FreeBSD.org) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [IPv6:2a01:e0c:1:1599::14]) by mx1.freebsd.org (Postfix) with ESMTP id 3A39C8FC1B; Mon, 27 Aug 2012 07:02:16 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id B0955D48142; Mon, 27 Aug 2012 09:02:11 +0200 (CEST) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id 979B633F; Mon, 27 Aug 2012 09:02:10 +0200 (CEST) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id 6EC2F10754; Mon, 27 Aug 2012 07:02:10 +0000 (UTC) Date: Mon, 27 Aug 2012 09:02:10 +0200 From: Jeremie Le Hen To: freebsd-fs@FreeBSD.org Message-ID: <20120827070210.GA798@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: jlh@FreeBSD.org Subject: Cannot get zfsboot prompt 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, 27 Aug 2012 07:02:19 -0000 Hi there, Can you please keep me cc'ed as I'm not subscribed. Thanks. I've struggled all over the weekend to make a remote machine full ZFS. I did it once last year. I already struggled a lot at that time by the way so I took notes, but it doesn't work (see below for a manuel screenshot): The server is using the mbr partitionning scheme, with one slice -- ada0s1. There is a BSD label on it with two partitions, ada0s1a which is used in the zpool and ada0s1b which is used for swap/dump. I've set up boot0 and it works correctly: gpart bootcode -b /mnt/boot/boot0 ada0 I've then set up zfsboot: dd if=/mnt/boot/zfsboot of=/dev/ada0s1 count=1 dd if=/mny/boot/zfsboot of=/dev/ada0s1a skip=1 seek=1024 Here is the relevant datasets, the pool as been imported with altroot=/mnt: rescue-bsd# zfs list | head -n 3 NAME USED AVAIL REFER MOUNTPOINT zroot 827M 913G 31K none zroot/rootfs 826M 913G 381M /mnt rescue-bsd# zpool get bootfs zroot NAME PROPERTY VALUE SOURCE zroot bootfs zroot/rootfs local When the server boots I get: F1 FreeBSD F6 PXE Boot: F1 _ Any idea? Thanks. -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 08:28:29 2012 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 3EFBF1065673 for ; Mon, 27 Aug 2012 08:28:29 +0000 (UTC) (envelope-from mailinglists@nobaq.net) Received: from mail.nobaq.net (mail.nobaq.net [IPv6:2001:7b8:3cd:3::172]) by mx1.freebsd.org (Postfix) with ESMTP id 3A82E8FC29 for ; Mon, 27 Aug 2012 08:28:24 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=mail.nobaq.net) by mail.nobaq.net with esmtp (Exim 4.72) (envelope-from ) id 1T5ug9-0000qa-Pf; Mon, 27 Aug 2012 10:28:13 +0200 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=nobaq.net; h=message-id :date:from:mime-version:to:cc:references:in-reply-to :content-type:content-transfer-encoding:subject; s=n200908; bh=E QVG1WbAEXXpx54aroQ9iVl8zjs=; b=AKksz0we9Oi021h3Hb3jt8SqZegyWAK5F xHKWF/kEPveIvAgFbSdnW/xt/aeEh85Raq8hQzI5h3JA92MyD6w1KGl1Ogl0GJDh fZNjyhyHsbetxWR0fRBzPK7aB/O86YzScRQyi07Nde5jBOLNXzCQT/LURqMQZGCk ytnn2Gg1T0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=nobaq.net; h=message-id:date :from:mime-version:to:cc:references:in-reply-to:content-type :content-transfer-encoding:subject; q=dns; s=n200908; b=AqPZQrlQ +O6k1RsZQ8RWrFkm1Hh45Bll6VjdYziSYW0ISesPBfeBpH+vZ2Yy/cegwfGgOCC3 mm1ZkCYwQDrTo0Q2xiOxWIwfLAJVC3ZvCviQfKRdfYaPZq290LX9E2Lxkt6HCnou AG5Y+EinnSzBFnL7MuhqxSogGppOcs0yik4= Received: from 1360029737.d-dsl.at ([81.16.104.41] helo=[10.69.11.204]) by mail.nobaq.net with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1T5ufd-0000q0-B4; Mon, 27 Aug 2012 10:28:13 +0200 Message-ID: <503B2F78.4070800@nobaq.net> Date: Mon, 27 Aug 2012 10:27:36 +0200 From: Niki Hammler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Freddie Cash References: <503A6F9F.7070801@nobaq.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.nobaq.net X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.3.1 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: mailinglists@nobaq.net X-SA-Exim-Scanned: No (on mail.nobaq.net); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org Subject: Re: zvol + raidz issue? 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, 27 Aug 2012 08:28:29 -0000 Hi, According to [1], I want to add some debug info: http://www.nobaq.net/~niki/raidz-problem/zfs_debug_info.txt * iostat while writing to zvol on raidz1: http://www.nobaq.net/~niki/raidz-problem/zpool_iostat_raidz1.txt -> Often only one disk accessed, only few MB, sometimes even kb/s! * iostat while writing 1 GB directly to a dataset (same zpool!): http://www.nobaq.net/~niki/raidz-proble/zpool_iostat_raidz1_dataset2.txt -> No problem * iostat while writing to zvol on mirror (same disks): http://www.nobaq.net/~niki/raidz-proble/zpool_iostat_mirror.txt -> Also no problem Furthermore, I did some more tests and I think this must be a bug: The problem is not related with hardware and disks and it ONLY occurs when I create a zvol on the RAIDz1: Copying linear 1GB file onto a fresh 500g zvol on these zpools: ada2 ada3 (mirror) 105 MB/s ada1 ada3 (mirror) 128 MB/s ada1 ada2 (mirror) 117 MB/s ada1 ada2 ada3 (raidz) 2,5 MB/s <--- !!!!!!!!!!!!! ada1 ada2 ada3 (mirror) 112 MB/s Since 512 and 4096 drives are mixed, the alignment is set correctly: # zdb | grep ashift ashift=12 ashift=12 What other tests/debugging can I do and where could I file a bug report? Regards, Niki [1] http://wiki.freebsd.org/ZFS/ProblemReporting Am 26.08.2012 22:13, schrieb Freddie Cash: > On Aug 26, 2012 11:50 AM, "Niki Hammler" > wrote: > > Hi, > > Given: new HP Proliant Microserver N40L (4 GB RAM) and 3x2TB SATA drives > (SAMSUNG HD204UI, ST32000542AS, WDC WD20EARX-00PASB0). > > Goal: RAIDz1 containg datasets and zvols to be exported via iSCSI. > > Issue: When I create a zvol on a RAIDz1 I get horrible performance (few > MB/s or less). > > First test: 500G zvol on a mirror (freshly created): > > # zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > plvl1i0 1.81T 1.97G 1.81T 0% ONLINE /mnt > # zfs list > NAME USED AVAIL REFER MOUNTPOINT > plvl1i0 500G 1.30T 112K /mnt/plvl1i0 > plvl1i0/zvtest 500G 1.78T 1.97G - > # dd if=/dev/zero of=/dev/zvol/plvl1i0/zvtest bs=2048k count=1000 > 1000+0 records in > 1000+0 records out > 2097152000 bytes transferred in 17.318348 secs (121094230 bytes/sec) > # > > Corresponds to 115,48 MB/s which is good (similar results for a single > drive). > > Second test: 500G zvol on the 3x2TB raidz1 (freshly created): > > # dd if=/dev/zero of=/dev/zvol/plvl5i0/zvtest bs=2048k count=1000 > > 1000+0 records in > 1000+0 records out > 2097152000 bytes transferred in 700.126725 secs (2995389 bytes/sec) > # > > which is only 2,85 MB/s. > > Remark: Both pools are created with the force 4096 alignment option > (since I have 512 and 4096 drives mixed). > > Now is the point where you might say the problem is related to the > raidz1. But it is not: I created a 500G dataset in the same RAIDz pool > and copied about 100G data onto it with rsync+ssh. Result: about 28MB/s > end2end performance which is reasonable. > > Are there any issues with zvol + raidz1? Google resulted in empty result > set. > > I run a minimal FreeBSD 8.2 (FreeNAS): > > # uname -a > FreeBSD zetta 8.2-RELEASE-p9 FreeBSD 8.2-RELEASE-p9 #0: Thu Jul 19 > 12:39:10 PDT 2012 > root@build.ixsystems.com:/build/home/jpaetzel/8.2.0/os-base/amd64/build/home/jpaetzel/8.2.0/FreeBSD/src/sys/FREENAS.amd64 > amd64 > > Regards, > Niki > > > PS: This is also posted on > http://forums.freenas.org/showthread.php?p=35590 > _______________________________________________ > 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 Aug 27 08:31:51 2012 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 369C3106566B for ; Mon, 27 Aug 2012 08:31:51 +0000 (UTC) (envelope-from antonintessier@live.fr) Received: from dub0-omc4-s27.dub0.hotmail.com (dub0-omc4-s27.dub0.hotmail.com [157.55.2.102]) by mx1.freebsd.org (Postfix) with ESMTP id C21708FC0A for ; Mon, 27 Aug 2012 08:31:50 +0000 (UTC) Received: from DUB109-W39 ([157.55.2.72]) by dub0-omc4-s27.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 27 Aug 2012 01:27:27 -0700 Message-ID: X-Originating-IP: [93.182.219.16] From: antonin tessier To: Date: Mon, 27 Aug 2012 10:27:27 +0200 Importance: Normal In-Reply-To: <20120827010606.GA57096@neutralgood.org> References: , <20120827010606.GA57096@neutralgood.org> MIME-Version: 1.0 X-OriginalArrivalTime: 27 Aug 2012 08:27:27.0694 (UTC) FILETIME=[CAF326E0:01CD842D] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: Recover ZFS pool after having deleted zfs configuration file in /boot 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, 27 Aug 2012 08:31:51 -0000 > You can try to '-f' import the pool if you are _sure_ that all disks > are connected. I suggest a read-only import to start with. But the > documentation implies that zpool import should tell you when it has > run into this case=2C and if I understand correctly then you are saying > this isn't what is happening. # zpool import -f tells me: "cannot import 'home': a pool with that name is= already created/imported=2C and no additional pools with that name were found" > Also make sure you aren't mixing up the mount point with the pool name. > The path "/usr/home" is a mount point. I don't recall if you've given > the name of the pool yet or not. My pool is known as "home". Even if I mounted the "created pool"=2C /usr/ho= me keeps empty... Regards. = From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 08:43:38 2012 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 05266106566B for ; Mon, 27 Aug 2012 08:43:38 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 875A48FC15 for ; Mon, 27 Aug 2012 08:43:37 +0000 (UTC) Received: from server.rulingia.com (c220-239-249-137.belrs5.nsw.optusnet.com.au [220.239.249.137]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q7R8hYnD044638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 27 Aug 2012 18:43:34 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q7R8hSw3093350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Aug 2012 18:43:28 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q7R8hSYE093349; Mon, 27 Aug 2012 18:43:28 +1000 (EST) (envelope-from peter) Date: Mon, 27 Aug 2012 18:43:28 +1000 From: Peter Jeremy To: antonin tessier Message-ID: <20120827084328.GA93310@server.rulingia.com> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: Recover ZFS pool after having deleted zfs configuration file in /boot 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, 27 Aug 2012 08:43:38 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Please stop creating new threads. If you reply to other people's questions, it's far easier to follow. On 2012-Aug-26 22:39:11 +0200, antonin tessier wro= te: >t printing anything ...I noticed that /boot/zfs/ was deleted. Do you know how/why /boot/zfs got deleted? What is the output of "zpool status -v"? Have you tried "zpool export home" and then "zpool import home"? Do you have root on ZFS or UFS? --=20 Peter Jeremy --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA7MzAACgkQ/opHv/APuIfEwwCginilc+zcpI9hFK3RclSB4kHW za4Anj5QC1wMSKV0lMSTVxgRASItNwsh =PvCR -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 10:00:04 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38B45106564A; Mon, 27 Aug 2012 10:00:04 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward4.mail.yandex.net (forward4.mail.yandex.net [IPv6:2a02:6b8:0:602::4]) by mx1.freebsd.org (Postfix) with ESMTP id 99DA38FC1B; Mon, 27 Aug 2012 10:00:03 +0000 (UTC) Received: from smtp3.mail.yandex.net (smtp3.mail.yandex.net [77.88.46.103]) by forward4.mail.yandex.net (Yandex) with ESMTP id 7EB621BC188B; Mon, 27 Aug 2012 14:00:02 +0400 (MSK) Received: from smtp3.mail.yandex.net (localhost [127.0.0.1]) by smtp3.mail.yandex.net (Yandex) with ESMTP id 5462F1BA034A; Mon, 27 Aug 2012 14:00:02 +0400 (MSK) Received: from ns.kirov.so-ups.ru (ns.kirov.so-ups.ru [178.74.170.1]) by smtp3.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 01tWKcqZ-01tSEMho; Mon, 27 Aug 2012 14:00:01 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1346061602; bh=BTmTPo7MmQGIWbcbXKT3oxMZrS8YqmsHBJ1nQN8wW0A=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=D0ML9FEeO94mZJejUf61KwcELg32XbcxUFng/GIIVK5cFgy69dliprGsb290COFdc MX/QQFfQNTsdygk4Z3RRjwlALYYOxmGdwdA9lJ7sencFHJn/SfkB7sowZHqHXwvZAb bs9Gy2eXzbpWjRlal817+U+MdQvX0jb7xoNP+Oqg= Message-ID: <503B4521.9080603@yandex.ru> Date: Mon, 27 Aug 2012 14:00:01 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Jeremie Le Hen References: <20120827070210.GA798@felucia.tataz.chchile.org> In-Reply-To: <20120827070210.GA798@felucia.tataz.chchile.org> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: Cannot get zfsboot prompt 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, 27 Aug 2012 10:00:04 -0000 On 27.08.2012 11:02, Jeremie Le Hen wrote: > I've struggled all over the weekend to make a remote machine full ZFS. > I did it once last year. I already struggled a lot at that time by the > way so I took notes, but it doesn't work (see below for a manuel > screenshot): > > The server is using the mbr partitionning scheme, with one slice -- > ada0s1. There is a BSD label on it with two partitions, ada0s1a which > is used in the zpool and ada0s1b which is used for swap/dump. > > I've set up boot0 and it works correctly: > gpart bootcode -b /mnt/boot/boot0 ada0 > I've then set up zfsboot: > dd if=/mnt/boot/zfsboot of=/dev/ada0s1 count=1 > dd if=/mny/boot/zfsboot of=/dev/ada0s1a skip=1 seek=1024 Hi, When i'm configuring ZFS-only system, usually i do the following steps: 1. zpool create -R /mnt bsdroot ada0s1a 2. Create several filesystems and install the system. 3. zpool set bootfs=bsdroot/root bsdroot 4. zpool set cachefile=/mnt/boot/zfs/zpool.cache bsdroot 5. echo 'vfs.root.mountfrom="zfs:bsdroot/root"' >> /boot/loader.conf echo 'zfs_load="YES"' >> /boot/loader.conf 6. echo 'zfs_enable="YES"' >> /etc/rc.conf 7. Add swap entry to the /etc/fstab 8. zpool set mountpoint=none bsdroot/root 9. zpool set mountpoint=none bsdroot 10. Write bootcode: > dd if=/mnt/boot/zfsboot of=/dev/ada0s1 count=1 > dd if=/mnt/boot/zfsboot of=/dev/ada0s1 skip=1 seek=1024 I guess your ada0s1a partition has non zero offset, and second part of zfsboot bootcode has been written into wrong place. AFAIK, the first part of the zfsboot does read the second part from the 1024 sector of the active FreeBSD slice in the MBR. -- WBR, Andrey V. Elsukov From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 10:14:07 2012 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 036C41065695 for ; Mon, 27 Aug 2012 10:14:07 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 8800A8FC27 for ; Mon, 27 Aug 2012 10:14:06 +0000 (UTC) Received: from server.rulingia.com (c220-239-249-137.belrs5.nsw.optusnet.com.au [220.239.249.137]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q7RAE1dq045322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 27 Aug 2012 20:14:02 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q7RADt9Y094303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Aug 2012 20:13:56 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q7RADs42094301; Mon, 27 Aug 2012 20:13:54 +1000 (EST) (envelope-from peter) Date: Mon, 27 Aug 2012 20:13:54 +1000 From: Peter Jeremy To: Daniel Mayfield Message-ID: <20120827101354.GC93853@server.rulingia.com> References: <4E305393-A1BF-4425-BF11-286A045B7136@3geeks.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pAwQNkOnpTn9IO2O" Content-Disposition: inline In-Reply-To: <4E305393-A1BF-4425-BF11-286A045B7136@3geeks.org> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: import a pool with a bad vdev config 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, 27 Aug 2012 10:14:07 -0000 --pAwQNkOnpTn9IO2O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-26 00:19:40 -0500, Daniel Mayfield wrote: >I have a zpool on a SAN that came from a solaris machine running EMC >Powerpath. When I try to import this, zpool tells me I have an >invalid vdev config. Running a "zdb -l" on the device shows >powerpath specific devices. Any idea how I can alter that enough >to get the pool imported? The paths is the ZFS label don't really matter. "zpool import" will scan the available devices looking for pools. Does "zdb -l" show all 4 labels on each device? --=20 Peter Jeremy --pAwQNkOnpTn9IO2O Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA7SGIACgkQ/opHv/APuIcVOwCggaZCEEGd+jjlUuDa4f6gfv61 15EAn3LltvxzGY5625A8bLEZq8DGJG0S =nA4E -----END PGP SIGNATURE----- --pAwQNkOnpTn9IO2O-- From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 11:07:07 2012 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 47112106566C for ; Mon, 27 Aug 2012 11:07:07 +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 2F54E8FC20 for ; Mon, 27 Aug 2012 11:07:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7RB777I085836 for ; Mon, 27 Aug 2012 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7RB76oq085834 for freebsd-fs@FreeBSD.org; Mon, 27 Aug 2012 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Aug 2012 11:07:06 GMT Message-Id: <201208271107.q7RB76oq085834@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, 27 Aug 2012 11:07:07 -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/170945 fs [gpt] disk layout not portable between direct connect o kern/170914 fs [zfs] [patch] Import patchs related with issues 3090 a o kern/170912 fs [zfs] [patch] unnecessarily setting DS_FLAG_INCONSISTE o bin/170778 fs [zfs] [panic] FreeBSD panics randomly o kern/170680 fs [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEA o kern/170497 fs [xfs][panic] kernel will panic whenever I ls a mounted o kern/170238 fs [zfs] [panic] Panic when deleting data o kern/169945 fs [zfs] [panic] Kernel panic while importing zpool (afte o kern/169480 fs [zfs] ZFS stalls on heavy I/O o kern/169398 fs [zfs] Can't remove file with permanent error o kern/169339 fs panic while " : > /etc/123" o kern/169319 fs [zfs] zfs resilver can't complete o kern/168947 fs [nfs] [zfs] .zfs/snapshot directory is messed up when o kern/168942 fs [nfs] [hang] nfsd hangs after being restarted (not -HU o kern/168158 fs [zfs] incorrect parsing of sharenfs options in zfs (fs o kern/167979 fs [ufs] DIOCGDINFO ioctl does not work on 8.2 file syste o kern/167977 fs [smbfs] mount_smbfs results are differ when utf-8 or U o kern/167688 fs [fusefs] Incorrect signal handling with direct_io o kern/167685 fs [zfs] ZFS on USB drive prevents shutdown / reboot o kern/167612 fs [portalfs] The portal file system gets stuck inside po o kern/167272 fs [zfs] ZFS Disks reordering causes ZFS to pick the wron o kern/167260 fs [msdosfs] msdosfs disk was mounted the second time whe o kern/167109 fs [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene o kern/167105 fs [nfs] mount_nfs can not handle source exports wiht mor o kern/167067 fs [zfs] [panic] ZFS panics the server o kern/167066 fs [zfs] ZVOLs not appearing in /dev/zvol o kern/167065 fs [zfs] boot fails when a spare is the boot disk o kern/167048 fs [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF o kern/166912 fs [ufs] [panic] Panic after converting Softupdates to jo o kern/166851 fs [zfs] [hang] Copying directory from the mounted UFS di o kern/166477 fs [nfs] NFS data corruption. o kern/165950 fs [ffs] SU+J and fsck problem o kern/165923 fs [nfs] Writing to NFS-backed mmapped files fails if flu o kern/165521 fs [zfs] [hang] livelock on 1 Gig of RAM with zfs when 31 o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/162362 fs [snapshots] [panic] ufs with snapshot(s) panics when g o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo p kern/161897 fs [zfs] [patch] zfs partition probing causing long delay o kern/161864 fs [ufs] removing journaling from UFS partition fails on o bin/161807 fs [patch] add option for explicitly specifying metadata o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic o kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs p 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 p 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/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 bin/153142 fs [zfs] ls -l outputs `ls: ./.zfs: Operation not support o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small 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 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/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa 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 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 " p 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 f 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/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/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/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/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/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha 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 kern/118318 fs [nfs] NFS server hangs under special circumstances o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance 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/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 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 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/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/36566 fs [smbfs] System reboot with dead smb mount and umount 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 289 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 15:06:58 2012 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 0A366106566B; Mon, 27 Aug 2012 15:06:58 +0000 (UTC) (envelope-from jlh@FreeBSD.org) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [IPv6:2a01:e0c:1:1599::14]) by mx1.freebsd.org (Postfix) with ESMTP id C03068FC1F; Mon, 27 Aug 2012 15:06:55 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id 94220D480D5; Mon, 27 Aug 2012 17:06:49 +0200 (CEST) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id 7F5EE3F7; Mon, 27 Aug 2012 17:06:48 +0200 (CEST) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id 4A3D6109B4; Mon, 27 Aug 2012 15:06:48 +0000 (UTC) Date: Mon, 27 Aug 2012 17:06:48 +0200 From: Jeremie Le Hen To: "Andrey V. Elsukov" Message-ID: <20120827150648.GE32062@felucia.tataz.chchile.org> References: <20120827070210.GA798@felucia.tataz.chchile.org> <503B4521.9080603@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <503B4521.9080603@yandex.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Jeremie Le Hen , freebsd-fs@FreeBSD.org Subject: Re: Cannot get zfsboot prompt 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, 27 Aug 2012 15:06:58 -0000 On Mon, Aug 27, 2012 at 02:00:01PM +0400, Andrey V. Elsukov wrote: > > When i'm configuring ZFS-only system, usually i do the following steps: > 1. zpool create -R /mnt bsdroot ada0s1a > 2. Create several filesystems and install the system. > 3. zpool set bootfs=bsdroot/root bsdroot > 4. zpool set cachefile=/mnt/boot/zfs/zpool.cache bsdroot > 5. echo 'vfs.root.mountfrom="zfs:bsdroot/root"' >> /boot/loader.conf > echo 'zfs_load="YES"' >> /boot/loader.conf > 6. echo 'zfs_enable="YES"' >> /etc/rc.conf > 7. Add swap entry to the /etc/fstab > 8. zpool set mountpoint=none bsdroot/root > 9. zpool set mountpoint=none bsdroot > 10. Write bootcode: > > dd if=/mnt/boot/zfsboot of=/dev/ada0s1 count=1 > > dd if=/mnt/boot/zfsboot of=/dev/ada0s1 skip=1 seek=1024 > > I guess your ada0s1a partition has non zero offset, and second > part of zfsboot bootcode has been written into wrong place. > > AFAIK, the first part of the zfsboot does read the second part > from the 1024 sector of the active FreeBSD slice in the MBR. Yes I agree this is probably where the catch is. But note that contrary to your procedure, I laid zfsboot2 from ada0s1a. The first partition of my BSD label indeed starts at sector 1. rescue-bsd# gpart show ada0s1 => 0 1953525105 ada0s1 BSD (931G) 0 1 - free - (512B) 1 1951799000 1 freebsd-zfs (930G) 1951799001 1726096 4 freebsd-swap (842M) 1953525097 8 - free - (4.0k) >From what I undestand from sys/boot/i386/zfsboot/zfsldr.S, zfsboot1 expects zfsboot2 to be at offset 1024 for the start of the first FreeBSD (0xA5) MBR active slice (fall-back to non-active). 1024 sectors is not chosen randomly, this is because in zpools, the boot block is located after the two heading vdev label replicas which are 256KB each. Given my partition in shifted by one sector, zfsboot2 is shifted by one sector as well so zfsboot1 doesn't find it. Do you know if this topic is documented somewhere? I couldn't find anything when I needed it. Also, why does gpart(8) enforce a one sector offset for partition inside a BSD scheme? I tried to set an offset to 0 without any effect. Regards, -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 19:50:05 2012 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 8E7A4106564A for ; Mon, 27 Aug 2012 19:50:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 794448FC22 for ; Mon, 27 Aug 2012 19:50:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7RJo5Yn076680 for ; Mon, 27 Aug 2012 19:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7RJo5BQ076679; Mon, 27 Aug 2012 19:50:05 GMT (envelope-from gnats) Date: Mon, 27 Aug 2012 19:50:05 GMT Message-Id: <201208271950.q7RJo5BQ076679@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Mark Saad Cc: Subject: Re: kern/170680: [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEASE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Saad List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Aug 2012 19:50:05 -0000 The following reply was made to PR kern/170680; it has been noted by GNATS. From: Mark Saad To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/170680: [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEASE Date: Mon, 27 Aug 2012 15:41:47 -0400 This is a multi-part message in MIME format. --------------080001080802040503070409 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello In addendium to the MFC's noted in this pr please add this one as well, as it addresses a needed fix to the rpc subsystem . r227810 - stable/7/sys/rpc -- Mark Saad DataCenter Operations About.com | Need. Know. Accomplish. 249 West 17Th Street New York, NY, 10011 T: (212) 204-2620 F: (212) 620-0128 About.com is part of The New York Times Company O< ascii ribbon campaign - stop html mail - www.asciiribbon.org --------------080001080802040503070409 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 
Hello
  In addendium to the MFC's noted in this pr please add this one as well, as it addresses a needed fix to the rpc subsystem .
 
 r227810 - stable/7/sys/rpc
 
 -- 
 Mark Saad
 DataCenter Operations
 About.com | Need. Know. Accomplish.
 
 249 West 17Th Street
 New York, NY, 10011
 T: (212) 204-2620
 F: (212) 620-0128
 
 About.com is part of The New York Times Company
 
 O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
--------------080001080802040503070409-- From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 21:08:01 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0261F106564A for ; Mon, 27 Aug 2012 21:08:01 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C70318FC12 for ; Mon, 27 Aug 2012 21:08:00 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so8310513pbb.13 for ; Mon, 27 Aug 2012 14:08:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:date:message-id:subject:from:to:content-type; bh=7Pa/cN1iwn3cgFJt76gnPfIrpNQ6RfMY7lLRotgpS+c=; b=feubCJPV5TMOL7FwBokBsQXvY4Zo8DB0qNGtAqZFeyAXVDooyGwTKHnTUIqrucpPGj mHkQczwSvyhs0kueLOJxfpNt4dK3OLNgwWRpCLQXThw2vDXPm4zcYLypBGb3T4ubCZoO caV4roWlJED81rUagDvDMY+34gmhBfrmlQtsc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=7Pa/cN1iwn3cgFJt76gnPfIrpNQ6RfMY7lLRotgpS+c=; b=MZvMiJOGLjr2NM8LiuqIu0uYvhRqMRNHd6DiDC9S6+SvCKEBtlLt81WBgPV5TC7GHD 7Anf0TvAQwB2aLqO+EfhFD/Zh0JhE7YeYWlR4dVUjn+sW2E6fPQRo2HiP42zEm3sBa3B Vm9MNNSf/xZOC/3+e6oiLtevrz6VgWHkSoYpYGXeW+0bv8/vEU0No5dyvJ+1YqTxtgMu LSTOmyMYrAUS0H2HF1tJPyCP5OUNU6BsXOzEuAyJGlsDy1GGzw/6PkRQnVgYBDQv1TfJ u0Eda7wcRlf4x7BJEnx0SbVNzaKa5OljenAFmuzETdaZkz+8QFUroW1/WKg3dMO6Q6Cn 8WaQ== MIME-Version: 1.0 Received: by 10.66.83.8 with SMTP id m8mr32848572pay.48.1346101680365; Mon, 27 Aug 2012 14:08:00 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Mon, 27 Aug 2012 14:08:00 -0700 (PDT) Date: Mon, 27 Aug 2012 14:08:00 -0700 Message-ID: From: Tim Gustafson To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQljZfihIcBLvgF0IKZ5uEZCrvtl4TXV9HbmmF5r5IlucAUPNTSD6sbSdACjAkavK6AoK9pD Subject: ZFS snapshot Folder Disappearing 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, 27 Aug 2012 21:08:01 -0000 Hi, I have a FreeBSD 9.0-RELEASE box that's running ZFS with zpool version 28. I can't recall if this pool was upgraded from an earlier zpool version, or if it was created natively as a zpool version 28; is there any way to check that? I use snapshots for nightly backups. I went in today to test to see if the snapshots were working correctly, and I got the following: root@bsd-06: cd /tank/export/projects/www/.zfs/snapshot /tank/export/projects/www/.zfs/snapshot: Not a directory. I'm getting the same error when I try to cd into the snapshot folder on any of my filesystems that have snapshots. The zpool is healthy, reporting no errors, and was last scrubbed less than a month ago with no errors being reported. The server had been up for 51 days. This server does not currently have a cache drive installed, nor am I using de-dupe anywhere. Based on some Googling around that I did, I ran: zdb -d tank | grep % and came up empty-handed - no errors appear to be reported there. I do create and delete snapshots on a regular basis, and I saw some chatter that suggested that might be the culprit, but I don't know how else to check for that. I updated to 9.0-RELEASE-p4 and rebooted. The machine did not shut down properly, so I had to power-cycle it. Upon rebooting all the way, the snapshots came back, but I wonder if they'll disappear again after the next round of snapshot creation and removal? Before anyone asks: presently, it would be feasible to do a "zfs send" to back this system up, and then rebuild the pool an then do a "zfs receive" to restore it, but that will become problematic shortly. This server has 135TB of disks, and will probably be about half full some time during the next few months. I do have a mirror server with another 135TB of disks that I could use for that sort of backup/restore procedure, but it will be located at the far end of a 1GB network connection shortly, living about 50 miles away in a remote data closet, so backing up and restoring that much data will become more or less impossible. -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 21:35:09 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D667C106564A for ; Mon, 27 Aug 2012 21:35:09 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 908D38FC18 for ; Mon, 27 Aug 2012 21:35:09 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAHrnO1CDaFvO/2dsb2JhbABCA4YDtgCCIAEBAQQBAQEgJgUgCxsOAwMBAgECAg0ZAikBCR4IBggCBQQBHASHXQMMC6dfiTUFiVaBIYlnGoMegg+BEgOTKoIrgRSPAYJ/gUU X-IronPort-AV: E=Sophos;i="4.77,838,1336363200"; d="scan'208,217";a="179223099" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 27 Aug 2012 17:35:03 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 9C38CB3F93; Mon, 27 Aug 2012 17:35:02 -0400 (EDT) Date: Mon, 27 Aug 2012 17:35:02 -0400 (EDT) From: Rick Macklem To: Mark Saad Message-ID: <1793934539.1178555.1346103302619.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <201208271950.q7RJo5BQ076679@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@FreeBSD.org Subject: Re: kern/170680: [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEASE 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, 27 Aug 2012 21:35:09 -0000 Mark Saad wrote: > The following reply was made to PR kern/170680; it has been noted by > GNATS. > > From: Mark Saad > To: bug-followup@FreeBSD.org > Cc: > Subject: Re: kern/170680: [nfs] Multiple NFS Client bug in the FreeBSD > 7.4-RELEASE > Date: Mon, 27 Aug 2012 15:41:47 -0400 > > This is a multi-part message in MIME format. > --------------080001080802040503070409 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: 7bit > > Hello > In addendium to the MFC's noted in this pr please add this one as > well, as it addresses a needed fix to the rpc subsystem . > > r227810 - stable/7/sys/rpc > I'm not sure if you are aware of this, but normally afaik, only critical security fixes are MFC'd to a releng branch. Although re@ would be the final authority on this, I suspect that MFC'ng these to releng/7.4 is not likely to happen. If there are any of the fixes not already in stable/7, then email and I'll see what can be done about that, rick. > -- > Mark Saad > DataCenter Operations > About.com | Need. Know. Accomplish. > > 249 West 17Th Street > New York, NY, 10011 > T: (212) 204-2620 > F: (212) 620-0128 > > About.com is part of The New York Times Company > > O< ascii ribbon campaign - stop html mail - www.asciiribbon.org > > > --------------080001080802040503070409 > Content-Type: text/html; charset=ISO-8859-1 > Content-Transfer-Encoding: 7bit > > > > > > > > > 
Hello
> In addendium to the MFC's noted in this pr please add this one as
> well, as it addresses a needed fix to the rpc subsystem .
> 
> r227810 - stable/7/sys/rpc
> 
> --
> Mark Saad
> DataCenter Operations
> About.com | Need. Know. Accomplish.
> 
> 249 West 17Th Street
> New York, NY, 10011
> T: (212) 204-2620
> F: (212) 620-0128
> 
> About.com is part of The New York Times Company
> 
> O< ascii ribbon campaign - stop html mail -  class="moz-txt-link-abbreviated"
> href="http://www.asciiribbon.org">www.asciiribbon.org
>
> > > > --------------080001080802040503070409-- > _______________________________________________ > 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 Aug 27 21:54:16 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AC48E106564A for ; Mon, 27 Aug 2012 21:54:16 +0000 (UTC) (envelope-from claudiu.vasadi@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7E0A18FC15 for ; Mon, 27 Aug 2012 21:54:16 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so8369559pbb.13 for ; Mon, 27 Aug 2012 14:54:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wTeJT4pLiQiI/rWTij+aoUDAQECkSlOfx/G2ul4Udvo=; b=GE4rUnrmCpnDxpma3QCJP7x1ax+/sAwgeWlrHlE8j3di5T1YScA7CrynBfiS6RYvRA 4fYnl0Pw8j+2s+hpCcL5eMYQx3z+4DZZK42mxZ88RSRzX0FgEghQGH+7D4LljM52j8k1 +gRdZWti6Q+Aerflx4sEexsM8DWA8cE0f68WWD0Wfd8NsSTPxZZ0RWHCyZZ9zWZ0YaXT NchnGH5ispvL1XZN4tCU8ZMBFoGVqx8AAe2u+xVeyDUfDqTx1e1dX4oe3/D6c8Map30b aocI17ORVnPa16KdNKp0JJpCfQ+nX9uLVNuqhi6VyHiFnmOLolwonhhQlFgpFP/YvdY6 9nyA== MIME-Version: 1.0 Received: by 10.68.132.228 with SMTP id ox4mr37417084pbb.13.1346104455220; Mon, 27 Aug 2012 14:54:15 -0700 (PDT) Received: by 10.66.80.105 with HTTP; Mon, 27 Aug 2012 14:54:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 27 Aug 2012 23:54:15 +0200 Message-ID: From: claudiu vasadi To: Tim Gustafson 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 snapshot Folder Disappearing 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, 27 Aug 2012 21:54:16 -0000 On Mon, Aug 27, 2012 at 11:08 PM, Tim Gustafson wrote: > Hi, > > I have a FreeBSD 9.0-RELEASE box that's running ZFS with zpool version > 28. I can't recall if this pool was upgraded from an earlier zpool > version, or if it was created natively as a zpool version 28; is there > any way to check that? > > I use snapshots for nightly backups. I went in today to test to see > if the snapshots were working correctly, and I got the following: > > root@bsd-06: cd /tank/export/projects/www/.zfs/snapshot > /tank/export/projects/www/.zfs/snapshot: Not a directory. > > I'm getting the same error when I try to cd into the snapshot folder > on any of my filesystems that have snapshots. > > The zpool is healthy, reporting no errors, and was last scrubbed less > than a month ago with no errors being reported. The server had been > up for 51 days. This server does not currently have a cache drive > installed, nor am I using de-dupe anywhere. > > Based on some Googling around that I did, I ran: > > zdb -d tank | grep % > > and came up empty-handed - no errors appear to be reported there. > > I do create and delete snapshots on a regular basis, and I saw some > chatter that suggested that might be the culprit, but I don't know how > else to check for that. > > I updated to 9.0-RELEASE-p4 and rebooted. The machine did not shut > down properly, so I had to power-cycle it. Upon rebooting all the > way, the snapshots came back, but I wonder if they'll disappear again > after the next round of snapshot creation and removal? > > Before anyone asks: presently, it would be feasible to do a "zfs send" > to back this system up, and then rebuild the pool an then do a "zfs > receive" to restore it, but that will become problematic shortly. > This server has 135TB of disks, and will probably be about half full > some time during the next few months. I do have a mirror server with > another 135TB of disks that I could use for that sort of > backup/restore procedure, but it will be located at the far end of a > 1GB network connection shortly, living about 50 miles away in a remote > data closet, so backing up and restoring that much data will become > more or less impossible. > > -- > > Tim Gustafson > tjg@soe.ucsc.edu > 831-459-5354 > Baskin Engineering, Room 313A > _______________________________________________ > 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" > Hi, Did you try "zfs set snapdir=visible " ? -- Best regards, Claudiu Vasadi From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 22:01:51 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 27192106566B for ; Mon, 27 Aug 2012 22:01:51 +0000 (UTC) (envelope-from antonintessier@live.fr) Received: from dub0-omc4-s13.dub0.hotmail.com (dub0-omc4-s13.dub0.hotmail.com [157.55.2.88]) by mx1.freebsd.org (Postfix) with ESMTP id B6F998FC1F for ; Mon, 27 Aug 2012 22:01:50 +0000 (UTC) Received: from DUB109-W131 ([157.55.2.72]) by dub0-omc4-s13.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 27 Aug 2012 14:51:05 -0700 Message-ID: X-Originating-IP: [93.182.219.16] From: antonin tessier To: Date: Mon, 27 Aug 2012 23:51:06 +0200 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 27 Aug 2012 21:51:05.0675 (UTC) FILETIME=[0F1B29B0:01CD849E] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ZFS compression doesn't 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: Mon, 27 Aug 2012 22:01:51 -0000 Hello=2C I am trying to understand and use ZFS features. My issue is that compressio= n doesn't work=2C indeed I have a pool and a filesystem named "home" and "h= ome/compressed". #zfs list NAME USED AVAIL REFER MOUNTPOINT home 7.33G 180G 32K home home/compressed 7.33G 180G 7.33G /home/compressed despite I did: # zfs set compression=3Dgzip home/compressed I don't understand where it is wrong. Thank you. =20 = From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 22:08:39 2012 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 25B551065670; Mon, 27 Aug 2012 22:08:39 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id E7BC48FC16; Mon, 27 Aug 2012 22:08:38 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:100]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 6CF2B23F645; Mon, 27 Aug 2012 18:08:37 -0400 (EDT) Date: Mon, 27 Aug 2012 18:08:33 -0400 From: Glen Barber To: antonin tessier Message-ID: <20120827220833.GK1435@glenbarber.us> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sLx0z+5FKKtIVDwd" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS compression doesn't 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: Mon, 27 Aug 2012 22:08:39 -0000 --sLx0z+5FKKtIVDwd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 27, 2012 at 11:51:06PM +0200, antonin tessier wrote: >=20 > Hello, >=20 >=20 > I am trying to understand and use ZFS features. My issue is that > compression doesn't work, indeed I have a pool and a filesystem > named "home" and "home/compressed". > #zfs list >=20 > NAME USED AVAIL REFER MOUNTPOINT > home 7.33G 180G 32K home > home/compressed 7.33G 180G 7.33G /home/compressed >=20 > despite I did: > # zfs set compression=3Dgzip home/compressed >=20 > I don't understand where it is wrong. >=20 Did you set this at time the pool was created? If you set this after the pool already contained data, existing data is not compressed. Glen --sLx0z+5FKKtIVDwd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQO+/hAAoJEFJPDDeguUaj6KgH/0Aw+XpRedu/p2qpikhwjAOQ 8FSFlpRO6ZSRRHRUZXkZl8sp6L0xoyzEWsf4jIh8U5ChhgRIBJRMtl4zjTr2xJsY k2zYBmQBtBg78RK/5guhgABni7CwAaCg4Oi0h/MZbZ/5wTLR89uJK1jgr8Vl5vjB RIhj0e+J1uHmLBKljp/06Fu2topphoNMpiUuQxe4TawxzZlZNwtWtFL4hOCwa14V mZe6YPG+8uf8gDKf1nIh7/z60J+KoBJclJ/SFJXG0Pejw9rlipa/GPT0cpqeGYTi LmRy26cgIGXq66uYiSUxMFJq2B/FDj4g4gpBwgN+ntZWNAQJoZNVuqdYw3TaPpE= =J2E9 -----END PGP SIGNATURE----- --sLx0z+5FKKtIVDwd-- From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 22:15:37 2012 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 2796C106564A for ; Mon, 27 Aug 2012 22:15:37 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id AC2B48FC0A for ; Mon, 27 Aug 2012 22:15:35 +0000 (UTC) Received: from server.rulingia.com (c220-239-249-137.belrs5.nsw.optusnet.com.au [220.239.249.137]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q7RMFYbh052208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 28 Aug 2012 08:15:34 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q7RMFSZY069403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Aug 2012 08:15:28 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q7RMFSE5069402; Tue, 28 Aug 2012 08:15:28 +1000 (EST) (envelope-from peter) Date: Tue, 28 Aug 2012 08:15:28 +1000 From: Peter Jeremy To: antonin tessier Message-ID: <20120827221528.GA69174@server.rulingia.com> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS compression doesn't 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: Mon, 27 Aug 2012 22:15:37 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-27 23:51:06 +0200, antonin tessier wro= te: >I am trying to understand and use ZFS features. My issue is that compressi= on doesn't work, zfs compression definitely does work and you haven't explained why you think it doesn't. > NAME USED AVAIL REFER MOUNTPOINT > home 7.33G 180G 32K home > home/compressed 7.33G 180G 7.33G /home/compressed > >despite I did: ># zfs set compression=3Dgzip home/compressed Did you run that command before or after you copied the data into /home/compressed? How much data did you load into /home/compressed? How did you copy the data into /home/compressed? What is the result of "zfs get all home/compressed"? --=20 Peter Jeremy --jRHKVT23PllUwdXP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA78YAACgkQ/opHv/APuIdPuwCgru/YIcgjhqMAH5qhC5t44plR T/MAmwaJ6EZcsiVyOQR9fo++CQ2S7hhA =OB9r -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 23:33:50 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F16F106564A for ; Mon, 27 Aug 2012 23:33:50 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id DEA878FC08 for ; Mon, 27 Aug 2012 23:33:49 +0000 (UTC) Received: by dadr6 with SMTP id r6so2865566dad.13 for ; Mon, 27 Aug 2012 16:33:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kWmk61vYkYGIt6EPgquFVSWU+PJJhnpGKtCRY/sugJQ=; b=mTYeyVw7qxTLe/pjpvoASYaV6NV3KjhVCIRoqofVLB/E4RSH78qzhY6ZgdtunL7Q5i Ii/4c4cNmIDUL8XiWImcc5da5NWFGQmE9J9CLZFrgBEAUMGFL08uZgyzZdO9YOfQcRj5 iTNFT53ZtyJBTPvBkhLciuGRKioNXUIRUTBBc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=kWmk61vYkYGIt6EPgquFVSWU+PJJhnpGKtCRY/sugJQ=; b=EPw3QgRICw4/sViTQREKTsGQKeLudT9AQ3xkpeZGsQt197ygFsBkLzNsQ3mt/mwDIT Yq7cVm6sy/o76D28gljaV0uRxiWEUFfxwBL+oDwmGOsFrrdBq4hFMkyYRibptQqg9YBr 1XJcyRHep/iH4DTFSlRk8T6ZW/0/eFejeg7kf3WKkMDcIgdmr3c2w66Cc/nWJF3rHRz6 UkYMoEM+PGDM39w/EgtsoZ5I6JPurpUCkmGB7Iyuaoc1kGmJMFYfGIC7k86S7PFXzhjL 5H7SIInzJzwFyd6i76HKbQH77FyR5pVJ7PdcvFPrWGur8w93MYMSg4bypUrHNFDIWNCK 6VDw== MIME-Version: 1.0 Received: by 10.66.77.71 with SMTP id q7mr33692462paw.0.1346110429451; Mon, 27 Aug 2012 16:33:49 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Mon, 27 Aug 2012 16:33:49 -0700 (PDT) In-Reply-To: References: Date: Mon, 27 Aug 2012 16:33:49 -0700 Message-ID: From: Tim Gustafson To: claudiu vasadi Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQly/+7COKG/SfMxqnt72xXUMPJljt1MBOPl4Rrpn+CfPBlGntaavFWqozo1W5C+eIugoRop Cc: freebsd-fs@freebsd.org Subject: Re: ZFS snapshot Folder Disappearing 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, 27 Aug 2012 23:33:50 -0000 > Did you try "zfs set snapdir=visible " ? I did not, but I never set them to be invisible either, and also when I did: ls -al /tank/export/projects/www/.zfs I saw a "snapshot" folder listed there; it was only when I tried: ls -al /tank/export/projects/www/.zfs/snapshot that I got the "Not a directory" message. -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 22:24:18 2012 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 F41F81065673 for ; Mon, 27 Aug 2012 22:24:17 +0000 (UTC) (envelope-from Dave.Robison@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id BE20A8FC1A for ; Mon, 27 Aug 2012 22:24:17 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa04.fnfis.com (8.14.4/8.14.4) with ESMTP id q7RMOAgT028903 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Mon, 27 Aug 2012 17:24:10 -0500 Received: from lefty.vicor.com (10.14.152.57) by smtp.fisglobal.com (10.132.206.15) with Microsoft SMTP Server (TLS) id 14.2.309.2; Mon, 27 Aug 2012 17:24:10 -0500 Message-ID: <503BF387.2080309@fisglobal.com> Date: Mon, 27 Aug 2012 15:24:07 -0700 From: "Robison, Dave" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0) Gecko/20120209 Thunderbird/10.0 MIME-Version: 1.0 To: References: <20120827221528.GA69174@server.rulingia.com> In-Reply-To: <20120827221528.GA69174@server.rulingia.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.14.152.57] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.428, 0.0.0000 definitions=2012-08-27_02:2012-08-27, 2012-08-27, 1970-01-01 signatures=0 X-Mailman-Approved-At: Mon, 27 Aug 2012 23:43:56 +0000 Subject: Re: ZFS compression doesn't work X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: david.robison@fisglobal.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Aug 2012 22:24:18 -0000 On 08/27/2012 15:15, Peter Jeremy wrote: > On 2012-Aug-27 23:51:06 +0200, antonin tessier wrote: >> I am trying to understand and use ZFS features. My issue is that compression doesn't work, Not sure what "compression=gzip" will give you. I believe you might be safer using "compression=gzip-6" or whichever value you want to use. gzip9 will be pretty slow if that's the default for "gzip". I use lzjb because there isn't much advantage to gzip, at least in my experience, and lzjb is fast. I did some testing and didn't find a big space savings with gzip-6 or gzip-9. % zfs get compressratio NAME PROPERTY VALUE SOURCE raid1 compressratio 1.78x - raid1/BACKUPS/BACULA compressratio 1.83x - -- Dave Robison Sales Solution Architect II FIS Banking Solutions 510/621-2089 (w) 530/518-5194 (c) 510/621-2020 (f) daver@vicor.com david.robison@fisglobal.com _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 23:48:32 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52ED0106566C; Mon, 27 Aug 2012 23:48:32 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 1F3328FC12; Mon, 27 Aug 2012 23:48:32 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:100]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id B319C23F645; Mon, 27 Aug 2012 19:48:29 -0400 (EDT) Date: Mon, 27 Aug 2012 19:48:25 -0400 From: Glen Barber To: "Robison, Dave" Message-ID: <20120827234825.GN1435@glenbarber.us> References: <20120827221528.GA69174@server.rulingia.com> <503BF387.2080309@fisglobal.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="T4IYkFBVPN84tP7K" Content-Disposition: inline In-Reply-To: <503BF387.2080309@fisglobal.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS compression doesn't 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: Mon, 27 Aug 2012 23:48:32 -0000 --T4IYkFBVPN84tP7K Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 27, 2012 at 03:24:07PM -0700, Robison, Dave wrote: > On 08/27/2012 15:15, Peter Jeremy wrote: > > On 2012-Aug-27 23:51:06 +0200, antonin tessier = wrote: > >> I am trying to understand and use ZFS features. My issue is that compr= ession doesn't work, >=20 > Not sure what "compression=3Dgzip" will give you. I believe you might be > safer using "compression=3Dgzip-6" or whichever value you want to use. > gzip9 will be pretty slow if that's the default for "gzip". >=20 zfs(8) states: compression=3Don | off | lzjb | gzip | gzip-N | zle [...] You can specify the gzip level by using the value gzip-N where N is an integer from 1 (fastest) to 9 (best compression ratio). Currently, gzip is equivalent to gzip-6 (which is also the default for gzip(1)). > I use lzjb because there isn't much advantage to gzip, at least in my > experience, and lzjb is fast. I did some testing and didn't find a big > space savings with gzip-6 or gzip-9. >=20 gzip-9 will gain you almost no additional compression over gzip-6, and will certainly cost more CPU cycles. See gzip(1). Glen --T4IYkFBVPN84tP7K Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQPAdJAAoJEFJPDDeguUajhz0IALONOB87xeUHAf81oC6f78PK ceSPkPfesgF6Igs3B+U666DonAcPhktXAWILxmhZFGoywYw9fSIN6yJnKhfW/lqk bqIK54z64W2TaYusSl4wjwgJpjuKQP5Ex9YatIW+S/8DbnTj5Bp3Zu4HATfWVrbV gUQoXCiLcqORCsUxFn31RW4QFw18Sf0PGqjO3kNF62SQjZLDQp5SIP3n0wrXH4C6 LSm91ulEpuxANeOIAAdRrwLiWKQD4AeASKfqtkVZKYr6S5P/W/fOIaUnm6tqu/CR 5B67OHl9g7tdblIWsND3J44j1t+ikUszhsbE/OEmifTdmHm/STmXMdfnxLisblM= =KCrw -----END PGP SIGNATURE----- --T4IYkFBVPN84tP7K-- From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 23:49:44 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 556A51065670 for ; Mon, 27 Aug 2012 23:49:44 +0000 (UTC) (envelope-from freebsd@pki2.com) Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2]) by mx1.freebsd.org (Postfix) with ESMTP id 22AB78FC12 for ; Mon, 27 Aug 2012 23:49:44 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by btw.pki2.com (8.14.5/8.14.5) with ESMTP id q7RNnbcc024334 for ; Mon, 27 Aug 2012 16:49:37 -0700 (PDT) (envelope-from freebsd@pki2.com) From: Dennis Glatting To: freebsd-fs@freebsd.org In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Date: Mon, 27 Aug 2012 16:49:37 -0700 Message-ID: <1346111377.85365.5.camel@btw.pki2.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-yoursite-MailScanner-Information: Dennis Glatting X-yoursite-MailScanner-ID: q7RNnbcc024334 X-yoursite-MailScanner: Found to be clean X-MailScanner-From: freebsd@pki2.com Subject: Re: ZFS compression doesn't 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: Mon, 27 Aug 2012 23:49:44 -0000 On Mon, 2012-08-27 at 23:51 +0200, antonin tessier wrote: > Hello, > > > I am trying to understand and use ZFS features. My issue is that compression doesn't work, indeed I have a pool and a filesystem named "home" and "home/compressed". > #zfs list > > NAME USED AVAIL REFER MOUNTPOINT > home 7.33G 180G 32K home > home/compressed 7.33G 180G 7.33G /home/compressed > > despite I did: > # zfs set compression=gzip home/compressed > > I don't understand where it is wrong. > Compression works. I use it extensively. > Thank you. > > _______________________________________________ > 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 Aug 28 02:46:47 2012 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 DD834106564A; Tue, 28 Aug 2012 02:46:47 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward5.mail.yandex.net (forward5.mail.yandex.net [IPv6:2a02:6b8:0:602::5]) by mx1.freebsd.org (Postfix) with ESMTP id 560A28FC18; Tue, 28 Aug 2012 02:46:47 +0000 (UTC) Received: from smtp4.mail.yandex.net (smtp4.mail.yandex.net [77.88.46.104]) by forward5.mail.yandex.net (Yandex) with ESMTP id BE06912019B6; Tue, 28 Aug 2012 06:46:45 +0400 (MSK) Received: from smtp4.mail.yandex.net (localhost [127.0.0.1]) by smtp4.mail.yandex.net (Yandex) with ESMTP id 9B1E15C056D; Tue, 28 Aug 2012 06:46:45 +0400 (MSK) Received: from ns.kirov.so-ups.ru (ns.kirov.so-ups.ru [178.74.170.1]) by smtp4.mail.yandex.net (nwsmtp/Yandex) with ESMTP id ki9W23H2-kj9in9Fh; Tue, 28 Aug 2012 06:46:45 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1346122005; bh=T7uJpLEAqCIH0T8Dl9VyPy6pW3SkMoWz57UFOU0iLfA=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=hxT9+SqWfwBdkTnpiTvk7ViBmy/H5XLOm/xQz94EWDOxKcnKAeQpeEHYQr9B8EjWP HIjEml3IL3q0kXNa3rWqA2UfpkQEN0zd7tyYwibmC2FGwzgDVZkCsdWLyD8uujkk9J fIwltazl77vIsLmBH6R5Du+YrUQYbUIKRW7Ggicc= Message-ID: <503C3114.3080000@yandex.ru> Date: Tue, 28 Aug 2012 06:46:44 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Jeremie Le Hen References: <20120827070210.GA798@felucia.tataz.chchile.org> <503B4521.9080603@yandex.ru> <20120827150648.GE32062@felucia.tataz.chchile.org> In-Reply-To: <20120827150648.GE32062@felucia.tataz.chchile.org> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: Cannot get zfsboot prompt 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, 28 Aug 2012 02:46:48 -0000 On 27.08.2012 19:06, Jeremie Le Hen wrote: >> I guess your ada0s1a partition has non zero offset, and second >> part of zfsboot bootcode has been written into wrong place. >> >> AFAIK, the first part of the zfsboot does read the second part >> from the 1024 sector of the active FreeBSD slice in the MBR. > > Yes I agree this is probably where the catch is. But note that contrary > to your procedure, I laid zfsboot2 from ada0s1a. > > The first partition of my BSD label indeed starts at sector 1. > > rescue-bsd# gpart show ada0s1 > => 0 1953525105 ada0s1 BSD (931G) > 0 1 - free - (512B) > 1 1951799000 1 freebsd-zfs (930G) > 1951799001 1726096 4 freebsd-swap (842M) > 1953525097 8 - free - (4.0k) > >>From what I undestand from sys/boot/i386/zfsboot/zfsldr.S, zfsboot1 > expects zfsboot2 to be at offset 1024 for the start of the first FreeBSD > (0xA5) MBR active slice (fall-back to non-active). 1024 sectors is not > chosen randomly, this is because in zpools, the boot block is located > after the two heading vdev label replicas which are 256KB each. > > Given my partition in shifted by one sector, zfsboot2 is shifted by one > sector as well so zfsboot1 doesn't find it. > > Do you know if this topic is documented somewhere? I couldn't find > anything when I needed it. > > Also, why does gpart(8) enforce a one sector offset for partition inside > a BSD scheme? I tried to set an offset to 0 without any effect. Probably your disk has 4k sectors and gpart did an automatic alignment. You can disable automatic alignment by specifying "-a 1" when you create partition. But it will be better if you create BSD slice already aligned. The problem is that automatic alignment doesn't work with MBR :) You need to calculate start offset based on disk geometry and sectorsize. # gpart list ada0 | grep fwsectors I think you will get 63, so your alignment value will be 63*8 = 504. To create aligned BSD slice you can use this command: # gpart add -t freebsd -a 504 ada0 -- WBR, Andrey V. Elsukov From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 06:03:40 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4ADD5106566B for ; Tue, 28 Aug 2012 06:03:40 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id C5D5E8FC1C for ; Tue, 28 Aug 2012 06:03:39 +0000 (UTC) Received: from seedling.local (host86-182-42-128.range86-182.btcentralplus.com [86.182.42.128]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id q7S63TXK092658 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 28 Aug 2012 07:03:30 +0100 (BST) (envelope-from matthew@FreeBSD.org) X-DKIM: OpenDKIM Filter v2.5.2 smtp.infracaninophile.co.uk q7S63TXK092658 Authentication-Results: smtp.infracaninophile.co.uk/q7S63TXK092658; dkim=none (no signature); dkim-adsp=none X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host host86-182-42-128.range86-182.btcentralplus.com [86.182.42.128] claimed to be seedling.local Message-ID: <503C5F2A.701@FreeBSD.org> Date: Tue, 28 Aug 2012 07:03:22 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Tim Gustafson References: In-Reply-To: X-Enigmail-Version: 1.4.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigCAEF7D1AF347D1273FCC0948" X-Virus-Scanned: clamav-milter 0.97.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=4.4 required=5.0 tests=BAYES_00,RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Level: **** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS snapshot Folder Disappearing 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, 28 Aug 2012 06:03:40 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCAEF7D1AF347D1273FCC0948 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 28/08/2012 00:33, Tim Gustafson wrote: >> Did you try "zfs set snapdir=3Dvisible " ? >=20 > I did not, but I never set them to be invisible either, and also when I= did: >=20 > ls -al /tank/export/projects/www/.zfs >=20 > I saw a "snapshot" folder listed there; it was only when I tried: >=20 > ls -al /tank/export/projects/www/.zfs/snapshot >=20 > that I got the "Not a directory" message. I got bitten by this. It seemed to be triggered by cvsup'ing the Ports CVS repo -- ever since the switch to SVN it hasn't bothered me at all. Anyhow, to the point: I first noticed this on a zpool which was built under 8.1 originally, and had since tracked 8-STABLE and then 9-STABLE. I tried a bunch of things to see if I could make the problem go away, including the nuclear option: splitting the mirror, wiping one of the drives, building a whole new zpool on it, using send..recv to move the data over, reboot onto the new zpool, wipe original disk then add it to the new zpool as the other half of a mirror. Didn't work. Whatever the problem is, I believe it is still present in the latest ZFS code. (Can't say for sure because like I said, I'm simply not running the sort of IO patterns that would trigger the problem any more.) There's a PR for this somewhere (not created by me), but I can't find it in my records right now. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --------------enigCAEF7D1AF347D1273FCC0948 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlA8XzEACgkQ8Mjk52CukIxJgwCghHwyXburxIhkDpUQz5ZvZ7l9 wEUAoIdmFQ0g4alFRRJ4hnumgthPe0DV =goLF -----END PGP SIGNATURE----- --------------enigCAEF7D1AF347D1273FCC0948-- From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 06:20:48 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52AC7106564A; Tue, 28 Aug 2012 06:20:48 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from micro.madpilot.net (micro.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id E128D8FC19; Tue, 28 Aug 2012 06:20:47 +0000 (UTC) Received: from micro.madpilot.net (localhost [127.0.0.1]) by micro.madpilot.net (Postfix) with ESMTP id 3X5fwZ2gLVz28x; Tue, 28 Aug 2012 08:20:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=mail; t=1346134843; x=1347949244; bh=kR44LED0s+6tUl1OO7HmaCDybfqPyKcaLZIRMv1/iSw=; b= WwUJkyjQVeVxziVAox81KiR1Pf5XLUA62fI42oWl4EBHBijIWzmSY0frbrzqhvD+ j5ToJjuy5yulHlNQWO0IsmWzqms/1iXf4w+JB0iEkQl5D4e76ASfJr/stN3+o3cd 3Ffyoou+XgtRrTvSyR4cGnf++YWvBqlIhS+bYkt3AMU= X-Virus-Scanned: amavisd-new at madpilot.net Received: from micro.madpilot.net ([127.0.0.1]) by micro.madpilot.net (micro.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rg_NYEp0ATvs; Tue, 28 Aug 2012 08:20:43 +0200 (CEST) Received: from marvin.madpilot.net (localhost [127.0.0.1]) by micro.madpilot.net (Postfix) with ESMTP; Tue, 28 Aug 2012 08:20:43 +0200 (CEST) Message-ID: <503C633B.2070508@madpilot.net> Date: Tue, 28 Aug 2012 08:20:43 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120727 Thunderbird/14.0 MIME-Version: 1.0 To: Matthew Seaman References: <503C5F2A.701@FreeBSD.org> In-Reply-To: <503C5F2A.701@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS snapshot Folder Disappearing 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, 28 Aug 2012 06:20:48 -0000 On 08/28/12 08:03, Matthew Seaman wrote: > On 28/08/2012 00:33, Tim Gustafson wrote: >>> Did you try "zfs set snapdir=visible " ? >> >> I did not, but I never set them to be invisible either, and also when I did: >> >> ls -al /tank/export/projects/www/.zfs >> >> I saw a "snapshot" folder listed there; it was only when I tried: >> >> ls -al /tank/export/projects/www/.zfs/snapshot >> >> that I got the "Not a directory" message. > > I got bitten by this. It seemed to be triggered by cvsup'ing the Ports > CVS repo -- ever since the switch to SVN it hasn't bothered me at all. > > Anyhow, to the point: I first noticed this on a zpool which was built > under 8.1 originally, and had since tracked 8-STABLE and then 9-STABLE. > I tried a bunch of things to see if I could make the problem go away, > including the nuclear option: splitting the mirror, wiping one of the > drives, building a whole new zpool on it, using send..recv to move the > data over, reboot onto the new zpool, wipe original disk then add it to > the new zpool as the other half of a mirror. > > Didn't work. Whatever the problem is, I believe it is still present in > the latest ZFS code. (Can't say for sure because like I said, I'm > simply not running the sort of IO patterns that would trigger the > problem any more.) > > There's a PR for this somewhere (not created by me), but I can't find it > in my records right now. > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/156781 I got hit by this a few times too. Ti me it looks like it's easier to get this problem on more low spec machines(low spec regarding ZFS, so anything under 3-4 GiB ram is on the low side, for example). Using nullfs across snapshots did trigger this easily. I did that to have a nullfs mounted snapshot of the whole filesystem structure. I'm using read only zfs clones for that now. -- Guido Falsi From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 06:36:01 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 349F2106567A for ; Tue, 28 Aug 2012 06:36:01 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 8C1CF8FC16 for ; Tue, 28 Aug 2012 06:36:00 +0000 (UTC) Received: from seedling.local (host86-182-42-128.range86-182.btcentralplus.com [86.182.42.128]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id q7S6ZsuK093162 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 28 Aug 2012 07:35:55 +0100 (BST) (envelope-from matthew@FreeBSD.org) X-DKIM: OpenDKIM Filter v2.5.2 smtp.infracaninophile.co.uk q7S6ZsuK093162 Authentication-Results: smtp.infracaninophile.co.uk/q7S6ZsuK093162; dkim=none (no signature); dkim-adsp=none X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host host86-182-42-128.range86-182.btcentralplus.com [86.182.42.128] claimed to be seedling.local Message-ID: <503C66C2.5010209@FreeBSD.org> Date: Tue, 28 Aug 2012 07:35:46 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Guido Falsi References: <503C5F2A.701@FreeBSD.org> <503C633B.2070508@madpilot.net> In-Reply-To: <503C633B.2070508@madpilot.net> X-Enigmail-Version: 1.4.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0D058A0B5A8D03E22B6715A5" X-Virus-Scanned: clamav-milter 0.97.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS snapshot Folder Disappearing 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, 28 Aug 2012 06:36:01 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0D058A0B5A8D03E22B6715A5 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 28/08/2012 07:20, Guido Falsi wrote: >> >> There's a PR for this somewhere (not created by me), but I can't find = it >> in my records right now. >> >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/156781 That's the one. > I got hit by this a few times too. Ti me it looks like it's easier to > get this problem on more low spec machines(low spec regarding ZFS, so > anything under 3-4 GiB ram is on the low side, for example). My machine has 8GB RAM which I wouldn't call low spec particularly. > Using nullfs across snapshots did trigger this easily. I did that to > have a nullfs mounted snapshot of the whole filesystem structure. I'm > using read only zfs clones for that now. Interesting. I do have certain ZFSes null-mounted into a jail. I wonder if that's a common factor? Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --------------enig0D058A0B5A8D03E22B6715A5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlA8ZsoACgkQ8Mjk52CukIx0TwCglYv9Kq5C++TXB7Ntrz5jaJHu fLEAnRH1smzDdgSGzREX3raFJu+99hsK =u7ZA -----END PGP SIGNATURE----- --------------enig0D058A0B5A8D03E22B6715A5-- From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 08:09:21 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 61445106564A for ; Tue, 28 Aug 2012 08:09:21 +0000 (UTC) (envelope-from antonintessier@live.fr) Received: from dub0-omc2-s9.dub0.hotmail.com (dub0-omc2-s9.dub0.hotmail.com [157.55.1.148]) by mx1.freebsd.org (Postfix) with ESMTP id D29168FC19 for ; Tue, 28 Aug 2012 08:09:20 +0000 (UTC) Received: from DUB109-W81 ([157.55.1.137]) by dub0-omc2-s9.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 28 Aug 2012 01:04:29 -0700 Message-ID: X-Originating-IP: [93.182.219.16] From: antonin tessier To: Date: Tue, 28 Aug 2012 10:04:29 +0200 Importance: Normal In-Reply-To: <20120827221528.GA69174@server.rulingia.com> References: , <20120827221528.GA69174@server.rulingia.com> MIME-Version: 1.0 X-OriginalArrivalTime: 28 Aug 2012 08:04:29.0121 (UTC) FILETIME=[BFAB5B10:01CD84F3] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: RE: ZFS compression doesn't 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: Tue, 28 Aug 2012 08:09:21 -0000 > >despite I did: > ># zfs set compression=3Dgzip home/compressed >=20 > Did you run that command before or after you copied the data into > /home/compressed? >=20 > How much data did you load into /home/compressed? >=20 > How did you copy the data into /home/compressed? >=20 > What is the result of "zfs get all home/compressed"? I did it after the data was copied=3B /home/compressed now contains 7.5 Gio=3B "zfs get all home/compressed" tells me "NAME PROPERTY = VALUE SOURCE home/compressed type filesystem - home/compressed creation Mon Aug 27 13:49 2012 - home/compressed used 7.32G - home/compressed available 180G - home/compressed referenced 7.32G - home/compressed compressratio 1.05x - home/compressed mounted yes - home/compressed quota none default home/compressed reservation none default home/compressed recordsize 128K default home/compressed mountpoint /home/compressed default home/compressed sharenfs off default home/compressed checksum on default home/compressed compression lzjb local home/compressed atime on default home/compressed devices on default home/compressed exec on default home/compressed setuid on default home/compressed readonly off default home/compressed jailed off default home/compressed snapdir hidden default home/compressed aclmode discard default home/compressed aclinherit restricted default home/compressed canmount on default home/compressed xattr off temporary home/compressed copies 1 default home/compressed version 5 - home/compressed utf8only off - home/compressed normalization none - home/compressed casesensitivity sensitive - home/compressed vscan off default home/compressed nbmand off default home/compressed sharesmb off default home/compressed refquota none default home/compressed refreservation none default home/compressed primarycache all default home/compressed secondarycache all default home/compressed usedbysnapshots 0 - home/compressed usedbydataset 7.32G - home/compressed usedbychildren 0 - home/compressed usedbyrefreservation 0 - home/compressed logbias latency default home/compressed dedup off default home/compressed mlslabel - home/compressed sync standard default home/compressed refcompressratio 1.05x - home/compressed written 7.32G -" Ending=2C if I change gzip into lzjb=2C will my data by compress this new w= ay ? Thank you. = From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 08:13:51 2012 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 94FE0106564A; Tue, 28 Aug 2012 08:13:51 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from micro.madpilot.net (micro.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 2C47A8FC15; Tue, 28 Aug 2012 08:13:51 +0000 (UTC) Received: from micro.madpilot.net (localhost [127.0.0.1]) by micro.madpilot.net (Postfix) with ESMTP id 3X5jR175TMz29D; Tue, 28 Aug 2012 10:13:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received; s=mail; t=1346141624; x= 1347956025; bh=I12sSkfX5OeQPF5FNaMHIgvL5bEspIjRj3fAPKmFgr0=; b=V GrvwNlgj/7tgl/t4mE16fZrrv6vmHzE5jXqWE6QdtT72iTaogF/lZ8s6RY+GdVxc aFfHVui6wU7mJoAAQ7fI4VE+tJnqHhllC0Ove8aPScqOxAofBjdAuGx5t8UBjFRr e/kjmzRUemGh5Fc5J3KdPQybzuj9nD2ldhecQlOxew= X-Virus-Scanned: amavisd-new at madpilot.net Received: from micro.madpilot.net ([127.0.0.1]) by micro.madpilot.net (micro.madpilot.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id VzDkTgpxqilb; Tue, 28 Aug 2012 10:13:44 +0200 (CEST) Received: by micro.madpilot.net (Postfix, from userid 1000) id 3X5jQw2rdJz29C; Tue, 28 Aug 2012 10:13:44 +0200 (CEST) Date: Tue, 28 Aug 2012 10:13:44 +0200 From: Guido Falsi To: Matthew Seaman Message-ID: <20120828081344.GA20350@micro.madpilot.net> References: <503C5F2A.701@FreeBSD.org> <503C633B.2070508@madpilot.net> <503C66C2.5010209@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <503C66C2.5010209@FreeBSD.org> X-Operating-System: FreeBSD 9.1-PRERELEASE User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS snapshot Folder Disappearing 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, 28 Aug 2012 08:13:51 -0000 On Tue, Aug 28, 2012 at 07:35:46AM +0100, Matthew Seaman wrote: > > I got hit by this a few times too. Ti me it looks like it's easier to > > get this problem on more low spec machines(low spec regarding ZFS, so > > anything under 3-4 GiB ram is on the low side, for example). > > My machine has 8GB RAM which I wouldn't call low spec particularly. No, Definitely not. But in my experience when I have upgraded machines showing this problem it's frequency decreased a lot. > > > Using nullfs across snapshots did trigger this easily. I did that to > > have a nullfs mounted snapshot of the whole filesystem structure. I'm > > using read only zfs clones for that now. > > Interesting. I do have certain ZFSes null-mounted into a jail. I > wonder if that's a common factor? That could be a common trigger in my opinion, but it just exposes some other problem. I know very little about ZFS internals so I have been unable to dig any further. -- Guido Falsi From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 08:18:10 2012 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 E0172106564A for ; Tue, 28 Aug 2012 08:18:10 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9C5748FC15 for ; Tue, 28 Aug 2012 08:18:10 +0000 (UTC) Received: by obbun3 with SMTP id un3so13053739obb.13 for ; Tue, 28 Aug 2012 01:18:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QWxG2hOxBtufxEz2USMPR84XHIpegalkQAPmmFMfMho=; b=gy+OrGeF9FhYJlGfxDZpg3Cyh3FxE5FqN6V1UtJW9HPLh7QY4q9FlCpIYbIGMjRc1D vlYW8x22QVkzKU3xf8qnbUnRgVJmZXq3PzQaFLCuKGZLoAQsfKXeyS9xlygTZ6cBIdGu Od6kOLbVfXgtno9EYZSXU74hFEowy2By9wheP3YmmXPcRQ8a5E1A/DcSqkJusF12mESG ZuRuWCUKZuSeBXfpuaPFKoEADzLB/wb8xRJqh/LTtZF+ccJ0+LBzHLVFc+JUPH6fm3CB KpHDiejv39ZTPcbVk7nAb0y7P0DnvoM8oRRo1FmBpi5vl1x93lZaypQFE7dz8DMTQqQ1 Uw5g== MIME-Version: 1.0 Received: by 10.182.1.72 with SMTP id 8mr11735406obk.61.1346141890133; Tue, 28 Aug 2012 01:18:10 -0700 (PDT) Received: by 10.60.46.165 with HTTP; Tue, 28 Aug 2012 01:18:10 -0700 (PDT) In-Reply-To: References: <20120827221528.GA69174@server.rulingia.com> Date: Tue, 28 Aug 2012 10:18:10 +0200 Message-ID: From: Andreas Nilsson To: antonin tessier 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 compression doesn't 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: Tue, 28 Aug 2012 08:18:11 -0000 On Tue, Aug 28, 2012 at 10:04 AM, antonin tessier wrote: > > > >despite I did: > > ># zfs set compression=gzip home/compressed > > > > Did you run that command before or after you copied the data into > > /home/compressed? > > > > How much data did you load into /home/compressed? > > > > How did you copy the data into /home/compressed? > > > > What is the result of "zfs get all home/compressed"? > > > I did it after the data was copied; > /home/compressed now contains 7.5 Gio; > > "zfs get all home/compressed" tells me "NAME PROPERTY > VALUE SOURCE > home/compressed type filesystem - > home/compressed creation Mon Aug 27 13:49 2012 - > home/compressed used 7.32G - > home/compressed available 180G - > home/compressed referenced 7.32G - > home/compressed compressratio 1.05x - > home/compressed mounted yes - > home/compressed quota none default > home/compressed reservation none default > home/compressed recordsize 128K default > home/compressed mountpoint /home/compressed default > home/compressed sharenfs off default > home/compressed checksum on default > home/compressed compression lzjb local > home/compressed atime on default > home/compressed devices on default > home/compressed exec on default > home/compressed setuid on default > home/compressed readonly off default > home/compressed jailed off default > home/compressed snapdir hidden default > home/compressed aclmode discard default > home/compressed aclinherit restricted default > home/compressed canmount on default > home/compressed xattr off temporary > home/compressed copies 1 default > home/compressed version 5 - > home/compressed utf8only off - > home/compressed normalization none - > home/compressed casesensitivity sensitive - > home/compressed vscan off default > home/compressed nbmand off default > home/compressed sharesmb off default > home/compressed refquota none default > home/compressed refreservation none default > home/compressed primarycache all default > home/compressed secondarycache all default > home/compressed usedbysnapshots 0 - > home/compressed usedbydataset 7.32G - > home/compressed usedbychildren 0 - > home/compressed usedbyrefreservation 0 - > home/compressed logbias latency default > home/compressed dedup off default > home/compressed mlslabel - > home/compressed sync standard default > home/compressed refcompressratio 1.05x - > home/compressed written 7.32G -" > > Ending, if I change gzip into lzjb, will my data by compress this new way ? > > Thank you. > > Only data added after you set compression=on or change compression=gzip|lzjb will be compressed. Best regards Andreas From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 09:10:29 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4FD7E106564A for ; Tue, 28 Aug 2012 09:10:29 +0000 (UTC) (envelope-from mailinglists@nobaq.net) Received: from mail.nobaq.net (mail.nobaq.net [IPv6:2001:7b8:3cd:3::172]) by mx1.freebsd.org (Postfix) with ESMTP id AC6698FC17 for ; Tue, 28 Aug 2012 09:10:28 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=mail.nobaq.net) by mail.nobaq.net with esmtp (Exim 4.72) (envelope-from ) id 1T6HoX-0004hp-RZ; Tue, 28 Aug 2012 11:10:26 +0200 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=nobaq.net; h=message-id :date:from:mime-version:to:cc:references:in-reply-to :content-type:content-transfer-encoding:subject; s=n200908; bh=B 6IBsIYK36jt3a/BMry6w3/wsFI=; b=fB/3FsyKWdR1l0ORwjAz+sG0RHHOxKk5d RQ06IMZuGD9y1uyqLwewgvX+R3psF4I0tMfjwFNZXTzGk2SX49VUCRMruhHlRhp7 cOJKggevMp/VBDluTaUXIGLNu2gYmB8qWPJ4qy8nUP+bfZpKPZzCiFNhF2UHvTCI gkxls44xuo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=nobaq.net; h=message-id:date :from:mime-version:to:cc:references:in-reply-to:content-type :content-transfer-encoding:subject; q=dns; s=n200908; b=To5v4FKK hD//oHEgwaiiftjAxMhCrJptUHV35Up58o5d+g7im90qfyLnQU4jL+egn+fvyOTx 3kZ8diets0kv2W8Z6jph7vMAEQocITmDgAL+bP1CWTKiKxdc1djIto1oSogYUdXE t/qDeCrdZAC4p1X6dw5ZQUanjhVtYvHPEkc= Received: from gate.nobaq.net ([93.83.102.170] helo=[192.168.200.202]) by mail.nobaq.net with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1T6Ho9-0004hX-1K; Tue, 28 Aug 2012 11:10:25 +0200 Message-ID: <503C8AEE.1090703@nobaq.net> Date: Tue, 28 Aug 2012 11:10:06 +0200 From: Niki Hammler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Freddie Cash References: <503A6F9F.7070801@nobaq.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.nobaq.net X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: mailinglists@nobaq.net X-SA-Exim-Scanned: No (on mail.nobaq.net); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org Subject: Re: zvol + raidz issue? 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, 28 Aug 2012 09:10:29 -0000 Am 26.08.2012 22:13, schrieb Freddie Cash: > (Sorry for top-post, sending from phone.) > > Please show the command-line used to create the zvol. Especially the > recordsize option. When using zvols, you have to make sure to match the > recordsize of the zvol to that of the filesystem used above it. > Otherwise, performance will be atrocious. Hi, Sorry for my third posting on this. Now I strictly followed your suggestion and used zfs create -b 128k -V 500g plvl5i0/zvtest (with 128k being the recordsize of the dataset in the zpool). Suddenly the write performance increased from the 2.5 MB/s to 250 MB/s (or 78MB/s when using bs=4096 with dd) 1.) How can this explained? 2.) Is there any problem when choosing -b 128k (can I always blindly choose -b 128k)? Remember again that the problem ONLY occurs with raidz1+zvol+force 4096 block alignment and in no other case! Regards Niki > On Aug 26, 2012 11:50 AM, "Niki Hammler" > wrote: > > Hi, > > Given: new HP Proliant Microserver N40L (4 GB RAM) and 3x2TB SATA drives > (SAMSUNG HD204UI, ST32000542AS, WDC WD20EARX-00PASB0). > > Goal: RAIDz1 containg datasets and zvols to be exported via iSCSI. > > Issue: When I create a zvol on a RAIDz1 I get horrible performance (few > MB/s or less). > > First test: 500G zvol on a mirror (freshly created): > > # zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > plvl1i0 1.81T 1.97G 1.81T 0% ONLINE /mnt > # zfs list > NAME USED AVAIL REFER MOUNTPOINT > plvl1i0 500G 1.30T 112K /mnt/plvl1i0 > plvl1i0/zvtest 500G 1.78T 1.97G - > # dd if=/dev/zero of=/dev/zvol/plvl1i0/zvtest bs=2048k count=1000 > 1000+0 records in > 1000+0 records out > 2097152000 bytes transferred in 17.318348 secs (121094230 bytes/sec) > # > > Corresponds to 115,48 MB/s which is good (similar results for a single > drive). > > Second test: 500G zvol on the 3x2TB raidz1 (freshly created): > > # dd if=/dev/zero of=/dev/zvol/plvl5i0/zvtest bs=2048k count=1000 > > 1000+0 records in > 1000+0 records out > 2097152000 bytes transferred in 700.126725 secs (2995389 bytes/sec) > # > > which is only 2,85 MB/s. > > Remark: Both pools are created with the force 4096 alignment option > (since I have 512 and 4096 drives mixed). > > Now is the point where you might say the problem is related to the > raidz1. But it is not: I created a 500G dataset in the same RAIDz pool > and copied about 100G data onto it with rsync+ssh. Result: about 28MB/s > end2end performance which is reasonable. > > Are there any issues with zvol + raidz1? Google resulted in empty result > set. > > I run a minimal FreeBSD 8.2 (FreeNAS): > > # uname -a > FreeBSD zetta 8.2-RELEASE-p9 FreeBSD 8.2-RELEASE-p9 #0: Thu Jul 19 > 12:39:10 PDT 2012 > root@build.ixsystems.com:/build/home/jpaetzel/8.2.0/os-base/amd64/build/home/jpaetzel/8.2.0/FreeBSD/src/sys/FREENAS.amd64 > amd64 > > Regards, > Niki > > > PS: This is also posted on > http://forums.freenas.org/showthread.php?p=35590 > _______________________________________________ > 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 Aug 28 11:47:43 2012 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 11584106566B; Tue, 28 Aug 2012 11:47:43 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id CF4598FC16; Tue, 28 Aug 2012 11:47:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:Cc:To:Content-Type; bh=ZK0XJMtICcE1KbFd2MY3zfbE9tZXDt8TnkPr1CSMKKg=; b=XHVU1LXCUIWayR0SMkabb/bz/KrlXRoIpBvpT1LivV8Jt5lqZXl+O5NJ/wUs6g5vu1Yi0PPwsDPj6Dayn/YXkxrClXvXyXprmbT6gyt5vX0+EdexEFZvyMDLrriztbPx; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80 (FreeBSD)) (envelope-from ) id 1T6KGc-0008tG-D3; Tue, 28 Aug 2012 06:47:41 -0500 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpa id 1346154448-3058-3056/5/5; Tue, 28 Aug 2012 11:47:28 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: Guido Falsi , Matthew Seaman References: <503C5F2A.701@FreeBSD.org> <503C633B.2070508@madpilot.net> <503C66C2.5010209@FreeBSD.org> Date: Tue, 28 Aug 2012 06:47:28 -0500 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <503C66C2.5010209@FreeBSD.org> User-Agent: Opera Mail/12.01 (FreeBSD) X-SA-Report: ALL_TRUSTED=-1, KHOP_THREADED=-0.5 X-SA-Score: -1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS snapshot Folder Disappearing 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, 28 Aug 2012 11:47:43 -0000 On Tue, 28 Aug 2012 01:35:46 -0500, Matthew Seaman wrote: > Interesting. I do have certain ZFSes null-mounted into a jail. I > wonder if that's a common factor? This has also happened to me. My server has 12GB of RAM, and lots of nullfs mounts happen because I run Poudriere. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 14:26:10 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DC99E106566B; Tue, 28 Aug 2012 14:26:10 +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 178FC8FC0C; Tue, 28 Aug 2012 14:26:06 +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 RAA22612; Tue, 28 Aug 2012 17:25:53 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <503CD4F1.6060001@FreeBSD.org> Date: Tue, 28 Aug 2012 17:25:53 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120730 Thunderbird/14.0 MIME-Version: 1.0 To: Trent Nelson References: <20120824011517.GJ42732@snakebite.org> In-Reply-To: <20120824011517.GJ42732@snakebite.org> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: chmod -h 000x against symlink has bizarre results on 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, 28 Aug 2012 14:26:11 -0000 on 24/08/2012 04:15 Trent Nelson said the following: > Hi folks, > > I recently set up a FreeBSD build slave for the Python project, > and noticed some symlink tests were failing in a very strange way > (http://bugs.python.org/issue15748). > > When chmod -h 000x is done against a file/link of length less than > 24, the target seems to get padded out to 24 with 0s. If it's > longer than 24, it'll get truncated. 'x' can be 7, 6, 5 or 4 and > the behaviour is the same. > > Here's the output from the attached test_readlink.sh, also available > at http://bugs.python.org/file26979/test_readlink.sh: > > % ./test_readlink.sh > > ****** TEST 1: link/target length less than 24 ****** > before chmod -h 0007: > -rw-r----- /tmp/lt24 > lrwxr-x--- /tmp/lt24.lnk->/tmp/lt24 > python os.readlink(/tmp/lt24.lnk): > '/tmp/lt24' > after chmod -h 0007: > -rw-r----- /tmp/lt24 > l------rwx /tmp/lt24.lnk->/tmp/lt24 > python os.readlink(/tmp/lt24.lnk): > '/tmp/lt24\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > target is padded out with NULLs to 24 > > > > > ****** TEST 2: link/target length longer than 24 ****** > before chmod -h 0007: > -rw-r----- /tmp/definitelywaylongerthantwentyfour > lrwxr-x--- > /tmp/definitelywaylongerthantwentyfour.lnk->/tmp/definitelywaylongerthantwentyfour > python os.readlink(/tmp/definitelywaylongerthantwentyfour.lnk): > '/tmp/definitelywaylongerthantwentyfour' > after chmod -h 0007: > -rw-r----- /tmp/definitelywaylongerthantwentyfour > l------rwx > /tmp/definitelywaylongerthantwentyfour.lnk->/tmp/definitelywaylonger > python os.readlink(/tmp/definitelywaylongerthantwentyfour.lnk): > '/tmp/definitelywaylonger' > ^^^^^^^^^^^^^^^^^^^^^^^^ > target gets truncated to 24 > > > > ****** Other modes... ****** > after chmod -h 0006: > l------rw- > /tmp/definitelywaylongerthantwentyfour.lnk->/tmp/definitelywaylonger > after chmod -h 0005: > l------r-x > /tmp/definitelywaylongerthantwentyfour.lnk->/tmp/definitelywaylonger > after chmod -h 0004: > l------r-- > /tmp/definitelywaylongerthantwentyfour.lnk->/tmp/definitelywaylonger > after chmod -h 0000: > l--------- > /tmp/definitelywaylongerthantwentyfour.lnk->/tmp/definitelywaylongerthantwentyfour > > > This only happens on ZFS. I'm on v28, don't have any v15s lying > around. > > I'm perplexed. Can others reproduce it? > I can reproduce this problem I can also provide some additional bits of information using a modified version of zdb: $ ln -fs definitelywaylongerthantwentyfour definitelywaylongerthantwentyfour.lnk $ stat -s definitelywaylongerthantwentyfour.lnk st_dev=3895460379 st_ino=27165 st_mode=0120755 st_nlink=1 st_uid=0 st_gid=0 st_rdev=4294967295 st_size=33 st_atime=1346161009 st_mtime=1346161009 st_ctime=1346161009 st_birthtime=1346161009 st_blksize=131072 st_blocks=1 st_flags=0 $ zdb -ddddddd tank/tmp 27165 Dataset tank/tmp [ZPL], ID 69, cr_txg 31, 4.57G, 24910 objects, rootbp DVA[0]=<0:5c5375e000:200> DVA[1]=<0:4c1a80ce00:200> [L0 DMU objset] fletcher4 lzjb LE contiguous unique double size=800L/200P birth=70882769L/70882769P fill=24910 cksum=1c72e8f065:89bbdf9d575:1732432c541ff:2d672d98b0ff66 Object lvl iblk dblk dsize lsize %full type 27165 1 16K 512 0 512 0.00 ZFS plain file (K=inherit) (Z=inherit) 209 bonus System attributes dnode flags: USERUSED_ACCOUNTED dnode maxblkid: 0 path /definitelywaylongerthantwentyfour.lnk uid 0 gid 0 atime Tue Aug 28 16:36:49 2012 mtime Tue Aug 28 16:36:49 2012 ctime Tue Aug 28 16:36:49 2012 crtime Tue Aug 28 16:36:49 2012 gen 70882769 mode 120755 size 33 parent 3 links 1 pflags 40800000104 symlink definitelywaylongerthantwentyfour symlink size 33 Indirect blocks: $ chmod -h 0007 definitelywaylongerthantwentyfour.lnk $ stat -s definitelywaylongerthantwentyfour.lnk st_dev=3895460379 st_ino=27165 st_mode=0120007 st_nlink=1 st_uid=0 st_gid=0 st_rdev=4294967295 st_size=33 st_atime=1346161009 st_mtime=1346161009 st_ctime=1346161227 st_birthtime=1346161227 st_blksize=131072 st_blocks=1 st_flags=0 $ zdb -ddddddd tank/tmp 27165 Dataset tank/tmp [ZPL], ID 69, cr_txg 31, 4.57G, 24910 objects, rootbp DVA[0]=<0:5c556b4400:200> DVA[1]=<0:4c1a989600:200> [L0 DMU objset] fletcher4 lzjb LE contiguous unique double size=800L/200P birth=70882812L/70882812P fill=24910 cksum=170e778d58:737e87307d3:140a45f4106a6:283187f7da9de7 Object lvl iblk dblk dsize lsize %full type 27165 1 16K 512 0 512 0.00 ZFS plain file (K=inherit) (Z=inherit) 216 bonus System attributes dnode flags: USERUSED_ACCOUNTED dnode maxblkid: 0 path /definitelywaylongerthantwentyfour.lnk uid 0 gid 0 atime Tue Aug 28 16:36:49 2012 mtime Tue Aug 28 16:36:49 2012 ctime Tue Aug 28 16:40:27 2012 crtime Tue Aug 28 16:36:49 2012 gen 70882769 mode 120007 size 33 parent 3 links 1 pflags 40800000004 symlink definitelywaylongerthant symlink size 24 Indirect blocks: Note how the file/object size remains 33, but size of ZPL_SYMLINK attribute is changed to 24. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 15:01:41 2012 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 06FCB106566C; Tue, 28 Aug 2012 15:01:41 +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 1724A8FC14; Tue, 28 Aug 2012 15:01:39 +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 SAA23086; Tue, 28 Aug 2012 18:01:34 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <503CDD4E.6050902@FreeBSD.org> Date: Tue, 28 Aug 2012 18:01:34 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120730 Thunderbird/14.0 MIME-Version: 1.0 To: Trent Nelson References: <20120824011517.GJ42732@snakebite.org> <503CD4F1.6060001@FreeBSD.org> In-Reply-To: <503CD4F1.6060001@FreeBSD.org> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: chmod -h 000x against symlink has bizarre results on 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, 28 Aug 2012 15:01:41 -0000 on 28/08/2012 17:25 Andriy Gapon said the following: [snip] > I can reproduce this problem > I can also provide some additional bits of information using a modified version of > zdb: > > $ ln -fs definitelywaylongerthantwentyfour definitelywaylongerthantwentyfour.lnk > $ stat -s definitelywaylongerthantwentyfour.lnk > st_dev=3895460379 st_ino=27165 st_mode=0120755 st_nlink=1 st_uid=0 st_gid=0 > st_rdev=4294967295 st_size=33 st_atime=1346161009 st_mtime=1346161009 > st_ctime=1346161009 st_birthtime=1346161009 st_blksize=131072 st_blocks=1 st_flags=0 > $ zdb -ddddddd tank/tmp 27165 > Dataset tank/tmp [ZPL], ID 69, cr_txg 31, 4.57G, 24910 objects, rootbp > DVA[0]=<0:5c5375e000:200> DVA[1]=<0:4c1a80ce00:200> [L0 DMU objset] fletcher4 lzjb > LE contiguous unique double size=800L/200P birth=70882769L/70882769P fill=24910 > cksum=1c72e8f065:89bbdf9d575:1732432c541ff:2d672d98b0ff66 > > Object lvl iblk dblk dsize lsize %full type > 27165 1 16K 512 0 512 0.00 ZFS plain file (K=inherit) > (Z=inherit) > 209 bonus System attributes > dnode flags: USERUSED_ACCOUNTED > dnode maxblkid: 0 > path /definitelywaylongerthantwentyfour.lnk > uid 0 > gid 0 > atime Tue Aug 28 16:36:49 2012 > mtime Tue Aug 28 16:36:49 2012 > ctime Tue Aug 28 16:36:49 2012 > crtime Tue Aug 28 16:36:49 2012 > gen 70882769 > mode 120755 > size 33 > parent 3 > links 1 > pflags 40800000104 > symlink definitelywaylongerthantwentyfour > symlink size 33 > Indirect blocks: > > $ chmod -h 0007 definitelywaylongerthantwentyfour.lnk > $ stat -s definitelywaylongerthantwentyfour.lnk > st_dev=3895460379 st_ino=27165 st_mode=0120007 st_nlink=1 st_uid=0 st_gid=0 > st_rdev=4294967295 st_size=33 st_atime=1346161009 st_mtime=1346161009 > st_ctime=1346161227 st_birthtime=1346161227 st_blksize=131072 st_blocks=1 st_flags=0 > $ zdb -ddddddd tank/tmp 27165 > Dataset tank/tmp [ZPL], ID 69, cr_txg 31, 4.57G, 24910 objects, rootbp > DVA[0]=<0:5c556b4400:200> DVA[1]=<0:4c1a989600:200> [L0 DMU objset] fletcher4 lzjb > LE contiguous unique double size=800L/200P birth=70882812L/70882812P fill=24910 > cksum=170e778d58:737e87307d3:140a45f4106a6:283187f7da9de7 > > Object lvl iblk dblk dsize lsize %full type > 27165 1 16K 512 0 512 0.00 ZFS plain file (K=inherit) > (Z=inherit) > 216 bonus System attributes > dnode flags: USERUSED_ACCOUNTED > dnode maxblkid: 0 > path /definitelywaylongerthantwentyfour.lnk > uid 0 > gid 0 > atime Tue Aug 28 16:36:49 2012 > mtime Tue Aug 28 16:36:49 2012 > ctime Tue Aug 28 16:40:27 2012 > crtime Tue Aug 28 16:36:49 2012 > gen 70882769 > mode 120007 > size 33 > parent 3 > links 1 > pflags 40800000004 > symlink definitelywaylongerthant > symlink size 24 > Indirect blocks: > > Note how the file/object size remains 33, but size of ZPL_SYMLINK attribute is > changed to 24. > Will you be able to test the following patch? Preferably on a temporary test pool - I don't want to risk your data. diff --git a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c index 69374fb..7f61517 100644 --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c @@ -1695,6 +1695,7 @@ sa_modify_attrs(sa_handle_t *hdl, sa_attr_type_t newattr, ASSERT(action == SA_REPLACE); SA_ADD_BULK_ATTR(attr_desc, j, attr, locator, datastart, buflen); + length_idx++; } else { length = SA_REGISTERED_LEN(sa, attr); if (length == 0) { -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 15:18:51 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A1EA106566B for ; Tue, 28 Aug 2012 15:18:51 +0000 (UTC) (envelope-from attila.bogar@linguamatics.com) Received: from mail.linguamatics.com (mail.linguamatics.com [188.39.80.203]) by mx1.freebsd.org (Postfix) with ESMTP id C34F18FC14 for ; Tue, 28 Aug 2012 15:18:50 +0000 (UTC) Received: from [10.252.10.232] (random.linguamatics.com [10.252.10.232]) by mail.linguamatics.com (Postfix) with ESMTPSA id A7742EFB461 for ; Tue, 28 Aug 2012 16:18:49 +0100 (BST) Message-ID: <503CE159.8040208@linguamatics.com> Date: Tue, 28 Aug 2012 16:18:49 +0100 From: =?UTF-8?B?QXR0aWxhIEJvZ8Ohcg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <503C5F2A.701@FreeBSD.org> <503C633B.2070508@madpilot.net> <503C66C2.5010209@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS snapshot Folder Disappearing 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, 28 Aug 2012 15:18:51 -0000 Hi, I managed to reproduce this problem on 9-STABLE using port misc/amanda-server with the amzfs_snapshot plugin. It was on 9.1-PRERELEASE Attila From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 15:21:04 2012 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 DB265106564A for ; Tue, 28 Aug 2012 15:21:03 +0000 (UTC) (envelope-from attila.bogar@linguamatics.com) Received: from mail.linguamatics.com (mail.linguamatics.com [188.39.80.203]) by mx1.freebsd.org (Postfix) with ESMTP id 57EE48FC1B for ; Tue, 28 Aug 2012 15:21:03 +0000 (UTC) Received: from [10.252.10.232] (random.linguamatics.com [10.252.10.232]) by mail.linguamatics.com (Postfix) with ESMTPSA id 5FC28EFB451 for ; Tue, 28 Aug 2012 16:13:22 +0100 (BST) Message-ID: <503CE012.3040408@linguamatics.com> Date: Tue, 28 Aug 2012 16:13:22 +0100 From: =?ISO-8859-1?Q?Attila_Bog=E1r?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Need hints debugging KGSSAPI 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, 28 Aug 2012 15:21:04 -0000 Hi, I'd like to spend some time finding out myself what's wrong with the kerberized nfs server on the FreeBSD 9-STABLE. I thought the solution is to simply force DES+RFC1964 GSSAPI, but unfortunately it's not that simple. I built a patched nfs-utils package by merging the patch referenced from https://bugzilla.redhat.com/show_bug.cgi?id=802469 - with the legacy option did not resolve the problem. I have some wireshark traces which show that one EL6 box get 3 times auth_denied however the other succeeds for the 3rd time. I can reproduce this. My kernel is a GENERIC + some option as per Rick's page: options KGSSAPI device crypto device cryptodev I know, that all interesting NFS/GSSAPI job is done within kernel space. I suppose it's not possible to unload the KGSSAPI module: http://svnweb.freebsd.org/base/head/sys/kgssapi/gss_impl.c?view=markup&pathrev=224084 What's the best way to debug the kernel other than inserting debug messages into the source tree+recompiling+rebooting? What debugger do you recommend? Is there an up-to-date tutorial on FreeBSD kernel debugging? Any constructive comments appreciated. Thanks, Attila From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 15:27:29 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9426E106564A for ; Tue, 28 Aug 2012 15:27:29 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 162028FC12 for ; Tue, 28 Aug 2012 15:27:28 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so3938643lbb.13 for ; Tue, 28 Aug 2012 08:27:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IWSoFCwwtN32uZSFME0Bw3FuA9Jh9wny4gunBrFQ2HA=; b=ioNMGda5LwsKfKdXZoYQL5gJMcmemor5HD0+aKK2ERHaGuKsLiymnVcwdbjuSvfQFK cc4s0a5LjSP/4ubDwd1J77q42jkx6q36CC8ZVrbI7+9lY/DzO8sep/P+Xw8xmqBZuqM/ ep1AKlifzuq77KaseWwSvavzVXBbhKBKXsysIp405rMw9Vqqh34wFipuozuhUMamI6kO ZK3PlKX2o03cs2+a3fIhXd3RtAh9wMlLB1ADS27TqthgR+mDW93qhAnDzHewgOqaV3/K lIYysqC1khKmI14XjDcAt0tGWTmhIMxgh4OqdvU8HxuEyZQ0oLDKQjLtOED+8EncbiFc Kmcw== MIME-Version: 1.0 Received: by 10.152.114.3 with SMTP id jc3mr18970245lab.11.1346167647938; Tue, 28 Aug 2012 08:27:27 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Tue, 28 Aug 2012 08:27:27 -0700 (PDT) In-Reply-To: <503C8AEE.1090703@nobaq.net> References: <503A6F9F.7070801@nobaq.net> <503C8AEE.1090703@nobaq.net> Date: Tue, 28 Aug 2012 08:27:27 -0700 Message-ID: From: Freddie Cash To: Niki Hammler Content-Type: text/plain; charset=UTF-8 Cc: freebsd-fs@freebsd.org Subject: Re: zvol + raidz issue? 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, 28 Aug 2012 15:27:29 -0000 On Tue, Aug 28, 2012 at 2:10 AM, Niki Hammler wrote: > Am 26.08.2012 22:13, schrieb Freddie Cash: >> (Sorry for top-post, sending from phone.) >> >> Please show the command-line used to create the zvol. Especially the >> recordsize option. When using zvols, you have to make sure to match the >> recordsize of the zvol to that of the filesystem used above it. >> Otherwise, performance will be atrocious. > > Sorry for my third posting on this. > Now I strictly followed your suggestion and used > > zfs create -b 128k -V 500g plvl5i0/zvtest > > (with 128k being the recordsize of the dataset in the zpool). > > Suddenly the write performance increased from the 2.5 MB/s to 250 MB/s > (or 78MB/s when using bs=4096 with dd) > > 1.) How can this explained? > 2.) Is there any problem when choosing -b 128k (can I always blindly > choose -b 128k)? > > Remember again that the problem ONLY occurs with raidz1+zvol+force 4096 > block alignment and in no other case! Most likely it has to do with the raidz stripe size and the constant block size of the zvol causing alignment or similar issues. I've also seen indications in the zfs-discuss mailing list about optimal and sub-optimal disk configurations for the various raidz types (wrong number of disks in the vdev leads to horrible performance). -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 16:43:34 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 51D68106564A; Tue, 28 Aug 2012 16:43:34 +0000 (UTC) (envelope-from trent@snakebite.org) Received: from exchange.liveoffice.com (exchla3.liveoffice.com [64.70.67.188]) by mx1.freebsd.org (Postfix) with ESMTP id 0BD6C8FC08; Tue, 28 Aug 2012 16:43:33 +0000 (UTC) Received: from EXHUB03.exchhosting.com (192.168.11.104) by exhub09.exchhosting.com (192.168.11.107) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 28 Aug 2012 09:43:25 -0700 Received: from localhost (35.8.247.10) by exchange.liveoffice.com (192.168.11.104) with Microsoft SMTP Server id 8.3.213.0; Tue, 28 Aug 2012 09:43:24 -0700 Date: Tue, 28 Aug 2012 12:43:23 -0400 From: Trent Nelson To: Andriy Gapon Message-ID: <20120828164323.GA25443@snakebite.org> References: <20120824011517.GJ42732@snakebite.org> <503CD4F1.6060001@FreeBSD.org> <503CDD4E.6050902@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <503CDD4E.6050902@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-fs@FreeBSD.org" Subject: Re: chmod -h 000x against symlink has bizarre results on 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, 28 Aug 2012 16:43:34 -0000 On Tue, Aug 28, 2012 at 08:01:34AM -0700, Andriy Gapon wrote: > on 28/08/2012 17:25 Andriy Gapon said the following: > [snip] > > I can reproduce this problem > > I can also provide some additional bits of information using a modified version of > > zdb: > > > > $ ln -fs definitelywaylongerthantwentyfour definitelywaylongerthantwentyfour.lnk > > $ stat -s definitelywaylongerthantwentyfour.lnk > > st_dev=3895460379 st_ino=27165 st_mode=0120755 st_nlink=1 st_uid=0 st_gid=0 > > st_rdev=4294967295 st_size=33 st_atime=1346161009 st_mtime=1346161009 > > st_ctime=1346161009 st_birthtime=1346161009 st_blksize=131072 st_blocks=1 st_flags=0 > > $ zdb -ddddddd tank/tmp 27165 > > Dataset tank/tmp [ZPL], ID 69, cr_txg 31, 4.57G, 24910 objects, rootbp > > DVA[0]=<0:5c5375e000:200> DVA[1]=<0:4c1a80ce00:200> [L0 DMU objset] fletcher4 lzjb > > LE contiguous unique double size=800L/200P birth=70882769L/70882769P fill=24910 > > cksum=1c72e8f065:89bbdf9d575:1732432c541ff:2d672d98b0ff66 > > > > Object lvl iblk dblk dsize lsize %full type > > 27165 1 16K 512 0 512 0.00 ZFS plain file (K=inherit) > > (Z=inherit) > > 209 bonus System attributes > > dnode flags: USERUSED_ACCOUNTED > > dnode maxblkid: 0 > > path /definitelywaylongerthantwentyfour.lnk > > uid 0 > > gid 0 > > atime Tue Aug 28 16:36:49 2012 > > mtime Tue Aug 28 16:36:49 2012 > > ctime Tue Aug 28 16:36:49 2012 > > crtime Tue Aug 28 16:36:49 2012 > > gen 70882769 > > mode 120755 > > size 33 > > parent 3 > > links 1 > > pflags 40800000104 > > symlink definitelywaylongerthantwentyfour > > symlink size 33 > > Indirect blocks: > > > > $ chmod -h 0007 definitelywaylongerthantwentyfour.lnk > > $ stat -s definitelywaylongerthantwentyfour.lnk > > st_dev=3895460379 st_ino=27165 st_mode=0120007 st_nlink=1 st_uid=0 st_gid=0 > > st_rdev=4294967295 st_size=33 st_atime=1346161009 st_mtime=1346161009 > > st_ctime=1346161227 st_birthtime=1346161227 st_blksize=131072 st_blocks=1 st_flags=0 > > $ zdb -ddddddd tank/tmp 27165 > > Dataset tank/tmp [ZPL], ID 69, cr_txg 31, 4.57G, 24910 objects, rootbp > > DVA[0]=<0:5c556b4400:200> DVA[1]=<0:4c1a989600:200> [L0 DMU objset] fletcher4 lzjb > > LE contiguous unique double size=800L/200P birth=70882812L/70882812P fill=24910 > > cksum=170e778d58:737e87307d3:140a45f4106a6:283187f7da9de7 > > > > Object lvl iblk dblk dsize lsize %full type > > 27165 1 16K 512 0 512 0.00 ZFS plain file (K=inherit) > > (Z=inherit) > > 216 bonus System attributes > > dnode flags: USERUSED_ACCOUNTED > > dnode maxblkid: 0 > > path /definitelywaylongerthantwentyfour.lnk > > uid 0 > > gid 0 > > atime Tue Aug 28 16:36:49 2012 > > mtime Tue Aug 28 16:36:49 2012 > > ctime Tue Aug 28 16:40:27 2012 > > crtime Tue Aug 28 16:36:49 2012 > > gen 70882769 > > mode 120007 > > size 33 > > parent 3 > > links 1 > > pflags 40800000004 > > symlink definitelywaylongerthant > > symlink size 24 > > Indirect blocks: > > > > Note how the file/object size remains 33, but size of ZPL_SYMLINK attribute is > > changed to 24. > > > > Will you be able to test the following patch? Sure. Just out of interest, is it FreeBSD-specific? Or likely to affect other ZFS platforms as well? Just out of interest, is it FreeBSD-specific? Or likely to affect other ZFS platforms as well? Just out of interest, is it FreeBSD-specific? Or likely to affect other ZFS platforms as well? Just out of interest, is it FreeBSD -specific? Or likely to affect other ZFS platforms as well? > Preferably on a temporary test pool - I don't want to risk your data. Ah, thanks for the heads up. I'll work something out and report back. Trent. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 16:53:59 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 57804106566B for ; Tue, 28 Aug 2012 16:53:59 +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 A55898FC0A for ; Tue, 28 Aug 2012 16:53:58 +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 TAA24083; Tue, 28 Aug 2012 19:53:53 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <503CF7A1.6070105@FreeBSD.org> Date: Tue, 28 Aug 2012 19:53:53 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120730 Thunderbird/14.0 MIME-Version: 1.0 To: Trent Nelson References: <20120824011517.GJ42732@snakebite.org> <503CD4F1.6060001@FreeBSD.org> <503CDD4E.6050902@FreeBSD.org> <20120828164323.GA25443@snakebite.org> In-Reply-To: <20120828164323.GA25443@snakebite.org> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: "freebsd-fs@FreeBSD.org" Subject: Re: chmod -h 000x against symlink has bizarre results on 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, 28 Aug 2012 16:53:59 -0000 on 28/08/2012 19:43 Trent Nelson said the following: > On Tue, Aug 28, 2012 at 08:01:34AM -0700, Andriy Gapon wrote: >> Will you be able to test the following patch? > > Sure. Just out of interest, is it FreeBSD-specific? Or likely to > affect other ZFS platforms as well? Just out of interest, is it > FreeBSD-specific? Or likely to affect other ZFS platforms as well? > Just out of interest, is it FreeBSD-specific? Or likely to affect > other ZFS platforms as well? Just out of interest, is it FreeBSD > -specific? Or likely to affect other ZFS platforms as well? Likely to affect other ZFS platforms in some form or shape. Likely to affect other ZFS platforms in some form or shape. Likely to affect other ZFS platforms in some form or shape. Likely to affect other ZFS platforms in some form or shape. :-) At least if those hold true: - I correctly understood what's going on - the platforms use the same ZFS core; e.g. I can't say anything about non-public ZFS code in Oracle Solaris Also, for the bug to reveal itself there should be at least two variable sized attributes of a file, one of them must be updated, its value must change size and the attribute should not the last one. >> Preferably on a temporary test pool - I don't want to risk your data. > > Ah, thanks for the heads up. I'll work something out and report > back. Yeah, better safe than sorry. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 16:56:53 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E5D71065679; Tue, 28 Aug 2012 16:56:53 +0000 (UTC) (envelope-from trent@snakebite.org) Received: from exchange.liveoffice.com (exchla3.liveoffice.com [64.70.67.188]) by mx1.freebsd.org (Postfix) with ESMTP id 1929B8FC17; Tue, 28 Aug 2012 16:56:52 +0000 (UTC) Received: from exhub13.exchhosting.com (192.168.11.122) by exhub05.exchhosting.com (192.168.11.101) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 28 Aug 2012 09:56:52 -0700 Received: from localhost (35.8.247.10) by exchange.liveoffice.com (192.168.11.122) with Microsoft SMTP Server id 8.3.213.0; Tue, 28 Aug 2012 09:56:51 -0700 Date: Tue, 28 Aug 2012 12:56:50 -0400 From: Trent Nelson To: Andriy Gapon Message-ID: <20120828165650.GB25443@snakebite.org> References: <20120824011517.GJ42732@snakebite.org> <503CD4F1.6060001@FreeBSD.org> <503CDD4E.6050902@FreeBSD.org> <20120828164132.GA939@snakebite.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20120828164132.GA939@snakebite.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-fs@FreeBSD.org" Subject: Re: chmod -h 000x against symlink has bizarre results on 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, 28 Aug 2012 16:56:53 -0000 On Tue, Aug 28, 2012 at 09:42:32AM -0700, Trent Nelson wrote: > Sure. Just out of interest, is it FreeBSD-specific? Or likely to > affect other ZFS platforms as well? Just out of interest, is it > FreeBSD-specific? Or likely to affect other ZFS platforms as well? > Just out of interest, is it FreeBSD-specific? Or likely to affect > other ZFS platforms as well? Just out of interest, is it FreeBSD > -specific? Or likely to affect other ZFS platforms as well? Good grief. Not sure what happened there. (vi fat fingering, perhaps.) Trent. From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 17:06:53 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 20117106566B for ; Tue, 28 Aug 2012 17:06:53 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E43E98FC20 for ; Tue, 28 Aug 2012 17:06:52 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so10019200pbb.13 for ; Tue, 28 Aug 2012 10:06:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:date:message-id:subject:from:to:content-type; bh=mNu++6lGG95ZGMksTP3qDM+lFlVQ1NHmcygefBkeiog=; b=QmROCKG/PQtD0oyC30p7ZgvA2dflS7eEKddxJ2y6ZndOXLnsW3xR0Y5tvSc2SVakuw acT77s4lyVCd7HuVWQj0Zj6rqAS43abtFMvxXQ8S+5IkAlUh/R1JNWtj/Bo0TbM8bXIS X5Zx9q2QA54Qyr395ewJS255V6Od2PmQyNp+o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=mNu++6lGG95ZGMksTP3qDM+lFlVQ1NHmcygefBkeiog=; b=HMKpwx+yTwXSvEfvckwtAARk3UgHKNr0+e7zyOzjmSpZO8V7kryBAdqN8QwOuuew06 OPuWZVFirMu6bLLyaOFJ8G1DPURM1lrCFBbkLu4BSxeUzHTB5iREEljvv+1Pn/dZpGWl XXZkX8GixQV5BuEdP4fJ9ERnz4ao7LuMnLU737y+Vn3uOn/i0oAN3wB8Jy+ngAF8GEAn FxfIA+tBK/yTyvThgQE8gd/V7bRWiuNvqMY8got7UW1K5ws4bXRSBTP4aXLpRRXdLYTw DeSyEYX1hgZeEnOnOHlN4I0Uf5ZymwF2UGZvfIegpuCMUdDZAI4hiGWj6vRYvlPfMtLU 7veQ== MIME-Version: 1.0 Received: by 10.68.234.99 with SMTP id ud3mr43724177pbc.166.1346173611736; Tue, 28 Aug 2012 10:06:51 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Tue, 28 Aug 2012 10:06:51 -0700 (PDT) Date: Tue, 28 Aug 2012 10:06:51 -0700 Message-ID: From: Tim Gustafson To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmbEE9vceCT1x5K72AxaOI3ELNolojfr1ys9xHvnFkxp+12Ma1hfwjQ2rDnAkfmVawzibBc Subject: Using AMD with NFS Mounts 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, 28 Aug 2012 17:06:53 -0000 Unrelated to my existing ZFS issue, I also have an NFS/AMD question. I am trying to get FreeBSD to behave more like our existing Linux, Mac and Solaris systems when it comes to auto-mounting. We maintain all our mount information in our LDAP server, and Linux, Mac and Solaris act upon that data directly using autofs. I know that FreeBSD prefers AMD, so I'm willing to write a script that exports the data from the LDAP server into AMD-map format, but I'm having a problem getting even the basics to go. My configuration files are included below. AMD runs, and the log file indicates that it's ready to accept requests, but when I try to cd into any AMD-hosted folder, I get miscellaneous errors related to "too many levels of symlinks" or flat-out permission denied errors. Sometimes I am able to re-start AMD, and other time re-starting AMD hangs. I can statically mount the filesystems in question by hand, so I'm sure the "permission denied" errors are not NFS-related. I'm guessing that I have some minor error in my configuration file, but I can't see what it is. What am I missing? Here's the output from my syslog: amd[1983]: switched to logfile "syslog:daemon" amd[1983]: AM-UTILS VERSION INFORMATION: amd[1983]: Copyright (c) 1997-2006 Erez Zadok amd[1983]: Copyright (c) 1990 Jan-Simon Pendry amd[1983]: Copyright (c) 1990 Imperial College of Science, Technology & Medicine amd[1983]: Copyright (c) 1990 The Regents of the University of California. amd[1983]: am-utils version 6.1.5 (build 900044). amd[1983]: Report bugs to https://bugzilla.am-utils.org/ or am-utils@am-utils.org. amd[1983]: Configured by David O'Brien on date 4-December-2007 PST. amd[1983]: Built by root@client.soe.ucsc.edu. amd[1983]: cpu=amd64 (little-endian), arch=amd64, karch=amd64. amd[1983]: full_os=freebsd9.0, os=freebsd9, osver=9.0, vendor=undermydesk, distro=The FreeBSD Project. amd[1983]: domain=soe.ucsc.edu, host=client, hostd=client.soe.ucsc.edu. amd[1983]: Map support for: root, passwd, union, nis, ndbm, file, exec, error. amd[1983]: AMFS: nfs, link, nfsx, nfsl, host, linkx, program, union, ufs, cdfs, amd[1983]: pcfs, auto, direct, toplvl, error, inherit. amd[1983]: FS: cd9660, nfs, nfs3, nullfs, msdosfs, ufs, unionfs. amd[1983]: Network 1: wire=*SNIP* amd[1983]: Network 2: wire=*SNIP* amd[1983]: My ip addr is 127.0.0.1 amd[1984]: released controlling tty using setsid() amd[1984]: Locked process pages in memory amd[1984]: file server localhost, type local, state starts up amd[1984]: /dev/ad8s1a restarted fstype ufs on /, flags 0x89 amd[1984]: devfs restarted fstype link on /dev, flags 0x89 amd[1984]: procfs restarted fstype link on /proc, flags 0x89 amd[1984]: fdescfs restarted fstype link on /dev/fd, flags 0x89 amd[1984]: Unknown host: pid1715@client amd[1984]: pid1715@client:/projects restarted fstype nfs on /projects, flags 0x29 amd[1984]: Unknown host: pid1715@client amd[1984]: pid1715@client:/soe restarted fstype nfs on /soe, flags 0x29 amd[1984]: pid1715@client:/soe referenced fstype nfs on /soe amd[1984]: /soe set to timeout in 30 seconds amd[1984]: pid1715@client:/projects referenced fstype nfs on /projects amd[1984]: /projects set to timeout in 30 seconds amd[1984]: WARNING: automounter going down on signal 15 amd[1984]: WARNING: automounter going down on signal 15 And, here are my configuration files: ==================== amd.conf ==================== [ global ] browsable_dirs = no map_type = file mount_type = nfs cache_duration = 30 autofs_use_lofs = yes log_file = syslog:daemon log_options = fatal,error print_pid = yes pid_file = /var/run/amd.pid restart_mounts = yes selectors_in_defaults = no [ /soe ] map_name = /etc/amd/soe.map [ /projects ] map_name = /etc/amd/projects.map ==================== soe.map ==================== /defaults type:=nfs;opts:=tcp,soft,nodev,nosuid,umount,vers=3 * fs:=/soe/${key};rhost:=fs2;rfs:=/export/home/${key} tjg fs:=/soe/tjg;rhost:=bsd-06;rfs:=/tank/export/home/tjg ==================== projects.map ==================== /defaults type:=nfs;opts:=tcp,soft,nodev,nosuid,umount,vers=3 * fs:=/projects/${key};rhost:=fs2;rfs:=/export/projects/${key} -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 18:13:25 2012 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 3D419106564A for ; Tue, 28 Aug 2012 18:13:25 +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 D60228FC08 for ; Tue, 28 Aug 2012 18:13:24 +0000 (UTC) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.5/8.14.5) with ESMTP id q7SIDKVW008891; Tue, 28 Aug 2012 19:13:20 +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 q7SIDF75000784; Tue, 28 Aug 2012 19:13:15 +0100 Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id q7SIDEiJ000779; Tue, 28 Aug 2012 19:13:14 +0100 Date: Tue, 28 Aug 2012 19:13:14 +0100 Message-Id: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> From: Martin Simmons To: Tim Gustafson In-reply-to: (message from Tim Gustafson on Tue, 28 Aug 2012 10:06:51 -0700) References: Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 28 Aug 2012 18:13:25 -0000 >>>>> On Tue, 28 Aug 2012 10:06:51 -0700, Tim Gustafson said: > > Unrelated to my existing ZFS issue, I also have an NFS/AMD question. > > I am trying to get FreeBSD to behave more like our existing Linux, Mac > and Solaris systems when it comes to auto-mounting. We maintain all > our mount information in our LDAP server, and Linux, Mac and Solaris > act upon that data directly using autofs. I know that FreeBSD prefers > AMD, so I'm willing to write a script that exports the data from the > LDAP server into AMD-map format, but I'm having a problem getting even > the basics to go. My configuration files are included below. > > AMD runs, and the log file indicates that it's ready to accept > requests, but when I try to cd into any AMD-hosted folder, I get > miscellaneous errors related to "too many levels of symlinks" or > flat-out permission denied errors. Sometimes I am able to re-start > AMD, and other time re-starting AMD hangs. I can statically mount the > filesystems in question by hand, so I'm sure the "permission denied" > errors are not NFS-related. > > I'm guessing that I have some minor error in my configuration file, > but I can't see what it is. What am I missing? Here's the output > from my syslog: > > amd[1983]: switched to logfile "syslog:daemon" > amd[1983]: AM-UTILS VERSION INFORMATION: > amd[1983]: Copyright (c) 1997-2006 Erez Zadok > amd[1983]: Copyright (c) 1990 Jan-Simon Pendry > amd[1983]: Copyright (c) 1990 Imperial College of Science, Technology & Medicine > amd[1983]: Copyright (c) 1990 The Regents of the University of California. > amd[1983]: am-utils version 6.1.5 (build 900044). > amd[1983]: Report bugs to https://bugzilla.am-utils.org/ or > am-utils@am-utils.org. > amd[1983]: Configured by David O'Brien on date > 4-December-2007 PST. > amd[1983]: Built by root@client.soe.ucsc.edu. > amd[1983]: cpu=amd64 (little-endian), arch=amd64, karch=amd64. > amd[1983]: full_os=freebsd9.0, os=freebsd9, osver=9.0, > vendor=undermydesk, distro=The FreeBSD Project. > amd[1983]: domain=soe.ucsc.edu, host=client, hostd=client.soe.ucsc.edu. > amd[1983]: Map support for: root, passwd, union, nis, ndbm, file, exec, error. > amd[1983]: AMFS: nfs, link, nfsx, nfsl, host, linkx, program, union, ufs, cdfs, > amd[1983]: pcfs, auto, direct, toplvl, error, inherit. > amd[1983]: FS: cd9660, nfs, nfs3, nullfs, msdosfs, ufs, unionfs. > amd[1983]: Network 1: wire=*SNIP* > amd[1983]: Network 2: wire=*SNIP* > amd[1983]: My ip addr is 127.0.0.1 > amd[1984]: released controlling tty using setsid() > amd[1984]: Locked process pages in memory > amd[1984]: file server localhost, type local, state starts up > amd[1984]: /dev/ad8s1a restarted fstype ufs on /, flags 0x89 > amd[1984]: devfs restarted fstype link on /dev, flags 0x89 > amd[1984]: procfs restarted fstype link on /proc, flags 0x89 > amd[1984]: fdescfs restarted fstype link on /dev/fd, flags 0x89 > amd[1984]: Unknown host: pid1715@client > amd[1984]: pid1715@client:/projects restarted fstype nfs on /projects, > flags 0x29 > amd[1984]: Unknown host: pid1715@client > amd[1984]: pid1715@client:/soe restarted fstype nfs on /soe, flags 0x29 > amd[1984]: pid1715@client:/soe referenced fstype nfs on /soe > amd[1984]: /soe set to timeout in 30 seconds > amd[1984]: pid1715@client:/projects referenced fstype nfs on /projects > amd[1984]: /projects set to timeout in 30 seconds > amd[1984]: WARNING: automounter going down on signal 15 > amd[1984]: WARNING: automounter going down on signal 15 > > And, here are my configuration files: > > ==================== > amd.conf > ==================== > [ global ] > browsable_dirs = no > map_type = file > mount_type = nfs > cache_duration = 30 > autofs_use_lofs = yes > log_file = syslog:daemon > log_options = fatal,error > print_pid = yes > pid_file = /var/run/amd.pid > restart_mounts = yes > selectors_in_defaults = no > > [ /soe ] > map_name = /etc/amd/soe.map > > [ /projects ] > map_name = /etc/amd/projects.map > > ==================== > soe.map > ==================== > /defaults type:=nfs;opts:=tcp,soft,nodev,nosuid,umount,vers=3 > * fs:=/soe/${key};rhost:=fs2;rfs:=/export/home/${key} > tjg fs:=/soe/tjg;rhost:=bsd-06;rfs:=/tank/export/home/tjg > > ==================== > projects.map > ==================== > /defaults type:=nfs;opts:=tcp,soft,nodev,nosuid,umount,vers=3 > * fs:=/projects/${key};rhost:=fs2;rfs:=/export/projects/${key} I think you want to remove "fs:=/projects/${key};" from here (its default value should be sufficent). That should make fs2:/export/projects/foo available as /projects/foo etc. Note that amd mounts the filesystem in a hidden directory (named by the fs option) and makes a symlink to it from the directory named in amd.conf. You shouldn't set fs to the directory named in amd.conf. __Martin From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 18:15:36 2012 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 AF1EE106566C for ; Tue, 28 Aug 2012 18:15:36 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7A7578FC1D for ; Tue, 28 Aug 2012 18:15:36 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so10133790pbb.13 for ; Tue, 28 Aug 2012 11:15:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XnU9s6wugpc+ofgNWnjuZd01P/2hXsM46443Yev6mBw=; b=gsP8NlmoUw6hjzAPXUdy4oxaBSXX6TbMFy1jW3xvfrtYAlaFl4RBNO8cDUszM5RUE4 aVzeJBGTQEXBcZsDhtNplMdz73pAtPTpiETIMLZlaRDkJ2lrelilgZAZ587EB7Rm5sSH ruFg6WCbn7Q5gHKPnhiq/UpT5Ocx4sL2UvOHE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=XnU9s6wugpc+ofgNWnjuZd01P/2hXsM46443Yev6mBw=; b=gmAdZ6bscJLrVNFPwTSX5MSrup/QdIWzlsh3bGH6HiPm9drlM8FBO3ORsgymIUblnH TAq3xt3rJlOU/ITFP51BRSNkoe2EmfPcjsKzXTsVc6LXcFnc/PRPHjQCrhCTsFVtKp3X lONPs+RBjEajo2DycOoR7fnBUNd8mNLgM6kGQ47+lt+/LK/YT5B4yEG67q5FPWaVU9Bw dotk8cO56a3iPbcEIfdUYgIm19om5swfcjNvicdUTZglX+utz1d7HChOgi26WB4wekGO 0GbsvDt9VXatCgIDuwT53tvZdmn/F/DAgbpsHttXPrekmRoZBj/Du8Amr2YIvH3bfzPa 6aJA== MIME-Version: 1.0 Received: by 10.68.213.138 with SMTP id ns10mr22229156pbc.157.1346177735799; Tue, 28 Aug 2012 11:15:35 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Tue, 28 Aug 2012 11:15:35 -0700 (PDT) In-Reply-To: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> Date: Tue, 28 Aug 2012 11:15:35 -0700 Message-ID: From: Tim Gustafson To: Martin Simmons Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmUzKfWxMYwJZcSDrvAb0Qibp3WIMvjyeBE4HfcJcQjptUn2vgFHm+isrXTpFLGveYe8OUg Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 28 Aug 2012 18:15:36 -0000 > Note that amd mounts the filesystem in a hidden directory (named by the fs > option) and makes a symlink to it from the directory named in amd.conf. You > shouldn't set fs to the directory named in amd.conf. I'm not using the symlinks option; I've specified "autofs_use_lofs = yes" to mount the directories in-place. I don't want AMD's normal symlink structure because I want all the mounts to behave the same way as the Linux/Mac/Sun machines do. -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 18:50:21 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34AC81065706 for ; Tue, 28 Aug 2012 18:50:21 +0000 (UTC) (envelope-from mailinglists@nobaq.net) Received: from mail.nobaq.net (mail.nobaq.net [IPv6:2001:7b8:3cd:3::172]) by mx1.freebsd.org (Postfix) with ESMTP id B4D768FC17 for ; Tue, 28 Aug 2012 18:50:20 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=mail.nobaq.net) by mail.nobaq.net with esmtp (Exim 4.72) (envelope-from ) id 1T6Qrh-0005lP-BB; Tue, 28 Aug 2012 20:50:18 +0200 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=nobaq.net; h=message-id :date:from:mime-version:to:cc:references:in-reply-to :content-type:content-transfer-encoding:subject; s=n200908; bh=p JvcHHhDeiX/P8+cLCQx011Qyok=; b=ZMDdLxQo27ydrbwfE01KQ6xGp9uPQ4Kyv bLzteupEI1OpOmHk3bIy5PhqtSdJKQAUzXVr2wJ+kWYOGoo1nSv/HoT/PNxLElGA mZVe8RjlgnMBuU1EYfPnTAmF5yM1OSBA+w2vz7SgIz8X81fTHkqVdVFtI9etqTLF Eh/CTegxA8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=nobaq.net; h=message-id:date :from:mime-version:to:cc:references:in-reply-to:content-type :content-transfer-encoding:subject; q=dns; s=n200908; b=Gm2zNgDm cfOI0JJ1kVHTOziKffuqRDc1rDM5Ulh16f+d8aeaGsHyx3XGxSTnW/vB3hdvmeLn mxFl+z/eItx8upvkDpqTO+OfsjwqqyiU1x0GXZ/6TKdxvap7b9bAuVPL/FhFcqtw 63tEjZLW9+oY0JR5vEb9qxQRRJ60c7ZXRaU= Received: from gate.nobaq.net ([93.83.102.170] helo=[192.168.200.202]) by mail.nobaq.net with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1T6QrO-0005lF-Qc; Tue, 28 Aug 2012 20:50:16 +0200 Message-ID: <503D12DB.3040909@nobaq.net> Date: Tue, 28 Aug 2012 20:50:03 +0200 From: Niki Hammler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Freddie Cash References: <503A6F9F.7070801@nobaq.net> <503C8AEE.1090703@nobaq.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.nobaq.net X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: mailinglists@nobaq.net X-SA-Exim-Scanned: No (on mail.nobaq.net); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org Subject: Re: zvol + raidz issue? 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, 28 Aug 2012 18:50:21 -0000 Am 28.08.2012 17:27, schrieb Freddie Cash: > On Tue, Aug 28, 2012 at 2:10 AM, Niki Hammler wrote: >> Am 26.08.2012 22:13, schrieb Freddie Cash: >>> (Sorry for top-post, sending from phone.) >>> >>> Please show the command-line used to create the zvol. Especially the >>> recordsize option. When using zvols, you have to make sure to match the >>> recordsize of the zvol to that of the filesystem used above it. >>> Otherwise, performance will be atrocious. >> >> Sorry for my third posting on this. >> Now I strictly followed your suggestion and used >> >> zfs create -b 128k -V 500g plvl5i0/zvtest >> >> (with 128k being the recordsize of the dataset in the zpool). >> >> Suddenly the write performance increased from the 2.5 MB/s to 250 MB/s >> (or 78MB/s when using bs=4096 with dd) >> >> 1.) How can this explained? >> 2.) Is there any problem when choosing -b 128k (can I always blindly >> choose -b 128k)? >> >> Remember again that the problem ONLY occurs with raidz1+zvol+force 4096 >> block alignment and in no other case! > > Most likely it has to do with the raidz stripe size and the constant > block size of the zvol causing alignment or similar issues. Yes, but I thought a zvol is merely a file in a zpool? How can it be explained that writing to a file (with the same parameters!) is OK while writing to a zvol drastically slower? Is there anything I can check/debug? I already filed a bug in FreeNAS but since this seems to be FreeBSD-related I will also file a bug report for FreeBSD. > I've also seen indications in the zfs-discuss mailing list about > optimal and sub-optimal disk configurations for the various raidz > types (wrong number of disks in the vdev leads to horrible > performance). Yes, I know this. In my case it's 3x2TB which is fine. Regards, Niki From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 20:54:56 2012 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 B07551065678; Tue, 28 Aug 2012 20:54:56 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) by mx1.freebsd.org (Postfix) with ESMTP id 934F68FC1C; Tue, 28 Aug 2012 20:54:56 +0000 (UTC) Received: from epsilon.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 0D8C51D579; Tue, 28 Aug 2012 13:54:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1346187296; bh=rWCqtLZsUqIvIPPaa5hpUBknJTupyFmrTy3maujcUCk=; h=Date:From:Reply-To:To:Subject; b=XhCibDuoNrehJI9Bt3+M2LemZbHpgcNT2grrHsd+PI505u9itf7uh5pv+PBep+vru krgIlEmk0v5//fMkuntbilW/vxC2SiyLZ4LH0LWGPTA3rAf5zrTNEtWnvLgQNfSM52 tiahXQfNipGEBBy1N0bhcla2DPi0UUqRTicZgp0M= Message-ID: <503D301F.5080607@delphij.net> Date: Tue, 28 Aug 2012 13:54:55 -0700 From: Xin Li Organization: The freeBSD Project User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.6esrpre) Gecko/20120727 Thunderbird/10.0.6 MIME-Version: 1.0 To: rmacklem@FreeBSD.org, freebsd-fs@FreeBSD.ORG X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Why vfs_stdcheckexp is a VFS operation? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2012 20:54:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, We have recently run into a problem with exports(5) and I then read the code of mountd(8) as well as sys/kern/vfs_exports.c and found that vfs_stdcheckexp is a VFS operation and not a vnode operation. So for instance if one exports a mountpoint, and later changes his mind and export a directory under that mountpoint, clients that have mounted the mountpoint before the second operation will still have access. Is this intentional (e.g. for performance consideration?) Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJQPTAfAAoJEG80Jeu8UPuzGykIAIBOrRNGsqgLNzIpEtqsBjKE ZSGTVLCfoAWeeOLKLuNv3yusFs1TVoIPWlr1Pnq/olQQWaShj7iFQioKQSQtMfJC xBJrn1IRGaYqR31VzxZ4KWof5QU+1hAgyxLnoZaHqYiNTIQWz2G0LYKs9QdQmyZ2 IP5WXtGVXi6U1VClIpr6GzMebGMGObQqlpzqN23EEmUjIIML1lWX/3vNqXjp7WsH pcalf7PdthnKINn7IWcfLcmJydWQz4lihs/sm5oT9KwnlQtryH3pTa1C5qHP4vK2 lIPc6jAhr9X0tY28YzBPRHej9ChVm61Qrkudeg7fGZ7arKFRDDG/h1TbJDEdCOw= =42qZ -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Wed Aug 29 03:39:58 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4A55106564A for ; Wed, 29 Aug 2012 03:39:58 +0000 (UTC) (envelope-from prvs=1581c7f85d=greg.robinson@dsto.defence.gov.au) Received: from defence.gov.au (actmail.defence.gov.au [203.6.68.1]) by mx1.freebsd.org (Postfix) with ESMTP id 0794D8FC16 for ; Wed, 29 Aug 2012 03:39:57 +0000 (UTC) X-MimeOLE: Produced By Microsoft Exchange V6.5 x-titus-version: 3.0.65 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable x-protective-marking: VER=2005.6, NS=gov.au, SEC=UNCLASSIFIED, ORIGIN=greg.robinson@dsto.defence.gov.au x-tituslabs-classifications-30: Classification=UNCLASSIFIED; Precedence=ROUTINE; Privacy= ; Content-class: urn:content-classes:message Date: Wed, 29 Aug 2012 12:54:42 +0930 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: zvol + raidz issue? - a similar question [SEC=UNCLASSIFIED] Thread-Index: Ac2FldOWAMMDJYuTQtO/uDCNB9q9+Q== From: "Robinson, Greg" To: X-OriginalArrivalTime: 29 Aug 2012 03:24:42.0848 (UTC) FILETIME=[D4AF1E00:01CD8595] X-TM-AS-Product-Ver: SMEX-10.0.0.1412-6.800.1017-19146.001 X-TM-AS-Result: No--1.810100-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No Subject: Re: zvol + raidz issue? - a similar question [SEC=UNCLASSIFIED] 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, 29 Aug 2012 03:39:58 -0000 UNCLASSIFIED Hi, Along the lines on Niki's question, could someone explain the difference between the following zfs commands in terms of performance: zpool create -m /export fooz raidz da0 da1 da2 da3 da4 mkdir /export/home vs. zpool create fooz raidz da0 da1 da2 da3 da4 zfs create fooz/home (or in Niki's example): zfs create -b 128k fooz/home I think I'm in the same boat as Niki, seeing some performance issues with my setup... Greg. IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From owner-freebsd-fs@FreeBSD.ORG Wed Aug 29 10:53:53 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A4C22106566B for ; Wed, 29 Aug 2012 10:53:53 +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 3AD108FC16 for ; Wed, 29 Aug 2012 10:53:52 +0000 (UTC) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.5/8.14.5) with ESMTP id q7TArmXP016212; Wed, 29 Aug 2012 11:53:48 +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 q7TArlJE000413; Wed, 29 Aug 2012 11:53:47 +0100 Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id q7TArlAs000409; Wed, 29 Aug 2012 11:53:47 +0100 Date: Wed, 29 Aug 2012 11:53:47 +0100 Message-Id: <201208291053.q7TArlAs000409@higson.cam.lispworks.com> From: Martin Simmons To: Tim Gustafson In-reply-to: (message from Tim Gustafson on Tue, 28 Aug 2012 11:15:35 -0700) References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 29 Aug 2012 10:53:53 -0000 >>>>> On Tue, 28 Aug 2012 11:15:35 -0700, Tim Gustafson said: > > > Note that amd mounts the filesystem in a hidden directory (named by the fs > > option) and makes a symlink to it from the directory named in amd.conf. You > > shouldn't set fs to the directory named in amd.conf. > > I'm not using the symlinks option; I've specified "autofs_use_lofs = > yes" to mount the directories in-place. I don't want AMD's normal > symlink structure because I want all the mounts to behave the same way > as the Linux/Mac/Sun machines do. AFAIK, you can't avoid the symlinks for nfs mounts (it only affects local type:=link mounts). Also, autofs (and hence autofs_use_lofs) isn't implemented on FreeBSD (it only works in conjunction with autofs on Linux and Solaris). __Martin From owner-freebsd-fs@FreeBSD.ORG Wed Aug 29 12:59:18 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56049106564A; Wed, 29 Aug 2012 12:59:18 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id F129E8FC17; Wed, 29 Aug 2012 12:59:17 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EANARPlCDaFvO/2dsb2JhbABFhgO1c4IgAQEBAwEBAQEgKyALBRYYAgINGQIpAQkmDgcEARwEh2YGC6g6kxSBIYoBAYUsgRIDkyuCK4EUiBuGZoJ/gUU X-IronPort-AV: E=Sophos;i="4.80,334,1344225600"; d="scan'208";a="179434971" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 29 Aug 2012 08:59:11 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 09C86B401F; Wed, 29 Aug 2012 08:59:11 -0400 (EDT) Date: Wed, 29 Aug 2012 08:59:11 -0400 (EDT) From: Rick Macklem To: d@delphij.net Message-ID: <140200696.1251333.1346245151029.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <503D301F.5080607@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@FreeBSD.ORG, rmacklem@FreeBSD.org Subject: Re: Why vfs_stdcheckexp is a VFS operation? 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, 29 Aug 2012 12:59:18 -0000 Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi, > > We have recently run into a problem with exports(5) and I then read > the code of mountd(8) as well as sys/kern/vfs_exports.c and found that > vfs_stdcheckexp is a VFS operation and not a vnode operation. > > So for instance if one exports a mountpoint, and later changes his > mind and export a directory under that mountpoint, clients that have > mounted the mountpoint before the second operation will still have > access. > > Is this intentional (e.g. for performance consideration?) > Short answer..yes. Longer answer... A vnode is only cached in the kernel, so the exports would drop out of the cache when the vnode does. Also, this is checked for every RPC, so it does need to be efficient and there is no easy way to determine of the file object referred to by a vnode is a child (in the director subtree) of another vnode with exports on it. (I suppose there might be a way to hang exports off of every vnode, by having vnodes inherit their exports from their parents, but that would be a major VFS/VOP change.) Exporting a directory that is not a mount point only implements what rwatson@ referred to as an "administrative control" enforced only by mountd for the Mount protocol (NFS doesn't know anything about "mounts"). The ancient history of this goes something like: - When Sun introduced NFS in 1985, the exports were only done by the Mount protocol and nothing was enforced by the kernel. - I think I introduced the first case where exports were enforced on a per RPC case by hanging them off the mountpoints in the kernel, for 4.3Reno (about 1988?). - When I did so, I felt that restricting /etc/exports to server mount points made sense (and I'll admit I still feel that way), but others wanted /etc/exports to remain SunOS compatible (since NFS was "their protocol" is those days). It seems that changing the semantics of /etc/exports is very difficult (it's a stumbling block w.r.t. adoption of nfse, as an example) at this time so, although confusing, exporting a directory that is not a mount point results in the entire mount point exported for NFS RPCs, but a restriction of only mounting that directory is enforced for the Mount protocol (only done at mount time and only for NFSv3). rick > Cheers, > - -- > Xin LI https://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBCAAGBQJQPTAfAAoJEG80Jeu8UPuzGykIAIBOrRNGsqgLNzIpEtqsBjKE > ZSGTVLCfoAWeeOLKLuNv3yusFs1TVoIPWlr1Pnq/olQQWaShj7iFQioKQSQtMfJC > xBJrn1IRGaYqR31VzxZ4KWof5QU+1hAgyxLnoZaHqYiNTIQWz2G0LYKs9QdQmyZ2 > IP5WXtGVXi6U1VClIpr6GzMebGMGObQqlpzqN23EEmUjIIML1lWX/3vNqXjp7WsH > pcalf7PdthnKINn7IWcfLcmJydWQz4lihs/sm5oT9KwnlQtryH3pTa1C5qHP4vK2 > lIPc6jAhr9X0tY28YzBPRHej9ChVm61Qrkudeg7fGZ7arKFRDDG/h1TbJDEdCOw= > =42qZ > -----END PGP SIGNATURE----- > _______________________________________________ > 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 Wed Aug 29 13:29:17 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 188951065686 for ; Wed, 29 Aug 2012 13:29:17 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id C42D08FC1A for ; Wed, 29 Aug 2012 13:29:16 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EAGQYPlCDaFvO/2dsb2JhbABFhgO1c4IgAQEBAwEBAQEgKyALBRYYAgINGQIpAQkmBggHBAEaAgSHZgYLqDeTE4EhigGFLYESA5MrgiuBFI8Bgn+BRQ X-IronPort-AV: E=Sophos;i="4.80,334,1344225600"; d="scan'208";a="176995433" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 29 Aug 2012 09:29:10 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id E8F77B401F; Wed, 29 Aug 2012 09:29:09 -0400 (EDT) Date: Wed, 29 Aug 2012 09:29:09 -0400 (EDT) From: Rick Macklem To: =?utf-8?Q?Attila_Bog=C3=A1r?= Message-ID: <487642909.1254184.1346246949938.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <503CE012.3040408@linguamatics.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@FreeBSD.org Subject: Re: Need hints debugging KGSSAPI 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, 29 Aug 2012 13:29:17 -0000 Attila wrote: > Hi, > > I'd like to spend some time finding out myself what's wrong with the > kerberized nfs server on the FreeBSD 9-STABLE. > > I thought the solution is to simply force DES+RFC1964 GSSAPI, but > unfortunately it's not that simple. > I built a patched nfs-utils package by merging the patch referenced > from > https://bugzilla.redhat.com/show_bug.cgi?id=802469 - with the legacy > option did not resolve the problem. > > I have some wireshark traces which show that one EL6 box get 3 times > auth_denied however the other succeeds for the 3rd time. I can > reproduce this. > > My kernel is a GENERIC + some option as per Rick's page: > options KGSSAPI > device crypto > device cryptodev > > I know, that all interesting NFS/GSSAPI job is done within kernel > space. > Not exactly. All the KGSSAPI does is package up the arguments for the GSS api call and then do an upcall to the userland gssd. The userland gssd does the GSS api call against the Kerberos libraries it has been linked to and then passes the results of that call back down into the kernel. So, once you get past the RPCSEC_GSS stuff and down to the actual GSS API call, it is the userland Kerberos libraries that do the interesting stuff. (There are a few tricks, like a "hidden effective uid argument" for init_sec_context(), but mostly the KGSSAPI/gssd just passes arguments between the kernel call and the userland Kerberos library.) > I suppose it's not possible to unload the KGSSAPI module: > http://svnweb.freebsd.org/base/head/sys/kgssapi/gss_impl.c?view=markup&pathrev=224084 > > What's the best way to debug the kernel other than inserting debug > messages into the source tree+recompiling+rebooting? > I'm an old fashioned printf() guy, so that's what I do. If it appears that it is the upcall to the userland gssd that generates a failed reply, then the problem is most likely the userland Kerberos libraries. (I'd probably cram a pile of printf()s in the rpcsec_gss and kgssapi sources, especially at the kgssapi upcalls to the userland gssd, to try and figure out where the "authentication failure" is occurring.) I've already emailed this person w.r.t. making sure he isn't seeing the "non-atomic export update" problem. Since mountd deletes all exports and then re-adds them non-atomically, the security flavours allowed will be messed up whenever mountd gets a HUP signal. (This happens automagically whenever a "mount" of a file system happens on the NFS server, since "mount" sends "mountd" a HUP signal.) If it is the userland Kerberos libraries, I'd try installing a vanilla up to date Heimdal distro (it usually installs easily in somewhere like /usr/heimdal) and then I'd rebuild gssd.c linked to those libraries and see if I could get that to work. Long ago, to get kerberized NFS to work on OpenBSD, I'd statically link the gssd I had for it (very different than the FreeBSD gssd) to freshly built Heimdal libraries. rick > What debugger do you recommend? > Is there an up-to-date tutorial on FreeBSD kernel debugging? > > Any constructive comments appreciated. > > Thanks, > Attila > _______________________________________________ > 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 Wed Aug 29 14:19:31 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 221F61065670 for ; Wed, 29 Aug 2012 14:19:31 +0000 (UTC) (envelope-from antonintessier@live.fr) Received: from dub0-omc4-s28.dub0.hotmail.com (dub0-omc4-s28.dub0.hotmail.com [157.55.2.103]) by mx1.freebsd.org (Postfix) with ESMTP id AB8F88FC08 for ; Wed, 29 Aug 2012 14:19:30 +0000 (UTC) Received: from DUB109-W51 ([157.55.2.72]) by dub0-omc4-s28.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 29 Aug 2012 07:18:22 -0700 Message-ID: X-Originating-IP: [93.182.202.8] From: antonin tessier To: Date: Wed, 29 Aug 2012 16:18:23 +0200 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 29 Aug 2012 14:18:22.0827 (UTC) FILETIME=[259CFBB0:01CD85F1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Error using truecrypt 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, 29 Aug 2012 14:19:31 -0000 Hi=2C I get a problem trying to mount a Truecrypt file under FreeBSD 9.0 STABLE. = Indeed=2C truecrypt file /mnt returns me=20 =09 Error: mount: /dev/md0: Invalid argument How would I figure this out? Thanks=2C Gollum. = From owner-freebsd-fs@FreeBSD.ORG Wed Aug 29 16:05:06 2012 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 E16541065670 for ; Wed, 29 Aug 2012 16:05:05 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id AC7F68FC14 for ; Wed, 29 Aug 2012 16:05:05 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so1504281pbb.13 for ; Wed, 29 Aug 2012 09:05:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wMl41jf9HRl3MjxS/u1Fx5Fw+BrohpXA26vT8qeDrhE=; b=HZ1Vzz8hc45OuI+MJ4STyPOqQRvUXmjlfc+oAp7o8iAqeqNIhAJ5pPHY6mkqMm2X2Q VwJqh/Kez8nP1abeuVF2b5OXct9AsKUgClOuLqy3wsCFTChZG0yu5Llc0BHqRGYceMOo pb1E/BBOIfHUE4Wto6WVzsDcGyUXbzc0Xj9/o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=wMl41jf9HRl3MjxS/u1Fx5Fw+BrohpXA26vT8qeDrhE=; b=iwka5wDSdUgKS2ViDxSDPZAZ0Dj0B8c0tdgOfRDDa4EvosCPuYTXkeo6dX2cHEitlh jN0Y7mYvqM1NDheyd82cjR2HSqR2TpObh1u4eIoTdhK7WvpSxpJiUZUoGHt5yatJxDJH X6Q5cbO9sUhuPl1ClNDvzHbYHtw54j0IoaKhFMHyug8TX0qQBOjO3Rx3vc4DPy72WwQ5 2MDg7iUalBlJVfzE1GEkOUtD/4p1k3Grk5QZs6HLCprEhJL8UE10J/O5Ahl3PXbCMjIg 6I+xqSsZiRolH7Abgm36oRfATuC8mVhPrW/LSUz4FZRPMtdI24wtKbKUbqAvylTNY0/P Se2Q== MIME-Version: 1.0 Received: by 10.68.218.162 with SMTP id ph2mr5763851pbc.21.1346256305011; Wed, 29 Aug 2012 09:05:05 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Wed, 29 Aug 2012 09:05:04 -0700 (PDT) In-Reply-To: <201208291053.q7TArlAs000409@higson.cam.lispworks.com> References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> Date: Wed, 29 Aug 2012 09:05:04 -0700 Message-ID: From: Tim Gustafson To: Martin Simmons Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkbCaXGkV0pYNJxrqDpD2sG6Rqj5jq0iQRegWFtCijcs8Bwerezpmo2vyda5bHkLCKGmxWm Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 29 Aug 2012 16:05:06 -0000 > AFAIK, you can't avoid the symlinks for nfs mounts (it only affects local > type:=link mounts). Also, autofs (and hence autofs_use_lofs) isn't > implemented on FreeBSD (it only works in conjunction with autofs on Linux and > Solaris). Is there a particular reason that autofs isn't implemented in FreeBSD? I've asked this question before on a few other lists and haven't really gotten a satisfactory answer. Autofs is supported by Sun, Linux and Mac - basically everyone except FreeBSD. I actually talked about why it wasn't implemented with both Alfred Perlstein a while ago, and Jordan Hubbard more recently, and it seems that originally Apple threatened Alfred with a lawsuit for patent infringement way back when, but Jordan's more recent position on the matter was that the patent thing probably wouldn't be an issue anymore, but that Alfred's original code would more or less have to be re-written at this point, due to changes in the FreeBSD over the years. Not having autofs on FreeBSD is a real thorn in my side. I'm trying to get FreeBSD implemented more at UCSC, and specifically the School of Engineering, as a large-volume file server, and the lack of a proper auto-mounter that works the same way (or at least close enough) as all our other systems is a huge roadblock. I'm not much of a kernel hacker, otherwise I might attempt this myself, but it seems like this can't possibly be that hard, especially since it's implemented in Linux, which is GPL'd and therefore open to porting. I'm trying hard to not sound whiny here, because I certainly do appreciate all the work that everyone has done on FreeBSD...so please don't take this e-mail as a complaint. I'm just trying to understand how we got here, and what it might take to get autofs working on FreeBSD. -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Wed Aug 29 17:15:47 2012 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 1E62B106566B for ; Wed, 29 Aug 2012 17:15:47 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id CF27D8FC16 for ; Wed, 29 Aug 2012 17:15:46 +0000 (UTC) Received: from scooby.simplesystems.org (scooby.simplesystems.org [65.66.246.67]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q7THFdB1017608; Wed, 29 Aug 2012 12:15:39 -0500 (CDT) Date: Wed, 29 Aug 2012 12:15:39 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@scooby.simplesystems.org To: Tim Gustafson In-Reply-To: Message-ID: References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Wed, 29 Aug 2012 12:15:39 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 29 Aug 2012 17:15:47 -0000 On Wed, 29 Aug 2012, Tim Gustafson wrote: > > Not having autofs on FreeBSD is a real thorn in my side. I'm trying > to get FreeBSD implemented more at UCSC, and specifically the School > of Engineering, as a large-volume file server, and the lack of a > proper auto-mounter that works the same way (or at least close enough) > as all our other systems is a huge roadblock. I agree. I don't understand the relationship between FreeBSD and AMD (am-utils). FreeBSD barely admits to having AMD and does not provide any documentation for it. Likewise, books about FreeBSD do not discuss the automounter. > I'm not much of a kernel hacker, otherwise I might attempt this > myself, but it seems like this can't possibly be that hard, especially > since it's implemented in Linux, which is GPL'd and therefore open to > porting. It would be more reasonable to re-use the Sun automounter code from Illumos which should be under CDDL license like zfs. The Sun automounter code is more mature than Linux automounter and has fewer missing features and fewer bugs. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Wed Aug 29 22:41:42 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E87981065670 for ; Wed, 29 Aug 2012 22:41:42 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9F4B08FC08 for ; Wed, 29 Aug 2012 22:41:42 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAEyZPlCDaFvO/2dsb2JhbABFhgO1doIgAQEBAwEBAQEgKyAEBwUWDgoCAg0ZAikBCSYGCAcEAQgUBIdmBguocJMpgSGJZxqFLYESA5MrgiuBFI8Bgn+BRQ X-IronPort-AV: E=Sophos;i="4.80,336,1344225600"; d="scan'208";a="177074082" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 29 Aug 2012 18:41:34 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id B1528B3FE3; Wed, 29 Aug 2012 18:41:33 -0400 (EDT) Date: Wed, 29 Aug 2012 18:41:33 -0400 (EDT) From: Rick Macklem To: Bob Friesenhahn Message-ID: <1825065717.1296363.1346280093679.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 29 Aug 2012 22:41:43 -0000 Bob Friesenhahn wrote: > On Wed, 29 Aug 2012, Tim Gustafson wrote: > > > > Not having autofs on FreeBSD is a real thorn in my side. I'm trying > > to get FreeBSD implemented more at UCSC, and specifically the School > > of Engineering, as a large-volume file server, and the lack of a > > proper auto-mounter that works the same way (or at least close > > enough) > > as all our other systems is a huge roadblock. > > I agree. I don't understand the relationship between FreeBSD and AMD > (am-utils). FreeBSD barely admits to having AMD and does not provide > any documentation for it. Likewise, books about FreeBSD do not > discuss the automounter. > Among other things, I think amd is the last thing to use the old mount(2) syscall instead of nmount(2) for NFS mounts. I haven't had the nerve to even look at the code. > > I'm not much of a kernel hacker, otherwise I might attempt this > > myself, but it seems like this can't possibly be that hard, > > especially > > since it's implemented in Linux, which is GPL'd and therefore open > > to > > porting. > > It would be more reasonable to re-use the Sun automounter code from > Illumos which should be under CDDL license like zfs. The Sun > automounter code is more mature than Linux automounter and has fewer > missing features and fewer bugs. > I had actually thought that the Mac OS X autofs was based on the Solaris one, but I could be incorrect? I think I've also mentioned that an autofs port would be nice. I suspect the reason it hasn't happened is simply "no one with the time/resources and skills has volunteered to do it"? (I am not familiar with Alfred's port and there may be others I am not familiar with. I am also not familiar with any patent issues that might exist. Talk of patents does make me nervous, but I would hope that the CDDL'd code would be ok to include as a loadable module.) rick > Bob > -- > Bob Friesenhahn > bfriesen@simple.dallas.tx.us, > http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.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" From owner-freebsd-fs@FreeBSD.ORG Wed Aug 29 23:01:48 2012 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 8C1511065670 for ; Wed, 29 Aug 2012 23:01:48 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 4D7918FC19 for ; Wed, 29 Aug 2012 23:01:47 +0000 (UTC) Received: from scooby.simplesystems.org (scooby.simplesystems.org [65.66.246.67]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q7TN1kGk018880; Wed, 29 Aug 2012 18:01:46 -0500 (CDT) Date: Wed, 29 Aug 2012 18:01:46 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@scooby.simplesystems.org To: Rick Macklem In-Reply-To: <1825065717.1296363.1346280093679.JavaMail.root@erie.cs.uoguelph.ca> Message-ID: References: <1825065717.1296363.1346280093679.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Wed, 29 Aug 2012 18:01:47 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 29 Aug 2012 23:01:48 -0000 On Wed, 29 Aug 2012, Rick Macklem wrote: >> >> It would be more reasonable to re-use the Sun automounter code from >> Illumos which should be under CDDL license like zfs. The Sun >> automounter code is more mature than Linux automounter and has fewer >> missing features and fewer bugs. >> > I had actually thought that the Mac OS X autofs was based on the Solaris > one, but I could be incorrect? You are probably correct. I noticed that the Mac OS X Leopard autofs template configuration files were byte-for-byte identical to those on Solaris 10. I also found that the Mac OS X automounter worked fine. > with Alfred's port and there may be others I am not familiar with. I am > also not familiar with any patent issues that might exist. Talk of patents > does make me nervous, but I would hope that the CDDL'd code would be ok > to include as a loadable module.) The automounter seems rather low-tech and I can't imagine any active patents which might apply to it. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 12:07:15 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 50B061065677 for ; Thu, 30 Aug 2012 12:07:15 +0000 (UTC) (envelope-from attila.bogar@linguamatics.com) Received: from mail.linguamatics.com (mail.linguamatics.com [188.39.80.203]) by mx1.freebsd.org (Postfix) with ESMTP id AD7AD8FC1D for ; Thu, 30 Aug 2012 12:07:14 +0000 (UTC) Received: from [10.252.10.232] (random.linguamatics.com [10.252.10.232]) by mail.linguamatics.com (Postfix) with ESMTPSA id B55C2EFB450; Thu, 30 Aug 2012 13:07:06 +0100 (BST) Message-ID: <503F576A.7030102@linguamatics.com> Date: Thu, 30 Aug 2012 13:07:06 +0100 From: =?UTF-8?B?QXR0aWxhIEJvZ8Ohcg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Rick Macklem References: <487642909.1254184.1346246949938.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <487642909.1254184.1346246949938.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@FreeBSD.org Subject: KRPC layer: NFS requests are not processed 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, 30 Aug 2012 12:07:15 -0000 Hi Rick, On 29/08/12 14:29, Rick Macklem wrote: > I'm an old fashioned printf() guy, so that's what I do. If it appears > that it is the upcall to the userland gssd that generates a failed > reply, then the problem is most likely the userland Kerberos > libraries. (I'd probably cram a pile of printf()s in the rpcsec_gss > and kgssapi sources, especially at the kgssapi upcalls to the userland > gssd, to try and figure out where the "authentication failure" is > occurring.) I've already emailed this person w.r.t. making sure he > isn't seeing the "non-atomic export update" problem. Since mountd > deletes all exports and then re-adds them non-atomically, the security > flavours allowed will be messed up whenever mountd gets a HUP signal. > (This happens automagically whenever a "mount" of a file system > happens on the NFS server, since "mount" sends "mountd" a HUP signal.) > If it is the userland Kerberos libraries, I'd try installing a vanilla > up to date Heimdal distro (it usually installs easily in somewhere > like /usr/heimdal) and then I'd rebuild gssd.c linked to those > libraries and see if I could get that to work. Long ago, to get > kerberized NFS to work on OpenBSD, I'd statically link the gssd I had > for it (very different than the FreeBSD gssd) to freshly built Heimdal > libraries. rick Thanks for your hints. I done all you suggested and now I see, that the problem lies on an upper level. I changed the subject according to this. I'm debugging now NFSv4 What I can see so far: - the "old" RHEL5 linux clients open 2 NFS TCP connection per mount request and it's successful - the "new" RHEL6 non-working or partly-working linux clients open at least 4 NFS TCP connection per mount request - I have two identically setup boxes (a vm and a bare metal) and the bare metal fails to mount all the time - the bare metal is a faster machine Furthermore: ./fs/nfsserver/nfs_nfsdkrpc.c: in nfsrvd_addsock(): before the out: label the svc_reg()'s are called. BUT same file: nfssvc_program() is not called for these TCP connections This could be a timing, locking, parallel race condition, rpc parsing or some other issue. I'm aware mountd HUP bug, it's an annoying one but I think we can rule this out for this case. In this thread http://lists.freebsd.org/pipermail/freebsd-stable/2012-August/069052.html I learned, that - the freebsd team doesn't want these patches to hanging around for years in the PR database without committing them - the freebsd committers and you do the volunteering for free and I think this is great thing which should be appreciated by everyone using freebsd - the closed ticket rate is around 1/3 rate of the opened ones in the kern category - the freebsd team is urges if users come up with patches as everyone does this in his/her spare time It is a fact that commiting a verified patch we kwow is much less effort than to to diagnose the problem and to come up with the patch. Ignoring the patches (effort of their userbase) for multiple years is not a fair attitude from the freebsd team even if they are resource limited. In other words if verified patches cannot be get committed into the stable means that freebsd is an OS with a growing number of bugs. From my point of view: - I currently have a freebsd-stable with some patches which I need to maintain during every upgrade. - I do not like this approach and I suppose the people experiencing the same problem and patching their system with the same patches do not like either. - the people who can't find these bugs in the pr database for the same problem are the most frustrated ones, because they feel, that freebsd is no good for them I'm happy to put effort into fixing this bug and possibly come up with a patch or diagnose the specific problem. What I'm certainly not happy to do and I won't do is to spend my time gratuitously with my patch hanging around in the PR database for years without being commited. I'd like to kindly ask you and other people involved in the freebsd project: how could patches be included in the -stable? Kind regards, Attila From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 16:23:54 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BDA99106564A for ; Thu, 30 Aug 2012 16:23: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 319E18FC18 for ; Thu, 30 Aug 2012 16:23:53 +0000 (UTC) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.5/8.14.5) with ESMTP id q7UGNj4M070982; Thu, 30 Aug 2012 17:23:45 +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 q7UGNiDP006231; Thu, 30 Aug 2012 17:23:44 +0100 Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id q7UGNiEr006228; Thu, 30 Aug 2012 17:23:44 +0100 Date: Thu, 30 Aug 2012 17:23:44 +0100 Message-Id: <201208301623.q7UGNiEr006228@higson.cam.lispworks.com> From: Martin Simmons To: Bob Friesenhahn In-reply-to: (message from Bob Friesenhahn on Wed, 29 Aug 2012 12:15:39 -0500 (CDT)) References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 16:23:54 -0000 >>>>> On Wed, 29 Aug 2012 12:15:39 -0500 (CDT), Bob Friesenhahn said: > > On Wed, 29 Aug 2012, Tim Gustafson wrote: > > > > Not having autofs on FreeBSD is a real thorn in my side. I'm trying > > to get FreeBSD implemented more at UCSC, and specifically the School > > of Engineering, as a large-volume file server, and the lack of a > > proper auto-mounter that works the same way (or at least close enough) > > as all our other systems is a huge roadblock. > > I agree. I don't understand the relationship between FreeBSD and AMD > (am-utils). FreeBSD barely admits to having AMD and does not provide > any documentation for it. Hmm, there is an example of AMD in the FreeBSD Handbook and extensive documentation via man pages and info pages. > > I'm not much of a kernel hacker, otherwise I might attempt this > > myself, but it seems like this can't possibly be that hard, especially > > since it's implemented in Linux, which is GPL'd and therefore open to > > porting. > > It would be more reasonable to re-use the Sun automounter code from > Illumos which should be under CDDL license like zfs. The Sun > automounter code is more mature than Linux automounter and has fewer > missing features and fewer bugs. I would miss AMD things like type:=link and normalize_hostnames for preventing duplicate mounts of the same resource. __Martin From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 16:52:42 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 172171065670 for ; Thu, 30 Aug 2012 16:52:42 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id D245C8FC18 for ; Thu, 30 Aug 2012 16:52:40 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so3533498pbb.13 for ; Thu, 30 Aug 2012 09:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=a9QaYdG2z7naPO0lSErXPrdaQB9T5Ta4Q4rsI3kCRkU=; b=gsB/JguETCkScX0ly9lKUMcHC9PX3ZxjuI+awSixJT3fI4N1JMuUT+VzDr+lUdBjoQ zF7OdznNmtGcN+37XxTM2lKtORbA/2JNOJ7xNMf82Fhs2T0Cd/WWXYdO3GdmvmR4fmxN cSkzxCF3XH7UBUVVPNBu/vCM1Xy1+F/8pje2k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=a9QaYdG2z7naPO0lSErXPrdaQB9T5Ta4Q4rsI3kCRkU=; b=HfWj5JNklvGaR+etvg96AAKafvpT6/THYr44reYIf9Zqd7ljntQu6cnYjcAnjRAdFX j7l7+rsT+M5ftB7sgSOs4XthjZ91QzIr2K2dxFmtWgXEJgK4ybpgb/Cpf6VQxBLODrax rQN0yqR2EvWhyKyx/mmT7GousfFX29UqKDkIxREsmJ4Q4DXSUSNtnKbuDfIeyh697Wkt KLq2it0xKVvV3GcUjmHbp0XA7T39xGWKPkkzv3rAAwZJMXY79V06gnzv7QVqaqx9S7ST IQaJLvcV5pS8/tU0f1Snu87AId+kGOMW3uTrBZkDnIrxQFuvO/QiClDzZHNrmrAguX2a Cocw== MIME-Version: 1.0 Received: by 10.68.218.162 with SMTP id ph2mr12474288pbc.21.1346345560491; Thu, 30 Aug 2012 09:52:40 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Thu, 30 Aug 2012 09:52:40 -0700 (PDT) In-Reply-To: <201208301623.q7UGNiEr006228@higson.cam.lispworks.com> References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> <201208301623.q7UGNiEr006228@higson.cam.lispworks.com> Date: Thu, 30 Aug 2012 09:52:40 -0700 Message-ID: From: Tim Gustafson To: Martin Simmons Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmbnOIV8sCy6xRq9886lM1TJ61m6Uqwz/N7EqS7SjdWYAx8d4pm6W7wKbf2HVD3YDBfaERa Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 16:52:42 -0000 > I would miss AMD things like type:=link and normalize_hostnames for > preventing duplicate mounts of the same resource. I don't think anyone is suggesting we deprecate AMD. I'd just like to have autofs as an option. -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 17:36:41 2012 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 9B78C106564A for ; Thu, 30 Aug 2012 17:36:41 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 5EA4B8FC1D for ; Thu, 30 Aug 2012 17:36:41 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.80 (FreeBSD)) (envelope-from ) id 1T78fV-000B0Z-4Z; Thu, 30 Aug 2012 13:36:37 -0400 Date: Thu, 30 Aug 2012 13:36:37 -0400 From: Gary Palmer To: Tim Gustafson Message-ID: <20120830173636.GC2526@in-addr.com> References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> <201208301623.q7UGNiEr006228@higson.cam.lispworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 17:36:41 -0000 On Thu, Aug 30, 2012 at 09:52:40AM -0700, Tim Gustafson wrote: > > I would miss AMD things like type:=link and normalize_hostnames for > > preventing duplicate mounts of the same resource. > > I don't think anyone is suggesting we deprecate AMD. I'd just like to > have autofs as an option. Is autofs purely userland? Could it be in ports? Gary From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 17:38:21 2012 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 32F69106566B for ; Thu, 30 Aug 2012 17:38:21 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id EC7D58FC25 for ; Thu, 30 Aug 2012 17:38:20 +0000 (UTC) Received: by dadr6 with SMTP id r6so1355848dad.13 for ; Thu, 30 Aug 2012 10:38:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2hcvied5iqmCuYC/TyFTNDndVxZOWK8ycmdBr/mDr7Q=; b=U0XI6pX5x9iL1K21MoOyBBj41V6qqOmdfbCpjX+9cgirkIDKLbHtx+Ftc1VRze3Yqz NaDDrSe9M8/+0JhhAXcFX7WbdSFTbgM1j/U4tmpHTPKqBumlRQ+yoiyRwHs6T1v8rcj2 CnvflPkGWML9rH1GCmRVfPUcutgCrHA9ZehFs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=2hcvied5iqmCuYC/TyFTNDndVxZOWK8ycmdBr/mDr7Q=; b=i2E42BfSDKkNfzxyT6vgByQ2YaUmUBtQBnpt/huTnRGFaLFf+8ipUpK39sUTmK+3Jc w2sHQh4p2nUPbooqbl3MhZEU02/dlvQxpORQX2qiRrsfmYovUpusDkDN638cPM93i8J2 hK3pBN6EKrSCSl+YJIVFLJLyfZx6ZFteB2Zl8xcQb7YMKy/9xF8UPbrSWD72XmG31rv/ SXhtiOg/PC6c58tzNYEGJ+PgDQOTWIUs+0priMVncd6y2ReqybIRpRLkt6XjS65LQprC qpjlV1OJJtuGuaEQu7XJ9n9rvFFZUimjpB3e8cvY+uc1IDSbBUq2crGUNxlTjxiZ/G+B 53rQ== MIME-Version: 1.0 Received: by 10.68.221.168 with SMTP id qf8mr12542501pbc.37.1346348300279; Thu, 30 Aug 2012 10:38:20 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Thu, 30 Aug 2012 10:38:20 -0700 (PDT) In-Reply-To: <20120830173636.GC2526@in-addr.com> References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> <201208301623.q7UGNiEr006228@higson.cam.lispworks.com> <20120830173636.GC2526@in-addr.com> Date: Thu, 30 Aug 2012 10:38:20 -0700 Message-ID: From: Tim Gustafson To: Gary Palmer Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlpiTlBWztQR3D2dw7gAFBaZ9N+5brDXdj5PSk5uAyejTn2i8RQDnGhfuMJqyvvpBIN1UW6 Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 17:38:21 -0000 > Is autofs purely userland? Could it be in ports? Yes, I believe so. -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 17:46:10 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C19C10657AC for ; Thu, 30 Aug 2012 17:46:10 +0000 (UTC) (envelope-from hans@beastielabs.net) Received: from mail.beastielabs.net (beasties.demon.nl [82.161.3.114]) by mx1.freebsd.org (Postfix) with ESMTP id F015A8FC0A for ; Thu, 30 Aug 2012 17:46:08 +0000 (UTC) Received: from merom.hotsoft.nl (merom.hotsoft.nl [192.168.0.12]) by mail.beastielabs.net (8.14.5/8.14.5) with ESMTP id q7UHk0IE020402; Thu, 30 Aug 2012 19:46:01 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <503FA6D8.5070309@beastielabs.net> Date: Thu, 30 Aug 2012 19:46:00 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: Bob Friesenhahn References: <1825065717.1296363.1346280093679.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 17:46:10 -0000 On 08/30/12 01:01, Bob Friesenhahn wrote: > On Wed, 29 Aug 2012, Rick Macklem wrote: >>> >>> It would be more reasonable to re-use the Sun automounter code from >>> Illumos which should be under CDDL license like zfs. The Sun >>> automounter code is more mature than Linux automounter and has fewer >>> missing features and fewer bugs. >>> >> I had actually thought that the Mac OS X autofs was based on the Solaris >> one, but I could be incorrect? > > You are probably correct. I noticed that the Mac OS X Leopard autofs > template configuration files were byte-for-byte identical to those on > Solaris 10. I also found that the Mac OS X automounter worked fine. > >> with Alfred's port and there may be others I am not familiar with. I am >> also not familiar with any patent issues that might exist. Talk of >> patents >> does make me nervous, but I would hope that the CDDL'd code would be ok >> to include as a loadable module.) > > The automounter seems rather low-tech and I can't imagine any active > patents which might apply to it. > Well, implementing a "real" Autofs is probably not that easy. We have seen both Solaris and Linux going through several iterations to get it (mostly) right. If there are any patents on this kind of technology they might very well have expired by now: Autofs as a concept is from the early 90's. As I have mentioned before, AutoFS for FreeBSD was the topic of a GSoC 2006 project and results seem to be presented at BSDCan 2007, see: http://www.bsdcan.org/2007/schedule/events/32.en.html (The presentation has a .ppt extension, but is actually a pdf). Despite plans, to my knowledge nothing ever happened with the results and I have no idea why. As far as I know, the sources are only viewable in Perforce, but not (easily) downloadable by mere mortals, and probably quite stale by now. It might already help if somebody liberated the code from Perforce and put it up for download somewhere. I agree that having a real AutoFS fully interoperable with Linux and Solaris (and Mac OS-X ?) would be really nice to have, especially for scientific and engineering environments. Kind regards, Hans Ottevanger From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 18:09:08 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0EE6E106564A; Thu, 30 Aug 2012 18:09:08 +0000 (UTC) (envelope-from hans@beastielabs.net) Received: from mail.beastielabs.net (beasties.demon.nl [82.161.3.114]) by mx1.freebsd.org (Postfix) with ESMTP id 85CF38FC1E; Thu, 30 Aug 2012 18:09:06 +0000 (UTC) Received: from merom.hotsoft.nl (merom.hotsoft.nl [192.168.0.12]) by mail.beastielabs.net (8.14.5/8.14.5) with ESMTP id q7UI94ZM020474; Thu, 30 Aug 2012 20:09:04 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <503FAC40.4050505@beastielabs.net> Date: Thu, 30 Aug 2012 20:09:04 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: Gary Palmer References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> <201208301623.q7UGNiEr006228@higson.cam.lispworks.com> <20120830173636.GC2526@in-addr.com> In-Reply-To: <20120830173636.GC2526@in-addr.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 18:09:08 -0000 On 08/30/12 19:36, Gary Palmer wrote: > On Thu, Aug 30, 2012 at 09:52:40AM -0700, Tim Gustafson wrote: >>> I would miss AMD things like type:=link and normalize_hostnames for >>> preventing duplicate mounts of the same resource. >> >> I don't think anyone is suggesting we deprecate AMD. I'd just like to >> have autofs as an option. > > Is autofs purely userland? Could it be in ports? > Both the Linux and Solaris Autofs implementations are kernel based, probably to save context switches. The same is true for the FreeBSD GSoC 2006 "proof-of-concept" Autofs. Kind regards, Hans From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 18:12:02 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1B09D106566B for ; Thu, 30 Aug 2012 18:12:02 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id D28618FC0C for ; Thu, 30 Aug 2012 18:12:01 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so3647950pbb.13 for ; Thu, 30 Aug 2012 11:12:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=x1AWoMMkpEyMWge/t/FS1MHRuZjELC8cPCxiKoqwm2Y=; b=HV7+zjCg9soGxszFyWx23IhrbHlWMYFHweew95qwaH0/kzj/+zebAHDfrdpzx8TJk0 3awpySCqax9bpdjUJC6Jz24d4Hp5Ml5ABPSjqTypPosWgy5YA1jJTAiZUjhv4wNX91B1 BKLiKew5Yuu7zoDCnTBK2pg3OFFmW6DbQaj+s= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=x1AWoMMkpEyMWge/t/FS1MHRuZjELC8cPCxiKoqwm2Y=; b=jbMigyiOVTsvjysRCxtq5vW3/+9ToI1g615nHbJBBwY5x3dJIysOosFyOKz6zoF8YD 46x/kiT/DKt+/f7ytYE2xZ+URfIamly+0iqkV0Ja2Pyz5x47lBNjIu/fBlgOLOjrP7zO i0xs+TmL5QjDs8WtR6Lbws5OeiQNqq1SW35mLYJGWatMvuiFJbX3ZCkT026mnYKN0Ieo mfkv8kgyiCbYv8xI8xy677Oyu3RaCflrsabaXokM9omWYsDmmMHH9Zd3MX9imXWItLmx 4RTWdchthaVA/Hzv11GR2OyhG9WY36iKcGqcX7CEwAud2PUW4JBvEh6WummHi6BDozM3 IJVQ== MIME-Version: 1.0 Received: by 10.68.221.168 with SMTP id qf8mr12667985pbc.37.1346350321151; Thu, 30 Aug 2012 11:12:01 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Thu, 30 Aug 2012 11:12:01 -0700 (PDT) In-Reply-To: <503FAC40.4050505@beastielabs.net> References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> <201208301623.q7UGNiEr006228@higson.cam.lispworks.com> <20120830173636.GC2526@in-addr.com> <503FAC40.4050505@beastielabs.net> Date: Thu, 30 Aug 2012 11:12:01 -0700 Message-ID: From: Tim Gustafson To: Hans Ottevanger Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQl6lhSo3Gd+z8loQQ9yS++yntkFnlwfDuvVT406POijEbgutYE/CWMqWOrTSZUV7YZBojl+ Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 18:12:02 -0000 > Both the Linux and Solaris Autofs implementations are kernel based, probably > to save context switches. The same is true for the FreeBSD GSoC 2006 > "proof-of-concept" Autofs. Hrmm...does that necessarily exclude it from being a port? Can't it be a loadable kernel module? -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 18:30:47 2012 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 775C51065688; Thu, 30 Aug 2012 18:30:47 +0000 (UTC) (envelope-from hans@beastielabs.net) Received: from mail.beastielabs.net (beasties.demon.nl [82.161.3.114]) by mx1.freebsd.org (Postfix) with ESMTP id EF9678FC12; Thu, 30 Aug 2012 18:30:46 +0000 (UTC) Received: from merom.hotsoft.nl (merom.hotsoft.nl [192.168.0.12]) by mail.beastielabs.net (8.14.5/8.14.5) with ESMTP id q7UIUjwr020549; Thu, 30 Aug 2012 20:30:45 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <503FB155.1040201@beastielabs.net> Date: Thu, 30 Aug 2012 20:30:45 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: Tim Gustafson References: <201208281813.q7SIDEiJ000779@higson.cam.lispworks.com> <201208291053.q7TArlAs000409@higson.cam.lispworks.com> <201208301623.q7UGNiEr006228@higson.cam.lispworks.com> <20120830173636.GC2526@in-addr.com> <503FAC40.4050505@beastielabs.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 18:30:47 -0000 On 08/30/12 20:12, Tim Gustafson wrote: >> Both the Linux and Solaris Autofs implementations are kernel based, probably >> to save context switches. The same is true for the FreeBSD GSoC 2006 >> "proof-of-concept" Autofs. > > Hrmm...does that necessarily exclude it from being a port? Can't it > be a loadable kernel module? > There are more kernel modules in ports, e.g. sysutils/fusefs-kmod, so an autofs kernel module in ports should not be a problem. Kind regards, Hans From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 19:22:55 2012 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 828A81065673 for ; Thu, 30 Aug 2012 19:22:55 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3D20D8FC15 for ; Thu, 30 Aug 2012 19:22:54 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EAE28P1CDaFvO/2dsb2JhbABCAw6FdrYUgiABAQEEAQEBICsgCxsOCgICDRkCKQEJJgYIBwQBHASHbAupEJJ3gSGKAYMegg+BEgOTK4IsgRSPBYIpVoFF X-IronPort-AV: E=Sophos;i="4.80,342,1344225600"; d="scan'208";a="177199960" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 30 Aug 2012 15:22:48 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 5FA28B40EA; Thu, 30 Aug 2012 15:22:48 -0400 (EDT) Date: Thu, 30 Aug 2012 15:22:48 -0400 (EDT) From: Rick Macklem To: Tim Gustafson Message-ID: <951954369.1342002.1346354568372.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 19:22:55 -0000 Tim Gustafson wrote: > > I would miss AMD things like type:=link and normalize_hostnames for > > preventing duplicate mounts of the same resource. > > I don't think anyone is suggesting we deprecate AMD. I'd just like to > have autofs as an option. > Although I'd see it as an option initially, planning on supporting both "forever" would just result in bloat and yet more software to try and maintain, imho. (Theoretical comment, at least until a solid autofs port exists.) rick > -- > > Tim Gustafson > tjg@soe.ucsc.edu > 831-459-5354 > Baskin Engineering, Room 313A > _______________________________________________ > 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 Thu Aug 30 19:54:13 2012 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 8E22F106564A for ; Thu, 30 Aug 2012 19:54:13 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 58F2E8FC08 for ; Thu, 30 Aug 2012 19:54:13 +0000 (UTC) Received: by dadr6 with SMTP id r6so1426722dad.13 for ; Thu, 30 Aug 2012 12:54:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dwbojQ+cWBoNzqQdUMmqO5X9C4jIYGIxayNNzfa8ZLs=; b=jFSc5JLiAlc2XInRfWNi0XsNCg/ahunPZ4pYJ6BKXa8Lw36aGMduuNLuid7H5JYyTO crBLNrQA/fRVPaKmHLUqp4VHAtmABDE8d+gUrcSlhFc4LjWrPJBxLjYuT5Zs1gCBiiHe 2PZFLesbtCV1gE3zvZVHrJ/h/g1YMg4+whD+c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=dwbojQ+cWBoNzqQdUMmqO5X9C4jIYGIxayNNzfa8ZLs=; b=F9u5Ult/UsyeScwh8zq3cXiJl4gyUZYSb4ILS+bdg7UV6VnM28T2kWGnuuWgXkMPUs qCBlEB/6Vb0s1asrUe7Uv5msH/zpZDk2z/3svApBQgdjSm9Za51gXR4dxJ4NF+OKQi/9 qEsSd48TzXT7Vmlf2MIC69zfOxx0dEJJ2wHsYRf3dG1RYuO2+DwwJ2IKSqCJqCxdrrxg +xDShesh40V7bJzBs3ISICK9UZeyunDpUOxY90LQHMpnkcR41KfVvUyg3Z3e9HriplaN a/mtWVN+/yc5jwT4Z9BX8BR5ejdzaJjfgeqBRGv6H5hfMAx3IR+cKWmF6up6L4n39JWi fJVA== MIME-Version: 1.0 Received: by 10.66.83.8 with SMTP id m8mr11223746pay.48.1346356452604; Thu, 30 Aug 2012 12:54:12 -0700 (PDT) Received: by 10.66.233.133 with HTTP; Thu, 30 Aug 2012 12:54:12 -0700 (PDT) In-Reply-To: <951954369.1342002.1346354568372.JavaMail.root@erie.cs.uoguelph.ca> References: <951954369.1342002.1346354568372.JavaMail.root@erie.cs.uoguelph.ca> Date: Thu, 30 Aug 2012 12:54:12 -0700 Message-ID: From: Tim Gustafson To: Rick Macklem Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlZKicl4/AF1JP2IES20IEwGdD6RDAmZnzOH9EK+pgIIyipjTeb9+yKUUcCUKG3Def7SxbU Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 19:54:13 -0000 > Although I'd see it as an option initially, planning on supporting both > "forever" would just result in bloat and yet more software to try and > maintain, imho. (Theoretical comment, at least until a solid autofs port > exists.) I don't see that as a valid argument against adding an autofs port. Should we drop the port for Exim or Postgres, because ports for Sendmail and mySQL exist? -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 20:37:03 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4CA81065670 for ; Thu, 30 Aug 2012 20:37:03 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id A053B8FC12 for ; Thu, 30 Aug 2012 20:37:03 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAOHNP1CDaFvO/2dsb2JhbABCAw6FdrYTgiABAQUjVhsOCgICDRkCWQYTiA2pHZJ1gSGNH4IPgRIDlVeQGYIpVg X-IronPort-AV: E=Sophos;i="4.80,342,1344225600"; d="scan'208";a="179666609" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 30 Aug 2012 16:36:56 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id BB73BB402C; Thu, 30 Aug 2012 16:36:56 -0400 (EDT) Date: Thu, 30 Aug 2012 16:36:56 -0400 (EDT) From: Rick Macklem To: Tim Gustafson Message-ID: <380236740.1347711.1346359016755.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 20:37:04 -0000 Tim Gustafson wrote: > > Although I'd see it as an option initially, planning on supporting > > both > > "forever" would just result in bloat and yet more software to try > > and > > maintain, imho. (Theoretical comment, at least until a solid autofs > > port > > exists.) > > I don't see that as a valid argument against adding an autofs port. > Should we drop the port for Exim or Postgres, because ports for > Sendmail and mySQL exist? > The problem with something that goes in the kernel and uses the VFS/VOP interface is that it easily "bit rots" if it isn't in src/sys and being maintained by someone. (Note the file systems that aren't MP safe or don't work well that currently live within src/sys. Some will go away soon if the aren't made MP safe by someone.) I think you'd find that an autofs port (not necessarily in "ports") would suffer the same fate. (I'm honestly surprised that amd keeps working, since no one really maintains it. I mentioned that it is the last use of the old mount(2) syscall for NFS mounts. I know because I broke the backwards compatibility for mount(2) and amd got broken by that;-) However, I agree it isn't a reason for not having a port of it. I'd just rather see it replace amd, because it is old code I don't know how to maintain. This is similar to mountd.c. I am about to look at a couple of patches for mountd.c, but I hate doing this, because is it really old hard to read code. Lots of people complain about the lack of atomic export updates, but replacing mountd with nfse doesn't seem to be in the cards because it isn't absolutely 100% (including the bugs) compatible with mountd. (It seems mountd will exist "forever" unless someone implements a 100% compatible replacement and it will only get harder to maintain. If you don't believe me, take a look at mountd.c.:-) rick > -- > > Tim Gustafson > tjg@soe.ucsc.edu > 831-459-5354 > Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 21:24:19 2012 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 284791065674 for ; Thu, 30 Aug 2012 21:24:19 +0000 (UTC) (envelope-from portereyecare@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 E18068FC12 for ; Thu, 30 Aug 2012 21:24:18 +0000 (UTC) Received: by ialo14 with SMTP id o14so5016853ial.13 for ; Thu, 30 Aug 2012 14:24:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=NDM/6x4o4cpHTvL5kRFt0u3zW59IU+yoZWjiR6p4vis=; b=bi5i0p90fr6A8xGlqbXhzKyqR7DuaLgaHpyiYFApdMSsRu0vpVxIX6XzUX1T1ksXAr CfJO+JVKGiC3e3Om/M2EFfZnFzPmeSSXtV94vWVMuNSmBP3pgn5XLShxkSwLniLSro66 vzVdiULbddweBSwZwBJ/sNZlJ5VHgflV2TQSLDc6fCV2PrmLUD+8+Qg5UXcQZTfQr25v 1iH4SFxF8pLIYx0z4tPWtlQwhJAfnWMjnYXeQffAlXeuuwNYvey7opIWIT7wDSAr2BLm iOcaszAtY8W64S591PeL1T4Z98F09/HaNF89o2E3pCXN/hjfsvSi5XOxTkH+doQZupM1 IUZA== Received: by 10.42.61.16 with SMTP id s16mr6458669ich.7.1346361858393; Thu, 30 Aug 2012 14:24:18 -0700 (PDT) Received: from [192.168.0.107] (c122-108-168-198.rochd4.qld.optusnet.com.au. [122.108.168.198]) by mx.google.com with ESMTPS id wg9sm2105439igb.0.2012.08.30.14.24.09 (version=SSLv3 cipher=OTHER); Thu, 30 Aug 2012 14:24:15 -0700 (PDT) Message-ID: <503FD9F3.6040205@pobox.com> Date: Fri, 31 Aug 2012 07:24:03 +1000 From: Duncan Young User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: zfs woes 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, 30 Aug 2012 21:24:19 -0000 Hi All, I have a problem. My computer has been regularly locking up, I think it could be disk related. This has been causing the odd checksum error on the disks, which scrubbing seems to clean up. Now my problem is, after starting up after one of these lockups, the system mirror, reported an uncorrectable error. Both drives showed checksum errors (4 errors, I think). Using the -v flag a file was identified as corrupt. Upon trying to delete this file, the system panicked. O.K. it is on the system/ports filesystem, so I'll just copy all but the corrupt directory, to system/ports2 etc, etc. Upon zfs destroy -r system/ports, another panic. Now the entire system pool is corrupted, resulting in a panic upon boot. I presume the reslivering is causing this. I moved the two disks to my backup machine (purely used for sending backups onto). Its running 9.0-release #2. When I try to do an import, it panics. Now this I find surprising. Surely importing disks should either succeed or fail, not bring the whole machine down. Trying to import into openindiana also causes a panic and reboot (I didn't expect this). Any pointers as to where I go from now (other than reinstall). Duncan From owner-freebsd-fs@FreeBSD.ORG Thu Aug 30 23:52:50 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 46A511065677 for ; Thu, 30 Aug 2012 23:52:50 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id E99BE8FC0C for ; Thu, 30 Aug 2012 23:52:49 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so3450621vcb.13 for ; Thu, 30 Aug 2012 16:52:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; bh=UTN+ffPuSDcD/FpZCcjnsFlU0ckHVwyhzP388tirhq4=; b=TvPCVd/vhxa9LEGPHWpApOqmHXmvMK++Bn7bReMfYejOQw9ecN5smE6Pusy9ilC931 TBJOPBIAIcDxiv74uduF69gHWBgvTs1nmbWSgmRdonmuDJnurNQuQ/oGOXZjqfAZkQyN Uhm0xy8SHGiYypyAlAkIj6OMJSh1NP8IYCOlvMIvK1UafOvUvh8e6rCsisIJbOt+fYqF Z3gio9qEzrs+WMeR8/FtAz74+X0PBjF1IZqNaU7jzULCMclSdkN87G9+AcMhM5fjq7ah iOrLqA+sKpbLOxg8ddtMQVvfJswF8FOy9jwFWrfyoAXzUT5VW8O/R/E8dURlAEemOELI Gl/w== Received: by 10.52.20.138 with SMTP id n10mr3657291vde.129.1346370768213; Thu, 30 Aug 2012 16:52:48 -0700 (PDT) Received: from kan.dyndns.org (c-24-63-226-98.hsd1.ma.comcast.net. [24.63.226.98]) by mx.google.com with ESMTPS id b15sm1090674vdt.7.2012.08.30.16.52.46 (version=SSLv3 cipher=OTHER); Thu, 30 Aug 2012 16:52:47 -0700 (PDT) Date: Thu, 30 Aug 2012 19:52:41 -0400 From: Alexander Kabaev To: Tim Gustafson Message-ID: <20120830195241.5795a3bd@kan.dyndns.org> In-Reply-To: References: <951954369.1342002.1346354568372.JavaMail.root@erie.cs.uoguelph.ca> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/6bcU4Zw=GH6N+IYTdlQp4z/"; protocol="application/pgp-signature" Cc: freebsd-fs@freebsd.org Subject: Re: Using AMD with NFS Mounts 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, 30 Aug 2012 23:52:50 -0000 --Sig_/6bcU4Zw=GH6N+IYTdlQp4z/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 30 Aug 2012 12:54:12 -0700 Tim Gustafson wrote: > > Although I'd see it as an option initially, planning on supporting > > both "forever" would just result in bloat and yet more software to > > try and maintain, imho. (Theoretical comment, at least until a > > solid autofs port exists.) >=20 > I don't see that as a valid argument against adding an autofs port. > Should we drop the port for Exim or Postgres, because ports for > Sendmail and mySQL exist? >=20 No, we should not. But we should recognize that current VFS namecache architecture in FreeBSD makes autofs implementation very impractical without implementing full nullfs-like vnode stacking, and _that_ should be considered an argument against adding autofs port and for re-architecting namecache. We've been through this discussion many times before and all cards are marked in this game :) --=20 Alexander Kabaev --Sig_/6bcU4Zw=GH6N+IYTdlQp4z/ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iD8DBQFQP/zNQ6z1jMm+XZYRAjV1AJsHMXI56U+ymirZUcjc9Yw8dGizqACdG2bP SpV2NHG9gveJZoic/Vi8wJ4= =57cW -----END PGP SIGNATURE----- --Sig_/6bcU4Zw=GH6N+IYTdlQp4z/-- From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 07:13:11 2012 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 3FA0A106566C for ; Fri, 31 Aug 2012 07:13:11 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 9DADA8FC14 for ; Fri, 31 Aug 2012 07:13:07 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 242B02143B for ; Fri, 31 Aug 2012 03:13:07 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 31 Aug 2012 03:13:07 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type; s=smtpout; bh=G7+/ fjOIuwAtI18SubFbsKOGGds=; b=ozhUhyStSq81m5W/uLh1rRaHdlJewicZRz6R SGZbVBZ1TOUA0u6F5zAp8nKyiYAiiZx26VJLlCJt+kGaKIBvidY9230Y74q80GjD d1Xgx6Eijdw8LgXArBdARFY/V69yZ0/cH1TW+o2cLEHIAgTfT3p5n08zb4Y81EIR OY3rRt0= X-Sasl-enc: 9mXeIVJB/FtWr+hJge2VZBudhGvY4HvqnbA2EwLQLaDw 1346397180 Received: from [192.168.0.107] (unknown [122.108.168.198]) by mail.messagingengine.com (Postfix) with ESMTPA id C390A8E0205 for ; Fri, 31 Aug 2012 03:12:59 -0400 (EDT) Message-ID: <504063FC.1080408@pobox.com> Date: Fri, 31 Aug 2012 17:13:00 +1000 From: Duncan Young User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <503FD9F3.6040205@pobox.com> In-Reply-To: <503FD9F3.6040205@pobox.com> Content-Type: multipart/mixed; boundary="------------080201090901040701010407" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: zfs woes 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, 31 Aug 2012 07:13:11 -0000 This is a multi-part message in MIME format. --------------080201090901040701010407 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit My apologies, I forgot to attach an image of the output from the panic. Duncan On 31/08/2012 7:24 AM, Duncan Young wrote: > Hi All, > > I have a problem. > > My computer has been regularly locking up, I think it could be disk > related. This has been causing the odd > checksum error on the disks, which scrubbing seems to clean up. > > Now my problem is, after starting up after one of these lockups, the > system mirror, reported an uncorrectable error. > Both drives showed checksum errors (4 errors, I think). Using the -v > flag a file was identified as corrupt. Upon trying > to delete this file, the system panicked. O.K. it is on the > system/ports filesystem, so I'll just copy all but the corrupt > directory, to system/ports2 etc, etc. Upon zfs destroy -r > system/ports, another panic. Now the entire system pool is corrupted, > resulting in a panic upon boot. I presume the reslivering is causing > this. > > I moved the two disks to my backup machine (purely used for sending > backups onto). Its running 9.0-release #2. When I try to do > an import, it panics. Now this I find surprising. Surely importing > disks should either succeed or fail, not bring the whole machine down. > > Trying to import into openindiana also causes a panic and reboot (I > didn't expect this). > > Any pointers as to where I go from now (other than reinstall). > > Duncan > > _______________________________________________ > 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" --------------080201090901040701010407-- From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 08:25:57 2012 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 1FBD4106566B for ; Fri, 31 Aug 2012 08:25:57 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mx1.freebsd.org (Postfix) with ESMTP id B63598FC12 for ; Fri, 31 Aug 2012 08:25:54 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0LwVKN-1TgJDY33nj-018NHP; Fri, 31 Aug 2012 10:25:47 +0200 Message-ID: <5040750D.5070109@brockmann-consult.de> Date: Fri, 31 Aug 2012 10:25:49 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <503FD9F3.6040205@pobox.com> <504063FC.1080408@pobox.com> In-Reply-To: <504063FC.1080408@pobox.com> X-Enigmail-Version: 1.4.4 X-Provags-ID: V02:K0:4KVrgDgL/Oyg57KDlLVk3qq15CvBveLgD6GbRNXssW8 HE4tVdBgOVdlrQxXEdY+0j8PJ+p8VqyOTDnVhvhLAwWoaSJlkP 4RVmvwAoNC9V60shj3pSiTlNVhRBKo5CHbDOvHNgK7Qsin0Dy5 mOPZ98D8ZKwhsolpTsPX4uJ5FrDF5vG+G28uHiQxZQXAzBenEK VQx0MKSh1Hc2ybyVteO4rD0owJ0MNazJsvhBa0//4Gk2M6Tc81 B2S2WZvYPCJNOwC7UiA5/wYPTh8KvOvhhlnBQ2PqOJ5j/cc4P6 fW2qlwNXKwl8DJntvTqrg933brXMjw0cPFN+5skkDVP+NryPrw 82UsVAqzTmhFANhe5l29nXrfZMydkJvxeG4KK098U Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: zfs woes 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, 31 Aug 2012 08:25:57 -0000 The mailing list strips attachments. We still don't have your image. And as prevention, I would say test your disks and upgrade the firmware. I had a similar problem (panics when both root disks were gone, checksum errors on boot) with Crucial SSDs, but new firmware fixed it. Sebulon on the forum had an issue with some Samsung disks or some SSDs and I believe fixed it the same way. I test my disks by putting them in a redundant test zpool, writing to them, then pulling one, putting back in, pulling again, and putting back in, and then testing to see if the disk can be seen. It seems to work in detecting the problem on those SSDs, but I don't have any other disks that I've tested with time in the OS. (btw warning #1 if you do this non-redundant, your writing process will lock up, and the zpool command might too, so you can't as easily test multiple disks, and warning #2 gpart show on the disk you pulled and broke will segfault, and gpart recover will panic the system) As for a fix after your system is already damaged... sorry, don't know. On 08/31/2012 09:13 AM, Duncan Young wrote: > My apologies, I forgot to attach an image of the output from the panic. > > Duncan > > On 31/08/2012 7:24 AM, Duncan Young wrote: >> Hi All, >> >> I have a problem. >> >> My computer has been regularly locking up, I think it could be disk >> related. This has been causing the odd >> checksum error on the disks, which scrubbing seems to clean up. >> >> Now my problem is, after starting up after one of these lockups, the >> system mirror, reported an uncorrectable error. >> Both drives showed checksum errors (4 errors, I think). Using the -v >> flag a file was identified as corrupt. Upon trying >> to delete this file, the system panicked. O.K. it is on the >> system/ports filesystem, so I'll just copy all but the corrupt >> directory, to system/ports2 etc, etc. Upon zfs destroy -r >> system/ports, another panic. Now the entire system pool is corrupted, >> resulting in a panic upon boot. I presume the reslivering is causing >> this. >> >> I moved the two disks to my backup machine (purely used for sending >> backups onto). Its running 9.0-release #2. When I try to do >> an import, it panics. Now this I find surprising. Surely importing >> disks should either succeed or fail, not bring the whole machine down. >> >> Trying to import into openindiana also causes a panic and reboot (I >> didn't expect this). >> >> Any pointers as to where I go from now (other than reinstall). >> >> Duncan >> >> _______________________________________________ >> 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" -- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de -------------------------------------------- From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 11:01:55 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B434E106566B; Fri, 31 Aug 2012 11:01:55 +0000 (UTC) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.kpi.ua (comsys.kpi.ua [77.47.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6213C8FC08; Fri, 31 Aug 2012 11:01:55 +0000 (UTC) Received: from pm513-1.comsys.kpi.ua ([10.18.52.101] helo=pm513-1.comsys.ntu-kpi.kiev.ua) by comsys.kpi.ua with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1T7Oz3-0005k3-1J; Fri, 31 Aug 2012 14:01:53 +0300 Received: by pm513-1.comsys.ntu-kpi.kiev.ua (Postfix, from userid 1001) id 3F1FB1CC23; Fri, 31 Aug 2012 14:01:52 +0300 (EEST) Date: Fri, 31 Aug 2012 14:01:51 +0300 From: Andrey Simonenko To: Rick Macklem Message-ID: <20120831110151.GA21041@pm513-1.comsys.ntu-kpi.kiev.ua> References: <503D301F.5080607@delphij.net> <140200696.1251333.1346245151029.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <140200696.1251333.1346245151029.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: Mutt/1.5.21 (2010-09-15) X-Authenticated-User: simon@comsys.ntu-kpi.kiev.ua X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.63 (build at 28-Apr-2011 07:11:12) X-Date: 2012-08-31 14:01:53 X-Connected-IP: 10.18.52.101:63539 X-Message-Linecount: 28 X-Body-Linecount: 12 X-Message-Size: 1325 X-Body-Size: 576 Cc: freebsd-fs@FreeBSD.ORG, rmacklem@FreeBSD.org Subject: Re: Why vfs_stdcheckexp is a VFS operation? 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, 31 Aug 2012 11:01:55 -0000 On Wed, Aug 29, 2012 at 08:59:11AM -0400, Rick Macklem wrote: > > It seems that changing the semantics of /etc/exports is very difficult > (it's a stumbling block w.r.t. adoption of nfse, as an example) at this > time so, although confusing, exporting a directory that is not a mount > point results in the entire mount point exported for NFS RPCs, but a > restriction of only mounting that directory is enforced for the Mount > protocol (only done at mount time and only for NFSv3). > Which information is the statement about semantics of exports(5) and nfse is based on? From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 11:59:25 2012 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 2D7DE1065670; Fri, 31 Aug 2012 11:59:25 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id CA2038FC16; Fri, 31 Aug 2012 11:59:24 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAMumQFCDaFvO/2dsb2JhbABFhgS2GYIgAQEFI1YbDgoCAg0ZAlkGiCCpa5MNgSGJaIVvgRIDlViJM4Zngn8 X-IronPort-AV: E=Sophos;i="4.80,347,1344225600"; d="scan'208";a="179728549" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 31 Aug 2012 07:59:23 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id A2773B402C; Fri, 31 Aug 2012 07:59:23 -0400 (EDT) Date: Fri, 31 Aug 2012 07:59:23 -0400 (EDT) From: Rick Macklem To: Andrey Simonenko Message-ID: <42823120.1362161.1346414363645.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20120831110151.GA21041@pm513-1.comsys.ntu-kpi.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@FreeBSD.ORG, rmacklem@FreeBSD.org Subject: Re: Why vfs_stdcheckexp is a VFS operation? 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, 31 Aug 2012 11:59:25 -0000 Andrey Simonenko wrote: > On Wed, Aug 29, 2012 at 08:59:11AM -0400, Rick Macklem wrote: > > > > It seems that changing the semantics of /etc/exports is very > > difficult > > (it's a stumbling block w.r.t. adoption of nfse, as an example) at > > this > > time so, although confusing, exporting a directory that is not a > > mount > > point results in the entire mount point exported for NFS RPCs, but a > > restriction of only mounting that directory is enforced for the > > Mount > > protocol (only done at mount time and only for NFSv3). > > > > Which information is the statement about semantics of exports(5) and > nfse is based on? I was just going on what you have posted. You always seem to say that certain buggy cases for how mountd interprets /etc/exports is handled differently for nfse, but I may have misunderstood. rick From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 12:09:40 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD1F51065676; Fri, 31 Aug 2012 12:09:40 +0000 (UTC) (envelope-from marcel@xcllnt.net) Received: from mail.xcllnt.net (mail.xcllnt.net [70.36.220.4]) by mx1.freebsd.org (Postfix) with ESMTP id 7CA9F8FC1C; Fri, 31 Aug 2012 12:09:40 +0000 (UTC) Received: from [10.4.0.166] ([149.6.120.133]) (authenticated bits=0) by mail.xcllnt.net (8.14.5/8.14.5) with ESMTP id q7VC9V3b042859 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 Aug 2012 05:09:33 -0700 (PDT) (envelope-from marcel@xcllnt.net) Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\)) From: Marcel Moolenaar In-Reply-To: Date: Fri, 31 Aug 2012 13:09:40 +0100 Message-Id: <96DC4416-6CA5-45B4-B790-068797FAA2C6@xcllnt.net> References: To: Boris Astardzhiev X-Mailer: Apple Mail (2.1486) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Grzegorz Bernacki Subject: Re: NANDFS: out of space 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: Fri, 31 Aug 2012 12:09:40 -0000 On Aug 22, 2012, at 4:34 PM, Boris Astardzhiev = wrote: > Now when I attempt to delete /mnt/file1234 I get a panic: > root@smartcpe:/mnt # rm file1234 > panic: bmap_truncate_mapping: error 28 when truncate at level 1 >=20 > KDB: enter: panic > [ thread pid 606 tid 100047 ] > Stopped at kdb_enter+0x48: ldrb r15, [r15, r15, ror r15]! > db> >=20 > So how do I solve this? It is easily reproduced following this = scenario > every time. > Up to this commit I've made the following minor changes so that I ran into this as well. There are 2 aspects here: 1. Currently errors pretty much result in panics by virtue of a compile-time option. This means that reasonable errors (i.e. errors that simply trigger recovery code or are being propagated upstream) also cause panics. 2. There's a real bug. For me it gives the following panic (by virtue of me changing the behaviour of point 1): nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment nandfs_add_blocks: error:1 when creating segment nandfs_new_segment: cannot create segment error 1 create_segment: cannot create next segment lock order reversal: 1st 0xd944e60c bufwait (bufwait) @ kern/vfs_bio.c:1905 2nd 0xc501cd18 devfs (devfs) @ fs/nandfs/nandfs_segment.c:769 KDB: stack backtrace: db_trace_self_wrapper(c08fea97,746e656d,373a632e,a3936,0,...) at = db_trace_self_wrapper+0x26 kdb_backtrace(c06cadeb,c09024bc,c0b03d88,301,c46c5a88,...) at = kdb_backtrace+0x2a _witness_debugger(c09024bc,c501cd18,c08f5fd8,c4921b80,c08e785b,...) at = _witness_debugger+0x25 witness_checkorder(c501cd18,9,c08e7852,301,c501cd38,...) at = witness_checkorder+0x86f __lockmgr_args(c501cd18,80000,c501cd38,0,0,...) at __lockmgr_args+0x824 vop_stdlock(c46c5bbc,c08e76ed,c46c5b9c,c46c5b9c,c46c5bf8,...) at = vop_stdlock+0x62 VOP_LOCK1_APV(c0961780,c46c5bbc,100000,c4ffc480,c4b15000,...) at = VOP_LOCK1_APV+0xf3 nandfs_clean_segblocks(fee0,0,c46c5c6c,c46c5c6c,1,...) at = nandfs_clean_segblocks+0x48 clean_seginfo(c0962360,c46c5c6c,317a,0,0,...) at clean_seginfo+0x49 nandfs_segment_constructor(c4b1ec00,0,5c,c08ed1d5,1f4,...) at = nandfs_segment_constructor+0x5e5 nandfs_syncer(c4b1ec00,c46c5d08,c08f5110,3d8,c09b7520,...) at = nandfs_syncer+0x8f fork_exit(c05a63a0,c4b1ec00,c46c5d08) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xc46c5d40, ebp =3D 0 --- panic: brelse: not dirty cpuid =3D 0 KDB: enter: panic I haven't had the time to look into it in detail. Also: design documentation is missing right now, which does mean that there's a pretty steep curve for anyone who didn't write the file system to go in and fix any bugs. FYI, --=20 Marcel Moolenaar marcel@xcllnt.net From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 12:40:31 2012 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 35ABF106567A; Fri, 31 Aug 2012 12:40:31 +0000 (UTC) (envelope-from boris.astardzhiev@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 76B298FC1C; Fri, 31 Aug 2012 12:40:29 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so1418083lbb.13 for ; Fri, 31 Aug 2012 05:40:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4fqau8eCpcJLmOZaokY6g7IkgLAlDfd7iCd8/4mpijg=; b=hL4FEqparSgm6j0tdUANZplHYTW9ViwcG238QnwnV/8vHaecD2JemzH/XUJ8lMOJw7 xoD1HbT379nTYWJsy3Gbzx05yjzX1bFt6O34ocLt9bpTGzAWjdRHH+4+ZA7so89tGnBL /M7vYlIcGvBbyREAl9dsyfmi1GeFDLHne0sjSsr2HtZLsnlMTeJXkO2DZUcf2cqmcli+ geGUQIFc/pZFU7Z3wGa88Rryn2QJIj5F/FODCcQa2m1xoWmNHAHgizz80wBuAJgEaStg vutYlJ4SNflyRlLSi2IxVRok286mXQx0tr6cKURVRw74mbIKUOxO/zdQTRVJNtyU+tX8 dvQw== MIME-Version: 1.0 Received: by 10.112.26.10 with SMTP id h10mr2547120lbg.4.1346416828984; Fri, 31 Aug 2012 05:40:28 -0700 (PDT) Received: by 10.112.58.2 with HTTP; Fri, 31 Aug 2012 05:40:28 -0700 (PDT) In-Reply-To: <96DC4416-6CA5-45B4-B790-068797FAA2C6@xcllnt.net> References: <96DC4416-6CA5-45B4-B790-068797FAA2C6@xcllnt.net> Date: Fri, 31 Aug 2012 15:40:28 +0300 Message-ID: From: Boris Astardzhiev To: Marcel Moolenaar Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Grzegorz Bernacki Subject: Re: NANDFS: out of space 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: Fri, 31 Aug 2012 12:40:31 -0000 Hi, I'm aware of the compile-time panics regarding nandfs_error(). The output you've posted is exactly the same as mine here w/ TEST_MODE defined in sys/fs/nandfs/nandfs_subr.h . Secondly, I'm open to trying to make this filesystem robust due to the fact that it's high time that FreeBSD had a reliable NAND flash filesystem support. I am willing to spend the time and do the work (as useful as it may be), I just need someone to point me in the right direction. :-) Thank you for the reply. From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 15:39:48 2012 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 51BE01065675 for ; Fri, 31 Aug 2012 15:39:48 +0000 (UTC) (envelope-from attila.bogar@linguamatics.com) Received: from mail.linguamatics.com (mail.linguamatics.com [188.39.80.203]) by mx1.freebsd.org (Postfix) with ESMTP id CBEAE8FC1E for ; Fri, 31 Aug 2012 15:39:47 +0000 (UTC) Received: from [10.252.10.232] (random.linguamatics.com [10.252.10.232]) by mail.linguamatics.com (Postfix) with ESMTPSA id 8E8DCEFB451 for ; Fri, 31 Aug 2012 16:39:41 +0100 (BST) Message-ID: <5040DABD.20001@linguamatics.com> Date: Fri, 31 Aug 2012 16:39:41 +0100 From: =?ISO-8859-1?Q?Attila_Bog=E1r?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: NFS: rpcsec_gss with Linux clients 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, 31 Aug 2012 15:39:48 -0000 Hi, In the wireshark trace I see, that during an NFS mount, Linux opens two TCP connections. Linux creates the GSS conect on one tcp connection, sends a DESTROY destroys rpcsec, but immediately (without waiting for the DESTROY reply) - reusing the context on the other TCP connection. I don't know who is guilty the BSD or the Linux (or both) as I haven't spent time reading the RFCs. This is very difficult to reproduce if the server is very fast. You have to use an extremely fast client. With a Linux virtual machine I couldn't reproduce. Even printf's in the bsd kernel destroy the balance and everything starts to suddenly work because of the timing. This is a quantum bug. Look at /usr/src/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c In svc_rpc_gss() case RPCSEC_GSS_DESTROY: svc_rpc_gss_validate returns FALSE during the DESTROY. I don't quite know why, but during the destroy within the the svc_rpc_gss_validate() gss_verify_mic() returns maj_stat = GSS_S_DEFECTIVE_TOKEN, no matter what heimdal version I use. As a consequence, client->cl_state is marked CLIENT_STALE; I think client locking should have been used at this point. In the meantime the next TCP connection's nfs PUTROOTFH request is being processed in the kernel. And this is the point where the problem may or may not happen. In svc_rpc_gss() at the beginning svc_rpc_gss_timeout_clients() is called. If it's called before svc_rpc_gss_validate() marked the cl_state CLIENT_STALE and the Linux client survived. Here is my patch for review. This is my first ever kernel patch. I'm going to open a PR... Constructive comments are welcome. Thanks, Attila --- /usr/src/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c.orig 2012-08-30 23:34:00.000000000 +0100 +++ /usr/src/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c 2012-08-31 15:59:40.000000000 +0100 @@ -565,7 +565,8 @@ */ client->cl_state = CLIENT_NEW; client->cl_locked = FALSE; - client->cl_expiration = time_uptime + 5*60; + /* we are now more cautious */ + client->cl_expiration = time_uptime + 4*60; return (client); } @@ -930,7 +931,11 @@ if (cred_lifetime == GSS_C_INDEFINITE) cred_lifetime = time_uptime + 24*60*60; - client->cl_expiration = time_uptime + cred_lifetime; + /* + * we are now more cautious + * 12 sec is just an adhoc hack value + */ + client->cl_expiration = time_uptime + cred_lifetime - 12; /* * Fill in cred details in the rawcred structure. @@ -990,7 +995,7 @@ gss_buffer_desc rpcbuf, checksum; OM_uint32 maj_stat, min_stat; gss_qop_t qop_state; - int32_t rpchdr[128 / sizeof(int32_t)]; + int32_t rpchdr[2048 / sizeof(int32_t)]; int32_t *buf; rpc_gss_log_debug("in svc_rpc_gss_validate()"); @@ -1024,7 +1029,12 @@ if (maj_stat != GSS_S_COMPLETE) { rpc_gss_log_status("gss_verify_mic", client->cl_mech, maj_stat, min_stat); - client->cl_state = CLIENT_STALE; + /* + * Linux nfs-utils>=1.2.3 is re-using GSS context + * on other TCP NFS connection after it DESTROYED it + * The garbage collector will remove client at cl_expiration + */ + /* client->cl_state = CLIENT_STALE; */ return (FALSE); } From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 23:06:03 2012 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 12B351065673; Fri, 31 Aug 2012 23:06:03 +0000 (UTC) (envelope-from trent@snakebite.org) Received: from exchange.liveoffice.com (exchla3.liveoffice.com [64.70.67.188]) by mx1.freebsd.org (Postfix) with ESMTP id E8A0B8FC0C; Fri, 31 Aug 2012 23:06:02 +0000 (UTC) Received: from EXHUB03.exchhosting.com (192.168.11.104) by exhub08.exchhosting.com (192.168.11.106) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 31 Aug 2012 16:05:56 -0700 Received: from localhost (35.8.247.10) by exchange.liveoffice.com (192.168.11.104) with Microsoft SMTP Server id 8.3.213.0; Fri, 31 Aug 2012 16:05:55 -0700 Date: Fri, 31 Aug 2012 19:05:53 -0400 From: Trent Nelson To: Andriy Gapon Message-ID: <20120831230553.GC59852@snakebite.org> References: <20120824011517.GJ42732@snakebite.org> <503CD4F1.6060001@FreeBSD.org> <503CDD4E.6050902@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <503CDD4E.6050902@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-fs@FreeBSD.org" Subject: Re: chmod -h 000x against symlink has bizarre results on 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: Fri, 31 Aug 2012 23:06:03 -0000 On Tue, Aug 28, 2012 at 08:01:34AM -0700, Andriy Gapon wrote: > on 28/08/2012 17:25 Andriy Gapon said the following: > Will you be able to test the following patch? > Preferably on a temporary test pool - I don't want to risk your data. > > diff --git a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c > b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c > index 69374fb..7f61517 100644 > --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c > +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c > @@ -1695,6 +1695,7 @@ sa_modify_attrs(sa_handle_t *hdl, sa_attr_type_t newattr, > ASSERT(action == SA_REPLACE); > SA_ADD_BULK_ATTR(attr_desc, j, attr, > locator, datastart, buflen); > + length_idx++; > } else { > length = SA_REGISTERED_LEN(sa, attr); > if (length == 0) { > That looks like it did the trick. Nice one :-) What's the protocol for ZFS bugfixes? I'm happy to do the leg work (submitting PRs to other teams etc). > Andriy Gapon Trent. From owner-freebsd-fs@FreeBSD.ORG Fri Aug 31 23:12:25 2012 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 C1F3F1065673 for ; Fri, 31 Aug 2012 23:12:25 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 52F938FC08 for ; Fri, 31 Aug 2012 23:12:24 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so2545622wgb.31 for ; Fri, 31 Aug 2012 16:12:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=3897AyrmUs2nO0AmkSxn2y6lAlxTzrDRKXRTfNapQtY=; b=JkSpMUEawhTV8hxVYv31musWzbUX8fRzU56ay/d05JRLv7aVHvL6BcyTOjN32gYIcY +qt147bmmaLJVsCKHP8d4C0WQE9DKt2sr1G++4KYOGx6Nv3auXV3biEaEF0HG3BgwEci O0eWGoxn5iupBPqbPnDKm2BWaCCaepcilqcfyO8S50yMMz/HStZn9Li3TB910UuwjUFZ 3VmtobOPAPhnh+eVZ/YSFckGkfG4x98gsjcaUPP17TXIK9CTgF8lY21fGZiRYcnX8Arz lUXO+esNnyHoVH3xidsueL991ygBK/iORXrFoEvrGGjZb8Uwe1IBry1bOvzl0zfa2Xqm mXPA== Received: by 10.180.107.163 with SMTP id hd3mr7451093wib.19.1346454744152; Fri, 31 Aug 2012 16:12:24 -0700 (PDT) Received: from X220.optiplex-networks.com (81-178-2-118.dsl.pipex.com. [81.178.2.118]) by mx.google.com with ESMTPS id b7sm5077262wiz.9.2012.08.31.16.12.21 (version=SSLv3 cipher=OTHER); Fri, 31 Aug 2012 16:12:22 -0700 (PDT) Message-ID: <504144D6.5030800@gmail.com> Date: Sat, 01 Sep 2012 00:12:22 +0100 From: Kaya Saman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: DMA Error on disk FreeBSD won't boot 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, 31 Aug 2012 23:12:25 -0000 Hi, I'm pretty sure this means "bad" disk which is surprising considering how new the disk is. I run FreeBSD 8.2 x64 on a little Mini-ITX based server which has 1 SSD for root / and 2x 2TB disks used as a ZFS pool called ZFS_POOL_1 and 2x 4TB disks used as a second ZFS pool called ZFS_POOL_2. I don't have a ZFS file system on the disks as they were built using the 'zpool' command so data is basically being stored on raw (pseudo) RAID 0. Just now one of the disks started reporting DMA timeouts... now I've noticed this before with JMicron based controller from STARTECH however the disk in question was connected directly to the mother board. These are the errors I was getting: WARNING: Kernel Errors Present ad13: FAILURE - READ_DMA48 status=51 error=10 at ata6-master UDMA100 SATA 3Gb/s 1 Time(s): ad13: 3815447MB at ata6-slave UDMA100 SATA 3Gb/s 1 Time(s): ad13: FAILURE - READ_DMA48 timed out LBA=1330838659 1 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (0 retries left) LBA=1086500736 1 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (0 retries left) LBA=1330838659 1 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1086500736 1 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1330838659 1 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1409316096 1 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1409317248 10 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1681236467 4 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1681236723 8 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1681236979 1 Time(s): ad13: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1747452672 1 Time(s): ad14: 1907729MB at ata7-master UDMA100 SATA 3Gb/s am not sure where to go from here? My usual response would be to dock via USB and see if the drives mounted, since this is a ZPOOL the only thing I could think of was to run 'zpool import ZFS_POOL_2' on my laptop running FreeBSD 9 x64 and see if that worked. Unfortunately the disks registered in the system but due to some SCSI errors didn't actually show under /dev. I can't be more specific unfortunately to the type of error due to the fact that my laptop: Lenovo X220 doesn't have GUI on FreeBSD partition.. for whatever reason even with Kernel patch X won't start. I guess I could have sent it to myself using mail command as ext4 file system won't mount on FreeBSD either... for my Linux partition. Anyhow, the disks were not using AHCI as the server system board wouldn't detect them so was using ATA mode. It worked fine up till now. Of course all my data is backed up bar a few gigs if not 10s of gigs however, I would really like to recover the issue if even possible. In Linux I always used to be able to run dd on a failing disk then mount it using 'Loop', my aim now as the drive is so large is to do a direct dd copy from the failing drive to a new drive but if FreeBSD won't start with the drive in place, or add the drive when booted (using hotswap - mainly as not sure how to do, have read a little but as not using AHCI didn't really find anything substantial), or dock via USB then dd from any *NIX based OS. Could anyone suggest anything? I guess I could run a Linux recovery CD with the drive inserted and see if I could 'dd' from there, though I have an uncanny feeling that it won't recognize upon boot?? Regards, Kaya From owner-freebsd-fs@FreeBSD.ORG Sat Sep 1 23:57:58 2012 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 D68E1106564A for ; Sat, 1 Sep 2012 23:57:58 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 78D0C8FC17 for ; Sat, 1 Sep 2012 23:57:57 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8EAMyfQlCDaFvO/2dsb2JhbABEhgW2I4IgAQEBAwEBAQELFQQnFwkLBRYYERkCBCUBCSYGCAcEARwEh2YGC6hFkXqLJ4V3gRIDjmKES4IsgRSIH4Zngn+BRQ X-IronPort-AV: E=Sophos;i="4.80,354,1344225600"; d="scan'208";a="177419131" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 01 Sep 2012 19:57:50 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 64982B4022; Sat, 1 Sep 2012 19:57:50 -0400 (EDT) Date: Sat, 1 Sep 2012 19:57:50 -0400 (EDT) From: Rick Macklem To: =?utf-8?Q?Attila_Bog=C3=A1r?= Message-ID: <817398955.1415204.1346543870350.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <5040DABD.20001@linguamatics.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1415203_641086622.1346543870347" X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@FreeBSD.org Subject: Re: NFS: rpcsec_gss with Linux clients 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, 01 Sep 2012 23:57:58 -0000 ------=_Part_1415203_641086622.1346543870347 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Attila Bogar wrote: > Hi, > > In the wireshark trace I see, that during an NFS mount, Linux opens > two > TCP connections. > Linux creates the GSS conect on one tcp connection, sends a DESTROY > destroys rpcsec, > but immediately (without waiting for the DESTROY reply) - reusing the > context on the other TCP connection. > > I don't know who is guilty the BSD or the Linux (or both) as I haven't > spent time reading the RFCs. > This certainly sounds bogus. I can see an argument for 2 TCP connections for trunking, but since a security context should only be destroyed when the client is done with it, doing a DESTROY doesn't make sense? (There is something in the RPC header called a "handle". It identifies the security context, and it would be nice to check the wireshark trace to see if it the same as the one being used on the other connection?) > This is very difficult to reproduce if the server is very fast. You > have to use an extremely fast client. > With a Linux virtual machine I couldn't reproduce. Even printf's in > the > bsd kernel destroy the balance and everything starts to suddenly work > because of the timing. This is a quantum bug. > > Look at /usr/src/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c > > In svc_rpc_gss() > case RPCSEC_GSS_DESTROY: > > svc_rpc_gss_validate returns FALSE during the DESTROY. > > I don't quite know why, but during the destroy within the the > svc_rpc_gss_validate() gss_verify_mic() returns maj_stat = > GSS_S_DEFECTIVE_TOKEN, no matter what heimdal version I use. > That would indicate the encrypted checksum isn't correct. It might be using an algorithm only supported by the newer RPCSEC_GSS_V3? > As a consequence, client->cl_state is marked CLIENT_STALE; > For DESTROY when it will fail, I'm not sure if marking the context stale makes sense. (I can see an argument for and against doing this.) I've attached a small patch with disables setting client->cl_state to CLIENT_STALE for this case, which you could try, to see if it helps? > I think client locking should have been used at this point. > > In the meantime the next TCP connection's nfs PUTROOTFH request is > being > processed in the kernel. > > And this is the point where the problem may or may not happen. > In svc_rpc_gss() at the beginning svc_rpc_gss_timeout_clients() is > called. > If it's called before svc_rpc_gss_validate() marked the cl_state > CLIENT_STALE and the Linux client survived. > > Here is my patch for review. This is my first ever kernel patch. > > I'm going to open a PR... > I'd suggest contacting the Linux folks first and see if they are willing to look at the wireshark trace or know of an issue/fix, because it really sounds like a Linux client issue. > Constructive comments are welcome. > > Thanks, > Attila > > --- /usr/src/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c.orig 2012-08-30 > 23:34:00.000000000 +0100 > +++ /usr/src/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c 2012-08-31 > 15:59:40.000000000 +0100 > @@ -565,7 +565,8 @@ > */ > client->cl_state = CLIENT_NEW; > client->cl_locked = FALSE; > - client->cl_expiration = time_uptime + 5*60; > + /* we are now more cautious */ > + client->cl_expiration = time_uptime + 4*60; > Waiting 4 minutes instead of 5 shouldn't have any real effect, although it might avoid the problem for your case w.r.t. timing. > return (client); > } > @@ -930,7 +931,11 @@ > if (cred_lifetime == GSS_C_INDEFINITE) > cred_lifetime = time_uptime + 24*60*60; > > - client->cl_expiration = time_uptime + cred_lifetime; > + /* > + * we are now more cautious > + * 12 sec is just an adhoc hack value > + */ > + client->cl_expiration = time_uptime + cred_lifetime - 12; > This time is usually the TGT lifetime (12->24hrs), so subtracting 12 sec from it doesn't really make any sense. (I will note that the calculation of cred_lifetime for the GSS_C_INDEFINITE case looks incorrect, since time_uptime gets added twice, but I doubt that's relevant to your problem, since it is set to more than 24hrs.) > /* > * Fill in cred details in the rawcred structure. > @@ -990,7 +995,7 @@ > gss_buffer_desc rpcbuf, checksum; > OM_uint32 maj_stat, min_stat; > gss_qop_t qop_state; > - int32_t rpchdr[128 / sizeof(int32_t)]; > + int32_t rpchdr[2048 / sizeof(int32_t)]; > int32_t *buf; > > rpc_gss_log_debug("in svc_rpc_gss_validate()"); > @@ -1024,7 +1029,12 @@ > if (maj_stat != GSS_S_COMPLETE) { > rpc_gss_log_status("gss_verify_mic", client->cl_mech, > maj_stat, min_stat); > - client->cl_state = CLIENT_STALE; > + /* > + * Linux nfs-utils>=1.2.3 is re-using GSS context > + * on other TCP NFS connection after it DESTROYED it > + * The garbage collector will remove client at cl_expiration > + */ > + /* client->cl_state = CLIENT_STALE; */ > return (FALSE); > } > If this helps, please try the attached patch which does the same thing, but only for the DESTROY case. rick > _______________________________________________ > 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" ------=_Part_1415203_641086622.1346543870347 Content-Type: text/x-patch; name=rpcsec-destroy.patch Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=rpcsec-destroy.patch LS0tIHJwYy9ycGNzZWNfZ3NzL3N2Y19ycGNzZWNfZ3NzLmMuc2F2CTIwMTItMDktMDEgMTk6MjA6 MzUuMDAwMDAwMDAwIC0wNDAwCisrKyBycGMvcnBjc2VjX2dzcy9zdmNfcnBjc2VjX2dzcy5jCTIw MTItMDktMDEgMTk6MjQ6MTUuMDAwMDAwMDAwIC0wNDAwCkBAIC05ODQsNyArOTg0LDcgQEAgc3Zj X3JwY19nc3NfYWNjZXB0X3NlY19jb250ZXh0KHN0cnVjdCBzdgogCiBzdGF0aWMgYm9vbF90CiBz dmNfcnBjX2dzc192YWxpZGF0ZShzdHJ1Y3Qgc3ZjX3JwY19nc3NfY2xpZW50ICpjbGllbnQsIHN0 cnVjdCBycGNfbXNnICptc2csCi0gICAgZ3NzX3FvcF90ICpxb3ApCisgICAgZ3NzX3FvcF90ICpx b3AsIHJwY19nc3NfcHJvY190IGdjcHJvYykKIHsKIAlzdHJ1Y3Qgb3BhcXVlX2F1dGgJKm9hOwog CWdzc19idWZmZXJfZGVzYwkJIHJwY2J1ZiwgY2hlY2tzdW07CkBAIC0xMDI0LDcgKzEwMjQsOCBA QCBzdmNfcnBjX2dzc192YWxpZGF0ZShzdHJ1Y3Qgc3ZjX3JwY19nc3NfCiAJaWYgKG1hal9zdGF0 ICE9IEdTU19TX0NPTVBMRVRFKSB7CiAJCXJwY19nc3NfbG9nX3N0YXR1cygiZ3NzX3ZlcmlmeV9t aWMiLCBjbGllbnQtPmNsX21lY2gsCiAJCSAgICBtYWpfc3RhdCwgbWluX3N0YXQpOwotCQljbGll bnQtPmNsX3N0YXRlID0gQ0xJRU5UX1NUQUxFOworCQlpZiAoZ2Nwcm9jICE9IFJQQ1NFQ19HU1Nf REVTVFJPWSkKKwkJCWNsaWVudC0+Y2xfc3RhdGUgPSBDTElFTlRfU1RBTEU7CiAJCXJldHVybiAo RkFMU0UpOwogCX0KIApAQCAtMTM1OCw3ICsxMzU5LDcgQEAgc3ZjX3JwY19nc3Moc3RydWN0IHN2 Y19yZXEgKnJxc3QsIHN0cnVjdAogCQkJYnJlYWs7CiAJCX0KIAotCQlpZiAoIXN2Y19ycGNfZ3Nz X3ZhbGlkYXRlKGNsaWVudCwgbXNnLCAmcW9wKSkgeworCQlpZiAoIXN2Y19ycGNfZ3NzX3ZhbGlk YXRlKGNsaWVudCwgbXNnLCAmcW9wLCBnYy5nY19wcm9jKSkgewogCQkJcmVzdWx0ID0gUlBDU0VD X0dTU19DUkVEUFJPQkxFTTsKIAkJCWJyZWFrOwogCQl9Cg== ------=_Part_1415203_641086622.1346543870347--