[GLLUG] RE: partitioning Compaq raid devices
Mark Szidik/mlc
SzidikM@mlcnet.org
Wed, 4 Sep 2002 16:31:34 -0400
He gang,
I hope someone out there can help me with this. below is the outpuf of
fdisk looking at a Compaq RAID device. I have not worked with a HW raid
device before, so the fdisk output is scaring me a bit (all the stuff about
the physical/logical beginnings and the start and end cylinder numbers all
being 1) . We don't want to use fdisk to change patitions, just want to be
sure things are ok and can put partition 4 to work.
Partitions 1, 2, 5, 6, 7, 8 are all mounted and are working just fine.
What we are hoping is that we can do a mkfs on partition 4
(/dev/cciss/c0d0p4) and not mess anything else up. Any thoughts?
Thanks,
~~~
Mark Szidik, System Administrator
Michigan Library Consortium
1407 Rensen Street, Suite 1, Lansing, MI 48910-3657
Ph:800.530.9019 x17 Fax:517.394.2096
----- Forwarded by Mark Szidik/mlc on 09/04/02 04:21 PM -----
"Karen C.
Ventura" To: "Mark Szidik/mlc" <SzidikM@mlcnet.org>
<kknox@tln.li cc:
b.mi.us> Subject: RE: Linux FS's
09/04/02
04:15 PM
Mark,
Yeah, ok - that makes sense. (Can you tell I'm not good with this disk
stuff??)
Here's the output of my fdisk:
-------------------------------
[root@novilin kknox]# /sbin/fdisk /dev/cciss/c0d0
Command (m for help): p
Disk /dev/cciss/c0d0: 1 heads, 71106240 sectors, 1 cylinders
Units = cylinders of 71106240 * 512 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 1 53040 83 Linux
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(9, 0, 1) logical=(0, 0, 73441)
Partition 1 has different physical/logical endings:
phys=(21, 254, 32) logical=(0, 0, 179520)
Partition 1 does not end on cylinder boundary:
phys=(21, 254, 32) should be (21, 0, 71106240)
/dev/cciss/c0d0p2 1 1 25104240 83 Linux
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(22, 0, 1) logical=(0, 0, 179521)
Partition 2 has different physical/logical endings:
phys=(1023, 254, 32) logical=(0, 0, 50388000)
Partition 2 does not end on cylinder boundary:
phys=(1023, 254, 32) should be (1023, 0, 71106240)
/dev/cciss/c0d0p3 1 1 36704 12 Compaq
diagnostics
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(0, 1, 1) logical=(0, 0, 33)
Partition 3 has different physical/logical endings:
phys=(8, 254, 32) logical=(0, 0, 73440)
Partition 3 does not end on cylinder boundary:
phys=(8, 254, 32) should be (8, 0, 71106240)
/dev/cciss/c0d0p4 1 1 10359120 f Win95 Ext'd (LBA)
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(1023, 254, 32) logical=(0, 0, 50388001)
Partition 4 has different physical/logical endings:
phys=(1023, 254, 32) logical=(0, 0, 71106240)
Partition 4 does not end on cylinder boundary:
phys=(1023, 254, 32) should be (1023, 0, 71106240)
/dev/cciss/c0d0p5 1 1 9179984 83 Linux
/dev/cciss/c0d0p6 1 1 391664 83 Linux
/dev/cciss/c0d0p7 1 1 522224 82 Linux swap
/dev/cciss/c0d0p8 1 1 261104 83 Linux
Partition table entries are not in disk order
Command (m for help):
----------------------------
Does that mean something to you? :) I know, I know. Looks to me like all
8 partitions on that disk are defined here, but the first 4 look a little
odd - perhaps in the Compaq formatting?
Karen
-------------------------------------------
Karen C. Ventura, MLIS
kknox@tln.lib.mi.us
Head of Systems & Technology
Novi Public Library - Novi, Michigan
-----Original Message-----
From: Mark Szidik/mlc [mailto:SzidikM@mlcnet.org]
Sent: Wednesday, September 04, 2002 4:05 PM
To: Karen C. Ventura
Subject: RE: Linux FS's
Karen,
The first step to creating a new FS (mkfs) is finding a physical location
for it - that is the partition part (fdisk). A Windows analogy would be if
you have a C drive and want to add a D drive you have to have a location to
put D - either on a new hard drive or on some unused space on the original
hard drive. The Windows world does partitioning too with a program also
called fdisk. once you know of a chunk of free space on the physical disks
(using fdisk) you can make that free space into a partition and then make a
new filesystem on that space (windows calls it formatting).
Would you like to me log into the system to see if you have any remaining
unpartitioned space available to setup a new partition and filesystem?
Call me if you do.
This link has some info:
http://www.uwsg.indiana.edu/usail/peripherals/disks/
~~~
Mark Szidik, System Administrator
Michigan Library Consortium
1407 Rensen Street, Suite 1, Lansing, MI 48910-3657
Ph:800.530.9019 x17 Fax:517.394.2096
"Karen C.
Ventura" To: "Mark Szidik/mlc"
<SzidikM@mlcnet.org>
<kknox@tln.li cc:
b.mi.us> Subject: RE: Linux FS's
09/04/02
03:54 PM
Mark,
Thanks for the clarification on the Compaq stuff. But I gotta say, this
seems more complicated to me than I thought it should. I remember making
filesystems with a "mkfs" command on AIX. I don't remember dealing with
paritions per se. Perhaps my initial email to you was off-base. Or
perhaps
not.
So basically, I see that on your machine, you do have a /opt (and /opt0 and
/opt2) partition that is large. I would think that I could create one too,
mount it, and the copy all the data there. Which is kinda like you
originally talked about with moving the data to a section of /usr. I
think.
How did you create your filesystems?
Karen
-------------------------------------------
Karen C. Ventura, MLIS
kknox@tln.lib.mi.us
Head of Systems & Technology
Novi Public Library - Novi, Michigan
-----Original Message-----
From: Mark Szidik/mlc [mailto:SzidikM@mlcnet.org]
Sent: Tuesday, September 03, 2002 3:51 PM
To: kknox@tln.lib.mi.us
Subject: Linux FS's
My df command on RedHat looks like this:
[szidikm@oahu linux]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda7 988M 60M 878M 7% /
/dev/sda3 23M 5.9M 15M 28% /boot
/dev/sda2 3.9G 1.8G 2.0G 47% /usr
/dev/sda8 919M 50M 822M 6% /var
/dev/md0 13G 11G 2.0G 84% /opt
/dev/sdc2 3.2G 24k 3.1G 1% /home
/dev/sdb2 3.2G 20k 3.1G 1% /home0
/dev/sdd1 8.7G 5.9G 2.3G 72% /opt0
/dev/sdd3 16G 2.5G 13G 16% /opt2
/dev/sdd2 8.7G 4.8G 3.5G 58% /home/u
Ok, I did some research (does Google count as research?) and found that the
'cciss' that was throwing me off was the device for a Compaq raid
controller. The world makes sense again.
Lets look at this line: /dev/cciss/c0d0p6
cciss is the device driver for the Compaq controller
the c0 part means controller 0
the d0 part means disk 0
the p6 part means partition 6 (you can have up to 8 on each disk)
Your df list shows partitions 3,4,7 are not being used.
Read this howto to get some background and examples.
http://www.tldp.org/HOWTO/mini/Partition/index.html
then use the very dangerous '/sbin/fdisk' command to look at the disk
itself.
# /sbin/fdisk /dev/cciss/c0d0
p will print the partition data
q will quit
you will have to look at the start and end cylinder number to figure out if
you have any unused space on the disk. If you have space , then read the
Howto again, it shows you how to add new partitions.
HTH
-Mark
~~~
Mark Szidik, System Administrator
Michigan Library Consortium
1407 Rensen Street, Suite 1, Lansing, MI 48910-3657
Ph:800.530.9019 x17 Fax:517.394.2096