HP Proliant / Redhat Linux disks & filesystems question

[s2budd]

Hello all

I am looking after a HP ProLiant DL380 Redhat linux machine
running kernel 2.4.9-e.24smp.

The DL380 has disks 0 to 5 installed, each being 72.8 GB
There is also a Storeage Works connected (I think) with bays 1 to 3 used, each containing 148.8 GB disks.

I would like to find out what actual disks I have installed via the command line and if there is 20 GB of unused disk space on any of the disks.

Forgive me but I am used to the Solaris format and df commands and I am stuck within Linux.

I have tried various combinations of fdisk -l [device] but I an not getting anywhere.

Any help would be apreciated.
Cheers, Stuart

 

[Chacalinc]

take a look to the /proc folder.. it has all the current configuration of your system (they are files generated on the fly about your system). Take a look to /proc/scsi

If my memory serves me, HP proliant uses cciss controllers, so you should see your internal disks in /proc/scsi/cciss and external in /proc/scsi.

can we see the result of [tt]df -h[/tt] command?

Cheers.



"Avoid virus, boil your PC 1 min. before use it

 

[SamBones]

You may not be able to see the individual disks. If there is a hardware RAID controller in the Proliant, then what the OS sees depends on how the array is configured. I have the same hardware and I've set the drives in the array as one large logical volume. So even though it's multiple disks, it looks like one big one to the OS. Then in the OS I can partition that into the file systems I want.

I use the Smartstart CD to configure the array before the OS install.

Hope this helps.

 

[s2budd]

Thanks for the replies. Very helpful.

I think that the following filesystem is free

/dev/cciss/c0d1p5 14025 14662 5124703+ 83 Linux


In order to come to this assumption I used the commands below. If someone could check this and let me know if I am right and if so how to use the spare spare space then that would be great. Thanks.

One thing I do not understand though is how one filesystem is mounted from none as shown in the df output.

none 1005M 0 1005M 0% /dev/shm


ls -alp /proc/scsi
total 0
dr-xr-xr-x 2 root root 0 Jul 1 10:32 ./
dr-xr-xr-x 298 root root 0 Nov 23 2004 ../
-r--r--r-- 1 root root 0 Jul 1 10:32 scsi

df -h
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p2 3.9G 1.4G 2.3G 38% /
/dev/cciss/c0d0p1 99M 14M 79M 15% /boot
none 1005M 0 1005M 0% /dev/shm
/dev/cciss/c0d0p5 1.5G 279M 1.1G 20% /var
/dev/cciss/c0d0p6 23G 15G 7.0G 68% /software
/dev/cciss/c0d0p7 96G 71G 20G 78% /MAD/area01
/dev/cciss/c0d1p2 95G 76G 13G 85% /MAD/area02
/dev/cciss/c0d0p8 9.5G 6.5G 2.5G 72% /ualn01/app
/dev/cciss/c0d0p9 19G 46M 18G 1% /ftphome
/dev/cciss/c0d0p10 95G 57G 33G 63% /data
/dev/cciss/c0d1p1 9.5G 17M 8.9G 1% /logs
/dev/cciss/c0d1p6 14G 13G 1018M 93% /ICL


fdisk /dev/cciss/c0d0

The number of cylinders for this disk is set to 44274.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/cciss/c0d0: 255 heads, 63 sectors, 44274 cylinders
Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 13 104391 83 Linux
/dev/cciss/c0d0p2 14 535 4192965 83 Linux
/dev/cciss/c0d0p3 536 796 2096482+ 82 Linux swap
/dev/cciss/c0d0p4 797 44274 349237035 5 Extended
/dev/cciss/c0d0p5 797 994 1590403+ 83 Linux
/dev/cciss/c0d0p6 995 4000 24145663+ 83 Linux
/dev/cciss/c0d0p7 4001 16749 102406311 83 Linux
/dev/cciss/c0d0p8 16750 18024 10241406 83 Linux
/dev/cciss/c0d0p9 18025 20574 20482843+ 83 Linux
/dev/cciss/c0d0p10 20575 33323 102406311 83 Linux


fdisk /dev/cciss/c1d0

Unable to open /dev/cciss/c1d0
[root@ualn01 /software]# fdisk /dev/cciss/c0d1

The number of cylinders for this disk is set to 35697.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/cciss/c0d1: 255 heads, 63 sectors, 35697 cylinders
Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d1p1 1 1275 10241406 83 Linux
/dev/cciss/c0d1p2 1276 14024 102406342+ 83 Linux
/dev/cciss/c0d1p3 14025 35697 174088372+ 5 Extended
/dev/cciss/c0d1p5 14025 14662 5124703+ 83 Linux
/dev/cciss/c0d1p6 14663 16575 15366141 83 Linux


Nothing on the following devices:
fdisk -l /dev/cciss/c0d2
fdisk -l /dev/cciss/c0d3
fdisk -l /dev/cciss/c0d4
fdisk -l /dev/cciss/c0d5
fdisk -l /dev/cciss/c0d6
fdisk -l /dev/cciss/c0d7
fdisk -l /dev/cciss/c0d8
fdisk -l /dev/cciss/c0d9
fdisk -l /dev/cciss/c0d10
fdisk -l /dev/cciss/c0d11
fdisk -l /dev/cciss/c0d12
fdisk -l /dev/cciss/c0d13
fdisk -l /dev/cciss/c0d14
fdisk -l /dev/cciss/c0d15
fdisk -l /dev/cciss/c1d0
fdisk -l /dev/cciss/c1d1
fdisk -l /dev/cciss/c1d2
fdisk -l /dev/cciss/c1d3
fdisk -l /dev/cciss/c1d4
fdisk -l /dev/cciss/c1d5
fdisk -l /dev/cciss/c1d6
fdisk -l /dev/cciss/c1d7
fdisk -l /dev/cciss/c1d8
fdisk -l /dev/cciss/c1d9
fdisk -l /dev/cciss/c1d10
fdisk -l /dev/cciss/c1d11
fdisk -l /dev/cciss/c1d12
fdisk -l /dev/cciss/c1d13
fdisk -l /dev/cciss/c1d14
fdisk -l /dev/cciss/c1d15

 

[Chacalinc]

as I can see, your assumption is correct, /dev/cciss/c0d1p5.

I would try mounting it first in order to ensure that you don't have any data on it:

[tt]mount /dev/cciss/c0d1p5 /mnt[/tt]

if this command get errors, probably there is no filesystem, so:

[tt]mkfs /dev/cciss/c0d1p5
tune2fs -j /dev/cciss/c0d1p5
mount /dev/cciss/c0d1p5 /mnt[/tt]

Cheers.

"Avoid virus, boil your PC 1 min. before use it

 

[s2budd]

Chacalinc and SamBones
Many thanks for your help. I now have a new filesystem.
Cheers, Stuart