8 Krypton

loosing the persistency of mount point in suse linux

I just got a new additional lun from CX..

powermt display dev=all looks good. so;
I run powermt config, powermt save.. and did the formatting and mounting stuff.. All went fine
I edit my /etc/fstab just to make sure it is persistent..

However after I reboot and run again df -ah, the mount point is gone. I double checked my /fstab and it is there..


What could it be?
Labels (1)
0 Kudos
15 Replies
8 Krypton

Re: 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.
0 Kudos
8 Krypton

Re: loosing the persistency of mount point in suse linux

hi:

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

any other clue?

thanks.
0 Kudos
8 Krypton

Re: loosing the persistency of mount point in suse linux

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

Re: loosing the persistency of mount point in suse linux

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

mounting manually is fine. but once rebooted it is gone again.
0 Kudos
8 Krypton

Re: loosing the persistency of mount point in suse linux

can you post content of /etc/fstab
0 Kudos
8 Krypton

Re: loosing the persistency of mount point in suse linux

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
0 Kudos
8 Krypton

Re: loosing the persistency of mount point in suse linux

found might could be cause of the problem..

when i run powermt display dev=all.. after another reboot
I found out I'm missing the clarion ID [server name] and the logical device [lun11]

what I did run again the powermt config and then run powermt save..
when I run the powermt display dev=all this time.. it looks good, I can see my server name and the LUN11.. however after the reboot the information is missing again the server name and logical device [lun 11].
0 Kudos
8 Krypton

Re: loosing the persistency of mount point in suse linux

anything suspicious in /var/log/messages ?
0 Kudos
8 Krypton

Re: loosing the persistency of mount point in suse linux

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:~ #
0 Kudos