[Pacemaker] why pacemaker can't clone CIFS Filesystem resource

[Mark Gardner]

>
> 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 ?
>

I had a similar problem with a different cluster aware Filesystem, panasas.
 Simply make a copy of the Filesystem script with your own name, add smbfs,
to the list of cluster aware filesystems.  Then create your clone of the
"new" resource agent.

(BTW, sambafs is NOT cluster aware, there is no distributed locking, and
CIFS is cluster aware, CIFS is an enhanced version of Microsoft's SMB
protocol,  They are subtly different.  )

In most cases they are interchangeable, but depending on
your distribution, CIFS and smbfs may or may not be an alias of each other.


-- 

   ~ Mark
         Gardner ~
If it were easy everyone would do it.  Hard is what keeps out the riffraff.
***
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20111223/86b9e615/attachment.htm>