From owner-freebsd-fs Sun Aug 1 22:21:21 1999 Delivered-To: freebsd-fs@freebsd.org Received: from chrome.dreamscape.com (chrome.dreamscape.com [206.64.128.4]) by hub.freebsd.org (Postfix) with ESMTP id 2FB4114E62 for ; Sun, 1 Aug 1999 22:21:07 -0700 (PDT) (envelope-from krentel@dreamscape.com) Received: from europa.dreamscape.com (mail.dreamscape.com [206.64.128.147]) by chrome.dreamscape.com (8.9.1/8.9.1) with ESMTP id BAA13107 for ; Mon, 2 Aug 1999 01:20:37 -0400 (EDT) X-Dreamscape-Track-Chrome-A: mail.dreamscape.com [206.64.128.147] X-Dreamscape-Track-Chrome-B: Mon, 2 Aug 1999 01:20:37 -0400 (EDT) Received: from dreamscape.com (sA17-p27.dreamscape.com [209.217.195.218]) by europa.dreamscape.com (8.8.5/8.8.4) with ESMTP id BAA29059 for ; Mon, 2 Aug 1999 01:20:36 -0400 (EDT) X-Dreamscape-Track-A: sA17-p27.dreamscape.com [209.217.195.218] X-Dreamscape-Track-B: Mon, 2 Aug 1999 01:20:36 -0400 (EDT) Received: (from krentel@localhost) by dreamscape.com (8.9.3/8.9.3) id BAA02386 for freebsd-fs@freebsd.org; Mon, 2 Aug 1999 01:19:59 -0400 (EDT) (envelope-from krentel) Date: Mon, 2 Aug 1999 01:19:59 -0400 (EDT) From: "Mark W. Krentel" Message-Id: <199908020519.BAA02386@dreamscape.com> To: freebsd-fs@freebsd.org Subject: link counts in ext2fs are all 0 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've noticed that the link counts of files from an EXT2FS filesystem (mounted in freebsd) all show up as 0. For example, I have a machine that dual boots between 3.2-release and Red Hat 6.0. I have options "EXT2FS" compiled into kernel and I mount linux's / partition: # mount_ext2fs /dev/da0s1 /mnt # /bin/ls -l /mnt total 65 drwxr-xr-x 0 root wheel 2048 Jul 29 13:22 bin drwxr-xr-x 0 root wheel 1024 Jul 29 14:33 boot drwxr-xr-x 0 root wheel 34816 Jul 30 01:09 dev drwxr-xr-x 0 root wheel 3072 Jul 30 01:09 etc ... Is there some reason for this? Is it a known problem? It is a bug, right? The linux filesystem does have link counts. --Mark Krentel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 2 21:59: 4 1999 Delivered-To: freebsd-fs@freebsd.org Received: from rodent.crp.com.au (rodent.ringtail.com.au [203.13.222.1]) by hub.freebsd.org (Postfix) with ESMTP id BA4FB15060 for ; Mon, 2 Aug 1999 21:58:50 -0700 (PDT) (envelope-from pedro@crp.com.au) Received: from crp.com.au (pedro.ringtail.com.au [203.13.222.13]) by rodent.crp.com.au (8.9.3/8.9.3) with ESMTP id NAA46017 for ; Thu, 5 Aug 1999 13:21:48 +1000 (EST) (envelope-from pedro@crp.com.au) Message-ID: <37A676D8.50108E8D@crp.com.au> Date: Tue, 03 Aug 1999 14:58:00 +1000 From: pedro X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: ccdconfig and mirroring Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone successful got mirroring working under 3.2-RELEASE. I have 2x4Gb SCSI drives and I have followed the steps that I could find at freebsd.org made ccd device added pseudo-device ccd 4 to kernel config disklabel -r -w d10 auto disklabel -e da1c *I wasn't sure about this one so I changed the fstype ccdconfig ccd0 32 6 /dev/da0a /dev/da1c newfs /dev/rccd0c When I rebooted the machine it dosen't have a kernel to start in. I am now re-installing the machine so if anyone could give me an idea of what I need to do it would be very helpful. Thanks, Dave Peterson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Aug 3 3:41:56 1999 Delivered-To: freebsd-fs@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id E272A15290 for ; Tue, 3 Aug 1999 03:41:23 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA16747; Tue, 3 Aug 1999 20:41:00 +1000 Date: Tue, 3 Aug 1999 20:41:00 +1000 From: Bruce Evans Message-Id: <199908031041.UAA16747@godzilla.zeta.org.au> To: freebsd-fs@FreeBSD.ORG, krentel@dreamscape.com Subject: Re: link counts in ext2fs are all 0 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I've noticed that the link counts of files from an EXT2FS filesystem >(mounted in freebsd) all show up as 0. For example, I have a machine >that dual boots between 3.2-release and Red Hat 6.0. I have options >"EXT2FS" compiled into kernel and I mount linux's / partition: > > # mount_ext2fs /dev/da0s1 /mnt > # /bin/ls -l /mnt > total 65 > drwxr-xr-x 0 root wheel 2048 Jul 29 13:22 bin > ... Link counts in ext2fs were broken by the soft updates changes (although soft updates are not implemented for ext2fs). Partial fix: diff -c2 ext2_vfsops.c~ ext2_vfsops.c *** ext2_vfsops.c~ Wed Jun 2 22:19:57 1999 --- ext2_vfsops.c Tue Aug 3 01:44:10 1999 *************** *** 582,585 **** --- 593,597 ---- EXT2_INODE_SIZE * ino_to_fsbo(fs, ip->i_number)), &ip->i_din); + ip->i_effnlink = ip->i_nlink; brelse(bp); vput(vp); *************** *** 1063,1066 **** --- 1077,1081 ---- ext2_ei2di((struct ext2_inode *) ((char *)bp->b_data + EXT2_INODE_SIZE * ino_to_fsbo(fs, ino)), &ip->i_din); + ip->i_effnlink = ip->i_nlink; ip->i_block_group = ino_to_cg(fs, ino); ip->i_next_alloc_block = 0; This works for old links but not for new ones, since ext2_vnops.c doesn't know anything about i_effnlink. E.g., link(2) appears to corrupt the link count (by not changing it), but the problem is magically fixed by umount/mount when the above changes do the translation. Bugs like this show why ext2fs shouldn't use any ufs vnops. (I just noticed some related ones for chflags(2). ext2fs uses ufs_setattr() which writes ffs values without translation. The values appear to change after umount/ mount when they are interpreted as ext2fs ones.) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Aug 4 20:16:45 1999 Delivered-To: freebsd-fs@freebsd.org Received: from chrome.dreamscape.com (chrome.dreamscape.com [206.64.128.4]) by hub.freebsd.org (Postfix) with ESMTP id 4EEB115064 for ; Wed, 4 Aug 1999 20:16:38 -0700 (PDT) (envelope-from krentel@dreamscape.com) Received: from europa.dreamscape.com (mail.dreamscape.com [206.64.128.147]) by chrome.dreamscape.com (8.9.1/8.9.1) with ESMTP id XAA00290; Wed, 4 Aug 1999 23:15:47 -0400 (EDT) X-Dreamscape-Track-Chrome-A: mail.dreamscape.com [206.64.128.147] X-Dreamscape-Track-Chrome-B: Wed, 4 Aug 1999 23:15:47 -0400 (EDT) Received: from dreamscape.com (sA9-p62.dreamscape.com [207.198.13.254]) by europa.dreamscape.com (8.8.5/8.8.4) with ESMTP id WAA03034; Wed, 4 Aug 1999 22:19:40 -0400 (EDT) X-Dreamscape-Track-A: sA9-p62.dreamscape.com [207.198.13.254] X-Dreamscape-Track-B: Wed, 4 Aug 1999 22:19:40 -0400 (EDT) Received: (from krentel@localhost) by dreamscape.com (8.9.3/8.9.3) id WAA03204; Wed, 4 Aug 1999 22:18:44 -0400 (EDT) (envelope-from krentel) Date: Wed, 4 Aug 1999 22:18:44 -0400 (EDT) From: "Mark W. Krentel" Message-Id: <199908050218.WAA03204@dreamscape.com> To: bde@zeta.org.au, freebsd-fs@FreeBSD.ORG Subject: Re: link counts in ext2fs are all 0 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Link counts in ext2fs were broken by the soft updates changes (although > soft updates are not implemented for ext2fs). Partial fix: I see. This happens even though I'm not using soft updates? I tried your patch in 3.2-release and indeed it does what you said it would. Old files have a correct link count while new ones appear to have 0 links. And even the new ones appear correct if you wait long enough (even without umount/mount). I guess that happens when the vnode gets flushed out of memory? A bazillion sync's doesn't do it, but unpacking a large tar file does. Should I consider the patch dangerous? Suppose I create a new file, the data gets sync'd but the power goes off before the vnode gets flushed or the partition is unmounted. Would the link count be wrong for that file? > This works for old links but not for new ones, since ext2_vnops.c doesn't > know anything about i_effnlink. E.g., link(2) appears to corrupt the > link count (by not changing it), but the problem is magically fixed > by umount/mount when the above changes do the translation. Bugs like > this show why ext2fs shouldn't use any ufs vnops. (I just noticed some > related ones for chflags(2). I'm confused. Is your comment, "ext2fs shouldn't use any ufs vnops", directed at developers (suggesting that ext2fs should be reorganized) or at users? Thanks! --Mark Krentel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Aug 4 20:55:18 1999 Delivered-To: freebsd-fs@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id B982914BF6 for ; Wed, 4 Aug 1999 20:55:12 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA10798; Thu, 5 Aug 1999 13:54:31 +1000 Date: Thu, 5 Aug 1999 13:54:31 +1000 From: Bruce Evans Message-Id: <199908050354.NAA10798@godzilla.zeta.org.au> To: bde@zeta.org.au, freebsd-fs@FreeBSD.ORG, krentel@dreamscape.com Subject: Re: link counts in ext2fs are all 0 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Link counts in ext2fs were broken by the soft updates changes (although >> soft updates are not implemented for ext2fs). Partial fix: > >I see. This happens even though I'm not using soft updates? Yes. >... And even the new ones appear correct if you wait long >enough (even without umount/mount). I guess that happens when the >vnode gets flushed out of memory? A bazillion sync's doesn't do it, >but unpacking a large tar file does. Yes. I mentioned umount/mount because it's the easiest way to ensure flushing of the vnode. >Should I consider the patch dangerous? Suppose I create a new file, It's probably harmless. >> ... Bugs like >> this show why ext2fs shouldn't use any ufs vnops. (I just noticed some >> related ones for chflags(2). > >I'm confused. Is your comment, "ext2fs shouldn't use any ufs vnops", >directed at developers (suggesting that ext2fs should be reorganized) >or at users? Developers. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Aug 5 14:43: 0 1999 Delivered-To: freebsd-fs@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-11.cpinternet.com [208.149.16.11]) by hub.freebsd.org (Postfix) with ESMTP id 00AF31557E for ; Thu, 5 Aug 1999 14:42:50 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id QAA24392; Thu, 5 Aug 1999 16:40:28 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 5 Aug 1999 16:40:28 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: freebsd-fs@freebsd.org Subject: blocking X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14250.853.418320.65158@avalon.east> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org An NFS blocking behaviour which doesn't seem correct to me: 1. background a long /bin/cp to /foo from an NFS-mounted file system. 2. ls /foo note that (2) hangs until (1) completes. Is this a bug? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Aug 5 16: 7:15 1999 Delivered-To: freebsd-fs@freebsd.org Received: from gatewaya.anheuser-busch.com (gatewaya.anheuser-busch.com [151.145.250.252]) by hub.freebsd.org (Postfix) with SMTP id 102D515655; Thu, 5 Aug 1999 16:04:48 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewaya.anheuser-busch.com; id SAA00171; Thu, 5 Aug 1999 18:05:34 -0500 Received: from stlexggtw002-pozzoli.fw-users.busch.com(151.145.101.130) by gatewaya.anheuser-busch.com via smap (V5.0) id xma000145; Thu, 5 Aug 99 18:04:47 -0500 Received: from stlabcexg006.anheuser-busch.com ([151.145.101.161]) by 151.145.101.130 (Norton AntiVirus for Internet Email Gateways 1.0) ; Thu, 05 Aug 1999 23:02:47 0000 (GMT) Received: by stlabcexg006.anheuser-busch.com with Internet Mail Service (5.5.2448.0) id ; Thu, 5 Aug 1999 18:02:32 -0500 Message-ID: <0740CBD1D149D31193EB0008C7C56836EB8AFC@STLABCEXG012> From: "Alton, Matthew" To: "'Hackers@FreeBSD.ORG'" , "'fs@FreeBSD.ORG'" Subject: BSD XFS Port & BSD VFS Rewrite Date: Thu, 5 Aug 1999 18:02:47 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am currently conducting a thorough study of the VFS subsystem in preparation for an all-out effort to port SGI's XFS filesystem to FreeBSD 4.x at such time as SGI gives up the code. Matt Dillon has written in hackers- that the VFS subsystem is presently not well understood by any of the active kernel code contributers and that it will be rewritten later this year. This is obviously of great concern to me in this port. I greatly appreciate all assistance in answering the following questions: 1) What are the perceived problems with the current VFS? 2) What options are available to us as remedies? 3) To what extent will existing FS code require revision in order to be useful after the rewrite? 4) Will Chapters 6,7,8 & 9 of "The Design and Implementation of the 4.4BSD Operating System" still pertain after the rewrite? 5) How important are questions 3 & 4 in the design of the new VFS? I believe that the VFS is conceptually sound and that the existing semantics should be strictly retained in the new code. Any new functionality should be added in the form of entirely new kernel routines and system calls, or possibly by such means as converting the existing routines to the vararg format &etc. Does anyone know when SGI will release XFS? Matthew Alton Computer Services - UNIX Systems Administration (314)632-6644 matthew.alton@anheuser-busch.com alton@plantnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Aug 5 18:26: 3 1999 Delivered-To: freebsd-fs@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 518E914D06 for ; Thu, 5 Aug 1999 18:25:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA13972; Fri, 6 Aug 1999 10:55:50 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA82836; Fri, 6 Aug 1999 10:55:46 +0930 (CST) Date: Fri, 6 Aug 1999 10:55:45 +0930 From: Greg Lehey To: pedro Cc: freebsd-fs@FreeBSD.ORG Subject: Re: ccdconfig and mirroring Message-ID: <19990806105545.U5126@freebie.lemis.com> References: <37A676D8.50108E8D@crp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37A676D8.50108E8D@crp.com.au>; from pedro on Tue, Aug 03, 1999 at 02:58:00PM +1000 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 3 August 1999 at 14:58:00 +1000, pedro wrote: > Has anyone successful got mirroring working under 3.2-RELEASE. Yes. But I use Vinum. > I have 2x4Gb SCSI drives and I have followed the steps that I could > find at freebsd.org > > made ccd device > added pseudo-device ccd 4 to kernel config > disklabel -r -w d10 auto > disklabel -e da1c *I wasn't sure about this one so I changed the > fstype > ccdconfig ccd0 32 6 /dev/da0a /dev/da1c > newfs /dev/rccd0c > > When I rebooted the machine it dosen't have a kernel to start in. Could you expand on that statement? > I am now re-installing the machine so if anyone could give me an > idea of what I need to do it would be very helpful. Well, first, never reinstall unless you have a very good reason to do so, such as a completely trashed disk. Then, describe the problems you're having. This message should probably go to FreeBSD-questions, since it's not a file system technical issue. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Aug 5 22:17:56 1999 Delivered-To: freebsd-fs@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 5916A14F6F for ; Thu, 5 Aug 1999 22:17:45 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id HAA11379; Fri, 6 Aug 1999 07:16:31 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id HAA62394; Fri, 6 Aug 1999 07:16:05 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id HAA30963; Fri, 6 Aug 1999 07:16:45 +0200 (CEST) (envelope-from ticso) Date: Fri, 6 Aug 1999 07:16:44 +0200 From: Bernd Walter To: Greg Lehey Cc: pedro , freebsd-fs@FreeBSD.ORG Subject: Re: ccdconfig and mirroring Message-ID: <19990806071644.A30939@cicely8.cicely.de> References: <37A676D8.50108E8D@crp.com.au> <19990806105545.U5126@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990806105545.U5126@freebie.lemis.com>; from Greg Lehey on Fri, Aug 06, 1999 at 10:55:45AM +0930 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Aug 06, 1999 at 10:55:45AM +0930, Greg Lehey wrote: > On Tuesday, 3 August 1999 at 14:58:00 +1000, pedro wrote: > > Has anyone successful got mirroring working under 3.2-RELEASE. > > Yes. But I use Vinum. > > > I have 2x4Gb SCSI drives and I have followed the steps that I could > > find at freebsd.org > > > > made ccd device > > added pseudo-device ccd 4 to kernel config > > disklabel -r -w d10 auto > > disklabel -e da1c *I wasn't sure about this one so I changed the > > fstype > > ccdconfig ccd0 32 6 /dev/da0a /dev/da1c > > newfs /dev/rccd0c > > > > When I rebooted the machine it dosen't have a kernel to start in. > > Could you expand on that statement? > > > I am now re-installing the machine so if anyone could give me an > > idea of what I need to do it would be very helpful. > > Well, first, never reinstall unless you have a very good reason to do Agree - but a newfs on anything derived from da0a is generaly a good reason. > so, such as a completely trashed disk. Then, describe the problems > you're having. This message should probably go to FreeBSD-questions, > since it's not a file system technical issue. > -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Aug 5 22:32:22 1999 Delivered-To: freebsd-fs@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id B635D14F55 for ; Thu, 5 Aug 1999 22:32:14 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id HAA11737; Fri, 6 Aug 1999 07:22:21 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id HAA62463; Fri, 6 Aug 1999 07:21:53 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id HAA30985; Fri, 6 Aug 1999 07:22:44 +0200 (CEST) (envelope-from ticso) Date: Fri, 6 Aug 1999 07:22:44 +0200 From: Bernd Walter To: pedro Cc: freebsd-fs@FreeBSD.ORG Subject: Re: ccdconfig and mirroring Message-ID: <19990806072243.B30939@cicely8.cicely.de> References: <37A676D8.50108E8D@crp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <37A676D8.50108E8D@crp.com.au>; from pedro on Tue, Aug 03, 1999 at 02:58:00PM +1000 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 03, 1999 at 02:58:00PM +1000, pedro wrote: > Has anyone successful got mirroring working under 3.2-RELEASE. > I have 2x4Gb SCSI drives and I have followed the steps that I could > find at freebsd.org > > made ccd device > added pseudo-device ccd 4 to kernel config > disklabel -r -w d10 auto > disklabel -e da1c *I wasn't sure about this one so I changed the > fstype > ccdconfig ccd0 32 6 /dev/da0a /dev/da1c > newfs /dev/rccd0c > > When I rebooted the machine it dosen't have a kernel to start in. > I am now re-installing the machine so if anyone could give me an idea of Sounds like you have shoot yourself in the foot. As Greg statet try vinum. vinum is not only the better choice for mirror than ccd, but it also protects you succesfully from many 'shoot yourself in the foot' situations. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Aug 5 23:48:14 1999 Delivered-To: freebsd-fs@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 3622415004 for ; Thu, 5 Aug 1999 23:47:49 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA15226; Fri, 6 Aug 1999 16:17:45 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA44190; Fri, 6 Aug 1999 16:17:42 +0930 (CST) Date: Fri, 6 Aug 1999 16:17:42 +0930 From: Greg Lehey To: Bernd Walter Cc: pedro , freebsd-fs@FreeBSD.ORG Subject: Re: ccdconfig and mirroring Message-ID: <19990806161742.S5126@freebie.lemis.com> References: <37A676D8.50108E8D@crp.com.au> <19990806105545.U5126@freebie.lemis.com> <19990806071644.A30939@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990806071644.A30939@cicely8.cicely.de>; from Bernd Walter on Fri, Aug 06, 1999 at 07:16:44AM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 6 August 1999 at 7:16:44 +0200, Bernd Walter wrote: > On Fri, Aug 06, 1999 at 10:55:45AM +0930, Greg Lehey wrote: >> On Tuesday, 3 August 1999 at 14:58:00 +1000, pedro wrote: >>> Has anyone successful got mirroring working under 3.2-RELEASE. >> >> Yes. But I use Vinum. >> >>> I have 2x4Gb SCSI drives and I have followed the steps that I could >>> find at freebsd.org >>> >>> made ccd device >>> added pseudo-device ccd 4 to kernel config >>> disklabel -r -w d10 auto >>> disklabel -e da1c *I wasn't sure about this one so I changed the >>> fstype >>> ccdconfig ccd0 32 6 /dev/da0a /dev/da1c >>> newfs /dev/rccd0c >>> >>> When I rebooted the machine it dosen't have a kernel to start in. >> >> Could you expand on that statement? >> >>> I am now re-installing the machine so if anyone could give me an >>> idea of what I need to do it would be very helpful. >> >> Well, first, never reinstall unless you have a very good reason to >> do so, such as a completely trashed disk. > > Agree - but a newfs on anything derived from da0a is generaly a good > reason. Yes, I suppose if he had had his root file system on /dev/da0a, that would explain a lot of things, including the reinstall. This is the reason that Vinum will refuse to build on a partition of type 4.2BSD. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message