On 10/07/2009 04:50 AM, Dan Track wrote:
On Tue, Oct 6, 2009 at 4:40 PM, Phil Meyer<pmeyer@xxxxxxxxxxxxxxxx> wrote:
On 10/05/2009 09:58 AM, Dan Track wrote:
Hi,
I've just added a new hp array to my server and when looking in dmesg
I can see the following:
scsi0 : ioc0: LSISAS1068E B3, FwRev=01192100h, Ports=1, MaxQ=343, IRQ=185
Vendor: HP Model: MSA2012sa Rev: J300
Type: Enclosure ANSI SCSI revision: 05
ACPI: PCI Interrupt 0000:17:00.0[A] -> GSI 19 (level, low) -> IRQ 98
mptbase: ioc1: Initiating bringup
ioc1: LSISAS1068E B3: Capabilities={Initiator}
PCI: Setting latency timer of device 0000:17:00.0 to 64
scsi1 : ioc1: LSISAS1068E B3, FwRev=01192100h, Ports=1, MaxQ=343, IRQ=98
Vendor: HP Model: MSA2012sa Rev: J300
Type: Enclosure ANSI SCSI revision: 05
HP CISS Driver (v 3.6.20-RH2)
ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 18 (level, low) -> IRQ 185
cciss0:<0x3230> at PCI 0000:06:00.0 IRQ 130 using DAC
blocks= 143305920 block_size= 512
heads= 255, sectors= 32, cylinders= 17562
blocks= 143305920 block_size= 512
heads= 255, sectors= 32, cylinders= 17562
cciss/c0d0: p1 p2
libata version 3.00 loaded.
Initializing USB Mass Storage driver...
mount
/dev/mapper/VolGroup00-LogVolRoot on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/mapper/VolGroup00-LogVolVar on /var type ext3 (rw)
/dev/mapper/VolGroup00-LogVolTmp on /tmp type ext3 (rw)
/dev/mapper/VolGroup00-LogVolUsr on /usr type ext3 (rw)
/dev/cciss/c0d0p1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
My question is how can I tell where the partition on the array is
mapped to on my server?
Thanks in advance.
Dan
When you get things right, you should be able to:
$ cat /proc/partitions
and see the new device there.
Most arrays will be seen as soon as configured, no reboot needed.
Hi Phil,
Many thanks for that pointer. I checked it after mapping the volume to
the LUN but it still didn't pop up after watching /proc/partitions for
a minute, how long does it take to pop up in there, is there a daemon
that is monitoring new additions/changes and then makes the changes?
FYI After reboot I can see the array.
Thanks
Dan
It is driver specific. Many arrays use the standard scsi driver which
will see them immediately. ISCSI or Fiber Channel arrays may have
additional drivers that need to be loaded.
It just depends. But in almost all cases it is possible to get things
set up and see the new drives without a reboot.
In your case it might have been a driver that needed loading or perhaps
it needed to be unloaded and loaded again.
For instance, if it were a fiber attached array, and if this were the
first LUN assigned to you, and it got botched while the driver was
active, and then fixed, you might have been able to:
# rmmod qla4xxx
# modprobe qla4xxx
Again, it is driver specific, and some drivers will not unload like that.
A reboot is 'easier', but on large platforms where other services are
critical it is important the the admin know how to do things like this.
Good luck!
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
