----- Original Message -----
From: "santosh" <sbahir@commvault.com> To: users@ovirt.org Sent: Friday, July 25, 2014 8:34:35 PM Subject: [ovirt-users] RHEV - Hypervisor directory structure.
Hi,
I am trying to understand the directory structure on the RHEV hypervisor. Below is the part of the directory tree on hypervisor.
root@XYZ dom_md] tree /rhev/data-center/51a24440-6a1f-48f0-8306-92455fe7aaa1/mastersd/
/rhev/data-center/51a24440-6a1f-48f0-8306-92455fe7aaa1/mastersd/ ├── dom_md │ ├── ids -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/ids │ ├── inbox -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/inbox │ ├── leases -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/leases │ ├── master -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/master │ ├── metadata -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/metadata │ └── outbox -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/outbox ├── images │ ├── 7f0be608-0251-4125-a3a1-b4e74bbcaa34 │ │ └── 53596e07-0317-43b3-838a-13cde56ce1c8 -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/53596e07-0317-43b3-838a-13cde56ce1c8 │ ├── aa6b4787-271f-4651-98c8-97054ff4418d │ │ ├── 22961431-c139-4311-bc78-c4f5a58cfda7 -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/22961431-c139-4311-bc78-c4f5a58cfda7 │ │ └── f5f5f1ff-af71-4d11-a15a-dbc863e5d6f7 -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/f5f5f1ff-af71-4d11-a15a-dbc863e5d6f7 │ └── e4f70c9e-c5b3-4cbe-a755-684d6a86026f │ └── 8c2f5f05-c109-45e7-af98-c54437ad5d9e -> /dev/f86ee04c-d84d-4032-a3f8-c77ed1ad29ea/8c2f5f05-c109-45e7-af98-c54437ad5d9e └── master ├── lost+found ├── tasks └── vms ├── 1ba7645c-79db-403a-95f6-b3078e441b86 │ └── 1ba7645c-79db-403a-95f6-b3078e441b86.ovf └── 6df2c080-a0d5-4202-8f09-ed719184f667 └── 6df2c080-a0d5-4202-8f09-ed719184f667.ovf
I am trying to understand the ids, inbox, leases, master, metadata and outbox device files above.
ids - used by sanlock - each host maintain a lockspace on each domain, allowing it to acquire resources on the leases volume. leases - used for acquiring resources. For example, the spm node acquire a resource on this volume inbox - every host can write message to the spm node using this volume outbox - the spm write messages to other hosts on this volume master - this volume is mounted on the spm node for storing stuff related to the master storage domain metadata - used to store storage domain metadata On block storage, these volumes are lvs. On file storage, these ares files. For more info on inbox and outbox, see: http://www.ovirt.org/File:Storage-mailbox.odp Nir