loosing the persistency of mount point in suse linux

what did you use in fstab ..native /dev/sd* device or powerpath device ? You need to use powerpath device as that will not change at reboot time.

hi:

I used the powerpath device... /dev/emcpowerc...

any other clue?

thanks.

subject mount point is /dev/emcpowera /myfs1


/dev/cciss/c0d0p1 / ext3 acl,user_xattr 1 1
/dev/cciss/c0d0p2 /boot ext3 acl,user_xattr 1 2
/dev/cciss/c0d0p4 /local ext3 acl,user_xattr 1 2
/dev/cciss/c0d0p3 swap swap pri=42 0 0
/dev/emcpowera /myfs1 ext3 defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0

yes, the powermt display dev=all stay same..

mounting manually is fine. but once rebooted it is gone again.

but after reboot powerpath device name stayed the same ..and you can mount it manually ok ?

can you post content of /etc/fstab

anything suspicious in /var/log/messages ?

Go this specific to emcpowera..
It is confirmed, I'm lossing the powerpath config settings specific to LUN name and server name whenever I did reboot..



Jan 6 21:03:36 myfs-01 /etc/hotplug/block.agent[14779]: try 1 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:37 myfs-01 kernel: emcpowera: unknown partition table
Jan 6 21:03:37 myfs-01 /etc/hotplug/block.agent[14779]: try 2 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:39 myfs-01 /etc/hotplug/block.agent[14779]: try 3 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:40 myfs-01 /etc/hotplug/block.agent[14779]: try 4 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:41 myfs-01 /etc/hotplug/block.agent[14779]: try 5 while waiting for /block/emcpowera's bus_id
Jan 6 21:03:42 myfs-01 /etc/hotplug/block.agent[14779]: new block device /block/emcpowera
Jan 6 21:17:50 myfs-01 kernel: emcpowera: unknown partition table
Jan 6 21:17:50 myfs-01 /etc/hotplug/block.agent[15414]: try 1 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:51 myfs-01 /etc/hotplug/block.agent[15414]: try 2 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:52 myfs-01 /etc/hotplug/block.agent[15414]: try 3 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:53 myfs-01 /etc/hotplug/block.agent[15414]: try 4 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:54 myfs-01 /etc/hotplug/block.agent[15414]: try 5 while waiting for /block/emcpowera's bus_id
Jan 6 21:17:55 myfs-01 /etc/hotplug/block.agent[15414]: new block device /block/emcpowera
Jan 6 22:12:14 myfs-01 kernel: emcpowera: unknown partition table
Jan 6 22:12:14 myfs-01 /etc/hotplug/block.agent[14125]: try 1 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:15 myfs-01 /etc/hotplug/block.agent[14125]: try 2 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:16 myfs-01 /etc/hotplug/block.agent[14125]: try 3 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:17 myfs-01 /etc/hotplug/block.agent[14125]: try 4 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:18 myfs-01 /etc/hotplug/block.agent[14125]: try 5 while waiting for /block/emcpowera's bus_id
Jan 6 22:12:19 myfs-01 /etc/hotplug/block.agent[14125]: new block device /block/emcpowera
myfs-01:~ #

run this for me please ..and post output:

fdisk -l /dev/emcpowera

I got this..!

fdisk -l /dev/emcpowera

Disk /dev/emcpowera: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/emcpowera doesn't contain a valid partition table

did you create a partition when you first got the lun. Typically you would use fdisk to create a partiton, in your case you would run fdisk /dev/emcpowera ...once you create a primary partition ..at that point ouput from fdislk -l should show partition emcpowera1. After that you would create your file system.

i don't think you can rename it ....you can rename powerpath device ..but not the partition itself. How did you do it on your other servers ?

I skipped that fdisk..since I thought dont need to do fdisk sicne my entire LUN will be dedicated for one volume..

My question is if I do fdisk -l after the fdisk config.. can I just rename the emcpowera1 to emcpowera..before making the file system.. need to maintain our standard naming..

thanks

Hi Chikka,

Could you please share what was the solution for this issue? if you get any?