I maintain MariaDB.
There is a subpackage containing TokuDB storage engine. (available only for
However the TokuDB can't be build against Jemalloc 5, but on F>=28 there is
no older jemalloc version.
The build without jemalloc is not supported too.
Is it OK to drop the subpackage on F28 and later until the upstream adds
the Jemalloc 5 support?
I'm ready to drop such update to Bodhi.
Here's a bugzilla for this issue:
So far, on F>=28 the TokuDB was build without jemalloc.
It may be risky to rely on, yet no one complained.
That's why I'm asking users mailing list too, to get a feedback for such
pontential users, i would be otherwise unable to reach.
Associate Software Engineer
Core Services - Databases Team
On 29-04-18 09:25, Hans de Goede wrote:
> Hi All,
> I'm sending this to the fedora-kernel and -devel lists
> both to get the kernel team aware of this and because it
> is not entirely clear to me how to best deal with this.
> I guess we should get this added to the release-notes /
> common-bugs page for F28, but I'm not sure what the
> procedure is for that ?
> I've just become aware that at least for some users
> the use of SATA LPM in F28 causes the Lenovo 50
> series laptops (confirmed X250, T450s G50-80) freeze/
> hang hard under certain conditions when using SATA
> LPM, independent of the disk used (*).
> This is currently being tracked in:
> A known workaround is to add: "ahci.mobile_lpm_policy=0"
> to the kernel boot command line.
> Can someone help me to get this documented? Once we've
> figured out what is going on I hope to be able to fix this
> with a kernel update, but people may still need the
> workaround to install Fedora 28.
> Also if people are using Fedora 28 on a 50 series Lenovo
> laptop without issues, please let me know.
Some more info on this, the user with a x250 is reporting
the problem is hard-freeze about once a day, which goes
away when disabling LPM, so if you have a 50 series Lenovo
laptop and are seeing the occasional hard-freeze this may
be the cause.
(sorry if this gets posted twice; previous attempt was sent from wrong
address and will hopefully bounce anyway)
Thrift in rawhide is currently 0.10.0. My intention is move to Thrift
0.11.0 in rawhide.
Affected packages seem to be:
accumulo (ctubbsii, mizdebsk, milleruntime)
avro (ricardo, gil, lef)
golang-opencensus (eclipseo, nim, jchaloup)
hive (orphan, pmackinn, coolsvap, moceap)
python-elasticsearch (dbruno, apevec, piotrp)
For work reasons, I need a Fedora 28 VM. I've got a bunch of disk space
set aside to create logical volumes (LVM) for exactly this purpose, with
several existing VMs. On this occasion, I decided that I no longer needed
an older Fedora VM and decided to recycle it. I got the Fedora 28 x86_64
Workstation ISO image, set that as the boot CD in virt-manager, and fired
it up. I told it to install to disk and immediately ran into these
(apparently duplicate bugs):
Okay, so I zeroed out the partition table inside the logical volume and
tried again. The installer pegged the CPU at 100% and stayed there. Okay,
so maybe that LV is damaged beyond repair. I created a new one out of the
unused space in the VG and tried again. Same result. CPU pegged at 100%,
installer completely unresponsive.
Does anybody have any tips on creating a VM with storage in an LV on a
Fedora 28 host? The above procedure worked just fine in F26 and F27, by