From owner-freebsd-fs@FreeBSD.ORG Sun Jun 15 17:23:42 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CFD81065674 for ; Sun, 15 Jun 2008 17:23:42 +0000 (UTC) (envelope-from andrew@thefrog.net) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.184]) by mx1.freebsd.org (Postfix) with ESMTP id CEE908FC14 for ; Sun, 15 Jun 2008 17:23:41 +0000 (UTC) (envelope-from andrew@thefrog.net) Received: by fk-out-0910.google.com with SMTP id k31so3053816fkk.11 for ; Sun, 15 Jun 2008 10:23:40 -0700 (PDT) Received: by 10.82.127.14 with SMTP id z14mr310124buc.67.1213550620372; Sun, 15 Jun 2008 10:23:40 -0700 (PDT) Received: by 10.82.185.16 with HTTP; Sun, 15 Jun 2008 10:23:35 -0700 (PDT) Message-ID: <16a6ef710806151023y58bd905dr3671e76c71aa1f4d@mail.gmail.com> Date: Mon, 16 Jun 2008 03:23:35 +1000 From: "Andrew Hill" Sender: andrew@thefrog.net To: "FreeBSD Mailing List" MIME-Version: 1.0 X-Google-Sender-Auth: d75c9e88c93ea80b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: raidz vdev marked faulted with only one faulted disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2008 17:23:42 -0000 i'm a bit lost here as to exactly what's gone wrong - it seems like it may be a bug in zfs but also entirely likely i'm assuming something i shoudln't or am just not using the zfs tools properly (i rather hope its the latter...) background: i had a system running with 4 zpools. the two that are relevant to this issue are the raidz volumes: - 1x zpool (tank) consisting of a raidz vdev consisting of 7x250 GB slices (each slice on a separate disk) - 1x zpool (tank2) consisting of a raidz vdev consisting of 3x70 GB slices (again, separate disks from each other, but these are slices on the same disks as the other raidz vdev) (this is a cheap home system built out of parts lying around, basically intended to get a lot of storage space out of a bunch of disks with little concern for performance, so no need to point out these problems) the system was originally installed on a ufs partition then migrated onto a raidz zpool (so i was using the kernel and /boot from the ufs drive still, but the system root was on raidz), apart from well-known deadlocks and panics here and there, it generally worked well enough (uptimes of a week or so if i wasn't actively trying to trigger a deadlock/panic) problem: a couple of weeks ago, it completely stopped being able to mount root from zfs, so i booted back into the old ufs partition (which still had whatever world was originally installed on there from my 7.0-release amd64 CD but with an up-to-date -stable kernel) and i discovered that one of my disks (ad12) was now FAULTED. this is one of the disks that affects both raidz vdevs mentioned above (i.e. it has a 250gb slice in tank and a 70gb slice in tank2) so both raidz vdevs were effectively missing one disk device, but both should be able to handle this type of failure... right? i've not yet looked too far into the cause of the failure, though my guess is it relates to the silicon image sil3114 controller that disk was attached to (mainly due to the repuatation those controllers have) though for now i'm trying to figure out the other major issue... from 'zpool import' i can see that this disk (ad12) is marked "FAULTED corrupted data" in the list of 7 drives in tank (i.e. ad12s1d), and the list of 3 drives in tank2 (ad12s1e). in both zpools, the raidz vdev and the whole zpool is then marked "FAULTED corrupted data", despite only one disk in the raidz being FAULTED - my understanding is that it should be DEGRADED... right? example output showing tank2: gutter# zpool import pool: tank2 id: 8036862119610852708 state: FAULTED status: The pool was last accessed by another system. action: The pool cannot be imported due to damaged devices or data. The pool may be active on on another system, but can be imported using the '-f' flag. see: http://www.sun.com/msg/ZFS-8000-EY config: tank2 FAULTED corrupted data raidz1 FAULTED corrupted data ad8s1e ONLINE ad10s1e ONLINE ad12s1e FAULTED corrupted data tank2 is/was a zpool created as a single raidz vdev of 3 slices as shown above, so it seems like the failure/loss of one disk shouldn't be causing it to get marked FAULTED. tank is the same but with 7 drives (6 ONLINE, 1 FAULTED)... since the zpools were never exported (i'm unable to mount the root file system on the zpool to export either of them...) they obviously show up the errors above about being last accessed by another system, so attempting to override that (zpool import -f tank or tank2) gives the following messages on the console: ZFS: vdev failure, zpool=tank2 type=vdev.no_replicas ZFS: failed to load zpool tank2 cannot import 'tank2': permission denied when i first booted into the old ufs drive that the zpools were created from, they showed up on that system in zpool list (since they'd not been exported after i set it up to use one as the root fs), and zpool status told me to see: http://www.sun.com/msg/ZFS-8000-5E, which is about zpools that have a faulted device and no redundancy - *very* odd to see on a raidz vdev i've also tried completely removing the faulted disk with no better result, and removing two drives causes it to show up as UNAVAIL (as expected) or a "panic: dangling dbufs" when i try to 'zpool import', though i suspect this might be memory related (i've also been trying all of this on a second motherboard, which i can only supply with 512 MB RAM) i've tried various different combinations - hardware - two different motherboards (with different cpu and ram, the only thing common to all systems is a new sata controller - promise chip PDC20376 - to replace the silicon image sata controller so that i can put all 7 drives into the system) - software - a fresh FreeBSD install on a new hard drive (from a 7.0 i386 CD i downloaded about 3 months ago, and then again after updating to the latest -stable source), as well as the system i mentioned earlier on my boot/kernel drive, which had the latest amd64 kernel built on my zfs system but hadn't had the userland updated since 7.0 amd64 install) when i first set up the system, i tested out the behaviour of removing a drive from a raidz vdev, and definitely saw it enter the DEGRADED state, though i did not try exporting and re-importing in this state, but according to the sun zfs documentation this should be possible (i realise this doesn't mean its in the bsd port, but i've not found anything to confirm this specifically is/isn't possible) so my question is - is this a bug in zfs that is causing the raidz to be faulted when one device is faulted/corrupted (would have to be under specific conditions, since raidz vdevs can definitely go between DEGRADED and ONLINE states just fine in general), or am i misusing the zfs utilities or making invalid assumptions, e.g. is there some other method of importing or perhaps scrubbing/resilvering prior to importing that i'm missing? Andrew From owner-freebsd-fs@FreeBSD.ORG Sun Jun 15 17:59:21 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67A611065678 for ; Sun, 15 Jun 2008 17:59:21 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A4B418FC15; Sun, 15 Jun 2008 17:59:19 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48555878.9070301@FreeBSD.org> Date: Sun, 15 Jun 2008 19:59:20 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Randy Bush References: <48532183.2040306@psg.com> In-Reply-To: <48532183.2040306@psg.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.ORG Subject: Re: zfs dump to non-zfs host X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2008 17:59:21 -0000 Randy Bush wrote: > currently, my dump server is a large non-zfs raid to which i use dump > over ssh to a remote host, as in > > /sbin/dump 0Luaf - /dev/twed0s1a | $SSH $BSYS "/bin/cat > $DDIR/base" > > now i have a zfs host that i want to dump to this server. yes, i know i > can snapshot on the zfs system itself. but what if it goes completely > dead? it is in an earthquake zone, ... > > /sbin/dump does not work, of course. > > files created with zsend might not be decodable in a future version, so > i can not zsend | to it. If this is the case then presumably there will be a migration tool. zfs sending to a file is the officially recommended method. Kris From owner-freebsd-fs@FreeBSD.ORG Sun Jun 15 18:37:20 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2F0D1065670; Sun, 15 Jun 2008 18:37:20 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id C9F2D8FC1F; Sun, 15 Jun 2008 18:37:20 +0000 (UTC) (envelope-from randy@psg.com) Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1K7x6O-000H7B-Gx; Sun, 15 Jun 2008 18:37:20 +0000 Message-ID: <4855615E.6070603@psg.com> Date: Mon, 16 Jun 2008 03:37:18 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Kris Kennaway References: <48532183.2040306@psg.com> <48555878.9070301@FreeBSD.org> In-Reply-To: <48555878.9070301@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.ORG Subject: Re: zfs dump to non-zfs host X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2008 18:37:21 -0000 >> files created with zsend might not be decodable in a future version, so >> i can not zsend | to it. > If this is the case then presumably there will be a migration tool. zfs > sending to a file is the officially recommended method. that would be alright. but the man page is pretty direct, brutal, and negative; > The format of the stream is evolving. No backwards compatibility is > guaranteed. You may not be able to receive your streams on future ver- > sions of ZFS. this is not very reassuring. randy From owner-freebsd-fs@FreeBSD.ORG Sun Jun 15 19:27:50 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78A4210656FD for ; Sun, 15 Jun 2008 19:27:50 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 209C58FC1D for ; Sun, 15 Jun 2008 19:27:50 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 0CF921CC060; Sun, 15 Jun 2008 12:27:50 -0700 (PDT) Date: Sun, 15 Jun 2008 12:27:50 -0700 From: Jeremy Chadwick To: Randy Bush Message-ID: <20080615192750.GA14559@eos.sc1.parodius.com> References: <48532183.2040306@psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48532183.2040306@psg.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-fs@FreeBSD.ORG Subject: Re: zfs dump to non-zfs host X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2008 19:27:50 -0000 On Sat, Jun 14, 2008 at 10:40:19AM +0900, Randy Bush wrote: > currently, my dump server is a large non-zfs raid to which i use dump > over ssh to a remote host, as in > > /sbin/dump 0Luaf - /dev/twed0s1a | $SSH $BSYS "/bin/cat > $DDIR/base" > > now i have a zfs host that i want to dump to this server. yes, i know i > can snapshot on the zfs system itself. but what if it goes completely > dead? it is in an earthquake zone, ... > > /sbin/dump does not work, of course. > > files created with zsend might not be decodable in a future version, so > i can not zsend | to it. The only two options I see are "zfs send" (which you've covered), and using rsync for that host. We switched to rsync exclusively (regardless of fuilesystem) due to dump -L becoming slower and slower over time on UFS2 filesystems (a known problem), plus more or less deadlocking the system while it makes the snapshot. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Sun Jun 15 20:02:36 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70AD01065676 for ; Sun, 15 Jun 2008 20:02:36 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B16BD8FC1A; Sun, 15 Jun 2008 20:02:35 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4855755C.6010201@FreeBSD.org> Date: Sun, 15 Jun 2008 22:02:36 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Randy Bush References: <48532183.2040306@psg.com> <48555878.9070301@FreeBSD.org> <4855615E.6070603@psg.com> In-Reply-To: <4855615E.6070603@psg.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.ORG Subject: Re: zfs dump to non-zfs host X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2008 20:02:36 -0000 Randy Bush wrote: >>> files created with zsend might not be decodable in a future version, so >>> i can not zsend | to it. >> If this is the case then presumably there will be a migration tool. zfs >> sending to a file is the officially recommended method. > > that would be alright. but the man page is pretty direct, brutal, and > negative; > >> The format of the stream is evolving. No backwards compatibility is >> guaranteed. You may not be able to receive your streams on future ver- >> sions of ZFS. > > this is not very reassuring. You'll have to take this up with the ZFS developers. Kris From owner-freebsd-fs@FreeBSD.ORG Mon Jun 16 00:04:33 2008 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B29C1065673; Mon, 16 Jun 2008 00:04:33 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3014B8FC12; Mon, 16 Jun 2008 00:04:33 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5G04Xai091249; Mon, 16 Jun 2008 00:04:33 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5G04Xq1091245; Mon, 16 Jun 2008 00:04:33 GMT (envelope-from gavin) Date: Mon, 16 Jun 2008 00:04:33 GMT Message-Id: <200806160004.m5G04Xq1091245@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-fs@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/124621: [ext3] Cannot mount ext2fs partition X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 00:04:33 -0000 Old Synopsis: Cannot mount ext2fs partition New Synopsis: [ext3] Cannot mount ext2fs partition Responsible-Changed-From-To: freebsd-i386->freebsd-fs Responsible-Changed-By: gavin Responsible-Changed-When: Mon Jun 16 00:03:20 UTC 2008 Responsible-Changed-Why: This doesn't sound -i386 specific http://www.freebsd.org/cgi/query-pr.cgi?pr=124621 From owner-freebsd-fs@FreeBSD.ORG Mon Jun 16 04:00:29 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8322C1065672; Mon, 16 Jun 2008 04:00:29 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id EDA0A8FC2B; Mon, 16 Jun 2008 04:00:28 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.14.3/8.14.3) with ESMTP id m5G3gwiE098237; Mon, 16 Jun 2008 05:42:58 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.3/8.14.3/Submit) id m5G3gwIK098234; Sun, 15 Jun 2008 23:42:58 -0400 (EDT) (envelope-from cracauer) Date: Sun, 15 Jun 2008 23:42:58 -0400 From: Martin Cracauer To: Kris Kennaway Message-ID: <20080616034258.GA94873@cons.org> References: <20080118120140.2a8170a0@dev> <47921931.9050606@FreeBSD.org> <47921AE2.1060004@FreeBSD.org> <20080301220924.72bf355d@dev.citybikes.cz> <47C9C912.1020700@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47C9C912.1020700@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@FreeBSD.ORG, cracauer@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, maxim@FreeBSD.ORG Subject: Re: infinite loop when copying to ext2fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 04:00:29 -0000 Kris Kennaway wrote on Sat, Mar 01, 2008 at 10:22:26PM +0100: > Jakub Siroky wrote: > >I've just confirmed the same situation on 6.2-RELEASE amd64/GENERIC. I > >did not noticed it before because I started using ext2fs extensively > >some months ago. > > > >Regards, > >Jakub > > > >On Sat, 19 Jan 2008 16:44:34 +0100 > >Kris Kennaway wrote: > > > >>Kris Kennaway wrote: > >>>Jakub Siroky wrote: > >>>>I have two large ext2fs partitions (368 and 313GB) to hold data > >>>>shared between several OSes. While there were no problems on > >>>>6-STABLE branch I was quite disappointed after upgrade to > >>>>7-STABLE. Whenever I copy/write to ext2fs partition the system > >>>>freezes totally without crashdump. So I set debugging settings to > >>>>kernel config (DEBUG,WITNESS,..) and in console I reproduced error > >>>>situation ending with full screen of unstoppable running text with > >>>>lot of memory addresses and a few recognisable words: 'new block > >>>>bit set for ext already' - again with no crashdump. Then I have > >>>>formatted 1GB partition with ext2fs and the problem on this small > >>>>partition appears only sometimes. > >>>OK, I am able to reproduce this. > >>> > >>>Kris > >>> > >>Is anyone able to look at this? I could not spot a candidate change > >>that has not been merged to 6.x. > >> > >>Kris > > > > > > Sounds like it may have been broken by the change to ext2_bitops.h by > cracauer. Can you confirm whether backing out 1.2.2.1 fixes it? I don't think my change can cause a new endless loop. I only reversed the order of tests to ensure we don't overrun a page bounddary (into possibly unmapped space). - while(*p == ~0U && ofs < sz) { + while(ofs < sz && *p == ~0U) { It is, however, likely that the code was buggy in the first place. Linux has replaced all this (the allocation code). Also note that the code I fixed is amd64 only. If the endless loop appears on i386 it's something else. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-fs@FreeBSD.ORG Mon Jun 16 09:27:57 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 969131065673; Mon, 16 Jun 2008 09:27:57 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E9E958FC1D; Mon, 16 Jun 2008 09:27:54 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48563219.9070306@FreeBSD.org> Date: Mon, 16 Jun 2008 11:27:53 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Martin Cracauer References: <20080118120140.2a8170a0@dev> <47921931.9050606@FreeBSD.org> <47921AE2.1060004@FreeBSD.org> <20080301220924.72bf355d@dev.citybikes.cz> <47C9C912.1020700@FreeBSD.org> <20080616034258.GA94873@cons.org> In-Reply-To: <20080616034258.GA94873@cons.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.ORG, cracauer@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, maxim@FreeBSD.ORG Subject: Re: infinite loop when copying to ext2fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 09:27:57 -0000 Martin Cracauer wrote: > Kris Kennaway wrote on Sat, Mar 01, 2008 at 10:22:26PM +0100: >> Jakub Siroky wrote: >>> I've just confirmed the same situation on 6.2-RELEASE amd64/GENERIC. I >>> did not noticed it before because I started using ext2fs extensively >>> some months ago. >>> >>> Regards, >>> Jakub >>> >>> On Sat, 19 Jan 2008 16:44:34 +0100 >>> Kris Kennaway wrote: >>> >>>> Kris Kennaway wrote: >>>>> Jakub Siroky wrote: >>>>>> I have two large ext2fs partitions (368 and 313GB) to hold data >>>>>> shared between several OSes. While there were no problems on >>>>>> 6-STABLE branch I was quite disappointed after upgrade to >>>>>> 7-STABLE. Whenever I copy/write to ext2fs partition the system >>>>>> freezes totally without crashdump. So I set debugging settings to >>>>>> kernel config (DEBUG,WITNESS,..) and in console I reproduced error >>>>>> situation ending with full screen of unstoppable running text with >>>>>> lot of memory addresses and a few recognisable words: 'new block >>>>>> bit set for ext already' - again with no crashdump. Then I have >>>>>> formatted 1GB partition with ext2fs and the problem on this small >>>>>> partition appears only sometimes. >>>>> OK, I am able to reproduce this. >>>>> >>>>> Kris >>>>> >>>> Is anyone able to look at this? I could not spot a candidate change >>>> that has not been merged to 6.x. >>>> >>>> Kris >>> >> Sounds like it may have been broken by the change to ext2_bitops.h by >> cracauer. Can you confirm whether backing out 1.2.2.1 fixes it? > > I don't think my change can cause a new endless loop. > > I only reversed the order of tests to ensure we don't overrun a page > bounddary (into possibly unmapped space). > > - while(*p == ~0U && ofs < sz) { > + while(ofs < sz && *p == ~0U) { > > It is, however, likely that the code was buggy in the first place. > Linux has replaced all this (the allocation code). > > Also note that the code I fixed is amd64 only. If the endless loop > appears on i386 it's something else. > > Martin It is amd64 only. I am able to reproduce using the method in the original mails, can you? Kris From owner-freebsd-fs@FreeBSD.ORG Mon Jun 16 11:06:54 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 679111065674 for ; Mon, 16 Jun 2008 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 57C378FC20 for ; Mon, 16 Jun 2008 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5GB6sD2036700 for ; Mon, 16 Jun 2008 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5GB6rjQ036696 for freebsd-fs@FreeBSD.org; Mon, 16 Jun 2008 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Jun 2008 11:06:53 GMT Message-Id: <200806161106.m5GB6rjQ036696@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 11:06:54 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o kern/116170 fs [panic] Kernel panic when mounting /tmp o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t 6 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o bin/118249 fs mv(1): moving a directory changes its mtime o kern/124621 fs [ext3] Cannot mount ext2fs partition 7 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Jun 16 12:16:11 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EF551065670 for ; Mon, 16 Jun 2008 12:16:11 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 31C908FC15 for ; Mon, 16 Jun 2008 12:16:10 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.14.3/8.14.3) with ESMTP id m5GCG9F7027079; Mon, 16 Jun 2008 14:16:09 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.14.3/8.14.3/Submit) id m5GCG9Zp027078; Mon, 16 Jun 2008 08:16:09 -0400 (EDT) (envelope-from cracauer) Date: Mon, 16 Jun 2008 08:16:09 -0400 From: Martin Cracauer To: Kris Kennaway Message-ID: <20080616121609.GA26978@cons.org> References: <20080118120140.2a8170a0@dev> <47921931.9050606@FreeBSD.org> <47921AE2.1060004@FreeBSD.org> <20080301220924.72bf355d@dev.citybikes.cz> <47C9C912.1020700@FreeBSD.org> <20080616034258.GA94873@cons.org> <48563219.9070306@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48563219.9070306@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: maxim@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-fs@FreeBSD.org, cracauer@FreeBSD.org, Martin Cracauer Subject: Re: infinite loop when copying to ext2fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 12:16:11 -0000 Kris Kennaway wrote on Mon, Jun 16, 2008 at 11:27:53AM +0200: > Martin Cracauer wrote: > >Kris Kennaway wrote on Sat, Mar 01, 2008 at 10:22:26PM +0100: > >>Jakub Siroky wrote: > >>>I've just confirmed the same situation on 6.2-RELEASE amd64/GENERIC. I > >>>did not noticed it before because I started using ext2fs extensively > >>>some months ago. > >>> > >>>Regards, > >>>Jakub > >>> > >>>On Sat, 19 Jan 2008 16:44:34 +0100 > >>>Kris Kennaway wrote: > >>> > >>>>Kris Kennaway wrote: > >>>>>Jakub Siroky wrote: > >>>>>>I have two large ext2fs partitions (368 and 313GB) to hold data > >>>>>>shared between several OSes. While there were no problems on > >>>>>>6-STABLE branch I was quite disappointed after upgrade to > >>>>>>7-STABLE. Whenever I copy/write to ext2fs partition the system > >>>>>>freezes totally without crashdump. So I set debugging settings to > >>>>>>kernel config (DEBUG,WITNESS,..) and in console I reproduced error > >>>>>>situation ending with full screen of unstoppable running text with > >>>>>>lot of memory addresses and a few recognisable words: 'new block > >>>>>>bit set for ext already' - again with no crashdump. Then I have > >>>>>>formatted 1GB partition with ext2fs and the problem on this small > >>>>>>partition appears only sometimes. > >>>>>OK, I am able to reproduce this. > >>>>> > >>>>>Kris > >>>>> > >>>>Is anyone able to look at this? I could not spot a candidate change > >>>>that has not been merged to 6.x. > >>>> > >>>>Kris > >>> > >>Sounds like it may have been broken by the change to ext2_bitops.h by > >>cracauer. Can you confirm whether backing out 1.2.2.1 fixes it? > > > >I don't think my change can cause a new endless loop. > > > >I only reversed the order of tests to ensure we don't overrun a page > >bounddary (into possibly unmapped space). > > > >- while(*p == ~0U && ofs < sz) { > >+ while(ofs < sz && *p == ~0U) { > > > >It is, however, likely that the code was buggy in the first place. > >Linux has replaced all this (the allocation code). > > > >Also note that the code I fixed is amd64 only. If the endless loop > >appears on i386 it's something else. > > > >Martin > > It is amd64 only. I am able to reproduce using the method in the > original mails, can you? Didn't try yet, but I did get a probably unrelated panic on ext2fs just last week :-) I'll fire it up this week. How big does the partition have to be to show the problem in this bug? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-fs@FreeBSD.ORG Mon Jun 16 12:54:05 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C726106568C; Mon, 16 Jun 2008 12:54:05 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 21C6C8FC41; Mon, 16 Jun 2008 12:54:01 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48566269.2050001@FreeBSD.org> Date: Mon, 16 Jun 2008 14:54:01 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Martin Cracauer References: <20080118120140.2a8170a0@dev> <47921931.9050606@FreeBSD.org> <47921AE2.1060004@FreeBSD.org> <20080301220924.72bf355d@dev.citybikes.cz> <47C9C912.1020700@FreeBSD.org> <20080616034258.GA94873@cons.org> <48563219.9070306@FreeBSD.org> <20080616121609.GA26978@cons.org> In-Reply-To: <20080616121609.GA26978@cons.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, cracauer@FreeBSD.org, freebsd-stable@FreeBSD.org, maxim@FreeBSD.org Subject: Re: infinite loop when copying to ext2fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 12:54:05 -0000 Martin Cracauer wrote: > Kris Kennaway wrote on Mon, Jun 16, 2008 at 11:27:53AM +0200: >> Martin Cracauer wrote: >>> Kris Kennaway wrote on Sat, Mar 01, 2008 at 10:22:26PM +0100: >>>> Jakub Siroky wrote: >>>>> I've just confirmed the same situation on 6.2-RELEASE amd64/GENERIC. I >>>>> did not noticed it before because I started using ext2fs extensively >>>>> some months ago. >>>>> >>>>> Regards, >>>>> Jakub >>>>> >>>>> On Sat, 19 Jan 2008 16:44:34 +0100 >>>>> Kris Kennaway wrote: >>>>> >>>>>> Kris Kennaway wrote: >>>>>>> Jakub Siroky wrote: >>>>>>>> I have two large ext2fs partitions (368 and 313GB) to hold data >>>>>>>> shared between several OSes. While there were no problems on >>>>>>>> 6-STABLE branch I was quite disappointed after upgrade to >>>>>>>> 7-STABLE. Whenever I copy/write to ext2fs partition the system >>>>>>>> freezes totally without crashdump. So I set debugging settings to >>>>>>>> kernel config (DEBUG,WITNESS,..) and in console I reproduced error >>>>>>>> situation ending with full screen of unstoppable running text with >>>>>>>> lot of memory addresses and a few recognisable words: 'new block >>>>>>>> bit set for ext already' - again with no crashdump. Then I have >>>>>>>> formatted 1GB partition with ext2fs and the problem on this small >>>>>>>> partition appears only sometimes. >>>>>>> OK, I am able to reproduce this. >>>>>>> >>>>>>> Kris >>>>>>> >>>>>> Is anyone able to look at this? I could not spot a candidate change >>>>>> that has not been merged to 6.x. >>>>>> >>>>>> Kris >>>> Sounds like it may have been broken by the change to ext2_bitops.h by >>>> cracauer. Can you confirm whether backing out 1.2.2.1 fixes it? >>> I don't think my change can cause a new endless loop. >>> >>> I only reversed the order of tests to ensure we don't overrun a page >>> bounddary (into possibly unmapped space). >>> >>> - while(*p == ~0U && ofs < sz) { >>> + while(ofs < sz && *p == ~0U) { >>> >>> It is, however, likely that the code was buggy in the first place. >>> Linux has replaced all this (the allocation code). >>> >>> Also note that the code I fixed is amd64 only. If the endless loop >>> appears on i386 it's something else. >>> >>> Martin >> It is amd64 only. I am able to reproduce using the method in the >> original mails, can you? > > Didn't try yet, but I did get a probably unrelated panic on ext2fs > just last week :-) I'll fire it up this week. > > How big does the partition have to be to show the problem in this bug? Sorry, I don't remember. I probably tried it on a md that was a couple of GB. Kris From owner-freebsd-fs@FreeBSD.ORG Mon Jun 16 16:24:53 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7392106564A; Mon, 16 Jun 2008 16:24:53 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 551E88FC17; Mon, 16 Jun 2008 16:24:53 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.2/8.14.2) with ESMTP id m5GGPMFq031888; Mon, 16 Jun 2008 11:25:22 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.2/8.14.2/Submit) id m5GGPMQ9031887; Mon, 16 Jun 2008 11:25:22 -0500 (CDT) (envelope-from brooks) Date: Mon, 16 Jun 2008 11:25:22 -0500 From: Brooks Davis To: Jeremy Chadwick Message-ID: <20080616162522.GA31835@lor.one-eyed-alien.net> References: <48532183.2040306@psg.com> <20080615192750.GA14559@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20080615192750.GA14559@eos.sc1.parodius.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Mon, 16 Jun 2008 11:25:22 -0500 (CDT) Cc: Randy Bush , freebsd-fs@freebsd.org Subject: Re: zfs dump to non-zfs host X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2008 16:24:54 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 15, 2008 at 12:27:50PM -0700, Jeremy Chadwick wrote: > On Sat, Jun 14, 2008 at 10:40:19AM +0900, Randy Bush wrote: > > currently, my dump server is a large non-zfs raid to which i use dump > > over ssh to a remote host, as in > >=20 > > /sbin/dump 0Luaf - /dev/twed0s1a | $SSH $BSYS "/bin/cat > $DDIR/base" > >=20 > > now i have a zfs host that i want to dump to this server. yes, i know i > > can snapshot on the zfs system itself. but what if it goes completely > > dead? it is in an earthquake zone, ... > >=20 > > /sbin/dump does not work, of course. > >=20 > > files created with zsend might not be decodable in a future version, so > > i can not zsend | to it. >=20 > The only two options I see are "zfs send" (which you've covered), and > using rsync for that host. We switched to rsync exclusively (regardless > of fuilesystem) due to dump -L becoming slower and slower over time on > UFS2 filesystems (a known problem), plus more or less deadlocking the > system while it makes the snapshot. Clearly someone needs to teach libarchive to speak zfs send-recieve so peop= le can save these things in tarballs. 1/2 :-) -- Brooks --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFIVpPxXY6L6fI4GtQRAqvUAJ9kowrugZgyNLQedOimaBFiX3HuAACePFd3 wIgNX5J0aZj4gk/j+Xj6xho= =D/WZ -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- From owner-freebsd-fs@FreeBSD.ORG Tue Jun 17 03:16:26 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E12671065670 for ; Tue, 17 Jun 2008 03:16:26 +0000 (UTC) (envelope-from ernst.winter@t-online.de) Received: from mailout07.t-online.de (mailout07.t-online.de [194.25.134.83]) by mx1.freebsd.org (Postfix) with ESMTP id A26FC8FC17 for ; Tue, 17 Jun 2008 03:16:26 +0000 (UTC) (envelope-from ernst.winter@t-online.de) Received: from fwd27.aul.t-online.de by mailout07.sul.t-online.de with smtp id 1K8RRK-00056h-02; Tue, 17 Jun 2008 05:00:58 +0200 Received: from lobo.ewinter.org (G0B0MrZYwh2EDn4dCpeihICZQ4r-xzGhF6sdiLdBcea-V-m9rQWOKQMveIT83W8Z-O@[91.48.202.200]) by fwd27.aul.t-online.de with esmtp id 1K8RRH-1r8GaO0; Tue, 17 Jun 2008 05:00:55 +0200 Received: from lobo.ewinter.org (localhost [127.0.0.1]) by lobo.ewinter.org (8.14.2/8.14.1) with ESMTP id m5H30akt018749 for ; Tue, 17 Jun 2008 05:00:39 +0200 (CEST) (envelope-from ewinter@lobo.ewinter.org) Received: (from ewinter@localhost) by lobo.ewinter.org (8.14.2/8.14.1/Submit) id m5H30aRq018748 for freebsd-fs@freebsd.org; Tue, 17 Jun 2008 05:00:36 +0200 (CEST) (envelope-from ewinter) Date: Tue, 17 Jun 2008 05:00:34 +0200 From: ernst.winter@t-online.de (Ernst W. Winter) To: freebsd-fs@freebsd.org Message-ID: <20080617030034.GA18701@ewinter.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Phone: + 49-7734-936-247 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.ewinter.org 7.0-STABLE FreeBSD 7.0-STABLE User-Agent: Mutt/1.5.18 (2008-05-17) X-ID: G0B0MrZYwh2EDn4dCpeihICZQ4r-xzGhF6sdiLdBcea-V-m9rQWOKQMveIT83W8Z-O X-TOI-MSGID: 961ded3c-49c8-4371-9ae3-f5d17f7481aa Subject: installation of zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2008 03:16:27 -0000 Hello, can anyone pount me to a document on how to install zfs with FreeBSD? I am a "end user" mainly, but have enough knowledge to perform the installation. Ihave tried it on a external HD a while back and then screwd somewher along the line ans dleted the system again. I only need a plain installation, no Raid or anything like the. The HD is 230GIG and the partitions are at the moment a 4GIG root with a minimal installation and 4GIG for swap. Thanks in advance foir any help. Ernst -- ================================================== Mail just Ascii plain text. HTML & Base64 is spam email = nur reiner Text. HTML & Base64 sind SPAM From owner-freebsd-fs@FreeBSD.ORG Tue Jun 17 07:05:51 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79925106566C for ; Tue, 17 Jun 2008 07:05:51 +0000 (UTC) (envelope-from mark@legios.org) Received: from bade.legios.org (ppp198-172.static.internode.on.net [59.167.198.172]) by mx1.freebsd.org (Postfix) with ESMTP id 31A6D8FC22 for ; Tue, 17 Jun 2008 07:05:51 +0000 (UTC) (envelope-from mark@legios.org) Received: from localhost (unknown [192.168.0.17]) by bade.legios.org (Postfix) with ESMTP id 176C41AD018; Tue, 17 Jun 2008 13:47:33 +1000 (EST) X-Virus-Scanned: amavisd-new at legios.org Received: from bade.legios.org ([192.168.0.17]) by localhost (legios.org [192.168.0.17]) (amavisd-new, port 10024) with ESMTP id QPLRQiLTlxEd; Tue, 17 Jun 2008 13:46:55 +1000 (EST) Received: from legios.org (unknown [192.168.0.13]) by bade.legios.org (Postfix) with ESMTP id 615DB1AD012; Tue, 17 Jun 2008 13:46:55 +1000 (EST) Received: from 150.101.214.246 (SquirrelMail authenticated user mark) by legios.org with HTTP; Tue, 17 Jun 2008 13:46:55 +1000 (EST) Message-ID: <30337.150.101.214.246.1213674415.squirrel@legios.org> Date: Tue, 17 Jun 2008 13:46:55 +1000 (EST) From: "Mark Gladman(legios.org)" To: "Ernst W. Winter" User-Agent: SquirrelMail/1.4.11 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-fs@freebsd.org Subject: Re: installation of zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2008 07:05:51 -0000 > Hello, > > can anyone pount me to a document on how to install zfs with > FreeBSD? > > I am a "end user" mainly, but have enough knowledge to perform > the installation. Ihave tried it on a external HD a while back > and then screwd somewher along the line ans dleted the system > again. I only need a plain installation, no Raid or anything like > the. > > The HD is 230GIG and the partitions are at the moment a 4GIG root > with a minimal installation and 4GIG for swap. > > Thanks in advance foir any help. > > Ernst > > -- > ================================================== > Mail just Ascii plain text. HTML & Base64 is spam > email = nur reiner Text. HTML & Base64 sind SPAM > > _______________________________________________ > 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" > > Hey there, http://wiki.freebsd.org/ZFSQuickStartGuide is a good quickstart guide. I also recommend reading through http://wiki.freebsd.org/ZFS for additional information. Cheers, Mark From owner-freebsd-fs@FreeBSD.ORG Tue Jun 17 20:21:15 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFBE3106564A for ; Tue, 17 Jun 2008 20:21:15 +0000 (UTC) (envelope-from ernst.winter@t-online.de) Received: from mailout08.t-online.de (mailout08.t-online.de [194.25.134.20]) by mx1.freebsd.org (Postfix) with ESMTP id 5D1808FC0A for ; Tue, 17 Jun 2008 20:21:15 +0000 (UTC) (envelope-from ernst.winter@t-online.de) Received: from fwd26.aul.t-online.de by mailout08.sul.t-online.de with smtp id 1K8hfy-0007qk-03; Tue, 17 Jun 2008 22:21:10 +0200 Received: from lobo.ewinter.org (GuF-NTZBrh9BxjSF4uukNZsVzqefqyIXbqeSoLsqzz6zZR0GcInHVZeWHPWPU1Qw7H@[91.48.202.200]) by fwd26.aul.t-online.de with esmtp id 1K8hfe-1RSwYi0; Tue, 17 Jun 2008 22:20:50 +0200 Received: from lobo.ewinter.org (localhost [127.0.0.1]) by lobo.ewinter.org (8.14.2/8.14.1) with ESMTP id m5HKKU7b002033; Tue, 17 Jun 2008 22:20:33 +0200 (CEST) (envelope-from ewinter@lobo.ewinter.org) Received: (from ewinter@localhost) by lobo.ewinter.org (8.14.2/8.14.1/Submit) id m5HKKTwQ002032; Tue, 17 Jun 2008 22:20:29 +0200 (CEST) (envelope-from ewinter) Date: Tue, 17 Jun 2008 22:20:26 +0200 From: ernst.winter@t-online.de (Ernst W. Winter) To: "Mark Gladman(legios.org)" Message-ID: <20080617202026.GA1997@ewinter.org> References: <26377.150.101.214.246.1213676733.squirrel@legios.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26377.150.101.214.246.1213676733.squirrel@legios.org> X-Phone: + 49-7734-936-247 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.ewinter.org 7.0-STABLE FreeBSD 7.0-STABLE User-Agent: Mutt/1.5.18 (2008-05-17) X-ID: GuF-NTZBrh9BxjSF4uukNZsVzqefqyIXbqeSoLsqzz6zZR0GcInHVZeWHPWPU1Qw7H X-TOI-MSGID: 36e0e7f9-4502-4d39-b251-c3a4440cb8d6 Cc: freebsd-fs@freebsd.org Subject: Re: installation of zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2008 20:21:15 -0000 On Tue, 17 Jun 2008, Mark Gladman(legios.org) wrote: [cut] > >> Hey there, > >> > >> http://wiki.freebsd.org/ZFSQuickStartGuide is a good quickstart guide. > >> > > Thanks, just had a look and looks good, ecept for this: > > > > zpool create tank raidz da0 da1 da2 > > > > Does it have to have "raidz"? > > > >> I also recommend reading through http://wiki.freebsd.org/ZFS for > >> additional information. > >> > > Thank you, will do that too. > > > > I will have a bit more time this afternoon and then try to get it > > going again as I try to setup with this HD a new one with the new > > kde4. > > > >> Cheers, > > > > Thanks again, > > > >> Mark > >> > > Ernst > > > Hm.. Not sure my messages are actually going to the mailing > list (given you responded and my email hasn't shown up on it > yet). > well this one will. > In any case, no, if you don't want there to be any raid etc. > just an array of disks you can use zpool create tank da0 da1 > da2. (if I remember correctly - I don't have a machine with me > at work I can test it on). > > http://www.freebsd.org/cgi/man.cgi?query=zpool&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html > ans > http://www.freebsd.org/cgi/man.cgi?query=zfs&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html > are fairly digestable too, if you get the chance. > Got it all going and then compiled it all with make buildworld and kernel, when I try to restart in single user mode I don't have the /usr directory. What could have happen? > Cheers! > Mark > Ernst > > -- ================================================== Mail just Ascii plain text. HTML & Base64 is spam email = nur reiner Text. HTML & Base64 sind SPAM From owner-freebsd-fs@FreeBSD.ORG Tue Jun 17 21:32:18 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CAF9106566C for ; Tue, 17 Jun 2008 21:32:18 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4538A8FC1D for ; Tue, 17 Jun 2008 21:32:18 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 2B94B1CC07A; Tue, 17 Jun 2008 14:32:18 -0700 (PDT) Date: Tue, 17 Jun 2008 14:32:18 -0700 From: Jeremy Chadwick To: "Ernst W. Winter" Message-ID: <20080617213218.GA27283@eos.sc1.parodius.com> References: <26377.150.101.214.246.1213676733.squirrel@legios.org> <20080617202026.GA1997@ewinter.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080617202026.GA1997@ewinter.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org Subject: Re: installation of zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2008 21:32:18 -0000 On Tue, Jun 17, 2008 at 10:20:26PM +0200, Ernst W. Winter wrote: > On Tue, 17 Jun 2008, Mark Gladman(legios.org) wrote: > > [cut] > > >> Hey there, > > >> > > >> http://wiki.freebsd.org/ZFSQuickStartGuide is a good quickstart guide. > > >> > > > Thanks, just had a look and looks good, ecept for this: > > > > > > zpool create tank raidz da0 da1 da2 > > > > > > Does it have to have "raidz"? > > > > > >> I also recommend reading through http://wiki.freebsd.org/ZFS for > > >> additional information. > > >> > > > Thank you, will do that too. > > > > > > I will have a bit more time this afternoon and then try to get it > > > going again as I try to setup with this HD a new one with the new > > > kde4. > > > > > >> Cheers, > > > > > > Thanks again, > > > > > >> Mark > > >> > > > Ernst > > > > > Hm.. Not sure my messages are actually going to the mailing > > list (given you responded and my email hasn't shown up on it > > yet). > > > well this one will. > > > In any case, no, if you don't want there to be any raid etc. > > just an array of disks you can use zpool create tank da0 da1 > > da2. (if I remember correctly - I don't have a machine with me > > at work I can test it on). > > > > http://www.freebsd.org/cgi/man.cgi?query=zpool&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html > > ans > > http://www.freebsd.org/cgi/man.cgi?query=zfs&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html > > are fairly digestable too, if you get the chance. > > > Got it all going and then compiled it all with make buildworld > and kernel, when I try to restart in single user mode I don't > have the /usr directory. What could have happen? You'll need to mount -a once in single-user to get all of your filesystems. Unless you're referring to /usr being on ZFS, which in that case you'll need to run "/etc/rc.d/hostid start", then "/etc/rc.d/zfs start". Your pools should load automatically. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Tue Jun 17 21:34:35 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 128F8106566B; Tue, 17 Jun 2008 21:34:35 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id E7E9E8FC1E; Tue, 17 Jun 2008 21:34:34 +0000 (UTC) (envelope-from randy@psg.com) Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1K8ip0-000P8T-2I; Tue, 17 Jun 2008 21:34:34 +0000 Message-ID: <48582DE7.4010009@psg.com> Date: Wed, 18 Jun 2008 06:34:31 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Jeremy Chadwick References: <26377.150.101.214.246.1213676733.squirrel@legios.org> <20080617202026.GA1997@ewinter.org> <20080617213218.GA27283@eos.sc1.parodius.com> In-Reply-To: <20080617213218.GA27283@eos.sc1.parodius.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: installation of zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2008 21:34:35 -0000 > Unless you're referring to /usr being on ZFS, which in that case you'll > need to run "/etc/rc.d/hostid start", then "/etc/rc.d/zfs start". Your > pools should load automatically. iff you did setmountpoint randyu From owner-freebsd-fs@FreeBSD.ORG Tue Jun 17 22:39:43 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B8801065677 for ; Tue, 17 Jun 2008 22:39:43 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail5out.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) by mx1.freebsd.org (Postfix) with ESMTP id DEB3C8FC0C for ; Tue, 17 Jun 2008 22:39:42 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by mail5out.barnet.com.au (Postfix, from userid 1001) id B9A7C2218ABC; Wed, 18 Jun 2008 08:22:27 +1000 (EST) X-Viruscan-Id: <48583923000173E5FDC448@BarNet> Received: from mail5auth.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail5auth.barnet.com.au", Issuer "*.barnet.com.au" (verified OK)) by mail5.barnet.com.au (Postfix) with ESMTP id 6600F21B3A88; Wed, 18 Jun 2008 08:22:27 +1000 (EST) Received: from k7.mavetju (unknown [10.10.26.6]) by mail5auth.barnet.com.au (Postfix) with ESMTP id A81132218A88; Wed, 18 Jun 2008 08:22:26 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id 89F214F1; Wed, 18 Jun 2008 08:22:27 +1000 (EST) Date: Wed, 18 Jun 2008 08:22:27 +1000 From: Edwin Groothuis To: freebsd-fs@FreeBSD.org Message-ID: <20080617222227.GA87804@k7.mavetju> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline In-Reply-To: <200806100753.m5A7rFIY079040@fire.js.berklix.net> User-Agent: Mutt/1.4.2.3i Cc: Julian Stacey Subject: Re: CFS Cryptographic file system. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2008 22:39:43 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Is there some replacement of /usr/ports/security/cfs > (encryped file system) for 7.0 ? Call me a slacker, but I got them from somebody else but never commited them. I never tested them, because I got it working with my own patches. Give it a try, if it works then I'll commit it. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/ --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=cfs cvs diff: Diffing . Index: patch-cfs__fh.c =================================================================== RCS file: /home/pcvs/ports/security/cfs/files/patch-cfs__fh.c,v retrieving revision 1.1 diff -u -r1.1 patch-cfs__fh.c --- patch-cfs__fh.c 12 Apr 2005 09:06:25 -0000 1.1 +++ patch-cfs__fh.c 18 Nov 2007 03:56:08 -0000 @@ -1,9 +1,16 @@ +$FreeBSD$ -$FreeBSD: ports/security/cfs/files/patch-cfs__fh.c,v 1.1 2005/04/12 09:06:25 flz Exp $ - ---- cfs_fh.c.orig -+++ cfs_fh.c -@@ -61,7 +61,7 @@ +--- cfs_fh.c.orig Thu May 3 11:24:59 2001 ++++ cfs_fh.c Sat Nov 17 19:43:36 2007 +@@ -43,6 +43,7 @@ + #ifdef NO_UTIMES + #include + #endif ++#include + + #include "nfsproto.h" + #include "admproto.h" +@@ -61,7 +62,7 @@ } #endif @@ -12,7 +19,7 @@ int inst = 0;/* starting point */ instance *instances[NINSTANCES]; -@@ -135,7 +135,6 @@ +@@ -135,7 +136,6 @@ int headlen; int writemore=0; struct stat sb; @@ -20,7 +27,7 @@ char buf[8216]; /* big enough, may not even need it */ /* first, normalize to the proper boundries */ -@@ -763,7 +762,7 @@ +@@ -763,7 +763,7 @@ char vect[9]; union{ u_char ch[9]; @@ -29,7 +36,7 @@ } buf; char linkname[NFS_MAXPATHLEN+1]; -@@ -792,8 +791,8 @@ +@@ -792,8 +792,8 @@ /* sprintf((char *)buf,"%08x",(u_long)sb.st_ino+(u_long)sb.st_ctime); */ @@ -40,7 +47,7 @@ q_block_cipher("fixedkey",&buf,1); /* des is just used here as a hash fn to spread the bits */ /* since we only use 32 bits of the result, its a nonperfect */ -@@ -908,7 +907,7 @@ +@@ -908,7 +908,7 @@ f->name=NULL; } } else { @@ -49,7 +56,7 @@ fprintf(stderr,"cfsd: out of memory\n"); cfserrno=NFSERR_STALE; /* bad news */ return -2; -@@ -1146,7 +1145,7 @@ +@@ -1146,7 +1146,7 @@ break anything */ struct dirent * rootrd(cookie) @@ -58,7 +65,7 @@ { static struct dirent d; -@@ -1198,7 +1197,7 @@ +@@ -1198,7 +1198,7 @@ #endif /* SHORTLINKS */ )) == NULL) { if ((f=(cfs_fileid *) Index: patch-cfs__nfs.c =================================================================== RCS file: /home/pcvs/ports/security/cfs/files/patch-cfs__nfs.c,v retrieving revision 1.1 diff -u -r1.1 patch-cfs__nfs.c --- patch-cfs__nfs.c 12 Apr 2005 09:06:25 -0000 1.1 +++ patch-cfs__nfs.c 18 Nov 2007 03:56:08 -0000 @@ -1,9 +1,170 @@ -$FreeBSD: ports/security/cfs/files/patch-cfs__nfs.c,v 1.1 2005/04/12 09:06:25 flz Exp $ +$FreeBSD$ ---- cfs_nfs.c.orig -+++ cfs_nfs.c -@@ -877,12 +877,11 @@ +--- cfs_nfs.c.orig Sun Dec 24 22:24:31 1995 ++++ cfs_nfs.c Sat Nov 17 19:43:00 2007 +@@ -33,6 +33,7 @@ + #else + #include + #endif ++#include + #include "nfsproto.h" + #include "admproto.h" + #include "cfs.h" +@@ -58,7 +59,7 @@ + } + + void * +-nfsproc_null_2(ap,rp) ++nfsproc_null_2_svc(ap,rp) + void *ap; + SR rp; + { +@@ -72,7 +73,7 @@ + readdirres *rootreaddir(); + + attrstat * +-nfsproc_getattr_2(ap,rp) ++nfsproc_getattr_2_svc(ap,rp) + nfs_fh *ap; + SR rp; + { +@@ -118,7 +119,7 @@ + } + + attrstat * +-nfsproc_setattr_2(ap,rp) ++nfsproc_setattr_2_svc(ap,rp) + sattrargs *ap; + SR rp; + { +@@ -168,7 +169,7 @@ + } + + void * +-nfsproc_root_2(ap,rp) ++nfsproc_root_2_svc(ap,rp) + void *ap; + SR rp; + { +@@ -179,7 +180,7 @@ + + /* fix this to deal w/ fs root (instance root should be ok) */ + diropres * +-nfsproc_lookup_2(ap,rp) ++nfsproc_lookup_2_svc(ap,rp) + diropargs *ap; + SR rp; + { +@@ -258,7 +259,7 @@ + } + + readlinkres * +-nfsproc_readlink_2(ap,rp) ++nfsproc_readlink_2_svc(ap,rp) + nfs_fh *ap; + SR rp; + { +@@ -309,7 +310,7 @@ + + + readres * +-nfsproc_read_2(ap,rp) ++nfsproc_read_2_svc(ap,rp) + readargs *ap; + SR rp; + { +@@ -370,7 +371,7 @@ + + + void * +-nfsproc_writecache_2(ap,rp) ++nfsproc_writecache_2_svc(ap,rp) + void *ap; + SR rp; + { +@@ -381,7 +382,7 @@ + + + attrstat * +-nfsproc_write_2(ap,rp) ++nfsproc_write_2_svc(ap,rp) + writeargs *ap; + SR rp; + { +@@ -442,7 +443,7 @@ + + + diropres * +-nfsproc_create_2(ap,rp) ++nfsproc_create_2_svc(ap,rp) + createargs *ap; + SR rp; + { +@@ -545,7 +546,7 @@ + + + nfsstat * +-nfsproc_remove_2(ap,rp) ++nfsproc_remove_2_svc(ap,rp) + diropargs *ap; + SR rp; + { +@@ -587,7 +588,7 @@ + + + nfsstat * +-nfsproc_rename_2(ap,rp) ++nfsproc_rename_2_svc(ap,rp) + renameargs *ap; + SR rp; + { +@@ -643,7 +644,7 @@ + + + nfsstat * +-nfsproc_link_2(ap,rp) ++nfsproc_link_2_svc(ap,rp) + linkargs *ap; + SR rp; + { +@@ -694,7 +695,7 @@ + + + nfsstat * +-nfsproc_symlink_2(ap,rp) ++nfsproc_symlink_2_svc(ap,rp) + symlinkargs *ap; + SR rp; + { +@@ -743,7 +744,7 @@ + } + + diropres * +-nfsproc_mkdir_2(ap,rp) ++nfsproc_mkdir_2_svc(ap,rp) + createargs *ap; + SR rp; + { +@@ -817,7 +818,7 @@ + + + nfsstat * +-nfsproc_rmdir_2(ap,rp) ++nfsproc_rmdir_2_svc(ap,rp) + diropargs *ap; + SR rp; + { +@@ -864,7 +865,7 @@ + /* #define cfsclosedir(x) fhclosedir(x) */ + + readdirres * +-nfsproc_readdir_2(ap,rp) ++nfsproc_readdir_2_svc(ap,rp) + readdirargs *ap; + SR rp; + { +@@ -877,12 +878,11 @@ static DIR *dp=NULL; static struct dirent *dent; entry **prev; @@ -18,7 +179,7 @@ int eof; int ne; int bytes; -@@ -944,7 +943,7 @@ +@@ -944,7 +944,7 @@ else if (strcmp(s,"..")==0) /* parent */ entrytab[ne].fileid=fhpid(h); else entrytab[ne].fileid=dent->d_fileno; @@ -27,7 +188,7 @@ *prev = &entrytab[ne]; prev = &entrytab[ne].nextentry; entrytab[ne].nextentry=NULL; -@@ -964,12 +963,12 @@ +@@ -964,12 +964,12 @@ DIR *curdir; int curdirid=0; @@ -42,7 +203,16 @@ { DIR *ret; DIR *fhopendir(); -@@ -1151,7 +1150,7 @@ +@@ -991,7 +991,7 @@ + } + + statfsres * +-nfsproc_statfs_2(ap,rp) ++nfsproc_statfs_2_svc(ap,rp) + nfs_fh *ap; + SR rp; + { +@@ -1151,7 +1151,7 @@ typedef char str[NFS_MAXNAMLEN+1]; static str names[MAXENTRIES]; entry **prev; @@ -51,7 +221,7 @@ int eof; int ne; int bytes; -@@ -1163,7 +1162,7 @@ +@@ -1163,7 +1163,7 @@ ne=0; prev= &ret.readdirres_u.reply.entries; *prev=NULL; @@ -60,7 +230,7 @@ eof=1; ret.status=NFS_OK; -@@ -1182,7 +1181,7 @@ +@@ -1182,7 +1182,7 @@ else entrytab[ne].fileid=dent->d_fileno; cookie=dent->d_reclen; /* may not work everywhere */ *prev = &entrytab[ne]; Index: patch-cfs_adm.c =================================================================== RCS file: patch-cfs_adm.c diff -N patch-cfs_adm.c --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ patch-cfs_adm.c 18 Nov 2007 03:56:08 -0000 @@ -0,0 +1,35 @@ + +$FreeBSD$ + +--- cfs_adm.c.orig Mon Dec 25 01:41:30 1995 ++++ cfs_adm.c Sat Nov 17 19:44:35 2007 +@@ -36,14 +36,14 @@ + } + + void * +-admproc_null_2() ++admproc_null_2_svc(void *v, SR rp) + { + } + + cfsstat * +-admproc_attach_2(ap,rp) ++admproc_attach_2_svc(ap,rp) + cfs_attachargs *ap; +- SR *rp; ++ SR rp; + { + static cfsstat ret; + int i; +@@ -154,9 +154,9 @@ + } + + cfsstat * +-admproc_detach_2(ap,rp) ++admproc_detach_2_svc(ap,rp) + cfs_detachargs *ap; +- SR *rp; ++ SR rp; + { + static cfsstat ret; + int i; --PEIAKu/WMn1b1Hv9-- From owner-freebsd-fs@FreeBSD.ORG Wed Jun 18 06:36:29 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2CA41065678 for ; Wed, 18 Jun 2008 06:36:29 +0000 (UTC) (envelope-from ernst.winter@t-online.de) Received: from mailout05.t-online.de (mailout05.t-online.de [194.25.134.82]) by mx1.freebsd.org (Postfix) with ESMTP id 7A3A68FC23 for ; Wed, 18 Jun 2008 06:36:29 +0000 (UTC) (envelope-from ernst.winter@t-online.de) Received: from fwd29.aul.t-online.de by mailout05.sul.t-online.de with smtp id 1K8rHL-0005Cx-00; Wed, 18 Jun 2008 08:36:23 +0200 Received: from lobo.ewinter.org (SOISkyZXghz0mC9NxnQftFZavvyfdcHtF+tbTU2POBI4tp87SEpoHaBIwuP15kVQZn@[91.48.223.82]) by fwd29.aul.t-online.de with esmtp id 1K8rH2-24oaSu0; Wed, 18 Jun 2008 08:36:04 +0200 Received: from lobo.ewinter.org (localhost [127.0.0.1]) by lobo.ewinter.org (8.14.2/8.14.1) with ESMTP id m5I6ZiTt034996; Wed, 18 Jun 2008 08:35:47 +0200 (CEST) (envelope-from ewinter@lobo.ewinter.org) Received: (from ewinter@localhost) by lobo.ewinter.org (8.14.2/8.14.1/Submit) id m5I6Zicf034995; Wed, 18 Jun 2008 08:35:44 +0200 (CEST) (envelope-from ewinter) Date: Wed, 18 Jun 2008 08:35:42 +0200 From: ernst.winter@t-online.de (Ernst W. Winter) To: Randy Bush Message-ID: <20080618063542.GC19490@ewinter.org> References: <26377.150.101.214.246.1213676733.squirrel@legios.org> <20080617202026.GA1997@ewinter.org> <20080617213218.GA27283@eos.sc1.parodius.com> <48582DE7.4010009@psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48582DE7.4010009@psg.com> X-Phone: + 49-7734-936-247 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.ewinter.org 7.0-STABLE FreeBSD 7.0-STABLE User-Agent: Mutt/1.5.18 (2008-05-17) X-ID: SOISkyZXghz0mC9NxnQftFZavvyfdcHtF+tbTU2POBI4tp87SEpoHaBIwuP15kVQZn X-TOI-MSGID: 22b8ca2d-607b-4f25-b80e-3aadc50986fd Cc: freebsd-fs@FreeBSD.org Subject: Re: installation of zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2008 06:36:29 -0000 On Wed, 18 Jun 2008, Randy Bush wrote: > > Unless you're referring to /usr being on ZFS, which in that case you'll > > need to run "/etc/rc.d/hostid start", then "/etc/rc.d/zfs start". Your > > pools should load automatically. > > iff you did setmountpoint > aha, I see, and where do I set it permanently? Thanks, > randyu Ernst -- ================================================== Mail just Ascii plain text. HTML & Base64 is spam email = nur reiner Text. HTML & Base64 sind SPAM From owner-freebsd-fs@FreeBSD.ORG Wed Jun 18 06:38:46 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2903C106564A for ; Wed, 18 Jun 2008 06:38:46 +0000 (UTC) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [IPv6:2001:418:1::39]) by mx1.freebsd.org (Postfix) with ESMTP id 0819B8FC1D for ; Wed, 18 Jun 2008 06:38:46 +0000 (UTC) (envelope-from randy@psg.com) Received: from [202.214.86.146] (helo=rmac.psg.com) by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1K8rJc-0000b8-6K; Wed, 18 Jun 2008 06:38:44 +0000 Message-ID: <4858AD72.3090707@psg.com> Date: Wed, 18 Jun 2008 15:38:42 +0900 From: Randy Bush User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: "Ernst W. Winter" References: <26377.150.101.214.246.1213676733.squirrel@legios.org> <20080617202026.GA1997@ewinter.org> <20080617213218.GA27283@eos.sc1.parodius.com> <48582DE7.4010009@psg.com> <20080618063542.GC19490@ewinter.org> In-Reply-To: <20080618063542.GC19490@ewinter.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: installation of zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2008 06:38:46 -0000 Ernst W. Winter wrote: > On Wed, 18 Jun 2008, Randy Bush wrote: > >>> Unless you're referring to /usr being on ZFS, which in that case you'll >>> need to run "/etc/rc.d/hostid start", then "/etc/rc.d/zfs start". Your >>> pools should load automatically. >> iff you did setmountpoint > aha, I see, and where do I set it permanently? see 'zfs setmountpoint' also in wiki and other docs. then they are mounted automagically, analogously to /etc/fstab mounts for ufs filesystems. randy From owner-freebsd-fs@FreeBSD.ORG Wed Jun 18 06:46:27 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E98F106564A for ; Wed, 18 Jun 2008 06:46:27 +0000 (UTC) (envelope-from ernst.winter@t-online.de) Received: from mailout10.t-online.de (mailout10.t-online.de [194.25.134.21]) by mx1.freebsd.org (Postfix) with ESMTP id B1F748FC16 for ; Wed, 18 Jun 2008 06:46:26 +0000 (UTC) (envelope-from ernst.winter@t-online.de) Received: from fwd35.aul.t-online.de by mailout10.sul.t-online.de with smtp id 1K8rQz-0008J2-01; Wed, 18 Jun 2008 08:46:21 +0200 Received: from lobo.ewinter.org (ZASzZZZ6ZhOq4xKfy4xEdrMV5CJd2knpO65oHvAJMVzbQp+Fhrq8g+anm9y4Sj7ZmY@[91.48.223.82]) by fwd35.aul.t-online.de with esmtp id 1K8rQl-0RYBoO0; Wed, 18 Jun 2008 08:46:07 +0200 Received: from lobo.ewinter.org (localhost [127.0.0.1]) by lobo.ewinter.org (8.14.2/8.14.1) with ESMTP id m5I6jj9i035086; Wed, 18 Jun 2008 08:45:49 +0200 (CEST) (envelope-from ewinter@lobo.ewinter.org) Received: (from ewinter@localhost) by lobo.ewinter.org (8.14.2/8.14.1/Submit) id m5I6jjT5035085; Wed, 18 Jun 2008 08:45:45 +0200 (CEST) (envelope-from ewinter) Date: Wed, 18 Jun 2008 08:45:42 +0200 From: ernst.winter@t-online.de (Ernst W. Winter) To: Randy Bush Message-ID: <20080618064542.GA35047@ewinter.org> References: <26377.150.101.214.246.1213676733.squirrel@legios.org> <20080617202026.GA1997@ewinter.org> <20080617213218.GA27283@eos.sc1.parodius.com> <48582DE7.4010009@psg.com> <20080618063542.GC19490@ewinter.org> <4858AD72.3090707@psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4858AD72.3090707@psg.com> X-Phone: + 49-7734-936-247 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.ewinter.org 7.0-STABLE FreeBSD 7.0-STABLE User-Agent: Mutt/1.5.18 (2008-05-17) X-ID: ZASzZZZ6ZhOq4xKfy4xEdrMV5CJd2knpO65oHvAJMVzbQp+Fhrq8g+anm9y4Sj7ZmY X-TOI-MSGID: 5c6c1ed9-92b4-44f1-9b93-5d26986276bc Cc: freebsd-fs@freebsd.org Subject: Re: installation of zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2008 06:46:27 -0000 On Wed, 18 Jun 2008, Randy Bush wrote: > Ernst W. Winter wrote: > > On Wed, 18 Jun 2008, Randy Bush wrote: > > > >>> Unless you're referring to /usr being on ZFS, which in that case you'll > >>> need to run "/etc/rc.d/hostid start", then "/etc/rc.d/zfs start". Your > >>> pools should load automatically. > >> iff you did setmountpoint > > aha, I see, and where do I set it permanently? > > see 'zfs setmountpoint' > SUPER! I will recompile everything first as I have csuped it all and so I will be up to date. Looking forward to learn about it more as it sounds good to have a filesystem like that and easy to handle so far. I will add a another HD as well for storage. > also in wiki and other docs. then they are mounted automagically, > analogously to /etc/fstab mounts for ufs filesystems. > Thanks again, > randy > _______________________________________________ > 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" Ernst -- ================================================== Mail just Ascii plain text. HTML & Base64 is spam email = nur reiner Text. HTML & Base64 sind SPAM From owner-freebsd-fs@FreeBSD.ORG Wed Jun 18 12:29:14 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5BD61065670 for ; Wed, 18 Jun 2008 12:29:14 +0000 (UTC) (envelope-from gdt@ir.bbn.com) Received: from fnord.ir.bbn.com (fnord.ir.bbn.com [192.1.100.210]) by mx1.freebsd.org (Postfix) with ESMTP id 890EF8FC16 for ; Wed, 18 Jun 2008 12:29:14 +0000 (UTC) (envelope-from gdt@ir.bbn.com) Received: by fnord.ir.bbn.com (Postfix, from userid 10853) id CCD0252EA; Wed, 18 Jun 2008 08:13:48 -0400 (EDT) From: Greg Troxel To: Edwin Groothuis References: <20080617222227.GA87804@k7.mavetju> X-Hashcash: 1:20:080618:edwin@mavetju.org::uZnazoz3duM/CWP+:000000000000000000000000000000000000000000000mwU X-Hashcash: 1:20:080618:jhs@berklix.org::EXmMNjXt6DhYluah:0011Np X-Hashcash: 1:20:080618:freebsd-fs@freebsd.org::SNHF1IdWsz13EG/Z:00000000000000000000000000000000000000013zT Date: Wed, 18 Jun 2008 08:13:48 -0400 In-Reply-To: <20080617222227.GA87804@k7.mavetju> (Edwin Groothuis's message of "Wed, 18 Jun 2008 08:22:27 +1000") Message-ID: User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@FreeBSD.org, Julian Stacey Subject: Re: CFS Cryptographic file system. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2008 12:29:15 -0000 I have been running cfs for a very long time (15 years?), most recently on NetBSD, but I've run it on 4.2BSD, SunOS 4, Linux, FreeBSD (2.1 to 4.x), and NetBSD (1.3ish to present). Your patch looks like it is adjusting for rpcgen differences, which makes sense. I've also had two other problems, but my memory is a bit fuzzy. on sparc, I needed to change something to avoid miscompilation; it worked on i386. It might be the patch appended. on i386, with gcc 4.1.2, it doesn't work (zero-length files?). With binaries built with gcc 3.3 on NetBSD 3, it works (even running on NetBSD 4.0). You may want to look at http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/security/cfs/ It might be time to roll a lot of these patches in and have a new tarball released. $NetBSD: patch-ae,v 1.1 2001/06/09 04:32:14 jlam Exp $ --- cfs_adm.c.orig Mon Dec 25 01:41:30 1995 +++ cfs_adm.c Fri Jun 8 21:14:35 2001 @@ -43,7 +43,7 @@ cfsstat * admproc_attach_2(ap,rp) cfs_attachargs *ap; - SR *rp; + SR rp; { static cfsstat ret; int i; @@ -156,7 +156,7 @@ cfsstat * admproc_detach_2(ap,rp) cfs_detachargs *ap; - SR *rp; + SR rp; { static cfsstat ret; int i; From owner-freebsd-fs@FreeBSD.ORG Fri Jun 20 20:03:31 2008 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C986A10656DA; Fri, 20 Jun 2008 20:03:31 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B238F8FC1E; Fri, 20 Jun 2008 20:03:31 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5KK3Vjm030916; Fri, 20 Jun 2008 20:03:31 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5KK3VAS030912; Fri, 20 Jun 2008 20:03:31 GMT (envelope-from gavin) Date: Fri, 20 Jun 2008 20:03:31 GMT Message-Id: <200806202003.m5KK3VAS030912@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/93942: [vfs] [patch] panic: ufs_dirbad: bad dir (patch from DragonFly) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2008 20:03:31 -0000 Synopsis: [vfs] [patch] panic: ufs_dirbad: bad dir (patch from DragonFly) Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: gavin Responsible-Changed-When: Fri Jun 20 20:01:34 UTC 2008 Responsible-Changed-Why: Over to freebsd-fs, where hopefully somebody can assess this PR http://www.freebsd.org/cgi/query-pr.cgi?pr=93942