From owner-freebsd-fs@FreeBSD.ORG Sun Jan 1 00:35: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 F175A106566C for ; Sun, 1 Jan 2012 00:35:21 +0000 (UTC) (envelope-from boydjd@jbip.net) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 861708FC08 for ; Sun, 1 Jan 2012 00:35:21 +0000 (UTC) Received: by eaaf13 with SMTP id f13so19116177eaa.13 for ; Sat, 31 Dec 2011 16:35:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jbip.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=hTpvDZjAfjS3GWwc/8T1ZDeaydU+R3LPEjgwfjenJPA=; b=KWXzwF1DWHO0EcHcaFaJjO4pVkeg03DPnvCip8Fvt9BCsnR0Ud+SqG0z3RSBH/5EPI uRFULTg0eXDnr2nx+3B2NSvSGf/G7kNoAE9mmcATzHCDdg9GWYlsxcoLL0gR3Mpe6ytG 49PinwWTL6pFi9Vyh/3rS6JYtKXe3IwfrTyFk= Received: by 10.204.149.212 with SMTP id u20mr10741053bkv.120.1325376521021; Sat, 31 Dec 2011 16:08:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.98.202 with HTTP; Sat, 31 Dec 2011 16:08:18 -0800 (PST) In-Reply-To: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> References: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> From: Joshua Boyd Date: Sat, 31 Dec 2011 19:08:18 -0500 Message-ID: To: Michael DeMan 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 detach/replace 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, 01 Jan 2012 00:35:22 -0000 On Sat, Dec 31, 2011 at 1:58 AM, Michael DeMan wrote: > Hi All, > > The origination of the problem is entirely my fault on FreeBSD 8.1 > RELEASE #0. We had old notes that attempting a 'replace' (which is > appropriate for a mirror) leaves ZFS in a funky state on BSD. I > inadvertently did just that on a drive swap on a raidz2 pool. My old notes > show the only recovery that we knew of at the time was to rsync or zfs-send > the pool elsewhere, destroy the local and rebuild from scratch. > I've never had a problem before, and have replaced about 5 drives in my striped raidz ... Usually I'll execute a zpool offline, camcontrol stop, remove the drive, then zpool replace. I am running 8-STABLE though, and not -RELEASE. -- Joshua Boyd E-mail: boydjd@jbip.net http://www.jbip.net From owner-freebsd-fs@FreeBSD.ORG Sun Jan 1 11:27:30 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 8ECC2106566B for ; Sun, 1 Jan 2012 11:27:30 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mailgw.dannysplace.net (mailgw.dannysplace.net [204.109.56.184]) by mx1.freebsd.org (Postfix) with ESMTP id 2DCE48FC08 for ; Sun, 1 Jan 2012 11:27:29 +0000 (UTC) Received: from [203.206.171.212] (helo=[192.168.10.12]) by mailgw.dannysplace.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RhJIO-0007Pj-2C for freebsd-fs@freebsd.org; Sun, 01 Jan 2012 21:10:16 +1000 Message-ID: <4F003EB8.6080006@dannysplace.net> Date: Sun, 01 Jan 2012 21:08:40 +1000 From: Dan Carroll User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.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-Authenticated-User: danny X-Authenticator: plain X-Exim-Version: 4.76 (build at 08-Jun-2011 18:40:49) X-Date: 2012-01-01 21:09:44 X-Connected-IP: 203.206.171.212:56059 X-Message-Linecount: 132 X-Body-Linecount: 122 X-Message-Size: 4939 X-Body-Size: 4553 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on damka.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailgw.dannysplace.net) Subject: ZFS With Gpart partitions 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, 01 Jan 2012 11:27:30 -0000 Hello all, I'm currently trying to fix a suspect drive and I've run into a small problem. I was wondering if someone can shed some light into how GPart works (when using labels for partitions). My drives are 2Tb WD RE4's, originally the array was using 1Tb Seagate drives, and I was replacing about 3 of those a year, but since I migrated to the RE4's this is my first problem. Here is my setup. NAME STATE READ WRITE CKSUM areca ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/data0 ONLINE 0 0 0 gpt/data1 ONLINE 0 0 0 gpt/data2 ONLINE 0 0 0 gpt/data3 ONLINE 103 0 0 gpt/data4 ONLINE 0 0 0 gpt/data5 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/data6 ONLINE 0 0 0 gpt/data7 ONLINE 0 0 0 gpt/data8 ONLINE 0 0 0 gpt/data9 ONLINE 0 0 0 gpt/data10 ONLINE 0 0 0 gpt/data11 ONLINE 0 0 0 errors: No known data errors The drives are connected via an Areca controller, each drive is created as a Pass-Thru (just like JBod but also using the cache and BBU). So, my problem began when I tried to replace gpt/data3. Here is what I did. # zpool offline areca gpt/data3 # shutdown -p now (I could not remember the camcontrol commands to detach a device and shutting down was not an issue, so that's the way I did it.) Replace the failing drive and re-create the passthru device in the areca console. power on. All good so far, except the drive I used as a replacement came from a decomissioned server. It already had a gpart label on it. As it happens it was labelled data2. I quickly shut down the system, took the new drive out, put it into another machine and wiped the first few megabytes of the disk with dd. I re-inserted the drive, recreated the passthrough, powered up and replaced the offlined drive. Now it's resilvering. Currently, my system looks like this: NAME STATE READ WRITE CKSUM areca DEGRADED 0 0 0 raidz1 DEGRADED 0 0 0 gpt/data0 ONLINE 0 0 0 gpt/data1 ONLINE 0 0 0 da8p1 ONLINE 0 0 0 replacing DEGRADED 0 0 0 gpt/data3/old OFFLINE 0 0 0 gpt/data3 ONLINE 0 0 0 931G resilvered gpt/data4 ONLINE 0 0 0 gpt/data5 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/data6 ONLINE 0 0 0 gpt/data7 ONLINE 0 0 0 gpt/data8 ONLINE 0 0 0 gpt/data9 ONLINE 0 0 0 gpt/data10 ONLINE 0 0 0 gpt/data11 ONLINE 0 0 0 The resilvering looks like it's working fine, but I am curious about the gpart label. When I query da8p1 I cannot find it. # gpart show da8 => 34 3907029101 da8 GPT (1.8T) 34 3907029101 1 freebsd-zfs (1.8T) # glabel list da8p1 glabel: No such geom: da8p1. It should look like this: # gpart show da0 => 34 3907029101 da0 GPT (1.8T) 34 3907029101 1 freebsd-zfs (1.8T) # glabel list da0p1 Geom name: da0p1 Providers: 1. Name: gpt/data0 Mediasize: 2000398899712 (1.8T) Sectorsize: 512 Mode: r1w1e1 secoffset: 0 offset: 0 seclength: 3907029101 length: 2000398899712 index: 0 Consumers: 1. Name: da0p1 Mediasize: 2000398899712 (1.8T) Sectorsize: 512 Mode: r1w1e2 So it seems to me that when I inserted the second drive with a label called data2, it wiped the label from the *original* drive. ZFS does not seem to care about this. If the label is simply a label and losing it does not alter the user data on the drive, then this makes sense. I am wondering if I can simply re-label the partition without fear of breaking something? Reading the glabel man page I suspect that it may be ok. -D From owner-freebsd-fs@FreeBSD.ORG Sun Jan 1 12:09:00 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 4F817106566C for ; Sun, 1 Jan 2012 12:09:00 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0E3578FC18 for ; Sun, 1 Jan 2012 12:08:59 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so20315049vcb.13 for ; Sun, 01 Jan 2012 04:08:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5QydiMZ6dbqYMWcT29kHgdcHgXyqhLss/H8359QEg1w=; b=FOv3YtfI9aCYhQRjpPab04JyJdtCz46lrJ1rcmW9/88aBwgmxnuznYtEB1mmN74bAG BBoNMZx/ioaRTnLLFcKINEaS6/a3pDLaEjPFqt9rFMM5pyEJ8nldFc//mPr7OfsfuyZs Gio6DLD0UzpAp6Ju0ZRh4yIVYwNjn+8cdFGpM= MIME-Version: 1.0 Received: by 10.220.147.197 with SMTP id m5mr27991291vcv.48.1325419739260; Sun, 01 Jan 2012 04:08:59 -0800 (PST) Received: by 10.220.194.131 with HTTP; Sun, 1 Jan 2012 04:08:59 -0800 (PST) In-Reply-To: <4F003EB8.6080006@dannysplace.net> References: <4F003EB8.6080006@dannysplace.net> Date: Sun, 1 Jan 2012 04:08:59 -0800 Message-ID: From: Freddie Cash To: Dan Carroll Content-Type: text/plain; charset=UTF-8 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 01 Jan 2012 12:09:00 -0000 When in doubt, read the man page: man gpart The option you are looking for is "-l": # gpart show -l da8 That will show the labels set in the GPT for each partition. And labels are created using "-l" in the "gpart add" command, as well. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Sun Jan 1 12:31: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 B112E1065672 for ; Sun, 1 Jan 2012 12:31:55 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mailgw.dannysplace.net (mailgw.dannysplace.net [204.109.56.184]) by mx1.freebsd.org (Postfix) with ESMTP id 7D1AA8FC16 for ; Sun, 1 Jan 2012 12:31:55 +0000 (UTC) Received: from [203.206.171.212] (helo=[192.168.10.12]) by mailgw.dannysplace.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RhKam-0009n2-K0; Sun, 01 Jan 2012 22:32:49 +1000 Message-ID: <4F00522F.6020700@dannysplace.net> Date: Sun, 01 Jan 2012 22:31:43 +1000 From: Dan Carroll User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Freddie Cash References: <4F003EB8.6080006@dannysplace.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Exim-Version: 4.76 (build at 08-Jun-2011 18:40:49) X-Date: 2012-01-01 22:32:49 X-Connected-IP: 203.206.171.212:64572 X-Message-Linecount: 34 X-Body-Linecount: 21 X-Message-Size: 1192 X-Body-Size: 572 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on damka.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailgw.dannysplace.net) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 01 Jan 2012 12:31:55 -0000 On 1/01/2012 10:08 PM, Freddie Cash wrote: > When in doubt, read the man page: man gpart > > The option you are looking for is "-l": > > # gpart show -l da8 > > That will show the labels set in the GPT for each partition. > > And labels are created using "-l" in the "gpart add" command, as well. Ok, so the label is still there. Two things are still strange. 1) data2 is not in /dev/gpt/ 2) "glabel list da8p1" does not find anything. But it does for other drives. Also, is there a difference (for ZFS) acessing the drive via /dev/da8p1 or /dev/gpt/data2 -D From owner-freebsd-fs@FreeBSD.ORG Sun Jan 1 12:45:26 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 5691E106564A for ; Sun, 1 Jan 2012 12:45:26 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id C73498FC0C for ; Sun, 1 Jan 2012 12:45:24 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so20417767vbb.13 for ; Sun, 01 Jan 2012 04:45:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=SxerGOkfGaol6HQeZRf0Cqrr/T76rLbsOQInA26Z7ho=; b=CTQWezeeSqD0cZovEortUZ71wlqpTGLmT5lA37Aki8aPn/GVC8dfw7m734oWpRP6Dg HtdhE0tA3vJ4xHC8imi3RWYNmcLPv5oRjUVnqIoGGKMv8xfkaOAVJU7QJLtjhKD/D45A 7T60bpP/5CuTU6v3o6+yLzEIjN0AqDIE8bGvE= MIME-Version: 1.0 Received: by 10.52.17.139 with SMTP id o11mr23563795vdd.62.1325421923988; Sun, 01 Jan 2012 04:45:23 -0800 (PST) Received: by 10.220.194.131 with HTTP; Sun, 1 Jan 2012 04:45:23 -0800 (PST) In-Reply-To: <4F00522F.6020700@dannysplace.net> References: <4F003EB8.6080006@dannysplace.net> <4F00522F.6020700@dannysplace.net> Date: Sun, 1 Jan 2012 04:45:23 -0800 Message-ID: From: Freddie Cash To: Dan Carroll Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 01 Jan 2012 12:45:26 -0000 On Sun, Jan 1, 2012 at 4:31 AM, Dan Carroll wrote: > On 1/01/2012 10:08 PM, Freddie Cash wrote: >> >> When in doubt, read the man page: =C2=A0man gpart >> >> The option you are looking for is "-l": >> >> # gpart show -l da8 >> >> That will show the labels set in the GPT for each partition. >> >> And labels are created using "-l" in the "gpart add" command, as well. > > Ok, so the label is still there. =C2=A0 Two things are still strange. > 1) =C2=A0data2 is not in /dev/gpt/ > 2) =C2=A0"glabel list da8p1" does not find anything. =C2=A0 But it does f= or other > drives. You may need to offline the disk in the zfs pool, then "gpart destroy da8" to clear out the primary GPT table at the start of the disk, and the secondary GPT table at the end of the disk. That will also clear out the /dev/da8p* entries, and related /dev/gpt/ entry. Then create the GPT from scratch, including the label. Then, finally, add/replace the disk to the ZFS pool. The [kernel|GEOM|whatever] doesn't do a very good job of re-checking the disks for changed GPT tables, instead using the ones in memory. Or something along those lines. You have to destroy the existing table, then create it, which causes the [kernel|GEOM|whatever] to re-taste the disk and load the GPT off the disk, thus creating the /dev/gpt/ entry. > Also, is there a difference (for ZFS) acessing the drive via /dev/da8p1 o= r > /dev/gpt/data2 As far as ZFS is concerned, no. When importing the pool, ZFS checks for ZFS metadata to determine which disk belongs to which vdev in which pool, and gets all the pathing sorted out automatically. However, since disk device nodes can change at boot (add a new controller, boot with a dead drive, do a BIOS update that reverses the PCI scan order, etc), it makes it easier on the admin to have labels. For example, in our 16-bay storage servers, I've set up a coordinate system where columns are letters A-D, and rows are numbers 1-4. Then I've labelled each disk according to where it is in the chassis: /dev/gpt/disk-a1 /dev/gpt/disk-a2 /dev/gpt/disk-a3 /dev/gpt/disk-a4 etc That way, no matter how the drives are actually enumerated by the BIOS, loader, kernel, drivers, etc, I always know which disk is having issues. :) --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Sun Jan 1 19:03:24 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 B83D2106564A for ; Sun, 1 Jan 2012 19:03:24 +0000 (UTC) (envelope-from freebsd@deman.com) Received: from plato.corp.nas.com (plato.corp.nas.com [66.114.32.138]) by mx1.freebsd.org (Postfix) with ESMTP id 71DBF8FC12 for ; Sun, 1 Jan 2012 19:03:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by plato.corp.nas.com (Postfix) with ESMTP id D633910488269 for ; Sun, 1 Jan 2012 11:03:23 -0800 (PST) X-Virus-Scanned: amavisd-new at corp.nas.com Received: from plato.corp.nas.com ([127.0.0.1]) by localhost (plato.corp.nas.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCO8eKZvWD5L for ; Sun, 1 Jan 2012 11:03:22 -0800 (PST) Received: from [192.168.2.247] (mono-sis1.s.bli.openaccess.org [66.114.32.149]) by plato.corp.nas.com (Postfix) with ESMTPSA id 8904610488257 for ; Sun, 1 Jan 2012 11:03:22 -0800 (PST) From: Michael DeMan Mime-Version: 1.0 (Apple Message framework v1084) Date: Sun, 1 Jan 2012 11:03:21 -0800 In-Reply-To: To: freebsd-fs@freebsd.org References: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> Message-Id: X-Mailer: Apple Mail (2.1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: zfs detach/replace 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, 01 Jan 2012 19:03:24 -0000 Right, I botched it and did a 'replace' on a drive that is in an raidz2 = pool. replace is for replacing a mirrored drive. This happened to us a couple years ago during early testing, we noticed = it, and at that time were unable to get the machine out of its funky = state without destroying and rebuilding the pool. Basically drive #5 in = the raidz2 pool thinks that it is supposed to be working on a = replacement for a pair of mirrored physical drives. We have shutdown and started the machine without the drive installed, = done all sorts of things, etc. We can not even offline it because: # zpool offline zp1rz2 label/ada5LABEL cannot offline label/ada5LABEL: no valid replicas On Dec 31, 2011, at 4:08 PM, Joshua Boyd wrote: > On Sat, Dec 31, 2011 at 1:58 AM, Michael DeMan = wrote: > Hi All, >=20 > The origination of the problem is entirely my fault on FreeBSD 8.1 = RELEASE #0. We had old notes that attempting a 'replace' (which is = appropriate for a mirror) leaves ZFS in a funky state on BSD. I = inadvertently did just that on a drive swap on a raidz2 pool. My old = notes show the only recovery that we knew of at the time was to rsync or = zfs-send the pool elsewhere, destroy the local and rebuild from scratch. >=20 > I've never had a problem before, and have replaced about 5 drives in = my striped raidz ... >=20 > Usually I'll execute a zpool offline, camcontrol stop, remove the = drive, then zpool replace. >=20 > I am running 8-STABLE though, and not -RELEASE. >=20 > --=20 > Joshua Boyd >=20 > E-mail: boydjd@jbip.net > http://www.jbip.net From owner-freebsd-fs@FreeBSD.ORG Sun Jan 1 19:54:12 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 CB80E106566C for ; Sun, 1 Jan 2012 19:54:12 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id ACD298FC0C for ; Sun, 1 Jan 2012 19:54:12 +0000 (UTC) Received: from omta09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by qmta14.emeryville.ca.mail.comcast.net with comcast id GKn01i0010S2fkCAEKu6LC; Sun, 01 Jan 2012 19:54:06 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta09.emeryville.ca.mail.comcast.net with comcast id GKur1i01D1t3BNj8VKusH6; Sun, 01 Jan 2012 19:54:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 45AFF102C1E; Sun, 1 Jan 2012 11:54:11 -0800 (PST) Date: Sun, 1 Jan 2012 11:54:11 -0800 From: Jeremy Chadwick To: Michael DeMan Message-ID: <20120101195411.GA73487@icarus.home.lan> References: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: zfs detach/replace 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, 01 Jan 2012 19:54:12 -0000 On Sun, Jan 01, 2012 at 11:03:21AM -0800, Michael DeMan wrote: > Right, I botched it and did a 'replace' on a drive that is in an > raidz2 pool. replace is for replacing a mirrored drive. I just want to clarify for readers: this statement is inaccurate. "zpool replace" can (should) be used on anything (mirrors, raidzX, etc.). I have used "zpool replace" myself on FreeBSD on raidz1 without problems for years. Here's valid proof, and this is not "simulated" or done on a VM or anything like that -- this is bare metal. http://koitsu.wordpress.com/2010/07/22/freebsd-and-zfs-hot-swapping-sata-disks-with-ahci/ Full commands/output are provided there as well (there's a link within my blog post providing full output). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Sun Jan 1 22:04:17 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 8BE9B106564A for ; Sun, 1 Jan 2012 22:04:17 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mailgw.dannysplace.net (mailgw.dannysplace.net [204.109.56.184]) by mx1.freebsd.org (Postfix) with ESMTP id 4F5E68FC13 for ; Sun, 1 Jan 2012 22:04:16 +0000 (UTC) Received: from [203.206.171.212] (helo=[192.168.10.12]) by mailgw.dannysplace.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RhTWe-0004bk-QB; Mon, 02 Jan 2012 08:05:11 +1000 Message-ID: <4F00D853.5010607@dannysplace.net> Date: Mon, 02 Jan 2012 08:04:03 +1000 From: Dan Carroll User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Freddie Cash References: <4F003EB8.6080006@dannysplace.net> <4F00522F.6020700@dannysplace.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Exim-Version: 4.76 (build at 08-Jun-2011 18:40:49) X-Date: 2012-01-02 08:05:09 X-Connected-IP: 203.206.171.212:63328 X-Message-Linecount: 110 X-Body-Linecount: 97 X-Message-Size: 4916 X-Body-Size: 4192 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on damka.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailgw.dannysplace.net) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 01 Jan 2012 22:04:17 -0000 On 1/01/2012 10:45 PM, Freddie Cash wrote: > On Sun, Jan 1, 2012 at 4:31 AM, Dan Carroll wrote: >> >> Ok, so the label is still there. Two things are still strange. >> 1) data2 is not in /dev/gpt/ >> 2) "glabel list da8p1" does not find anything. But it does for other >> drives. > > You may need to offline the disk in the zfs pool, then "gpart destroy > da8" to clear out the primary GPT table at the start of the disk, and > the secondary GPT table at the end of the disk. That will also clear > out the /dev/da8p* entries, and related /dev/gpt/ entry. > > Then create the GPT from scratch, including the label. > > Then, finally, add/replace the disk to the ZFS pool. > > The [kernel|GEOM|whatever] doesn't do a very good job of re-checking > the disks for changed GPT tables, instead using the ones in memory. > Or something along those lines. You have to destroy the existing > table, then create it, which causes the [kernel|GEOM|whatever] to > re-taste the disk and load the GPT off the disk, thus creating the > /dev/gpt/ entry. Thanks for your reply. It's quite informative. Reading a little more I see that the label stuff is written to the end of the disk. Here is what I think happened. 1) I inserted a disk with a label that already existed. The kernel decided to simply remove the device entry from /dev/gpt (data2) and so ZFS found it's data on the GPT partition (rather than the label that points to the partition). 2) I wiped the new disk on a second system, but actually I didn't wipe the GPT label at the end until I re-did the GPT partition. 3) Re-inserted new disk and resilvered. All good but ZFS now knows the old disk via the GPT partition. I'm still confused as to why "glabel list da8p1" does not work. Perhaps all that command does is: scan the device for a label (it would find data2) and then check what data2 is in /dev/gpt? I guess another way might be to bring down the server, take the disk out, re-do the GPT stuff on another machine, and then put it back. That way ZFS may well simpy see it's data on the labeled device. Oh wait, that wont create the /dev/gpt entries... :-( I'd really like to fix this but avoid doing *another* resilver. The first one is finished now and a scrub operation will be done in an hour or so. I guess I should have the faith to do go ahead and do it again, but there is an element of risk, and it's to fix something cosmetic. That feels wrong... >> Also, is there a difference (for ZFS) acessing the drive via /dev/da8p1 or >> /dev/gpt/data2 > > As far as ZFS is concerned, no. When importing the pool, ZFS checks > for ZFS metadata to determine which disk belongs to which vdev in > which pool, and gets all the pathing sorted out automatically. > > However, since disk device nodes can change at boot (add a new > controller, boot with a dead drive, do a BIOS update that reverses the > PCI scan order, etc), it makes it easier on the admin to have labels. Yeah I am aware of ZFS doing that. It's a nice feature. It's also the reason why in my system data2 is NOT da2p1. What I was trying to dertermine is if there is any danger to ZFS accessing the disk in this manner. Is da8p1 an identical device to data3? From what you describe, from ZFS' point of view, for each device in the pool, there are actually 2 versions of it. The dataX version, and the daXp1 version.. I am guessing that ZFS keeps track of the disk names in it's pools. Otherwise, what would stop this (the label being replaced with a device name in ZFS) happening between reboots? > > > For example, in our 16-bay storage servers, I've set up a coordinate > system where columns are letters A-D, and rows are numbers 1-4. Then > I've labelled each disk according to where it is in the chassis: > /dev/gpt/disk-a1 > /dev/gpt/disk-a2 > /dev/gpt/disk-a3 > /dev/gpt/disk-a4 > etc > > That way, no matter how the drives are actually enumerated by the > BIOS, loader, kernel, drivers, etc, I always know which disk is having > issues. :) > That was also my reasoning. My numbering starts disk0 being in the top left slot, and continues row by row. -D From owner-freebsd-fs@FreeBSD.ORG Mon Jan 2 01:04:26 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 E27E1106566C for ; Mon, 2 Jan 2012 01:04:26 +0000 (UTC) (envelope-from dpd@bitgravity.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 AB6838FC12 for ; Mon, 2 Jan 2012 01:04:26 +0000 (UTC) Received: by iadj38 with SMTP id j38so35914734iad.13 for ; Sun, 01 Jan 2012 17:04:26 -0800 (PST) Received: by 10.50.160.199 with SMTP id xm7mr56201265igb.24.1325466266166; Sun, 01 Jan 2012 17:04:26 -0800 (PST) Received: from 173-13-188-41-sfba.hfc.comcastbusiness.net (173-13-188-41-sfba.hfc.comcastbusiness.net. [173.13.188.41]) by mx.google.com with ESMTPS id pb6sm70607628igc.5.2012.01.01.17.04.24 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 01 Jan 2012 17:04:25 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "David P. Discher" In-Reply-To: <20111230090256.GA6796@reks> Date: Sun, 1 Jan 2012 17:04:23 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <87E5C7D5-2D73-4A42-B871-8B27448B0DD9@bitgravity.com> <20111229215125.GA8539@reks> <20111230090256.GA6796@reks> To: Gleb Kurtsou X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@freebsd.org, Johannes Totz Subject: Re: fusefs broken on 8-stable? 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, 02 Jan 2012 01:04:27 -0000 On Dec 30, 2011, at 1:02 AM, Gleb Kurtsou wrote: > On (29/12/2011 14:06), David P Discher wrote: >> Is this a straight dump for p4 ? =20 >>=20 >> Earlier this week, I checked out = //depot/projects/soc2011/ilya_fuse/... out of p4. But only used the = kmod, not the libs. Unfortunately, it was 10x slower than the 0.3.9 = version currently in the ports tree. I never got it to the same point = ... after a few days, had only written about 6-10GB of data. >=20 > It's the same as p4 (+ few minor tweaks). fuse-0.4 is more strict on > resizing files which is very likely to be slow for encrypted file > system (encfs). Try setting sysctl vfs.fuse.sync_resize=3D0. Got this port started, however its still around 10-60x slower than the = 0.3.9 version in the ports tree. vfs.fuse.sync_resize seemed to make no = difference. Granted this is a custom fusefs that I'm comparing, based = off of bbfs (http://www.cs.nmsu.edu/~pfeiffer/fuse-tutorial/). >=20 > I don't know all the details but there was memory leak and arbitrary > memory corruption in old fuse. It's believed to be fixed in fuse-0.4. = My > guess you are hitting the same bug. I've compared the functions in the stack the trace, and have found no = change between 0.4.4 and 0.3.9. If you (or anyone else on the list) = knows what patches are the memory leak and corruption fixes are - I'd = like to attempt to back port them into 0.3.9. I'd like the stability = and speed.=20 --- David P. Discher dpd@bitgravity.com * AIM: bgDavidDPD BITGRAVITY * http://www.bitgravity.com From owner-freebsd-fs@FreeBSD.ORG Mon Jan 2 05:09:40 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 E84F8106566B for ; Mon, 2 Jan 2012 05:09:39 +0000 (UTC) (envelope-from freebsd@deman.com) Received: from plato.corp.nas.com (plato.corp.nas.com [66.114.32.138]) by mx1.freebsd.org (Postfix) with ESMTP id A78F28FC0A for ; Mon, 2 Jan 2012 05:09:39 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by plato.corp.nas.com (Postfix) with ESMTP id 1C8161049404B for ; Sun, 1 Jan 2012 21:09:39 -0800 (PST) X-Virus-Scanned: amavisd-new at corp.nas.com Received: from plato.corp.nas.com ([127.0.0.1]) by localhost (plato.corp.nas.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6mTNdApm46d0 for ; Sun, 1 Jan 2012 21:09:38 -0800 (PST) Received: from [192.168.2.247] (mono-sis1.s.bli.openaccess.org [66.114.32.149]) by plato.corp.nas.com (Postfix) with ESMTPSA id 5D0591049403F for ; Sun, 1 Jan 2012 21:09:38 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: Michael DeMan In-Reply-To: <20120101195411.GA73487@icarus.home.lan> Date: Sun, 1 Jan 2012 21:09:37 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> <20120101195411.GA73487@icarus.home.lan> To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.1084) Subject: Re: zfs detach/replace 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, 02 Jan 2012 05:09:40 -0000 Hi, Sounds realistic to me that the 'replace' command works after a 'detach' = is properly done. In my case, I forgot to do the 'detach' - just did the 'replace' after = changing the drive (and after a reboot). =46rom there, ZFS gets in the = state below - where it automagically created label/ada5LABEL/old and = appears to be wanting to do the rebuild onto label/ada5LABEL as if it is = part of a mirrored pair? This pool was built on FreeBSD 8.0, with an operating system update to = 8.1 after that. Possibly I could try and update the ZFS pool version or = something if this is fixed now? =20 I know for a fact, back with FreeBSD 7.x, that this same scenario could = occur. Basically on below - my old notes show there is no way to fix = the situation with ada5LABEL and ada5LABEL/old without destroying and = rebuilding the pool. Any attempts to 'detach', 'offline' or anything = else on either of those two logical entries fails with a 'no valid = replicas'. $ zpool status pool: zp1rz2 state: DEGRADED status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are = unaffected. action: Determine if the device needs to be replaced, and clear the = errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: scrub in progress for 53h42m, 80.53% done, 12h59m to go config: NAME STATE READ WRITE CKSUM zp1rz2 DEGRADED 0 0 0 raidz2 DEGRADED 0 0 0 label/ada0LABEL ONLINE 0 0 0 label/ada1LABEL ONLINE 0 0 0 label/ada2LABEL ONLINE 35 0 0 19.5K = repaired label/ada3LABEL ONLINE 0 0 0 label/ada4LABEL ONLINE 0 0 0 replacing UNAVAIL 0 3.24M 0 = insufficient replicas label/ada5LABEL/old UNAVAIL 0 3.74M 0 cannot = open label/ada5LABEL UNAVAIL 0 3.74M 0 cannot = open label/ada6LABEL ONLINE 0 0 0 label/ada7LABEL ONLINE 0 0 0 errors: No known data errors - Mike On Jan 1, 2012, at 11:54 AM, Jeremy Chadwick wrote: > On Sun, Jan 01, 2012 at 11:03:21AM -0800, Michael DeMan wrote: >> Right, I botched it and did a 'replace' on a drive that is in an >> raidz2 pool. replace is for replacing a mirrored drive. >=20 > I just want to clarify for readers: this statement is inaccurate. >=20 > "zpool replace" can (should) be used on anything (mirrors, raidzX, > etc.). >=20 > I have used "zpool replace" myself on FreeBSD on raidz1 without = problems > for years. Here's valid proof, and this is not "simulated" or done on = a > VM or anything like that -- this is bare metal. >=20 > = http://koitsu.wordpress.com/2010/07/22/freebsd-and-zfs-hot-swapping-sata-d= isks-with-ahci/ >=20 > Full commands/output are provided there as well (there's a link within > my blog post providing full output). >=20 > --=20 > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | >=20 From owner-freebsd-fs@FreeBSD.ORG Mon Jan 2 05:18: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 62C631065673 for ; Mon, 2 Jan 2012 05:18:07 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 19DF88FC0A for ; Mon, 2 Jan 2012 05:18:06 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so20614494vcb.13 for ; Sun, 01 Jan 2012 21:18:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Rp0WFlFc6Bzgk1RqCol6B9lynbLmlLlDjGFuexOYxEc=; b=pUc0rfRaGLREMrwe/kbOOTtyl1dqD1VmlYDyrj1D9bgl3aYmVtbE4y5lc6yy3IU1HP R+zXbC1V3CNegX6Dmfa+PjF8lmb90s1D0WlVhBrkCZc9qoBdzx+7qWPMfqwZD185WYnH zrPPp90CVUdxd6gipLJ++qoVVSbNnFBP4pdK8= MIME-Version: 1.0 Received: by 10.220.147.197 with SMTP id m5mr29184111vcv.48.1325481486124; Sun, 01 Jan 2012 21:18:06 -0800 (PST) Received: by 10.220.194.131 with HTTP; Sun, 1 Jan 2012 21:18:06 -0800 (PST) In-Reply-To: References: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> <20120101195411.GA73487@icarus.home.lan> Date: Sun, 1 Jan 2012 21:18:06 -0800 Message-ID: From: Freddie Cash To: Michael DeMan Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: zfs detach/replace 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, 02 Jan 2012 05:18:07 -0000 On Sun, Jan 1, 2012 at 9:09 PM, Michael DeMan wrote: > Sounds realistic to me that the 'replace' command works after a 'detach' = is properly done. > > In my case, I forgot to do the 'detach' - just did the 'replace' after ch= anging the drive (and after a reboot). =C2=A0From there, ZFS gets in the st= ate below - where it automagically created label/ada5LABEL/old and appears = to be wanting to do the rebuild onto label/ada5LABEL as if it is part of a = mirrored pair? "zpool detach" and "zpool replace" are two very different, and totally unconnected, things. "zpool detach" is used to remove drives from mirror vdevs. The vdev then has one less drive in it. The beauty of the way mirror vdevs work in ZFS is that you can "zpool attach" a drive to an existing 2-way mirror vdev, thus turning it into a 3-way mirror. Then "zpool detach" the extra drive. Makes upgrading drive capacity a cinch, as you never lose any redundancy in the vdev. "zpool replace" is used to do an in-place replacement of a drive in a vdev, and can be used with mirror, raidz1, raidz2, and raidz3 vdevs. I think the part you may be getting confused with is the "zpool offline" step that should be done before doing a "zpool replace". That way, if anything goes wrong, you can always put back the old drive, do a "zpool online" to it, and then do a "zpool remove" or "zpool detach" to the "new" drive. That's saved my bacon a couple of times. :) Learnt the hard way about that, losing a 20 TB pool (only a couple TB of data in it) due to "insufficient replicas" and "missing drives" and whatnot. > I know for a fact, back with FreeBSD 7.x, that this same scenario could o= ccur. =C2=A0Basically on below - my old notes show there is no way to fix t= he situation with ada5LABEL and ada5LABEL/old without destroying and rebuil= ding the pool. =C2=A0Any attempts to 'detach', 'offline' or anything else o= n either of those two logical entries fails with a 'no valid replicas'. If you have the original drive (the /old one), put it back in the system, "zpool online" it, then you should be able to "zpool remove" or "zpool detach" the other drive. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Mon Jan 2 06:27:15 2012 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1293106566B; Mon, 2 Jan 2012 06:27:15 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id B1C628FC08; Mon, 2 Jan 2012 06:27:15 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so17285273obb.13 for ; Sun, 01 Jan 2012 22:27:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=DIxWHvrrLL9xMvdWeHAc7/mZHQe8hpSdFu4l5CpXi/g=; b=LsRdeZWZZ4x15tqk80aGLsYLTGfoNNoc89JU/nvK5Xz/RrKZOxWLXGvt1xBgvv2f2L amQPpPuFNQyZR8SalIEQR3WHXsG+6OEh7C3ouvrH4Hp+WZ5nizZ1ZjlaejYWO67w/XJA jV6YvL0C5O0gqPtgaSr4LKs3TXh+G2GaZfp6c= MIME-Version: 1.0 Received: by 10.182.159.70 with SMTP id xa6mr40992253obb.1.1325483907833; Sun, 01 Jan 2012 21:58:27 -0800 (PST) Received: by 10.182.152.6 with HTTP; Sun, 1 Jan 2012 21:58:27 -0800 (PST) Date: Sun, 1 Jan 2012 21:58:27 -0800 Message-ID: From: Garrett Cooper To: Pawel Jakub Dawidek Content-Type: text/plain; charset=ISO-8859-1 Cc: re@freebsd.org, fs@freebsd.org Subject: r227705 broke my ZFS on root 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, 02 Jan 2012 06:27:16 -0000 Pawel and Releng, I spent over 5 hours today debugging my stable-9 RC2 -> PRERELEASE upgrade not working, and I've finally come to the conclusion that r227705 completely broke my boot. This commit is in 9.0-RC{2,3}, and probably needs to be redone. Bottom line is what happens is that when it boots it fails to find the bootfs ("/"), and thus when I do ls in gptzfsboot it says "Hmmm... nothing here boss!" when it tries to load /boot/kernel/kernel . I saw this before (around RC1) and wrote it off as local changes, because I preemptively MFCed r226549, r226551, r226552, r226553, r226568, r226611 as I thought the changes were pertinent to ZFS runtime and not boottime. I unmerged r226549, minus the open_disk changes and magically everything works again... So, what next? My setup: $ uname -a FreeBSD bayonetta.local 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0 r229187M: Sun Jan 1 14:39:27 PST 2012 gcooper@bayonetta.local:/usr/obj/store/freebsd/stable/9/sys/BAYONETTA amd64 $ zfs list NAME USED AVAIL REFER MOUNTPOINT sac 71.1G 819G 1.01G / sac/scratch 67.5G 819G 62.4G /scratch sac/scratch/freenas 5.08G 819G 4.14G /scratch/freenas sac/scratch/freenas/FreeBSD 965M 819G 928M /scratch/freenas/FreeBSD sac/usr 2.38G 819G 2.38G /usr sac/var 150M 819G 150M /var store 1.04T 765G 1.04T /store store/freebsd 4.11G 765G 4.11G /store/freebsd store/home 39.0M 765G 39.0M /usr/home $ zpool get bootfs,cachefile sac store NAME PROPERTY VALUE SOURCE sac bootfs sac local sac cachefile - default store bootfs - default store cachefile - default I don't have any noticeable changes in the sys directory that would impact this functionality, but I'll be more than happy to share if interested. Thanks, -Garrett From owner-freebsd-fs@FreeBSD.ORG Mon Jan 2 07:51:45 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 67977106566B for ; Mon, 2 Jan 2012 07:51:45 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 4B38D8FC1D for ; Mon, 2 Jan 2012 07:51:44 +0000 (UTC) Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta12.emeryville.ca.mail.comcast.net with comcast id GXrb1i0010EPchoACXreFQ; Mon, 02 Jan 2012 07:51:38 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta01.emeryville.ca.mail.comcast.net with comcast id GXWk1i00L1t3BNj8MXWkve; Mon, 02 Jan 2012 07:30:45 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 92BDB102C1E; Sun, 1 Jan 2012 23:51:43 -0800 (PST) Date: Sun, 1 Jan 2012 23:51:43 -0800 From: Jeremy Chadwick To: Michael DeMan Message-ID: <20120102075143.GA84030@icarus.home.lan> References: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> <20120101195411.GA73487@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: zfs detach/replace 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, 02 Jan 2012 07:51:45 -0000 On Sun, Jan 01, 2012 at 09:09:37PM -0800, Michael DeMan wrote: > Sounds realistic to me that the 'replace' command works after a > 'detach' is properly done. No, that's not correct either. "zpool detach" means "remove this device from the mirror" (and applies only to mirrors). Per the man page: zpool detach pool device Detaches device from a mirror. The operation is refused if there are no other valid replicas of the data. Therefore, there's no way you could do "zpool detach" followed by a "zpool replace", because once you do the "detach", there's no device shown as part of the pool for you to issue a "replace" command. You can't issue "zpool detach" on raidzX pools either. Proof: # mdconfig -a -t malloc -o reserve -s 64m -u 0 # mdconfig -a -t malloc -o reserve -s 64m -u 1 # mdconfig -a -t malloc -o reserve -s 64m -u 2 # zpool create testpool raidz1 md0 md1 md2 # zpool status testpool pool: testpool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM testpool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 md0 ONLINE 0 0 0 md1 ONLINE 0 0 0 md2 ONLINE 0 0 0 errors: No known data errors # zpool detach testpool md1 cannot detach md1: only applicable to mirror and replacing vdevs If you read the link I provided you (to my blog), you'd see that I *did not* issue "zpool detach" anywhere during the procedure. Furthermore, the "zpool offline" commands I issued prior to "zpool replace" aren't really necessary either -- I did that solely as a nicety. > In my case, I forgot to do the 'detach' - just did the 'replace' after > changing the drive (and after a reboot). From there, ZFS gets in the > state below - where it automagically created label/ada5LABEL/old and > appears to be wanting to do the rebuild onto label/ada5LABEL as if it > is part of a mirrored pair? I can't answer this. I avoid using disk labels like the plague, so there may be something going on with those that explains the behaviour you're seeing. Others will need to help here. > This pool was built on FreeBSD 8.0, with an operating system update to > 8.1 after that. Possibly I could try and update the ZFS pool version > or something if this is fixed now? Let's be specific here: the pool version that's on the disks (that is to say, the actual format of the data on the disks as shown by "zpool upgrade -v") almost certainly has nothing to do with the issue you're seeing. Anyone running ZFS on FreeBSD should be using RELENG_8 or newer. That means 8.2-STABLE as recently as possible or newer. Bugfixes for all sorts of things have committed between 8.0 and 8.1, and 8.1 and 8.2. I spent a very long time trying to track all of these changes, you can read old posts of mine on the mailing lists if you wish. These days, I just tell people to run RELENG_8 as recent as possible and be done with it. > I know for a fact, back with FreeBSD 7.x, that this same scenario > could occur. Basically on below - my old notes show there is no way > to fix the situation with ada5LABEL and ada5LABEL/old without > destroying and rebuilding the pool. Any attempts to 'detach', > 'offline' or anything else on either of those two logical entries > fails with a 'no valid replicas'. I wouldn't be surprised. You're not going to get good support here for RELENG_7. I've proven to you already that on RELENG_8 -- even RELENG_8 as of August 2010 -- works just fine with "zpool replace". I'm really not sure what else to tell you. There may be quirks/oddities pertaining to raidz2 (vs. raidz1) on FreeBSD, but I simply don't know. I know for a fact "zpool replace pool XXX" on RELENG_8 works just fine (no labels, and ahci.ko is used) by doing this procedure: 1. Yank physical (bad) disk. 2. Wait a few seconds. The kernel will report "lost device" on the console (viewable via "dmesg"). 3. "zpool status" at this point will, I believe, show the disk as "UNAVAIL" -- and only that disk. For systems which may act weird with disk numbering, you should make note of what the device string is (e.g. "ada4"). 4. Insert physical (new) disk. 5. Wait a few seconds. The kernel will report ATA IDENTIFY results (disk model, size of disk, speed/capability, etc.) on the console (viewable via "dmesg"). Take note of what the device string is that the kernel assigned to this disk. 6. Issue one of the following commands, depending on whether or not the device string in #3 and #5 is identical or not: - If identical: "zpool replace pool XXX" Example: "zpool replace pool ada2" - If different: "zpool replace pool old new" (old = what's in step 3, new = what's in step 5) Example: "zpool replace pool ada2 ada6" FreeBSD does not have autoreplace support (the framework/shims for that are not written), so there is no way the system will "magically issue the 'zpool replace' command" if you physically replace a disk. There are some weirdos ( :-) ) on the mailing lists who have tried to make this happen automatically via devd(8), but that's a separate topic which I won't partake in. I've never personally experienced the device-name-changing problem *on the fly*, but have seen it in the case a system reboot/reset is done between phases. I tend to "wire down" my AHCI ports to specific device indexes anyway. Here's what's in our /boot/loader.conf on all of our 6-port production machines (RELENG_8 using ahci.ko): # "Wire down" device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at="ahcich0" hint.scbus.1.at="ahcich1" hint.scbus.2.at="ahcich2" hint.scbus.3.at="ahcich3" hint.scbus.4.at="ahcich4" hint.scbus.5.at="ahcich5" hint.ada.0.at="scbus0" hint.ada.1.at="scbus1" hint.ada.2.at="scbus2" hint.ada.3.at="scbus3" hint.ada.4.at="scbus4" hint.ada.5.at="scbus5" -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Mon Jan 2 11:07:00 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 E9B20106564A for ; Mon, 2 Jan 2012 11:07:00 +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 D67C58FC20 for ; Mon, 2 Jan 2012 11:07:00 +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 q02B70va005094 for ; Mon, 2 Jan 2012 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q02B70k9005092 for freebsd-fs@FreeBSD.org; Mon, 2 Jan 2012 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Jan 2012 11:07:00 GMT Message-Id: <201201021107.q02B70k9005092@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, 02 Jan 2012 11:07:01 -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/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/162083 fs [zfs] [panic] zfs unmount -f pool o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o 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/161674 fs [ufs] snapshot on journaled ufs doesn't work 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/161511 fs [unionfs] Filesystem deadlocks when using multiple uni 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 Random UFS root filesystem corruption with SU+J [regre 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/159971 fs [ffs] [panic] panic with soft updates journaling durin 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/158711 fs [ffs] [panic] panic in ffs_blkfree and ffs_valloc o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157722 fs [geli] unable to newfs a geli encrypted partition 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 f 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/153847 fs [nfs] [panic] Kernel panic from incorrect m_free in nf o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small 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 " o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an 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/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/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 f sparc/123566 fs [zfs] zpool import issue: EOVERFLOW 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 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/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o 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 256 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Jan 2 13:39:25 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 B590A106564A; Mon, 2 Jan 2012 13:39:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8B8D88FC14; Mon, 2 Jan 2012 13:39:25 +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 q02DdPkr049978; Mon, 2 Jan 2012 13:39:25 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q02DdPKV049974; Mon, 2 Jan 2012 13:39:25 GMT (envelope-from linimon) Date: Mon, 2 Jan 2012 13:39:25 GMT Message-Id: <201201021339.q02DdPKV049974@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/163770: [zfs] [hang] LOR between zfs&syncer + vnlru leading to ZFS deadlock 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, 02 Jan 2012 13:39:25 -0000 Old Synopsis: LOR between zfs&syncer + vnlru leading to ZFS deadlock New Synopsis: [zfs] [hang] LOR between zfs&syncer + vnlru leading to ZFS deadlock Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 2 13:39:00 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=163770 From owner-freebsd-fs@FreeBSD.ORG Mon Jan 2 15:17:10 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 87E9C106564A; Mon, 2 Jan 2012 15:17:10 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5DE898FC14; Mon, 2 Jan 2012 15:17:10 +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 q02FHAZc041159; Mon, 2 Jan 2012 15:17:10 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q02FHAOO041155; Mon, 2 Jan 2012 15:17:10 GMT (envelope-from eadler) Date: Mon, 2 Jan 2012 15:17:10 GMT Message-Id: <201201021517.q02FHAOO041155@freefall.freebsd.org> To: gcooper@FreeBSD.org, eadler@FreeBSD.org, freebsd-fs@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: kern/117314: [ntfs] Long-filename only NTFS fs'es cause kernel panics on read 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, 02 Jan 2012 15:17:10 -0000 Synopsis: [ntfs] Long-filename only NTFS fs'es cause kernel panics on read State-Changed-From-To: open->feedback State-Changed-By: eadler State-Changed-When: Mon Jan 2 15:17:09 UTC 2012 State-Changed-Why: Is this still an issue? http://www.freebsd.org/cgi/query-pr.cgi?pr=117314 From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 01:01: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 C8FDD1065678 for ; Tue, 3 Jan 2012 01:01:06 +0000 (UTC) (envelope-from freebsd@deman.com) Received: from plato.corp.nas.com (plato.corp.nas.com [66.114.32.138]) by mx1.freebsd.org (Postfix) with ESMTP id 815E38FC15 for ; Tue, 3 Jan 2012 01:01:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by plato.corp.nas.com (Postfix) with ESMTP id E90F2104B3AD1 for ; Mon, 2 Jan 2012 17:01:05 -0800 (PST) X-Virus-Scanned: amavisd-new at corp.nas.com Received: from plato.corp.nas.com ([127.0.0.1]) by localhost (plato.corp.nas.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qn8fbinSLdg0 for ; Mon, 2 Jan 2012 17:01:04 -0800 (PST) Received: from [192.168.0.4] (184-100-212-115.ptld.qwest.net [184.100.212.115]) by plato.corp.nas.com (Postfix) with ESMTPSA id BD3F6104B3ABD for ; Mon, 2 Jan 2012 17:01:03 -0800 (PST) From: Michael DeMan Mime-Version: 1.0 (Apple Message framework v1084) Date: Mon, 2 Jan 2012 17:01:02 -0800 In-Reply-To: <20120102075143.GA84030@icarus.home.lan> To: freebsd-fs@freebsd.org References: <8EA721E0-977D-483C-AC06-1040B87E0AA7@deman.com> <20120101195411.GA73487@icarus.home.lan> <20120102075143.GA84030@icarus.home.lan> Message-Id: <238E7987-3741-4260-91E5-80B677ECB8EF@deman.com> X-Mailer: Apple Mail (2.1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: zfs detach/replace 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, 03 Jan 2012 01:01:06 -0000 Yeah, I will update to 8.2 and see if things clear up. On Jan 1, 2012, at 11:51 PM, Jeremy Chadwick wrote: > Anyone running ZFS on FreeBSD should be using RELENG_8 or newer. From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 01:29: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 0A314106566C for ; Tue, 3 Jan 2012 01:29:07 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 93B1E8FC08 for ; Tue, 3 Jan 2012 01:29:06 +0000 (UTC) Received: by wibhr1 with SMTP id hr1so15485129wib.13 for ; Mon, 02 Jan 2012 17:29:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=/IBUnXamSS5jwV5XLWXl3XTCiOry1BfFY9pec3Dw+So=; b=E31xzJ+3pRy7FigiVvVZ/CEfAByS25DPLhGzVfCSkEwIuNtu+hrr0ZKALpy4bBlHpJ CU2CxdztJVuRBFeUzTd5M2XR+UUjlz/WNpRMRlT6umuVluOstlCG67SIWVWBaQKtj55F gNAWiA407HxEfYzQXr8zN3wg20R9GZtAd9mug= MIME-Version: 1.0 Received: by 10.180.91.201 with SMTP id cg9mr110294821wib.15.1325552619563; Mon, 02 Jan 2012 17:03:39 -0800 (PST) Received: by 10.180.5.35 with HTTP; Mon, 2 Jan 2012 17:03:39 -0800 (PST) Date: Mon, 2 Jan 2012 20:03:39 -0500 Message-ID: From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: ZFS (Solaris 11 source 'leaked') 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, 03 Jan 2012 01:29:07 -0000 Some recent news of interest to the ZFS and open source crowd. Has Oracle confirmed this yet? build: 175 zpool: 33 https://thepiratebay.org/torrent/6894292 http://www.phoronix.com/scan.php?page=news_item&px=MTAzMDE http://openindiana.org/pipermail/openindiana-discuss/2011-December/006542.html From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 01:55:02 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 F0E0A106566B for ; Tue, 3 Jan 2012 01:55:02 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [78.47.114.122]) by mx1.freebsd.org (Postfix) with ESMTP id 3314D8FC0A for ; Tue, 3 Jan 2012 01:55:01 +0000 (UTC) Received: (qmail 36206 invoked by uid 89); 3 Jan 2012 01:44:56 -0000 Received: by simscan 1.4.0 ppid: 36197, pid: 36203, t: 0.0509s scanners: attach: 1.4.0 clamav: 0.97.1/m:54/d:14227 Received: from unknown (HELO ?192.168.1.201?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 3 Jan 2012 01:44:56 -0000 Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Rainer Duffner In-Reply-To: Date: Tue, 3 Jan 2012 02:44:55 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <39A90A91-4FB3-4B52-A7D2-4E0349B78E6F@ultra-secure.de> References: To: grarpamp X-Mailer: Apple Mail (2.1251.1) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS (Solaris 11 source 'leaked') 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, 03 Jan 2012 01:55:03 -0000 Am 03.01.2012 um 02:03 schrieb grarpamp: > Some recent news of interest to the ZFS and open source crowd. > Has Oracle confirmed this yet? I'm sorry - but are you joking? Oracle didn't even confirm the "no more Solaris-source" leaked memo. And that was just a piece of (virtual) paper. I haven't downloaded it (I'm not a developer, it's useless to me anyway) = but I suspect that what applies to other leaked sources (remember the = NT4+W2K leak a couple of years ago?) also applies to this one: stay away = from it, if you want to be in a position to commit code to *anything*. = Ever. From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 06:30: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 13D5B106564A for ; Tue, 3 Jan 2012 06:30:21 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 9D4458FC0A for ; Tue, 3 Jan 2012 06:30:20 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so27136271wgb.31 for ; Mon, 02 Jan 2012 22:30:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3kX3gyW4Cnnhk7Tpo+Q9M7xEzV5YvQw6V44P8O/q18Q=; b=rp9n1VuHPMggAQSiz6b5JfzATj6D3nUeCRi9WNXOBekMCASPqQ/VaH2XtRshAZQrC4 DURmikOY4Z6mOJfysU3DHP9vtwNw+65s2fE1KHVG96k6MKieknhBMwQHrQZ1nt6rbwRy LT83HnxUxTQEwPMH81743rSccJAPPkZD9pFQg= MIME-Version: 1.0 Received: by 10.227.206.78 with SMTP id ft14mr50481198wbb.24.1325572219558; Mon, 02 Jan 2012 22:30:19 -0800 (PST) Received: by 10.180.5.35 with HTTP; Mon, 2 Jan 2012 22:30:19 -0800 (PST) In-Reply-To: <39A90A91-4FB3-4B52-A7D2-4E0349B78E6F@ultra-secure.de> References: <39A90A91-4FB3-4B52-A7D2-4E0349B78E6F@ultra-secure.de> Date: Tue, 3 Jan 2012 01:30:19 -0500 Message-ID: From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: ZFS (Solaris 11 source 'leaked') 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, 03 Jan 2012 06:30:21 -0000 >> Some recent news of interest to the ZFS and open source crowd. >> Has Oracle confirmed this yet? > > I'm sorry - but are you joking? No one is joking. It is merely a mention of news of interest. No one is saying anything about any company. Any company may do as it wishes when it wishes. This is not intended to spark a flood/rehash. It is purely informational for those not in the know. There are many situations in which developers, students, doc/spec writers, journalists and so forth may make good and taint free use of this file. And also good unproveable use. And also get themselves and/or their projects in trouble. To each their own. Consult an authority. Here are some hashes as observed in the wild. That is all. SHA1 946d94114d381ed292e68d89f0b34242468491c3 solaris11.tar.bz2 MD5 b0b053c0a0316668cc4f90100e1b0353 solaris11.tar.bz2 From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 09:50:11 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 48363106564A for ; Tue, 3 Jan 2012 09:50:11 +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 36A498FC0C for ; Tue, 3 Jan 2012 09:50:11 +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 q039oBie095945 for ; Tue, 3 Jan 2012 09:50:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q039oBvC095944; Tue, 3 Jan 2012 09:50:11 GMT (envelope-from gnats) Date: Tue, 3 Jan 2012 09:50:11 GMT Message-Id: <201201030950.q039oBvC095944@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Garrett Cooper Cc: Subject: Re: conf/116931: lack of fsck_cd9660 prevents mounting iso images with mdconfig_md%d (with workaround) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Garrett Cooper List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2012 09:50:11 -0000 The following reply was made to PR conf/116931; it has been noted by GNATS. From: Garrett Cooper To: bug-followup@FreeBSD.org, phk@critter.freebsd.dk Cc: Subject: Re: conf/116931: lack of fsck_cd9660 prevents mounting iso images with mdconfig_md%d (with workaround) Date: Tue, 3 Jan 2012 01:41:28 -0800 The attached patch looks ok. The only suggestion that I have is that since you're grabbing the fs field from /etc/fstab, instead of keeping a blacklist, I would just use command -v; example: $ command -v fsck_ufs; echo $? /sbin/fsck_ufs 0 $ command -v fsck_cd9660; echo $? 1 $ This would reduce the number of needed special cases in the mdconfig script. Thanks! -Garrett From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 12:27:52 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 6D9D0106564A for ; Tue, 3 Jan 2012 12:27:52 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id E86BA8FC15 for ; Tue, 3 Jan 2012 12:27:51 +0000 (UTC) Received: by yenl9 with SMTP id l9so10225462yen.13 for ; Tue, 03 Jan 2012 04:27:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jVcWKoEjj+SpgxpAKj5LBsk7BaePilaxQM/1rhYtUG8=; b=UjrK23GMDgsDbuV8kPzIyiQpbjSoHu7RovE4JNcV4ONJ57hM1ocPcWyafNrnvsMNJz X9Ul7xNwKvkeArKmC1jqhO0V3G0jkAfqzz74nGoHO5A9+xPvr/arjGmzraqVT5tnPwks tMFR8tYua63T93kM6VBtH16DSFXUoYR30wjJ8= MIME-Version: 1.0 Received: by 10.236.78.193 with SMTP id g41mr65602330yhe.25.1325593671199; Tue, 03 Jan 2012 04:27:51 -0800 (PST) Received: by 10.236.139.193 with HTTP; Tue, 3 Jan 2012 04:27:51 -0800 (PST) In-Reply-To: <4F003EB8.6080006@dannysplace.net> References: <4F003EB8.6080006@dannysplace.net> Date: Tue, 3 Jan 2012 12:27:51 +0000 Message-ID: From: krad To: Dan Carroll 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 With Gpart partitions 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, 03 Jan 2012 12:27:52 -0000 On 1 January 2012 11:08, Dan Carroll wrote: > Hello all, > > I'm currently trying to fix a suspect drive and I've run into a small > problem. > I was wondering if someone can shed some light into how GPart works (when > using labels for partitions). > > My drives are 2Tb WD RE4's, originally the array was using 1Tb Seagate > drives, and I was replacing about 3 of those a year, but since I migrated > to the RE4's this is my first problem. > Here is my setup. > > NAME STATE READ WRITE CKSUM > areca ONLINE 0 0 0 > raidz1 ONLINE 0 0 0 > gpt/data0 ONLINE 0 0 0 > gpt/data1 ONLINE 0 0 0 > gpt/data2 ONLINE 0 0 0 > gpt/data3 ONLINE 103 0 0 > gpt/data4 ONLINE 0 0 0 > gpt/data5 ONLINE 0 0 0 > raidz1 ONLINE 0 0 0 > gpt/data6 ONLINE 0 0 0 > gpt/data7 ONLINE 0 0 0 > gpt/data8 ONLINE 0 0 0 > gpt/data9 ONLINE 0 0 0 > gpt/data10 ONLINE 0 0 0 > gpt/data11 ONLINE 0 0 0 > > errors: No known data errors > > The drives are connected via an Areca controller, each drive is created as > a Pass-Thru (just like JBod but also using the cache and BBU). > So, my problem began when I tried to replace gpt/data3. > > Here is what I did. > > # zpool offline areca gpt/data3 > # shutdown -p now > > (I could not remember the camcontrol commands to detach a device and > shutting down was not an issue, so that's the way I did it.) > Replace the failing drive and re-create the passthru device in the areca > console. > power on. > > All good so far, except the drive I used as a replacement came from a > decomissioned server. It already had a gpart label on it. > As it happens it was labelled data2. > > I quickly shut down the system, took the new drive out, put it into > another machine and wiped the first few megabytes of the disk with dd. > > I re-inserted the drive, recreated the passthrough, powered up and > replaced the offlined drive. > Now it's resilvering. > Currently, my system looks like this: > > NAME STATE READ WRITE CKSUM > areca DEGRADED 0 0 0 > raidz1 DEGRADED 0 0 0 > gpt/data0 ONLINE 0 0 0 > gpt/data1 ONLINE 0 0 0 > da8p1 ONLINE 0 0 0 > replacing DEGRADED 0 0 0 > gpt/data3/old OFFLINE 0 0 0 > gpt/data3 ONLINE 0 0 0 931G resilvered > gpt/data4 ONLINE 0 0 0 > gpt/data5 ONLINE 0 0 0 > raidz1 ONLINE 0 0 0 > gpt/data6 ONLINE 0 0 0 > gpt/data7 ONLINE 0 0 0 > gpt/data8 ONLINE 0 0 0 > gpt/data9 ONLINE 0 0 0 > gpt/data10 ONLINE 0 0 0 > gpt/data11 ONLINE 0 0 0 > > The resilvering looks like it's working fine, but I am curious about the > gpart label. When I query da8p1 I cannot find it. > # gpart show da8 > => 34 3907029101 da8 GPT (1.8T) > 34 3907029101 1 freebsd-zfs (1.8T) > > # glabel list da8p1 > glabel: No such geom: da8p1. > > It should look like this: > > # gpart show da0 > => 34 3907029101 da0 GPT (1.8T) > 34 3907029101 1 freebsd-zfs (1.8T) > > # glabel list da0p1 > Geom name: da0p1 > Providers: > 1. Name: gpt/data0 > Mediasize: 2000398899712 (1.8T) > Sectorsize: 512 > Mode: r1w1e1 > secoffset: 0 > offset: 0 > seclength: 3907029101 > length: 2000398899712 > index: 0 > Consumers: > 1. Name: da0p1 > Mediasize: 2000398899712 (1.8T) > Sectorsize: 512 > Mode: r1w1e2 > > > So it seems to me that when I inserted the second drive with a label > called data2, it wiped the label from the *original* drive. > ZFS does not seem to care about this. If the label is simply a label and > losing it does not alter the user data on the drive, then this makes sense. > > I am wondering if I can simply re-label the partition without fear of > breaking something? Reading the glabel man page I suspect that it may be > ok. > > -D > ______________________________**_________________ > 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 > " > Just a not you dont appear to be 4k aligned on this drive. As the drive capacity is > 1.5 Tb you probably should be. You will also be ashift=9 as well. This may or may not be a problem for you. From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 13:02:08 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 174B8106567A for ; Tue, 3 Jan 2012 13:02:08 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mailgw.dannysplace.net (mailgw.dannysplace.net [204.109.56.184]) by mx1.freebsd.org (Postfix) with ESMTP id 9D5048FC25 for ; Tue, 3 Jan 2012 13:02:07 +0000 (UTC) Received: from [203.206.171.212] (helo=[192.168.10.12]) by mailgw.dannysplace.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Ri415-000A3U-31; Tue, 03 Jan 2012 23:03:03 +1000 Message-ID: <4F02FC42.1040103@dannysplace.net> Date: Tue, 03 Jan 2012 23:01:54 +1000 From: Dan Carroll User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: krad References: <4F003EB8.6080006@dannysplace.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Exim-Version: 4.76 (build at 08-Jun-2011 18:40:49) X-Date: 2012-01-03 23:02:59 X-Connected-IP: 203.206.171.212:62807 X-Message-Linecount: 24 X-Body-Linecount: 11 X-Message-Size: 1088 X-Body-Size: 472 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on damka.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailgw.dannysplace.net) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 03 Jan 2012 13:02:08 -0000 On 3/01/2012 10:27 PM, krad wrote: > Just a not you dont appear to be 4k aligned on this drive. As the > drive capacity is > 1.5 Tb you probably should be. You will also be > ashift=9 as well. This may or may not be a problem for you. That was intentional, as I *thought* these drives were not 4k sector drives. I am not sure how I am supposed to tell. They are WD RE4 drives. I confess, however to knowing nothing about ashift=9..... Could you elaborate? -D From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 14:34: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 7E2C51065672 for ; Tue, 3 Jan 2012 14:34:29 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.freebsd.org (Postfix) with ESMTP id 141F88FC18 for ; Tue, 3 Jan 2012 14:34:28 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MbcdF-1S0aAQ43xF-00IqOm; Tue, 03 Jan 2012 15:34:28 +0100 Message-ID: <4F0311F2.7050209@brockmann-consult.de> Date: Tue, 03 Jan 2012 15:34:26 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> In-Reply-To: <4F02FC42.1040103@dannysplace.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:l2WImqyTl1cjsQc3k9+OYl2GYB0ywc4PSFujXlWpFka trAHYA4EOqx5cT4/qFBDKQReFYI2AzwmjW/n2wrz1ZUSAgY1ZS 0yyvYPyu/Wsw1KZRY6GUJtvju04VgVLFM6MLtVAvM7/HCKGaBM zkmRMXCHAbPBtbfVEaaUtO1LbNyowzbwmkpA0M+EhU8Guf1Kne hUJURbkJr5YUHt6PK3D43b50Ev8wt2APJJIL89n8aydlzL9uR1 Yu9GU3YWSanvluIewx4fu7dQNHWDYnY5CI4QcDhg+OBQPQfKng s8dSxplYYaDxC6TlPNVbw3Waap0zbvxpdFSE8XzUz1Po2weT45 2ouXCVeVXm+5nFTz2oxLdzRVmob4rpna64b+2WZNB Subject: Re: ZFS With Gpart partitions 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, 03 Jan 2012 14:34:29 -0000 On 01/03/2012 02:01 PM, Dan Carroll wrote: > On 3/01/2012 10:27 PM, krad wrote: >> Just a not you dont appear to be 4k aligned on this drive. As the >> drive capacity is > 1.5 Tb you probably should be. You will also be >> ashift=9 as well. This may or may not be a problem for you. > > That was intentional, as I *thought* these drives were not 4k sector > drives. I am not sure how I am supposed to tell. They are WD RE4 > drives. > I confess, however to knowing nothing about ashift=9..... Could you > elaborate? Read this thread: ZFS using 'advanced format drives' with FreeBSD (8.2-RC3) http://forums.freebsd.org/showthread.php?t=21644 (and of course don't play around and run the dd command, etc. for disks with valuable data on them) > > -D > _______________________________________________ > 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 Tue Jan 3 14:38:24 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 E20981065687 for ; Tue, 3 Jan 2012 14:38:24 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mx1.freebsd.org (Postfix) with ESMTP id 8DF2C8FC16 for ; Tue, 3 Jan 2012 14:38:24 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0Lp6ay-1SMuQl22dg-00esMH; Tue, 03 Jan 2012 15:38:23 +0100 Message-ID: <4F0312DF.8050004@brockmann-consult.de> Date: Tue, 03 Jan 2012 15:38:23 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> In-Reply-To: <4F0311F2.7050209@brockmann-consult.de> X-Enigmail-Version: 1.1.2 X-Provags-ID: V02:K0:LkK3FPxclQb+T5g6y7VyMBnw8ABAaCqzz6aVoSF3Y83 cnXIp02vOUUD+4SoZzPmemRX58NOZXIqiVq6kTukNLWaEkjFpX p03g/UWE09sK1BjyKmu8r9SeBq1gb8I/rSSR+y3r0jIn7Iymro bRa2XMJ9qtcBl5s72l5AUYMFv3zlvPIyEUrnO6DVgYhA9VjLI4 NSFsq+8aSP4dlNZCjF5TyJTDESjWRu2tFrdwg1lDhG+DXJlcV8 1hqSi82sHOhSkVaFvhbrzN5P2x7QuJD+HvZLeCQwVW0UFal8JX +LRaWT5fCeBAttRyTIh+433+0A0pkq+uQsJ7Otlcy8dxl06AkM Wk1IHzsFJPuFcSDLam83KUZz8bL1PkDi/loagfiZn Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS With Gpart partitions 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, 03 Jan 2012 14:38:25 -0000 On 01/03/2012 03:34 PM, Peter Maloney wrote: > On 01/03/2012 02:01 PM, Dan Carroll wrote: >> On 3/01/2012 10:27 PM, krad wrote: >>> Just a not you dont appear to be 4k aligned on this drive. As the >>> drive capacity is > 1.5 Tb you probably should be. You will also be >>> ashift=9 as well. This may or may not be a problem for you. >> That was intentional, as I *thought* these drives were not 4k sector >> drives. I am not sure how I am supposed to tell. They are WD RE4 >> drives. >> I confess, however to knowing nothing about ashift=9..... Could you >> elaborate? > Read this thread: > > ZFS using 'advanced format drives' with FreeBSD (8.2-RC3) > http://forums.freebsd.org/showthread.php?t=21644 > > (and of course don't play around and run the dd command, etc. for disks > with valuable data on them) > And looking at dmesg or /var/log/messages should probably tell you what your sector size is. eg. # dmesg | grep "da2:" or # grep "da2:" /var/log/messages or # bunzip2 -c /var/log/messages.1.bz2 | grep "da2:" Nov 28 13:59:35 bcnas1 kernel: da2: Fixed Direct Access SCSI-6 device Nov 28 13:59:35 bcnas1 kernel: da2: 600.000MB/s transfers Nov 28 13:59:35 bcnas1 kernel: da2: Command Queueing enabled Nov 28 13:59:35 bcnas1 kernel: da2: 2861588MB (5860533168 *512 byte sectors*: 255H 63S/T 364801C) >> -D >> _______________________________________________ >> 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 Tue Jan 3 14:53:12 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 E9B10106564A for ; Tue, 3 Jan 2012 14:53:11 +0000 (UTC) (envelope-from mattblists@icritical.com) Received: from mail1.icritical.com (mail1.icritical.com [93.95.13.41]) by mx1.freebsd.org (Postfix) with SMTP id 4B1478FC17 for ; Tue, 3 Jan 2012 14:53:10 +0000 (UTC) Received: (qmail 3111 invoked from network); 3 Jan 2012 14:53:08 -0000 Received: from localhost (127.0.0.1) by mail1.icritical.com with SMTP; 3 Jan 2012 14:53:08 -0000 Received: (qmail 3100 invoked by uid 599); 3 Jan 2012 14:53:08 -0000 Received: from unknown (HELO icritical.com) (212.57.254.146) by mail1.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 03 Jan 2012 14:53:08 +0000 Message-ID: <4F031654.1080200@icritical.com> Date: Tue, 03 Jan 2012 14:53:08 +0000 From: Matt Burke User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110403 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Jan 2012 14:53:08.0040 (UTC) FILETIME=[67C4FC80:01CCCA27] X-Virus-Scanned: by iCritical at mail1.icritical.com Subject: ZFS v28 on -STABLE not using hot spare 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, 03 Jan 2012 14:53:12 -0000 Over the holidays one of the disks on a server has failed, but despite configuring a hot spare, ZFS hasn't used it for some reason. Can anyone shed some light on what I might have mis-configured to break the hot-spare functionality? [root@x ~]# uname -a FreeBSD x 8.2-STABLE FreeBSD 8.2-STABLE #4: Mon Dec 5 12:43:58 GMT 2011 root@x:/usr/obj/usr/src/sys/x amd64 [root@x ~]# more /usr/src/sys/amd64/conf/x include GENERIC ident x options GEOM_STRIPE options ROUTETABLES=4 [root@x ~]# zpool status -v pool: data state: DEGRADED status: One or more devices are faulted in response to persistent errors. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the faulted device, or use 'zpool clear' to mark the device repaired. scan: none requested config: NAME STATE READ WRITE CKSUM data DEGRADED 0 0 0 mirror-0 ONLINE 0 0 0 mfid0 ONLINE 0 0 0 mfid14 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 mfid1 ONLINE 0 0 0 mfid15 ONLINE 0 0 0 mirror-2 DEGRADED 0 0 0 mfid2 ONLINE 0 0 0 mfid16 FAULTED 0 931 0 too many errors mirror-3 ONLINE 0 0 0 mfid3 ONLINE 0 0 0 mfid17 ONLINE 0 0 0 mirror-4 ONLINE 0 0 0 mfid4 ONLINE 0 0 0 mfid18 ONLINE 0 0 0 mirror-5 ONLINE 0 0 0 mfid5 ONLINE 0 0 0 mfid19 ONLINE 0 0 0 mirror-6 ONLINE 0 0 0 mfid6 ONLINE 0 0 0 mfid20 ONLINE 0 0 0 mirror-7 ONLINE 0 0 0 mfid7 ONLINE 0 0 0 mfid21 ONLINE 0 0 0 mirror-8 ONLINE 0 0 0 mfid8 ONLINE 0 0 0 mfid22 ONLINE 0 0 0 mirror-9 ONLINE 0 0 0 mfid9 ONLINE 0 0 0 mfid23 ONLINE 0 0 0 mirror-10 ONLINE 0 0 0 mfid10 ONLINE 0 0 0 mfid24 ONLINE 0 0 0 logs mirror-11 ONLINE 0 0 0 mfid13 ONLINE 0 0 0 mfid26 ONLINE 0 0 0 cache mfid12 ONLINE 0 0 0 mfid25 ONLINE 0 0 0 spares mfid11 AVAIL errors: No known data errors The logs show loads of mfi1 and mfid16 errors for a few minutes, and then (presumably when ZFS dropped the disk) nothing relevant after that. ZFS hasn't logged anything, not even that it's failed a disk. I've manually done a 'zpool replace data mfid16 mfid11' which has brought the spare in without problems, but I'm eager to learn what I did (or didn't do?) to cause the spare to not be used automatically. Thanks in advance, -- The information contained in this message is confidential and is intended for the addressee only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. Critical Software Ltd. reserves the right to monitor and record e-mail messages sent to and from this address for the purposes of investigating or detecting any unauthorised use of its system and ensuring its effective operation. Critical Software Ltd. registered in England, 04909220. Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH. ------------------------------------------------------------ This message has been scanned for security threats by iCritical. For further information, please visit www.icritical.com ------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 15:10: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 1EFCB106564A for ; Tue, 3 Jan 2012 15:10:56 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.freebsd.org (Postfix) with ESMTP id AA81A8FC0C for ; Tue, 3 Jan 2012 15:10:55 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MVawh-1SFRtR3EDv-00YSQW; Tue, 03 Jan 2012 16:10:54 +0100 Message-ID: <4F031A7E.6090008@brockmann-consult.de> Date: Tue, 03 Jan 2012 16:10:54 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F031654.1080200@icritical.com> In-Reply-To: <4F031654.1080200@icritical.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:fd8E4omrtSAbg5yedABarjYNI6y9vK65S9/0FvIdCHA wcTMapSk+csezKDf3WQrkSbJqh8UQawuGO+0vCCSChkUcUBr+1 RasM9xRvSwpe+FUgteeyqvtTRJuUHK36woMy9IJbuemOU9sCHH 7fXHrpxjqXXd+/m8/iaF9OV2TLZZGaeIMxBiURKvpTSSFxYlgG brsQ4iEhQfvknqK9lXZHgXkhC+ezosm3QNi3Dw5blqUHd1OlJ3 AG4aps8LLEGy3QaZdq4hMVT860/6B+V7618q0ItaAef5hoadbq Btm8v2ALKtINv5HWF7RLYolCPEmTlbehwDJ/o0I2jHzshaMkL6 /nWf9mG9PD8abW+InH2auKYggK0jGy6nw8+m7xjv9 Subject: Re: ZFS v28 on -STABLE not using hot spare 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, 03 Jan 2012 15:10:56 -0000 On 01/03/2012 03:53 PM, Matt Burke wrote: > mfid16 FAULTED 0 931 0 too many errors Hot spare management is not part of the zfs system; it is part of the OpenSolaris "fault management daemon" which does not exist in FreeBSD. :( Here is some random reading about it: http://freebsd.1045724.n5.nabble.com/ZFS-hot-spares-automatic-or-not-td3955449.html I don't know if there is something more recent to actually accomplish this. And FYI there is a property you are supposed to set to get OpenSolaris FMD to replace a disk, so if it is implemented in some daemon you find or have, maybe this property is required: # zpool get autoreplace tank NAME PROPERTY VALUE SOURCE tank autoreplace off default -- -------------------------------------------- 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 Tue Jan 3 15:17: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 B0B3F106566B for ; Tue, 3 Jan 2012 15:17:18 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 454068FC08 for ; Tue, 3 Jan 2012 15:17:17 +0000 (UTC) Received: by wibhr1 with SMTP id hr1so16054923wib.13 for ; Tue, 03 Jan 2012 07:17:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=64Ewm/b2/7RC2ojdYs6szAbWBe/ESIIer4MO2kghh3o=; b=TFmpgvDfmeHb3VPxDDhRNl9gqnxo9MYjCCTIvdXYceNl7F7qcOBFCZd1ZU3zVWM3o1 sVv3U+lH/tvX09hI9wdiCG4pc+WXRjrJmsTQjAWT5XMTujy0idw/ShztEunWWcbKmXLY hvSnvtHr2UCG9rLALVLKIXZHOiKksj7okRa78= Received: by 10.180.106.165 with SMTP id gv5mr113954976wib.18.1325603837140; Tue, 03 Jan 2012 07:17:17 -0800 (PST) Received: from [192.168.50.103] (double-l.xs4all.nl. [80.126.205.144]) by mx.google.com with ESMTPS id q5sm6282754wbo.8.2012.01.03.07.17.15 (version=SSLv3 cipher=OTHER); Tue, 03 Jan 2012 07:17:16 -0800 (PST) Message-ID: <4F031BF7.8000900@gmail.com> Date: Tue, 03 Jan 2012 16:17:11 +0100 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Matt Burke References: <4F031654.1080200@icritical.com> In-Reply-To: <4F031654.1080200@icritical.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v28 on -STABLE not using hot spare 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, 03 Jan 2012 15:17:18 -0000 Matt Burke schreef: > Over the holidays one of the disks on a server has failed, but despite > configuring a hot spare, ZFS hasn't used it for some reason. Can anyone > shed some light on what I might have mis-configured to break the hot-spare > functionality? > > > [root@x ~]# uname -a > FreeBSD x 8.2-STABLE FreeBSD 8.2-STABLE #4: Mon Dec 5 12:43:58 GMT 2011 > root@x:/usr/obj/usr/src/sys/x amd64 > > > [root@x ~]# more /usr/src/sys/amd64/conf/x > include GENERIC > ident x > > options GEOM_STRIPE > options ROUTETABLES=4 > > > [root@x ~]# zpool status -v > pool: data > state: DEGRADED > status: One or more devices are faulted in response to persistent errors. > Sufficient replicas exist for the pool to continue functioning in a > degraded state. > action: Replace the faulted device, or use 'zpool clear' to mark the device > repaired. > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > data DEGRADED 0 0 0 > mirror-0 ONLINE 0 0 0 > mfid0 ONLINE 0 0 0 > mfid14 ONLINE 0 0 0 > mirror-1 ONLINE 0 0 0 > mfid1 ONLINE 0 0 0 > mfid15 ONLINE 0 0 0 > mirror-2 DEGRADED 0 0 0 > mfid2 ONLINE 0 0 0 > mfid16 FAULTED 0 931 0 too many errors > mirror-3 ONLINE 0 0 0 > mfid3 ONLINE 0 0 0 > mfid17 ONLINE 0 0 0 > mirror-4 ONLINE 0 0 0 > mfid4 ONLINE 0 0 0 > mfid18 ONLINE 0 0 0 > mirror-5 ONLINE 0 0 0 > mfid5 ONLINE 0 0 0 > mfid19 ONLINE 0 0 0 > mirror-6 ONLINE 0 0 0 > mfid6 ONLINE 0 0 0 > mfid20 ONLINE 0 0 0 > mirror-7 ONLINE 0 0 0 > mfid7 ONLINE 0 0 0 > mfid21 ONLINE 0 0 0 > mirror-8 ONLINE 0 0 0 > mfid8 ONLINE 0 0 0 > mfid22 ONLINE 0 0 0 > mirror-9 ONLINE 0 0 0 > mfid9 ONLINE 0 0 0 > mfid23 ONLINE 0 0 0 > mirror-10 ONLINE 0 0 0 > mfid10 ONLINE 0 0 0 > mfid24 ONLINE 0 0 0 > logs > mirror-11 ONLINE 0 0 0 > mfid13 ONLINE 0 0 0 > mfid26 ONLINE 0 0 0 > cache > mfid12 ONLINE 0 0 0 > mfid25 ONLINE 0 0 0 > spares > mfid11 AVAIL > > errors: No known data errors > > The logs show loads of mfi1 and mfid16 errors for a few minutes, and then > (presumably when ZFS dropped the disk) nothing relevant after that. ZFS > hasn't logged anything, not even that it's failed a disk. > > I've manually done a 'zpool replace data mfid16 mfid11' which has brought > the spare in without problems, but I'm eager to learn what I did (or didn't > do?) to cause the spare to not be used automatically. > > Thanks in advance, > > ZFS on FreeBSD does not have 'HOT' spares. They are cold, and human intervention is needed to replace a disk in a pool. There are some topics about it on the net. I opt for a warning, because a lot of users get a false security sence when using the spares. zpool should not accept the spare without a warning to the user that it is a cold spare and not a hot one. it looks like there is some work planned for a zfs deamon that should overcome this problem on FreeBSD http://svnweb.freebsd.org/base?view=revision&revision=222836 On Solaris there is also a deamon running that does the actual replace. It should not be to hard to make a script that checks every minute or what time interval you want and check if a pool is degraded, then check if autoreplace is set for the pool, if so check if there is a spare, if so do the actual replace. Unfortunally i can not code :( Maybe some one has a script lying around. ?? regards Johan Hendriks From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 15:52:14 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 A0097106566C for ; Tue, 3 Jan 2012 15:52:14 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 687238FC0C for ; Tue, 3 Jan 2012 15:52:14 +0000 (UTC) Received: by qcse13 with SMTP id e13so14368571qcs.13 for ; Tue, 03 Jan 2012 07:52:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.134.197 with SMTP id k5mr18467268qct.58.1325604449705; Tue, 03 Jan 2012 07:27:29 -0800 (PST) Received: by 10.229.217.207 with HTTP; Tue, 3 Jan 2012 07:27:29 -0800 (PST) In-Reply-To: <4F031BF7.8000900@gmail.com> References: <4F031654.1080200@icritical.com> <4F031BF7.8000900@gmail.com> Date: Tue, 3 Jan 2012 16:27:29 +0100 Message-ID: From: Olivier Smedts To: Johan Hendriks Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v28 on -STABLE not using hot spare 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, 03 Jan 2012 15:52:14 -0000 2012/1/3 Johan Hendriks : > ZFS on FreeBSD does not have 'HOT' spares. > They are cold, and human intervention is needed to replace a disk in a po= ol. > There are some topics about it on the net. > > I opt for a warning, because a lot of users get a false security sence wh= en > using the spares. > zpool should not accept the spare without a warning to the user that it i= s a > cold spare and not a hot one. > > it looks like there is some work planned for a zfs deamon that should > overcome this problem on FreeBSD > > http://svnweb.freebsd.org/base?view=3Drevision&revision=3D222836 > > On Solaris there is also a deamon running that does the actual replace. > > It should not be to hard to make a script that checks every minute or wha= t > time interval you want and check if a pool is degraded, then check if > autoreplace is set for the pool, if so check if there is a spare, if so d= o > the actual replace. > Unfortunally i can not code :( > Maybe some one has a script lying around. ?? Or maybe some devd.conf lines to handle this automatically ? Cheers --=20 Olivier Smedts=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 _ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 ASCII ribbon campaign ( ) e-mail: olivier@gid0.org=A0 =A0 =A0 =A0 - against HTML email & vCards=A0 X www: http://www.gid0.org=A0 =A0 - against proprietary attachments / \ =A0 "Il y a seulement 10 sortes de gens dans le monde : =A0 ceux qui comprennent le binaire, =A0 et ceux qui ne le comprennent pas." From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 16:07:30 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 CABF41065676 for ; Tue, 3 Jan 2012 16:07:30 +0000 (UTC) (envelope-from karl.oulmi@ibl.fr) Received: from mima.ibl.fr (mima.ibl.fr [193.49.178.26]) by mx1.freebsd.org (Postfix) with ESMTP id 69C8A8FC12 for ; Tue, 3 Jan 2012 16:07:30 +0000 (UTC) X-Virus-Scanned: amavisd-new at ibl.fr Message-ID: <4F032422.2050006@ibl.fr> Date: Tue, 03 Jan 2012 16:52:02 +0100 From: Karl Oulmi MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020201020008050403050903" X-Scanned-By: MIMEDefang 2.64 on 193.49.178.28 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Mount an iSCSI partition at startup 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, 03 Jan 2012 16:07:30 -0000 This is a cryptographically signed message in MIME format. --------------ms020201020008050403050903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Hi all, I'm testing a freshbox with FreeBSD 9.0RC3 and an ISCSI SAN DELL MD3200i.= I followed the howto here :=20 http://www.cyberciti.biz/faq/freebsd-iscsi-initiator-howto/ Everything is working fine and quick. The only thing I'am unable to succeed is to automaticaly mount the=20 remote iSCSI partition when I start my FreeBSD box. I tried some script via crontab (@reboot...) or via /usr/local/etc/rc.d/ = but nothing is working :( Furthermore I need a reliable solution because this box should become=20 the mail server of my company. If someone could help me, It would be nice. Best regards, Karl. --------------ms020201020008050403050903-- From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 16:24:30 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 B57161065749 for ; Tue, 3 Jan 2012 16:24:30 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id 9AA108FC1B for ; Tue, 3 Jan 2012 16:24:30 +0000 (UTC) Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta14.emeryville.ca.mail.comcast.net with comcast id H4Mn1i0081afHeLAE4QPlJ; Tue, 03 Jan 2012 16:24:23 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta17.emeryville.ca.mail.comcast.net with comcast id H3gX1i00a1t3BNj8d3gXrc; Tue, 03 Jan 2012 15:40:31 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C9594102C19; Tue, 3 Jan 2012 08:24:28 -0800 (PST) Date: Tue, 3 Jan 2012 08:24:28 -0800 From: Jeremy Chadwick To: Peter Maloney Message-ID: <20120103162428.GA18661@icarus.home.lan> References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> <4F0312DF.8050004@brockmann-consult.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F0312DF.8050004@brockmann-consult.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 03 Jan 2012 16:24:30 -0000 On Tue, Jan 03, 2012 at 03:38:23PM +0100, Peter Maloney wrote: > On 01/03/2012 03:34 PM, Peter Maloney wrote: > > On 01/03/2012 02:01 PM, Dan Carroll wrote: > >> On 3/01/2012 10:27 PM, krad wrote: > >>> Just a not you dont appear to be 4k aligned on this drive. As the > >>> drive capacity is > 1.5 Tb you probably should be. You will also be > >>> ashift=9 as well. This may or may not be a problem for you. > >> That was intentional, as I *thought* these drives were not 4k sector > >> drives. I am not sure how I am supposed to tell. They are WD RE4 > >> drives. > >> I confess, however to knowing nothing about ashift=9..... Could you > >> elaborate? > > Read this thread: > > > > ZFS using 'advanced format drives' with FreeBSD (8.2-RC3) > > http://forums.freebsd.org/showthread.php?t=21644 > > > > (and of course don't play around and run the dd command, etc. for disks > > with valuable data on them) > > > And looking at dmesg or /var/log/messages should probably tell you what > your sector size is. > > eg. > # dmesg | grep "da2:" > > or > > # grep "da2:" /var/log/messages > > or > > # bunzip2 -c /var/log/messages.1.bz2 | grep "da2:" > Nov 28 13:59:35 bcnas1 kernel: da2: Fixed Direct > Access SCSI-6 device > Nov 28 13:59:35 bcnas1 kernel: da2: 600.000MB/s transfers > Nov 28 13:59:35 bcnas1 kernel: da2: Command Queueing enabled > Nov 28 13:59:35 bcnas1 kernel: da2: 2861588MB (5860533168 *512 byte > sectors*: 255H 63S/T 364801C) This is incorrect. Most 4KB sector drives advertise a logical sector size of 512 (this is to maintain/guarantee full compatibility with older OSes and existing software), while sometimes advertising a physical sector size of 4096. Comparatively, Intel SSDs advertise both a logical and physical sector size of 512, even though we all know better. Use either "camcontrol identify" or "camcontrol inquiry" (which command depends on if you're using SATA-via-CAM or native SCSI) to find out. If this doesn't work for you, try using smartmontools (if there's a difference between logical/physical it will display both, otherwise it'll say "logical/physical" literally). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 16:27:22 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 634C01065675 for ; Tue, 3 Jan 2012 16:27:22 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 31F8D8FC22 for ; Tue, 3 Jan 2012 16:27:21 +0000 (UTC) Received: from omta24.emeryville.ca.mail.comcast.net ([76.96.30.92]) by qmta06.emeryville.ca.mail.comcast.net with comcast id H3df1i0021zF43QA64TFPn; Tue, 03 Jan 2012 16:27:15 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta24.emeryville.ca.mail.comcast.net with comcast id H5HN1i0111t3BNj8k5HPH8; Tue, 03 Jan 2012 17:17:23 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id AE3AB102C19; Tue, 3 Jan 2012 08:27:20 -0800 (PST) Date: Tue, 3 Jan 2012 08:27:20 -0800 From: Jeremy Chadwick To: Olivier Smedts Message-ID: <20120103162720.GA18750@icarus.home.lan> References: <4F031654.1080200@icritical.com> <4F031BF7.8000900@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v28 on -STABLE not using hot spare 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, 03 Jan 2012 16:27:22 -0000 On Tue, Jan 03, 2012 at 04:27:29PM +0100, Olivier Smedts wrote: > 2012/1/3 Johan Hendriks : > > ZFS on FreeBSD does not have 'HOT' spares. > > They are cold, and human intervention is needed to replace a disk in a pool. > > There are some topics about it on the net. > > > > I opt for a warning, because a lot of users get a false security sence when > > using the spares. > > zpool should not accept the spare without a warning to the user that it is a > > cold spare and not a hot one. > > > > it looks like there is some work planned for a zfs deamon that should > > overcome this problem on FreeBSD > > > > http://svnweb.freebsd.org/base?view=revision&revision=222836 > > > > On Solaris there is also a deamon running that does the actual replace. > > > > It should not be to hard to make a script that checks every minute or what > > time interval you want and check if a pool is degraded, then check if > > autoreplace is set for the pool, if so check if there is a spare, if so do > > the actual replace. > > Unfortunally i can not code :( > > Maybe some one has a script lying around. ?? > > Or maybe some devd.conf lines to handle this automatically ? At this time I'd recommend against that -- such a script would have to parse "zpool status" output *very carefully*. The output format from "zpool status" has also changed over time (on both Solaris and FreeBSD), so this complicates matters further. autoreplace defaults to off on FreeBSD because the necessary code bits in the kernel aren't completed. If folks need spares to be utilised automatically, they should run Solaris or OpenIndiana/Illumos. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 17:28:17 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 6BB02106566C for ; Tue, 3 Jan 2012 17:28:17 +0000 (UTC) (envelope-from mattblists@icritical.com) Received: from mail1.icritical.com (mail1.icritical.com [93.95.13.41]) by mx1.freebsd.org (Postfix) with SMTP id B8B438FC14 for ; Tue, 3 Jan 2012 17:28:16 +0000 (UTC) Received: (qmail 31426 invoked from network); 3 Jan 2012 17:28:14 -0000 Received: from localhost (127.0.0.1) by mail1.icritical.com with SMTP; 3 Jan 2012 17:28:14 -0000 Received: (qmail 31409 invoked by uid 599); 3 Jan 2012 17:28:13 -0000 Received: from unknown (HELO icritical.com) (212.57.254.146) by mail1.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 03 Jan 2012 17:28:13 +0000 Message-ID: <4F033AAD.3080200@icritical.com> Date: Tue, 03 Jan 2012 17:28:13 +0000 From: Matt Burke User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110403 Thunderbird/3.1.9 MIME-Version: 1.0 To: Peter Maloney References: <4F031654.1080200@icritical.com> <4F031A7E.6090008@brockmann-consult.de> In-Reply-To: <4F031A7E.6090008@brockmann-consult.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Jan 2012 17:28:13.0460 (UTC) FILETIME=[123B6540:01CCCA3D] X-Virus-Scanned: by iCritical at mail1.icritical.com Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v28 on -STABLE not using hot spare 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, 03 Jan 2012 17:28:17 -0000 On 01/03/12 15:10, Peter Maloney wrote: > On 01/03/2012 03:53 PM, Matt Burke wrote: >> mfid16 FAULTED 0 931 0 too many errors > > Hot spare management is not part of the zfs system; it is part of the > OpenSolaris "fault management daemon" which does not exist in FreeBSD. OK, my mistake was that I took the man page to be correct: Hot Spares ZFS allows devices to be associated with pools as "hot spares". These devices are not actively used in the pool, but when an active device fails, it is automatically replaced by a hot spare. Perhaps that section should be replaced with the text "DANGER: Hot spares are not (currently) implemented in FreeBSD"? It can't just be me who thought it would be a good idea to configure the RAID controller to just export all the disks as JBOD and configure a few hot spares under ZFS because: a) the man page says you can b) the userland command lets you do it c) there's no documentation telling you it's non-functional At least I'm aware of this now, so I can drop the spare drives on my other ZFS machines and have the controllers deal with replacement, but I think this is a pretty serious flaw in FreeBSD to tell users their data is safer than it actually is... If it's a good idea, I could attempt to make a patch to prevent zpool from setting a drive as spare? > And FYI there is a property you are supposed to set to get OpenSolaris > FMD to replace a disk, so if it is implemented in some daemon you find > or have, maybe this property is required: Hmm, the same man page suggests that the autoreplace property only comes into play once you've physically replaced the failed disk. The information contained in this message is confidential and is intended for the addressee only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. Critical Software Ltd. reserves the right to monitor and record e-mail messages sent to and from this address for the purposes of investigating or detecting any unauthorised use of its system and ensuring its effective operation. Critical Software Ltd. registered in England, 04909220. Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH. ------------------------------------------------------------ This message has been scanned for security threats by iCritical. For further information, please visit www.icritical.com ------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 17:56: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 074741065677 for ; Tue, 3 Jan 2012 17:56:18 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id AC6B38FC12 for ; Tue, 3 Jan 2012 17:56:17 +0000 (UTC) Received: by yenl9 with SMTP id l9so10409271yen.13 for ; Tue, 03 Jan 2012 09:56:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; bh=Nv/nDY3FXSgC7HhjrM2He42ne+02NKUZcegD6TYYjSU=; b=pjhxvIo1qlcmJy8/iiiMCllA6A4JhzFgLUy5yBlDZpfOunYiTVQgfav767k/mu4Ntm 6BxzW6IsqFOVmSwfz27OVXB2MzOcphh3BoZdn2JTP/N3X9G7sqLeEanR72b2xSYRr8Zd QQX8Xdm+U9YVlJxf8GAv5l1KVJZn1HBkLJcdY= Received: by 10.236.127.145 with SMTP id d17mr49126222yhi.39.1325613377038; Tue, 03 Jan 2012 09:56:17 -0800 (PST) Received: from DataIX.net (adsl-99-181-137-35.dsl.klmzmi.sbcglobal.net. [99.181.137.35]) by mx.google.com with ESMTPS id k48sm11627891yhj.16.2012.01.03.09.56.14 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 03 Jan 2012 09:56:15 -0800 (PST) Sender: Jason Hellenthal Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.5/8.14.5) with ESMTP id q03HuCCd018489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Jan 2012 12:56:12 -0500 (EST) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.5/8.14.5/Submit) id q03Hu7Zj018486; Tue, 3 Jan 2012 12:56:07 -0500 (EST) (envelope-from jhell@DataIX.net) Date: Tue, 3 Jan 2012 12:56:07 -0500 From: Jason Hellenthal To: grarpamp Message-ID: <20120103175607.GB10481@DataIX.net> References: <39A90A91-4FB3-4B52-A7D2-4E0349B78E6F@ultra-secure.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline In-Reply-To: Cc: freebsd-fs@freebsd.org Subject: Re: ZFS (Solaris 11 source 'leaked') 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, 03 Jan 2012 17:56:18 -0000 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Ethics are trouble for you arent they ? On Tue, Jan 03, 2012 at 01:30:19AM -0500, grarpamp wrote: > >> Some recent news of interest to the ZFS and open source crowd. > >> Has Oracle confirmed this yet? > > > > I'm sorry - but are you joking? >=20 > No one is joking. > It is merely a mention of news of interest. > No one is saying anything about any company. > Any company may do as it wishes when it wishes. > This is not intended to spark a flood/rehash. > It is purely informational for those not in the know. >=20 > There are many situations in which developers, students, doc/spec > writers, journalists and so forth may make good and taint free use > of this file. And also good unproveable use. And also get themselves > and/or their projects in trouble. To each their own. Consult an authority. >=20 > Here are some hashes as observed in the wild. That is all. >=20 > SHA1 946d94114d381ed292e68d89f0b34242468491c3 solaris11.tar.bz2 > MD5 b0b053c0a0316668cc4f90100e1b0353 solaris11.tar.bz2 > _______________________________________________ > 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" --=20 ;s =3D; --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJPA0E3AAoJEJBXh4mJ2FR+Ub8H/2jKLqHwxu02Lus7QsgbeRCp FcxYPm5PjbqYHie0e0hPcSuu9Rziqt5iPocTEPdkWllIHnkjTiXOWB4AZb1WROlt 7XJwNue4VMxnZi5h4xeQbZX7xZ8FGeFgmN6kwLryLsCh/XhiG+B1VDibMTBd1dAe lV0i4ycr2vr1YY4JVAEDFVHzfC8iqSgt2cVXFwzDAntjjmi6CVwz6mAaV3Pd5Y5P F2PH6bwqJiKvqNo0EkjNk7FveU95ov2FrzI5O0IqsgpPr7u6/QQTMyb2hX82vQIW ZX8tXMdtclbAz6trJDQ8vJiAq2o+fi4d5L1IMqvvNIIMiHjgs/4gfEDldsjCDno= =yNol -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 18:53: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 4A8691065670 for ; Tue, 3 Jan 2012 18:53:39 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 185668FC14 for ; Tue, 3 Jan 2012 18:53:38 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so19102361obb.13 for ; Tue, 03 Jan 2012 10:53:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xDaqBGa0hxGGQlE5deeaEF4FclC7qGydVra7fV5uvDc=; b=eVQWfZHX+TpWKoiXp9uAvwWTTf01tVavHc+6mW9mxKkAz+xl6js2VdGUqDbspblzGJ kXpVCwh0TT/XeQ+5vlXqGAx3FlawiQHPwpYwmwqQXeGx0tvSgaEaWoyTby4KkuE6dBLA kay0PRcgRHqnQSueS53eYmQ1StdQ+de1m3ZRI= MIME-Version: 1.0 Received: by 10.182.42.37 with SMTP id k5mr45386977obl.40.1325615444285; Tue, 03 Jan 2012 10:30:44 -0800 (PST) Received: by 10.182.171.67 with HTTP; Tue, 3 Jan 2012 10:30:44 -0800 (PST) In-Reply-To: <4F032422.2050006@ibl.fr> References: <4F032422.2050006@ibl.fr> Date: Tue, 3 Jan 2012 21:30:44 +0300 Message-ID: From: Sergey Kandaurov To: Karl Oulmi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: Mount an iSCSI partition at startup 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, 03 Jan 2012 18:53:39 -0000 On 3 January 2012 19:52, Karl Oulmi wrote: > Hi all, > > I'm testing a freshbox with FreeBSD 9.0RC3 and an ISCSI SAN DELL MD3200i. > > I followed the howto here : > http://www.cyberciti.biz/faq/freebsd-iscsi-initiator-howto/ > > Everything is working fine and quick. > > The only thing I'am unable to succeed is to automaticaly mount the remote > iSCSI partition when I start my FreeBSD box. > > I tried some script via crontab (@reboot...) or via /usr/local/etc/rc.d/ but > nothing is working :( > > Furthermore I need a reliable solution because this box should become the > mail server of my company. > > If someone could help me, It would be nice. Hi. IIRC there is no rc support for iscontrol(8) in the tree yet. To the moment, two different versions were proposed to act exactly what you ask - mount a list of file systems specified elsewhere, and none of them committed due to lack of review. [I hope this will happen eventually.] http://lists.freebsd.org/pipermail/freebsd-rc/2010-January/001841.html http://lists.freebsd.org/pipermail/freebsd-rc/2010-May/001971.html -- wbr, pluknet From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 19:10:12 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 924E51065675 for ; Tue, 3 Jan 2012 19:10:12 +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 67A768FC0C for ; Tue, 3 Jan 2012 19:10:12 +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 q03JAClv012366 for ; Tue, 3 Jan 2012 19:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q03JAClo012365; Tue, 3 Jan 2012 19:10:12 GMT (envelope-from gnats) Date: Tue, 3 Jan 2012 19:10:12 GMT Message-Id: <201201031910.q03JAClo012365@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/142401: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2012 19:10:12 -0000 The following reply was made to PR kern/142401; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/142401: commit references a PR Date: Tue, 3 Jan 2012 19:09:11 +0000 (UTC) Author: pfg Date: Tue Jan 3 19:09:01 2012 New Revision: 229407 URL: http://svn.freebsd.org/changeset/base/229407 Log: Minor cleanups to ntfs code bzero -> memset rename variables to avoid shadowing. PR: 142401 Obtained from: NetBSD Approved by jhb (mentor) Modified: head/sys/fs/ntfs/ntfs_compr.c head/sys/fs/ntfs/ntfs_subr.c Modified: head/sys/fs/ntfs/ntfs_compr.c ============================================================================== --- head/sys/fs/ntfs/ntfs_compr.c Tue Jan 3 19:01:54 2012 (r229406) +++ head/sys/fs/ntfs/ntfs_compr.c Tue Jan 3 19:09:01 2012 (r229407) @@ -42,7 +42,7 @@ int ntfs_uncompblock( - u_int8_t * buf, + u_int8_t * dbuf, u_int8_t * cbuf) { u_int32_t ctag; @@ -60,8 +60,8 @@ ntfs_uncompblock( dprintf(("ntfs_uncompblock: len: %x instead of %d\n", len, 0xfff)); } - memcpy(buf, cbuf + 2, len + 1); - bzero(buf + len + 1, NTFS_COMPBLOCK_SIZE - 1 - len); + memcpy(dbuf, cbuf + 2, len + 1); + memset(dbuf + len + 1, 0, NTFS_COMPBLOCK_SIZE - 1 - len); return len + 3; } cpos = 2; @@ -78,12 +78,12 @@ ntfs_uncompblock( boff = -1 - (GET_UINT16(cbuf + cpos) >> dshift); blen = 3 + (GET_UINT16(cbuf + cpos) & lmask); for (j = 0; (j < blen) && (pos < NTFS_COMPBLOCK_SIZE); j++) { - buf[pos] = buf[pos + boff]; + dbuf[pos] = dbuf[pos + boff]; pos++; } cpos += 2; } else { - buf[pos++] = cbuf[cpos++]; + dbuf[pos++] = cbuf[cpos++]; } ctag >>= 1; } Modified: head/sys/fs/ntfs/ntfs_subr.c ============================================================================== --- head/sys/fs/ntfs/ntfs_subr.c Tue Jan 3 19:01:54 2012 (r229406) +++ head/sys/fs/ntfs/ntfs_subr.c Tue Jan 3 19:09:01 2012 (r229407) @@ -1636,7 +1636,7 @@ ntfs_readntvattr_plain( for(; remains; remains--) uiomove("", 1, uio); } else - bzero(data, tocopy); + memset(data, 0, tocopy); data = data + tocopy; } cnt++; @@ -1783,7 +1783,7 @@ ntfs_readattr( uiomove("", 1, uio); } else - bzero(data, tocopy); + memset(data, 0, tocopy); } else { error = ntfs_uncompunit(ntmp, uup, cup); if (error) _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 20:31:23 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 99BFF1065673 for ; Tue, 3 Jan 2012 20:31:23 +0000 (UTC) (envelope-from danno@internet2.edu) Received: from int-proxy02.merit.edu (int-proxy02.merit.edu [207.75.116.231]) by mx1.freebsd.org (Postfix) with ESMTP id 58E2B8FC19 for ; Tue, 3 Jan 2012 20:31:22 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy02.merit.edu (Postfix) with ESMTP id 54E54120099; Tue, 3 Jan 2012 15:31:22 -0500 (EST) X-Virus-Scanned: amavisd-new at int-proxy02.merit.edu Received: from int-proxy02.merit.edu ([127.0.0.1]) by localhost (int-proxy02.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wznKITUrGITx; Tue, 3 Jan 2012 15:31:22 -0500 (EST) Received: from shrubbery.internet2.edu (eduroam-wlan-116.internet2.edu [198.108.5.116]) by int-proxy02.merit.edu (Postfix) with ESMTPSA id F1539120098; Tue, 3 Jan 2012 15:31:21 -0500 (EST) Message-ID: <4F036598.1020809@internet2.edu> Date: Tue, 03 Jan 2012 15:31:20 -0500 From: Dan Pritts User-Agent: Postbox 3.0.2 (Macintosh/20111203) MIME-Version: 1.0 To: Jeremy Chadwick References: <4EE118C7.8030803@internet2.edu> <4EE12632.4070309@internet2.edu> <4EE21936.6020502@egr.msu.edu> <4EEA155C.5050305@internet2.edu> <20111215161207.GA26990@icarus.home.lan> <4EEA23CC.2030105@internet2.edu> In-Reply-To: <4EEA23CC.2030105@internet2.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS hangs with 8.2-stable (was 8.2-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: Tue, 03 Jan 2012 20:31:23 -0000 I wrote: >> Otherwise, I'd consider just running OpenIndiana on this system, >> assuming their LSI card driver support is good. > > I've been wondering whether I should head in that direction, I guess I > know the answer. I'd been avoiding it due to concerns over its > long-term viability. At this point short-term functionality wins. > > The solaris LSI drivers were/are rock solid in my experience. Sun > used LSI chips extensively, presumably oracle still does. Just wanted to follow up on this thread. Soon after I sent this we installed nexenta core. The system has been up for 13 days. We have scrubbed all 5 of the 9-disk pools at least twice, with no hiccups. Clearly the mpt driver (or something else with the combo of freebsd, zfs, and this hardware) still needs some help. I'm not highly motivated to spend a bunch of time reproducing this issue for debugging, especially for a driver for such an old card. That said, does anyone know if the mpt code was used as a base for other drivers? If so it might be worth putting in the effort. thanks, danno -- Dan Pritts, Sr. Systems Engineer Internet2 office: +1-734-352-4953 | mobile: +1-734-834-7224 From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 23:31:02 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 61F021065678 for ; Tue, 3 Jan 2012 23:31:02 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 17E7E8FC0A for ; Tue, 3 Jan 2012 23:31:01 +0000 (UTC) Received: by ghrr16 with SMTP id r16so7002058ghr.13 for ; Tue, 03 Jan 2012 15:31:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xZfxlMq4UZcQsZBW2TTjilFoRrgZJXjLZ9PGDiNpOQk=; b=kGq81gz1gwQbpU7BUU1IR4PSq1YGSJ0BBBszB7P+SGkVzGjZvmshgVKaC1HuO23tQb FisRRBvBOadaEntZzLlUO2RrJT3UD9sXY92pBSMeGMcD/paYWJQsmLQUZ7H4aVkAl6Df XOlZCMFQhW+YTreH2iXylTie5PAWlGnbbJzTk= MIME-Version: 1.0 Received: by 10.236.150.134 with SMTP id z6mr70419330yhj.42.1325633461393; Tue, 03 Jan 2012 15:31:01 -0800 (PST) Received: by 10.236.139.193 with HTTP; Tue, 3 Jan 2012 15:31:01 -0800 (PST) Received: by 10.236.139.193 with HTTP; Tue, 3 Jan 2012 15:31:01 -0800 (PST) In-Reply-To: <20120103162428.GA18661@icarus.home.lan> References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> <4F0312DF.8050004@brockmann-consult.de> <20120103162428.GA18661@icarus.home.lan> Date: Tue, 3 Jan 2012 23:31:01 +0000 Message-ID: From: krad To: Jeremy Chadwick 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 With Gpart partitions 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, 03 Jan 2012 23:31:02 -0000 There has been.quite a bit of discussion on this already and I think the safest way is to always 4k align as this works fine on.both drive types On Jan 3, 2012 4:29 PM, "Jeremy Chadwick" wrote: > > On Tue, Jan 03, 2012 at 03:38:23PM +0100, Peter Maloney wrote: > > On 01/03/2012 03:34 PM, Peter Maloney wrote: > > > On 01/03/2012 02:01 PM, Dan Carroll wrote: > > >> On 3/01/2012 10:27 PM, krad wrote: > > >>> Just a not you dont appear to be 4k aligned on this drive. As the > > >>> drive capacity is > 1.5 Tb you probably should be. You will also be > > >>> ashift=9 as well. This may or may not be a problem for you. > > >> That was intentional, as I *thought* these drives were not 4k sector > > >> drives. I am not sure how I am supposed to tell. They are WD RE4 > > >> drives. > > >> I confess, however to knowing nothing about ashift=9..... Could you > > >> elaborate? > > > Read this thread: > > > > > > ZFS using 'advanced format drives' with FreeBSD (8.2-RC3) > > > http://forums.freebsd.org/showthread.php?t=21644 > > > > > > (and of course don't play around and run the dd command, etc. for disks > > > with valuable data on them) > > > > > And looking at dmesg or /var/log/messages should probably tell you what > > your sector size is. > > > > eg. > > # dmesg | grep "da2:" > > > > or > > > > # grep "da2:" /var/log/messages > > > > or > > > > # bunzip2 -c /var/log/messages.1.bz2 | grep "da2:" > > Nov 28 13:59:35 bcnas1 kernel: da2: Fixed Direct > > Access SCSI-6 device > > Nov 28 13:59:35 bcnas1 kernel: da2: 600.000MB/s transfers > > Nov 28 13:59:35 bcnas1 kernel: da2: Command Queueing enabled > > Nov 28 13:59:35 bcnas1 kernel: da2: 2861588MB (5860533168 *512 byte > > sectors*: 255H 63S/T 364801C) > > This is incorrect. Most 4KB sector drives advertise a logical sector > size of 512 (this is to maintain/guarantee full compatibility with older > OSes and existing software), while sometimes advertising a physical > sector size of 4096. Comparatively, Intel SSDs advertise both a logical > and physical sector size of 512, even though we all know better. > > Use either "camcontrol identify" or "camcontrol inquiry" (which command > depends on if you're using SATA-via-CAM or native SCSI) to find out. If > this doesn't work for you, try using smartmontools (if there's a > difference between logical/physical it will display both, otherwise > it'll say "logical/physical" literally). > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | > > _______________________________________________ > 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" There has been.quite a bit of discussion on this already and I think the safest way is to always 4k align as this works fine on.both drive types From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 23:51: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 839141065676 for ; Tue, 3 Jan 2012 23:51:11 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id 289C28FC25 for ; Tue, 3 Jan 2012 23:51:10 +0000 (UTC) Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta09.westchester.pa.mail.comcast.net with comcast id HBWw1i0031ei1Bg59BrBpW; Tue, 03 Jan 2012 23:51:11 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta24.westchester.pa.mail.comcast.net with comcast id HBr91i02E1t3BNj3kBrAZH; Tue, 03 Jan 2012 23:51:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id AFC24102C19; Tue, 3 Jan 2012 15:51:08 -0800 (PST) Date: Tue, 3 Jan 2012 15:51:08 -0800 From: Jeremy Chadwick To: krad Message-ID: <20120103235108.GA25691@icarus.home.lan> References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> <4F0312DF.8050004@brockmann-consult.de> <20120103162428.GA18661@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 03 Jan 2012 23:51:11 -0000 On Tue, Jan 03, 2012 at 11:31:01PM +0000, krad wrote: > There has been.quite a bit of discussion on this already and I think the > safest way is to always 4k align as this works fine on.both drive types > On Jan 3, 2012 4:29 PM, "Jeremy Chadwick" wrote: > > > > On Tue, Jan 03, 2012 at 03:38:23PM +0100, Peter Maloney wrote: > > > On 01/03/2012 03:34 PM, Peter Maloney wrote: > > > > On 01/03/2012 02:01 PM, Dan Carroll wrote: > > > >> On 3/01/2012 10:27 PM, krad wrote: > > > >>> Just a not you dont appear to be 4k aligned on this drive. As the > > > >>> drive capacity is > 1.5 Tb you probably should be. You will also be > > > >>> ashift=9 as well. This may or may not be a problem for you. > > > >> That was intentional, as I *thought* these drives were not 4k sector > > > >> drives. I am not sure how I am supposed to tell. They are WD RE4 > > > >> drives. > > > >> I confess, however to knowing nothing about ashift=9..... Could you > > > >> elaborate? > > > > Read this thread: > > > > > > > > ZFS using 'advanced format drives' with FreeBSD (8.2-RC3) > > > > http://forums.freebsd.org/showthread.php?t=21644 > > > > > > > > (and of course don't play around and run the dd command, etc. for > disks > > > > with valuable data on them) > > > > > > > And looking at dmesg or /var/log/messages should probably tell you what > > > your sector size is. > > > > > > eg. > > > # dmesg | grep "da2:" > > > > > > or > > > > > > # grep "da2:" /var/log/messages > > > > > > or > > > > > > # bunzip2 -c /var/log/messages.1.bz2 | grep "da2:" > > > Nov 28 13:59:35 bcnas1 kernel: da2: Fixed Direct > > > Access SCSI-6 device > > > Nov 28 13:59:35 bcnas1 kernel: da2: 600.000MB/s transfers > > > Nov 28 13:59:35 bcnas1 kernel: da2: Command Queueing enabled > > > Nov 28 13:59:35 bcnas1 kernel: da2: 2861588MB (5860533168 *512 byte > > > sectors*: 255H 63S/T 364801C) > > > > This is incorrect. Most 4KB sector drives advertise a logical sector > > size of 512 (this is to maintain/guarantee full compatibility with older > > OSes and existing software), while sometimes advertising a physical > > sector size of 4096. Comparatively, Intel SSDs advertise both a logical > > and physical sector size of 512, even though we all know better. > > > > Use either "camcontrol identify" or "camcontrol inquiry" (which command > > depends on if you're using SATA-via-CAM or native SCSI) to find out. If > > this doesn't work for you, try using smartmontools (if there's a > > difference between logical/physical it will display both, otherwise > > it'll say "logical/physical" literally). > > There has been.quite a bit of discussion on this already and I think the > safest way is to always 4k align as this works fine on.both drive types Agreed. The question is why FreeBSD isn't using those defaults in its installer. Furthermore, have you tried to actually accomplish this with gpart? I have. I got practically no where. The -a flag doesn't always do the right thing, and with the -b flag you have to "out-smart" internal calculations being made by the software itself. I also had to do the alignment offset at the filesystem level, and not at the actual slice level. E.g.: gpart create -s mbr adaX gpart add -t freebsd adaX gpart create -s bsd adaXs1 gpart add -b 4033 -s {size} -t freebsd-ufs adaXs1 I forget what the result was if I tried to use -b during the first "gpart add", but it kept coming out wrong or simply didn't work. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue Jan 3 23:51: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 745521065691 for ; Tue, 3 Jan 2012 23:51:21 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mailgw.dannysplace.net (mailgw.dannysplace.net [204.109.56.184]) by mx1.freebsd.org (Postfix) with ESMTP id E99098FC12 for ; Tue, 3 Jan 2012 23:51:20 +0000 (UTC) Received: from [203.206.171.212] (helo=[192.168.10.12]) by mailgw.dannysplace.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RiE9O-00076v-V4; Wed, 04 Jan 2012 09:52:16 +1000 Message-ID: <4F039470.9010405@dannysplace.net> Date: Wed, 04 Jan 2012 09:51:12 +1000 From: Dan Carroll User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: krad References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> <4F0312DF.8050004@brockmann-consult.de> <20120103162428.GA18661@icarus.home.lan> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Exim-Version: 4.76 (build at 08-Jun-2011 18:40:49) X-Date: 2012-01-04 09:52:15 X-Connected-IP: 203.206.171.212:61311 X-Message-Linecount: 23 X-Body-Linecount: 10 X-Message-Size: 1302 X-Body-Size: 417 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on damka.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailgw.dannysplace.net) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 03 Jan 2012 23:51:21 -0000 On 4/01/2012 9:31 AM, krad wrote: > There has been.quite a bit of discussion on this already and I think the > safest way is to always 4k align as this works fine on.both drive types Actually that does make sense. 99% of my files on this volume (office data / media server) will be larger than 4k anyway so I guess there is nothing to lose by aligning to a 4k boundry *and* asking ZFS to use 4k block size. -D From owner-freebsd-fs@FreeBSD.ORG Wed Jan 4 00:27:28 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 51B05106564A for ; Wed, 4 Jan 2012 00:27:28 +0000 (UTC) (envelope-from dan@sputnik.net.au) Received: from mailgw.dannysplace.net (mailgw.dannysplace.net [204.109.56.184]) by mx1.freebsd.org (Postfix) with ESMTP id 12FD08FC08 for ; Wed, 4 Jan 2012 00:27:27 +0000 (UTC) Received: from [203.206.171.212] (helo=[192.168.10.12]) by mailgw.dannysplace.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RiEE7-0007Ny-7g; Wed, 04 Jan 2012 09:57:09 +1000 Message-ID: <4F039594.4080408@sputnik.net.au> Date: Wed, 04 Jan 2012 09:56:04 +1000 From: Dan Carroll User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Jeremy Chadwick References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> <4F0312DF.8050004@brockmann-consult.de> <20120103162428.GA18661@icarus.home.lan> <20120103235108.GA25691@icarus.home.lan> In-Reply-To: <20120103235108.GA25691@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Exim-Version: 4.76 (build at 08-Jun-2011 18:40:49) X-Date: 2012-01-04 09:57:07 X-Connected-IP: 203.206.171.212:58507 X-Message-Linecount: 30 X-Body-Linecount: 17 X-Message-Size: 1779 X-Body-Size: 884 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Mail-From: dan@sputnik.net.au X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on damka.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mailgw.dannysplace.net) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 04 Jan 2012 00:27:28 -0000 On 4/01/2012 9:51 AM, Jeremy Chadwick wrote: > Agreed. The question is why FreeBSD isn't using those defaults in its > installer. Furthermore, have you tried to actually accomplish this > with gpart? I have. I got practically no where. The -a flag doesn't > always do the right thing, and with the -b flag you have to > "out-smart" internal calculations being made by the software itself. I > also had to do the alignment offset at the filesystem level, and not > at the actual slice level. E.g.: gpart create -s mbr adaX gpart add -t > freebsd adaX gpart create -s bsd adaXs1 gpart add -b 4033 -s {size} -t > freebsd-ufs adaXs1 I forget what the result was if I tried to use -b > during the first "gpart add", but it kept coming out wrong or simply > didn't work. In that case is there a "best practices" guide out there anywhere describing how this should be done? -D From owner-freebsd-fs@FreeBSD.ORG Wed Jan 4 00:55:23 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 B848110656FB; Wed, 4 Jan 2012 00:55:23 +0000 (UTC) (envelope-from rmacklem@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 89FB18FC17; Wed, 4 Jan 2012 00:55:23 +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 q040tNE5037447; Wed, 4 Jan 2012 00:55:23 GMT (envelope-from rmacklem@freefall.freebsd.org) Received: (from rmacklem@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q040tN9B037443; Wed, 4 Jan 2012 00:55:23 GMT (envelope-from rmacklem) Date: Wed, 4 Jan 2012 00:55:23 GMT Message-Id: <201201040055.q040tN9B037443@freefall.freebsd.org> To: martin@lispworks.com, rmacklem@FreeBSD.org, freebsd-fs@FreeBSD.org From: rmacklem@FreeBSD.org Cc: Subject: Re: kern/153847: [nfs] [panic] Kernel panic from incorrect m_free in nfs_getattr 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, 04 Jan 2012 00:55:23 -0000 Synopsis: [nfs] [panic] Kernel panic from incorrect m_free in nfs_getattr State-Changed-From-To: open->closed State-Changed-By: rmacklem State-Changed-When: Wed Jan 4 00:53:59 UTC 2012 State-Changed-Why: r227690, which is MFC'd to stable/7 as r229451 should fix it so this crash will not occur. http://www.freebsd.org/cgi/query-pr.cgi?pr=153847 From owner-freebsd-fs@FreeBSD.ORG Wed Jan 4 01:00:28 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 9C3F9106564A for ; Wed, 4 Jan 2012 01:00:28 +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 86E838FC0C for ; Wed, 4 Jan 2012 01:00:28 +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 q0410Sef037660 for ; Wed, 4 Jan 2012 01:00:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0410SoI037657; Wed, 4 Jan 2012 01:00:28 GMT (envelope-from gnats) Date: Wed, 4 Jan 2012 01:00:28 GMT Message-Id: <201201040100.q0410SoI037657@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/153847: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 01:00:28 -0000 The following reply was made to PR kern/153847; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/153847: commit references a PR Date: Wed, 4 Jan 2012 00:51:18 +0000 (UTC) Author: rmacklem Date: Wed Jan 4 00:51:05 2012 New Revision: 229451 URL: http://svn.freebsd.org/changeset/base/229451 Log: MFC: r227690 The old NFS client will crash due to the reply being m_freem()'d twice if the server bogusly returns an error with the NFSERR_RETERR bit (bit 31) set. No actual NFS error has this bit set, but it seems that amd will sometimes do this. This patch makes sure the NFSERR_RETERR bit is cleared to avoid a crash. This is not exactly a merge, since the code is in sys/nfsclient/nfs_socket.c, which does not exist in head. Tested by: martin at lispworks.com PR: kern/153847 Modified: stable/7/sys/nfsclient/nfs_socket.c Directory Properties: stable/7/sys/ (props changed) stable/7/sys/cddl/contrib/opensolaris/ (props changed) stable/7/sys/contrib/dev/acpica/ (props changed) stable/7/sys/contrib/pf/ (props changed) Modified: stable/7/sys/nfsclient/nfs_socket.c ============================================================================== --- stable/7/sys/nfsclient/nfs_socket.c Wed Jan 4 00:24:09 2012 (r229450) +++ stable/7/sys/nfsclient/nfs_socket.c Wed Jan 4 00:51:05 2012 (r229451) @@ -1351,6 +1351,12 @@ wait_for_pinned_req: rep->r_xid = *xidp = txdr_unsigned(nfs_xid_gen()); goto tryagain; } + /* + * Make sure NFSERR_RETERR isn't bogusly set by a + * server such as amd. (No actual NFS error has bit 31 + * set.) + */ + error &= ~NFSERR_RETERR; /* * If the File Handle was stale, invalidate the _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Wed Jan 4 01:34: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 400111065780 for ; Wed, 4 Jan 2012 01:34:10 +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 001748FC0A for ; Wed, 4 Jan 2012 01:34:08 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q041Y7Vu015561; Tue, 3 Jan 2012 19:34:08 -0600 (CST) Date: Tue, 3 Jan 2012 19:34:07 -0600 (CST) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Jeremy Chadwick In-Reply-To: <20120103235108.GA25691@icarus.home.lan> Message-ID: References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> <4F0312DF.8050004@brockmann-consult.de> <20120103162428.GA18661@icarus.home.lan> <20120103235108.GA25691@icarus.home.lan> User-Agent: Alpine 2.01 (GSO 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]); Tue, 03 Jan 2012 19:34:08 -0600 (CST) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 04 Jan 2012 01:34:10 -0000 On Tue, 3 Jan 2012, Jeremy Chadwick wrote: >> >> There has been.quite a bit of discussion on this already and I think the >> safest way is to always 4k align as this works fine on.both drive types > > Agreed. The question is why FreeBSD isn't using those defaults in its > installer. As it happens, 4k alignment increases space consumption. A zfs metadata element which previously consumed just 512 bytes (really at least 1024 bytes due to redundancy) would then consume 4k bytes (or 8K bytes due to redundancy). Users with large numbers of small files have definitely noticed the loss of disk space. Users with 15K RPM SAS drives are likely to have different requirements than users with large SATA drives. The installer should obtain the requirements from the user and provide suitable warnings about the negative behavior which may occur from either option. 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 Jan 4 01:35: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 8F0BB1065670 for ; Wed, 4 Jan 2012 01:35:55 +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 503448FC17 for ; Wed, 4 Jan 2012 01:35:55 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q041ZmfR015569; Tue, 3 Jan 2012 19:35:48 -0600 (CST) Date: Tue, 3 Jan 2012 19:35:48 -0600 (CST) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Dan Carroll In-Reply-To: <4F039470.9010405@dannysplace.net> Message-ID: References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> <4F0312DF.8050004@brockmann-consult.de> <20120103162428.GA18661@icarus.home.lan> <4F039470.9010405@dannysplace.net> User-Agent: Alpine 2.01 (GSO 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]); Tue, 03 Jan 2012 19:35:48 -0600 (CST) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 04 Jan 2012 01:35:55 -0000 On Wed, 4 Jan 2012, Dan Carroll wrote: > > Actually that does make sense. 99% of my files on this volume (office data > / media server) will be larger than 4k anyway so I guess there is nothing to > lose by aligning to a 4k boundry *and* asking ZFS to use 4k block size. Except that each file has at least two metadata blocks and these will increase to 4k in size. If the typical file size was 8K, then this would represent almost 100% waste. 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 Jan 4 01:48:17 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 B3890106566B for ; Wed, 4 Jan 2012 01:48:17 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 40FF88FC0A for ; Wed, 4 Jan 2012 01:48:16 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so28292811wgb.31 for ; Tue, 03 Jan 2012 17:48:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=L3uIj3+0dreiQJPxEtRygMPpYf4b7X+2g736pvCOws8=; b=Cyfpqcy7XP6luL8xLYJ6/WfBZGEwLQ0YghHr3Hn58a0S5h1tF35XUQuuVozFLhYUCI 6uB2UsLn0mpNMQV2d04pycjdlycP0GTl2L/7tXBXgFCVZu2VKTBzrkcEPOVannpOtBka E87SwFxVnhQoHNiMrr2nAOJx30NB0XzMPjkZg= MIME-Version: 1.0 Received: by 10.227.206.78 with SMTP id ft14mr53942294wbb.24.1325641696044; Tue, 03 Jan 2012 17:48:16 -0800 (PST) Received: by 10.180.5.35 with HTTP; Tue, 3 Jan 2012 17:48:15 -0800 (PST) In-Reply-To: <20120103175607.GB10481@DataIX.net> References: <39A90A91-4FB3-4B52-A7D2-4E0349B78E6F@ultra-secure.de> <20120103175607.GB10481@DataIX.net> Date: Tue, 3 Jan 2012 20:48:15 -0500 Message-ID: From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: ZFS (Solaris 11 source 'leaked') 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, 04 Jan 2012 01:48:17 -0000 > Ethics are trouble for you arent they ? We all know well the history of BSD, the impact licensing has had with it, and where it needs to go. No one is suggesting crossing any ethical lines. Sure, some folks do sit too high atop their crystal towers by default. Thereby, and often to their detriment, failing to see all the different things (legitimate or not) available to them. Just as some folks dive too deep. Yes, I'd find it humorous if some anon decided to maintain their own public/private third party ZFS module, Solaris clone, or bugfix branch based on this. Is that a suggestion that anyone needing towers have anything to do with it, no [!], duh. It's just news, these aren't the droids you're looking for... :) From owner-freebsd-fs@FreeBSD.ORG Wed Jan 4 16:14: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 502101065676 for ; Wed, 4 Jan 2012 16:14:31 +0000 (UTC) (envelope-from Martin.Birgmeier@aon.at) Received: from email.aon.at (nat-warsl417-02.aon.at [195.3.96.120]) by mx1.freebsd.org (Postfix) with ESMTP id 8FF618FC08 for ; Wed, 4 Jan 2012 16:14:29 +0000 (UTC) Received: (qmail 20242 invoked from network); 4 Jan 2012 15:47:48 -0000 Received: from smarthub77.res.a1.net (HELO email.aon.at) ([172.18.1.205]) (envelope-sender ) by fallback43.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 4 Jan 2012 15:47:48 -0000 Received: (qmail 22643 invoked from network); 4 Jan 2012 15:47:45 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on WARSBL604.highway.telekom.at X-Spam-Level: Received: from 91-113-14-211.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([91.113.14.211]) (envelope-sender ) by smarthub77.res.a1.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 4 Jan 2012 15:47:45 -0000 Received: from mizar-v1.xyzzy (mizar-v1.xyzzy [192.168.1.51]) by gandalf.xyzzy (8.14.5/8.14.5) with ESMTP id q04FljPM024916 for ; Wed, 4 Jan 2012 16:47:45 +0100 (CET) (envelope-from Martin.Birgmeier@aon.at) Message-ID: <4F04749E.9020301@aon.at> Date: Wed, 04 Jan 2012 16:47:42 +0100 From: Martin Birgmeier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.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: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 04 Jan 2012 16:14:31 -0000 I'll be upgrading a server from 8.2 to 9.0 soon. On it, I currently have the following zpool: ---------- [0]# zpool status pool: hal.1 state: ONLINE status: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. action: Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. scrub: none requested config: NAME STATE READ WRITE CKSUM hal.1 ONLINE 0 0 0 raidz2 ONLINE 0 0 0 ad10p3 ONLINE 0 0 0 ad12p3 ONLINE 0 0 0 ad14p3 ONLINE 0 0 0 ad16p3 ONLINE 0 0 0 ad18p3 ONLINE 0 0 0 ad20p3 ONLINE 0 0 0 errors: No known data errors [0]# ---------- I would like to do two things: 1) Wire the ATA CAM disks such that ad10 -> ada0, ad12 -> ada1, etc. 2) Change the zpool to use the then newly available ada0p3, ada1p3, ..., ada5p3 gparts. Ultimately, I want to set sysctl kern.cam.ada.legacy_aliases=0. Please advise on how best to achieve this. Regards, Martin p.s. The following information relates to the current ata attachments: ---------- [0]# egrep 'ad[0-9]|ata[0-9]|atapci[0-9]' /var/run/dmesg.boot atapci0: port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f mem 0xfe8fe000-0xfe8fffff irq 18 at device 0.0 on pci3 atapci0: [ITHREAD] atapci1: on atapci0 atapci1: [ITHREAD] atapci1: AHCI v1.00 controller with 2 3Gbps ports, PM supported ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] atapci2: port 0xa000-0xa007,0x9000-0x9003,0x8000-0x8007,0x7000-0x7003,0x6000-0x600f mem 0xfe4ffc00-0xfe4fffff irq 19 at device 17.0 on pci0 atapci2: [ITHREAD] atapci2: AHCI v1.20 controller with 6 3Gbps ports, PM supported ata5: on atapci2 ata5: [ITHREAD] ata6: on atapci2 ata6: [ITHREAD] ata7: on atapci2 ata7: [ITHREAD] ata8: on atapci2 ata8: [ITHREAD] ata9: on atapci2 ata9: [ITHREAD] ata10: on atapci2 ata10: [ITHREAD] ad10: 1907729MB at ata5-master UDMA100 SATA 3Gb/s ad12: 1907729MB at ata6-master UDMA100 SATA 3Gb/s ad14: 1907729MB at ata7-master UDMA100 SATA 3Gb/s ad16: 1907729MB at ata8-master UDMA100 SATA 3Gb/s ad18: 1907729MB at ata9-master UDMA100 SATA 3Gb/s ad20: 1907729MB at ata10-master UDMA100 SATA 3Gb/s [0]# ---------- From owner-freebsd-fs@FreeBSD.ORG Wed Jan 4 17:23:53 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 6FD551065670 for ; Wed, 4 Jan 2012 17:23:53 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 57EB78FC17 for ; Wed, 4 Jan 2012 17:23:53 +0000 (UTC) Received: from omta18.emeryville.ca.mail.comcast.net ([76.96.30.74]) by qmta10.emeryville.ca.mail.comcast.net with comcast id HUqD1i0031bwxycAAVPmlu; Wed, 04 Jan 2012 17:23:46 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta18.emeryville.ca.mail.comcast.net with comcast id HW611i00o1t3BNj8eW61rD; Wed, 04 Jan 2012 18:06:02 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id DB918102C19; Wed, 4 Jan 2012 09:23:51 -0800 (PST) Date: Wed, 4 Jan 2012 09:23:51 -0800 From: Jeremy Chadwick To: Martin Birgmeier Message-ID: <20120104172351.GA42855@icarus.home.lan> References: <4F04749E.9020301@aon.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F04749E.9020301@aon.at> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 04 Jan 2012 17:23:53 -0000 On Wed, Jan 04, 2012 at 04:47:42PM +0100, Martin Birgmeier wrote: > I'll be upgrading a server from 8.2 to 9.0 soon. On it, I currently > have the following zpool: > > ---------- > [0]# zpool status > pool: hal.1 > state: ONLINE > status: The pool is formatted using an older on-disk format. The pool can > still be used, but some features are unavailable. > action: Upgrade the pool using 'zpool upgrade'. Once this is done, the > pool will no longer be accessible on older software versions. > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > hal.1 ONLINE 0 0 0 > raidz2 ONLINE 0 0 0 > ad10p3 ONLINE 0 0 0 > ad12p3 ONLINE 0 0 0 > ad14p3 ONLINE 0 0 0 > ad16p3 ONLINE 0 0 0 > ad18p3 ONLINE 0 0 0 > ad20p3 ONLINE 0 0 0 > > errors: No known data errors > [0]# > ---------- > > I would like to do two things: > > 1) Wire the ATA CAM disks such that ad10 -> ada0, ad12 -> ada1, etc. > > 2) Change the zpool to use the then newly available ada0p3, ada1p3, > ..., ada5p3 gparts. > > Ultimately, I want to set sysctl kern.cam.ada.legacy_aliases=0. > > Please advise on how best to achieve this. > > Regards, > > Martin > > p.s. The following information relates to the current ata attachments: > > ---------- > [0]# egrep 'ad[0-9]|ata[0-9]|atapci[0-9]' /var/run/dmesg.boot > atapci0: port > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f > mem 0xfe8fe000-0xfe8fffff irq 18 at device 0.0 on pci3 > atapci0: [ITHREAD] > atapci1: on atapci0 > atapci1: [ITHREAD] > atapci1: AHCI v1.00 controller with 2 3Gbps ports, PM supported > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > ata4: on atapci0 > ata4: [ITHREAD] > atapci2: port > 0xa000-0xa007,0x9000-0x9003,0x8000-0x8007,0x7000-0x7003,0x6000-0x600f > mem 0xfe4ffc00-0xfe4fffff irq 19 at device 17.0 on pci0 > atapci2: [ITHREAD] > atapci2: AHCI v1.20 controller with 6 3Gbps ports, PM supported > ata5: on atapci2 > ata5: [ITHREAD] > ata6: on atapci2 > ata6: [ITHREAD] > ata7: on atapci2 > ata7: [ITHREAD] > ata8: on atapci2 > ata8: [ITHREAD] > ata9: on atapci2 > ata9: [ITHREAD] > ata10: on atapci2 > ata10: [ITHREAD] > ad10: 1907729MB at ata5-master > UDMA100 SATA 3Gb/s > ad12: 1907729MB at ata6-master > UDMA100 SATA 3Gb/s > ad14: 1907729MB at ata7-master > UDMA100 SATA 3Gb/s > ad16: 1907729MB at ata8-master > UDMA100 SATA 3Gb/s > ad18: 1907729MB at ata9-master > UDMA100 SATA 3Gb/s > ad20: 1907729MB at ata10-master > UDMA100 SATA 3Gb/s > [0]# You can try doing this on 8.2 already, and always revert if need be. All you need to do is add ahci_load="yes" to /boot/loader.conf and see how things behave after that. This will make use of the AHCI-to-CAM translation layer (which is now default in 9.0). There isn't much you need to do with ZFS either: it should "taste" the disks and find them on boot. If it doesn't, try "zpool import", then when it shows the pool, do "zpool import {poolid}". It should automatically refer to everything as adaX going forward. No need to bother with kern.cam.ada.legacy_aliases. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Jan 4 20:40:28 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 75499106564A for ; Wed, 4 Jan 2012 20:40:28 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 2B5DE8FC12 for ; Wed, 4 Jan 2012 20:40:27 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC41BAE.dip.t-dialin.net [79.196.27.174]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 98EDF84400D; Wed, 4 Jan 2012 21:40:13 +0100 (CET) Received: from unknown (IO.Leidinger.net [192.168.1.12]) by outgoing.leidinger.net (Postfix) with ESMTP id C52471509; Wed, 4 Jan 2012 21:40:10 +0100 (CET) Date: Wed, 4 Jan 2012 21:40:09 +0100 From: Alexander Leidinger To: Dan Carroll Message-ID: <20120104214009.00004dbe@unknown> In-Reply-To: <4F039594.4080408@sputnik.net.au> References: <4F003EB8.6080006@dannysplace.net> <4F02FC42.1040103@dannysplace.net> <4F0311F2.7050209@brockmann-consult.de> <4F0312DF.8050004@brockmann-consult.de> <20120103162428.GA18661@icarus.home.lan> <20120103235108.GA25691@icarus.home.lan> <4F039594.4080408@sputnik.net.au> X-Mailer: Claws Mail 3.7.10cvs42 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 98EDF84400D.A2CF0 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.923, required 6, autolearn=disabled, ALL_TRUSTED -1.00, TW_ZF 0.08) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1326314414.65783@vyTaBwIRkVr5sbU713g3nQ X-EBL-Spam-Status: No Cc: freebsd-fs@freebsd.org Subject: Re: ZFS With Gpart partitions 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, 04 Jan 2012 20:40:28 -0000 On Wed, 04 Jan 2012 09:56:04 +1000 Dan Carroll wrote: > On 4/01/2012 9:51 AM, Jeremy Chadwick wrote: > > Agreed. The question is why FreeBSD isn't using those defaults in > > its installer. Furthermore, have you tried to actually accomplish > > this with gpart? I have. I got practically no where. The -a flag > > doesn't always do the right thing, and with the -b flag you have to > > "out-smart" internal calculations being made by the software > > itself. I also had to do the alignment offset at the filesystem > > level, and not at the actual slice level. E.g.: gpart create -s mbr > > adaX gpart add -t freebsd adaX gpart create -s bsd adaXs1 gpart add > > -b 4033 -s {size} -t freebsd-ufs adaXs1 I forget what the result > > was if I tried to use -b during the first "gpart add", but it kept > > coming out wrong or simply didn't work. > > In that case is there a "best practices" guide out there anywhere > describing how this should be done? There are several HOWTOs available. If you don't mind that it is with GPT and not MBR: http://www.leidinger.net/blog/2011/05/03/another-root-on-zfs-howto-optimized-for-4k-sector-drives/ Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 07:59: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 F0A331065673 for ; Thu, 5 Jan 2012 07:59:43 +0000 (UTC) (envelope-from Martin.Birgmeier@aon.at) Received: from email.aon.at (smtpout05.highway.telekom.at [195.3.96.77]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0108FC18 for ; Thu, 5 Jan 2012 07:59:41 +0000 (UTC) Received: (qmail 28567 invoked from network); 5 Jan 2012 07:59:40 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on WARSBL607.highway.telekom.at X-Spam-Level: Received: from 188-23-41-23.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([188.23.41.23]) (envelope-sender ) by smarthub83.res.a1.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 Jan 2012 07:59:39 -0000 Received: from mizar-v1.xyzzy (mizar-v1.xyzzy [192.168.1.51]) by gandalf.xyzzy (8.14.5/8.14.5) with ESMTP id q057xdMu004742 for ; Thu, 5 Jan 2012 08:59:39 +0100 (CET) (envelope-from Martin.Birgmeier@aon.at) Message-ID: <4F05586B.9060109@aon.at> Date: Thu, 05 Jan 2012 08:59:39 +0100 From: Martin Birgmeier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> In-Reply-To: <20120104172351.GA42855@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 05 Jan 2012 07:59:44 -0000 On 01/04/12 18:23, Jeremy Chadwick wrote: > On Wed, Jan 04, 2012 at 04:47:42PM +0100, Martin Birgmeier wrote: >> I'll be upgrading a server from 8.2 to 9.0 soon. On it, I currently >> have the following zpool: >> >> ---------- >> [0]# zpool status >> pool: hal.1 >> state: ONLINE >> status: The pool is formatted using an older on-disk format. The pool can >> still be used, but some features are unavailable. >> action: Upgrade the pool using 'zpool upgrade'. Once this is done, the >> pool will no longer be accessible on older software versions. >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> hal.1 ONLINE 0 0 0 >> raidz2 ONLINE 0 0 0 >> ad10p3 ONLINE 0 0 0 >> ad12p3 ONLINE 0 0 0 >> ad14p3 ONLINE 0 0 0 >> ad16p3 ONLINE 0 0 0 >> ad18p3 ONLINE 0 0 0 >> ad20p3 ONLINE 0 0 0 >> >> errors: No known data errors >> [0]# >> ---------- >> >> I would like to do two things: >> >> 1) Wire the ATA CAM disks such that ad10 -> ada0, ad12 -> ada1, etc. >> >> 2) Change the zpool to use the then newly available ada0p3, ada1p3, >> ..., ada5p3 gparts. >> >> Ultimately, I want to set sysctl kern.cam.ada.legacy_aliases=0. >> >> Please advise on how best to achieve this. >> >> Regards, >> >> Martin >> >> p.s. The following information relates to the current ata attachments: >> >> ---------- >> [0]# egrep 'ad[0-9]|ata[0-9]|atapci[0-9]' /var/run/dmesg.boot >> atapci0: port >> 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f >> mem 0xfe8fe000-0xfe8fffff irq 18 at device 0.0 on pci3 >> atapci0: [ITHREAD] >> atapci1: on atapci0 >> atapci1: [ITHREAD] >> atapci1: AHCI v1.00 controller with 2 3Gbps ports, PM supported >> ata2: on atapci1 >> ata2: [ITHREAD] >> ata3: on atapci1 >> ata3: [ITHREAD] >> ata4: on atapci0 >> ata4: [ITHREAD] >> atapci2: port >> 0xa000-0xa007,0x9000-0x9003,0x8000-0x8007,0x7000-0x7003,0x6000-0x600f >> mem 0xfe4ffc00-0xfe4fffff irq 19 at device 17.0 on pci0 >> atapci2: [ITHREAD] >> atapci2: AHCI v1.20 controller with 6 3Gbps ports, PM supported >> ata5: on atapci2 >> ata5: [ITHREAD] >> ata6: on atapci2 >> ata6: [ITHREAD] >> ata7: on atapci2 >> ata7: [ITHREAD] >> ata8: on atapci2 >> ata8: [ITHREAD] >> ata9: on atapci2 >> ata9: [ITHREAD] >> ata10: on atapci2 >> ata10: [ITHREAD] >> ad10: 1907729MB at ata5-master >> UDMA100 SATA 3Gb/s >> ad12: 1907729MB at ata6-master >> UDMA100 SATA 3Gb/s >> ad14: 1907729MB at ata7-master >> UDMA100 SATA 3Gb/s >> ad16: 1907729MB at ata8-master >> UDMA100 SATA 3Gb/s >> ad18: 1907729MB at ata9-master >> UDMA100 SATA 3Gb/s >> ad20: 1907729MB at ata10-master >> UDMA100 SATA 3Gb/s >> [0]# > You can try doing this on 8.2 already, and always revert if need be. > All you need to do is add ahci_load="yes" to /boot/loader.conf and see > how things behave after that. This will make use of the AHCI-to-CAM > translation layer (which is now default in 9.0). > > There isn't much you need to do with ZFS either: it should "taste" > the disks and find them on boot. If it doesn't, try "zpool import", > then when it shows the pool, do "zpool import {poolid}". > > It should automatically refer to everything as adaX going forward. > > No need to bother with kern.cam.ada.legacy_aliases. > Thank you for this explanation. I understand that many improvements to zfs have gone into the code after 8.2.0; therefore, I am very careful not doing any "exotic" things with this server, as it is a production system and I do not want to lose data. (Note: Single and double failures are supposedly covered by using raidz2, and history is preserved by using snapshots, so I have no further backups on tapes or other disks. Thus, theoretically, all backup cases except for disaster are covered, and regarding that I currently count on the probability of floods, fire, burglary, and Russian Mars probes falling on my house as being sufficiently low, whereas I am not that confident regarding software disasters.) To make it short, I do not want to experiment, but just to apply a tried and true procedure for getting my pool to operate flawlessly under 9.0. Remark: My root partition is a UFS. In 9.0, if I keep kern.cam.ada.legacy_aliases=1, there will be two paths to each device, one through adX, the other through adaX. Which one will zfs use, and show with 'zpool status'? Also, I understand that I will have to wire down the various ATA CAMs to obtain the old numbering. How can I do this? Again, which path would zfs use if I did not wire down the ATA CAMs? Will I have half of my devices go through adX and the other through adaX, or will zfs even believe that it has a multipath connectivity to each device? Regards, Martin From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 08:21: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 4C3DC106564A for ; Thu, 5 Jan 2012 08:21:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 08E9A8FC13 for ; Thu, 5 Jan 2012 08:21:57 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so356010vcb.13 for ; Thu, 05 Jan 2012 00:21:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=NnUQm+so8EsZCtaRNLd0CSQelC9+kFIQk6Xgde9em1w=; b=dM9coviIXtFZFHyY3f09uWHj93jSfTLn5H25GtlcgIOEzbPsvzMyvqwmV2XwoOVZ/z rLHPo1Uam6hzw1+VTcPCRV3rzzn82fTYq6dzsqxh1l2SrV5IDymjSXEiZ9GSI1BjsjfE p0TAvXSKuPADOAQOAGX1SAo4ybFL0Je59/DEw= MIME-Version: 1.0 Received: by 10.52.33.99 with SMTP id q3mr381210vdi.100.1325750264895; Wed, 04 Jan 2012 23:57:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Wed, 4 Jan 2012 23:57:44 -0800 (PST) Date: Wed, 4 Jan 2012 23:57:44 -0800 X-Google-Sender-Auth: deumgNbsHau7Q5Qgx30ieF70xUA Message-ID: From: Adrian Chadd To: freebsd-arch@freebsd.org, freebsd-current , freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Is it possible to make subr_acl_nfs4 and subr_acl_posix1e disabled? 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, 05 Jan 2012 08:21:58 -0000 Hi, I'm trying to slim down the freebsd kernel to fit on some devices with 4MB of flash. Since I'm not using NFS or UFS_ACL, I wondered if that code required. It turns out I can just build a kernel with those two disabled. Would it be possible to remove them from "standard" and make them optional? Or is there a reason to keep it in base? If so (eg so things can be kldload'ed that uses the ACL code) can we make it a build-time option, and/or a pair of loadable kernel modules? Thanks, Adrian From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 09:19:00 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 48E31106566C for ; Thu, 5 Jan 2012 09:19:00 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 008EF8FC12 for ; Thu, 5 Jan 2012 09:18:59 +0000 (UTC) Received: by yhfq46 with SMTP id q46so41376yhf.13 for ; Thu, 05 Jan 2012 01:18:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WA9oUARlPirabOs6rlKhwUgLiO1vKlNVZzwlsJHUL+Y=; b=hxQ1rnB0cxls8cXWtZVmgpygNXx50quGkhncszaZmBN3/lbJB3MyLLhc2jyuKMUQZF zJFMxWJzKpQ7BWGc4bxvvTOA7Bsms2H4U3D2VpzWrHo2wWnsIHGlf1EHrHjmVpiaQK1k HUnINT0w0/0JV7AomozgHUCeGfjUWmPYnckqs= MIME-Version: 1.0 Received: by 10.236.78.193 with SMTP id g41mr491038yhe.25.1325755139273; Thu, 05 Jan 2012 01:18:59 -0800 (PST) Received: by 10.236.139.193 with HTTP; Thu, 5 Jan 2012 01:18:59 -0800 (PST) In-Reply-To: <4F05586B.9060109@aon.at> References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> Date: Thu, 5 Jan 2012 09:18:59 +0000 Message-ID: From: krad To: Martin Birgmeier Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 05 Jan 2012 09:19:00 -0000 On 5 January 2012 07:59, Martin Birgmeier wrote: > On 01/04/12 18:23, Jeremy Chadwick wrote: > >> On Wed, Jan 04, 2012 at 04:47:42PM +0100, Martin Birgmeier wrote: >> >>> I'll be upgrading a server from 8.2 to 9.0 soon. On it, I currently >>> have the following zpool: >>> >>> ---------- >>> [0]# zpool status >>> pool: hal.1 >>> state: ONLINE >>> status: The pool is formatted using an older on-disk format. The pool >>> can >>> still be used, but some features are unavailable. >>> action: Upgrade the pool using 'zpool upgrade'. Once this is done, the >>> pool will no longer be accessible on older software versions. >>> scrub: none requested >>> config: >>> >>> NAME STATE READ WRITE CKSUM >>> hal.1 ONLINE 0 0 0 >>> raidz2 ONLINE 0 0 0 >>> ad10p3 ONLINE 0 0 0 >>> ad12p3 ONLINE 0 0 0 >>> ad14p3 ONLINE 0 0 0 >>> ad16p3 ONLINE 0 0 0 >>> ad18p3 ONLINE 0 0 0 >>> ad20p3 ONLINE 0 0 0 >>> >>> errors: No known data errors >>> [0]# >>> ---------- >>> >>> I would like to do two things: >>> >>> 1) Wire the ATA CAM disks such that ad10 -> ada0, ad12 -> ada1, etc. >>> >>> 2) Change the zpool to use the then newly available ada0p3, ada1p3, >>> ..., ada5p3 gparts. >>> >>> Ultimately, I want to set sysctl kern.cam.ada.legacy_aliases=0. >>> >>> Please advise on how best to achieve this. >>> >>> Regards, >>> >>> Martin >>> >>> p.s. The following information relates to the current ata attachments: >>> >>> ---------- >>> [0]# egrep 'ad[0-9]|ata[0-9]|atapci[0-9]' /var/run/dmesg.boot >>> atapci0: port >>> 0xcc00-0xcc07,0xc880-0xc883,**0xc800-0xc807,0xc480-0xc483,** >>> 0xc400-0xc40f >>> mem 0xfe8fe000-0xfe8fffff irq 18 at device 0.0 on pci3 >>> atapci0: [ITHREAD] >>> atapci1: on atapci0 >>> atapci1: [ITHREAD] >>> atapci1: AHCI v1.00 controller with 2 3Gbps ports, PM supported >>> ata2: on atapci1 >>> ata2: [ITHREAD] >>> ata3: on atapci1 >>> ata3: [ITHREAD] >>> ata4: on atapci0 >>> ata4: [ITHREAD] >>> atapci2: port >>> 0xa000-0xa007,0x9000-0x9003,**0x8000-0x8007,0x7000-0x7003,** >>> 0x6000-0x600f >>> mem 0xfe4ffc00-0xfe4fffff irq 19 at device 17.0 on pci0 >>> atapci2: [ITHREAD] >>> atapci2: AHCI v1.20 controller with 6 3Gbps ports, PM supported >>> ata5: on atapci2 >>> ata5: [ITHREAD] >>> ata6: on atapci2 >>> ata6: [ITHREAD] >>> ata7: on atapci2 >>> ata7: [ITHREAD] >>> ata8: on atapci2 >>> ata8: [ITHREAD] >>> ata9: on atapci2 >>> ata9: [ITHREAD] >>> ata10: on atapci2 >>> ata10: [ITHREAD] >>> ad10: 1907729MB at ata5-master >>> UDMA100 SATA 3Gb/s >>> ad12: 1907729MB at ata6-master >>> UDMA100 SATA 3Gb/s >>> ad14: 1907729MB at ata7-master >>> UDMA100 SATA 3Gb/s >>> ad16: 1907729MB at ata8-master >>> UDMA100 SATA 3Gb/s >>> ad18: 1907729MB at ata9-master >>> UDMA100 SATA 3Gb/s >>> ad20: 1907729MB at ata10-master >>> UDMA100 SATA 3Gb/s >>> [0]# >>> >> You can try doing this on 8.2 already, and always revert if need be. >> All you need to do is add ahci_load="yes" to /boot/loader.conf and see >> how things behave after that. This will make use of the AHCI-to-CAM >> translation layer (which is now default in 9.0). >> >> There isn't much you need to do with ZFS either: it should "taste" >> the disks and find them on boot. If it doesn't, try "zpool import", >> then when it shows the pool, do "zpool import {poolid}". >> >> It should automatically refer to everything as adaX going forward. >> >> No need to bother with kern.cam.ada.legacy_aliases. >> >> Thank you for this explanation. > > I understand that many improvements to zfs have gone into the code after > 8.2.0; therefore, I am very careful not doing any "exotic" things with this > server, as it is a production system and I do not want to lose data. (Note: > Single and double failures are supposedly covered by using raidz2, and > history is preserved by using snapshots, so I have no further backups on > tapes or other disks. Thus, theoretically, all backup cases except for > disaster are covered, and regarding that I currently count on the > probability of floods, fire, burglary, and Russian Mars probes falling on > my house as being sufficiently low, whereas I am not that confident > regarding software disasters.) To make it short, I do not want to > experiment, but just to apply a tried and true procedure for getting my > pool to operate flawlessly under 9.0. > > Remark: My root partition is a UFS. > > In 9.0, if I keep kern.cam.ada.legacy_aliases=1, there will be two paths > to each device, one through adX, the other through adaX. Which one will zfs > use, and show with 'zpool status'? > > Also, I understand that I will have to wire down the various ATA CAMs to > obtain the old numbering. How can I do this? Again, which path would zfs > use if I did not wire down the ATA CAMs? Will I have half of my devices go > through adX and the other through adaX, or will zfs even believe that it > has a multipath connectivity to each device? > > Regards, > > Martin > > > ______________________________**_________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@**freebsd.org > " > i have upgraded a few of my systems to 9 and they seamlessly went from adX to adaX without any intervention. I am however pure zfs, and its the ufs bit of your system thats likely to be the issue here. Best thing to do if its remote is to make sure you get out of band access (ilom etc) or have a decent set of remote hands. Then if anything goes wrong on the flip over to the new os its not to much of an issue to fix. You should probably consider implementing some form of labeling while you have the down time arranged as if you were doing this rather than using device names you wouldnt have this problem. I livecd/usb would be useful for setting that up From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 09:35:44 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 B6CA9106564A for ; Thu, 5 Jan 2012 09:35:44 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 43A638FC17 for ; Thu, 5 Jan 2012 09:35:43 +0000 (UTC) Received: by wibhr1 with SMTP id hr1so312838wib.13 for ; Thu, 05 Jan 2012 01:35:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=gkroaI4Yg51JPgE7ZMmZ5B+cu53iL3NsmWLjj6eBBEc=; b=g1GfQGBDMZRiYPtqm+1atMcKTv5dw0wmiljChfN0YITyNTqcH0978goZ+Tk1w9AVsq OorqnvpHqZDLYvliYTk3HNNfc8zLLb7KG4WCobW2JAm6hYDp65L8UYHs7cAFOmU65skk C/TH8/aA8jQXu21fYrlcX8aikXORYpjBT+Fsk= Received: by 10.180.19.42 with SMTP id b10mr325508wie.13.1325756142225; Thu, 05 Jan 2012 01:35:42 -0800 (PST) Received: from green.tandem.local (utwig.xim.bz. [91.216.237.46]) by mx.google.com with ESMTPS id q5sm14772945wbo.8.2012.01.05.01.35.40 (version=SSLv3 cipher=OTHER); Thu, 05 Jan 2012 01:35:40 -0800 (PST) Message-ID: <4F056EEB.3050902@gmail.com> Date: Thu, 05 Jan 2012 11:35:39 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111223 Thunderbird/9.0 MIME-Version: 1.0 To: Martin Birgmeier References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> In-Reply-To: <4F05586B.9060109@aon.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 05 Jan 2012 09:35:44 -0000 05.01.2012 09:59, Martin Birgmeier wrote: > In 9.0, if I keep kern.cam.ada.legacy_aliases=1, there will be two paths > to each device, one through adX, the other through adaX. Which one will > zfs use, and show with 'zpool status'? You are partially incorrect here: [torn] ~> ls -la /dev | grep ad lrwxr-xr-x 1 root wheel 4 5 jan 08:22 ad6@ -> ada0 lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6a@ -> ada0a lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6b@ -> ada0b lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6d@ -> ada0d lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6e@ -> ada0e lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6f@ -> ada0f lrwxr-xr-x 1 root wheel 13 5 jan 08:22 ad6f.journal@ -> ada0f.journal crw-r----- 1 root operator 0, 64 5 jan 08:22 ada0 crw-r----- 1 root operator 0, 66 5 jan 08:23 ada0a crw-r----- 1 root operator 0, 68 5 jan 08:22 ada0b crw-r----- 1 root operator 0, 70 5 jan 08:23 ada0d crw-r----- 1 root operator 0, 72 5 jan 08:23 ada0e crw-r----- 1 root operator 0, 74 5 jan 08:22 ada0f crw-r----- 1 root operator 0, 79 5 jan 08:23 ada0f.journal > Also, I understand that I will have to wire down the various ATA CAMs to > obtain the old numbering. How can I do this? Again, which path would zfs > use if I did not wire down the ATA CAMs? Will I have half of my devices > go through adX and the other through adaX, or will zfs even believe that > it has a multipath connectivity to each device? Not at all, ad6 would be a symlink to correct ada device, I haven't yet changed the fstab on this machine and it reads: # Device Mountpoint FStype Options Dump Pass# /dev/ad6b none swap sw 0 0 /dev/ad6a / ufs rw 1 1 /dev/ad6e /tmp ufs rw 2 2 /dev/ad6f.journal /usr ufs rw,async 2 2 /dev/ad6d /var ufs rw 2 2 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 10:50:35 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 12E0E106567E for ; Thu, 5 Jan 2012 10:50:35 +0000 (UTC) (envelope-from Martin.Birgmeier@aon.at) Received: from email.aon.at (smtpout04.highway.telekom.at [195.3.96.117]) by mx1.freebsd.org (Postfix) with ESMTP id 526DF8FC18 for ; Thu, 5 Jan 2012 10:50:33 +0000 (UTC) Received: (qmail 21398 invoked from network); 5 Jan 2012 10:50:30 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on WARSBL507.highway.telekom.at X-Spam-Level: Received: from 188-23-41-23.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([188.23.41.23]) (envelope-sender ) by smarthub82.res.a1.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 Jan 2012 10:50:30 -0000 Received: from mizar-v1.xyzzy (mizar-v1.xyzzy [192.168.1.51]) by gandalf.xyzzy (8.14.5/8.14.5) with ESMTP id q05AoTAK013038 for ; Thu, 5 Jan 2012 11:50:30 +0100 (CET) (envelope-from Martin.Birgmeier@aon.at) Message-ID: <4F058075.1020108@aon.at> Date: Thu, 05 Jan 2012 11:50:29 +0100 From: Martin Birgmeier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> <4F056EEB.3050902@gmail.com> In-Reply-To: <4F056EEB.3050902@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 05 Jan 2012 10:50:35 -0000 On 01/05/12 10:35, Volodymyr Kostyrko wrote: > 05.01.2012 09:59, Martin Birgmeier wrote: >> In 9.0, if I keep kern.cam.ada.legacy_aliases=1, there will be two paths >> to each device, one through adX, the other through adaX. Which one will >> zfs use, and show with 'zpool status'? > > You are partially incorrect here: > [torn] ~> ls -la /dev | grep ad > lrwxr-xr-x 1 root wheel 4 5 jan 08:22 ad6@ -> ada0 > lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6a@ -> ada0a > lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6b@ -> ada0b > lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6d@ -> ada0d > lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6e@ -> ada0e > lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6f@ -> ada0f > lrwxr-xr-x 1 root wheel 13 5 jan 08:22 ad6f.journal@ -> > ada0f.journal > crw-r----- 1 root operator 0, 64 5 jan 08:22 ada0 > crw-r----- 1 root operator 0, 66 5 jan 08:23 ada0a > crw-r----- 1 root operator 0, 68 5 jan 08:22 ada0b > crw-r----- 1 root operator 0, 70 5 jan 08:23 ada0d > crw-r----- 1 root operator 0, 72 5 jan 08:23 ada0e > crw-r----- 1 root operator 0, 74 5 jan 08:22 ada0f > crw-r----- 1 root operator 0, 79 5 jan 08:23 ada0f.journal > >> Also, I understand that I will have to wire down the various ATA CAMs to >> obtain the old numbering. How can I do this? Again, which path would zfs >> use if I did not wire down the ATA CAMs? Will I have half of my devices >> go through adX and the other through adaX, or will zfs even believe that >> it has a multipath connectivity to each device? > > Not at all, ad6 would be a symlink to correct ada device, I haven't > yet changed the fstab on this machine and it reads: > > # Device Mountpoint FStype Options Dump > Pass# > /dev/ad6b none swap sw 0 0 > /dev/ad6a / ufs rw 1 1 > /dev/ad6e /tmp ufs rw 2 2 > /dev/ad6f.journal /usr ufs rw,async > 2 2 > /dev/ad6d /var ufs rw 2 2 > /dev/cd0 /cdrom cd9660 ro,noauto 0 0 > Sigh... I get only half the answers, and these are not so helpful either. First of all, I *am* correct in saying that there are two paths to the same device, because the purpose of a (sym-)link precisely is to have an alternate path to the same object in the filesystem. So if someone tells me that zfs somehow (how?) excludes devices reached through symlinks, *that* would be an information I would find useful. Second, the whole purpose of the kern.cam.ada.legacy_aliases is to have backwards compatibility for fstab etc by installing symlinks in /dev. I know this very well but want to prepare for the day when I want to get rid of the necessity for this compatibility. Third, I have now asked twice how to wire the ATA CAM devices, without anybody even referring to that question. Well, I guess I'll have to find that out myself. I do appreciate all answers, even more so as I perfectly understand they are *free* answers, and maybe the above is even helpful to someone else (and does not confuse them instead), but I'd appreciate it even more if they were real answers. Regards, Martin From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 10:59:17 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 5475C1065672; Thu, 5 Jan 2012 10:59:17 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 0D9578FC14; Thu, 5 Jan 2012 10:59:16 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 1054F62A0; Thu, 5 Jan 2012 10:39:41 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id E408B8CB8; Thu, 5 Jan 2012 11:39:40 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Adrian Chadd References: Date: Thu, 05 Jan 2012 11:39:40 +0100 In-Reply-To: (Adrian Chadd's message of "Wed, 4 Jan 2012 23:57:44 -0800") Message-ID: <86ty4a8mc3.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-current , freebsd-arch@freebsd.org Subject: Re: Is it possible to make subr_acl_nfs4 and subr_acl_posix1e disabled? 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, 05 Jan 2012 10:59:17 -0000 Adrian Chadd writes: > Since I'm not using NFS or UFS_ACL, I wondered if that code required. > It turns out I can just build a kernel with those two disabled. > > Would it be possible to remove them from "standard" and make them > optional? Or is there a reason to keep it in base? I would be very annoyed if it were no longer possible to netboot GENERIC... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 12:10: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 05876106567C for ; Thu, 5 Jan 2012 12:10:38 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 7C5658FC0C for ; Thu, 5 Jan 2012 12:10:37 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8283E28429; Thu, 5 Jan 2012 12:55:14 +0100 (CET) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 56C1528428; Thu, 5 Jan 2012 12:55:13 +0100 (CET) Message-ID: <4F058FA0.7070301@quip.cz> Date: Thu, 05 Jan 2012 12:55:12 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Martin Birgmeier References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> <4F056EEB.3050902@gmail.com> <4F058075.1020108@aon.at> In-Reply-To: <4F058075.1020108@aon.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 05 Jan 2012 12:10:38 -0000 Martin Birgmeier wrote: > On 01/05/12 10:35, Volodymyr Kostyrko wrote: >> 05.01.2012 09:59, Martin Birgmeier wrote: >>> In 9.0, if I keep kern.cam.ada.legacy_aliases=1, there will be two paths >>> to each device, one through adX, the other through adaX. Which one will >>> zfs use, and show with 'zpool status'? >> >> You are partially incorrect here: >> [torn] ~> ls -la /dev | grep ad >> lrwxr-xr-x 1 root wheel 4 5 jan 08:22 ad6@ -> ada0 >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6a@ -> ada0a >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6b@ -> ada0b >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6d@ -> ada0d >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6e@ -> ada0e >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6f@ -> ada0f >> lrwxr-xr-x 1 root wheel 13 5 jan 08:22 ad6f.journal@ -> ada0f.journal >> crw-r----- 1 root operator 0, 64 5 jan 08:22 ada0 >> crw-r----- 1 root operator 0, 66 5 jan 08:23 ada0a >> crw-r----- 1 root operator 0, 68 5 jan 08:22 ada0b >> crw-r----- 1 root operator 0, 70 5 jan 08:23 ada0d >> crw-r----- 1 root operator 0, 72 5 jan 08:23 ada0e >> crw-r----- 1 root operator 0, 74 5 jan 08:22 ada0f >> crw-r----- 1 root operator 0, 79 5 jan 08:23 ada0f.journal >> >>> Also, I understand that I will have to wire down the various ATA CAMs to >>> obtain the old numbering. How can I do this? Again, which path would zfs >>> use if I did not wire down the ATA CAMs? Will I have half of my devices >>> go through adX and the other through adaX, or will zfs even believe that >>> it has a multipath connectivity to each device? >> >> Not at all, ad6 would be a symlink to correct ada device, I haven't >> yet changed the fstab on this machine and it reads: >> >> # Device Mountpoint FStype Options Dump Pass# >> /dev/ad6b none swap sw 0 0 >> /dev/ad6a / ufs rw 1 1 >> /dev/ad6e /tmp ufs rw 2 2 >> /dev/ad6f.journal /usr ufs rw,async 2 2 >> /dev/ad6d /var ufs rw 2 2 >> /dev/cd0 /cdrom cd9660 ro,noauto 0 0 >> > Sigh... I get only half the answers, and these are not so helpful either. > > First of all, I *am* correct in saying that there are two paths to the > same device, because the purpose of a (sym-)link precisely is to have an > alternate path to the same object in the filesystem. So if someone tells > me that zfs somehow (how?) excludes devices reached through symlinks, > *that* would be an information I would find useful. > > Second, the whole purpose of the kern.cam.ada.legacy_aliases is to have > backwards compatibility for fstab etc by installing symlinks in /dev. I > know this very well but want to prepare for the day when I want to get > rid of the necessity for this compatibility. > > Third, I have now asked twice how to wire the ATA CAM devices, without > anybody even referring to that question. Well, I guess I'll have to find > that out myself. > > I do appreciate all answers, even more so as I perfectly understand they > are *free* answers, and maybe the above is even helpful to someone else > (and does not confuse them instead), but I'd appreciate it even more if > they were real answers. ZFS taste available devices on boot, find ondisk stored metadata and additionally useses informations stored in /boot/zfs/zpool.cache "ad" to "ada" transition is not the only case where one disk device is accessible by multiple ways. On one of my servers with SAS drives, the ZFS partitions can be accessed by /dev/daXsY or /dev/gpt/ or /dev/gptid/ It works correctly without any confusions. If you will delete zpool.cache and then export / import pool, the member devices will be named as "first tasted". So if you will disable symlinks to "ad" device names, your zpool will be correctly loaded with new device names. ZFS is smart enough to not depend on device names and order. You can safely change order of cables / devices on controller and ZFS will start without any problem. So the problem with "ad" to "ada" transition on ZFS is rather cosmetic (device names shown in zpool status output) but it will work with whatever names. You just need to fix UFS / fstab issues. Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 12:20: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 E9F811065677 for ; Thu, 5 Jan 2012 12:20:29 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 75D278FC16 for ; Thu, 5 Jan 2012 12:20:28 +0000 (UTC) Received: by werb13 with SMTP id b13so451819wer.13 for ; Thu, 05 Jan 2012 04:20:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9QPqALdk2b47sZuUzkbZzN70bB4M4lCz0l/uYNUKKhE=; b=tup4OjMMmbnG8F+HEMVetaEosTcG4/nlJOyDSfQPhYqb7215VRStvTd780SFyNRijO lj23o3Wq9uNzayH2SdCZY7UTS7XWameuMQL/gqjppNp7PYTg+q7GxkTAwS8DR74G7N1F Jdd3Pf9P6uyjP6kzPAagjTs8smDzBxCiGFUGw= Received: by 10.216.132.82 with SMTP id n60mr1184580wei.1.1325766027526; Thu, 05 Jan 2012 04:20:27 -0800 (PST) Received: from green.tandem.local (utwig.xim.bz. [91.216.237.46]) by mx.google.com with ESMTPS id r1sm277451wia.8.2012.01.05.04.20.25 (version=SSLv3 cipher=OTHER); Thu, 05 Jan 2012 04:20:26 -0800 (PST) Message-ID: <4F059588.7080804@gmail.com> Date: Thu, 05 Jan 2012 14:20:24 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111223 Thunderbird/9.0 MIME-Version: 1.0 To: Martin Birgmeier References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> <4F056EEB.3050902@gmail.com> <4F058075.1020108@aon.at> In-Reply-To: <4F058075.1020108@aon.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 05 Jan 2012 12:20:30 -0000 05.01.2012 12:50, Martin Birgmeier wrote: > First of all, I *am* correct in saying that there are two paths to the > same device, because the purpose of a (sym-)link precisely is to have an > alternate path to the same object in the filesystem. So if someone tells > me that zfs somehow (how?) excludes devices reached through symlinks, > *that* would be an information I would find useful. Device once opened is locked until closed so noone can reuse such device. And ZFS searches only GEOM providers and is totally unaware about symlinks. > Second, the whole purpose of the kern.cam.ada.legacy_aliases is to have > backwards compatibility for fstab etc by installing symlinks in /dev. I > know this very well but want to prepare for the day when I want to get > rid of the necessity for this compatibility. You can always use other ways of mounting partitions. If you set a label on each drive you can use /dev/ufs/label instead of /dev/ad6a. You can also use gpart to partition the drive and stick to guids. This way moving disk around doesn't require a change in fstab. ZFS already tastes disks before mounting so moving disks around wouldn't full it. Another good way is what DragonFlyBSD implements: each device gets it's own unique device node based on disk serial id. > Third, I have now asked twice how to wire the ATA CAM devices, without > anybody even referring to that question. Well, I guess I'll have to find > that out myself. No such option like static device numbering for ATA_CAM I guess. They will get numbers in order of arrival. > I do appreciate all answers, even more so as I perfectly understand they > are *free* answers, and maybe the above is even helpful to someone else > (and does not confuse them instead), but I'd appreciate it even more if > they were real answers. Not only. The answers are mostly *free* and *fast* because anyone can say what he have tried to do but most time would abstain from perusing sources and commit messages. If you are lazy about that why can't we be the same? :) -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 13:48:20 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 70C54106564A; Thu, 5 Jan 2012 13:48:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 42C138FC12; Thu, 5 Jan 2012 13:48:20 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id EE7FC46B0D; Thu, 5 Jan 2012 08:48:19 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 78918B971; Thu, 5 Jan 2012 08:48:19 -0500 (EST) From: John Baldwin To: freebsd-arch@freebsd.org Date: Thu, 5 Jan 2012 08:48:18 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201050848.18414.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 05 Jan 2012 08:48:19 -0500 (EST) Cc: freebsd-fs@freebsd.org, Adrian Chadd , freebsd-current Subject: Re: Is it possible to make subr_acl_nfs4 and subr_acl_posix1e disabled? 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, 05 Jan 2012 13:48:20 -0000 [ A bit excessive on the cross-posting? arch@ alone was probably fine ] On Thursday, January 05, 2012 2:57:44 am Adrian Chadd wrote: > Hi, > > I'm trying to slim down the freebsd kernel to fit on some devices with > 4MB of flash. > > Since I'm not using NFS or UFS_ACL, I wondered if that code required. > It turns out I can just build a kernel with those two disabled. > > Would it be possible to remove them from "standard" and make them > optional? Or is there a reason to keep it in base? > If so (eg so things can be kldload'ed that uses the ACL code) can we > make it a build-time option, and/or a pair of loadable kernel modules? NFS doesn't actually use them curently, only UFS and ZFS do. Unfortunately we've yet to make it possible to compile ZFS into the kernel, so you can't make the sys/conf/files bits completely accurate yet (it would be nice to let folks who don't need FFS for a ZFS-only system remove FFS and UFS, but this would break that): Index: files =================================================================== --- files (revision 229491) +++ files (working copy) @@ -2393,8 +2393,9 @@ kern/sched_ule.c optional sched_ule kern/serdev_if.m standard kern/stack_protector.c standard \ compile-with "${NORMAL_C:N-fstack-protector*}" -kern/subr_acl_nfs4.c standard -kern/subr_acl_posix1e.c standard +# XXX: subr_acl_nfs4.c is also used by ZFS +kern/subr_acl_nfs4.c optional ufs_acl +kern/subr_acl_posix1e.c optional ufs_acl kern/subr_autoconf.c standard kern/subr_blist.c standard kern/subr_bus.c standard -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 18:29: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 2E6151065672 for ; Thu, 5 Jan 2012 18:29:49 +0000 (UTC) (envelope-from boydjd@jbip.net) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id B97828FC14 for ; Thu, 5 Jan 2012 18:29:48 +0000 (UTC) Received: by eaaf13 with SMTP id f13so815821eaa.13 for ; Thu, 05 Jan 2012 10:29:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jbip.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=f0jy0k+40itpQI8o79kzI+aj1ooB+Oo1R7eMiY/X+qM=; b=IMqmSyKZZRaKR2oCIxoTDt69IG/PhvvPP6KKSqo3H/dEcPZbxukWF/qNMzjdLsMhLp YMLWgp8YebrTzj7uhlcp5Xpgwm6UgTCnHBYyNPS10wGrMgCXp5o2+Nt4GwamL+vMMUEG S/MXX7v2dqOZ1dwt+zR1LvJWPX7DFr/Hubl8o= Received: by 10.205.127.65 with SMTP id gz1mr1341863bkc.12.1325788187468; Thu, 05 Jan 2012 10:29:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.228.135 with HTTP; Thu, 5 Jan 2012 10:29:24 -0800 (PST) In-Reply-To: <4F058075.1020108@aon.at> References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> <4F056EEB.3050902@gmail.com> <4F058075.1020108@aon.at> From: Joshua Boyd Date: Thu, 5 Jan 2012 13:29:24 -0500 Message-ID: To: Martin Birgmeier Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 05 Jan 2012 18:29:49 -0000 On Thu, Jan 5, 2012 at 5:50 AM, Martin Birgmeier wrote: > Third, I have now asked twice how to wire the ATA CAM devices, without > anybody even referring to that question. Well, I guess I'll have to find > that out myself. > http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html -- Joshua Boyd E-mail: boydjd@jbip.net http://www.jbip.net From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 18:31: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 5A8AD1065670; Thu, 5 Jan 2012 18:31:41 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [IPv6:2a01:4f8:141:52a3:186::]) by mx1.freebsd.org (Postfix) with ESMTP id E2C558FC1B; Thu, 5 Jan 2012 18:31:40 +0000 (UTC) Received: from [10.20.15.50] (out1.hq.siminn.dk [195.184.109.1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id 9B1366A65A; Thu, 5 Jan 2012 19:31:39 +0100 (CET) X-DKIM: OpenDKIM Filter v2.4.1 mail.tyknet.dk 9B1366A65A DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1325788299; bh=tXVPwvXKzbnlAlzycYE8umzPAyHz+HRFEr6W5JnIy2k=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:Content-Type: Content-Transfer-Encoding; b=xBo+22LaUog2DI5LZsj4w3p15n8FymBQXOkqF7ojXj515Yf2ebRlf846+ZdhWfy2D uM35Sfjnrk4vamwlP+6R4dp3n5PKGGFseCQe6XfMGP4A9PA8KFnWD37+P1jxjsbLuN LhPOV0vXTkuCPyFDI0/ZkrOB4hQTpz2swKq/9e78= Message-ID: <4F05EC89.4050507@gibfest.dk> Date: Thu, 05 Jan 2012 19:31:37 +0100 From: Thomas Steen Rasmussen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: pjd@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: MFC of r225830 (hastd activemap cache flush) 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, 05 Jan 2012 18:31:41 -0000 Hello pjd@ and list, I think the MFC of this change was forgotten: http://svnweb.freebsd.org/base?view=revision&revision=225830 Any chance it can be committed to 9 ? Thanks! Best regards Thomas Steen Rasmussen ps. for the archives, I am trying to get rid of noise like this every five seconds: Jan 5 19:01:12 hostA hastd[60080]: [hasthd7] (primary) Local request failed (Operation not supported by device): FLUSH. Jan 5 19:01:12 hostA hastd[60080]: [hasthd7] (primary) Remote request failed (Operation not supported by device): FLUSH. This is from the primary, similar messages are logged on the secondary. From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 18:38:09 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 1AA0A106566B for ; Thu, 5 Jan 2012 18:38:09 +0000 (UTC) (envelope-from Martin.Birgmeier@aon.at) Received: from email.aon.at (smtpout01.highway.telekom.at [195.3.96.112]) by mx1.freebsd.org (Postfix) with ESMTP id 55FB28FC17 for ; Thu, 5 Jan 2012 18:38:08 +0000 (UTC) Received: (qmail 21161 invoked from network); 5 Jan 2012 18:38:06 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on WARSBL607.highway.telekom.at X-Spam-Level: Received: from 188-23-41-23.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([188.23.41.23]) (envelope-sender ) by smarthub83.res.a1.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 Jan 2012 18:38:06 -0000 Received: from mizar-v1.xyzzy (mizar-v1.xyzzy [192.168.1.51]) by gandalf.xyzzy (8.14.5/8.14.5) with ESMTP id q05Ic6lU036331 for ; Thu, 5 Jan 2012 19:38:06 +0100 (CET) (envelope-from Martin.Birgmeier@aon.at) Message-ID: <4F05EE0D.70604@aon.at> Date: Thu, 05 Jan 2012 19:38:05 +0100 From: Martin Birgmeier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> <4F056EEB.3050902@gmail.com> <4F058075.1020108@aon.at> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 05 Jan 2012 18:38:09 -0000 On 01/05/12 19:29, Joshua Boyd wrote: > On Thu, Jan 5, 2012 at 5:50 AM, Martin Birgmeierwrote: > >> Third, I have now asked twice how to wire the ATA CAM devices, without >> anybody even referring to that question. Well, I guess I'll have to find >> that out myself. >> > http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html > Interesting - thank you! Regards, Martin From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 22:52: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 C849E1065675; Thu, 5 Jan 2012 22:52:41 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 7E0258FC15; Thu, 5 Jan 2012 22:52:41 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 579962B8; Thu, 5 Jan 2012 23:52:38 +0100 (CET) Date: Thu, 5 Jan 2012 23:51:32 +0100 From: Pawel Jakub Dawidek To: Thomas Steen Rasmussen Message-ID: <20120105225132.GB1693@garage.freebsd.pl> References: <4F05EC89.4050507@gibfest.dk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lMM8JwqTlfDpEaS6" Content-Disposition: inline In-Reply-To: <4F05EC89.4050507@gibfest.dk> X-OS: FreeBSD 9.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, trociny@FreeBSD.org Subject: Re: MFC of r225830 (hastd activemap cache flush) 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, 05 Jan 2012 22:52:41 -0000 --lMM8JwqTlfDpEaS6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 05, 2012 at 07:31:37PM +0100, Thomas Steen Rasmussen wrote: > Hello pjd@ and list, >=20 > I think the MFC of this change was forgotten: > http://svnweb.freebsd.org/base?view=3Drevision&revision=3D225830 >=20 > Any chance it can be committed to 9 ? Thanks! >=20 > Best regards >=20 > Thomas Steen Rasmussen >=20 > ps. for the archives, I am trying to get rid of noise like this every > five seconds: > Jan 5 19:01:12 hostA hastd[60080]: [hasthd7] (primary) Local request > failed (Operation not supported by device): FLUSH. > Jan 5 19:01:12 hostA hastd[60080]: [hasthd7] (primary) Remote request > failed (Operation not supported by device): FLUSH. > This is from the primary, similar messages are logged on the secondary. I'm CCing Mikolaj, who was doing HAST merges, maybe he can merge it quickly. If not, I'll do it in a week or two. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --lMM8JwqTlfDpEaS6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk8GKXMACgkQForvXbEpPzQZjACg8oA7bU1qXqIqTOg80D57MGkS mogAn3va9TZYcpqOdpvT0JSlBKkzbU7l =SXiI -----END PGP SIGNATURE----- --lMM8JwqTlfDpEaS6-- From owner-freebsd-fs@FreeBSD.ORG Thu Jan 5 23:30:45 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 8B8791065673 for ; Thu, 5 Jan 2012 23:30:45 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1D42D8FC15 for ; Thu, 5 Jan 2012 23:30:44 +0000 (UTC) Received: by eaaf13 with SMTP id f13so1029094eaa.13 for ; Thu, 05 Jan 2012 15:30:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=gsWfD1VjxXE2SiFdP0f4bDwfNOcK497aTZHEnJtw8wA=; b=lFvqF25OYtAV6kMg16B9t3F/AJEAdK9yrGOgfEHmF+E3uexRQNSXgIBgRlSHmXKTRg tq9T2whzzzWxmlTIVtB78zb5Sj2sdjmI+YppKGqXQEa5y9uzFuGoqdg2t/eX2cJLHZ9P eBYRoRb91OnrCd6ZDNBY1keB5cW97et7k7ntM= Received: by 10.205.132.148 with SMTP id hu20mr1661521bkc.96.1325804826471; Thu, 05 Jan 2012 15:07:06 -0800 (PST) Received: from localhost ([95.69.173.122]) by mx.google.com with ESMTPS id l17sm116216711bkw.6.2012.01.05.15.07.04 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 Jan 2012 15:07:05 -0800 (PST) From: Mikolaj Golub To: Thomas Steen Rasmussen References: <4F05EC89.4050507@gibfest.dk> X-Comment-To: Thomas Steen Rasmussen Sender: Mikolaj Golub Date: Fri, 06 Jan 2012 01:07:02 +0200 In-Reply-To: <4F05EC89.4050507@gibfest.dk> (Thomas Steen Rasmussen's message of "Thu, 05 Jan 2012 19:31:37 +0100") Message-ID: <86pqexsq95.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org, pjd@freebsd.org Subject: Re: MFC of r225830 (hastd activemap cache flush) 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, 05 Jan 2012 23:30:45 -0000 On Thu, 05 Jan 2012 19:31:37 +0100 Thomas Steen Rasmussen wrote: TSR> Hello pjd@ and list, TSR> I think the MFC of this change was forgotten: TSR> http://svnweb.freebsd.org/base?view=revision&revision=225830 TSR> Any chance it can be committed to 9 ? Thanks! It was too late to get it into the release, so it was waiting for stable/9 being unfrozen. Committed yesterday together with other updates, to stable/9 (r229509) and stable/8 (r229510). -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Fri Jan 6 09:49:59 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 AA8C3106566B for ; Fri, 6 Jan 2012 09:49:59 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 62A498FC08 for ; Fri, 6 Jan 2012 09:49:59 +0000 (UTC) Received: by yhfq46 with SMTP id q46so602107yhf.13 for ; Fri, 06 Jan 2012 01:49:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HpsLkh518aqzwT3BEDLFIRfUTAWgWMMD/boVSDgc4l8=; b=JV/6cHzEZXq5ygXSy4HdbhoAGqStyI1VwIfJyfleyKyubYmXThbte32iDK9hNS8cnX orrQAK8u/1v5cnVdKXdXeXosy/dizV5QhIzlIQUnlFo2pmJK+GzTU+a3+chGHvFvYFwm vdz56FpOe/Y4kmDz47HsWeV+i/ODOVxna/Kdk= MIME-Version: 1.0 Received: by 10.236.78.193 with SMTP id g41mr5851940yhe.25.1325843398413; Fri, 06 Jan 2012 01:49:58 -0800 (PST) Received: by 10.236.139.193 with HTTP; Fri, 6 Jan 2012 01:49:58 -0800 (PST) In-Reply-To: <4F058FA0.7070301@quip.cz> References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> <4F056EEB.3050902@gmail.com> <4F058075.1020108@aon.at> <4F058FA0.7070301@quip.cz> Date: Fri, 6 Jan 2012 09:49:58 +0000 Message-ID: From: krad To: Miroslav Lachman <000.fbsd@quip.cz> Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Martin Birgmeier Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 06 Jan 2012 09:49:59 -0000 On 5 January 2012 11:55, Miroslav Lachman <000.fbsd@quip.cz> wrote: > Martin Birgmeier wrote: > >> On 01/05/12 10:35, Volodymyr Kostyrko wrote: >> >>> 05.01.2012 09:59, Martin Birgmeier wrote: >>> >>>> In 9.0, if I keep kern.cam.ada.legacy_aliases=1, there will be two paths >>>> to each device, one through adX, the other through adaX. Which one will >>>> zfs use, and show with 'zpool status'? >>>> >>> >>> You are partially incorrect here: >>> [torn] ~> ls -la /dev | grep ad >>> lrwxr-xr-x 1 root wheel 4 5 jan 08:22 ad6@ -> ada0 >>> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6a@ -> ada0a >>> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6b@ -> ada0b >>> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6d@ -> ada0d >>> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6e@ -> ada0e >>> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6f@ -> ada0f >>> lrwxr-xr-x 1 root wheel 13 5 jan 08:22 ad6f.journal@ -> ada0f.journal >>> crw-r----- 1 root operator 0, 64 5 jan 08:22 ada0 >>> crw-r----- 1 root operator 0, 66 5 jan 08:23 ada0a >>> crw-r----- 1 root operator 0, 68 5 jan 08:22 ada0b >>> crw-r----- 1 root operator 0, 70 5 jan 08:23 ada0d >>> crw-r----- 1 root operator 0, 72 5 jan 08:23 ada0e >>> crw-r----- 1 root operator 0, 74 5 jan 08:22 ada0f >>> crw-r----- 1 root operator 0, 79 5 jan 08:23 ada0f.journal >>> >>> Also, I understand that I will have to wire down the various ATA CAMs to >>>> obtain the old numbering. How can I do this? Again, which path would zfs >>>> use if I did not wire down the ATA CAMs? Will I have half of my devices >>>> go through adX and the other through adaX, or will zfs even believe that >>>> it has a multipath connectivity to each device? >>>> >>> >>> Not at all, ad6 would be a symlink to correct ada device, I haven't >>> yet changed the fstab on this machine and it reads: >>> >>> # Device Mountpoint FStype Options Dump Pass# >>> /dev/ad6b none swap sw 0 0 >>> /dev/ad6a / ufs rw 1 1 >>> /dev/ad6e /tmp ufs rw 2 2 >>> /dev/ad6f.journal /usr ufs rw,async 2 2 >>> /dev/ad6d /var ufs rw 2 2 >>> /dev/cd0 /cdrom cd9660 ro,noauto 0 0 >>> >>> Sigh... I get only half the answers, and these are not so helpful >> either. >> >> First of all, I *am* correct in saying that there are two paths to the >> same device, because the purpose of a (sym-)link precisely is to have an >> alternate path to the same object in the filesystem. So if someone tells >> me that zfs somehow (how?) excludes devices reached through symlinks, >> *that* would be an information I would find useful. >> >> Second, the whole purpose of the kern.cam.ada.legacy_aliases is to have >> backwards compatibility for fstab etc by installing symlinks in /dev. I >> know this very well but want to prepare for the day when I want to get >> rid of the necessity for this compatibility. >> >> Third, I have now asked twice how to wire the ATA CAM devices, without >> anybody even referring to that question. Well, I guess I'll have to find >> that out myself. >> >> I do appreciate all answers, even more so as I perfectly understand they >> are *free* answers, and maybe the above is even helpful to someone else >> (and does not confuse them instead), but I'd appreciate it even more if >> they were real answers. >> > > ZFS taste available devices on boot, find ondisk stored metadata and > additionally useses informations stored in /boot/zfs/zpool.cache > > "ad" to "ada" transition is not the only case where one disk device is > accessible by multiple ways. > On one of my servers with SAS drives, the ZFS partitions can be accessed > by /dev/daXsY or /dev/gpt/ or /dev/gptid/ > It works correctly without any confusions. > > If you will delete zpool.cache and then export / import pool, the member > devices will be named as "first tasted". So if you will disable symlinks to > "ad" device names, your zpool will be correctly loaded with new device > names. ZFS is smart enough to not depend on device names and order. You can > safely change order of cables / devices on controller and ZFS will start > without any problem. > So the problem with "ad" to "ada" transition on ZFS is rather cosmetic > (device names shown in zpool status output) but it will work with whatever > names. > You just need to fix UFS / fstab issues. > > Miroslav Lachman > > ______________________________**_________________ > 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 > " > and if you implement gpt or geom labeling event the ufs issues become a non event From owner-freebsd-fs@FreeBSD.ORG Fri Jan 6 17:26:34 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 8892B1065673 for ; Fri, 6 Jan 2012 17:26:34 +0000 (UTC) (envelope-from bryce@bryce.net) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2244B8FC16 for ; Fri, 6 Jan 2012 17:26:33 +0000 (UTC) Received: by werb13 with SMTP id b13so1848950wer.13 for ; Fri, 06 Jan 2012 09:26:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.139.91 with SMTP id b69mr3578387wej.51.1325869141603; Fri, 06 Jan 2012 08:59:01 -0800 (PST) Received: by 10.216.159.135 with HTTP; Fri, 6 Jan 2012 08:59:01 -0800 (PST) Date: Fri, 6 Jan 2012 10:59:01 -0600 Message-ID: From: Bryce Edwards To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: FS hang when creating snapshots on a UFS SU+J setup 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, 06 Jan 2012 17:26:34 -0000 Guys, I made the original post below to freebsd-current and a couple others confirmed the behavior I'm seeing but no ideas on a fix or troubleshooting so I wanted to bring it here. Bryce Edwards bryce.net> writes: > > I have a RELENG_9 machine that hangs when a snapshot is created on the > root fs (UFS, with SU+J). More accurately, all the processes show a > state of "suspfs" (with ^T) and no fs activity is completed from then > on. A hard reboot (power cycle) was the only way to proceed. > > Here's some reference info - let me know what else I should provide. > > $uname -a > FreeBSD xxx.xxx.net 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0: Sun Dec > 25 05:04:37 UTC 2011 root xxx.xxx.net:/usr/obj/usr/src/sys/GENERIC > amd64 > > csup was run just before build[world|kernel] so you have reference on > the version information. > > $mount > /dev/gpt/root on / (ufs, local, journaled soft-updates) > devfs on /dev (devfs, local, multilabel) > linprocfs on /compat/linux/proc (linprocfs, local) > { zfs info removed } > > $df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/gpt/root 454G 9.1G 409G 2% / > devfs 1.0k 1.0k 0B 100% /dev > linprocfs 4.0k 4.0k 0B 100% /compat/linux/proc > { zfs info removed } > > After the hard reset, there was a snapshot file listed in /.snap and > it was ~465 GB, iirc. Unfortunately, I needed to get things going > again so I was not able to debug or diagnose further. I may be able > to schedule a time that I could recreate the issue and diagnose > better, but I wanted to get your input on what data points and/or > command you would be interested in. > > Thanks in advance, > > Bryce > _______________________________________________ > freebsd-current freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe freebsd.org" > > Hi, May be i overlooked something but i can confirm the two precedents reports and PR kern/163310, i have the same freeze when trying to issue snapshot on the root fs when SUJ is ON. With 9-PRERELEASE and 10-CURRENT There was an old closed PR (may be or not) related to this PB: http://www.freebsd.org/cgi/query-pr.cgi?pr=160662 I never be able to create a snapshot when SUJ is activated. I use the STOCK GENERIC KERNEL ( System build form OFFICIAL RC ISO or from make world / no special make.conf) This PB occurs on several hardware and also in VM under VBox4 After the freeze i need to halt the system by pressing 5 seconds the power switch. Sometimes, the SUJ recovery is not enough, i have a PANIC with DUP ALLOC when i issue a full fsck -yf in single user, i got some files reconnected in lost+found and some rare recovery messages. To reproduce: Prior doing snapshot, i have fully checked with FSCK the integrity of the fs in single user mode. And just issue : mksnap_ffs /.snap/backup ( dump -L may also suffer from this ) My setup: ( NO ZFS / 4 GB / CORE 2 DUO / SATA 7.2k in ahci mode) FreeBSD test.test.test 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0: Sun Jan 1 13:35:33 CET 2012 root at test.test.test:/usr/obj/usr/src/sys/GENERIC amd64 /dev/ufs/ROOTFS on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) fdescfs on /dev/fd (fdescfs) procfs on /proc (procfs, local) Notice that nearly no fs activity occurring while doing this snapshot. Also no problems when SUJ is disable. Anyway, thanks so much for your wonderful and heavy work. It will be great to merge SUJ on 8.3 RELEASE when things got stable. Best wishes of happiness and success for this new year ! Alain from Paris. In love with FreeBSD since 386BSD 0.1 :-) From owner-freebsd-fs@FreeBSD.ORG Fri Jan 6 21:30:33 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 A46FE1065676; Fri, 6 Jan 2012 21:30:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 271858FC16; Fri, 6 Jan 2012 21:30:32 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so2468820vbb.13 for ; Fri, 06 Jan 2012 13:30:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=7i8L0JobRQXi8fpSUb/2zL5mr/eigMvIQmnjRiCPRqI=; b=DzZQTnzId4Lpls/2IaBjYGlBnvAdJ/5lxyqsnFmGdhduKjvt4B1f4hcVMjc1blwcre haPiqY19K2Yh2vixvPGfSr6wA5wtIU7pmRmWOlUTFyvJq94i/6ZtjuEH+NIXhhShAdLq HujoLAtCQlCTm93bpFuQGqUV2xSy4MfcL89ME= MIME-Version: 1.0 Received: by 10.52.24.35 with SMTP id r3mr3881435vdf.81.1325885431095; Fri, 06 Jan 2012 13:30:31 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Fri, 6 Jan 2012 13:30:31 -0800 (PST) In-Reply-To: <86ty4a8mc3.fsf@ds4.des.no> References: <86ty4a8mc3.fsf@ds4.des.no> Date: Fri, 6 Jan 2012 13:30:31 -0800 X-Google-Sender-Auth: VrRk9ZViKHedD6PwnMzfkv_i4i4 Message-ID: From: Adrian Chadd To: =?ISO-8859-1?Q?Dag=2DErling_Sm=F8rgrav?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-current , freebsd-arch@freebsd.org Subject: Re: Is it possible to make subr_acl_nfs4 and subr_acl_posix1e disabled? 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, 06 Jan 2012 21:30:33 -0000 2012/1/5 Dag-Erling Sm=F8rgrav : > Adrian Chadd writes: >> Since I'm not using NFS or UFS_ACL, I wondered if that code required. >> It turns out I can just build a kernel with those two disabled. >> >> Would it be possible to remove them from "standard" and make them >> optional? Or is there a reason to keep it in base? > > I would be very annoyed if it were no longer possible to netboot > GENERIC... I don't want to break that. :) I Just don't want to compile it in unless I'm using NFS/ZFS, and on my 4MB flash boards I'm not booting w/ NFS compiled in statically.. Adrian From owner-freebsd-fs@FreeBSD.ORG Fri Jan 6 21:37: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 B3CFF1065676; Fri, 6 Jan 2012 21:37:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 384678FC12; Fri, 6 Jan 2012 21:37:19 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so2475220vbb.13 for ; Fri, 06 Jan 2012 13:37:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=h5I48bZmkhT/BL8aTjZtM+ME+4su8sNBZEiKc/J1Ze4=; b=TovoUsGPZ+hQI7Dl/UFHa0WNC3+04nTj36ACPAataWHfTqC4Rr49Y9z4xWFX/prgqb R+NMbmDg3kiRzsQYp+bisGr/mjycBwxRCN72fy0houhGrSH0EBu60ThAM2PfuLKC0YDB V15z3HTQpI7uZ4XFz6B3cxHbvBo0bMye20VuA= MIME-Version: 1.0 Received: by 10.52.26.66 with SMTP id j2mr3838387vdg.98.1325885838661; Fri, 06 Jan 2012 13:37:18 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Fri, 6 Jan 2012 13:37:18 -0800 (PST) In-Reply-To: <201201050848.18414.jhb@freebsd.org> References: <201201050848.18414.jhb@freebsd.org> Date: Fri, 6 Jan 2012 13:37:18 -0800 X-Google-Sender-Auth: U9y4aWPHvV9i3FSLOZqseimAzS4 Message-ID: From: Adrian Chadd To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-current , freebsd-arch@freebsd.org Subject: Re: Is it possible to make subr_acl_nfs4 and subr_acl_posix1e disabled? 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, 06 Jan 2012 21:37:19 -0000 On 5 January 2012 05:48, John Baldwin wrote: > [ A bit excessive on the cross-posting? =A0arch@ alone was probably fine = ] I wanted to capture the attention of relevant people, as I don't want to break some subtle setup that I'm not at all aware of. > NFS doesn't actually use them curently, only UFS and ZFS do. =A0Unfortuna= tely > we've yet to make it possible to compile ZFS into the kernel, so you can'= t > make the sys/conf/files bits completely accurate yet (it would be nice to > let folks who don't need FFS for a ZFS-only system remove FFS and UFS, bu= t > this would break that): Ok. I'll just test that the GENERIC build works and then commit it. adrian From owner-freebsd-fs@FreeBSD.ORG Fri Jan 6 22:23: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 BDD16106564A for ; Fri, 6 Jan 2012 22:23:19 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 6CD6C8FC0C for ; Fri, 6 Jan 2012 22:23:19 +0000 (UTC) Received: (qmail 45860 invoked from network); 6 Jan 2012 21:56:37 -0000 Received: from unknown (HELO ?10.50.50.212?) (spawk@64.147.100.2) by acm.poly.edu with CAMELLIA256-SHA encrypted SMTP; 6 Jan 2012 21:56:37 -0000 Message-ID: <4F076E1E.4040908@acm.poly.edu> Date: Fri, 06 Jan 2012 16:56:46 -0500 From: Boris Kochergin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Martin Birgmeier References: <4F04749E.9020301@aon.at> <20120104172351.GA42855@icarus.home.lan> <4F05586B.9060109@aon.at> <4F056EEB.3050902@gmail.com> <4F058075.1020108@aon.at> In-Reply-To: <4F058075.1020108@aon.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Upgrade to 9.0: How to convert zpool from adX to adaX? 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, 06 Jan 2012 22:23:19 -0000 On 01/05/12 05:50, Martin Birgmeier wrote: > On 01/05/12 10:35, Volodymyr Kostyrko wrote: >> 05.01.2012 09:59, Martin Birgmeier wrote: >>> In 9.0, if I keep kern.cam.ada.legacy_aliases=1, there will be two >>> paths >>> to each device, one through adX, the other through adaX. Which one will >>> zfs use, and show with 'zpool status'? >> >> You are partially incorrect here: >> [torn] ~> ls -la /dev | grep ad >> lrwxr-xr-x 1 root wheel 4 5 jan 08:22 ad6@ -> ada0 >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6a@ -> ada0a >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6b@ -> ada0b >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6d@ -> ada0d >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6e@ -> ada0e >> lrwxr-xr-x 1 root wheel 5 5 jan 08:22 ad6f@ -> ada0f >> lrwxr-xr-x 1 root wheel 13 5 jan 08:22 ad6f.journal@ -> >> ada0f.journal >> crw-r----- 1 root operator 0, 64 5 jan 08:22 ada0 >> crw-r----- 1 root operator 0, 66 5 jan 08:23 ada0a >> crw-r----- 1 root operator 0, 68 5 jan 08:22 ada0b >> crw-r----- 1 root operator 0, 70 5 jan 08:23 ada0d >> crw-r----- 1 root operator 0, 72 5 jan 08:23 ada0e >> crw-r----- 1 root operator 0, 74 5 jan 08:22 ada0f >> crw-r----- 1 root operator 0, 79 5 jan 08:23 ada0f.journal >> >>> Also, I understand that I will have to wire down the various ATA >>> CAMs to >>> obtain the old numbering. How can I do this? Again, which path would >>> zfs >>> use if I did not wire down the ATA CAMs? Will I have half of my devices >>> go through adX and the other through adaX, or will zfs even believe >>> that >>> it has a multipath connectivity to each device? >> >> Not at all, ad6 would be a symlink to correct ada device, I haven't >> yet changed the fstab on this machine and it reads: >> >> # Device Mountpoint FStype Options Dump >> Pass# >> /dev/ad6b none swap sw >> 0 0 >> /dev/ad6a / ufs rw >> 1 1 >> /dev/ad6e /tmp ufs rw >> 2 2 >> /dev/ad6f.journal /usr ufs rw,async >> 2 2 >> /dev/ad6d /var ufs rw >> 2 2 >> /dev/cd0 /cdrom cd9660 ro,noauto >> 0 0 >> > Sigh... I get only half the answers, and these are not so helpful either. > > First of all, I *am* correct in saying that there are two paths to the > same device, because the purpose of a (sym-)link precisely is to have > an alternate path to the same object in the filesystem. So if someone > tells me that zfs somehow (how?) excludes devices reached through > symlinks, *that* would be an information I would find useful. > > Second, the whole purpose of the kern.cam.ada.legacy_aliases is to > have backwards compatibility for fstab etc by installing symlinks in > /dev. I know this very well but want to prepare for the day when I > want to get rid of the necessity for this compatibility. > > Third, I have now asked twice how to wire the ATA CAM devices, without > anybody even referring to that question. Well, I guess I'll have to > find that out myself. > > I do appreciate all answers, even more so as I perfectly understand > they are *free* answers, and maybe the above is even helpful to > someone else (and does not confuse them instead), but I'd appreciate > it even more if they were real answers. > > Regards, > > Martin > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" I've recently had to move a raidz2 pool from a /dev/ad* system to a /dev/ada* system. I, too, desired the disk numbers in the output of "zpool status" to stay the same. I'll assume that the problem is similar enough. First, I exported the pool on the /dev/ad* system with "zpool export". Then, I connected the disks, in random order, to the /dev/ada* system and ran "zpool import". "zpool import" does not consult the /boot/zfs/zpool.cache file, which is what has the preconceived notions of what pools contain what disks. The output of "zpool import" was my old pool, with all its disks, now in /dev/ada* form, albeit in random order. I then swapped disks between controllers until I got the order desired, and imported the pool. -Boris