[one-users] system datastores always have no space
Marius Rex
MariusRex at venda.com
Fri May 9 06:43:27 PDT 2014
The system DS is not supposed to show up with any space until a host is
configured? That is a surprising because the pre-configured sandbox
instance I downloaded first for testing (a Virtualbox instance) has
space listed in the system DS even though that has no hosts connected to
it.
In any case, there are no hosts connected to the test instance that I
gave the example on, but on some other instances which I have configured
elsewhere do have hosts configured and they have the same problem. I
have /var/lib/one as a NFS mount that is mounted on both the frontend
and the node. That instance comes up with no space in the system DS as
well.
Here is some output from that showing the system DS with no space even
though the logs say the node is successfully monitored:
http://pastebin.com/w6Wg909Y
-Marius
mariusrex at venda.com
On Fri, 2014-05-09 at 05:05 -0400, Carlos Martín Sánchez wrote:
> Hi,
>
>
> System DS are monitored with the host probes. Do you have any hosts
> configured?
>
> --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula
>
>
> On Fri, May 9, 2014 at 12:02 AM, Marius Rex <MariusRex at venda.com>
> wrote:
> Platform: Centos 6.5
> versions: opennebula-4.5.80 and opennebula-4.6.0-1
>
> I have been struggling with this for a while with various
> configurations
> and I continually run into the same problem.
>
> I cannot build out a VM as the system volumes always come up
> with no
> space. I have been trying to reduce variables and now at a
> very basic
> setup: I installed a fresh Centos 6 server and pulled down the
> latest
> stable opennebula RPMs from the official repo. I am just
> using local
> file systems for everything, and have done nothing beyond
> installing the
> RPM and starting opennebula. My system volume comes up with
> no
> available room, seemingly no matter what I do.
>
>
> [oneadmin at trainging ~]$ onedatastore
> list
> ID NAME SIZE AVAIL CLUSTER IMAGES TYPE
> DS
> TM
> 0 system 0M - - 0 sys -
> shared
> 1 default 6.6G 77% - 0 img
> fs
> shared
> 2 files 6.6G 77% - 0 fil
> fs
> ssh
>
>
>
> [oneadmin at trainging ~]$ onedatastore show 0
> DATASTORE 0
> INFORMATION
> ID :
> 0
> NAME :
> system
> USER : oneadmin
> GROUP : oneadmin
> CLUSTER : -
> TYPE : SYSTEM
> DS_MAD : -
> TM_MAD : shared
> BASE PATH : /var/lib/one//datastores/0
> DISK_TYPE : FILE
>
> DATASTORE
> CAPACITY
> TOTAL: : 0M
> FREE: : 0M
> USED: : 0M
> LIMIT: : -
>
> PERMISSIONS
> OWNER : um-
> GROUP : u--
> OTHER : ---
>
> DATASTORE
> TEMPLATE
> BASE_PATH="/var/lib/one//datastores/"
> SHARED="YES"
> TM_MAD="shared"
> TYPE="SYSTEM_DS"
>
> IMAGES
>
> It is the same filesystem the other volumes are on, yet they
> have
> available space. I have tried two different versions of
> OpenNebula. I
> have tried different base filesystems. I have tried custom
> RPMs. It
> comes up the same every time.
>
> Is there a bug or am I missing something very obvious?
>
>
> --
> Marius Rex
> mariusrex at venda.com
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
More information about the Users
mailing list