Thank you very much.
What about "direct lun" usage and database example?
2017-06-08 16:40 GMT+02:00 Elad Ben Aharon <ebena...@redhat.com>:
> Answer inline
> On Thu, Jun 8, 2017 at 1:07 PM, Stefano Bovina <bov...@gmail.com> wrote:
does a storage best practise document for oVirt exist?
oVirt allows to extend an existing storage domain: Is it better to keep a
1:1 relation between LUN and oVirt storage domain?
If not, is it better to avoid adding LUNs to an already existing storage
:128 active ready running
2017-05-13 18:50 GMT+02:00 Juan Pablo <pablo.localh...@gmail.com>:
> can you please give the output of:
> multipath -ll
> iscsiadm -m session -P3
> 2017-05-13 6:48 GMT-03:00 Stefano Bovina <bov...@gmail.com>:
multipath, with a dedicated raid group and ioping don't report latency.
2017-05-13 2:00 GMT+02:00 Juan Pablo <pablo.localh...@gmail.com>:
> sorry to jump in, but what kernel version are you using? had similar issue
> with kernel 4.10/4.11
> 2017-05-12 16:36 GMT-03:0
2017-05-08 11:56 GMT+02:00 Yaniv Kaul <yk...@redhat.com>:
> On Mon, May 8, 2017 at 11:50 AM, Stefano Bovina <bov...@gmail.com> wrote:
>> this configuration is the one suggested by EMC for EL7.
it should be fine.
2017-05-08 9:39 GMT+02:00 Yaniv Kaul <yk...@redhat.com>:
> On Sun, May 7, 2017 at 1:27 PM, Stefano Bovina <bov...@gmail.com> wrote:
>> Sense data are 0x0/0x0/0x0
> Interesting - first time I'm seeing 0/0/0. The 1st is usually 0x2 (see
Ok, ignore what I said regards step 2. The volume exists.
2017-05-07 20:27 GMT+02:00 Stefano Bovina <bov...@gmail.com>:
> What do you need exactly? Shutdown VM, edit disk, "extend size by" --->
> storage domain is up and runn
2017-05-07 8:36 GMT+02:00 Yaniv Kaul <yk...@redhat.com>:
> On Tue, May 2, 2017 at 11:09 PM, Stefa
Hi, while trying to update a VM disk, a failure was returned (forcing me to
add a new disk)
Any advice on how to resolve this error?
Hi, the engine logs show high latency on storage domains: "Storage domain
experienced a high latency of 19.2814 seconds from .. This may
cause performance and functional issues."
Looking at host logs, I found also these locking errors:
2017-05-02 20:52:13+0200 33883 : s1 renewal
Mail list logo