Displaying 4 results from an estimated 4 matches for "48ef".
Did you mean:
48e3
2018 Jan 17
1
Gluster endless heal
...tion without actually healing anything.
The bricks are all SSDs, and the logs of the source node is spamming with the following messages;
[2018-01-17 18:37:11.815247] I [MSGID: 108026] [afr-self-heal-common.c:1254:afr_log_selfheal] 0-ovirt_imgs-replicate-0: Completed data selfheal on 450fb07a-e95d-48ef-a229-48917557c278. sources=[0] sinks=1
[2018-01-17 18:37:12.830887] I [MSGID: 108026] [afr-self-heal-metadata.c:51:__afr_selfheal_metadata_do] 0-ovirt_imgs-replicate-0: performing metadata selfheal on ce0f545d-635a-40c0-95eb-ccfc71971f78
[2018-01-17 18:37:12.845978] I [MSGID: 108026] [afr-self-hea...
2016 Feb 11
0
Schema extension for Exchange and WERR_DS_DRA_SCHEMA_MISMATCH
...req_options)
File "/usr/local/samba/lib64/python2.7/site-packages/samba/drs_utils.py", line 83, in sendDsReplicaSync
raise drsException("DsReplicaSync failed %s" % estr)
# samba-tool drs replicate dc02 dc01 dc=company3,dc=dd
Start replicating for source GUID ae22e205-5f46-48ef-b165-27df4468843b.
Replicate from dc01 to dc02 was successful.
Also Schema replication looks like works fine:
# samba-tool drs replicate dc02 dc01 cn=Schema,cn=Configuration,dc=company3,dc=dd
Start replicating for source GUID ae22e205-5f46-48ef-b165-27df4468843b.
Replicate from dc01 to dc02 was s...
2020 Feb 14
1
[PATCH 2/3] PCI: Add DMA configuration for virtual platforms
...e is not just conceptually wrong
but actually broken, so the concept here worries me a bit. In a world
where of_iommu_configure() and friends are being called much earlier
around iommu_probe_device() time, how badly will this fall apart?
Robin.
[1]
https://lore.kernel.org/linux-iommu/9625faf4-48ef-2dd3-d82f-931d9cf26976 at huawei.com/
> Signed-off-by: Jean-Philippe Brucker <jean-philippe at linaro.org>
> ---
> drivers/pci/pci-driver.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index 0454c...
2020 Feb 14
5
[PATCH 0/3] virtio-iommu on non-devicetree platforms
Add topology description to the virtio-iommu driver and enable x86
platforms. Since the RFC [1] I've mostly given up on ACPI tables, since
the internal discussions seem to have reached a dead end. The built-in
topology description presented here isn't ideal, but it is simple to
implement and doesn't impose a dependency on ACPI or device-tree, which
can be beneficial to lightweight