libvirt/tests/storagevolxml2xmlin/vol-file.xml

<volume>
  <name>sparse.img</name>
  <source/>
  <capacity unit="TiB">1</capacity>
  <allocation unit="bytes">0</allocation>
  <target>
    <path>/var/lib/libvirt/images/sparse.img</path>
    <permissions>
      <mode>0</mode>
      <owner>0744</owner>
      <group>0</group>
      <label>virt_image_t</label>
    </permissions>
    <timestamps>
      <atime>1341933637.273190990</atime>
      <mtime>1341930622.047245868</mtime>
      <ctime>1341930622.047245868</ctime>
    </timestamps>
  </target>
</volume>
tests: Add storage volume XML 2 XML tests. 2009-10-09 14:17:21 -04:00			`<volume>`
			`<name>sparse.img</name>`
			`<source/>`
storage: support more scaling suffixes Disk manufacturers are fond of quoting sizes in powers of 10, rather than powers of 2 (after all, 2.1 GB sounds larger than 2.0 GiB, even though the exact opposite is true). So, we might as well follow coreutils' lead in supporting three types of suffix: single letter ${u} (which we already had) and ${u}iB for the power of 2, and ${u}B for power of 10. Additionally, it is impossible to create a file with more than 2*63 bytes, since off_t is signed (if you have enough storage to even create one 8EiB file, I'm jealous). This now reports failure up front rather than down the road when the kernel finally refuses an impossible size. docs/schemas/basictypes.rng (unit): Add suffixes. * src/conf/storage_conf.c (virStorageSize): Use new function. * docs/formatstorage.html.in: Document it. * tests/storagevolxml2xmlin/vol-file-backing.xml: Test it. * tests/storagevolxml2xmlin/vol-file.xml: Likewise. 2012-03-05 14:06:33 -07:00			`<capacity unit="TiB">1</capacity>`
			`<allocation unit="bytes">0</allocation>`
tests: Add storage volume XML 2 XML tests. 2009-10-09 14:17:21 -04:00			`<target>`
			`<path>/var/lib/libvirt/images/sparse.img</path>`
			`<permissions>`
			`<mode>0</mode>`
			`<owner>0744</owner>`
			`<group>0</group>`
			`<label>virt_image_t</label>`
			`</permissions>`
Added timestamps to storage volumes The access, birth, modification and change times are added to storage volumes and corresponding xml representations. This shows up in the XML in this format: <timestamps> <atime>1341933637.027319099</atime> <mtime>1341933637.027319099</mtime> </timestamps> Signed-off-by: Eric Blake <eblake@redhat.com> 2012-07-25 09:43:37 +02:00			`<timestamps>`
			`<atime>1341933637.273190990</atime>`
			`<mtime>1341930622.047245868</mtime>`
			`<ctime>1341930622.047245868</ctime>`
			`</timestamps>`
tests: Add storage volume XML 2 XML tests. 2009-10-09 14:17:21 -04:00			`</target>`
			`</volume>`