search for: mpath0p1

...an not be manipulated, filesystem wise, without requiring a reboot. I am using the inbuilt software ISCSI initiator and multipathing in CentOS 5.1. My steps so far. Create 10GB volume on SAN # iscsiadm -m session -R # fdisk /dev/mapper/mpath0 # kpartx -a /dev/mapper/mpath0 # mke2fs -j /dev/mapper/mpath0p1 # mount /dev/mapper/mpath0p1 /test-mount <--works fine to here--> Now I want to extend the volume on the SAN to 15GB run fdisk and use resize2fs to extend the filesystem, is this possible without a reboot? Currently, I don't seem to be able to get fdisk to see the new disk size after ext...

...ading to the latest CentOS kernel from kernel-2.6.18-164.11.1.el5 to kernel-2.6.18-164.15.1.el5 on an IBM HS21 blade with SAN boot. Upgrade went fine, but after rebooting the system was unable to find /boot even though it was mounted. The reboot displayed an error with fsck.ext3 that /dev/mapper/mpath0p1 was not found, which was the /boot volume. I reverted to the old kernel and it booted fine. At first I tried rebuilding the initrd to include the multipath modules, but this had no effect. I ended up just re-labeling all the ext3 filesystems and the changing the /boot line in fstab from the /dev/...

...mounting by label and also by explicit /dev/mapper/mpathXpY name with the same unpredictable behavior. I've also noticed that sometimes when a device is successfully mounted on all nodes, each node may return different output from the mount command regarding the device mounted; e.g. /dev/mapper/mpath0p1 vs. /dev/dm-17. One consistent aspect I have noticed whenever I receive the "device busy" error is that the /dev/dm-X names don't match up on each node. I also see that ocfs2console refers to each device by the /dev/dm-X name instead of the /dev/mapper/XX name. I guess my question i...

...attempted to try this... # cat /etc/udev/permissions.d/50-udev.permissions | grep mapper mapper/mpath*:oracle:dba:0660 But it did not seem to work... # ls -l /dev/mapper/mpath* brw-rw---- 1 root disk 253, 2 Feb 26 20:56 /dev/mapper/mpath0 brw-rw---- 1 root disk 253, 5 Feb 26 20:56 /dev/mapper/mpath0p1 brw-rw---- 1 root disk 253, 3 Feb 26 20:56 /dev/mapper/mpath1 brw-rw---- 1 root disk 253, 4 Feb 26 20:56 /dev/mapper/mpath1p1 Am I doing something wrong? Is there another way to do this? Thanks, Scott