BRRABill's Field Report With XenServer
-
-
Yes, as @Danp said, there is always a pool: a "single" host is by default in a pool with no name label.
XenCenter choose to hide this, not us.
-
-
Converted my first physical server to a production XS this morning.
So far, so good.
-
Question:
On the new production server, it is not reporting the space taken by my new VM.
This is what is says:
Total: 871.8 GiB
Currently used: 5.2 GiB
Available: 866.5 GiBBut for example the new VM I migrated over has at least 100GB.
Why would it not be reporting this?
-
-
Thin provisioning?
-
-
you have to refresh. Refresh doesn't happen automatically.
-
@Dashrender said:
you have to refresh. Refresh doesn't happen automatically.
Ah.
What is this? 1973?
-
@BRRABill said:
@Dashrender said:
you have to refresh. Refresh doesn't happen automatically.
Ah.
What is this? 1973?
I kinda asked/thought the same thing. Having to manually fresh, or relaunch the application just seems odd.
-
@Dashrender said:
I kinda asked/thought the same thing. Having to manually fresh, or relaunch the application just seems
oddOLD.FTFY
-
Did refreshing it solve the problem?
-
Yep.
Rescan is actually the word they use.
What does that do exactly, I wonder?
-
@Dashrender said:
Did refreshing it solve the problem?
Did you ever do this through XC?
I could not find the option there.
-
Am I clear... the issue is that XO only refreshes the data as to drive sizes on a page refresh?
-
@scottalanmiller said:
Am I clear... the issue is that XO only refreshes the data as to drive sizes on a page refresh?
No you have to click the "rescan" button or it never does it. At least that is what I am seeing.
-
-
@BRRABill said:
@scottalanmiller said:
Am I clear... the issue is that XO only refreshes the data as to drive sizes on a page refresh?
No you have to click the "rescan" button or it never does it. At least that is what I am seeing.
Ah okay, my guess is because they don't want to incur a storage penalty without everyone being clear that they are about to query the storage. In a small lab with local storage this seems silly, but if this was a massive environment with tons of heavily used remote storage, might be something that you want to carefully control. What if you had a hundred admins with XO open all of the time and a thousand nodes on it with gobs of shared storage all updating automatically... suddenly what seems like a trivial hit becomes crippling.
-
@scottalanmiller said:
@BRRABill said:
@scottalanmiller said:
Am I clear... the issue is that XO only refreshes the data as to drive sizes on a page refresh?
No you have to click the "rescan" button or it never does it. At least that is what I am seeing.
Ah okay, my guess is because they don't want to incur a storage penalty without everyone being clear that they are about to query the storage. In a small lab with local storage this seems silly, but if this was a massive environment with tons of heavily used remote storage, might be something that you want to carefully control. What if you had a hundred admins with XO open all of the time and a thousand nodes on it with gobs of shared storage all updating automatically... suddenly what seems like a trivial hit becomes crippling.
And, again, in a larger environment, seeing storage space in the GUI here is not really the proper way to manage it, correct?