From owner-freebsd-fs Thu Apr 1 7:49:25 1999 Delivered-To: freebsd-fs@freebsd.org Received: from nic.mco.net (nic.mco.net [209.205.43.25]) by hub.freebsd.org (Postfix) with ESMTP id 3294114F12 for ; Thu, 1 Apr 1999 07:49:23 -0800 (PST) (envelope-from mjones@mco.net) Received: from zigzag (zigzag.mco.net [209.167.186.150]) by nic.mco.net (8.9.1/8.9.1) with SMTP id KAA12642 for ; Thu, 1 Apr 1999 10:48:10 -0500 (EST) Message-ID: <00a501be7c57$2b69b720$96baa7d1@zigzag.london.skyscape.net> From: "Mark Jones" To: Subject: backup Date: Thu, 1 Apr 1999 10:49:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have multiple freebsd systems here. I would like to put a new hard drive into the system copy all files on to the new harddrive remove it and be able to put it into a new system and have it boot up identical to the original system. I have tried this and it has a problem on boot after the fsck when it trys to mount / as rw. It says that device is not as currently mounted. What should I do to accomplish this task? Mark Jones To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Apr 1 10: 2:43 1999 Delivered-To: freebsd-fs@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 2252814D03 for ; Thu, 1 Apr 1999 10:02:34 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id NAA06354; Thu, 1 Apr 1999 13:00:40 -0500 (EST) Date: Thu, 1 Apr 1999 13:00:40 -0500 (EST) From: Chuck Robey To: Mark Jones Cc: freebsd-fs@FreeBSD.ORG Subject: Re: backup In-Reply-To: <00a501be7c57$2b69b720$96baa7d1@zigzag.london.skyscape.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 1 Apr 1999, Mark Jones wrote: > I have multiple freebsd systems here. I would like to put a new hard drive > into the system copy all files on to the new harddrive remove it and be able > to put it into a new system and have it boot up identical to the original > system. I have tried this and it has a problem on boot after the fsck when > it trys to mount / as rw. It says that device is not as currently mounted. Did you correctly set the disklabel? This *does* work, I've done it. If you're having problems still (and you are sure your disklabel is right) then you're going to have to copy more info from the exact error message. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Apr 6 6:54:58 1999 Delivered-To: freebsd-fs@freebsd.org Received: from ns.icb.spb.su (ns.icb.spb.su [193.125.208.1]) by hub.freebsd.org (Postfix) with ESMTP id 879FF15626; Tue, 6 Apr 1999 06:53:27 -0700 (PDT) (envelope-from butthead@icb.spb.su) Received: (from uucp@localhost) by ns.icb.spb.su (8.9.1a/8.9.1) id RAA11587; Tue, 6 Apr 1999 17:51:16 +0400 (MSD) From: butthead@icb.spb.su Received: from netadmin.icbank(10.1.1.9) by ns.icb.spb.su via smap (V2.1) id xma011583; Tue, 6 Apr 99 17:51:08 +0400 Received: from tritosha.icbank (tritosha.icbank [10.1.1.10]) by netadmin.icbank (8.9.1/8.9.1) with ESMTP id RAA13479; Tue, 6 Apr 1999 17:51:03 +0400 (MSD) Received: by tritosha.icbank with Internet Mail Service (5.5.2448.0) id ; Tue, 6 Apr 1999 17:51:02 +0400 Message-ID: <49A0C11850D2D211AD3E00805FCBC538025089@kovnt.icbank> To: freebsd-stable@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Help with fsck trouble after crash. pls. Date: Tue, 6 Apr 1999 17:50:59 +0400 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 Hello. 1. My 3.1-RELEASE with custom kernel just crashes once per day or per two days... Yes I know, I must report stack trace from kernel to get help... Actually I have a core dump from savecore, but without debugging info :-( 2. Due that I have / and /usr FS corrupted in some way fsck says something like * FILESYSTEM STILL DIRTY * * PLS RERUN fsck * But rerun doesn't help. Messages are still the same. man page and FAQ seems contain no information about it. Can anybody help or point me to the relevant info about FS troubleshooting in BSD world. Thanks. -Dima. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Apr 6 7:14:34 1999 Delivered-To: freebsd-fs@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 6AB83151AA; Tue, 6 Apr 1999 07:14:28 -0700 (PDT) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id SAA20350; Tue, 6 Apr 1999 18:11:52 +0400 (MSD) Date: Tue, 6 Apr 1999 18:11:52 +0400 (MSD) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: butthead@icb.spb.su Cc: freebsd-stable@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Help with fsck trouble after crash. pls. In-Reply-To: <49A0C11850D2D211AD3E00805FCBC538025089@kovnt.icbank> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 6 Apr 1999 butthead@icb.spb.su wrote: > Date: Tue, 6 Apr 1999 17:50:59 +0400 > From: butthead@icb.spb.su > To: freebsd-stable@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG > Subject: Help with fsck trouble after crash. pls. > > Hello. > > 1. My 3.1-RELEASE with custom kernel just crashes > once per day or per two days... Yes I know, I must > report stack trace from kernel to get help... > Actually I have a core dump from savecore, but > without debugging info :-( With somethink like 'freeing wired page' message? Just upgrade to -stable. Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Apr 6 16:38:51 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 56D59154B2; Tue, 6 Apr 1999 16:38:44 -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 JAA11098; Wed, 7 Apr 1999 09:06:45 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA12793; Wed, 7 Apr 1999 09:06:45 +0930 (CST) Message-ID: <19990407090645.O2142@lemis.com> Date: Wed, 7 Apr 1999 09:06:45 +0930 From: Greg Lehey To: butthead@icb.spb.su, freebsd-stable@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Help with fsck trouble after crash. pls. References: <49A0C11850D2D211AD3E00805FCBC538025089@kovnt.icbank> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <49A0C11850D2D211AD3E00805FCBC538025089@kovnt.icbank>; from butthead@icb.spb.su on Tue, Apr 06, 1999 at 05:50:59PM +0400 WWW-Home-Page: http://www.lemis.com/~grog 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, 6 April 1999 at 17:50:59 +0400, butthead@icb.spb.su wrote: > Hello. > > 1. My 3.1-RELEASE with custom kernel just crashes > once per day or per two days... Yes I know, I must > report stack trace from kernel to get help... > Actually I have a core dump from savecore, but > without debugging info :-( There's an obvious solution there. If this crash is causing so much pain, it would be a good idea to find out what's causing it. > 2. Due that I have / and /usr FS corrupted in some way > fsck says something like * FILESYSTEM STILL DIRTY * > * PLS RERUN fsck * > But rerun doesn't help. Messages are still the same. > man page and FAQ seems > contain no information about it. > > Can anybody help or point me to the relevant info about > FS troubleshooting in BSD world. It looks like you have seriously broken your file system. Which file system is it? Boot in single user mode and do 'fsck -y /'. If that works, you at least have hope. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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 Fri Apr 30 9:14:43 1999 Delivered-To: freebsd-fs@freebsd.org Received: from inet16.us.oracle.com (inet16.us.oracle.com [192.86.155.100]) by hub.freebsd.org (Postfix) with ESMTP id A332914F96 for ; Fri, 30 Apr 1999 09:14:41 -0700 (PDT) (envelope-from klh@us.oracle.com) Received: from churchy20.us.oracle.com (churchy20.us.oracle.com [144.25.80.97]) by inet16.us.oracle.com (8.8.5/8.8.5) with SMTP id JAA05675 for ; Fri, 30 Apr 1999 09:14:40 -0700 (PDT) Received: by churchy20.us.oracle.com (5.59.11/37.7) id AA18445; Fri, 30 Apr 99 09:14:34 PDT Date: Fri, 30 Apr 99 9:14:33 PDT From: Ken Harrenstien To: freebsd-fs@freebsd.org Cc: klh@us.oracle.com Subject: When is a FFS not a FFS? Message-Id: Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm a relative newcomer to FreeBSD/NetBSD and have run into some problems with the filesystem code that have me both puzzled and concerned. Hopefully this is the appropriate list and someone can quickly set me straight. I have a number of large disks with UFS filesystems and data generated by non-BSD systems such as Alpha Digital Unix and SPARC Solaris. So far I've been able to directly mount and use Alpha D/U drives under both NetBSD/i386 and NetBSD/Alpha, and this has been a TREMENDOUSLY useful capability. (I've also noticed with admiration that the NetBSD filesystem code includes provision for detecting and handling byte swapping, which I'm hoping will permit me to eventually use SPARC drives as well.) However, to my surprise this doesn't work for FreeBSD/i386 (at least the 3.1-RELEASE version I have), and I'm not sure why. The magic numbers are the same and the structures look the same, but any attempts to mount simply fail: # mount /dev/da5a /mnt mount: /dev/da5a on /mnt: incorrect super block Trying to examine the disklabel typically gives: # disklabel da5 disklabel: ioctl DIOCGDINFO: Invalid argument But if I instead use "disklabel -r da5" it *does* read and print the correct disklabel information. My current theory (wild guess) is that for some reason the disklabel information from the disk is never taking up residence in the system proper, which means any reference to the [a-h] partitions will return bogus data. And that reason probably has something to do with interference by whatever code handles the DOS partition ("slice") table from the boot sector; possibly an unfortunate artifact of PC-centricism. Or is FreeBSD FFS really different from NetBSD FFS? D/U UFS? Why is there a ufs/ffs/* and ufs/ufs/* if according to the doc they're the same? I'm lost. I have enough disk backup that I'm willing to help alpha-test any fixes that might be forthcoming. I do hope I'm not the only one who thinks filesystem compatibility is an incredibly handy and useful feature... Thanks for any info! --Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Apr 30 12:25:49 1999 Delivered-To: freebsd-fs@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 16C1914C4A for ; Fri, 30 Apr 1999 12:25:25 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA59602; Fri, 30 Apr 1999 20:26:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 30 Apr 1999 20:26:24 +0100 (BST) From: Doug Rabson To: Ken Harrenstien Cc: freebsd-fs@freebsd.org Subject: Re: When is a FFS not a FFS? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 30 Apr 1999, Ken Harrenstien wrote: > I'm a relative newcomer to FreeBSD/NetBSD and have run into some > problems with the filesystem code that have me both puzzled and > concerned. Hopefully this is the appropriate list and someone can > quickly set me straight. > > I have a number of large disks with UFS filesystems and data generated > by non-BSD systems such as Alpha Digital Unix and SPARC Solaris. So > far I've been able to directly mount and use Alpha D/U drives under > both NetBSD/i386 and NetBSD/Alpha, and this has been a TREMENDOUSLY > useful capability. (I've also noticed with admiration that the NetBSD > filesystem code includes provision for detecting and handling byte > swapping, which I'm hoping will permit me to eventually use SPARC > drives as well.) > > However, to my surprise this doesn't work for FreeBSD/i386 (at least > the 3.1-RELEASE version I have), and I'm not sure why. The magic > numbers are the same and the structures look the same, but any attempts > to mount simply fail: > > # mount /dev/da5a /mnt > mount: /dev/da5a on /mnt: incorrect super block > > Trying to examine the disklabel typically gives: > > # disklabel da5 > disklabel: ioctl DIOCGDINFO: Invalid argument > > But if I instead use "disklabel -r da5" it *does* read and print the > correct disklabel information. > > My current theory (wild guess) is that for some reason the disklabel > information from the disk is never taking up residence in the system > proper, which means any reference to the [a-h] partitions will return > bogus data. And that reason probably has something to do with > interference by whatever code handles the DOS partition ("slice") table > from the boot sector; possibly an unfortunate artifact of PC-centricism. > > Or is FreeBSD FFS really different from NetBSD FFS? D/U UFS? Why is > there a ufs/ffs/* and ufs/ufs/* if according to the doc they're the same? > I'm lost. > > I have enough disk backup that I'm willing to help alpha-test any fixes > that might be forthcoming. I do hope I'm not the only one who thinks > filesystem compatibility is an incredibly handy and useful feature... FreeBSD/alpha will mount UFS filesystems from NetBSD/alpha and OSF1 with no problems at all. Your problem is that FreeBSD/i386 puts the disklabel at a different place on the disk from the alpha OSs. On the alpha, the disklabel is stored at offset 64 in block zero but on FreeBSD/i386, it is stored at offset zero in block one of the FreeBSD fdisk slice (which can be anywhere). I don't think FreeBSD/i386 is going to be sharing disks with different disklabel policies any day soon. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Apr 30 13: 7:25 1999 Delivered-To: freebsd-fs@freebsd.org Received: from inet16.us.oracle.com (inet16.us.oracle.com [192.86.155.100]) by hub.freebsd.org (Postfix) with ESMTP id 9AABA15029 for ; Fri, 30 Apr 1999 13:07:23 -0700 (PDT) (envelope-from klh@us.oracle.com) Received: from churchy20.us.oracle.com (churchy20.us.oracle.com [144.25.80.97]) by inet16.us.oracle.com (8.8.5/8.8.5) with SMTP id NAA17575; Fri, 30 Apr 1999 13:07:23 -0700 (PDT) Received: by churchy20.us.oracle.com (5.59.11/37.7) id AA18746; Fri, 30 Apr 99 13:07:17 PDT Date: Fri, 30 Apr 99 13:07:16 PDT From: Ken Harrenstien To: Doug Rabson Cc: Ken Harrenstien , freebsd-fs@freebsd.org Subject: Re: When is a FFS not a FFS? In-Reply-To: Your message of Fri, 30 Apr 1999 20:26:24 +0100 (BST) Message-Id: Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > FreeBSD/alpha will mount UFS filesystems from NetBSD/alpha and OSF1 with > no problems at all. Your problem is that FreeBSD/i386 puts the disklabel > at a different place on the disk from the alpha OSs. On the alpha, the > disklabel is stored at offset 64 in block zero but on FreeBSD/i386, it is > stored at offset zero in block one of the FreeBSD fdisk slice (which can > be anywhere). If I understand this correctly, you are saying that FreeBSD *always* expects to find and use a DOS partition, regardless of the actual platform? NetBSD appears to be able to work automatically either way so I blindly assumed FreeBSD would be equally astute. Still learning about their differences... However, I'm still a bit confused as to why "disklabel -r" was able to find the disklabel. Is it using a different algorithm from the kernel? > I don't think FreeBSD/i386 is going to be sharing disks with different > disklabel policies any day soon. If someone like myself were to find the time to make this possible (by borrowing NetBSD code) would it be permitted in FreeBSD? Just want to be clear whether this is due to policy or simple lack of resources. Thanks! --Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Apr 30 13:57:30 1999 Delivered-To: freebsd-fs@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 480F414C3C for ; Fri, 30 Apr 1999 13:57:11 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA59860; Fri, 30 Apr 1999 21:58:05 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 30 Apr 1999 21:58:05 +0100 (BST) From: Doug Rabson To: Ken Harrenstien Cc: freebsd-fs@freebsd.org Subject: Re: When is a FFS not a FFS? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 30 Apr 1999, Ken Harrenstien wrote: > > FreeBSD/alpha will mount UFS filesystems from NetBSD/alpha and OSF1 with > > no problems at all. Your problem is that FreeBSD/i386 puts the disklabel > > at a different place on the disk from the alpha OSs. On the alpha, the > > disklabel is stored at offset 64 in block zero but on FreeBSD/i386, it is > > stored at offset zero in block one of the FreeBSD fdisk slice (which can > > be anywhere). > > If I understand this correctly, you are saying that FreeBSD *always* > expects to find and use a DOS partition, regardless of the actual > platform? > > NetBSD appears to be able to work automatically either way so I blindly > assumed FreeBSD would be equally astute. Still learning about their > differences... Not quite. FreeBSD/i386 is a bit more complicated than OSF and *BSD/alpha for disklabeling. There are two ways of reserving disk space: The normal way uses an fdisk slice (the fdisk slice table and boot sector lives in block zero) to reserve a section of disk. Within that fdisk slice, the first block is a boot sector and the disklabel follows in byte zero of sector one. The 'dedicated' way skips the fdisk stage (actually I think it has a fake fdisk table) but still puts the disklabel in sector one offset zero of the freebsd area. This mode is not recommended since it can be hard to match up the different bogus geometry ideas of bios, hardware and kernel. On *BSD/alpha which have a simpler boot mechanism and no fdisk confusion (at least at the moment), the disklabel always lives in the same place (sector zero, offset 64). > > However, I'm still a bit confused as to why "disklabel -r" was able to > find the disklabel. Is it using a different algorithm from the kernel? Quite possibly. I think it grovels around looking for the disklabel magic number. > > > I don't think FreeBSD/i386 is going to be sharing disks with different > > disklabel policies any day soon. > > If someone like myself were to find the time to make this possible (by > borrowing NetBSD code) would it be permitted in FreeBSD? Just want to > be clear whether this is due to policy or simple lack of resources. I wouldn't mind this functionality being available. It might actually be handy to move disks between i386 and alpha (as long as no-one expects to be able to boot a disk on both platforms). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Apr 30 14:14:57 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 70B4315597 for ; Fri, 30 Apr 1999 14:14:54 -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 HAA19815; Sat, 1 May 1999 07:14:48 +1000 Date: Sat, 1 May 1999 07:14:48 +1000 From: Bruce Evans Message-Id: <199904302114.HAA19815@godzilla.zeta.org.au> To: dfr@nlsystems.com, klh@us.oracle.com Subject: Re: When is a FFS not a FFS? Cc: freebsd-fs@FreeBSD.ORG Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >FreeBSD/alpha will mount UFS filesystems from NetBSD/alpha and OSF1 with >no problems at all. Your problem is that FreeBSD/i386 puts the disklabel >at a different place on the disk from the alpha OSs. On the alpha, the >disklabel is stored at offset 64 in block zero but on FreeBSD/i386, it is >stored at offset zero in block one of the FreeBSD fdisk slice (which can >be anywhere). This doesn't explain why `disklabel -r da5' seemed to work, or how NetBSD/i386 handled labels at a nonstandard offset. I think alpha disks can only be handled by putting suitable metadata in sectors 0 and 1. Metadata suitable for NetBSD is not necessarily suitable for FreeBSD. `disklabel -r' is apparently finding slightly unsuitable metadata. For FreeBSD, sector 0 should not end with bytes { 0x55, 0xAA }, or else it will be considered to contain a DOS partition table and you would have to fudge that right too. Sector 1 must contain a valid label. A valid label for NetBSD needs more fudging than a valid label for FreeBSD, since the "raw" partition is 3 ('d') for NetBSD-i386 and 2 ('c') for NetBSD-alpha and FreeBSD-any. However, I think NetBSD-i386 labels look like FreeBSD-2.0 labels, and FreeBSD fixes up the latter. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Apr 30 14:38:39 1999 Delivered-To: freebsd-fs@freebsd.org Received: from inet16.us.oracle.com (inet16.us.oracle.com [192.86.155.100]) by hub.freebsd.org (Postfix) with ESMTP id 8A3611554A for ; Fri, 30 Apr 1999 14:38:37 -0700 (PDT) (envelope-from klh@us.oracle.com) Received: from churchy20.us.oracle.com (churchy20.us.oracle.com [144.25.80.97]) by inet16.us.oracle.com (8.8.5/8.8.5) with SMTP id OAA23680; Fri, 30 Apr 1999 14:38:35 -0700 (PDT) Received: by churchy20.us.oracle.com (5.59.11/37.7) id AA18810; Fri, 30 Apr 99 14:38:30 PDT Date: Fri, 30 Apr 99 14:38:30 PDT From: Ken Harrenstien To: Doug Rabson Cc: Ken Harrenstien , freebsd-fs@freebsd.org Subject: Re: When is a FFS not a FFS? In-Reply-To: Your message of Fri, 30 Apr 1999 21:58:05 +0100 (BST) Message-Id: Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > If someone like myself were to find the time to make this possible (by > > borrowing NetBSD code) would it be permitted in FreeBSD? Just want to > > be clear whether this is due to policy or simple lack of resources. > > I wouldn't mind this functionality being available. It might actually be > handy to move disks between i386 and alpha (as long as no-one expects to > be able to boot a disk on both platforms). OK, I'll take a look at the find-disklabel code in both FreeBSD and NetBSD and try some experiments if it seems within my capabilities. As for being handy, I must reiterate that it most definitely is! I doubt I have any more free time than you do, but this feature is worth enough to me that I'm making some. Big data (not boot) LVD drives, multi-platform environment, interest in testing FreeBSD if it isn't too hard to set up... QED. Thanks again for the background, that saved me a fair bit of digging! --Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed May 5 11:26:54 1999 Delivered-To: freebsd-fs@freebsd.org Received: from lac.uic.edu (bsd.lac.uic.edu [128.248.181.130]) by hub.freebsd.org (Postfix) with SMTP id 9FEC3151D7 for ; Wed, 5 May 1999 11:26:52 -0700 (PDT) (envelope-from marco@lac.uic.edu) Received: (qmail 809 invoked from network); 6 May 1999 02:30:46 -0000 Received: from localhost (HELO lac.uic.edu) (127.0.0.1) by localhost with SMTP; 6 May 1999 02:30:46 -0000 Message-ID: <3730FED6.6FC222FF@lac.uic.edu> Date: Thu, 06 May 1999 02:30:46 +0000 From: Marco Mazzucco X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-fs@FreeBSD.ORG Subject: lfs questions ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is LFS be currently supported for FreeBSD3.1? If so, could you point me to some information on this? Thanks much in advance, Marco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed May 5 11:28:20 1999 Delivered-To: freebsd-fs@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 97A0114CCD for ; Wed, 5 May 1999 11:28:16 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA12626; Wed, 5 May 1999 20:28:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA01060; Wed, 5 May 1999 20:28:15 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Marco Mazzucco Cc: freebsd-fs@FreeBSD.ORG Subject: Re: lfs questions ... In-reply-to: Your message of "Thu, 06 May 1999 02:30:46 -0000." <3730FED6.6FC222FF@lac.uic.edu> Date: Wed, 05 May 1999 20:28:15 +0200 Message-ID: <1058.925928895@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <3730FED6.6FC222FF@lac.uic.edu>, Marco Mazzucco writes: >Is LFS be currently supported for FreeBSD3.1? If so, could you point me >to some information on this? No, LFS isn't supported in any version of FreeBSD. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message