[Users] Recommended file system?

Any recommended file system to use to hold VM disk images? EXT4? BTRFS(disable COW I assume?)? ZFS? XFS?

This is a multi-part message in MIME format. ------=_NextPartTM-000-229cc3d0-88f1-4502-b081-81ba3e78b3cb Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > Von: users-bounces@ovirt.org [users-bounces@ovirt.org]" im Auftrag v= on "Blaster [blaster@556nato.com]=0A= > Gesendet: Mittwoch, 18. Dezember 2013 06:24=0A= > An: users@ovirt.org=0A= > Betreff: [Users] Recommended file system?=0A= > =0A= > Any recommended file system to use to hold VM disk images? EXT4? BTRFS(d= isable COW I assume?)? ZFS? XFS?=0A= =0A= Hello,=0A= =0A= from my point of view I would say do it as you like =0A= and use the filesystem you are comfortable with.=0A= Maybe to aspects that should be mentioned. =0A= =0A= 1) We use a custom build Ubuntu NFS Server with XFS. =0A= When we evaluated PROXMOX we noticed timeouts =0A= during creation of QCOW2 images. The simple solution=0A= was to change allocsize setting from some "insane high=0A= in internet found recommendation" to 16M. So if your=0A= VM writes a block into a empty disk area you only =0A= allocate the surrounding 16M.=0A= =0A= 2) COW of BTRFS could be a good idea especially if you =0A= go with RAID5/6. Even using Hardware RAID. Lets=0A= assume you have a lot of VMs. All of them writing some=0A= kind of data somewhere onto the disks. If each piece is=0A= to small for a full stripe write you run into a read modify=0A= write cycle. Consuming much more IOs. With COW=0A= all this data may be written into one continuous block.=0A= (Netapp sometimes shows quite high write ops, because=0A= their WAFL works similar).=0A= =0A= Markus=0A= =0A= ------=_NextPartTM-000-229cc3d0-88f1-4502-b081-81ba3e78b3cb Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-229cc3d0-88f1-4502-b081-81ba3e78b3cb--

On 12/18/2013 12:24 AM, Blaster wrote:
Any recommended file system to use to hold VM disk images? EXT4? BTRFS(disable COW I assume?)? ZFS? XFS?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
is this for local storage, or as the backend of an NFS server?

On 12/18/2013 3:09 AM, Itamar Heim wrote:
On 12/18/2013 12:24 AM, Blaster wrote:
Any recommended file system to use to hold VM disk images? EXT4? BTRFS(disable COW I assume?)? ZFS? XFS?
is this for local storage, or as the backend of an NFS server?
Well, my original intent was local...But I'd be curious about NFS as well. (and why would it be different?)

On 12/18/2013 11:22 PM, Blaster wrote:
On 12/18/2013 3:09 AM, Itamar Heim wrote:
On 12/18/2013 12:24 AM, Blaster wrote:
Any recommended file system to use to hold VM disk images? EXT4? BTRFS(disable COW I assume?)? ZFS? XFS?
is this for local storage, or as the backend of an NFS server?
Well, my original intent was local...But I'd be curious about NFS as well. (and why would it be different?)
well, while ovirt can manage VMs on a host in a "local data center", its more powerful when you have shared storage, and can put multiple hosts in the cluster, live migrate VMs between them,e tc.

On 12/19/2013 1:18 AM, Itamar Heim wrote:
well, while ovirt can manage VMs on a host in a "local data center", its more powerful when you have shared storage, and can put multiple hosts in the cluster, live migrate VMs between them,e tc.
Right, but reliable and fast shared storage is a bit expensive for a home lab..Even gig-E isn't all that fast compared to local SATA. Popping out disks and moving them to a new machine isn't that big of a deal...Under ESXi it's just "Add to inventory" and move on...This is more complicated under ovirt, but I don't do it that often, so it's not extremely inconvenient.
participants (4)
-
Blaster
-
Blaster
-
Itamar Heim
-
Markus Stockhausen