OpenVZ Forum


Home » General » Support » [solved] NFS export /vz results in "Cannot allocate memory" on HN / CT0
[solved] NFS export /vz results in "Cannot allocate memory" on HN / CT0 [message #33953] Fri, 21 November 2008 12:34 Go to next message
disaster is currently offline  disaster
Messages: 158
Registered: February 2006
Senior Member
Hello!

I would like to export /vz but it does not work. I always get permission denied but in log is only written.

mountd[19291]: authenticated mount request from 192.168.0.1:729 for /vz (/vz)


Client:
mount: 192.168.0.3:/vz/ failed, reason given by server: Permission denied


But when i change /etc/export from /vz to /usr and then try to mount /usr it works fine.

Kernel is: RHEL5 2.6.18-059.6

Stefan

[Updated on: Mon, 24 November 2008 12:00] by Moderator

Report message to a moderator

Re: NFS how to export /vz [message #33959 is a reply to message #33953] Fri, 21 November 2008 14:22 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hello,

I'm afraid it is not OpenVZ specific question.
May be it's worth looking at /etc/export, /etc/hosts.deny files more carefully or restart nfs service.
By the way why do you want to export /vz partition?
Re: NFS how to export /vz [message #33960 is a reply to message #33953] Fri, 21 November 2008 14:28 Go to previous messageGo to next message
disaster is currently offline  disaster
Messages: 158
Registered: February 2006
Senior Member
Hi!

As i've written all other directories OTHER than /vz DO work fork export with SAME /etc/export only change directoryname.

But here is the file content:
/vz 192.168.0.0/255.255.255.0(rw,no_root_squash,sync,no_subtree_check)


hosts.deny is empty. Although as i've written nfsd writes: "mountd[19291]: authenticated mount request from 192.168.0.1:729 for /vz (/vz)" if hosts.deny is the problem then it will not write this message.

I do not want to export /vz only a directory in it - but it also does not work for /vz at all.

cat /proc/mounts 
none /sys sysfs rw 0 0
none /proc proc rw 0 0
udev /dev tmpfs rw 0 0
/dev/sda6 / xfs rw 0 0
/dev/sda6 /dev/.static/dev xfs rw 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec 0 0
/dev/sda5 /boot ext2 rw 0 0
/dev/drbd0 /vz ext3 rw,data=ordered 0 0
nfsd /proc/fs/nfsd nfsd rw 0 0
/vz/private/110 /vz/root/110 simfs rw 0 0
tmpfs /vz/root/110/lib/init/rw tmpfs rw,nosuid 0 0
/proc /vz/root/110/proc proc rw,nosuid,nodev,noexec 0 0
sysfs /vz/root/110/sys sysfs rw,nosuid,nodev,noexec 0 0
varrun /vz/root/110/var/run tmpfs rw,nosuid 0 0
varlock /vz/root/110/var/lock tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /vz/root/110/dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /vz/root/110/dev/pts devpts rw,nosuid,noexec 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0


An strace if rpc.mountd results in some cannot allocate memory:
rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0
open("/var/lib/nfs/rmtab", O_RDWR)      = 11
fstat(11, {st_mode=S_IFREG|0644, st_size=330, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b6b2b250000
lseek(11, 0, SEEK_CUR)                  = 0
read(11, "192.168.0.10:192.168.0.0/255.255"..., 4096) = 330
lseek(11, 330, SEEK_SET)                = 330
lseek(11, -223, SEEK_CUR)               = 107
write(11, "192.168.0.1:192.168.0.0/255.255."..., 49) = 49
fdatasync(11)                           = 0
close(11)                               = 0
munmap(0x2b6b2b250000, 4096)            = 0
close(10)                               = 0
open("/proc/net/rpc/nfsd.export/channel", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 10
fstat(10, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b6b2b250000
write(10, "192.168.0.0/255.255.255.0 /vz 12"..., 61) = -1 ENOMEM (Cannot allocate memory)
close(10)                               = 0
munmap(0x2b6b2b250000, 4096)            = 0
open("/var/lib/nfs/rmtab", O_RDWR|O_CREAT, 01777777777777777777757) = 10
rt_sigaction(SIGALRM, {0x409fe0, [], SA_RESTORER, 0x2b6b2b59f110}, {SIG_DFL}, 8) = 0
alarm(10)                               = 0
fcntl(10, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0
alarm(0)                                = 10
rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0
open("/var/lib/nfs/rmtab", O_RDWR)      = 11
fstat(11, {st_mode=S_IFREG|0644, st_size=330, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b6b2b250000
lseek(11, 0, SEEK_CUR)                  = 0
read(11, "192.168.0.10:192.168.0.0/255.255"..., 4096) = 330
lseek(11, 330, SEEK_SET)                = 330
lseek(11, -41, SEEK_CUR)                = 289
write(11, "192.168.0.0/255.255.255.0:/vz:0x"..., 41) = 41
fdatasync(11)                           = 0
close(11)                               = 0
munmap(0x2b6b2b250000, 4096)            = 0
close(10)                               = 0
open("/proc/fs/nfsd/filehandle", O_RDWR) = 10
fstat(10, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b6b2b250000
write(10, "192.168.0.0/255.255.255.0 /vz 64"..., 34) = -1 ENOMEM (Cannot allocate memory)
read(10, "", 4096)                      = 0
close(10)                               = 0
munmap(0x2b6b2b250000, 4096)            = 0


Kernel is: RHEL5 2.6.18-059.6

Stefan

[Updated on: Fri, 21 November 2008 14:37]

Report message to a moderator

Re: NFS cannot export /vz [message #33983 is a reply to message #33953] Mon, 24 November 2008 07:45 Go to previous messageGo to next message
disaster is currently offline  disaster
Messages: 158
Registered: February 2006
Senior Member
nobody an idea?

Another example:
/etc/exports
/vz 192.168.0.0/255.255.255.0(rw,no_root_squash,sync,no_subtree_check)
/usr 192.168.0.0/255.255.255.0(rw,no_root_squash,sync,no_subtree_check)


mounting:
fw-office:~# mount -t nfs 192.168.0.3:/usr/ /mnt/; umount /mnt/  
fw-office:~# mount -t nfs 192.168.0.3:/vz/ /mnt/; umount /mnt/   
mount: 192.168.0.3:/vz/ failed, reason given by server: Permission denied
umount: /mnt/: not mounted


log on nfs:
==> /var/log/daemon <==
Nov 24 08:43:18 cluster-office2 mountd[8515]: authenticated mount request from 192.168.0.1:990 for /usr (/usr)
Nov 24 08:43:19 cluster-office2 mountd[8515]: authenticated unmount request from 192.168.0.1:992 for /usr (/usr)
Nov 24 08:43:27 cluster-office2 mountd[8515]: authenticated mount request from 192.168.0.1:995 for /vz (/vz)
Re: NFS cannot export /vz [message #33984 is a reply to message #33953] Mon, 24 November 2008 09:10 Go to previous messageGo to next message
disaster is currently offline  disaster
Messages: 158
Registered: February 2006
Senior Member
strace of mountd

For a dir that works fine (/usr):
open("/proc/fs/nfsd/filehandle", O_RDWR) = 10
fstat(10, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b50edee5000
write(10, "192.168.0.0/255.255.255.0 /usr 6"..., 35) = 35
read(10, "\\x010000000008000697080000\n", 4096) = 27
close(10)                               = 0
munmap(0x2b50edee5000, 4096)            = 0
write(8, "\200\0\0Dr\214\207Y\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 72) = 72
select(1024, [3 4 5 6 7 8], NULL, NULL, NULL) = 1 (in [8])
poll([{fd=8, events=POLLIN, revents=POLLIN}], 1, 35000) = 1
read(8, "", 4000)                       = 0
close(8)                                = 0
select(1024, [3 4 5 6 7], NULL, NULL, NULL


for /vz dir:
open("/proc/fs/nfsd/filehandle", O_RDWR) = 10
fstat(10, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b50edee5000
write(10, "192.168.0.0/255.255.255.0 /vz 64"..., 34) = -1 ENOMEM (Cannot allocate memory)
read(10, "", 4096)                      = 0
close(10)                               = 0
munmap(0x2b50edee5000, 4096)            = 0
write(8, "\200\0\0\34o~V*\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32) = 32
select(1024, [3 4 5 6 7 8], NULL, NULL, NULL) = 1 (in [8])
poll([{fd=8, events=POLLIN, revents=POLLIN}], 1, 35000) = 1
read(8, "", 4000)                       = 0
close(8)                                = 0
select(1024, [3 4 5 6 7], NULL, NULL, NULL


Re: NFS cannot export /vz [message #33985 is a reply to message #33984] Mon, 24 November 2008 11:18 Go to previous messageGo to next message
den is currently offline  den
Messages: 494
Registered: December 2005
Senior Member
it is impossible to export any filesystem which has vzquota turned on.

Rationale:
- NFS server accesses inodes by number. In this case the tree of dentries (path names) is not maintained
- VZQUOTA, in turn, failures if found not attached dentry
Re: NFS export /vz results in "Cannot allocate memory" on HN / CT0 [message #33986 is a reply to message #33953] Mon, 24 November 2008 11:21 Go to previous messageGo to next message
disaster is currently offline  disaster
Messages: 158
Registered: February 2006
Senior Member
mhm so i've to diable vzquota and then it'll work? (how to disable vzquota?)?

Is there any other workaround possible?
Re: NFS export /vz results in "Cannot allocate memory" on HN / CT0 [message #33987 is a reply to message #33986] Mon, 24 November 2008 11:35 Go to previous messageGo to next message
den is currently offline  den
Messages: 494
Registered: December 2005
Senior Member
check /etc/vz/vz.conf
it should have DISK_QUOTA=yes or no

if my memory does not fail me, reboot is required
Re: NFS export /vz results in "Cannot allocate memory" on HN / CT0 [message #33988 is a reply to message #33953] Mon, 24 November 2008 11:47 Go to previous message
disaster is currently offline  disaster
Messages: 158
Registered: February 2006
Senior Member
oh thanks - OK now it works.
Previous Topic: MySQL constantly crashing
Next Topic: Setting Resource Limit's
Goto Forum:
  


Current Time: Tue Jul 29 18:10:58 GMT 2025

Total time taken to generate the page: 0.07468 seconds