From owner-freebsd-fs Sun Aug 23 05:20:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08676 for freebsd-fs-outgoing; Sun, 23 Aug 1998 05:20:08 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from wanadoo.fr (smtp-out-1.wanadoo.fr [193.252.19.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08558 for ; Sun, 23 Aug 1998 05:19:55 -0700 (PDT) (envelope-from poipoi@famipow.com) From: poipoi@famipow.com Received: from root@tamaya.wanadoo.fr [193.252.19.31] by wanadoo.fr for Paris Sun, 23 Aug 1998 14:18:33 +0200 (MET DST) Received: from qmailr@cergy12-28.abo.wanadoo.fr [164.138.0.28] by smtp.wanadoo.fr for Paris Sun, 23 Aug 1998 14:18:23 +0200 (MET DST) Received: (qmail 397 invoked by uid 501); 23 Aug 1998 08:21:02 -0000 Message-ID: <19980823082102.396.qmail@hwi.poi.org> Subject: name cache wiping in readdir ? To: freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu Date: Sun, 23 Aug 1998 10:21:01 +0200 (MET DST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi in ext2, each name read by readdir (called by getdents(2)) is sent in the name cache. This can result of a cache wiping (i.e. cache flushed to store useless new names). is it a good policy ? some statistics/study are available ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Aug 23 13:27:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18556 for freebsd-fs-outgoing; Sun, 23 Aug 1998 13:27:59 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from casagate.staub.net (casagate.staub.net [206.129.249.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18548 for ; Sun, 23 Aug 1998 13:27:56 -0700 (PDT) (envelope-from phils@casagate.staub.net) Received: from staub.net (casa.staub.net [192.168.10.10]) by casagate.staub.net (8.8.8/8.8.8) with ESMTP id NAA10138 for ; Sun, 23 Aug 1998 13:27:09 -0700 (PDT) (envelope-from phils@casagate.staub.net) Message-ID: <35E07B1B.F7BC7E1C@staub.net> Date: Sun, 23 Aug 1998 13:27:07 -0700 From: Phil Staub Reply-To: phils@casagate.staub.net X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: freebsd-fs@FreeBSD.ORG Subject: Need help recovering a trashed partition Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Apologies in advance if this question should have been sent to a different list, but I thought this might have been a good place to start. The situation: FreeBSD 2.2.7-STABLE running on a drive shared with two other operating systems: Windoze 95 on slice 1, FreeBSD on slice 2, Linux (sorry!) using slices 3 and 4. In an attempt to install Linux on slices 3 and 4, I have somehow managed to trash something (maybe several things) on my FreeBSD slice, in spite of being very careful *not* to touch that slice when dealing with the Linux partitions. Needless to say, I've set aside the Linux installation for the time being, but now I have to deal with possible recovery of whatever is left of FreeBSD. First of all, I consider it to be a good sign that at least the disklabel read from the disk seems to be intact. However, the bootstrap was missing. (OS-BS boot menu reports "No operating system found"). So, I went back in with the fixit disk and used disklabel -B to reinstall the bootstrap. Now, OS-BS finds enough of the partition to see the bootloader, but all it does is print one '-' out of the spinning bar sequence, and hangs. So I decided to try fsck. Back to the fixit disk, I ran fsck /mnt2/dev/wd0s2 and it tells me that the superblock has a bad magic number. It also said that the disk is labeled as a 4.2 filesystem, but that the block length is zero. So I tried fsck -b 32 to try to use the first alternate superblock. Now it just says bad magic number. More information: I went into the disk partitioning and disk label utility in sysinstall. They seemed to know about all of my partitions on the FreeBSD slice. However, except for re-installing the bootstrap, I haven't written anything else to the disk before I got some further advice. At this point, I've just about exhausted what little knowledge I have about the FreeBSD filesystem layout. So the question is, is there any hope, and where do I go from here? (OK, so it's two questions...) Thanks, Phil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Aug 23 13:52:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20916 for freebsd-fs-outgoing; Sun, 23 Aug 1998 13:52:21 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from atrey.karlin.mff.cuni.cz (atrey.karlin.mff.cuni.cz [195.113.31.123]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20872 for ; Sun, 23 Aug 1998 13:52:09 -0700 (PDT) (envelope-from jack@atrey.karlin.mff.cuni.cz) Received: (from jack@localhost) by atrey.karlin.mff.cuni.cz (8.8.8/8.8.8) id WAA29320; Sun, 23 Aug 1998 22:49:05 +0200 Message-ID: <19980823224905.35695@atrey.karlin.mff.cuni.cz> Date: Sun, 23 Aug 1998 22:49:05 +0200 From: Jan Kara To: poipoi@famipow.com Cc: freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu Subject: Re: name cache wiping in readdir ? References: <19980823082102.396.qmail@hwi.poi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980823082102.396.qmail@hwi.poi.org>; from poipoi@famipow.com on Sun, Aug 23, 1998 at 10:21:01AM +0200 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. > hi > > in ext2, each name read by readdir (called by getdents(2)) is sent in > the name cache. OK. Looking in both ext2 and linux/fs/readdir.c getdents() code (kernel 2.1.117), I haven't found a place where the names would be sent to dcache. They are only stored in a special structure linux_dirent which has nothing to do with dcache. Nice hacking. Honza. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Aug 23 23:30:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00969 for freebsd-fs-outgoing; Sun, 23 Aug 1998 23:30:50 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from wanadoo.fr (smtp-out-1.wanadoo.fr [193.252.19.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00962 for ; Sun, 23 Aug 1998 23:30:46 -0700 (PDT) (envelope-from poipoi@famipow.com) From: poipoi@famipow.com Received: from aralia.wanadoo.fr [193.252.19.42] by wanadoo.fr for Paris Mon, 24 Aug 1998 08:29:28 +0200 (MET DST) Received: from qmailr@cergy13-38.abo.wanadoo.fr [164.138.1.38] by smtp.wanadoo.fr for Paris Mon, 24 Aug 1998 08:29:01 +0200 (MET DST) Received: (qmail 635 invoked by uid 501); 24 Aug 1998 06:37:43 -0000 Message-ID: <19980824063743.634.qmail@hwi.poi.org> Subject: Re: name cache wiping in readdir ? In-Reply-To: <19980823224905.35695@atrey.karlin.mff.cuni.cz> from Jan Kara at "Aug 23, 98 10:49:05 pm" To: jack@atrey.karlin.mff.cuni.cz (Jan Kara) Date: Mon, 24 Aug 1998 08:37:43 +0200 (MET DST) Cc: poipoi@famipow.com, freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello. > > > hi > > > > in ext2, each name read by readdir (called by getdents(2)) is sent in > > the name cache. > OK. Looking in both ext2 and linux/fs/readdir.c getdents() code (kernel 2.1.117), I > haven't found a place where the names would be sent to dcache. They are only stored > in a special structure linux_dirent which has nothing to do with dcache. you are right, i wasn't aware of this modification, but the sources (2.0.21) i have on my disk have it just before filldir(). personnaly i dont care of current state, i just wanna know if it is a good or a bad policy and why. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Aug 23 23:36:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01646 for freebsd-fs-outgoing; Sun, 23 Aug 1998 23:36:23 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from wanadoo.fr (smtp-out-1.wanadoo.fr [193.252.19.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01640 for ; Sun, 23 Aug 1998 23:36:22 -0700 (PDT) (envelope-from poipoi@famipow.com) From: poipoi@famipow.com Received: from root@tamaya.wanadoo.fr [193.252.19.31] by wanadoo.fr for Paris Mon, 24 Aug 1998 08:35:03 +0200 (MET DST) Received: from qmailr@cergy13-38.abo.wanadoo.fr [164.138.1.38] by smtp.wanadoo.fr for Paris Mon, 24 Aug 1998 08:34:59 +0200 (MET DST) Received: (qmail 652 invoked by uid 501); 24 Aug 1998 06:44:27 -0000 Message-ID: <19980824064427.651.qmail@hwi.poi.org> Subject: Re: name cache wiping in readdir ? In-Reply-To: <4012.903933178@critter.freebsd.dk> from Poul-Henning Kamp at "Aug 24, 98 06:32:58 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Mon, 24 Aug 1998 08:44:27 +0200 (MET DST) Cc: jack@atrey.karlin.mff.cuni.cz, poipoi@famipow.com, freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In message <19980823224905.35695@atrey.karlin.mff.cuni.cz>, Jan Kara writes: > > Hello. > > > >> hi > >> > >> in ext2, each name read by readdir (called by getdents(2)) is sent in > >> the name cache. > > OK. Looking in both ext2 and linux/fs/readdir.c getdents() code (kernel 2.1.117), I > >haven't found a place where the names would be sent to dcache. They are only stored > >in a special structure linux_dirent which has nothing to do with dcache. > > Further the namecache in FreeBSD isn't finite size, it contains > anything put into it that might still be of any use, so sticking > it all in there at readdir time (which may or may not be a bad > idea) wouldn't flush out other stuff. your computer has a finite memory so your cache has a finite size :) but ok your cache is no more fix size. but anyway it doesnt solve any cache wiping problem. Whatever your cache size, you can always fill it with useless data. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Aug 23 23:54:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04012 for freebsd-fs-outgoing; Sun, 23 Aug 1998 23:54:12 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04004 for ; Sun, 23 Aug 1998 23:54:09 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id GAA04014; Mon, 24 Aug 1998 06:32:59 +0200 (CEST) To: Jan Kara cc: poipoi@famipow.com, freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu Subject: Re: name cache wiping in readdir ? In-reply-to: Your message of "Sun, 23 Aug 1998 22:49:05 +0200." <19980823224905.35695@atrey.karlin.mff.cuni.cz> Date: Mon, 24 Aug 1998 06:32:58 +0200 Message-ID: <4012.903933178@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19980823224905.35695@atrey.karlin.mff.cuni.cz>, Jan Kara writes: > Hello. > >> hi >> >> in ext2, each name read by readdir (called by getdents(2)) is sent in >> the name cache. > OK. Looking in both ext2 and linux/fs/readdir.c getdents() code (kernel 2.1.117), I >haven't found a place where the names would be sent to dcache. They are only stored >in a special structure linux_dirent which has nothing to do with dcache. Further the namecache in FreeBSD isn't finite size, it contains anything put into it that might still be of any use, so sticking it all in there at readdir time (which may or may not be a bad idea) wouldn't flush out other stuff. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 24 01:12:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15092 for freebsd-fs-outgoing; Mon, 24 Aug 1998 01:12:36 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15067 for ; Mon, 24 Aug 1998 01:12:31 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from chalmers.com.au (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.9.1/8.9.1) with ESMTP id SAA09398 for ; Mon, 24 Aug 1998 18:10:57 +1000 (EST) Message-ID: <35E1211B.711998CD@chalmers.com.au> Date: Mon, 24 Aug 1998 18:15:23 +1000 From: Robert Chalmers Reply-To: robert@chalmers.com.au Organization: chalmers.com.au X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-fs@FreeBSD.ORG Subject: Trying to set up a bootable, boot partition. SCSI Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any way of setting up a boot/root partition using the disklabel procedures, on a SCSI drive anyway, or can it only be done using the sysinstall/fdisk utility? The process of ; I used the method as described in the manual, dd if=/dev/zero of=/dev/rsd2 bs=1k count=1 disklabel -Brw sd2 auto disklabel -e sd2 although it sets up a drive that can be used as, in this case, the third drive in the chain, still doesn't set it up with an active/boot sector. In other words, placing the drive in SCSI #0 position, as the boot drive, sd0, simply doesn't work. Although the BIOS sees the drive of course, it wont boot. Now, what I'm trying to discover, is, is it a REQUIREMENT that sysinstall/fdisk be used on FreeBSD to set up an active/boot sector? Thanks Bob -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 24 01:59:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21089 for freebsd-fs-outgoing; Mon, 24 Aug 1998 01:59:02 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from our.domaintje.com (our.domaintje.com [194.178.252.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21083 for ; Mon, 24 Aug 1998 01:58:59 -0700 (PDT) (envelope-from frank@our.domaintje.com) Received: from our.domaintje.com ([IPv6:::ffff:194.178.252.9] EHLO our.domaintje.com ident: IDENT-NONSENSE [port 2829]) by our.domaintje.com with ESMTP id <8009-182>; Mon, 24 Aug 1998 10:57:51 +0200 To: robert@chalmers.com.au cc: freebsd-fs@FreeBSD.ORG Subject: Re: Trying to set up a bootable, boot partition. SCSI In-reply-to: Your message of "Mon, 24 Aug 1998 18:15:23 +1000." <35E1211B.711998CD@chalmers.com.au> Date: Mon, 24 Aug 1998 10:57:43 +0200 From: Frank Ederveen Message-Id: <19980824085751Z8009-182+22@our.domaintje.com> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any way of setting up a boot/root partition using the disklabel procedures, on a SCSI drive anyway, or can it only be done using the sysinstall/fdisk utility? Hi, you might want to install the bootloader? Look in /usr/src/sys/i386/boot/biosboot; if you type make there you should get two files; boot1 and boot2. Then use disklabel -B -b boot1 -s boot2 to install them. Hope this helps? FrankE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 24 03:26:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02108 for freebsd-fs-outgoing; Mon, 24 Aug 1998 03:26:45 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02096 for ; Mon, 24 Aug 1998 03:26:41 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id MAA01090; Mon, 24 Aug 1998 12:22:16 +0200 (CEST) To: poipoi@famipow.com cc: jack@atrey.karlin.mff.cuni.cz, freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu Subject: Re: name cache wiping in readdir ? In-reply-to: Your message of "Mon, 24 Aug 1998 08:44:27 +0200." <19980824064427.651.qmail@hwi.poi.org> Date: Mon, 24 Aug 1998 12:22:10 +0200 Message-ID: <1088.903954130@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19980824064427.651.qmail@hwi.poi.org>, poipoi@famipow.com writes: >your computer has a finite memory so your cache has a finite size :) >but ok your cache is no more fix size. but anyway it doesnt solve any >cache wiping problem. Whatever your cache size, you can always fill it >with useless data. read the code... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 24 06:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23064 for freebsd-fs-outgoing; Mon, 24 Aug 1998 06:09:53 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from renko.ucs.ed.ac.uk (renko.ucs.ed.ac.uk [129.215.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23049 for ; Mon, 24 Aug 1998 06:09:37 -0700 (PDT) (envelope-from sct@redhat.com) Received: from dax.dcs.ed.ac.uk (root@dialup-111.publab.ed.ac.uk [129.215.38.111]) by renko.ucs.ed.ac.uk (8.8.7/8.8.7) with ESMTP id OAA13296; Mon, 24 Aug 1998 14:07:50 +0100 (BST) Received: (from sct@localhost) by dax.dcs.ed.ac.uk (8.8.7/8.8.7) id KAA21958; Mon, 24 Aug 1998 10:34:16 +0100 Date: Mon, 24 Aug 1998 10:34:16 +0100 Message-Id: <199808240934.KAA21958@dax.dcs.ed.ac.uk> From: "Stephen C. Tweedie" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: poipoi@famipow.com Cc: freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu Subject: Re: name cache wiping in readdir ? In-Reply-To: <19980823082102.396.qmail@hwi.poi.org> References: <19980823082102.396.qmail@hwi.poi.org> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Sun, 23 Aug 1998 10:21:01 +0200 (MET DST), poipoi@famipow.com said: > hi > in ext2, each name read by readdir (called by getdents(2)) is sent in > the name cache. This can result of a cache wiping (i.e. cache > flushed to store useless new names). > is it a good policy ? some statistics/study are available ? There are very many programs which take directory listings and then perform some operation (open, stat etc.) on each file. Think about doing "ls -l" or "grep *". Adding the readdir results to the name cache is a definite win here. One thing which I would like to try (we did it in earlier versions of the primitive name cache in 2.0) is a two-level name cache, where we promote names up to the next level on a hit and demote them when we want to emply a list. The primary win of such a scheme is that names which are only hit once never make it out of the first level of the cache, but names which are genuinely useful (hit at least twice) get promoted and hence get protected from the flushing effects of a mass "find" operation. It would be useful at some point to benchmark the effects of such a change, but that will definitely have to be a 2.3 thing. Just how effective it would be would depend enormously on the pattern of load; in general, the current scheme works pretty well. --Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 24 06:55:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28204 for freebsd-fs-outgoing; Mon, 24 Aug 1998 06:55:42 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from valerie.inf.elte.hu (valerie.inf.elte.hu [157.181.50.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28090 for ; Mon, 24 Aug 1998 06:55:02 -0700 (PDT) (envelope-from mingo@valerie.inf.elte.hu) Received: from localhost (mingo@localhost) by valerie.inf.elte.hu (8.8.8/8.8.8) with SMTP id PAA09907; Mon, 24 Aug 1998 15:53:51 +0200 (MET DST) Date: Mon, 24 Aug 1998 15:53:51 +0200 (MET DST) From: MOLNAR Ingo To: "Stephen C. Tweedie" cc: poipoi@famipow.com, freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu Subject: Re: name cache wiping in readdir ? In-Reply-To: <199808240934.KAA21958@dax.dcs.ed.ac.uk> 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 Mon, 24 Aug 1998, Stephen C. Tweedie wrote: > One thing which I would like to try (we did it in earlier versions of > the primitive name cache in 2.0) is a two-level name cache, where we > promote names up to the next level on a hit and demote them when we want > to emply a list. [...] we have dentry aging which should take care of these issues. Whenever we reply to memory pressure, we are more likely to free unused dentries. -- mingo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 24 12:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18649 for freebsd-fs-outgoing; Mon, 24 Aug 1998 12:04:30 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from renko.ucs.ed.ac.uk (renko.ucs.ed.ac.uk [129.215.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18608 for ; Mon, 24 Aug 1998 12:04:22 -0700 (PDT) (envelope-from sct@redhat.com) Received: from dax.dcs.ed.ac.uk (root@dialup-119.publab.ed.ac.uk [129.215.38.119]) by renko.ucs.ed.ac.uk (8.8.7/8.8.7) with ESMTP id UAA27811; Mon, 24 Aug 1998 20:03:29 +0100 (BST) Received: (from sct@localhost) by dax.dcs.ed.ac.uk (8.8.7/8.8.7) id SAA25353; Mon, 24 Aug 1998 18:57:08 +0100 Date: Mon, 24 Aug 1998 18:57:08 +0100 Message-Id: <199808241757.SAA25353@dax.dcs.ed.ac.uk> From: "Stephen C. Tweedie" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: MOLNAR Ingo Cc: "Stephen C. Tweedie" , poipoi@famipow.com, freebsd-fs@FreeBSD.ORG, linux-fsdevel@vger.rutgers.edu Subject: Re: name cache wiping in readdir ? In-Reply-To: References: <199808240934.KAA21958@dax.dcs.ed.ac.uk> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Mon, 24 Aug 1998 15:53:51 +0200 (MET DST), MOLNAR Ingo said: > On Mon, 24 Aug 1998, Stephen C. Tweedie wrote: >> One thing which I would like to try (we did it in earlier versions of >> the primitive name cache in 2.0) is a two-level name cache, where we >> promote names up to the next level on a hit and demote them when we want >> to emply a list. [...] > we have dentry aging which should take care of these issues. Whenever we > reply to memory pressure, we are more likely to free unused dentries. Yes. The multi-level architecture is just an optimisation which lets us deal with the common "find" special case without flushing _any_ of our established dcache entries. With an aging mechanism, the best that happens is that a find leaves active entries alone but still ages and eventually flushes out the initial contents of the cache. --Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Aug 26 00:22:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20031 for freebsd-fs-outgoing; Wed, 26 Aug 1998 00:22:09 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA19996 for ; Wed, 26 Aug 1998 00:21:53 -0700 (PDT) (envelope-from hiren@tagore.wipinfo.soft.net) Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id MAA03801; Wed, 26 Aug 1998 12:45:28 -0500 Date: Wed, 26 Aug 1998 12:55:44 +0530 (IST) From: Hiren Mehta X-Sender: hiren@tagore To: freebsd-fs@FreeBSD.ORG Subject: question about msdosfs file system 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 Hi All, In case of MSDOS formatted device, is there any guarantee that the files are will start on 8192 bytes boundary of the device ? Thanks Hiren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Aug 26 10:32:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08446 for freebsd-fs-outgoing; Wed, 26 Aug 1998 10:32:03 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08421 for ; Wed, 26 Aug 1998 10:31:54 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id KAA26967; Wed, 26 Aug 1998 10:31:00 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd026905; Wed Aug 26 10:30:51 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id KAA10855; Wed, 26 Aug 1998 10:30:39 -0700 (MST) From: Terry Lambert Message-Id: <199808261730.KAA10855@usr02.primenet.com> Subject: Re: question about msdosfs file system To: hiren@tagore.wipinfo.soft.net (Hiren Mehta) Date: Wed, 26 Aug 1998 17:30:38 +0000 (GMT) Cc: freebsd-fs@FreeBSD.ORG In-Reply-To: from "Hiren Mehta" at Aug 26, 98 12:55:44 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi All, > > In case of MSDOS formatted device, is there any guarantee that the > files are will start on 8192 bytes boundary of the device ? No. There is neither a guarantee that it will start on a 4096 byte boundary, a 2048, or a 1024. There *is* a guarantee that it will start on a 512 byte boundary. In general, where it starts depends on the C:H:S geometry of the device; specifically, DOS likes to write the DOS partition table to place the DOS partitions to start and end on cylinder boundaries. This means that for a default DOS device, where the first partition is not munged by an ill-informed "do-gooder", it will start at the 0 + S * H'th sector. Obviously, this can be on any boundary, whatsoever, based on the values of H and S. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Aug 28 18:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19790 for freebsd-fs-outgoing; Fri, 28 Aug 1998 18:11:28 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from nanguo.chalmers.com.au (gateway.chalmers.com.au [203.1.96.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19775 for ; Fri, 28 Aug 1998 18:11:20 -0700 (PDT) (envelope-from robert@chalmers.com.au) Received: from chalmers.com.au (carbon.chalmers.com.au [203.1.96.26]) by nanguo.chalmers.com.au (8.9.1/8.9.1) with ESMTP id LAA00458 for ; Sat, 29 Aug 1998 11:09:20 +1000 (EST) Message-ID: <35E755EF.53BD3DC@chalmers.com.au> Date: Sat, 29 Aug 1998 11:14:23 +1000 From: Robert Chalmers Reply-To: robert@chalmers.com.au Organization: chalmers.com.au X-Mailer: Mozilla 4.06 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-fs@FreeBSD.ORG Subject: Strange event with filesystem. Cant make Quantum Fireball 3.2 boot? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a strange event. I have this Qunatum Fireball SE3.2S SCSI drive. I have this Adaptec-AHA1540CF/1542CF (SCSI 2) controller. I can set the HDD up using disklabel, and and it works fine as a secondary drive. Three or so filesystems, sd2a/b/c/e/f etc. I can now set it up with disklabel -e, using a disktab, or just editing it with -e. I can do a disklable -B -b boot1 -s boot2 sd2, and it appears to take that fine. So in other words, creating filesystems using disklabel appears to work fine. Except that matter what I do, that sucker will not boot.!! It works fine as a secondary drive, the third drive actually, but if I plug it back in as the primary drive - nada! So, taking the bull by the horns, I thought - ok, lets do this the old-fashioned way. Let's play at being a beginner. Disconnect all other drives, and set up the Quantum as the ONLY HDD in the system. Boot from the 2.2SNAP floppy, CD in place, and fingers crossed. Select Beginner install. Set up the fdisk options, slices, and press Q - no sign of activity, then 'panic i/o error, rebooting'. In other words... It appears that nothing can be written to, or read from the bootsector? Now, is this a bodgie drive ??? (brand new) An incompatible card (it works ok if the drive is secondary) or something that needs setting in the Adaptec configuration that I'm missing. It is pretty simple, but thats no indication. Does anyone have any experience with Quantum Fireball SE 3.2S drives and this problem? Thanks Robert -- Support Whirled Peas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message