Hosted Engine Setup with the gluster bricks on the same disk as the OS
Hi. I am trying to follow this guide. Is it possible to use part of my OS disk /dev/sda for the bricks? https://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-4-1-and-gluster... I am using oVirt Node 4.1.1.1. I am aware of the manual partitioning requirements. I am guessing I have to create an LV for the OS that does not take up the entire disk during install, manually create a pv like /dev/sda3 afterwards, and then run Hosted Engine Setup and specify /sda3 rather than sdb? Thanks, -Mike
On 05/07/2017 04:48 PM, Mike DePaulo wrote:
Hi. I am trying to follow this guide. Is it possible to use part of my OS disk /dev/sda for the bricks? https://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-4-1-and-gluster...
I am using oVirt Node 4.1.1.1. I am aware of the manual partitioning requirements. I am guessing I have to create an LV for the OS that does not take up the entire disk during install, manually create a pv like /dev/sda3 afterwards, and then run Hosted Engine Setup and specify /sda3 rather than sdb?
Thanks, -Mike _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Mike, If you create gluster bricks on the same disk as OS it works but we do not recommend setting up gluster bricks on the same disk as the os. When user tries to create a gluster volume using by specifying the bricks from root partition it displays an error message "Bricks in root parition not recommended and use force at the end to create volume". Thanks kasturi
On Mon, May 8, 2017 at 9:00 AM, knarra <knarra@redhat.com> wrote:
On 05/07/2017 04:48 PM, Mike DePaulo wrote:
Hi. I am trying to follow this guide. Is it possible to use part of my OS disk /dev/sda for the bricks?
https://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-4-1-and-gluster...
I am using oVirt Node 4.1.1.1. I am aware of the manual partitioning requirements. I am guessing I have to create an LV for the OS that does not take up the entire disk during install, manually create a pv like /dev/sda3 afterwards, and then run Hosted Engine Setup and specify /sda3 rather than sdb?
Thanks, -Mike _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Mike,
If you create gluster bricks on the same disk as OS it works but we do not recommend setting up gluster bricks on the same disk as the os. When user tries to create a gluster volume using by specifying the bricks from root partition it displays an error message "Bricks in root parition not recommended and use force at the end to create volume".
Thanks
kasturi
Thank you very much. Is my process for doing this (listed in my original email) correct though? -Mike
Well, I tried both of the following: 1. Having only a boot partition and a PV for the OS that does not take up the entire disk, and then specifying "sda" in Hosted Engine Setup. 2. Having not only a boot partition and a PV for the OS, but also an empty (and not formatted) /dev/sda3 PV that I created with fdisk. Then, specfying "sda3" in Hosted Engine Setup. Both attempts resulted in errors like this: failed: [centerpoint.ad.depaulo.org] (item=/dev/sda3) => {"failed": true, "failed_when_result": true, "item": "/dev/sda3", "msg": " Device /dev/sda3 not found (or ignored by filtering).\n", "rc": 5} It seems like having gluster bricks on the same disk as the OS doesn't work at all. I am going to buy separate OS SSDs. -Mike On Tue, May 9, 2017 at 6:22 AM, Mike DePaulo <mikedep333@gmail.com> wrote:
On Mon, May 8, 2017 at 9:00 AM, knarra <knarra@redhat.com> wrote:
On 05/07/2017 04:48 PM, Mike DePaulo wrote:
Hi. I am trying to follow this guide. Is it possible to use part of my OS disk /dev/sda for the bricks?
https://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-4-1-and-gluster...
I am using oVirt Node 4.1.1.1. I am aware of the manual partitioning requirements. I am guessing I have to create an LV for the OS that does not take up the entire disk during install, manually create a pv like /dev/sda3 afterwards, and then run Hosted Engine Setup and specify /sda3 rather than sdb?
Thanks, -Mike _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Mike,
If you create gluster bricks on the same disk as OS it works but we do not recommend setting up gluster bricks on the same disk as the os. When user tries to create a gluster volume using by specifying the bricks from root partition it displays an error message "Bricks in root parition not recommended and use force at the end to create volume".
Thanks
kasturi
Thank you very much. Is my process for doing this (listed in my original email) correct though?
-Mike
On Thu, May 18, 2017 at 3:20 PM, Mike DePaulo <mikedep333@gmail.com> wrote:
Well, I tried both of the following: 1. Having only a boot partition and a PV for the OS that does not take up the entire disk, and then specifying "sda" in Hosted Engine Setup. 2. Having not only a boot partition and a PV for the OS, but also an empty (and not formatted) /dev/sda3 PV that I created with fdisk. Then, specfying "sda3" in Hosted Engine Setup.
Both attempts resulted in errors like this: failed: [centerpoint.ad.depaulo.org] (item=/dev/sda3) => {"failed": true, "failed_when_result": true, "item": "/dev/sda3", "msg": " Device /dev/sda3 not found (or ignored by filtering).\n", "rc": 5}
Can you provide gdeploy logs? I think, it's at ~/.gdeploy/gdeploy.log
It seems like having gluster bricks on the same disk as the OS doesn't work at all.
I am going to buy separate OS SSDs.
-Mike
On Tue, May 9, 2017 at 6:22 AM, Mike DePaulo <mikedep333@gmail.com> wrote:
On Mon, May 8, 2017 at 9:00 AM, knarra <knarra@redhat.com> wrote:
On 05/07/2017 04:48 PM, Mike DePaulo wrote:
Hi. I am trying to follow this guide. Is it possible to use part of my OS disk /dev/sda for the bricks?
ovirt-4-1-and-gluster-storage/
I am using oVirt Node 4.1.1.1. I am aware of the manual partitioning requirements. I am guessing I have to create an LV for the OS that does not take up the entire disk during install, manually create a pv like /dev/sda3 afterwards, and then run Hosted Engine Setup and specify /sda3 rather than sdb?
Thanks, -Mike _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Mike,
If you create gluster bricks on the same disk as OS it works but we do not recommend setting up gluster bricks on the same disk as the os. When user tries to create a gluster volume using by specifying the bricks from root partition it displays an error message "Bricks in root parition not recommended and use force at the end to create volume".
Thanks
kasturi
Thank you very much. Is my process for doing this (listed in my original email) correct though?
-Mike
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi, On Thu, May 18, 2017 at 7:08 PM, Sahina Bose <sabose@redhat.com> wrote:
On Thu, May 18, 2017 at 3:20 PM, Mike DePaulo <mikedep333@gmail.com> wrote:
Well, I tried both of the following: 1. Having only a boot partition and a PV for the OS that does not take up the entire disk, and then specifying "sda" in Hosted Engine Setup. 2. Having not only a boot partition and a PV for the OS, but also an empty (and not formatted) /dev/sda3 PV that I created with fdisk. Then, specfying "sda3" in Hosted Engine Setup.
Both attempts resulted in errors like this: failed: [centerpoint.ad.depaulo.org] (item=/dev/sda3) => {"failed": true, "failed_when_result": true, "item": "/dev/sda3", "msg": " Device /dev/sda3 not found (or ignored by filtering).\n", "rc": 5}
Can you provide gdeploy logs? I think, it's at ~/.gdeploy/gdeploy.log
It seems like having gluster bricks on the same disk as the OS doesn't work at all.
Hi, /dev/sda3 should work, the error here is possibly due to filesystem signature. Can you please set wipefs=yes? For example [pv] action=create wipefs=yes devices=/dev/sda3 -sac
On Thu, May 18, 2017 at 10:03 AM, Sachidananda URS <surs@redhat.com> wrote:
Hi,
On Thu, May 18, 2017 at 7:08 PM, Sahina Bose <sabose@redhat.com> wrote:
On Thu, May 18, 2017 at 3:20 PM, Mike DePaulo <mikedep333@gmail.com> wrote:
Well, I tried both of the following: 1. Having only a boot partition and a PV for the OS that does not take up the entire disk, and then specifying "sda" in Hosted Engine Setup. 2. Having not only a boot partition and a PV for the OS, but also an empty (and not formatted) /dev/sda3 PV that I created with fdisk. Then, specfying "sda3" in Hosted Engine Setup.
Both attempts resulted in errors like this: failed: [centerpoint.ad.depaulo.org] (item=/dev/sda3) => {"failed": true, "failed_when_result": true, "item": "/dev/sda3", "msg": " Device /dev/sda3 not found (or ignored by filtering).\n", "rc": 5}
Can you provide gdeploy logs? I think, it's at ~/.gdeploy/gdeploy.log
It seems like having gluster bricks on the same disk as the OS doesn't work at all.
Hi, /dev/sda3 should work, the error here is possibly due to filesystem signature.
Can you please set wipefs=yes? For example
[pv] action=create wipefs=yes devices=/dev/sda3
-sac
Sorry for the long delay. This worked. Thank you very much. -Mike
participants (4)
-
knarra -
Mike DePaulo -
Sachidananda URS -
Sahina Bose