RHEL4 LUN problem - multipathing, but only 1 device
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
RHEL4 LUN problem - multipathing, but only 1 device
Ok, so I've got an older RHEL4 system (2.6.9-34.ELsmp) which I am needing to migrate off of one LUN and onto another. My plan was to simply have the storage team assign me a new LUN and to setup LVM mirroring then remove the origional LUN. My problem is with the new LUN. I had to reboot to get the system to even see it. It now shows up in /proc/scsi/scsi but there is only one new device in /dev and I cannot even open the sd* device.. I can only open the dm-* device.
What is confusing me is the /dev/sd* devices.
/dev/sda* is local disk
/dev/sdb & /dev/sdd is the multipath copy of the local disk
/dev/sdc & /dev/sde is the origional LUN over both paths
/dev/sdf should be the new disk, but cannot be opened:
bash-3.00# fdisk /dev/sdf
Unable to open /dev/sdf
I can open /dev/dm-9:
Quote:
bash-3.00# fdisk /dev/dm-9
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.
The number of cylinders for this disk is set to 39941.
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)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): p
Disk /dev/dm-9: 328.5 GB, 328531443712 bytes
255 heads, 63 sectors/track, 39941 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
I'll get that for you tomorrow (yay Thanksgiving!)
The /proc/scsi/scsi file shows 6 devices though.. 2 Lun0 on scsi0 & scsi3 = onboard drive, Lun1 on scsi1 & scsi2 = origional SAN drive, Lun2 on scsi1 & scsi2 = new SAN drive.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.