On 2008-06-09T16:25:25, Florent DUTHEIL <[EMAIL PROTECTED]> wrote:
> One can see clearly in logs (when it comes to mount the first "bind/ro"
> ressource:
> Filesystem[2688][2718]: 2008/06/09_16:10:08 INFO: Running start for
> /mnt/filer1/drivers on /var/ftp/labtech/labtech_drivers
> Filesystem[2688][2719]: 2008/06/09_16:10:08 ERROR: DANGER! on
> /mnt/filer1/drivers is NOT cluster-aware!
> Filesystem[2688][2720]: 2008/06/09_16:10:08 ERROR: DO NOT RUN IT AS A
> CLONE!
> Filesystem[2688][2721]: 2008/06/09_16:10:08 ERROR: Politely refusing to
> proceed to avoid data corruption.
Well, I think that's fairly explicit. ;-) It tries to guard against
errors - such as users accidentially trying to clone an ext3 mount.
> Do I havet to "hack" the FS agent code to make him ignore every FS
> ressources that have the "bind" option?
> I suppose I would have to modify this statement:
>
> case $FSTYPE in
> ocfs2) ocfs2_init
> ;;
> nfs) : # this is kind of safe too
> ;;
> *) if [ -n "$OCF_RESKEY_CRM_meta_clone" ]; then
> 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_GENERIC
> fi
> ;;
> esac
Yes, you'll need to detect bind mounts here and permit them.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
