How long before /iwmnt matches /.iwmnt?

We are running TS 6.5 and OD 6.0.1 on Solaris 9. We are being victimized by this bug (fixed in OD 6.0.2):

59330 Database deployments deploying extended attributes on UNIX fails when using the non-cached mount point /.iwmnt.

(We are deploying DCRs, not extended attributes: that bug is more pernicious than described above.)

To get around the problem, we've added a "sleep" of 1 minute into our workflow to allow the /iwmnt cached mount to be synchronized with /.iwmt (so we can deploy from /iwmnt). Can we wait a shorter time? How short?

I guess it would be smarter to compare (for each submitted file) the version of the file in /iwmnt/.../STAGING with the version of the file in /.iwmnt/.../STAGING. Would that work? Or would we be better off doing a "diff"?

Is there a command to bring /iwmnt in sync with /.iwmnt? Any other thoughts? (Don't tell me to upgrade OD : )!)

Thanks,

S.

Find more posts tagged with

Comments

Migrateduser

Upgrade to 6.0.2 Smiley Wink

File attributes are by default cached for at least 3 seconds (30 for directories), but for no more than 60 seconds, hence the 1 minute recommendation. You could potentially change the caching options for /iwmnt, but this is, of course, NOT recommended by Interwoven support:

The <IWHOME>/bin/iwmount script contains the following two lines:

MOUNTOPTS="-o vers=2"
MOUNTOPTS_NOAC="-o vers=2,noac"

While I have not tested this, the following change should enable you to sleep for only 10 seconds:

MOUNTOPTS="-o vers=2,actimeo=10"
MOUNTOPTS_NOAC="-o vers=2,noac"

actimeo=n sets min and max times for regular files and directories to n seconds. Setting actimeo=0 disables attribute caching on the client. This means that every reference to attributes is satisfied directly from the server though file data is still cached. While this guarantees that the client always has the latest file attributes from the server, it has an adverse effect on performance through additional latency, network load, and server load.

A last option is setting the noac option as it also disables attribute caching, but has the further effect of disabling client write caching. While this guarantees that data written by an application is written directly to a server, where it can be viewed immediately by other clients, it has a significant adverse effect on client write performance:

MOUNTOPTS="-o vers=2,noac"
MOUNTOPTS_NOAC="-o vers=2,noac"

Stop TeamSite and make sure that all mounts under /iwmnt and /.iwmnt are unmounted successfully (use umount -f or reboot as needed). After starting TeamSite, the setup is complete.