From owner-freebsd-fs Tue Jul 22 17:16:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA09560 for fs-outgoing; Tue, 22 Jul 1997 17:16:40 -0700 (PDT) Received: from gatekeeper.megamedia.pt (gatekeeper.megamedia.pt [194.79.67.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA09544 for ; Tue, 22 Jul 1997 17:16:26 -0700 (PDT) Received: from pc_andre.megamedia.pt (pc24.megamedia.pt [194.79.67.24]) by gatekeeper.megamedia.pt (8.8.5/8.8.5) with SMTP id AAA01703 for ; Wed, 23 Jul 1997 00:16:17 +0100 (WEST) Received: by localhost with Microsoft MAPI; Wed, 23 Jul 1997 01:13:29 +0100 Message-ID: <01BC9705.A12AD220.Andre.Carvalho@megamedia.pt> From: André Esteves de Carvalho Reply-To: "Andre.Carvalho@megamedia.pt" To: "'freebsd-fs@FreeBSD.ORG'" Subject: hard disk reading errors Date: Wed, 23 Jul 1997 01:13:28 +0100 Organization: MegaMedia, SA X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA09551 Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, The disk of my freebsd 2.0.5 started to report this kind of errors: wds1e: hard error reading fsbn xxxxxx of xxxxx-xxxxx (wd1 bn xxxx; cn xxx tn xx sn xx)wd1:status 59 error 40 I am very worried since I have already lost some directories very important to me. I think the files are there but how can I recover them? I tried fsck but it seems to do nothing about bad blocks... Can anyone help me with a solution or at list a good description of what the error message fully means?? Thank you in advance. Please answer directly because I don't subscrive this list at the moment. André --------------------------------------------------------------- Andre' Esteves de Carvalho Gestor de Projecto / Project Manager Atenção: Nova morada, telefones e fax!!! MegaMedia, Solucoes Multimedia, SA Edif. Arroios, R. António Pedro 111, 1ºBC 1150 Lisboa, Portugal Tel: (+351 - 1) 317 22 60 Fax: (+351 - 1) 317 22 61 mailto:Andre.Carvalho@megamedia.pt http://www.megamedia.pt From owner-freebsd-fs Wed Jul 23 05:54:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA14823 for fs-outgoing; Wed, 23 Jul 1997 05:54:35 -0700 (PDT) Received: from nefertiti.lightningweb.com (nefertiti.lightningweb.com [198.68.191.157]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14805; Wed, 23 Jul 1997 05:54:32 -0700 (PDT) Received: from localhost (greg@localhost) by nefertiti.lightningweb.com (8.8.5/8.8.5) with SMTP id FAA25193; Wed, 23 Jul 1997 05:53:19 GMT Date: Wed, 23 Jul 1997 05:53:19 +0000 () From: "Greg K. Cagle" To: freebsd-fs@freebsd.org cc: freebsd-scsi@freebsd.org Subject: adding RAID to the OS without re-partitioning Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I plan on adding a RAID disk array to my existing server. Ther server has three HDD's in it now, with "/" as one, "/usr/" as another, and a spare that's partitioned as "/scratch/". The disk array will be an independent unit, and will hook up to the external port on my Adaptec 2940UW. The company (Baydel) says that the array will appear as one large volume to FreeBSD. My question: How do I include the new array as part of the filesystem, without re-installing? I know I can make those choices when I first install the OS, but can I add a partition now, without messing up anything? I want to end up with the large RAID as my "/usr/" partition. Thanks for suggestions, Greg ps I have 2.1.5 on a Pentium Pro 200 with 128MB ram. ***************************************** Greg K. Cagle - The Chief - Lightningweb http://www.lightningweb.com From owner-freebsd-fs Wed Jul 23 23:21:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11746 for fs-outgoing; Wed, 23 Jul 1997 23:21:48 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA11714 for ; Wed, 23 Jul 1997 23:21:35 -0700 (PDT) Received: (qmail 22008 invoked by uid 1000); 24 Jul 1997 06:21:48 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 23 Jul 1997 23:21:48 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Greg K. Cagle" Subject: RE: adding RAID to the OS without re-partitioning Cc: freebsd-scsi@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Greg K. Cagle"; On 23-Jul-97 you wrote: > I plan on adding a RAID disk array to my existing server. Ther server > has > three HDD's in it now, with "/" as one, "/usr/" as another, and a spare > that's partitioned as "/scratch/". > > The disk array will be an independent unit, and will hook up to the > external port on my Adaptec 2940UW. The company (Baydel) says that the > array will appear as one large volume to FreeBSD. > > My question: How do I include the new array as part of the filesystem, > without re-installing? I know I can make those choices when I first > install the OS, but can I add a partition now, without messing up > anything? I want to end up with the large RAID as my "/usr/" partition. > > Thanks for suggestions, > > Greg > > ps I have 2.1.5 on a Pentium Pro 200 with 128MB ram. Since no on else took it on, I will donate my $0.02. This is really not a SCSI issue at all. essentially, this is what you do: First, find out the name and size of the disk. Right after booting, do: dmesg | grep '^sd[0-9]' This will give you some output like: sd17(dpt0:1:0): Direct-Access 16394MB (32542592 528 byte sectors) You want to remember two things from the above example: 1. The disk is sd17 2. The reported size is 32,542,592 sectors. If you see (on a DPT): sd17: Forcing sector size to 512 Ignore that. It simply tells you that the disks have a physical size of 528 bytes. We use that to record ECC data. This insures that data transfers on the SCSI bus (cable) are ECC corrected. That's all. Next, create a file with this format: # This is the Sendero/Nomis SCSI RAID-5 array # It is composed of five 4GB Baracudas. # Reported capacity is 16,394MB (32,542,592x528) # Aligned to 1Mb ``cylinders'' it yields 32,540,672x512 blocks # or 15,889 ``cylinders'' # # Do not adjust partitions!!! g c15889 h64 s32 p 1 165 64 8388544 p 2 165 8388608 8388608 p 3 165 16777216 8388608 p 4 165 25165824 7374848 Adjust the cXXXX field in the geometry record to match capacity of the device (I take the number of sectors and mod 2048 itto arrive at the number of 1MB ``cylinders'' we have. It costs few megbytes of space but is so much easier to handle. The next step is to edit /etc/disktab and create an entry for each of these partitions. The terminology is confusing. What we have done so far is plan on which ``partitions'' will fdisk create. From this point forward, these partitions are actually called ``slices''. Also notice that until recently fdisk partitions (slices) were numbered 0-3, while disklabel slices are 1-4. Recently, at least this part is uniform; fdisk partitions are 1-4 and dislabel slices (same thing!) are also 1-4. Below is a typical /etc/disktab, for the LAST partition-slice (4) in the above RAID array: sd17.s4|sendero-5.s4|DPT Raid-5 composed of five 4GB Baracudas:\ :ty=simulated:\ :ns#2048:\ :nt#1:\ :nc#3601: \ <--- number of ``cylinders'' :sc#2048: \ :su#7374848:\ <---- su = nc * sc :se#512:\ :rm#7200:\ :pc#7374848:oc#0:tc=unused:bc#4096:fc#512: \ <-- the whole device :pa#2097088:oa#64:ta=4.2BSD:ba#4096:fa#512: \ <-- Partition a :pb#5277696:ob#2097152:tb=4.2BSD:bb#4096:fb#512: <-- partition b You can have partitions a,b,d,e,f,g,h. In theory you can have c as a partition but certain utilities ``know'' that c is hte whoile disk. Some things in FreeBSD also ``know'' that ``b'' is a swap device. Oh, when we say ``partition'' here, we mean FreeBSD partition WITHIN the fdisk partition, or more correctly (in this context); A device contains several fdisk slices, each contains several FreeBSD partitions. Enough ``theory''. go make the necessary nodes: cd /dev ./MAKEDEV sd17 ./MAKEDEV sd17s1a The above two created all the necessary entried for all the partitions, slices, and what-have-you. Now do: fdisk -i -f my_own_fdisk_file sd17 Now Listen Carefully: * MAKE SURE, ABSOLUTELY SURE you have dumped fdisk of your boot disk to a safe file, in the format indicated above. * MAKE SURE, ABSOLUTELY SURE you have the entries for (in our example) sd17 in /dev/ * TYPE the fdisk command EXACTLY as indicated above. Do NOT MISS an argument! If you do not, and I still miss sometimes, fdisk will write the new configuration, or some version of it ON YOUR BOOT DRIVE!!! It will do so with glee, quielty, without warning (sorry, it will put on the screen something like ``******* working on /dev/sd0 ****'' which you will MISS as you are so unsure and nervous about wiping your system out. If you saw that, you just did. If you did, don't panic! and DO NOT, I repeat, DO NOT reboot or shutdown your system! Just follow this procedure, to re-create the boot disk partitions-slices. Or back it up. you did back it up BEFORE starting this procedure. Right? Right... but did you actually read that tape? If all is well, fdisk will create the partitions and complain about the disk labels. This is OK. There are no labels yet, so why should they be correct? Once this is done, do the following: disklabel -w -r sd17s4 sd17.s4 "short/meaningful label" This will create /dev/sd17s4a and /dev/sd17s4b. As you run disklabel, it will complain about the label for this partition and for all the slices too. The reason is that when FreeBSD opens ANY raw device, it reads the fdisk data for the disk and all the labels for all the slices. Since you are just creating them, there will be complaints. just run each disklabel command twice and the complaint will disappear for that slice. After you created/labeled three slices, it will not complain about the fourth. If you want file systems there do: newfs /dev/rsd17s4a newfs /dev/rsd17s4b You can embelish, tune and improve how newfs makes the file system. You can change things with tunefs (or some such). I am not the person to ask about that. I use newfs as is. The last steps are just as easy. Say you have already /var/spool/news and you want to move it from /var to this new array, splitting it between two filesystems. Last time I installed news I had /var/spool/news/alt/binaries on a separate filesystem. Let's use that as an example. Edit /etc/fstab and add two new lines. Emulate what is already there, just replace the first two fields. Shutdown the news server. mount /dev/sd17s4a /mnt mkdir -p /mnt/alt/binaries chown news.news /mnt /mnt/alt/binaries mount /dev/sd17s4b /mnt/alt/binaries chown news.news /mnt/alt/binaries # Trust me on this one :-) cd /var/spool/news find . | cpio -dmpv /mnt sync umount /mnt/alt/binaries umount /mnt rm -rf /var/spool/news/* mount /var/spool/news mount /var/spool/news/alt/binaries Simple. Isn't it? And they said Unix is not better than NT. simon From owner-freebsd-fs Thu Jul 24 10:43:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14307 for fs-outgoing; Thu, 24 Jul 1997 10:43:16 -0700 (PDT) Received: from metrocon.com (root@metrocon.com [208.9.142.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14289; Thu, 24 Jul 1997 10:43:12 -0700 (PDT) Received: from metrocon.com (fbsd@localhost [127.0.0.1]) by metrocon.com (8.8.5/8.8.3) with ESMTP id NAA05027; Thu, 24 Jul 1997 13:44:05 GMT Message-Id: <199707241344.NAA05027@metrocon.com> To: freebsd-fs@freebsd.org, freebsd-scsi@freebsd.org Subject: CCD FileSystems Date: Thu, 24 Jul 1997 13:44:05 +0000 From: Free BSD Sender: owner-freebsd-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all.. I am having some trouble. I need to do a ccd situation with 2- 9GB uw-scsi drives. Can someone direct me to detailed instructions please? It would also be nice if someone sends me a sample ccd disklabel with instructions on how to impliment it. Thanks alot.. Isaac Kohen Systems Administrator MetroCon Communications From owner-freebsd-fs Thu Jul 24 16:06:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA00278 for fs-outgoing; Thu, 24 Jul 1997 16:06:31 -0700 (PDT) Received: from inet.uni-c.dk (inet.uni-c.dk [130.228.6.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA00269 for ; Thu, 24 Jul 1997 16:06:21 -0700 (PDT) Received: from PRO (kbh208.ppp.uni-c.dk [130.228.10.208]) by inet.uni-c.dk (8.8.4/8.6.9) with SMTP id BAA11013 for ; Fri, 25 Jul 1997 01:04:37 +0200 (METDST) Received: by PRO with Microsoft Mail id <01BDB768.094D8900@PRO >; Sat, 25 Jul 1998 01:03:29 +0200 Message-ID: <01BDB768.094D8900@PRO > From: Soren Brandt To: "'freebsd-fs@FreeBSD.ORG'" Date: Sat, 25 Jul 1998 01:03:23 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-fs Fri Jul 25 08:12:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA07443 for fs-outgoing; Fri, 25 Jul 1997 08:12:43 -0700 (PDT) Received: from roguetrader.com (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA07437 for ; Fri, 25 Jul 1997 08:12:41 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id JAA05193 for ; Fri, 25 Jul 1997 09:12:44 -0600 (MDT) Date: Fri, 25 Jul 1997 09:12:44 -0600 (MDT) From: Brandon Gillespie To: freebsd-fs@freebsd.org Subject: open advfs-like fs? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just curious, has anybody ever considered an open advfs-like spec? I only say this, because I seem to recall there were some problems with implementing the actual advfs that made it not worth the effort (copyright, or hard to get all specs, or some such). With this in mind, what about doing an open spec which would implement the same sortof thing--perhaps even get the other free unix groups all involved (at least in the spec :) I for one would love to have the ability of advfs in FreeBSD. -Brandon Gillespie