Hi Lewis,

On Tue, Sep 9, 2008 at 6:03 AM, Lewis Thompson <[EMAIL PROTECTED]> wrote:
> Hi,
> I have a simple zone configured to test the VxFS 'convosync=direct'
> option.  It's an s10u5 machine with no additional patches:
>        zonecfg:lt203398:fs> info
>        fs:
>                dir: /foo
>                special: /dev/lofi/1
>                raw: /dev/rlofi/1
>                type: vxfs
>                options: [rw]
> So far so good, but when I try and add a VxFS-style 'setting=value'
> option, zonecfg fails:
>        zonecfg:lt203398:fs> set options=[convosync=direct]
>        syntax error at '='

The zonecfg man page has an example of the use of fs options:

       zonecfg:myzone3> add fs
       zonecfg:myzone3:fs> set dir=/usr/local
       zonecfg:myzone3:fs> set special=/opt/local
       zonecfg:myzone3:fs> set type=lofs
       zonecfg:myzone3:fs> add options [ro,nodevices]
       zonecfg:myzone3:fs> end

Have you attempted to specify the options using that syntax?

> >From mount_vxfs man page:
>        convosync=direct|dsync|unbuffered|closesync|delay
> So my question is: do we support these vxfs options when setting up
> filesystem definitions?  If I manually edit the zone definition file to
> add the convosync=direct option then a zoneadm boot fails with fsck exit
> status 32...
> Many thanks,
> Lewis

zones-discuss mailing list

Reply via email to