Revision 620a85fd man/gnt-node.sgml
| b/man/gnt-node.sgml | ||
|---|---|---|
| 794 | 794 |
<para> |
| 795 | 795 |
The <option>--storage-type</option> option can be used to choose a |
| 796 | 796 |
storage unit type. Possible choices are <literal>lvm-pv</literal>, |
| 797 |
<literal>lvm-vg</literal> or <literal>file</literal>. Depending on the |
|
| 798 |
storage type, the available output fields change. |
|
| 797 |
<literal>lvm-vg</literal> or <literal>file</literal>. |
|
| 799 | 798 |
</para> |
| 800 | 799 |
|
| 801 | 800 |
<para> |
| ... | ... | |
| 809 | 808 |
</listitem> |
| 810 | 809 |
</varlistentry> |
| 811 | 810 |
<varlistentry> |
| 811 |
<term>type</term> |
|
| 812 |
<listitem> |
|
| 813 |
<simpara>the type of the storage unit (currently just |
|
| 814 |
what is passed in via |
|
| 815 |
<option>--storage-type</option>)</simpara> |
|
| 816 |
</listitem> |
|
| 817 |
</varlistentry> |
|
| 818 |
<varlistentry> |
|
| 812 | 819 |
<term>name</term> |
| 813 | 820 |
<listitem> |
| 814 |
<simpara>the physical drive name</simpara>
|
|
| 821 |
<simpara>the path/identifier of the storage unit</simpara>
|
|
| 815 | 822 |
</listitem> |
| 816 | 823 |
</varlistentry> |
| 817 | 824 |
<varlistentry> |
| 818 | 825 |
<term>size</term> |
| 819 | 826 |
<listitem> |
| 820 | 827 |
<simpara> |
| 821 |
the physical drive size |
|
| 822 |
(<literal>lvm-pv</literal> and <literal>lvm-vg</literal> only) |
|
| 828 |
total size of the unit; for the file type see a note below |
|
| 823 | 829 |
</simpara> |
| 824 | 830 |
</listitem> |
| 825 | 831 |
</varlistentry> |
| ... | ... | |
| 827 | 833 |
<term>used</term> |
| 828 | 834 |
<listitem> |
| 829 | 835 |
<simpara> |
| 830 |
used disk space |
|
| 831 |
(<literal>lvm-pv</literal> and <literal>file</literal> only) |
|
| 836 |
used space in the unit; for the file type see a note below |
|
| 832 | 837 |
</simpara> |
| 833 | 838 |
</listitem> |
| 834 | 839 |
</varlistentry> |
| ... | ... | |
| 837 | 842 |
<listitem> |
| 838 | 843 |
<simpara> |
| 839 | 844 |
available disk space |
| 840 |
(<literal>lvm-pv</literal> and <literal>file</literal> only) |
|
| 841 | 845 |
</simpara> |
| 842 | 846 |
</listitem> |
| 843 | 847 |
</varlistentry> |
| ... | ... | |
| 845 | 849 |
<term>allocatable</term> |
| 846 | 850 |
<listitem> |
| 847 | 851 |
<simpara> |
| 848 |
whether physical volume is allocatable |
|
| 849 |
(<literal>lvm-pv</literal> only) |
|
| 852 |
whether we the unit is available for allocation |
|
| 853 |
(only <literal>lvm-pv</literal> can change this |
|
| 854 |
setting, the other types always report true) |
|
| 850 | 855 |
</simpara> |
| 851 | 856 |
</listitem> |
| 852 | 857 |
</varlistentry> |
| ... | ... | |
| 854 | 859 |
</para> |
| 855 | 860 |
|
| 856 | 861 |
<para> |
| 862 |
Note that for the <quote>file</quote> type, the total disk |
|
| 863 |
space might not equal to the sum of used and free, due to the |
|
| 864 |
method Ganeti uses to compute each of them. The total and free |
|
| 865 |
values are computed as the total and free space values for the |
|
| 866 |
filesystem to which the directory belongs, but the used space |
|
| 867 |
is computed from the used space under that directory |
|
| 868 |
<emphasis>only</emphasis>, which might not be necessarily the |
|
| 869 |
root of the filesystem, and as such there could be files |
|
| 870 |
outside the file storage directory using disk space and |
|
| 871 |
causing a mismatch in the values. |
|
| 872 |
</para> |
|
| 873 |
|
|
| 874 |
<para> |
|
| 857 | 875 |
Example: |
| 858 | 876 |
<screen> |
| 859 |
# gnt-node list-storage node5.example.com
|
|
| 860 |
Node Name Size Used Free
|
|
| 861 |
node5.example.com /dev/sda7 673.8G 0M 673.8G
|
|
| 862 |
node5.example.com /dev/sdb1 698.6G 1.3G 697.4G
|
|
| 877 |
node1# gnt-node list-storage node2
|
|
| 878 |
Node Type Name Size Used Free Allocatable
|
|
| 879 |
node2 lvm-pv /dev/sda7 673.8G 1.5G 672.3G Y
|
|
| 880 |
node2 lvm-pv /dev/sdb1 698.6G 0M 698.6G Y
|
|
| 863 | 881 |
</screen> |
| 864 | 882 |
</para> |
| 865 | 883 |
</refsect2> |
Also available in: Unified diff