bbs.hsiao.net 交流論壇

Posted: **Fri May 20, 2016 5:33 pm**

I don’t remember why but there’s the following config in oratest02:

fs:
        dir: /arch
        special: /oracle/oradata/ddms2t/arch
        raw not specified
        type: lofs
        options: []

That was causing:

Code: Select all

%zoneadm -z oratest02 ready
could not verify fs /arch: could not access /oracle/oradata/ddms2t/arch: No such file or directory

Once I removed the fs: config, I was able to move on to the next issue.

Code: Select all

zoneadm: zone 'oratest02': These file-systems are mounted on subdirectories of XXX

I then remembered I had to unmount the file systems from ZFS before I could bring NGZ up. I unmounted all file systems and then I was able to bring oratest02 up.

As for orautil01, something is happening to /cldm. I could unmounts all other file systems but /cldm complained the dataset was busy.
I had to force the unmounts from the command line:

Code: Select all

%zfs unmount -f oracledatapool/orautil01_cldm

Then, I was able to bring orautil01 up.
When I then tried to mount the file systems back, /cldm caused the issue again.

Code: Select all

%zfs mount oracledatapool/orautil01_cldm   
cannot mount 'oracledatapool/orautil01_cldm': mountpoint or dataset is busy

Then, I had to use the “-O” flag to mount it:

Code: Select all

%zfs mount -O oracledatapool/orautil01_cldm

This may have something to do with the NFS mount point for Watson project.

Code: Select all

orazone01:/%exportfs
/cldm_arch      /zonepool/zones/orautil01/root/cldm/arch   ro   "CareLink Archive Logs"

bbs.hsiao.net 交流論壇

Orazone01 ZFS administration

Orazone01 ZFS administration