Dear All,
A combination of options fixed this:
yum downgrade ovirt-node-ng-image-update
lvremove /dev/<mapper>/<erroneous install>.0
lvremove /dev/<mapper>/<erroneous install>.0+1
lvremove /dev/<mapper>/var_crash
fstrim -av
reboot
Next time the yum update ovirt-node-ng-image-update works.
Thanks all for your help!
Regards,
Callum
--
Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. callum@well.ox.ac.uk<mailto:callum@well.ox.ac.uk>
On 18 Jul 2018, at 07:07, Oliver Riesener
<Oliver.Riesener@hs-bremen.de<mailto:Oliver.Riesener@hs-bremen.de>> wrote:
Hi Callum,
your LVM thin pool seams to be full.
Try to trim it with: fstrin -av.
Am 12.07.2018 um 13:13 schrieb Callum Smith
<callum@well.ox.ac.uk<mailto:callum@well.ox.ac.uk>>:
'lvcreate', '--thin', '--virtualsize', u'349121282048B',
'--name', 'ovirt-node-ng-4.2.4-0.20180626.0',
u'onn_virta003/pool00']'