[zones-discuss] Failing to NFS mount on non-global zone

2009-02-20 Thread Asif Iqbal
I configured a zone called `syslog' where I am failing to mount a NFS
folder and getting device busy

zonecfg -z syslog info
zonename: syslog
zonepath: /syslog
brand: native
autoboot: true
bootargs: -m verbose
pool:
limitpriv: default,sys_time
scheduling-class: FSS
ip-type: shared
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
fs:
dir: /var/logs
special: /var/logs
raw not specified
type: lofs
options: []
fs:
dir: /usr/local
special: /syslog-local/usr/local
raw not specified
type: lofs
options: []
fs:
dir: /netapp/tacacs
special: /syslog-local/netapp/tacacs
raw not specified
type: lofs
options: []
fs:
dir: /netapp/syslog
special: /syslog-local/netapp/syslog
raw not specified
type: lofs
options: []
net:
address: 192.168.0.113
physical: aggr1
defrouter: 192.168.0.1
dedicated-cpu:
ncpus: 1-8
importance: 10
capped-memory:
physical: 1G
[swap: 512M]
attr:
name: comment
type: string
value: syslog server
rctl:
name: zone.max-swap
value: (priv=privileged,limit=536870912,action=deny)~# zlogin syslog


[Connected to zone 'syslog' pts/2]
Last login: Fri Feb 20 11:16:32 from syslog1
Sun Microsystems Inc.   SunOS 5.10  Generic January 2005
# bash
bash-3.00# cat /etc/vfstab | grep netapp
192.168.0.25:/volB/netapp/syslog - /netapp/syslog nfs - no hard,intr,bg,xattr
192.168.0.25:/volA/netapp/tacacs - /netapp/tacacs nfs - no hard,intr,bg,xattr

bash-3.00# mount /netapp/syslog
nfs mount: mount: /netapp/syslog: Device busy

Any idea what I am doing wrong ?

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Failing to NFS mount on non-global zone

2009-02-20 Thread Christine Tran
 fs:
dir: /netapp/tacacs
special: /syslog-local/netapp/tacacs
raw not specified
type: lofs
options: []
 fs:
dir: /netapp/syslog
special: /syslog-local/netapp/syslog
raw not specified
type: lofs
options: []

 [Connected to zone 'syslog' pts/2]
 bash-3.00# cat /etc/vfstab | grep netapp
 192.168.0.25:/volB/netapp/syslog - /netapp/syslog nfs - no hard,intr,bg,xattr
 192.168.0.25:/volA/netapp/tacacs - /netapp/tacacs nfs - no hard,intr,bg,xattr


You LOFS-mount the directory *and* you NFS-mount it inside the zone?
How about one or the other?  Why not just NFS mount the directory from
syslog and that's that?  In fact, my memory is fuzzy but I don't think
you can LOFS an NFS-mount done by the global zone.  There's a
credential problem, the NFS client is really one client (the global
zone) but access to the mount looks different when it's done from the
global zone or the non-global zone.  There's a bug on record for this,
I think.

CT
___
zones-discuss mailing list
zones-discuss@opensolaris.org