On Tue, Oct 18, 2005 at 03:35:30PM -0600, [EMAIL PROTECTED] wrote:
> 
> I can mount it from the host using /usr/local/etc/vservers/unixdev1/fstab but 
> have not figured out how to umount (if possible)
> 
> I was able to use the bcapabilities numeric values with out getting errors on 
> vserver startup.
> cat /usr/local/etc/vservers/unixdev1/bcapabilities
> 0x00010000
> 0x00020000
> 0x00040000
> 
> even with this I am unable to unmount the nfs filesystem when mounted
> from the host into the vserver.

not unexpected, again bcaps != ccaps and if you want
to use numeric values, it's probably easier to use

 ^16
 ^17
 ^18

which means bits 16,17, and 18 ...

> when trying from inside the vserver I can not even mount the nfs filesystem
> sudo mount -v -t nfs calnfs01.corporate.net:/nfs_unix_data /unix_data
> mount: failed with nfs mount version 4, trying 3..
> mount: permission denied
> the nfs server shows
> Oct 18 15:31:57 calnfs01 rpc.mountd: authenticated mount request from 
> unixdev1.corporate.net:783 for /nfs_unix_data (/nfs_unix_data)
> Oct 18 15:31:57 calnfs01 rpc.mountd: authenticated mount request from 
> unixdev1.corporate.net:787 for /nfs_unix_data (/nfs_unix_data)
> 
> 
> I have been working on this from several angles to no avail. Is anyone
> else mounting nfs into a vserver? How are you doing it? Are you able
> to umount it afterwards?

you need SECURE_MOUNT and BINARY_MOUNT to mount and
unmount NFS inside a guest, but you can also unmount
it from the host (as you mounted it from the host :)

HTH,
Herbert

> thanks
> sig
> 
> 
> 
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Magnuson,
> Sig
> Sent: Tuesday, October 18, 2005 11:50 AM
> To: vserver@list.linux-vserver.org
> Subject: RE: [Vserver] unmount nfs with vserver
> 
> 
> I have done the following but am getting a error
> sudo vi /usr/local/etc/vservers/caloratst01/bcapabilities
> VXC_SECURE_MOUNT
> VXC_SECURE_REMOUNT
> VXC_BINARY_MOUNT
> 
> I also tried:
> SECURE_MOUNT
> SECURE_REMOUNT
> BINARY_MOUNT
> 
> I am getting the following error on vserver startup
> sudo vserver caloratst01 start
> Unknown bcap 'VXC_SECURE_MOUNT'
> 
> An error occured while executing the vserver startup sequence; when
> there are no other messages, it is very likely that the init-script
> (/sbin/init) failed.
> 
> Common causes are:
> * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build
>   method knows how to deal with this, but on existing installations,
>   appending 'true' to this file will help.
> 
> Failed to start vserver 'caloratst01'
> 
> Have I got the syntax of the file wrong?
> 
> 
> -----Original Message-----
> From: Herbert Poetzl [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 14, 2005 11:18 AM
> To: Magnuson, Sig
> Cc: vserver@list.linux-vserver.org
> Subject: Re: [Vserver] unmount nfs with vserver
> 
> 
> On Fri, Oct 14, 2005 at 10:42:49AM -0600, [EMAIL PROTECTED] wrote:
> > A while back I posted to the list about mounting nfs filesystem into a
> > vserver. The only suggestion that I could get to work was adding the
> > mount to fstab on host system.
> 
> > IE:
> > cat /usr/local/etc/vservers/unixdev1/fstab
> > none    /proc           proc    defaults                0 0
> > none    /tmp            tmpfs   size=64m,mode=1777      0 0
> > none    /dev/pts        devpts  gid=5,mode=620          0 0
> > # added Sept 14, 2005 - common unix NFS filesystem -sig
> > calnfs01.corporate.net:/nfs_unix_data /unix_data nfs     hard,intr,nolock 0 > > 0
> > 
> > The one issue I came across was that I could not find a way to umount
> > the NFS filesystem
> > ssh unixdev1
> > sudo umount /unix_data
> > umount: /unix_data: must be superuser to umount
> > umount: /unix_data: must be superuser to umount
> 
> >>hmm, looks like you are missing one of the
> >>context capabilities for secure mount ...
> 
> >>#define VXC_SECURE_MOUNT        0x00010000
> >>#define VXC_SECURE_REMOUNT      0x00020000
> >>#define VXC_BINARY_MOUNT        0x00040000
> 
> > I thought I would be fine with it that way but it turns out it is a
> > bigger issue than I thought. Any suggestions on how to umount the NFS
> > filesystem?
> 
> >>unmounting on the host should work quite fine ...
> 
> >>best,
> >>Herbert
> 
> > I have access to host and vserver.
> > thanks
> > sig
> > 
> > 
> > 
> > sudo ./vserver-testme.sh
> > Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl
> > chcontext is working.
> > chbind is working.
> > Linux 2.6.12.4-vs2.0 i686/0.30.208/0.30.208 [Ea] (0)
> > VCI:  0002:0001 273 03000016
> > ---
> > [000]# succeeded.
> > [001]# succeeded.
> > [011]# succeeded.
> > [031]# succeeded.
> > [101]# succeeded.
> > [102]# succeeded.
> > [201]# succeeded.
> > [202]# succeeded.
> > 
> > sudo vserver-info
> > Versions:
> >                    Kernel: 2.6.12.4-vs2.0
> >                    VS-API: 0x00020001
> >              util-vserver: 0.30.208; Aug 24 2005, 21:26:20
> > 
> > Features:
> >                        CC: gcc, gcc (GCC) 3.4.3 (CRUX)
> >                       CXX: g++, g++ (GCC) 3.4.3 (CRUX)
> >                  CPPFLAGS: ''
> >                    CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W 
> > -funit-at-a-time'
> >                  CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W 
> > -fmessage-length=0 -
> > funit-at-a-time'
> >                build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
> >              Use dietlibc: yes
> >        Build C++ programs: yes
> >        Build C99 programs: yes
> >            Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts
> >             ext2fs Source: e2fsprogs
> >     syscall(2) invocation: alternative
> >       vserver(2) syscall#: 273/glibc
> > 
> > Paths:
> >                    prefix: /usr/local
> >         sysconf-Directory: ${prefix}/etc
> >             cfg-Directory: ${prefix}/etc/vservers
> >          initrd-Directory: $(sysconfdir)/init.d
> >        pkgstate-Directory: ${prefix}/var/run/vservers
> >             Kernelheaders: /lib/modules/2.6.12.4-vs2.0/build/include
> >           vserver-Rootdir: /vservers
> > 
> > 
> > Assumed 'SYSINFO' as no other option given; try '--help' for more 
> > information.
> > 
> > 
> > _______________________________________________
> > Vserver mailing list
> > Vserver@list.linux-vserver.org
> > http://list.linux-vserver.org/mailman/listinfo/vserver
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to