Hi,
Is there a lock file on the Export Domain which stops it being mounted to a
2nd instance of oVirt? We have a replicated Export Domain in a separate
location that we would like to mount to a backup instance of oVirt for DR
purposes.
Thanks in advance.
Nick
On Tue, Dec 12, 2017 at 8:32 AM, Rajat Patel wrote:
> Hi Ovirt,
>
> We are using Ovirt 4.1 selfhosted engine attach nfs storega as
> data/iso/export, we have one image which we want to import
> (manageiq-ovirt-fine-4.qc2). We did copy to our export location
>
Hi Ovirt,
We are using Ovirt 4.1 selfhosted engine attach nfs storega as
data/iso/export, we have one image which we want to import
(manageiq-ovirt-fine-4.qc2). We did copy to our export location
(/export/3157c57b-8f6a-4709-862a-713bfa59899a) and chnage the owner ship to
(chown -R 36:36
Hi,
Our NFS storage domain is stored as a LUN, and served via a NFS server.
I have to change this NFS server, but I don't need to change the LUN.
After setting this NFS export domain in maintenance and detached, is it
safe to just update the database table storage_server_connections and
Le 16/04/2014 11:35, Nicolas Ecarnot a écrit :
Hi,
Our NFS storage domain is stored as a LUN, and served via a NFS server.
I have to change this NFS server, but I don't need to change the LUN.
After setting this NFS export domain in maintenance and detached, is it
safe to just update the
- Original Message -
From: Nicholas Kesick cybertimber2...@hotmail.com
To: oVirt Mailing List users@ovirt.org
Sent: Wednesday, September 25, 2013 8:43:47 PM
Subject: [Users] Export Domain Upgrade
This is the first time I've run through an 'upgrade', so I'm very new to
export
] Export Domain Upgrade
This is the first time I've run through an 'upgrade', so I'm very
new to export domains, and I'm having some trouble getting one
connected to 3.3. I had hoped to add this to the wiki, but it hasn't
been as straightforward as I thought.
On my oVirt 3.2
Date: Mon, 30 Sep 2013 00:33:08 +0300
From: ih...@redhat.com
To: ofren...@redhat.com
CC: cybertimber2...@hotmail.com; users@ovirt.org
Subject: Re: [Users] Export Domain Upgrade
On 09/29/2013 12:15 PM, Omer Frenkel wrote
Message -
From: Nicolas Ecarnot nico...@ecarnot.net
To: users users@ovirt.org
Sent: Tuesday, April 16, 2013 1:18:40 PM
Subject: [Users] Export domain was working... then... NFS, rpc.statd issues
Hi,
[oVirt 3.1, F17]
My good old NFS export domain was OK, but getting too small for our needs
Hi,
[oVirt 3.1, F17]
My good old NFS export domain was OK, but getting too small for our needs.
Then I unmounted it, created another bigger one somewhere else, and
tried to mount the new one.
Long things short, the NFS is not mounted and the relevant error is here:
On 03/14/2013 05:55 PM, Shu Ming wrote:
Dafna Ron:
ovirt should not react in any way :)
the size should be updated by queries that are sent to vdsm on domains
status.
I think vdsm domains do have their own meta-data except the lvm or
posix file system meta data.
the export domain is an NFS
On 03/14/2013 05:55 PM, Shu Ming wrote:
Dafna Ron:
ovirt should not react in any way :)
the size should be updated by queries that are sent to vdsm on domains
status.
I think vdsm domains do have their own meta-data except the lvm or posix
file system meta data.
iirc, the MD no longer cares
ovirt should not react in any way :)
the size should be updated by queries that are sent to vdsm on domains
status.
If you want to be extra careful you can always put the export domain in
maintenance before the extend :)
On 03/13/2013 09:45 PM, Jonathan Horne wrote:
What would happen if the
Dafna Ron:
ovirt should not react in any way :)
the size should be updated by queries that are sent to vdsm on domains
status.
I think vdsm domains do have their own meta-data except the lvm or posix
file system meta data.
If you want to be extra careful you can always put the export domain
So you have a block device in NFS server to be extended from 200 to
50GB?I think you should extend both the block device and the file
system on the block device in the server side. To oVirt, it doesn't
save the size in storage domain' meta-data and I believe the size is
only stored in
What would happen if the export domain (via NFS) was extended (say, while the
server was doing a reboot?) id like to extend the space of my export domain
from 200 to 500GB (with lvm commands).
How will ovirt react to finding the size of the export domain changed? Pleased
or unpleased?
Hi,
Thanks for your input, comments inline.
- Original Message -
From: Dead Horse deadhorseconsult...@gmail.com
To: Eli Mesika emes...@redhat.com
Cc: users users@ovirt.org
Sent: Thursday, November 8, 2012 5:47:26 AM
Subject: Re: [Users] export domain issues with latest nightly/GIT
- Original Message -
From: Dead Horse deadhorseconsult...@gmail.com
To: users@ovirt.org users@ovirt.org
Sent: Wednesday, November 7, 2012 3:12:07 AM
Subject: [Users] export domain issues with latest nightly/GIT Master
I have noted some export domain issues with builds from
classify
this as a regression.
On Wed, Nov 7, 2012 at 2:59 AM, Eli Mesika emes...@redhat.com wrote:
- Original Message -
From: Dead Horse deadhorseconsult...@gmail.com
To: users@ovirt.org users@ovirt.org
Sent: Wednesday, November 7, 2012 3:12:07 AM
Subject: [Users] export domain
I have noted some export domain issues with builds from the latest GIT
Master.
1) When importing a VM, the disks subtab of the VM to import will not show
the disks. Instead it shows the blinking progress squares. This is
persistent and will it will not show information on the disks to be
20 matches
Mail list logo