From owner-freebsd-fs@FreeBSD.ORG Sun Aug 4 17:19:36 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3109222D for ; Sun, 4 Aug 2013 17:19:36 +0000 (UTC) (envelope-from karl@denninger.net) Received: from fs.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DFC272082 for ; Sun, 4 Aug 2013 17:19:35 +0000 (UTC) Received: from [192.168.1.40] (localhost [127.0.0.1]) by fs.denninger.net (8.14.6/8.13.1) with ESMTP id r74HJTLH073567 for ; Sun, 4 Aug 2013 12:19:30 -0500 (CDT) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (TLS/SSL) [192.168.1.40] by Spamblock-sys (LOCAL/AUTH); Sun Aug 4 12:19:30 2013 Message-ID: <51FE8D1C.5080509@denninger.net> Date: Sun, 04 Aug 2013 12:19:24 -0500 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: How do I clear this problem? :-) X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 17:19:36 -0000 Development system here where I've been screwing around with ZFS and ZPOOL. I have a deprecated mirror that cannot be imported (the disks used for it were wiped and re-used); however, an attempt to destroy the pool fails because it's not mounted, and I can't find a command to clear the cache data that ZPOOL is using to find it. [root@dbms2 /]# zpool import pool: zstore id: 4828844235736846012 state: UNAVAIL status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: http://illumos.org/msg/ZFS-8000-3C config: zstore UNAVAIL insufficient replicas mirror-0 UNAVAIL insufficient replicas 6822277834587078071 UNAVAIL cannot open 17152979047208821543 UNAVAIL cannot open mirror-1 UNAVAIL insufficient replicas 9208768479824103717 UNAVAIL cannot open 2616541439243568493 UNAVAIL cannot open Correct, none of the devices can be found (the system bitches loudly on the console about this, incidentally.) [root@dbms2 /]# zpool destroy zstore cannot open 'zstore': no such pool [root@dbms2 /]# zpool destroy 4828844235736846012 cannot open '4828844235736846012': name must begin with a letter [root@dbms2 /]# Attempts to drop the devices in the mirror (to take it apart "piecemeal") also fail. How do I clear this deprecated entry that cannot be brought back online? I can't completely clear EVERYTHING related to ZFS because there is another pool that is current in-service and working. I can't find anything in the man pages that addresses this...... -- Karl Denninger karl@denninger.net /Cuda Systems LLC/ From owner-freebsd-fs@FreeBSD.ORG Sun Aug 4 17:27:18 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 52D46410 for ; Sun, 4 Aug 2013 17:27:18 +0000 (UTC) (envelope-from prvs=1928f37ee5=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E7B7320BD for ; Sun, 4 Aug 2013 17:27:17 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005328042.msg for ; Sun, 04 Aug 2013 18:27:09 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 04 Aug 2013 18:27:09 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1928f37ee5=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <5C38117C14594404AAC7034DB56FD1BA@multiplay.co.uk> From: "Steven Hartland" To: "Karl Denninger" , References: <51FE8D1C.5080509@denninger.net> Subject: Re: How do I clear this problem? :-) Date: Sun, 4 Aug 2013 18:27:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 17:27:18 -0000 Might sound silly but what are you actually trying to achieve? Are you trying to create a new pool of the same name? Does ZFS still think it has the pool loaded via zpool status and your trying to clear that? .... Regards Steve ----- Original Message ----- From: "Karl Denninger" To: Sent: Sunday, August 04, 2013 6:19 PM Subject: How do I clear this problem? :-) > Development system here where I've been screwing around with ZFS and ZPOOL. > > I have a deprecated mirror that cannot be imported (the disks used for > it were wiped and re-used); however, an attempt to destroy the pool > fails because it's not mounted, and I can't find a command to clear the > cache data that ZPOOL is using to find it. > > [root@dbms2 /]# zpool import > pool: zstore > id: 4828844235736846012 > state: UNAVAIL > status: One or more devices are missing from the system. > action: The pool cannot be imported. Attach the missing > devices and try again. > see: http://illumos.org/msg/ZFS-8000-3C > config: > > zstore UNAVAIL insufficient replicas > mirror-0 UNAVAIL insufficient replicas > 6822277834587078071 UNAVAIL cannot open > 17152979047208821543 UNAVAIL cannot open > mirror-1 UNAVAIL insufficient replicas > 9208768479824103717 UNAVAIL cannot open > 2616541439243568493 UNAVAIL cannot open > > Correct, none of the devices can be found (the system bitches loudly on > the console about this, incidentally.) > > [root@dbms2 /]# zpool destroy zstore > cannot open 'zstore': no such pool > [root@dbms2 /]# zpool destroy 4828844235736846012 > cannot open '4828844235736846012': name must begin with a letter > [root@dbms2 /]# > > Attempts to drop the devices in the mirror (to take it apart > "piecemeal") also fail. > > How do I clear this deprecated entry that cannot be brought back > online? I can't completely clear EVERYTHING related to ZFS because > there is another pool that is current in-service and working. > > I can't find anything in the man pages that addresses this...... > > -- > Karl Denninger > karl@denninger.net > /Cuda Systems LLC/ > _______________________________________________ > 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" > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 4 17:31:08 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6945A4B8 for ; Sun, 4 Aug 2013 17:31:08 +0000 (UTC) (envelope-from karl@denninger.net) Received: from fs.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2599E20DC for ; Sun, 4 Aug 2013 17:31:07 +0000 (UTC) Received: from [192.168.1.40] (localhost [127.0.0.1]) by fs.denninger.net (8.14.6/8.13.1) with ESMTP id r74HV6pd077656 for ; Sun, 4 Aug 2013 12:31:06 -0500 (CDT) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (TLS/SSL) [192.168.1.40] by Spamblock-sys (LOCAL/AUTH); Sun Aug 4 12:31:06 2013 Message-ID: <51FE8FD5.1050605@denninger.net> Date: Sun, 04 Aug 2013 12:31:01 -0500 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Steven Hartland Subject: Re: How do I clear this problem? :-) References: <51FE8D1C.5080509@denninger.net> <5C38117C14594404AAC7034DB56FD1BA@multiplay.co.uk> In-Reply-To: <5C38117C14594404AAC7034DB56FD1BA@multiplay.co.uk> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 17:31:08 -0000 I do indeed have a pool of the same name; I can rename it of course but then scripts have to be changed. What I'm trying to do is get rid of the old entry because it is no longer relevant and causes a collision; I can get around the collision by using the UID of the pool on the mount when done manually, but that particular pool's devices are never coming back and every time an import is run the console complains about the missing device entries that cannot be probed. This is development box and thus I CAN wipe it to get rid of this, but if it happens on a production machine I'd like to know how to clear the problem. I understand that by doing so I irretrievably destroy the ability to get to the pool in the future but in this particular case the disks in question have been hard-overwritten with other data so that's already a fact irrespective of what the system thinks. -- Karl On 8/4/2013 12:27 PM, Steven Hartland wrote: > Might sound silly but what are you actually trying to achieve? > > Are you trying to create a new pool of the same name? > > Does ZFS still think it has the pool loaded via zpool status > and your trying to clear that? > > .... > > Regards > Steve > > ----- Original Message ----- From: "Karl Denninger" > To: > Sent: Sunday, August 04, 2013 6:19 PM > Subject: How do I clear this problem? :-) > > >> Development system here where I've been screwing around with ZFS and >> ZPOOL. >> >> I have a deprecated mirror that cannot be imported (the disks used for >> it were wiped and re-used); however, an attempt to destroy the pool >> fails because it's not mounted, and I can't find a command to clear the >> cache data that ZPOOL is using to find it. >> >> [root@dbms2 /]# zpool import >> pool: zstore >> id: 4828844235736846012 >> state: UNAVAIL >> status: One or more devices are missing from the system. >> action: The pool cannot be imported. Attach the missing >> devices and try again. >> see: http://illumos.org/msg/ZFS-8000-3C >> config: >> >> zstore UNAVAIL insufficient replicas >> mirror-0 UNAVAIL insufficient replicas >> 6822277834587078071 UNAVAIL cannot open >> 17152979047208821543 UNAVAIL cannot open >> mirror-1 UNAVAIL insufficient replicas >> 9208768479824103717 UNAVAIL cannot open >> 2616541439243568493 UNAVAIL cannot open >> >> Correct, none of the devices can be found (the system bitches loudly on >> the console about this, incidentally.) >> >> [root@dbms2 /]# zpool destroy zstore >> cannot open 'zstore': no such pool >> [root@dbms2 /]# zpool destroy 4828844235736846012 >> cannot open '4828844235736846012': name must begin with a letter >> [root@dbms2 /]# >> >> Attempts to drop the devices in the mirror (to take it apart >> "piecemeal") also fail. >> >> How do I clear this deprecated entry that cannot be brought back >> online? I can't completely clear EVERYTHING related to ZFS because >> there is another pool that is current in-service and working. >> >> I can't find anything in the man pages that addresses this...... >> >> -- >> Karl Denninger >> karl@denninger.net >> /Cuda Systems LLC/ >> _______________________________________________ >> 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" >> > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. > and the person or entity to whom it is addressed. In the event of > misdirection, the recipient is prohibited from using, copying, > printing or otherwise disseminating it or any information contained in > it. > In the event of misdirection, illegible or incomplete transmission > please telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > > > > %SPAMBLOCK-SYS: Matched [+killing@multiplay.co.uk], message ok -- Karl Denninger karl@denninger.net /Cuda Systems LLC/ From owner-freebsd-fs@FreeBSD.ORG Sun Aug 4 17:46:26 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8F2E97F6 for ; Sun, 4 Aug 2013 17:46:26 +0000 (UTC) (envelope-from prvs=1928f37ee5=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2F17E2148 for ; Sun, 4 Aug 2013 17:46:25 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005328215.msg for ; Sun, 04 Aug 2013 18:46:24 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 04 Aug 2013 18:46:24 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1928f37ee5=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: From: "Steven Hartland" To: "Karl Denninger" References: <51FE8D1C.5080509@denninger.net> <5C38117C14594404AAC7034DB56FD1BA@multiplay.co.uk> <51FE8FD5.1050605@denninger.net> Subject: Re: How do I clear this problem? :-) Date: Sun, 4 Aug 2013 18:47:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 17:46:26 -0000 ----- Original Message ----- From: "Karl Denninger" >I do indeed have a pool of the same name; I can rename it of course but > then scripts have to be changed. > > What I'm trying to do is get rid of the old entry because it is no > longer relevant and causes a collision; I can get around the collision > by using the UID of the pool on the mount when done manually, but that > particular pool's devices are never coming back and every time an import > is run the console complains about the missing device entries that > cannot be probed. > > This is development box and thus I CAN wipe it to get rid of this, but > if it happens on a production machine I'd like to know how to clear the > problem. I understand that by doing so I irretrievably destroy the > ability to get to the pool in the future but in this particular case the > disks in question have been hard-overwritten with other data so that's > already a fact irrespective of what the system thinks. Sorry karl I still don't quite understand what you mean by "old entry" I'm guessing your seeing an old cached entry when you run "zpool import" Is that the case? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 4 18:09:38 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C4A2AC29 for ; Sun, 4 Aug 2013 18:09:38 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-vb0-x22f.google.com (mail-vb0-x22f.google.com [IPv6:2607:f8b0:400c:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 849A421FE for ; Sun, 4 Aug 2013 18:09:38 +0000 (UTC) Received: by mail-vb0-f47.google.com with SMTP id h10so2143777vbh.34 for ; Sun, 04 Aug 2013 11:09:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LhG88fT3JNg7MmDd1s+sx0ChBCk6INEQ3vZd4XEyGOw=; b=diWHahvrE1xEwnSHgvgI509uwDPRMLVPD9VL2HewN+ChkyQy1BaUJZ9OEjqCkxGilz l/WN3otY7azGWKFnvC09FNhGvuhNNlrM88FKsJ+FjnbpN5RmlClAti+Bm/5re4dBAn9G B0HcazfrMt/faNbtyL57XB1WcGhmi9eg/Ifaj8xh6F8Vs56JKSvxvH6ERq5UhJFuWUut Hu/YBRzdVxEi+h2fUfuKTzOgTtLub6EK9TwawOHnMB7ghxDDr1aRdYGPuxjK5RBKbhCq WSHwKzXe4caDGGDxAPztaV4BEqQDg+ia5G9skBe8eoshfN1JP4R4nXJRNEZdOZSTriPH nIag== MIME-Version: 1.0 X-Received: by 10.221.28.198 with SMTP id rv6mr4802175vcb.5.1375639777501; Sun, 04 Aug 2013 11:09:37 -0700 (PDT) Received: by 10.220.122.1 with HTTP; Sun, 4 Aug 2013 11:09:37 -0700 (PDT) In-Reply-To: <9F85D42E-D431-455E-8DFC-CEA7AC53F4BE@dragondata.com> References: <51FD867B.8070803@denninger.net> <9F85D42E-D431-455E-8DFC-CEA7AC53F4BE@dragondata.com> Date: Sun, 4 Aug 2013 14:09:37 -0400 Message-ID: Subject: Re: ZFS option vfs.zfs.cache_flush_disable=1 From: Zaphod Beeblebrox To: Kevin Day Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 18:09:38 -0000 I think the gravamen of the original question is the effect of vfs.zfs.cache_flush_disable=1. You have roughly the following situation: user writes --->> zfs caches --->> controller cache --->> drive cache --->> disk The stated problem was that zfs flushes push not only the zfs caches to the controller, but also the controller caches to disk. If the zfs cache flush is disabled, does that mean, in a period of inactivity, that data written to zfs will possibly sit in the zfs cache and not make it to disk? From owner-freebsd-fs@FreeBSD.ORG Sun Aug 4 18:33:40 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B64F66CC for ; Sun, 4 Aug 2013 18:33:40 +0000 (UTC) (envelope-from karl@denninger.net) Received: from fs.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 724142354 for ; Sun, 4 Aug 2013 18:33:39 +0000 (UTC) Received: from [192.168.1.40] (localhost [127.0.0.1]) by fs.denninger.net (8.14.6/8.13.1) with ESMTP id r74IXXLM099492 for ; Sun, 4 Aug 2013 13:33:34 -0500 (CDT) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (TLS/SSL) [192.168.1.40] by Spamblock-sys (LOCAL/AUTH); Sun Aug 4 13:33:34 2013 Message-ID: <51FE9E78.2010207@denninger.net> Date: Sun, 04 Aug 2013 13:33:28 -0500 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Steven Hartland Subject: Re: How do I clear this problem? :-) References: <51FE8D1C.5080509@denninger.net> <5C38117C14594404AAC7034DB56FD1BA@multiplay.co.uk> <51FE8FD5.1050605@denninger.net> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 18:33:40 -0000 Yes. On 8/4/2013 12:47 PM, Steven Hartland wrote: > ----- Original Message ----- From: "Karl Denninger" >> I do indeed have a pool of the same name; I can rename it of course but >> then scripts have to be changed. >> >> What I'm trying to do is get rid of the old entry because it is no >> longer relevant and causes a collision; I can get around the collision >> by using the UID of the pool on the mount when done manually, but that >> particular pool's devices are never coming back and every time an import >> is run the console complains about the missing device entries that >> cannot be probed. >> >> This is development box and thus I CAN wipe it to get rid of this, but >> if it happens on a production machine I'd like to know how to clear the >> problem. I understand that by doing so I irretrievably destroy the >> ability to get to the pool in the future but in this particular case the >> disks in question have been hard-overwritten with other data so that's >> already a fact irrespective of what the system thinks. > > Sorry karl I still don't quite understand what you mean by "old entry" > I'm guessing your seeing an old cached entry when you run "zpool import" > > Is that the case? > > Regards > Steve > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. > and the person or entity to whom it is addressed. In the event of > misdirection, the recipient is prohibited from using, copying, > printing or otherwise disseminating it or any information contained in > it. > In the event of misdirection, illegible or incomplete transmission > please telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > > > > %SPAMBLOCK-SYS: Matched [+killing@multiplay.co.uk], message ok -- Karl Denninger karl@denninger.net /Cuda Systems LLC/ From owner-freebsd-fs@FreeBSD.ORG Sun Aug 4 19:53:44 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CD02879B for ; Sun, 4 Aug 2013 19:53:44 +0000 (UTC) (envelope-from nicolas@i.0x5.de) Received: from n.0x5.de (n.0x5.de [217.197.85.144]) by mx1.freebsd.org (Postfix) with ESMTP id 87039273B for ; Sun, 4 Aug 2013 19:53:43 +0000 (UTC) Received: by pc5.i.0x5.de (Postfix, from userid 1003) id 3c7Xfn2tQVz7ySG; Sun, 4 Aug 2013 21:46:25 +0200 (CEST) Date: Sun, 4 Aug 2013 21:46:25 +0200 From: Nicolas Rachinsky To: freebsd-fs@freebsd.org Subject: Re: How do I clear this problem? :-) Message-ID: <20130804194625.GA97631@mid.pc5.i.0x5.de> Mail-Followup-To: freebsd-fs@freebsd.org References: <51FE8D1C.5080509@denninger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51FE8D1C.5080509@denninger.net> X-Powered-by: FreeBSD X-Homepage: http://www.rachinsky.de X-PGP-Keyid: 887BAE72 X-PGP-Fingerprint: 039E 9433 115F BC5F F88D 4524 5092 45C4 887B AE72 X-PGP-Keys: http://www.rachinsky.de/nicolas/gpg/nicolas_rachinsky.asc User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 19:53:44 -0000 * Karl Denninger [2013-08-04 12:19 -0500]: > it were wiped and re-used); however, an attempt to destroy the pool > fails because it's not mounted, and I can't find a command to clear the > cache data that ZPOOL is using to find it. Try exporting it. zpool export zstore This worked for me with 8.3 Nicolas -- http://www.rachinsky.de/nicolas From owner-freebsd-fs@FreeBSD.ORG Sun Aug 4 22:43:39 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0145C108; Sun, 4 Aug 2013 22:43:39 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id A8BA02CAB; Sun, 4 Aug 2013 22:43:37 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqIEABLY/lGDaFve/2dsb2JhbABagztQgxC8BYEzdIIkAQEFI1YbGAICDRkCWQYTiBCkSpBcBIEojj00B4JmgScDqS+DMyCBbg X-IronPort-AV: E=Sophos;i="4.89,814,1367985600"; d="scan'208";a="43084940" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 04 Aug 2013 18:43:31 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 45032B3F41; Sun, 4 Aug 2013 18:43:31 -0400 (EDT) Date: Sun, 4 Aug 2013 18:43:31 -0400 (EDT) From: Rick Macklem To: Berend de Boer Message-ID: <217266388.5736789.1375656211230.JavaMail.root@uoguelph.ca> In-Reply-To: <87iozr5c03.wl%berend@pobox.com> Subject: Re: Terrible NFS4 performance: FreeBSD 9.1 + UFS/ZFS + AWS EC2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 7.2.1_GA_2790 (ZimbraWebClient - FF3.0 (Win)/7.2.1_GA_2790) Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 22:43:39 -0000 Berend de Boer wrote: > >>>>> "Julian" == Julian Elischer writes: > > Julian> Recent evidence with AWS is suggesting that the > Julian> NOADAPTIVE_XXX options in the XENHVM kernel are now > Julian> seriously hindering AWS performance all over the place. > Julian> make sure you have tried with these options removed. > > Julian, on the same machine nfs3 is better than Linux, and nfs4 is > terrible. > All I could tell from the packet trace is that it is doing a massive number of lookups. I have no idea why the client does this, but it could possibly be the way the system is storing directory modify times and the change attribute (which is kinda like a modify time, in that it changes whenever a file's data or metadata changes, for NFSv4 only). I know absolutely nothing about this virtualized environment, so all I can suggest is trying "real hardware" to see if the same behaviour occurs when the server is running on a real hardware box. rick > > -- > All the best, > > Berend de Boer > > > ------------------------------------------------------ > Awesome Drupal hosting: https://www.xplainhosting.com/ > > From owner-freebsd-fs@FreeBSD.ORG Mon Aug 5 11:06:44 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9B63EF18 for ; Mon, 5 Aug 2013 11:06:44 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 87E192595 for ; Mon, 5 Aug 2013 11:06:44 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r75B6ijw036054 for ; Mon, 5 Aug 2013 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r75B6i2A036052 for freebsd-fs@FreeBSD.org; Mon, 5 Aug 2013 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Aug 2013 11:06:44 GMT Message-Id: <201308051106.r75B6i2A036052@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 Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 11:06:44 -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/180979 fs [netsmb][patch]: Fix large files handling o kern/180876 fs [zfs] [hast] ZFS with trim,bio_flush or bio_delete loc o kern/180678 fs [NFS] succesfully exported filesystems being reported o kern/180438 fs [smbfs] [patch] mount_smbfs fails on arm because of wr p kern/180236 fs [zfs] [nullfs] Leakage free space using ZFS with nullf o kern/178854 fs [ufs] FreeBSD kernel crash in UFS o kern/178713 fs [nfs] [patch] Correct WebNFS support in NFS server and o kern/178412 fs [smbfs] Coredump when smbfs mounted o kern/178388 fs [zfs] [patch] allow up to 8MB recordsize o kern/178349 fs [zfs] zfs scrub on deduped data could be much less see o kern/178329 fs [zfs] extended attributes leak o kern/178238 fs [nullfs] nullfs don't release i-nodes on unlink. f kern/178231 fs [nfs] 8.3 nfsv4 client reports "nfsv4 client/server pr o kern/178103 fs [kernel] [nfs] [patch] Correct support of index files o kern/177985 fs [zfs] disk usage problem when copying from one zfs dat o kern/177971 fs [nfs] FreeBSD 9.1 nfs client dirlist problem w/ nfsv3, o kern/177966 fs [zfs] resilver completes but subsequent scrub reports o kern/177658 fs [ufs] FreeBSD panics after get full filesystem with uf o kern/177536 fs [zfs] zfs livelock (deadlock) with high write-to-disk o kern/177445 fs [hast] HAST panic o kern/177240 fs [zfs] zpool import failed with state UNAVAIL but all d o kern/176978 fs [zfs] [panic] zfs send -D causes "panic: System call i o kern/176857 fs [softupdates] [panic] 9.1-RELEASE/amd64/GENERIC panic o bin/176253 fs zpool(8): zfs pool indentation is misleading/wrong o kern/176141 fs [zfs] sharesmb=on makes errors for sharenfs, and still o kern/175950 fs [zfs] Possible deadlock in zfs after long uptime o kern/175897 fs [zfs] operations on readonly zpool hang o kern/175449 fs [unionfs] unionfs and devfs misbehaviour o kern/175179 fs [zfs] ZFS may attach wrong device on move o kern/175071 fs [ufs] [panic] softdep_deallocate_dependencies: unrecov o kern/174372 fs [zfs] Pagefault appears to be related to ZFS o kern/174315 fs [zfs] chflags uchg not supported o kern/174310 fs [zfs] root point mounting broken on CURRENT with multi o kern/174279 fs [ufs] UFS2-SU+J journal and filesystem corruption o kern/173830 fs [zfs] Brain-dead simple change to ZFS error descriptio o kern/173718 fs [zfs] phantom directory in zraid2 pool f kern/173657 fs [nfs] strange UID map with nfsuserd o kern/173363 fs [zfs] [panic] Panic on 'zpool replace' on readonly poo o kern/173136 fs [unionfs] mounting above the NFS read-only share panic o kern/172942 fs [smbfs] Unmounting a smb mount when the server became o kern/172348 fs [unionfs] umount -f of filesystem in use with readonly o kern/172334 fs [unionfs] unionfs permits recursive union mounts; caus o kern/171626 fs [tmpfs] tmpfs should be noisier when the requested siz o kern/171415 fs [zfs] zfs recv fails with "cannot receive incremental o kern/170945 fs [gpt] disk layout not portable between direct connect o bin/170778 fs [zfs] [panic] FreeBSD panics randomly o kern/170680 fs [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEA o kern/170497 fs [xfs][panic] kernel will panic whenever I ls a mounted o kern/169945 fs [zfs] [panic] Kernel panic while importing zpool (afte o kern/169480 fs [zfs] ZFS stalls on heavy I/O o kern/169398 fs [zfs] Can't remove file with permanent error o kern/169339 fs panic while " : > /etc/123" o kern/169319 fs [zfs] zfs resilver can't complete o kern/168947 fs [nfs] [zfs] .zfs/snapshot directory is messed up when o kern/168942 fs [nfs] [hang] nfsd hangs after being restarted (not -HU o kern/168158 fs [zfs] incorrect parsing of sharenfs options in zfs (fs o kern/167979 fs [ufs] DIOCGDINFO ioctl does not work on 8.2 file syste o kern/167977 fs [smbfs] mount_smbfs results are differ when utf-8 or U o kern/167688 fs [fusefs] Incorrect signal handling with direct_io o kern/167685 fs [zfs] ZFS on USB drive prevents shutdown / reboot o kern/167612 fs [portalfs] The portal file system gets stuck inside po o kern/167272 fs [zfs] ZFS Disks reordering causes ZFS to pick the wron o kern/167260 fs [msdosfs] msdosfs disk was mounted the second time whe o kern/167109 fs [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene o kern/167105 fs [nfs] mount_nfs can not handle source exports wiht mor o kern/167067 fs [zfs] [panic] ZFS panics the server o kern/167065 fs [zfs] boot fails when a spare is the boot disk o kern/167048 fs [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF o kern/166912 fs [ufs] [panic] Panic after converting Softupdates to jo o kern/166851 fs [zfs] [hang] Copying directory from the mounted UFS di o kern/166477 fs [nfs] NFS data corruption. o kern/165950 fs [ffs] SU+J and fsck problem o kern/165521 fs [zfs] [hang] livelock on 1 Gig of RAM with zfs when 31 o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161864 fs [ufs] removing journaling from UFS partition fails on o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic f kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs p kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o bin/153142 fs [zfs] ls -l outputs `ls: ./.zfs: Operation not support o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/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/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 o kern/145750 fs [unionfs] [hang] unionfs locks the machine 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/141950 fs [unionfs] [lor] ufs/unionfs/ufs Lock order reversal 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/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/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/137588 fs [unionfs] [lor] LOR nfs/ufs/nfs 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 p kern/133174 fs [msdosfs] [patch] msdosfs must support multibyte inter 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/126973 fs [unionfs] [hang] System hang with unionfs and init chr o kern/126553 fs [unionfs] unionfs move directory problem 2 (files appe o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o bin/123574 fs [unionfs] df(1) -t option destroys info for unionfs (a 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 kern/121385 fs [unionfs] unionfs cross mount -> kernel panic o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118318 fs [nfs] NFS server hangs under special circumstances o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o 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/67326 fs [msdosfs] crash after attempt to mount write protected o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t o kern/9619 fs [nfs] Restarting mountd kills existing mounts 329 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 5 18:47:43 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7F8BF987 for ; Mon, 5 Aug 2013 18:47:43 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id 551AB2FF5 for ; Mon, 5 Aug 2013 18:47:42 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 940E02C985; Mon, 5 Aug 2013 14:47:36 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAdHCjX33jbY; Mon, 5 Aug 2013 14:47:36 -0400 (EDT) Received: from daemon.localdomain (daemon.egr.msu.edu [35.9.44.65]) by mail.egr.msu.edu (Postfix) with ESMTP id 6A3EB2C97B; Mon, 5 Aug 2013 14:47:36 -0400 (EDT) Received: by daemon.localdomain (Postfix, from userid 21281) id 4042619157C; Mon, 5 Aug 2013 14:47:36 -0400 (EDT) Date: Mon, 5 Aug 2013 14:47:36 -0400 From: Adam McDougall To: Karl Denninger Subject: Re: How do I clear this problem? :-) Message-ID: <20130805184736.GO25894@egr.msu.edu> References: <51FE8D1C.5080509@denninger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51FE8D1C.5080509@denninger.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 18:47:43 -0000 On Sun, Aug 04, 2013 at 12:19:24PM -0500, Karl Denninger wrote: Development system here where I've been screwing around with ZFS and ZPOOL. I have a deprecated mirror that cannot be imported (the disks used for it were wiped and re-used); however, an attempt to destroy the pool fails because it's not mounted, and I can't find a command to clear the cache data that ZPOOL is using to find it. [root@dbms2 /]# zpool import pool: zstore id: 4828844235736846012 state: UNAVAIL Can you take a look at the 'zpool labelclear' command? Please be aware that it apparently can clear more than just ZFS labels on devices you specify, which doesn't sound like a problem for you, but interested parties can see the 6/13/13 thread "Subject: zpool labelclear destroys GPT" on freebsd-stable. From owner-freebsd-fs@FreeBSD.ORG Mon Aug 5 19:20:16 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 94CE0375 for ; Mon, 5 Aug 2013 19:20:16 +0000 (UTC) (envelope-from tjg@ucsc.edu) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 57D1921CC for ; Mon, 5 Aug 2013 19:20:16 +0000 (UTC) Received: by mail-ob0-f179.google.com with SMTP id fb19so6360955obc.38 for ; Mon, 05 Aug 2013 12:20:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VlANDonnp4TC0phee9YMFaaJqlESOJu+gNMr/xmvNVI=; b=Ciku8M9tRpJI3K/hkQr6uTzH/XCv27PEF9pGEHYEOGQLupMoMHqIkpiPAR9S01Q1az hn+sdPez2ILJVECZtosqpIDqk3YcHOKeSO6HLQzmqWeDRodWP718pDMJ4TacSPbIHV6U nfEvD35MdG6xc30aD6Fwbya7iOtm6lYknPufo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=VlANDonnp4TC0phee9YMFaaJqlESOJu+gNMr/xmvNVI=; b=kjPF5NbKfZ2RsLSvDLsUUEDmu+JylK0cwZ3uwDkzJiqO5ZRjbhkE7P/UoHifFT8vFi FEUQ2x13p8b5NF0AOHewfx/9vIBxBoa0TY0tg+FL4ZGS+AyMNjNBQcYcogNp56uLmT4l bw6P0POdPpsPbFTX6FuL1mPyfGaekmP3de6jfgqPGrcaLaVg/NuTtTbkl3IbiN+aNoIR zNzqJEBhT7G6ejm9C2wsDZUu3DyKIcEBH+4wn/yAm2XhjVlYFtMLE490EmDsvVZQTQDM cl8KXlZtAvBQXdTr8BEozJ+YoB0Iy7yoFsqoxepaWMYWlASKY2HZqyq2mN2VvJ8VvyNS awyg== MIME-Version: 1.0 X-Received: by 10.42.63.207 with SMTP id d15mr1741298ici.21.1375730415490; Mon, 05 Aug 2013 12:20:15 -0700 (PDT) Received: by 10.42.233.143 with HTTP; Mon, 5 Aug 2013 12:20:15 -0700 (PDT) In-Reply-To: References: <51FBC806.3070500@egr.msu.edu> Date: Mon, 5 Aug 2013 12:20:15 -0700 Message-ID: Subject: Re: ZFS: unsupported ZFS version 5000 (should be 28) From: Tim Gustafson To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQn2uxU6fXRxSlVV4JYG+UGBuKCpy0v+D5SLBJhXctNoBDDt8typpFRgfKbSXFO5VMwqszRr X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 19:20:16 -0000 I wanted to report back to the group about how I was able to get past this problem. A quick re-cap of what happened: - A few weeks ago, we upgraded from 8.2 to 8.4 using the Subversion repository at http://svn.freebsd.org/base/releng/8.4 - On Thursday last week, I fat-fingered a command that caused /usr to be dismounted - I rebooted into single-user mode, fixed /usr, and rebooted successfully back into multi-user mode - Just to make sure that nothing in /usr got clobbered, I did a "make buildworld buildkernel installkernel installworld" - Upon rebooting after the buildworld procedure, the system reported that the zpool version (5000/28) was too new So, somehow among all that, the zpool got upgraded to a new version. I'm not sure how that's possible, given that at no time were we running a beta version of any OS up to this point. Reinstalling the bootcode (ala "gpart bootcode") from either the compiled sources or a 9.2-BETA CD didn't help because /boot/loader did not support the newer version. I actually needed to upgrade the box to 9.2-BETA in order to get a version of /boot/loader that could see the zpool correctly. So I'm running on 9.2-BETA now, and everything seems OK. I'm not thrilled that we're running a beta OS version on a production machine, but I see no other way unless I rebuild the zpool, which I don't want to do. This is several terabytes of data and includes a lot of snapshots that have to be preserved, and therefore rsync won't do, and zfs send/receive would preserve the incorrect zpool version (if I understand things correctly). So, is there *any* way at all that someone accidentally committed something to releng/8.4 that should have been committed to stable/8 instead? -- Tim Gustafson tjg@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A From owner-freebsd-fs@FreeBSD.ORG Tue Aug 6 10:34:03 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 869C16F7 for ; Tue, 6 Aug 2013 10:34:03 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 091C225CA for ; Tue, 6 Aug 2013 10:34:02 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id q55so195259wes.2 for ; Tue, 06 Aug 2013 03:34:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XrDKoufcjW7d9i48irja+7L5TgsX5rrqnbDTQQFq/24=; b=x009JxYjCoBE7jEV/cd4PlDQ8KztD+IrXsE2fGs+PPbxkmEjoQQ7dhs+A6ccv41mOE H5hJ3h8Cks5725fYVwNycPwkpyHHKDvgpK9D7yTDEMNkOc7Rx/PMntZCwMFG9I7oEn+/ K6kGoYqMok+RsLZgqRfTQ62XhPSyZh4uPb6ovqinIFkf+IvPoVlR2tkQgSgejQAbjdUD hpnYdtXItv2PwZznRqKXqx93CSH7VqbDYuIfGWz41pyiVpARFz5eKqhzXjyE+mGaUaoU nJssUW4K0q3QNs1IIkm16gyfc2SeSfmPwRCHnmhnCvo5sdrXTWDzNeNJMnVitBNW14JJ D3Yg== MIME-Version: 1.0 X-Received: by 10.180.84.225 with SMTP id c1mr1442051wiz.53.1375785241238; Tue, 06 Aug 2013 03:34:01 -0700 (PDT) Received: by 10.216.67.193 with HTTP; Tue, 6 Aug 2013 03:34:01 -0700 (PDT) In-Reply-To: <51FE9E78.2010207@denninger.net> References: <51FE8D1C.5080509@denninger.net> <5C38117C14594404AAC7034DB56FD1BA@multiplay.co.uk> <51FE8FD5.1050605@denninger.net> <51FE9E78.2010207@denninger.net> Date: Tue, 6 Aug 2013 11:34:01 +0100 Message-ID: Subject: Re: How do I clear this problem? :-) From: krad To: Karl Denninger Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 10:34:03 -0000 If you are not root on zfs and get real stuck, go into single user mode, export all your pools (valid ones), then delete the zpool.cache, then just reimport your valid pools On 4 August 2013 19:33, Karl Denninger wrote: > Yes. > > On 8/4/2013 12:47 PM, Steven Hartland wrote: > > ----- Original Message ----- From: "Karl Denninger" > >> I do indeed have a pool of the same name; I can rename it of course but > >> then scripts have to be changed. > >> > >> What I'm trying to do is get rid of the old entry because it is no > >> longer relevant and causes a collision; I can get around the collision > >> by using the UID of the pool on the mount when done manually, but that > >> particular pool's devices are never coming back and every time an import > >> is run the console complains about the missing device entries that > >> cannot be probed. > >> > >> This is development box and thus I CAN wipe it to get rid of this, but > >> if it happens on a production machine I'd like to know how to clear the > >> problem. I understand that by doing so I irretrievably destroy the > >> ability to get to the pool in the future but in this particular case the > >> disks in question have been hard-overwritten with other data so that's > >> already a fact irrespective of what the system thinks. > > > > Sorry karl I still don't quite understand what you mean by "old entry" > > I'm guessing your seeing an old cached entry when you run "zpool import" > > > > Is that the case? > > > > Regards > > Steve > > > > ================================================ > > This e.mail is private and confidential between Multiplay (UK) Ltd. > > and the person or entity to whom it is addressed. In the event of > > misdirection, the recipient is prohibited from using, copying, > > printing or otherwise disseminating it or any information contained in > > it. > > In the event of misdirection, illegible or incomplete transmission > > please telephone +44 845 868 1337 > > or return the E.mail to postmaster@multiplay.co.uk. > > > > > > > > %SPAMBLOCK-SYS: Matched [+killing@multiplay.co.uk], message ok > > -- > Karl Denninger > karl@denninger.net > /Cuda Systems LLC/ > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Tue Aug 6 11:26:40 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7ACD27FD for ; Tue, 6 Aug 2013 11:26:40 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F19BE2887 for ; Tue, 6 Aug 2013 11:26:39 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id hi8so191549lab.35 for ; Tue, 06 Aug 2013 04:26:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ahog9HSY7gdhSAkpoQL3ueoDzLF5Bk/AwQwmCD00Bps=; b=mGTnk41+PhP7Ufs6F47Btdrc0kOmK4PsM/XbV6BlN6H6849Z3kq1xBXMojvUo12iGv FSAVlbF6Qm4LYmx4rRvXPFs81ccF6n0WgUYfKzuIwl30z/BMirrDLPNBlpfknXAOjyVK 5vKx9iADocnbx2W2al0hLzDqJxWMHk1P3q2Cz5wJkSzpFhNW1M3DMvM2cPa4nsclHj/O 8tnL8OX6KcH6G2Iyk5Kdv5YAOeB8wc1xs8AcBmbUSBavpo5iyPeWRnPuU6uDMgttv0F4 546Hn7zLQ5uOLMc0Y+YBLlPbctHts+LjC2gDomyLbcSl5O/VuQVt7VsxEzTItU32p7aS sSpw== MIME-Version: 1.0 X-Received: by 10.112.20.200 with SMTP id p8mr989635lbe.87.1375788397812; Tue, 06 Aug 2013 04:26:37 -0700 (PDT) Received: by 10.112.201.41 with HTTP; Tue, 6 Aug 2013 04:26:37 -0700 (PDT) In-Reply-To: References: <51FBC806.3070500@egr.msu.edu> Date: Tue, 6 Aug 2013 12:26:37 +0100 Message-ID: Subject: Re: ZFS: unsupported ZFS version 5000 (should be 28) From: Tom Evans To: Tim Gustafson Content-Type: text/plain; charset=UTF-8 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 11:26:40 -0000 On Mon, Aug 5, 2013 at 8:20 PM, Tim Gustafson wrote: > I wanted to report back to the group about how I was able to get past > this problem. > > A quick re-cap of what happened: > > - A few weeks ago, we upgraded from 8.2 to 8.4 using the Subversion > repository at http://svn.freebsd.org/base/releng/8.4 > > - On Thursday last week, I fat-fingered a command that caused /usr to > be dismounted > > - I rebooted into single-user mode, fixed /usr, and rebooted > successfully back into multi-user mode > > - Just to make sure that nothing in /usr got clobbered, I did a "make > buildworld buildkernel installkernel installworld" > > - Upon rebooting after the buildworld procedure, the system reported > that the zpool version (5000/28) was too new > > So, somehow among all that, the zpool got upgraded to a new version. > I'm not sure how that's possible, given that at no time were we > running a beta version of any OS up to this point. You should be able to determine when the pool was upgraded by checking zpool history, given that you have ZFS working again. Even if you were running the very tip of 10-CURRENT, the pool would only be upgraded if "zpool ugrade " was run. Cheers Tom From owner-freebsd-fs@FreeBSD.ORG Wed Aug 7 08:48:24 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 19043E48 for ; Wed, 7 Aug 2013 08:48:24 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 63E1F2633 for ; Wed, 7 Aug 2013 08:48:22 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA21322; Wed, 07 Aug 2013 11:48:20 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1V6zPo-000O92-C2; Wed, 07 Aug 2013 11:48:20 +0300 Message-ID: <520209B0.1030402@FreeBSD.org> Date: Wed, 07 Aug 2013 11:47:44 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130708 Thunderbird/17.0.7 MIME-Version: 1.0 To: Konstantin Belousov Subject: Re: Deadlock in nullfs/zfs somewhere References: <20130718112814.GA5991@kib.kiev.ua> <51E7F05A.5020609@FreeBSD.org> <20130718185215.GE5991@kib.kiev.ua> <51E91277.3070309@FreeBSD.org> <20130719103025.GJ5991@kib.kiev.ua> <51E95CDD.7030702@FreeBSD.org> <20130719184243.GM5991@kib.kiev.ua> <51E99477.1030308@FreeBSD.org> <20130721071124.GY5991@kib.kiev.ua> <51EBABAB.5040808@FreeBSD.org> <20130721161854.GC5991@kib.kiev.ua> In-Reply-To: <20130721161854.GC5991@kib.kiev.ua> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 08:48:24 -0000 Kostik, thank you for being patient with me and explaining details of the contract and inner workings of VFS suspend. As we discussed out-of-band, unfortunately, it seems that it is impossible to implement the same contract for ZFS. The reason is that ZFS filesystems appear as many independent filesystems, but in reality they share a common pool. So suspending a single filesystem does not suspend the pool and that is contrary to current VFS suspend concept. Additionally, ZFS needs a "full" suspend mechanism that would prevent both read and write access from VFS layer. The current VFS suspend mechanism suspend writes / modifications only. I am not sure how to reconcile the differences... Here is a number of rough ideas. I will highly appreciate your opinion and suggestions. Idea #1. Add a new suspend type to VFS layer that would correspond to the needs of ZFS. This is quite laborious as it would require adding vn_start_read calls in many places. Also, making two kinds of VFS suspend play nice with each other could be non-trivial. Idea #2. This is perhaps an ugly approach, but I already have it implemented locally. The idea is to re-use / abuse vnode locking as a ZFS suspend barrier. (This can be considered to be analogous to putting vn_start_op() / vn_end_op() into vop_lock / vop_unlock). That is, ZFS would override VOP_LOCK/VOP_UNLOCK to check for internal suspension. The necessary care would be taken to respect all locking flags including LK_NOWAIT. Recursive entry would have to be supported too. Idea #3. Provide some other mechanism to expose ZFS suspension state to VFS. And then use that mechanism to avoid blocking on calls to ZFS in the strategic / sensitive places like vlrureclaim(), vtryrecycle(), etc. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Wed Aug 7 15:08:01 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4E8A8930 for ; Wed, 7 Aug 2013 15:08:00 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2366521F9 for ; Wed, 7 Aug 2013 15:08:00 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id D2930153435 for ; Wed, 7 Aug 2013 17:07:55 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxTXDgPL0gkU for ; Wed, 7 Aug 2013 17:07:55 +0200 (CEST) Received: from [IPv6:2001:4cb8:3:1:5d33:3a19:2ee6:6e9f] (unknown [IPv6:2001:4cb8:3:1:5d33:3a19:2ee6:6e9f]) by smtp.digiware.nl (Postfix) with ESMTP id 17639153433 for ; Wed, 7 Aug 2013 17:07:55 +0200 (CEST) Message-ID: <520262C6.2060606@digiware.nl> Date: Wed, 07 Aug 2013 17:07:50 +0200 From: Willem Jan Withagen Organization: Digiware Management b.v. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: fs@freebsd.org Subject: Crash while sending ZFS file system Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 15:08:01 -0000 Hi, I've got this relatively "old" (somewhere from around 8.0) ZFS filesytem that I'm trying to send to a new server. Given the ae, it could be very well that these is something off on the pool. But it core-dumps on: zfs send -v -R zfsraid@box | mbuffer -4 -m 100M -O box:5555 ........ send from @ to zfsraid/ezjail/nameserver@box estimated size is 245M send from @ to zfsraid/ezjail/newjail@box estimated size is 1.30M send from @ to zfsraid/obj@box estimated size is 4.80G send from @ to zfsraid/sonycam@box estimated size is 5.22M Assertion failed: (progress), file /usr/srcs/src9/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c, line 1316. The FreeBSD version is: FreeBSD zfs.digiware.nl 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #242 r253371 Now I can send some of the snapshots that are mounted on home. Just not the whole set of snapshots. It bombs out even still during the listing of all snapshots to send. If I look at the code it asserts that progress needs to be made. If this is not the case the assert is activated. Any suggestions as to how to fix/debug this? It generates a coredump Regards, --WjW From owner-freebsd-fs@FreeBSD.ORG Wed Aug 7 15:43:37 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9DAFD1F5 for ; Wed, 7 Aug 2013 15:43:37 +0000 (UTC) (envelope-from prvs=193113c93c=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 38F50240F for ; Wed, 7 Aug 2013 15:43:36 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005386564.msg for ; Wed, 07 Aug 2013 16:43:27 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 07 Aug 2013 16:43:27 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=193113c93c=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: fs@freebsd.org Message-ID: <4467AAF5BA6A450FAC9BD9306110A256@multiplay.co.uk> From: "Steven Hartland" To: "Willem Jan Withagen" , References: <520262C6.2060606@digiware.nl> Subject: Re: Crash while sending ZFS file system Date: Wed, 7 Aug 2013 16:43:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 15:43:37 -0000 ----- Original Message ----- From: "Willem Jan Withagen" To: Sent: Wednesday, August 07, 2013 4:07 PM Subject: Crash while sending ZFS file system > Hi, > > I've got this relatively "old" (somewhere from around 8.0) ZFS filesytem > that I'm trying to send to a new server. > Given the ae, it could be very well that these is something off on the pool. > > But it core-dumps on: > zfs send -v -R zfsraid@box | mbuffer -4 -m 100M -O box:5555 > ........ > send from @ to zfsraid/ezjail/nameserver@box estimated size is 245M > send from @ to zfsraid/ezjail/newjail@box estimated size is 1.30M > send from @ to zfsraid/obj@box estimated size is 4.80G > send from @ to zfsraid/sonycam@box estimated size is 5.22M > Assertion failed: (progress), file > /usr/srcs/src9/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c, > line 1316. > > The FreeBSD version is: > FreeBSD zfs.digiware.nl 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #242 r253371 > > Now I can send some of the snapshots that are mounted on home. > Just not the whole set of snapshots. > > It bombs out even still during the listing of all snapshots to send. > If I look at the code it asserts that progress needs to be made. > If this is not the case the assert is activated. > > Any suggestions as to how to fix/debug this? > It generates a coredump Whats the output of and the full output from the send: zfs list -t snapshot Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Wed Aug 7 18:04:47 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CED3D623; Wed, 7 Aug 2013 18:04:47 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from s1.omnilan.de (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3B8342D59; Wed, 7 Aug 2013 18:04:45 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by s1.omnilan.de (8.13.8/8.13.8) with ESMTP id r77I4grt080836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Aug 2013 20:04:43 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <52028C31.6060908@omnilan.de> Date: Wed, 07 Aug 2013 20:04:33 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: attilio@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions References: <20120829060158.GA38721@x2.osted.lan> <20120831052003.GA91340@x2.osted.lan> <20120905201531.GA54452@x2.osted.lan> <20120917140055.GA9037@x2.osted.lan> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0CA859C26DF2E57AF9889AAA" Cc: FreeBSD FS , FreeBSD current X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 18:04:48 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0CA859C26DF2E57AF9889AAA Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Bez=FCglich Attilio Rao's Nachricht vom 14.10.2012 02:27 (localtime): > On Fri, Sep 21, 2012 at 1:22 AM, Attilio Rao wrot= e: >> On Wed, Sep 19, 2012 at 3:48 AM, Attilio Rao wro= te: >>> On Fri, Jul 13, 2012 at 12:18 AM, Attilio Rao w= rote: >>>> 2012/7/4 Attilio Rao : >>>>> 2012/6/29 Attilio Rao : >>>>>> As already published several times, according to the following pla= n: >>>>>> http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS >>>>>> >>>>> I still haven't heard from Vivien or Edward, anyway as NTFS is >>>>> basically only used RO these days (also the mount_ntfs code just >>>>> permits RO mounting) I stripped all the uncomplete/bogus write supp= ort >>>>> with the following patch: >>>>> http://www.freebsd.org/~attilio/ntfs_remove_write.patch >>>>> >>>>> This is an attempt to make the code smaller and possibly just focus= on =2E.. > I've committed the FUSE support into base as r241519. Thank you for your great work! I had used http://www.freebsd.org/~attilio/fuse_import/fuse_stable9_241030.patch with releng/9.1. Some improovements were made in the meantime in head. I'm not familiar with svn. Was it possible to generate a new patchset against releng/9.2? I'd have to concat manually downloadad revisions via svnweb... :-( Thanks a lot, -Harry --------------enig0CA859C26DF2E57AF9889AAA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlICjDoACgkQLDqVQ9VXb8iQuwCfSxH85V+gfuN5AyQpiYb6a6pO QCgAoNECBYHrZ2dUVHjX87YoDK6XyK80 =DDAF -----END PGP SIGNATURE----- --------------enig0CA859C26DF2E57AF9889AAA-- From owner-freebsd-fs@FreeBSD.ORG Wed Aug 7 23:11:00 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EF01A69C; Wed, 7 Aug 2013 23:11:00 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B4FA22137; Wed, 7 Aug 2013 23:11:00 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id kp13so2690153pab.35 for ; Wed, 07 Aug 2013 16:11:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=jEEKILxGJCiC5GjRqevQ4KZ9ci1i3W1Stv24fC1zEMk=; b=v5VhDtcD0Y+kznltF5OTakDZVLAhsl9S1X+v8GrFR/IsLKCD2CwdFvUC3bSt7F0Pjx BQF0MsnP+srIAIWdm4pDkg1rGIkpDiSALOk61j4YsM5ZS7h9HQAhcAka9llAf9cQ4RG2 epZD5ulafR215BblNSlrgifrQVNfUyo0b3+v4Unvbb2nIz3C+THL1wS65VfJOfYMDVfi cBMzD5OeeKpKiDXS8PLDhIpTbm7Urk+UeI0Z+exUIVVx4yVN3moWot2MWVniD98dVJOR kJR0LMjjm0/TMzS4/WPRnCgILmXUD4R0dfKn/fDGuMYKq8BV7VBx03j/NwOiRfN+RjEw l0uA== MIME-Version: 1.0 X-Received: by 10.68.251.234 with SMTP id zn10mr2823951pbc.188.1375917060313; Wed, 07 Aug 2013 16:11:00 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.14.66 with HTTP; Wed, 7 Aug 2013 16:11:00 -0700 (PDT) In-Reply-To: <52028C31.6060908@omnilan.de> References: <20120829060158.GA38721@x2.osted.lan> <20120831052003.GA91340@x2.osted.lan> <20120905201531.GA54452@x2.osted.lan> <20120917140055.GA9037@x2.osted.lan> <52028C31.6060908@omnilan.de> Date: Wed, 7 Aug 2013 16:11:00 -0700 X-Google-Sender-Auth: A-okjY7GCK_xLR5LvQA8bkRpAiU Message-ID: Subject: Re: MPSAFE VFS -- List of upcoming actions From: Kevin Oberman To: Harald Schmalzbauer Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Attilio Rao , FreeBSD FS , FreeBSD current X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 23:11:01 -0000 On Wed, Aug 7, 2013 at 11:04 AM, Harald Schmalzbauer < h.schmalzbauer@omnilan.de> wrote: > Bez=C3=BCglich Attilio Rao's Nachricht vom 14.10.2012 02:27 (localtime): > > On Fri, Sep 21, 2012 at 1:22 AM, Attilio Rao > wrote: > >> On Wed, Sep 19, 2012 at 3:48 AM, Attilio Rao > wrote: > >>> On Fri, Jul 13, 2012 at 12:18 AM, Attilio Rao > wrote: > >>>> 2012/7/4 Attilio Rao : > >>>>> 2012/6/29 Attilio Rao : > >>>>>> As already published several times, according to the following pla= n: > >>>>>> http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS > >>>>>> > >>>>> I still haven't heard from Vivien or Edward, anyway as NTFS is > >>>>> basically only used RO these days (also the mount_ntfs code just > >>>>> permits RO mounting) I stripped all the uncomplete/bogus write > support > >>>>> with the following patch: > >>>>> http://www.freebsd.org/~attilio/ntfs_remove_write.patch > >>>>> > >>>>> This is an attempt to make the code smaller and possibly just focus > on > > ... > > > I've committed the FUSE support into base as r241519. > > Thank you for your great work! > I had used > http://www.freebsd.org/~attilio/fuse_import/fuse_stable9_241030.patch > with releng/9.1. > Some improovements were made in the meantime in head. > I'm not familiar with svn. > Was it possible to generate a new patchset against releng/9.2? I'd have > to concat manually downloadad revisions via svnweb... :-( > > Thanks a lot, > > -Harry > > Already done. All of the changes in head have been back-ported to 9.2-PRERELEASE with the exception of a locking enhancement not available outside of current. You can find it at: https://docs.google.com/file/d/0B9QNUQlebx5UdlhPUTB4TXF6enc/edit?usp=3Dshar= ing The changes were minor, mostly updating line numbers. There was a major update to the new fuse release, but it was rolled back because it would not work with fusefs-libs. Both will need to be updated at the same time. I don't know what the state of any effort to do this might be or how difficult it will be. --=20 R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com From owner-freebsd-fs@FreeBSD.ORG Thu Aug 8 07:17:32 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4D71A98A for ; Thu, 8 Aug 2013 07:17:32 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0D0D22AFC for ; Thu, 8 Aug 2013 07:17:32 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 0539F153434; Thu, 8 Aug 2013 09:17:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7H8TNkv5E9gN; Thu, 8 Aug 2013 09:17:19 +0200 (CEST) Received: from [IPv6:2001:4cb8:3:1:5d33:3a19:2ee6:6e9f] (unknown [IPv6:2001:4cb8:3:1:5d33:3a19:2ee6:6e9f]) by smtp.digiware.nl (Postfix) with ESMTP id 11B9E153433; Thu, 8 Aug 2013 09:17:19 +0200 (CEST) Message-ID: <520345F9.7090508@digiware.nl> Date: Thu, 08 Aug 2013 09:17:13 +0200 From: Willem Jan Withagen Organization: Digiware Management b.v. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Steven Hartland , fs@freebsd.org Subject: Re: Crash while sending ZFS file system References: <520262C6.2060606@digiware.nl> <4467AAF5BA6A450FAC9BD9306110A256@multiplay.co.uk> <52026DC2.8070000@digiware.nl> <5202AB11.205@digiware.nl> <39CF025C25F34968A4AF344142CC7225@multiplay.co.uk> In-Reply-To: <39CF025C25F34968A4AF344142CC7225@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 07:17:32 -0000 On 2013-08-07 23:22, Steven Hartland wrote: > > ----- Original Message ----- From: "Willem Jan Withagen" >> # zfs send -n -v -R zfsraid@box > ... > >> Need origin_guid 16676154253971996192 for zfsraid/home >> Need parent_guid 3602069970101155964 for zfsraid/home/clone_20100925 >> Need parent_guid 3602069970101155964 for zfsraid/home/Software >> Need parent_guid 3602069970101155964 for zfsraid/home/www >> Need parent_guid 3602069970101155964 for zfsraid/home/Media >> Need parent_guid 3602069970101155964 for zfsraid/home/angelic >> Need parent_guid 3602069970101155964 for zfsraid/home/mrtg >> Need parent_guid 3602069970101155964 for zfsraid/home/wjw >> Assertion failed: (progress), file >> /usr/srcs/src9/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c, >> >> line 1318. >> Abort (core dumped) > > I believe the problem you have is that zfsraid/home depends on its > parent guid of 16676154253971996192 which according to your > zfs list is:- > zfsraid/home/clone_20100925@20100925 16676154253971996192 - > > This is a child of zfsraid/home so it will itself dependent on > zfsraid/home creating a cyclic dependency which can't be resolved. > > I suspect zfsraid/home was cloned from zfsraid/somethingelse and > then subsiquently zfsraid/somethingelse was renamed to > zfsraid/home/clone_20100925 creating the cycle. > > The updated patch should had enough extra debug to confirm this. > > If I'm right then simpy renaming zfsraid/home/clone_20100925 to > zfsraid/clone_20100925, so its not under zfsraid/home, should be > enough to remove the cycle and allow the send to complete. I think you are most probably right. I have been experimenting with clones at one time to sort of "clean up" old snapshots.. But one way or another it did not work. I'll patch libzfs and send the resulting output. Is there a way to shortcut the buildproces? Now I just do 'make -DNO_CLEAN -DNOCLEAN buildworld && make installworld' But I have a feeling that there could be a shortcut. --WjW From owner-freebsd-fs@FreeBSD.ORG Thu Aug 8 08:12:56 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AF0432AE for ; Thu, 8 Aug 2013 08:12:56 +0000 (UTC) (envelope-from prvs=19321e062d=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4E51D2DA3 for ; Thu, 8 Aug 2013 08:12:56 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005401189.msg for ; Thu, 08 Aug 2013 09:12:53 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 08 Aug 2013 09:12:53 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=19321e062d=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: fs@freebsd.org Message-ID: <9789E77C6156417980C49B0202673887@multiplay.co.uk> From: "Steven Hartland" To: "Willem Jan Withagen" , References: <520262C6.2060606@digiware.nl> <4467AAF5BA6A450FAC9BD9306110A256@multiplay.co.uk> <52026DC2.8070000@digiware.nl> <5202AB11.205@digiware.nl> <39CF025C25F34968A4AF344142CC7225@multiplay.co.uk> <520345F9.7090508@digiware.nl> Subject: Re: Crash while sending ZFS file system Date: Thu, 8 Aug 2013 09:13:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 08:12:56 -0000 ----- Original Message ----- From: "Willem Jan Withagen" To: "Steven Hartland" ; Sent: Thursday, August 08, 2013 8:17 AM Subject: Re: Crash while sending ZFS file system > On 2013-08-07 23:22, Steven Hartland wrote: >> >> ----- Original Message ----- From: "Willem Jan Withagen" >>> # zfs send -n -v -R zfsraid@box >> ... >> >>> Need origin_guid 16676154253971996192 for zfsraid/home >>> Need parent_guid 3602069970101155964 for zfsraid/home/clone_20100925 >>> Need parent_guid 3602069970101155964 for zfsraid/home/Software >>> Need parent_guid 3602069970101155964 for zfsraid/home/www >>> Need parent_guid 3602069970101155964 for zfsraid/home/Media >>> Need parent_guid 3602069970101155964 for zfsraid/home/angelic >>> Need parent_guid 3602069970101155964 for zfsraid/home/mrtg >>> Need parent_guid 3602069970101155964 for zfsraid/home/wjw >>> Assertion failed: (progress), file >>> /usr/srcs/src9/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_sendrecv.c, >>> >>> line 1318. >>> Abort (core dumped) >> >> I believe the problem you have is that zfsraid/home depends on its >> parent guid of 16676154253971996192 which according to your >> zfs list is:- >> zfsraid/home/clone_20100925@20100925 16676154253971996192 - >> >> This is a child of zfsraid/home so it will itself dependent on >> zfsraid/home creating a cyclic dependency which can't be resolved. >> >> I suspect zfsraid/home was cloned from zfsraid/somethingelse and >> then subsiquently zfsraid/somethingelse was renamed to >> zfsraid/home/clone_20100925 creating the cycle. >> >> The updated patch should had enough extra debug to confirm this. >> >> If I'm right then simpy renaming zfsraid/home/clone_20100925 to >> zfsraid/clone_20100925, so its not under zfsraid/home, should be >> enough to remove the cycle and allow the send to complete. > > I think you are most probably right. > I have been experimenting with clones at one time to sort of "clean up" > old snapshots.. But one way or another it did not work. > > I'll patch libzfs and send the resulting output. > > Is there a way to shortcut the buildproces? > Now I just do > 'make -DNO_CLEAN -DNOCLEAN buildworld && make installworld' > But I have a feeling that there could be a shortcut. Yer the following is all thats required. cd cddl/lib/libzfs && make && make install Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Aug 8 08:31:22 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 60CC7830; Thu, 8 Aug 2013 08:31:22 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from s1.omnilan.de (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ECD5E2ED5; Thu, 8 Aug 2013 08:31:21 +0000 (UTC) Received: from titan.inop.wdn.omnilan.net (titan.inop.wdn.omnilan.net [172.21.3.1]) (authenticated bits=0) by s1.omnilan.de (8.13.8/8.13.8) with ESMTP id r788VFMI094776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Aug 2013 10:31:15 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <52035753.1080006@omnilan.de> Date: Thu, 08 Aug 2013 10:31:15 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Kevin Oberman Subject: Re: MPSAFE VFS -- List of upcoming actions References: <20120829060158.GA38721@x2.osted.lan> <20120831052003.GA91340@x2.osted.lan> <20120905201531.GA54452@x2.osted.lan> <20120917140055.GA9037@x2.osted.lan> <52028C31.6060908@omnilan.de> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBADF1F97E6A532456356F403" Cc: Attilio Rao , FreeBSD FS , FreeBSD current X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 08:31:22 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBADF1F97E6A532456356F403 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bez=C3=BCglich Kevin Oberman's Nachricht vom 08.08.2013 01:11 (localtime= ): > On Wed, Aug 7, 2013 at 11:04 AM, Harald Schmalzbauer < > h.schmalzbauer@omnilan.de> wrote: > >> Bez=C3=BCglich Attilio Rao's Nachricht vom 14.10.2012 02:27 (localtim= e): >>> On Fri, Sep 21, 2012 at 1:22 AM, Attilio Rao >> wrote: >>>> On Wed, Sep 19, 2012 at 3:48 AM, Attilio Rao >> wrote: >>>>> On Fri, Jul 13, 2012 at 12:18 AM, Attilio Rao = >> wrote: >>>>>> 2012/7/4 Attilio Rao : >>>>>>> 2012/6/29 Attilio Rao : >>>>>>>> As already published several times, according to the following p= lan: >>>>>>>> http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS >>>>>>>> >>>>>>> I still haven't heard from Vivien or Edward, anyway as NTFS is >>>>>>> basically only used RO these days (also the mount_ntfs code just >>>>>>> permits RO mounting) I stripped all the uncomplete/bogus write >> support >>>>>>> with the following patch: >>>>>>> http://www.freebsd.org/~attilio/ntfs_remove_write.patch >>>>>>> >>>>>>> This is an attempt to make the code smaller and possibly just foc= us >> on >> >> ... >> >>> I've committed the FUSE support into base as r241519. >> Thank you for your great work! >> I had used >> http://www.freebsd.org/~attilio/fuse_import/fuse_stable9_241030.patch >> with releng/9.1. >> Some improovements were made in the meantime in head. >> I'm not familiar with svn. >> Was it possible to generate a new patchset against releng/9.2? I'd hav= e >> to concat manually downloadad revisions via svnweb... :-( >> >> Thanks a lot, >> >> -Harry >> >> Already done. All of the changes in head have been back-ported to > 9.2-PRERELEASE with the exception of a locking enhancement not availabl= e > outside of current. You can find it at: > https://docs.google.com/file/d/0B9QNUQlebx5UdlhPUTB4TXF6enc/edit?usp=3D= sharing Great, I found accidentally the download-arrow for fuse_stable9_253631.patch after enabling java script - not used to google interfaces... (for those who want to get the patch with fetch/wget/...:=20 ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools/local-patches/RELEN= G_9_2/no_autoapply/fuse_stable9_253631.patch.orig ) There's still only GENERIC for amd64 altered to include fuse by default. Any reason why not i386? I'd not include it in any GENERIC kernel, I'd prefer keeping it loadable... Just for interest, is there a one-liner to get such a patchset out of svn? Looks like the above was done with local sourcetree, not svn internally? Best regards, -Harry --------------enigBADF1F97E6A532456356F403 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlIDV1MACgkQLDqVQ9VXb8gK1QCgnPmClsA2n5SLya5XgNClLYMJ NJcAn0WvKgg2vngB9UFz8KOwYB4fI//h =uKE3 -----END PGP SIGNATURE----- --------------enigBADF1F97E6A532456356F403-- From owner-freebsd-fs@FreeBSD.ORG Thu Aug 8 20:02:15 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 299D8631; Thu, 8 Aug 2013 20:02:15 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E26072F93; Thu, 8 Aug 2013 20:02:14 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id kp13so3953085pab.35 for ; Thu, 08 Aug 2013 13:02:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ZBXuRRbTKp753l88MLYIQlKsrU7YMQ7dr0J3nwjf8xE=; b=zGsUh6PgnKnJO7BP0dnED/1jaDvv7wj8X1TcautD5rtrx8uks2pPnOG7OQ013LS5Wv MOJrNwvenhId35A+tAdL20XQHoplFPd3n5uEAia6ztcbdsMoerRjv/sTBd4p2cBx2K9z M32R9k+SX4E0dGTT1bzxGJcIXodbKCjN/GS1oGN4ghLtMtiA99ee8YNfDC2iLf13EnT0 QvWAk+QjWffXTbCxsU48gkaANvlTqMi5kiSelJFhBku944bSpzn+siGAVD00Q4gz0Dph 84YFod7PKLX5GhINtCoC3XSA7Dnp2hYlOJ0j4l91kAaCnK727LXwzS52bq05d+Kje7uF bLnA== MIME-Version: 1.0 X-Received: by 10.66.102.70 with SMTP id fm6mr7989102pab.57.1375992134500; Thu, 08 Aug 2013 13:02:14 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.14.66 with HTTP; Thu, 8 Aug 2013 13:02:14 -0700 (PDT) In-Reply-To: <52035753.1080006@omnilan.de> References: <20120829060158.GA38721@x2.osted.lan> <20120831052003.GA91340@x2.osted.lan> <20120905201531.GA54452@x2.osted.lan> <20120917140055.GA9037@x2.osted.lan> <52028C31.6060908@omnilan.de> <52035753.1080006@omnilan.de> Date: Thu, 8 Aug 2013 13:02:14 -0700 X-Google-Sender-Auth: ip_vBuaaUcHPGXGegchzaQX-vAk Message-ID: Subject: Re: MPSAFE VFS -- List of upcoming actions From: Kevin Oberman To: Harald Schmalzbauer Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Attilio Rao , FreeBSD FS , FreeBSD current X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 20:02:15 -0000 On Thu, Aug 8, 2013 at 1:31 AM, Harald Schmalzbauer < h.schmalzbauer@omnilan.de> wrote: > Bez=C3=BCglich Kevin Oberman's Nachricht vom 08.08.2013 01:11 (localtime= ): > > On Wed, Aug 7, 2013 at 11:04 AM, Harald Schmalzbauer < > > h.schmalzbauer@omnilan.de> wrote: > > > >> Bez=C3=BCglich Attilio Rao's Nachricht vom 14.10.2012 02:27 (localtim= e): > >>> On Fri, Sep 21, 2012 at 1:22 AM, Attilio Rao > >> wrote: > >>>> On Wed, Sep 19, 2012 at 3:48 AM, Attilio Rao > >> wrote: > >>>>> On Fri, Jul 13, 2012 at 12:18 AM, Attilio Rao > >> wrote: > >>>>>> 2012/7/4 Attilio Rao : > >>>>>>> 2012/6/29 Attilio Rao : > >>>>>>>> As already published several times, according to the following > plan: > >>>>>>>> http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS > >>>>>>>> > >>>>>>> I still haven't heard from Vivien or Edward, anyway as NTFS is > >>>>>>> basically only used RO these days (also the mount_ntfs code just > >>>>>>> permits RO mounting) I stripped all the uncomplete/bogus write > >> support > >>>>>>> with the following patch: > >>>>>>> http://www.freebsd.org/~attilio/ntfs_remove_write.patch > >>>>>>> > >>>>>>> This is an attempt to make the code smaller and possibly just foc= us > >> on > >> > >> ... > >> > >>> I've committed the FUSE support into base as r241519. > >> Thank you for your great work! > >> I had used > >> http://www.freebsd.org/~attilio/fuse_import/fuse_stable9_241030.patch > >> with releng/9.1. > >> Some improovements were made in the meantime in head. > >> I'm not familiar with svn. > >> Was it possible to generate a new patchset against releng/9.2? I'd hav= e > >> to concat manually downloadad revisions via svnweb... :-( > >> > >> Thanks a lot, > >> > >> -Harry > >> > >> Already done. All of the changes in head have been back-ported to > > 9.2-PRERELEASE with the exception of a locking enhancement not availabl= e > > outside of current. You can find it at: > > > https://docs.google.com/file/d/0B9QNUQlebx5UdlhPUTB4TXF6enc/edit?usp=3Dsh= aring > > Great, I found accidentally the download-arrow for > fuse_stable9_253631.patch after enabling java script - not used to > google interfaces... (for those who want to get the patch with > fetch/wget/...: > > ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools/local-patches/RELEN= G_9_2/no_autoapply/fuse_stable9_253631.patch.orig > ) > > There's still only GENERIC for amd64 altered to include fuse by default. > Any reason why not i386? I'd not include it in any GENERIC kernel, I'd > prefer keeping it loadable... > > Just for interest, is there a one-liner to get such a patchset out of > svn? Looks like the above was done with local sourcetree, not svn > internally? > > Best regards, > > -Harry > I only updated the patches Attilio provided several months ago for 9-STABLE, and his patch-set only added the option for amd64. I see no reason that it should not be in i386, as well, but had not noticed since I run amd64 these days. You can certainly try adding the option to GENERIC on an i386 system and see what happens. I suspect it will work fine. If so (and unless I hear a reason not to from Attilio) I'll update the patch-set to do it. Kevin --=20 R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com