Mailing List Archive: [linux-ha-dev] Why CIFS Filesystem resouce doesn't support clone, but smbfs support ?

[linux-ha-dev] Why CIFS Filesystem resouce doesn't support clone, but smbfs support ?

Dec 23, 2011, 1:08 AM

Post #1 of 3 (1074 views)

Hi,

I want to mount CIFS storage on every node of pacemaker cluster, so I use
clone like following:

<clone id="cifs-clone">

<meta_attributes id="cifs-clone-meta_attributes">

<nvpair id="cifs-clone-meta_attributes-target-role"
name="target-role" value="Started"/>

</meta_attributes>

<primitive class="ocf" id="Mount_cifs" provider="heartbeat"
type="Filesystem">

<instance_attributes id="Mount_cifs-instance_attributes">

<nvpair id="Mount_cifs-instance_attributes-device" name="device"
value="//192.168.1.40/xxxx"/>

<nvpair id="Mount_cifs-instance_attributes-directory"
name="directory" value="/mnt/cifs"/>

<nvpair id="Mount_cifs-instance_attributes-fstype" name="fstype"
value="cifs"/>

<nvpair id="Mount_cifs-instance_attributes-options" name="options"
value="username=admin,password=xxxx,rw"/>

</instance_attributes>

</primitive>

</clone>

However when I start cifs-clone, some error occurred, start failed,
following is the log.

Dec 21 18:50:24 h10_150 Filesystem[2935]: INFO: Running start for
192.168.1.40:/mnt/test/nfs/xxxx on /mnt/nfs Dec 21 18:50:24 h10_150
Filesystem[2935]: ERROR: DANGER! cifs on 192.168.1.40:/mnt/test/nfs/xxxx is
NOT cluster-aware!

Dec 21 18:50:24 h10_150 Filesystem[2935]: ERROR: DO NOT RUN IT AS A CLONE!

Dec 21 18:50:24 h10_150 Filesystem[2935]: ERROR: Politely refusing to
proceed to avoid data corruption.

Dec 21 18:50:24 h10_150 crmd: [2083]: info: process_lrm_event: LRM operation

Mount_cifs:0_start_0 (call=13, rc=6, cib-update=103, confirmed=true) not
configured

So I read the Filesystem script code, find following code before start
resource.

case $FSTYPE in

ocfs2) ocfs2_init

;;

nfs|smbfs|none|gfs2) : # this is kind of safe too

;;

*) if [ -n "$OCF_RESKEY_CRM_meta_clone" ]; then

ocf_log err "$OCF_RESKEY_CRM_meta_clone"

ocf_log err "DANGER! $FSTYPE on $DEVICE is NOT
cluster-aware!"

ocf_log err "DO NOT RUN IT AS A CLONE!"

ocf_log err "Politely refusing to proceed to avoid data
corruption."

exit $OCF_ERR_CONFIGURED

fi

;;

Esac

I want to know why CIFS isn't the kind of safe FSTYPE, but smbfs is
considered safe ? They are not the same as it ?

PS:

I could start CIFS resource directly instead of clone.

Best Regards,

Qiu Zhigang

Re: [linux-ha-dev] Why CIFS Filesystem resouce doesn't support clone, but smbfs support ? [ In reply to ]

lars.ellenberg at linbit

Dec 28, 2011, 3:15 PM

Post #2 of 3 (1045 views)

Permalink

On Fri, Dec 23, 2011 at 05:08:18PM +0800, Qiu Zhigang wrote:
> Hi,
>
>
>
> I want to mount CIFS storage on every node of pacemaker cluster, so I use
> clone like following:
>
>
>
> <clone id="cifs-clone">
>
> <meta_attributes id="cifs-clone-meta_attributes">
>
> <nvpair id="cifs-clone-meta_attributes-target-role"
> name="target-role" value="Started"/>
>
> </meta_attributes>
>
> <primitive class="ocf" id="Mount_cifs" provider="heartbeat"
> type="Filesystem">
>
> <instance_attributes id="Mount_cifs-instance_attributes">
>
> <nvpair id="Mount_cifs-instance_attributes-device" name="device"
> value="//192.168.1.40/xxxx"/>
>
> <nvpair id="Mount_cifs-instance_attributes-directory"
> name="directory" value="/mnt/cifs"/>
>
> <nvpair id="Mount_cifs-instance_attributes-fstype" name="fstype"
> value="cifs"/>
>
> <nvpair id="Mount_cifs-instance_attributes-options" name="options"
> value="username=admin,password=xxxx,rw"/>
>
> </instance_attributes>
>
> </primitive>
>
> </clone>
>
>
>
> However when I start cifs-clone, some error occurred, start failed,
> following is the log.
>
>
>
> Dec 21 18:50:24 h10_150 Filesystem[2935]: INFO: Running start for
> 192.168.1.40:/mnt/test/nfs/xxxx on /mnt/nfs Dec 21 18:50:24 h10_150
> Filesystem[2935]: ERROR: DANGER! cifs on 192.168.1.40:/mnt/test/nfs/xxxx is
> NOT cluster-aware!
>
> Dec 21 18:50:24 h10_150 Filesystem[2935]: ERROR: DO NOT RUN IT AS A CLONE!
>
> Dec 21 18:50:24 h10_150 Filesystem[2935]: ERROR: Politely refusing to
> proceed to avoid data corruption.
>
> Dec 21 18:50:24 h10_150 crmd: [2083]: info: process_lrm_event: LRM operation
>
> Mount_cifs:0_start_0 (call=13, rc=6, cib-update=103, confirmed=true) not
> configured
>
>
>
> So I read the Filesystem script code, find following code before start
> resource.
>
>
>
> case $FSTYPE in
>
> ocfs2) ocfs2_init
>
> ;;
>
> nfs|smbfs|none|gfs2) : # this is kind of safe too

right. so just add cifs in there, ok?
and send a patch ...

current upstream is here:
https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/Filesystem

>
> ;;
>
> *) if [ -n "$OCF_RESKEY_CRM_meta_clone" ]; then
>
> ocf_log err "$OCF_RESKEY_CRM_meta_clone"
>
> ocf_log err "DANGER! $FSTYPE on $DEVICE is NOT
> cluster-aware!"
>
> ocf_log err "DO NOT RUN IT AS A CLONE!"
>
> ocf_log err "Politely refusing to proceed to avoid data
> corruption."
>
> exit $OCF_ERR_CONFIGURED
>
> fi
>
> ;;
>
> Esac
>
>
>
> I want to know why CIFS isn't the kind of safe FSTYPE, but smbfs is
> considered safe ? They are not the same as it ?
>
>
>
> PS:
>
>
>
> I could start CIFS resource directly instead of clone.
>
>
>
>
>
> Best Regards,
>
> Qiu Zhigang
>
>
>
>
>

> _______________________________________________________
> Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/

--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Re: [linux-ha-dev] Why CIFS Filesystem resouce doesn't support clone, but smbfs support ? [ In reply to ]

dejan at suse

Jan 9, 2012, 11:53 AM

Post #3 of 3 (1029 views)

Permalink

Hi,

On Thu, Dec 29, 2011 at 12:15:38AM +0100, Lars Ellenberg wrote:
> On Fri, Dec 23, 2011 at 05:08:18PM +0800, Qiu Zhigang wrote:
> > Hi,
> >
> >
> >
> > I want to mount CIFS storage on every node of pacemaker cluster, so I use
> > clone like following:
> >
> >
> >
> > <clone id="cifs-clone">
> >
> > <meta_attributes id="cifs-clone-meta_attributes">
> >
> > <nvpair id="cifs-clone-meta_attributes-target-role"
> > name="target-role" value="Started"/>
> >
> > </meta_attributes>
> >
> > <primitive class="ocf" id="Mount_cifs" provider="heartbeat"
> > type="Filesystem">
> >
> > <instance_attributes id="Mount_cifs-instance_attributes">
> >
> > <nvpair id="Mount_cifs-instance_attributes-device" name="device"
> > value="//192.168.1.40/xxxx"/>
> >
> > <nvpair id="Mount_cifs-instance_attributes-directory"
> > name="directory" value="/mnt/cifs"/>
> >
> > <nvpair id="Mount_cifs-instance_attributes-fstype" name="fstype"
> > value="cifs"/>
> >
> > <nvpair id="Mount_cifs-instance_attributes-options" name="options"
> > value="username=admin,password=xxxx,rw"/>
> >
> > </instance_attributes>
> >
> > </primitive>
> >
> > </clone>
> >
> >
> >
> > However when I start cifs-clone, some error occurred, start failed,
> > following is the log.
> >
> >
> >
> > Dec 21 18:50:24 h10_150 Filesystem[2935]: INFO: Running start for
> > 192.168.1.40:/mnt/test/nfs/xxxx on /mnt/nfs Dec 21 18:50:24 h10_150
> > Filesystem[2935]: ERROR: DANGER! cifs on 192.168.1.40:/mnt/test/nfs/xxxx is
> > NOT cluster-aware!
> >
> > Dec 21 18:50:24 h10_150 Filesystem[2935]: ERROR: DO NOT RUN IT AS A CLONE!
> >
> > Dec 21 18:50:24 h10_150 Filesystem[2935]: ERROR: Politely refusing to
> > proceed to avoid data corruption.
> >
> > Dec 21 18:50:24 h10_150 crmd: [2083]: info: process_lrm_event: LRM operation
> >
> > Mount_cifs:0_start_0 (call=13, rc=6, cib-update=103, confirmed=true) not
> > configured
> >
> >
> >
> > So I read the Filesystem script code, find following code before start
> > resource.
> >
> >
> >
> > case $FSTYPE in
> >
> > ocfs2) ocfs2_init
> >
> > ;;
> >
> > nfs|smbfs|none|gfs2) : # this is kind of safe too
>
> right. so just add cifs in there, ok?
> and send a patch ...

cifs added in upstream.

Thanks,

Dejan

> current upstream is here:
> https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/Filesystem
>
> >
> > ;;
> >
> > *) if [ -n "$OCF_RESKEY_CRM_meta_clone" ]; then
> >
> > ocf_log err "$OCF_RESKEY_CRM_meta_clone"
> >
> > ocf_log err "DANGER! $FSTYPE on $DEVICE is NOT
> > cluster-aware!"
> >
> > ocf_log err "DO NOT RUN IT AS A CLONE!"
> >
> > ocf_log err "Politely refusing to proceed to avoid data
> > corruption."
> >
> > exit $OCF_ERR_CONFIGURED
> >
> > fi
> >
> > ;;
> >
> > Esac
> >
> >
> >
> > I want to know why CIFS isn't the kind of safe FSTYPE, but smbfs is
> > considered safe ? They are not the same as it ?
> >
> >
> >
> > PS:
> >
> >
> >
> > I could start CIFS resource directly instead of clone.
> >
> >
> >
> >
> >
> > Best Regards,
> >
> > Qiu Zhigang
> >
> >
> >
> >
> >
>
> > _______________________________________________________
> > Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> > Home Page: http://linux-ha.org/
>
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
> _______________________________________________________
> Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/