You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/11 13:01:13 UTC
[jira] [Commented] (CLOUDSTACK-5202) [Hyper-V] Too many mount
points created for secondary storage in management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845337#comment-13845337 ]
ASF subversion and git services commented on CLOUDSTACK-5202:
-------------------------------------------------------------
Commit 5dea7728a3f8da4d2af21ad117ba052cb3f788fc in branch refs/heads/4.3 from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5dea772 ]
CLOUDSTACK-5248: Fixed creation of mount point when running as non root (cloud) user.
The systemvm iso file is copied only when a systemvm or router vm is to be started on
a host. The file gets copied to the secondary storage. The mount point used is the one
that has permissions for regular user to mount a share.
CLOUDSTACK-5275: The failure was because a secondary storage wasn't available when the
host was added. When a setup is done through wizard the hosts get added before the
secondary storage. CS was tying to copy yhe systemvm iso to secondary and it used to
fail if it wasn't available. Made a change to copy the iso only when a systemvm is
being started on a host.
CLOUDSTACK-5202: Made changes to clean up mount points on stop and start.
All the three are related fixes; so putting a fix in one commit.
> [Hyper-V] Too many mount points created for secondary storage in management server
> ----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5202
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5202
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server, Storage Controller
> Environment: 4.3, Hyper-v, Advanced zone
> Reporter: Sowmya Krishnan
> Priority: Minor
> Labels: hyper-V,
>
> Too many mount points are created in management server after secondary storage has been created. I didn't notice any issues due to this, but it's not very desirable to have too many mounts for any reason. Here's how it is in my current setup:
> [root@localhost ~]# mount
> /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
> proc on /proc type proc (rw)
> sysfs on /sys type sysfs (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> /dev/hda1 on /boot type ext3 (rw)
> tmpfs on /dev/shm type tmpfs (rw)
> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> nfsd on /proc/fs/nfsd type nfsd (rw)
> //10.102.192.101/sowmya/secondaryhyperv on /mnt/64538137909171.1c876101 type cifs (rw,mand)
> //10.102.192.101/sowmya/secondaryhyperv on /mnt/64538137909171.10333ac9 type cifs (rw,mand)
> //10.102.192.101/sowmya/secondaryhyperv on /mnt/64538137909171.3f64ab1b type cifs (rw,mand)
> //10.102.192.101/sowmya/secondaryhyperv on /mnt/64538137909171.302d837e type cifs (rw,mand)
> //10.102.192.101/sowmya/secondaryhyperv on /mnt/64538137909171.33ef7f2c type cifs (rw,mand)
> //10.102.192.101/sowmya/secondaryhyperv on /mnt/64538137909171.47f1b0e5 type cifs (rw,mand)
> [root@localhost ~]#
> mysql> select * from image_store\G
> *************************** 1. row ***************************
> id: 1
> name: secondary
> image_provider_name: NFS
> protocol: cifs
> url: cifs://10.102.192.101/sowmya/secondaryhyperv?user=sowmya&password=XXXX&domain=BLR
> data_center_id: 1
> scope: ZONE
> role: Image
> uuid: 17efa163-1c1a-4e60-ab16-c4a0bf683836
> parent: ee32aadd-b9ec-32a4-8242-9b1c7cb5ccf4
> created: 2013-11-13 10:49:42
> removed: NULL
> total_size: NULL
> used_bytes: NULL
> 1 row in set (0.00 sec)
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)