[Ocfs2-tools-devel] [RFC] [PATCH] ocfs2-tools: mark 'datavolume' in OCFS2 1.4 as obsoleted in documents

[Sunil Mushran]

We no longer maintain this faq in ocfs2-tools. Instead we update
the one on oss.oracle.com. There the older faq has been moved
under ocfs2 1.2 docs.

I am not sure we need to document this change in behavior. As in,
the complicated explanation has no real value to end users. We should
just let this mount option fade away into the sunset. No glorious send 
off. :)

All we have to do is ensure that the oracle db users are setting
the init.ora parameter filesystemio_options appropriately. The ocfs2
1.4 guide explains that bit.

Coly Li wrote:
> In OCFS2 1.4, mount option "datavolume" is not supported in upstream any more. In enterprise kernel
> like SLE11 HASI (SuSE Linux Enterprise 11 High Availability Storage Infrastructure) this option is
> still accepted for compatibility reason, but do nothing indeed.
>
> This patch adds explaining of 'datavolume' option support in OCFS2 1.4 of SLE11 HASI kernel. On
> kernel side, datavolume is still accepted, but a printk message will info users that the option is
> deprecated now.
>
> Any feedback is welcome. Thanks for review.
>
> Signed-off-by: Coly Li <coly.li at suse.de>
> ---
>  documentation/ocfs2_faq.txt  |   10 +++++++---
>  mount.ocfs2/mount.ocfs2.8.in |    4 +++-
>  2 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/documentation/ocfs2_faq.txt b/documentation/ocfs2_faq.txt
> index 28219d9..eb237e2 100644
> --- a/documentation/ocfs2_faq.txt
> +++ b/documentation/ocfs2_faq.txt
> @@ -302,13 +302,17 @@ Oracle RAC
>  ----------
>
>  Q01	Any special flags to run Oracle RAC?
> -A01	OCFS2 volumes containing the Voting diskfile (CRS), Cluster registry
> -	(OCR), Data files, Redo logs, Archive logs and control files must
> -	be mounted with the "datavolume" and "nointr" mount options. The
> +A01	OCFS2 1.2 volumes containing the Voting diskfile (CRS), Cluster
> +	registry (OCR), Data files, Redo logs, Archive logs and control files
> +	must be mounted with the "datavolume" and "nointr" mount options. The
>  	datavolume option ensures that the Oracle processes opens these files
>  	with the o_direct flag. The "nointr" option ensures that the ios
>  	are not interrupted by signals.
>  	# mount -o datavolume,nointr -t ocfs2 /dev/sda1 /u01/db
> +	OCFS2 1.4 volumes in enterprise kernel like SLE11 (SuSE Linux
> +	Enterprise 11) HASI (High Availability Storage Infrastructure),
> +	"datavolume" option is still accepted for compatibility reason, but
> +	does nothing indeed.
>
>  Q02	What about the volume containing Oracle home?
>  A02	Oracle home volume should be mounted normally, that is, without the
> diff --git a/mount.ocfs2/mount.ocfs2.8.in b/mount.ocfs2/mount.ocfs2.8.in
> index 0f666dd..c59dbf2 100644
> --- a/mount.ocfs2/mount.ocfs2.8.in
> +++ b/mount.ocfs2/mount.ocfs2.8.in
> @@ -52,7 +52,9 @@ recovery.
>  \fBdatavolume\fR
>  Use this mount option to mount volumes storing the Oracle data files,
>  control files, redo logs, archive logs, voting disk, cluster registry, etc.
> -(This mount option is only available with \fIOCFS2 1.2\fR and \fIOCFS2 1.4\fR.)
> +(This mount option is only available with \fIOCFS2 1.2\fR. For \fIOCFS2 1.4\fR
> +in enterprise kernel like SLE11 HASI, "datavolume" is still accepted for
> +compatibility reason, but does nothing indeed.)
>
>  .TP
>  \fBerrors=remount-ro / errors=panic\fR
>
>