Fwd: [Next problem with multipath-tools]

Fwd: [Next problem with multipath-tools]

[Patrick Caulfield]

[-- Attachment #1: Type: text/plain, Size: 15 bytes --]

 
-- 

patrick

[-- Attachment #2: Type: message/rfc822, Size: 4098 bytes --]

From: <Marek.Uher@t-mobile.cz>
To: <patrick@debian.org>
Subject: Next problem with multipath-tools
Date: Mon, 14 Feb 2005 15:47:01 +0100
Message-ID: <D18A13F01D850B409793C6C3FA5E0389012EEF24@SRVRE02.rdm.cz>


	Hello Patrick,

I installed the new version of libsysfs1 which fixed problem in location of 
libsysfs in /lib (instead in /usr/lib). But I think that this bug fix didn't
solve problem with multipath-tools. After reboot multipathd is able to start
correctly when server is coming up. Unfortunately if /var is located on
separate volume and is mounted at startup sequence after multipathd start, the
new mounted file system will overlay directory structure (located in /var -
i.e. /var/run and /var/cache/multipathd) for multipathd and daemon will stay
nonfunctional. Multipathd is running but do nothing from this moment. It is
necessary to restart multipathd after mounting of /var file system. I have no
idea how to solve this problem (maybe it is necessary to modify multipathd to
store information elsewhere than in /var - i.e. somewhere on root partition or
in ram disk).

Regards,

Marek
 --
Ing. Marek Uher
Linux System Specialist
Technology Division
T-Mobile Czech Republic a.s.
Tomickova 2144/1
149 00 Praha 4
Czech Republic
Mobile:	(+420) 603 400 728
Office:	(+420) 603 607 128
Fax:		(+420) 603 600 796
E-mail:	marek.uher@t-mobile.cz
Web:		http://www.t-mobile.cz/
 


---------- Disclaimer ----------
K tomuto e-mailu je připojeno prohlášení, jehož plné znění je dostupné na adrese http://www.t-mobile.cz/disclaimer
A disclaimer is attached to this e-mail, the full version of which is available at http://www.t-mobile.cz/disclaimer



[-- Attachment #3: Type: text/plain, Size: 93 bytes --]

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: Fwd: [Next problem with multipath-tools]

[Christophe Varoqui]

Patrick,

remember me why you can't start the daemon later in the boot process ?
Last time when talked about that I guess we concluded the startup 
position didn't really care ...

Anyway, if you maintain the need, several solution might be evaluated :
o a cmdline flag to disable pidfile creation, for those distro that 
manage that in the init script
o a different default pidfile location, or a flag to point to a custom 
location
o rip the pidfile logic altogether and go for a pidof() thing in the tool

Concerning /var/cache/multipathd, I guess the overlay doesn't matter as 
the CLONE_NEWNS flag should protect our namespace.

Please comment on your prefered ways.

Regards,
cvaroqui

>
>	Hello Patrick,
>
>I installed the new version of libsysfs1 which fixed problem in location of 
>libsysfs in /lib (instead in /usr/lib). But I think that this bug fix didn't
>solve problem with multipath-tools. After reboot multipathd is able to start
>correctly when server is coming up. Unfortunately if /var is located on
>separate volume and is mounted at startup sequence after multipathd start, the
>new mounted file system will overlay directory structure (located in /var -
>i.e. /var/run and /var/cache/multipathd) for multipathd and daemon will stay
>nonfunctional. Multipathd is running but do nothing from this moment. It is
>necessary to restart multipathd after mounting of /var file system. I have no
>idea how to solve this problem (maybe it is necessary to modify multipathd to
>store information elsewhere than in /var - i.e. somewhere on root partition or
>in ram disk).
>  
>
>


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel