Hi Marty,

Here is the information:

[root@meng]#cat /etc/exports
/secondary *(rw,async,no_root_squash)
/primary   *(rw,async,no_root_squash)

[root@meng Downloads]# exportfs
/secondary      <world>
/primary        <world>

[root@meng Downloads]# exportfs -a

There is no output for exportfs -a.





On Fri, 23 Aug 2013 18:53:51 +0100, Marty Sweet wrote:
Hi Meng,

I would first look at the management server and ignore the SSVM until you
are sure the NFS share is working.

Could you post the output of: exportfs -a and cat /etc/exports ?
I can then give more guidance.

Thanks,
Marty


On Fri, Aug 23, 2013 at 5:01 PM, Han,Meng <meng...@ufl.edu> wrote:

Hi folks,

I am following the 4.1 quick install guide to deploy cloudstack. Now I am
unable to mount the secondary storage from ssvm. I tried system
reinstallation many times...

Below is some information about this issue:

root@s-1-VM:~# /usr/local/cloud/systemvm/**ssvm-check.sh
==============================**==================
First DNS server is  8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=47 time=1067.133 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=47 time=66.248 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 66.248/566.691/1067.133/500.**443 ms
Good: Can ping DNS server
==============================**==================
Good: DNS resolves download.cloud.com
==============================**==================
ERROR: NFS is not currently mounted
Try manually mounting from inside the VM
NFS server is  169.254.3.46
PING 169.254.3.46 (169.254.3.46): 56 data bytes
64 bytes from 169.254.3.46: icmp_seq=0 ttl=64 time=0.042 ms
64 bytes from 169.254.3.46: icmp_seq=1 ttl=64 time=0.054 ms
--- 169.254.3.46 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.042/0.048/0.054/0.000 ms
Good: Can ping NFS server
==============================**==================
Management server is 10.244.18.55. Checking connectivity.
Good: Can connect to management server port 8250
==============================**==================
Good: Java process is running
==============================**==================
Tests Complete. Look for ERROR or WARNING above.

The NFS server address listed above is actually the address of ssvm. Could someone tell me why the ssvm address is there instead of the nfs server? I am using the management server as the nfs server, its ip is 10.244.18.55

The contents of /var/cache/cloud/cmdline is:
template=domP type=secstorage host=10.244.18.55 port=8250 name=s-1-VM zone=1 pod=1 guid=s-1-VM resource=com.cloud.storage.**resource.**NfsSecondaryStorageResource
instance=SecStorage sslcopy=true role=templateProcessor mtu=1500
eth2ip=10.244.18.56 eth2mask=255.255.255.0 gateway=10.244.18.1
eth0ip=169.254.3.46 eth0mask=255.255.0.0 eth1ip=10.244.18.47
eth1mask=255.255.255.0 mgmtcidr=10.244.18.0/24 localgw=10.244.18.1
private.network.device=eth1 eth3ip=10.244.18.49 eth3mask=255.255.255.0
storageip=10.244.18.49 storagenetmask=255.255.255.0
storagegateway=10.244.18.1 internaldns1=8.8.8.8 internaldns2=8.8.4.4
dns1=8.8.8.8 dns2=8.8.4.4

The firewall rule on the nfs server is :
-A INPUT -p tcp -m tcp --dport 49152:49216 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 16509 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 9090 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8250 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 7080 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport 111
-j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport 111
-j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport
2049 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport
32803 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport
32769 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport 892
-j ACCEPT
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport 892
-j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport 875
-j ACCEPT
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport 875
-j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport 662
-j ACCEPT
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport 662
-j ACCEPT
-A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state
RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT

The network information is:

cloud0    Link encap:Ethernet  HWaddr FE:00:A9:FE:01:A8
inet addr:169.254.0.1 Bcast:169.254.255.255 Mask:255.255.0.0
          inet6 addr: fe80::94da:98ff:fefd:ffa/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:364 errors:0 dropped:0 overruns:0 frame:0
          TX packets:562 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:43632 (42.6 KiB)  TX bytes:52405 (51.1 KiB)

cloudbr0  Link encap:Ethernet  HWaddr 00:23:AE:94:F7:22
inet addr:10.244.18.55 Bcast:10.244.18.255 Mask:255.255.255.0
          inet6 addr: fe80::223:aeff:fe94:f722/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1293010 errors:0 dropped:0 overruns:0 frame:0
          TX packets:855962 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
RX bytes:1021904803 (974.5 MiB) TX bytes:240327484 (229.1 MiB)

eth0      Link encap:Ethernet  HWaddr 00:23:AE:94:F7:22
          inet6 addr: fe80::223:aeff:fe94:f722/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2524952 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1556673 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
RX bytes:2862800124 (2.6 GiB) TX bytes:283924007 (270.7 MiB)
          Interrupt:21 Memory:fe6e0000-fe700000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:130588685 errors:0 dropped:0 overruns:0 frame:0
TX packets:130588685 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
RX bytes:444681794053 (414.1 GiB) TX bytes:444681794053 (414.1
GiB)

virbr0    Link encap:Ethernet  HWaddr 52:54:00:7C:47:2C
          inet addr:192.168.122.1  Bcast:192.168.122.255
 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:85 (85.0 b)

vnet0     Link encap:Ethernet  HWaddr FE:00:A9:FE:03:2E
          inet6 addr: fe80::fc00:a9ff:fefe:32e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:347 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3086 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:47385 (46.2 KiB)  TX bytes:218921 (213.7 KiB)

vnet1     Link encap:Ethernet  HWaddr FE:25:C6:00:00:03
          inet6 addr: fe80::fc25:c6ff:fe00:3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14481 errors:0 dropped:0 overruns:0 frame:0
          TX packets:285518 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:1442681 (1.3 MiB)  TX bytes:28710317 (27.3 MiB)

vnet2     Link encap:Ethernet  HWaddr FE:E9:D6:00:00:0B
          inet6 addr: fe80::fce9:d6ff:fe00:b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:219253 errors:0 dropped:0 overruns:0 frame:0
          TX packets:831307 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
RX bytes:12892318 (12.2 MiB) TX bytes:816300221 (778.4 MiB)

vnet3     Link encap:Ethernet  HWaddr FE:29:F2:00:00:05
          inet6 addr: fe80::fc29:f2ff:fe00:5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:271065 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:1332 (1.3 KiB)  TX bytes:27089428 (25.8 MiB)

vnet4     Link encap:Ethernet  HWaddr FE:00:A9:FE:01:A8
          inet6 addr: fe80::fc00:a9ff:fefe:1a8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2572 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:1343 (1.3 KiB)  TX bytes:169551 (165.5 KiB)

vnet5     Link encap:Ethernet  HWaddr FE:93:CA:00:00:07
          inet6 addr: fe80::fc93:caff:fe00:7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:82974 errors:0 dropped:0 overruns:0 frame:0
          TX packets:353899 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:9191158 (8.7 MiB)  TX bytes:35429714 (33.7 MiB)

vnet6     Link encap:Ethernet  HWaddr FE:72:0C:00:00:0E
          inet6 addr: fe80::fc72:cff:fe00:e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:270934 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:778 (778.0 b)  TX bytes:27076384 (25.8 MiB)

The contents of /etc/sysconfig/network-**scripts/ifcfg-eth0 is:
DEVICE=eth0
TYPE=Ethernet
UUID=7ba41ef9-9868-432d-866d-**b4dbe18d9ba5
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
HWADDR=00:23:AE:94:F7:22
PEERDNS=yes
PEERROUTES=yes
IPADDR=10.244.18.55
NETMASK=255.255.255.0
GATEWAY=10.244.18.1
DNS1=8.8.8.8
DNS2=8.8.4.4
BRIDGE=cloudbr0

Now on the management server side, I see the following error on one of my
templates:
Failed post download script: bunzip2: I/O or other error, bailing out.
Possible reason follows.bunzip2: No space left on devicefailed to
uncompress /mnt/SecStorage/9db5f864-def4-**30f9-8e25-2f5215113de8/**
template/tmpl/1/4/**dnld1953772300383463570tmp_

The secondary storage is giving me a alert about low availability. I tried
manually mount the nfs share inside the ssvm, the mount gives me an
input/output error. But I can mount the nfs share from the management
server.

Could someone give me some light what is wrong here? I reinstalled my OS
many times, this error shows every time.

Thanks you all.

Best Regards,
Meng



Reply via email to