topic Re: fdisk, SAN question in Operating System - Linux

fdisk, SAN question

brian_31 — Sun, 24 Dec 2006 17:57:02 GMT

Team:

Good Day!!!

I have pasted the out put of fdisk -l, attached scsi devices.

1. is the system attached to SAN..how can i tell?(i am sure it shd be since i see 1 440G chunk)

2. what about the boot disk..is it mirrored?

3. also i created a new 100G slice (/dev/sda11) and after the reboot i noticed the device name is /dev/sdaq11, how can the device name get changed?

Thanks All...

Best Regards

Brian

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 01
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 02
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 03
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 04
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 05
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 06
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 07
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 08
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 09
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 10
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 11
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 12
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 13
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 14
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 15
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 16
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 17
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 18
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 19
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 00 Lun: 20
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 01
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 02
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 03
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 04
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 05
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 06
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 07
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 08
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 09
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 10
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 11
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 12
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 13
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 14
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 15
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 16
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 17
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 18
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 19
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi1 Channel: 00 Id: 00 Lun: 20
Vendor: 3PARdata Model: VV Rev: 0000
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: SERVERAID Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 15 Lun: 00
Vendor: IBM Model: SERVERAID Rev: 1.00
Type: Processor ANSI SCSI revision: 02
Host: scsi2 Channel: 02 Id: 08 Lun: 00
Vendor: IBM Model: 40K6480a S320 0 Rev: 1
Type: Processor ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: HL-DT-ST Model: RW/DVD GCC-4244N Rev: 1.02
Type: CD-ROM ANSI SCSI revision: 02
[~] 05:56:07# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdaq5 6144304 233500 5598692 5% /
/dev/sdaq1 253855 15794 224955 7% /boot
/dev/sdaq8 2064192 1093476 865860 56% /home
/dev/sdaq2 24238492 3576792 19430444 16% /opt
/dev/sdaq9 1157028 341188 757064 32% /opt/monitor
none 4099276 0 4099276 0% /dev/shm
/dev/sdaq7 3047936 37524 2855584 2% /tmp
/dev/sdaq3 8256952 2760920 5076604 36% /usr
/dev/sdaq6 4128432 196500 3722220 6% /var
/dev/sdu1 1032072 16456 963188 2% /db2/ICMNLSDB
/dev/sdb1 10317828 32852 9760860 1% /db2/ICMNLSDB/db2data1
/dev/sdc1 10317828 32852 9760860 1% /db2/ICMNLSDB/db2data2
/dev/sdd1 5154852 32840 4860156 1% /db2/ICMNLSDB/db2temp1
/dev/sde1 2063504 32832 1925852 2% /db2/ICMNLSDB/log_dir
/dev/sdf1 10317828 106864 9686848 2% /db2/ICMNLSDB/log_archive
/dev/sdg1 1032072 16428 963216 2% /db2/ICMNLSDB/log_retrieve
/dev/sdh1 1032072 72376 907268 8% /db2/ICMNLSDB/db2dump
/dev/sdi1 1032072 331260 648384 34% /db2/db2inst1
/dev/sds1 1032072 16428 963216 2% /tracefiles
/dev/sdt1 1032072 16456 963188 2% /db2/RMDB
/dev/sdk1 10317828 32860 9760852 1% /db2/RMDB/db2data1
/dev/sdl1 10317828 32860 9760852 1% /db2/RMDB/db2data2
/dev/sdm1 5154852 32828 4860168 1% /db2/RMDB/db2temp1
/dev/sdn1 2063504 32832 1925852 2% /db2/RMDB/log_dir
/dev/sdo1 10317828 97536 9696176 1% /db2/RMDB/log_archive
/dev/sdp1 1032072 16428 963216 2% /db2/RMDB/log_retrieve
/dev/sdq1 1032072 16428 963216 2% /db2/RMDB/db2dump
/dev/sdr1 1032072 28072 951572 3% /db2/db2inst2
/dev/sdv1 103210940 4214288 93753844 5% /backup
[~] 05:56:31
# fdisk -l

Disk /dev/sdag: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdag1 1 1305 10482381 83 Linux

Disk /dev/sdah: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdah1 1 652 5237158+ 83 Linux

Disk /dev/sdai: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdai1 1 261 2096451 83 Linux

Disk /dev/sdaj: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdaj1 1 1305 10482381 83 Linux

Disk /dev/sdak: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdak1 1 1024 1048560 83 Linux

Disk /dev/sdal: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdal1 1 1024 1048560 83 Linux

Disk /dev/sdam: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdam1 1 1024 1048560 83 Linux

Disk /dev/sdan: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdan1 1 1024 1048560 83 Linux

Disk /dev/sdao: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdao1 1 1024 1048560 83 Linux

Disk /dev/sdap: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdap1 1 1024 1048560 83 Linux

Disk /dev/sdaq: 440.4 GB, 440442814464 bytes
128 heads, 32 sectors/track, 210019 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Device Boot Start End Blocks Id System
/dev/sdaq1 * 1 128 262128 83 Linux
/dev/sdaq2 129 12152 24625152 83 Linux
/dev/sdaq3 12153 16248 8388608 83 Linux
/dev/sdaq4 16249 210019 396843008 f Win95 Ext'd (LBA)
/dev/sdaq5 16249 19296 6242288 83 Linux
/dev/sdaq6 19297 21344 4194288 83 Linux
/dev/sdaq7 21345 22856 3096560 83 Linux
/dev/sdaq8 22857 23880 2097136 83 Linux
/dev/sdaq9 23881 24454 1175536 83 Linux
/dev/sdaq10 24455 25454 2047984 82 Linux swap
/dev/sdaq11 25455 75523 102541296 83 Linux

Disk /dev/sdq: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdq1 1 1024 1048560 83 Linux

Disk /dev/sdr: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdr1 1 1024 1048560 83 Linux

Disk /dev/sds: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sds1 1 1024 1048560 83 Linux

Disk /dev/sdt: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdt1 1 1024 1048560 83 Linux

Disk /dev/sdu: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdu1 1 1024 1048560 83 Linux

Disk /dev/sdv: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdv1 1 13054 104856223+ 83 Linux

Disk /dev/sdw: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdw1 1 1305 10482381 83 Linux

Disk /dev/sdx: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdx1 1 1305 10482381 83 Linux

Disk /dev/sdy: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdy1 1 652 5237158+ 83 Linux

Disk /dev/sdz: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdz1 1 261 2096451 83 Linux

Disk /dev/sdaa: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdaa1 1 1305 10482380+ 83 Linux

Disk /dev/sdab: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdab1 1 1024 1048560 83 Linux

Disk /dev/sdac: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdac1 1 1024 1048560 83 Linux

Disk /dev/sdad: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdad1 1 1024 1048560 83 Linux

Disk /dev/sdae: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdae1 1 1024 1048560 83 Linux

Disk /dev/sdaf: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdaf1 1 1305 10482381 83 Linux

Disk /dev/sda: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 13054 104856223+ 83 Linux

Disk /dev/sdb: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 1305 10482381 83 Linux

Disk /dev/sdc: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 1305 10482381 83 Linux

Disk /dev/sdd: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdd1 1 652 5237158+ 83 Linux

Disk /dev/sde: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sde1 1 261 2096451 83 Linux

Disk /dev/sdf: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdf1 1 1305 10482380+ 83 Linux

Disk /dev/sdg: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdg1 1 1024 1048560 83 Linux

Disk /dev/sdh: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdh1 1 1024 1048560 83 Linux

Disk /dev/sdi: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdi1 1 1024 1048560 83 Linux

Disk /dev/sdj: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdj1 1 1024 1048560 83 Linux

Disk /dev/sdk: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdk1 1 1305 10482381 83 Linux

Disk /dev/sdl: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdl1 1 1305 10482381 83 Linux

Disk /dev/sdm: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdm1 1 652 5237158+ 83 Linux

Disk /dev/sdn: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdn1 1 261 2096451 83 Linux

Disk /dev/sdo: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdo1 1 1305 10482381 83 Linux

Disk /dev/sdp: 1073 MB, 1073741824 bytes
64 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdp1 1 1024 1048560 83 Linux
[~] 05:57:03

Re: fdisk, SAN question

Steven E. Protter — Mon, 25 Dec 2006 03:52:40 GMT

Shalom,

Normally the boot disk is not mirrored, nor is it placed on a SAN. Its probably got a different device name.

Your SAN appears to have been divided into many small pieces, you added another one to that list. You may need to start over if the disk is not in use.

SEP

Re: fdisk, SAN question

Patrick Terlisten — Mon, 25 Dec 2006 05:41:14 GMT

Hello Brian,

you can check dmesg. There should be entries of the HBA and the devices which are attatched to it. Simply grep the output of dmesg for QLA or something else.

If you boot-disks would be mirrored with a software-raid, you should see md-devices, such as /dev/md0, /dev/md1 or something else.

AFAIK is the simpliest way to change the name of a device an UDEV rule. Correct me if I'm wrong. :)

Regards,
Patrick

Re: fdisk, SAN question

brian_31 — Mon, 25 Dec 2006 08:40:46 GMT

thanks.
1. i was wondering how the device name changed from /dev/sda to /dev/sdaq?

2. if the boot disk is not mirrored then what would be the best way to recover in case of lost boot disk?

3. when i create this new disk slice i get the foll error
# fdisk /dev/sdaq

The number of cylinders for this disk is set to 210019.
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/sdaq: 440.4 GB, 440442814464 bytes
128 heads, 32 sectors/track, 210019 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Device Boot Start End Blocks Id System
/dev/sdaq1 * 1 128 262128 83 Linux
/dev/sdaq2 129 12152 24625152 83 Linux
/dev/sdaq3 12153 16248 8388608 83 Linux
/dev/sdaq4 16249 210019 396843008 f Win95 Ext'd (LBA)
/dev/sdaq5 16249 19296 6242288 83 Linux
/dev/sdaq6 19297 21344 4194288 83 Linux
/dev/sdaq7 21345 22856 3096560 83 Linux
/dev/sdaq8 22857 23880 2097136 83 Linux
/dev/sdaq9 23881 24454 1175536 83 Linux
/dev/sdaq10 24455 25454 2047984 82 Linux swap
/dev/sdaq11 25455 75523 102541296 83 Linux

Command (m for help): n
First cylinder (75524-210019, default 75524):
Using default value 75524
Last cylinder or +size or +sizeM or +sizeK (75524-210019, default 210019): +1024M

Command (m for help): p

Disk /dev/sdaq: 440.4 GB, 440442814464 bytes
128 heads, 32 sectors/track, 210019 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes

Device Boot Start End Blocks Id System
/dev/sdaq1 * 1 128 262128 83 Linux
/dev/sdaq2 129 12152 24625152 83 Linux
/dev/sdaq3 12153 16248 8388608 83 Linux
/dev/sdaq4 16249 210019 396843008 f Win95 Ext'd (LBA)
/dev/sdaq5 16249 19296 6242288 83 Linux
/dev/sdaq6 19297 21344 4194288 83 Linux
/dev/sdaq7 21345 22856 3096560 83 Linux
/dev/sdaq8 22857 23880 2097136 83 Linux
/dev/sdaq9 23881 24454 1175536 83 Linux
/dev/sdaq10 24455 25454 2047984 82 Linux swap
/dev/sdaq11 25455 75523 102541296 83 Linux
/dev/sdaq12 75524 76012 1001456 83 Linux

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
[~] 15:00:35

thanks again

brian

Re: fdisk, SAN question

Patrick Terlisten — Tue, 26 Dec 2006 07:27:44 GMT

Hello Brian,

the best way is to build a RAID 1 with mdadm. This software-mirror is IMHO the best way to protect the system. If you have local dists attatched to a smart array, you can use the smart array. If you boot from a storage in a SAN, use mdadm to build a software-mirror.

The error when you start fdisk is not an error. It's only an information for you, that the disk has more than 1024 cylinder. Old bootloaders or some operating-systems have problems with boot-partitions or an os-kernel behind cylinder 1024. But today that is not a real problem.

Regards,
Patrick

Re: fdisk, SAN question

George Liu_4 — Tue, 26 Dec 2006 09:17:58 GMT

seems you have several disks on SAN. /dev/sdaq and /dev/sda are very likely two different disks, not the same one you thought. Disk /dev/sdaq: 440.4 GB is different with 100GB of /dev/sda.

Re: fdisk, SAN question

brian_31 — Tue, 26 Dec 2006 11:04:23 GMT

the /dev/sdaq had a different name when i created a new 11th slice. after the slice was created and rebooted the name changed.is that normal?

thanks

brian

Re: fdisk, SAN question

George Liu_4 — Tue, 26 Dec 2006 15:34:03 GMT

It is possible if the SCSI target order changed after the reboot. It is normal if you have hardware or kernel changed.

To prevent this problem propagated to file system, e.g., to mount a wrong partition, It is a good practice to label the partition to a meaning full label. You may use e2label to do that.