From owner-freebsd-fs Wed Sep 8 9:24:47 1999 Delivered-To: freebsd-fs@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 0AB2314DED; Wed, 8 Sep 1999 09:24:44 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id MAA29978; Wed, 8 Sep 1999 12:23:56 -0400 (EDT) Date: Wed, 8 Sep 1999 12:10:05 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: The usage of MNT_RELOAD 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 The flag MNT_RELOAD is not documented in mount manpages. From the source code, I find that it is always used along with MNT_UPDATE which can be speficied by user (-u option). Can anyone explain the usage of MNT_RELOAD for me? It seems not to be used normally. Any help is appreciated. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 9:39:14 1999 Delivered-To: freebsd-fs@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 7943714E3A; Wed, 8 Sep 1999 09:39:07 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FHR00J6P27CES@mta4.rcsntx.swbell.net>; Wed, 8 Sep 1999 11:38:01 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id LAA92249; Wed, 08 Sep 1999 11:37:49 -0500 (CDT envelope-from chris) Date: Wed, 08 Sep 1999 11:37:45 -0500 From: Chris Costello Subject: Re: The usage of MNT_RELOAD In-reply-to: To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19990908113744.F88000@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.6i References: Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Sep 08, 1999, Zhihui Zhang wrote: > > The flag MNT_RELOAD is not documented in mount manpages. From the source > code, I find that it is always used along with MNT_UPDATE which can be > speficied by user (-u option). Can anyone explain the usage of MNT_RELOAD > for me? It seems not to be used normally. It looks like it 'reloads' the file system when you change the mount flags, e.g. changing a synchronous file system to an asynchronous file system, without really un-mounting it. -- |Chris Costello |Base 8 is just like base 10, if you are missing two fingers. - Tom Lehrer `-------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 9:45: 4 1999 Delivered-To: freebsd-fs@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 1CFE015026; Wed, 8 Sep 1999 09:44:51 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id MAA10197; Wed, 8 Sep 1999 12:44:11 -0400 (EDT) (envelope-from luoqi) Date: Wed, 8 Sep 1999 12:44:11 -0400 (EDT) From: Luoqi Chen Message-Id: <199909081644.MAA10197@lor.watermarkgroup.com> To: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, zzhang@cs.binghamton.edu Subject: Re: The usage of MNT_RELOAD Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The flag MNT_RELOAD is not documented in mount manpages. From the source > code, I find that it is always used along with MNT_UPDATE which can be > speficied by user (-u option). Can anyone explain the usage of MNT_RELOAD > for me? It seems not to be used normally. > > Any help is appreciated. > > -------------------------------------------------- > Zhihui Zhang. Please visit http://www.freebsd.org > -------------------------------------------------- > It is created almost exclusively for fsck (and similar programs) to update the in core image of the superblock (of / in single user mode) after the on disk version has been modified. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 10:50: 4 1999 Delivered-To: freebsd-fs@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 04F3514D5B; Wed, 8 Sep 1999 10:49:56 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id NAA09216; Wed, 8 Sep 1999 13:48:21 -0400 (EDT) Date: Wed, 8 Sep 1999 13:34:30 -0400 (EDT) From: Zhihui Zhang To: Luoqi Chen Cc: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: The usage of MNT_RELOAD In-Reply-To: <199909081644.MAA10197@lor.watermarkgroup.com> 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 Wed, 8 Sep 1999, Luoqi Chen wrote: > > The flag MNT_RELOAD is not documented in mount manpages. From the source > > code, I find that it is always used along with MNT_UPDATE which can be > > speficied by user (-u option). Can anyone explain the usage of MNT_RELOAD > > for me? It seems not to be used normally. > > > It is created almost exclusively for fsck (and similar programs) to update > the in core image of the superblock (of / in single user mode) after the > on disk version has been modified. > Does fsck have to run on a MOUNTED filesystem? If so, your answer makes sense to me: if fsck modifies the on-disk copy of the superblock, it does not have to unmount and then remount the filesystem, it only need to reload the superlock for disk. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 10:57:38 1999 Delivered-To: freebsd-fs@freebsd.org Received: from marcy.nas.nasa.gov (marcy.nas.nasa.gov [129.99.113.17]) by hub.freebsd.org (Postfix) with ESMTP id 927F114CB3; Wed, 8 Sep 1999 10:57:34 -0700 (PDT) (envelope-from wrstuden@marcy.nas.nasa.gov) Received: from localhost (wrstuden@localhost) by marcy.nas.nasa.gov (8.9.3/NAS8.8.7n) with SMTP id KAA14033; Wed, 8 Sep 1999 10:57:05 -0700 (PDT) Date: Wed, 8 Sep 1999 10:57:05 -0700 (PDT) From: Bill Studenmund To: Zhihui Zhang Cc: Luoqi Chen , freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: The usage of MNT_RELOAD 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 Wed, 8 Sep 1999, Zhihui Zhang wrote: > > Does fsck have to run on a MOUNTED filesystem? If so, your answer makes > sense to me: if fsck modifies the on-disk copy of the superblock, it does > not have to unmount and then remount the filesystem, it only need to > reload the superlock for disk. I think it's more for the case where fsck has to run on a filesystem which is mounted. It's better to fsck unmounted filesystems, but you don't always have that option (say you want to fsck the fs with fsck on it :-) Take care, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 11: 1:57 1999 Delivered-To: freebsd-fs@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 3B5441547E for ; Wed, 8 Sep 1999 11:01:48 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 97521 invoked from network); 8 Sep 1999 18:00:50 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 8 Sep 1999 18:00:50 -0000 Date: Wed, 8 Sep 1999 13:00:50 -0500 (CDT) From: David Scheidt To: Zhihui Zhang Cc: Luoqi Chen , freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: The usage of MNT_RELOAD 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 Wed, 8 Sep 1999, Zhihui Zhang wrote: > > On Wed, 8 Sep 1999, Luoqi Chen wrote: > > > It is created almost exclusively for fsck (and similar programs) to update > > the in core image of the superblock (of / in single user mode) after the > > on disk version has been modified. > > > > Does fsck have to run on a MOUNTED filesystem? If so, your answer makes > sense to me: if fsck modifies the on-disk copy of the superblock, it does > not have to unmount and then remount the filesystem, it only need to > reload the superlock for disk. The root filesystem is mounted when it is fscked, as it is difficult to run fsck, which lives on the root filesystem, without mounting the root filesystem. You shouldn't run fsck on a mounted filesystem, except for this. The results are generally not fun. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 11: 8:58 1999 Delivered-To: freebsd-fs@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 072301506B; Wed, 8 Sep 1999 11:08:52 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id 7F8A2F817; Wed, 8 Sep 1999 14:07:44 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 71FF09B1C; Wed, 8 Sep 1999 14:07:44 -0400 (EDT) Date: Wed, 8 Sep 1999 14:07:44 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Zhihui Zhang Cc: Luoqi Chen , freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: The usage of MNT_RELOAD 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 Wed, 8 Sep 1999, Zhihui Zhang wrote: > > On Wed, 8 Sep 1999, Luoqi Chen wrote: > > > > The flag MNT_RELOAD is not documented in mount manpages. From the source > > > code, I find that it is always used along with MNT_UPDATE which can be > > > speficied by user (-u option). Can anyone explain the usage of MNT_RELOAD > > > for me? It seems not to be used normally. > > > > > It is created almost exclusively for fsck (and similar programs) to update > > the in core image of the superblock (of / in single user mode) after the > > on disk version has been modified. > > > > Does fsck have to run on a MOUNTED filesystem? If so, your answer makes > sense to me: if fsck modifies the on-disk copy of the superblock, it does > not have to unmount and then remount the filesystem, it only need to > reload the superlock for disk. > Filesystems do not have to be mounted to fsck them (in fact, it is generally bad to have them mounted rw when fsck'd); however, in order for the root filesystem to be fsck'd on boot, it must be mounted ro in order to access the fsck program itself. After done fsck'ing, it can remount rw for normal operation, done without actually unmounting the filesystem. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 11:12: 4 1999 Delivered-To: freebsd-fs@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id F111C14FFB; Wed, 8 Sep 1999 11:12:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA88623; Wed, 8 Sep 1999 11:11:12 -0700 (PDT) (envelope-from dillon) Date: Wed, 8 Sep 1999 11:11:12 -0700 (PDT) From: Matthew Dillon Message-Id: <199909081811.LAA88623@apollo.backplane.com> To: David Scheidt Cc: Zhihui Zhang , Luoqi Chen , freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: The usage of MNT_RELOAD References: Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :> Does fsck have to run on a MOUNTED filesystem? If so, your answer makes :> sense to me: if fsck modifies the on-disk copy of the superblock, it does :> not have to unmount and then remount the filesystem, it only need to :> reload the superlock for disk. : :The root filesystem is mounted when it is fscked, as it is difficult to run :fsck, which lives on the root filesystem, without mounting the root :filesystem. You shouldn't run fsck on a mounted filesystem, except for :this. The results are generally not fun. : :David Scheidt The root filesystem is mounted *READ-ONLY* initially. fsck is then run on all filesystems. Once fsck is done the root filesystem is remounted R/W and the remaining filesystems are mounted R/W. It's relatively safe to run fsck on a filesytem which has been mounted read-only. It is not safe to run fsck on a filesystem which has been mounted R/W. It is best, of course, to run fsck only on filesystems that have not been mounted but this cannot be done for the root filesystem for obvious reasons, hence the read-only mount + fsck + remount R/W. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 11:31:50 1999 Delivered-To: freebsd-fs@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A6BFB14BD0; Wed, 8 Sep 1999 11:31:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA45621; Wed, 8 Sep 1999 12:31:09 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA21513; Wed, 8 Sep 1999 12:30:48 -0600 (MDT) Message-Id: <199909081830.MAA21513@harmony.village.org> To: Matthew Dillon Subject: Re: The usage of MNT_RELOAD Cc: David Scheidt , Zhihui Zhang , Luoqi Chen , freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Sep 1999 11:11:12 PDT." <199909081811.LAA88623@apollo.backplane.com> References: <199909081811.LAA88623@apollo.backplane.com> Date: Wed, 08 Sep 1999 12:30:48 -0600 From: Warner Losh Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199909081811.LAA88623@apollo.backplane.com> Matthew Dillon writes: : It is best, of course, to run fsck only on filesystems that have not : been mounted but this cannot be done for the root filesystem for obvious : reasons, hence the read-only mount + fsck + remount R/W. Back in the Bad Old Days, when this option didn't exist, if fsck changed ANYTHING on /, the system rebooted... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 11:46:43 1999 Delivered-To: freebsd-fs@freebsd.org Received: from alexandria.cs.uchicago.edu (alexandria.cs.uchicago.edu [128.135.11.87]) by hub.freebsd.org (Postfix) with ESMTP id 2275C14BE7 for ; Wed, 8 Sep 1999 11:46:35 -0700 (PDT) (envelope-from dayton@overx.com) Received: from mecca.overx.com (kropp-duster.cs.uchicago.edu [128.135.11.102]) by alexandria.cs.uchicago.edu (8.9.1/8.9.3) with ESMTP id NAA07042 for ; Wed, 8 Sep 1999 13:45:29 -0500 (CDT) Received: from everest.overx.com (mail.overx.com [192.168.10.249]) by mecca.overx.com (Postfix) with ESMTP id 8D5C66C801 for ; Wed, 8 Sep 1999 13:44:17 -0500 (CDT) Received: from polo.overx.com (polo.overx.com [192.168.10.11]) by everest.overx.com (Postfix) with ESMTP id 6A6B91F93 for ; Wed, 8 Sep 1999 13:45:08 -0500 (CDT) Received: by polo.overx.com (Postfix, from userid 1001) id 828A83EC1; Wed, 8 Sep 1999 13:44:59 -0500 (CDT) From: Soren Dayton Reply-To: dayton+freebsd-fs@overx.com To: freebsd-fs@freebsd.org Subject: How much work to make nullfs work? Date: 08 Sep 1999 13:44:59 -0500 Message-ID: <86wvu14504.fsf@polo.overx.com> Lines: 9 User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) XEmacs/21.1 (Big Bend) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I would really be interested in using a loopback mount. What sorts of work would be involved in making this work? How/when did this get broken? Thanks Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Sep 8 22:52: 1 1999 Delivered-To: freebsd-fs@freebsd.org Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [195.24.160.51]) by hub.freebsd.org (Postfix) with ESMTP id 82B3E151C6 for ; Wed, 8 Sep 1999 22:51:54 -0700 (PDT) (envelope-from anders@enterprise.sanyusan.se) Received: (from anders@localhost) by enterprise.sanyusan.se (8.9.3/8.9.3) id HAA01091 for fs@freebsd.org; Thu, 9 Sep 1999 07:51:13 +0200 (CEST) (envelope-from anders) Date: Thu, 9 Sep 1999 07:51:13 +0200 From: Anders Andersson To: fs@freebsd.org Subject: RPM in disklabel Message-ID: <19990909075113.A1034@enterprise.sanyusan.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just got a new SCSI disk: da5 at ahc0 bus 0 target 12 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) and I noted if I read the disklabel 'disklabel -r /dev/da5s1e' it says 'rpm: 3600' This drive got a RPM of 7200, is it safe to change this in the disklabel? Will it matter? Thanks for any advise. Anders -- Anders Andersson anders@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Sep 9 8:30:22 1999 Delivered-To: freebsd-fs@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id A085B160ED for ; Thu, 9 Sep 1999 08:29:24 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id RAA14584; Thu, 9 Sep 1999 17:29:20 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id RAA23830; Thu, 9 Sep 1999 17:28:51 +0200 (MET DST) Date: Thu, 9 Sep 1999 17:28:47 +0200 From: Eivind Eklund To: Soren Dayton Cc: freebsd-fs@FreeBSD.ORG Subject: Re: How much work to make nullfs work? Message-ID: <19990909172847.E23200@bitbox.follo.net> References: <86wvu14504.fsf@polo.overx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <86wvu14504.fsf@polo.overx.com>; from Soren Dayton on Wed, Sep 08, 1999 at 01:44:59PM -0500 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Sep 08, 1999 at 01:44:59PM -0500, Soren Dayton wrote: > > Hi, > > I would really be interested in using a loopback mount. What sorts of > work would be involved in making this work? Quite a bit. I've started some of it, but have had very little time I've been able to dedicate to FreeBSD since ~christmas. > How/when did this get broken? The full breakage came With the VM system re-vamp right after 2.0. There are a bunch of lock bugs and similar which also create problems, but they're not quite as severe as that breakage (but this breakage is spread throughout the system, and needs quite a bit of work to clean up). I have patches for both fixing some of the major problems (VM object aliases, for instance), and for debugging the locks, and for some of the lock problems. Yell if you want them. McKusick also said he was going to start working on this when he came back from vacation, but I'm sure he'll appreciate help (e.g, fixing more of the lock bugs, which I'd like to do, but don't know when I'll have time to do more of :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Sep 9 22:43: 3 1999 Delivered-To: freebsd-fs@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0456115343 for ; Thu, 9 Sep 1999 22:42:55 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id HAA06360 for fs@freebsd.org; Fri, 10 Sep 1999 07:42:33 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 29629870A; Fri, 10 Sep 1999 07:29:26 +0200 (CEST) Date: Fri, 10 Sep 1999 07:29:26 +0200 From: Ollivier Robert To: fs@freebsd.org Subject: Re: RPM in disklabel Message-ID: <19990910072926.A16448@keltia.freenix.fr> Mail-Followup-To: fs@freebsd.org References: <19990909075113.A1034@enterprise.sanyusan.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <19990909075113.A1034@enterprise.sanyusan.se>; from Anders Andersson on Thu, Sep 09, 1999 at 07:51:13AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5593 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Anders Andersson: > This drive got a RPM of 7200, is it safe to change this in the > disklabel? Yes. > Will it matter? Don't think so. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message