On 02/23/2012 02:41 PM, Keith Robertson wrote:
On 02/23/2012 02:21 PM, Terry Phelps wrote:
Thanks for the quick reply.
My one hypervisor already had the ISO domain mounted (without any
explicit action by me):
This is to be expected. VDSM needs the mount. I suggested that
command just in case it wasn't mounted for some odd reason.
mount | grep iso
oravm3.acbl.net:/isodomain/ on
/rhev/data-center/mnt/oravm3.acbl.net:_isodomain type nfs4
(rw,relatime,vers=4,rsize=524288,wsize=524288,namlen=255,soft,nosharecache,proto=tcp,port=0,timeo=600,retrans=6,sec=sys,clientaddr=172.16.2.52,minorversion=0,local_lock=none,addr=192.168.118.10)
Using this mount (I didn't do exactly what you said, if that matters),
Nope, you're fine.
I did the tests you asked for.
Yes, I can touch a new file.
Yes, I can read the ISO file
Here is what I saw:
I'm assuming you were "vdsm" when you executed these commands, right?
bash-4.2$ ls
OracleLinux-R6-U2-Server-x86_64-dvd.iso
bash-4.2$ touch me
bash-4.2$ ls
me OracleLinux-R6-U2-Server-x86_64-dvd.iso
bash-4.2$ strings Orac* |head -2
CD001
LINUX OL6.2 x86_64 Disc 1 20111212
Funny, though. When I typed "su - vdsm" by mistake, from root, it said
"This account is currently not available." (Is that relevant?) But
what you said to do did work fine.
By default vdsm is given a nologin shell for security reasons. The
"-s /bin/bash" overrides that when switching users.
nfs-check tool might help here too... it mount, creates (as vdsm:kvsm)
and remove file into the nfs mountpoint...
http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=contrib/nfs-check.py;h=1b763c66e053eae2c273048879aa98e634b04d7f;hb=578cfe90239d5c3f6f11f1fc063c148606e991dc
--
Cheers
Douglas
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
