<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.6944.0"> <TITLE>Question about /etc/raidtab and using SAN Disk</TITLE> </HEAD> <BODY>  Hello, i have a question about md device and /etc/raidtab with san storage. sorry for this intro! my system has no local disk, only san storage and i have 2 qlogic fc adapter. to build a redundant systemdisk (/boot,swap,/ and lvm partition) i have definition over fc adapter1 one san disk and over fs adapter2 one (other) san disk. i can to this setup over kickstart an it looks good. all md devices are createt over san disk on sda and sdb. ###kickstart snip #Disk partitioning information part raid.15 --size 100 --ondisk sda part raid.20 --size 2000 --ondisk sda part raid.19 --size 2000 --ondisk sda part raid.21 --size 100 --grow --ondisk sda part raid.26 --size 100 --ondisk sdb part raid.24 --size 2000 --ondisk sdb part raid.23 --size 2000 --ondisk sdb part raid.25 --size 100 --grow --ondisk sdb raid /boot --level=1 --device=md0 --fstype ext3 raid.15 raid.26 raid swap --level=1 --device=md1 --fstype swap raid.20 raid.24 raid / --level=1 --device=md2 --fstype ext3 raid.19 raid.23 raid pv.38 --level=1 --device=md3 raid.21 raid.25 volgroup rhvg pv.38 logvol /opt --fstype ext3 --name=optlv --vgname=rhvg --size=500 logvol /home --fstype ext3 --name=homelv --vgname=rhvg --size=1000 logvol /usr --fstype ext3 --name=usrlv --vgname=rhvg --size=2000 logvol /var --fstype ext3 --name=varlv --vgname=rhvg --size=500 --kickstart snap ### for booting i have grub, i don't now at the moment, has grub support for raid1 installation ? for next task's (data or application oder db's) i need now more san disk to build other vg's. if i reboot the system to see a new san disk, i have a diff like: befor installation: fcs1 -> disk1 -> /dev/sda fcs2 -> disk2 -> /dev/sdb --> raid1 over disk1/disk2 (system md) after installation, adding 1 new disk open over 2 fc adapters: fcs1 -> disk1 -> /dev/sda (system md) -> disk3/path1 -> /dev/sdb fcs2 -> disk2 -> /dev/sdc (system md) -> disk3/path2 -> /dev/sdd it moves my sdb disk to sdc, becose sdb is now the new san disk and i can see the same disk over fc adapter2 as sdd. this looks ok for me. the system has no problem to boot an the md looks good and knows about /dev/sdc: ### /dev/md0: Version : 00.90.00 Creation Time : Thu Apr 29 18:07:15 2004 Raid Level : raid1 Array Size : 102272 (99.88 MiB 104.73 MB) Device Size : 102272 (99.88 MiB 104.73 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Thu Apr 29 18:35:44 2004 State : dirty, no-errors Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 33 1 active sync /dev/sdc1 UUID : 16af8897:23ed83ef:48831df1:45be2c5d ### becose inside /etc/raidtab, there are definitions about sda and sdb: mdadm -D /dev/md0 raiddev /dev/md0 raid-level 1 nr-raid-disks 2 chunk-size 64k persistent-superblock 1 nr-spare-disks 0 device /dev/sda1 raid-disk 0 device /dev/sdb1 raid-disk 1 cat /proc/partitions: major minor #blocks name rio rmerge rsect ruse wio wmerge wsect wuse running use aveq 58 0 1024000 lvma 0 0 0 0 0 0 0 0 0 0 0 58 1 512000 lvmb 0 0 0 0 0 0 0 0 0 0 0 58 2 2048000 lvmc 0 0 0 0 0 0 0 0 0 0 0 58 3 512000 lvmd 0 0 0 0 0 0 0 0 0 0 0 8 0 14423040 sda 16826 918 82906 66870 8194 4522 52986 34680 0 21730 101530 8 1 104391 sda1 51 0 108 1010 20 0 46 100 0 290 1110 8 2 2048287 sda2 1982 0 15754 9950 1905 502 19296 9190 0 5600 19140 8 3 2048287 sda3 29 0 64 250 1 0 8 0 0 30 250 8 4 1 sda4 16 0 32 20 0 0 0 0 0 20 20 8 5 10217308 sda5 12508 918 62468 53270 6268 4020 33636 25390 0 16080 78650 8 16 7211520 sdb 32 0 64 340 0 0 0 0 0 90 340 8 32 14423040 sdc 15603 2461 80558 65130 8529 4190 52986 33120 0 19750 98250 8 33 102384 sdc1 43 0 92 130 20 0 46 100 0 120 230 8 34 2048000 sdc2 2220 0 17736 12810 1815 596 19296 6050 0 5250 18870 8 35 2048000 sdc3 15 0 48 110 1 0 8 0 0 20 110 8 36 1 sdc4 15 0 30 0 0 0 0 0 0 0 0 8 37 10224624 sdc5 11055 2440 58100 49560 6693 3594 33636 26970 0 14390 76530 8 48 7211520 sdd 32 0 64 40 0 0 0 0 0 10 40 8 64 1048575 sde 48 0 96 0 0 0 0 0 0 0 0 9 0 102272 md0 0 0 0 0 0 0 0 0 0 0 0 9 1 2047936 md1 0 0 0 0 0 0 0 0 0 0 0 9 2 2047936 md2 0 0 0 0 0 0 0 0 0 0 0 9 3 10217216 md3 0 0 0 0 0 0 0 0 0 0 0 are there now any problems, if i have inside /etc/raidtab definitions with /dev/sdb and the md device is now over /dev/sdc ? regards, thomas and there is a dmesg output from boot: md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Initializing Cryptographic API NET4: Linux TCP/IP 1.0 for NET4.0 IP: routing cache hash table of 16384 buckets, 128Kbytes TCP: Hash tables configured (established 524288 bind 65536) Linux IP multicast router 0.06 plus PIM-SM Initializing IPsec netlink socket NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 399k freed VFS: Mounted root (ext2 filesystem). SCSI subsystem driver Revision: 1.00 qla2x00_set_info starts at address = f8834060 qla2x00: Found VID=1077 DID=2312 SSVID=1014 SSDID=27d scsi(0): Found a QLA2312 @ bus 2, device 0x2, irq 18, iobase 0xf887c000 scsi(0): Allocated 4096 SRB(s). scsi(0): Configure NVRAM parameters... scsi(0): 64 Bit PCI Addressing Enabled. scsi(0): Scatter/Gather entries= 3584 qla2x00_nvram_config ZIO enabled:intr_timer_delay=3 scsi(0): Verifying loaded RISC code... scsi(0): Verifying chip... scsi(0): Waiting for LIP to complete... scsi(0): LOOP UP detected. scsi(0): Port database changed. scsi(0) qla2x00_isr MBA_PORT_UPDATE ignored scsi(0): Topology - (F_Port), Host Loop address 0xffff qla2x00: Found VID=1077 DID=2312 SSVID=1014 SSDID=27d scsi(1): Found a QLA2312 @ bus 2, device 0x2, irq 19, iobase 0xf887e000 scsi(1): Allocated 4096 SRB(s). scsi(1): Configure NVRAM parameters... scsi(1): 64 Bit PCI Addressing Enabled. scsi(1): Scatter/Gather entries= 3584 qla2x00_nvram_config ZIO enabled:intr_timer_delay=3 scsi(1): Verifying loaded RISC code... scsi(1): Verifying chip... scsi(1): Waiting for LIP to complete... scsi(1): LOOP UP detected. scsi(1): Port database changed. scsi(1) qla2x00_isr MBA_PORT_UPDATE ignored scsi(1): Topology - (F_Port), Host Loop address 0xffff scsi0 : QLogic QLA2312 PCI to Fibre Channel Host Adapter: bus 2 device 2 irq 18 Firmware version: 3.02.13, Driver version 6.06.00b11 scsi1 : QLogic QLA2312 PCI to Fibre Channel Host Adapter: bus 2 device 2 irq 19 Firmware version: 3.02.13, Driver version 6.06.00b11 initializing plug timer for queue f72eae18 Starting timer : 1 1 blk: queue f72eae18, I/O limit 4294967295Mb (mask 0xffffffffffffffff) Vendor: HITACHI Model: OPEN-9 Rev: 2101 Type: Direct-Access ANSI SCSI revision: 02 initializing plug timer for queue f72eac18 Starting timer : 1 1 blk: queue f72eac18, I/O limit 4294967295Mb (mask 0xffffffffffffffff) Vendor: HITACHI Model: OPEN-9 Rev: 2101 Type: Direct-Access ANSI SCSI revision: 02 initializing plug timer for queue f72eaa18 Starting timer : 1 1 blk: queue f72eaa18, I/O limit 4294967295Mb (mask 0xffffffffffffffff) scsi(0:0:0:0): Enabled tagged queuing, queue depth 255. scsi(0:0:0:1): Enabled tagged queuing, queue depth 255. initializing plug timer for queue f72eaa18 Starting timer : 1 1 Vendor: HITACHI Model: OPEN-9 Rev: 2101 Type: Direct-Access ANSI SCSI revision: 02 initializing plug timer for queue f72ea818 Starting timer : 1 1 blk: queue f72ea818, I/O limit 4294967295Mb (mask 0xffffffffffffffff) Vendor: HITACHI Model: OPEN-9 Rev: 2101 Type: Direct-Access ANSI SCSI revision: 02 initializing plug timer for queue f7257e18 Starting timer : 1 1 blk: queue f7257e18, I/O limit 4294967295Mb (mask 0xffffffffffffffff) scsi(1:0:0:0): Enabled tagged queuing, queue depth 255. scsi(1:0:0:1): Enabled tagged queuing, queue depth 255. Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 0, lun 1 Attached scsi disk sdc at scsi1, channel 0, id 0, lun 0 Attached scsi disk sdd at scsi1, channel 0, id 0, lun 1 scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=40320, scaling scsi::resize_dma_pool: WARNING, dma_sectors=0, wanted=30240, scaling SCSI device sda: 28846080 512-byte hdwr sectors (14769 MB) Partition check: sda: sda1 sda2 sda3 sda4 < sda5 > SCSI device sdb: 14423040 512-byte hdwr sectors (7385 MB) sdb: SCSI device sdc: 28846080 512-byte hdwr sectors (14769 MB) sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 > SCSI device sdd: 14423040 512-byte hdwr sectors (7385 MB) sdd: LVM version 1.0.5+(22/07/2002) module loaded md: raid1 personality registered as nr 3 Journalled Block Device driver loaded md: Autodetecting RAID arrays. [events: 00000004] [events: 00000004] [events: 00000004] [events: 00000004] [events: 00000004] [events: 00000004] [events: 00000004] [events: 00000004] md: autorun ... md: considering sdc5 ... md: adding sdc5 ... md: adding sda5 ... md: created md3 md: bind<sda5,1> md: bind<sdc5,2> md: running: <sdc5><sda5> md: sdc5's event counter: 00000004 md: sda5's event counter: 00000004 md: device name has changed from sdb5 to sdc5 since last import! md: RAID level 1 does not need chunksize! Continuing anyway. md3: max total readahead window set to 124k md3: 1 data-disks, max readahead per data-disk: 124k raid1: device sdc5 operational as mirror 1 raid1: device sda5 operational as mirror 0 raid1: raid set md3 active with 2 out of 2 mirrors md: considering sdc3 ... md: adding sdc3 ... md: adding sda3 ... md: created md1 md: bind<sda3,1> md: bind<sdc3,2> md: running: <sdc3><sda3> md: sdc3's event counter: 00000004 md: sda3's event counter: 00000004 md: device name has changed from sdb3 to sdc3 since last import! md: RAID level 1 does not need chunksize! Continuing anyway. md1: max total readahead window set to 124k md1: 1 data-disks, max readahead per data-disk: 124k raid1: device sdc3 operational as mirror 1 raid1: device sda3 operational as mirror 0 raid1: raid set md1 active with 2 out of 2 mirrors md: considering sdc2 ... md: adding sdc2 ... md: adding sda2 ... md: created md2 md: bind<sda2,1> md: bind<sdc2,2> md: running: <sdc2><sda2> md: sdc2's event counter: 00000004 md: sda2's event counter: 00000004 md: device name has changed from sdb2 to sdc2 since last import! md: RAID level 1 does not need chunksize! Continuing anyway. md2: max total readahead window set to 124k md2: 1 data-disks, max readahead per data-disk: 124k raid1: device sdc2 operational as mirror 1 raid1: device sda2 operational as mirror 0 raid1: raid set md2 active with 2 out of 2 mirrors md: considering sdc1 ... md: adding sdc1 ... md: adding sda1 ... md: created md0 md: bind<sda1,1> md: bind<sdc1,2> md: running: <sdc1><sda1> md: sdc1's event counter: 00000004 md: sda1's event counter: 00000004 md: device name has changed from sdb1 to sdc1 since last import! md: RAID level 1 does not need chunksize! Continuing anyway. md0: max total readahead window set to 124k md0: 1 data-disks, max readahead per data-disk: 124k raid1: device sdc1 operational as mirror 1 raid1: device sda1 operational as mirror 0 raid1: raid set md0 active with 2 out of 2 mirrors md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Freeing unused kernel memory: 224k freed usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-ohci.c: USB OHCI at membase 0xf88e6000, IRQ 7 usb-ohci.c: usb-00:0f.2, ServerWorks CSB6 OHCI USB Controller usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 4 ports detected usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz> hid-core.c: USB HID support drivers mice: PS/2 mouse device common for all mice EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,2), internal journal loop: loaded (max 8 devices) hub.c: new USB device 00:0f.2-1, assigned address 2 usb.c: config descriptor too short (expected 25, got 9) usb.c: unable to get device 2 configuration (error=-22) Adding Swap: 2047928k swap-space (priority -1) hub.c: new USB device 00:0f.2-1, assigned address 3 hub.c: USB hub found hub.c: 4 ports detected hub.c: new USB device 00:0f.2-2, assigned address 4 hub.c: USB hub found hub.c: 4 ports detected kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,0), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on lvm(58,0), internal journal EXT3-fs: mounted filesystem with ordered data mode. hub.c: new USB device 00:0f.2-2.1, assigned address 5 kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on lvm(58,1), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on lvm(58,2), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on lvm(58,3), internal journal EXT3-fs: mounted filesystem with ordered data mode. </BODY> </HTML>