After I seen the talk about VDO:
https://www.youtube.com/watch?v=7CGr5LEAfRY
I went ahead and tried it.
I tried it on small (12GB) sample of Copr data and I saved 20-30% data.
I then deployed it on production server retrace.fedoraproject.org and saved there 15% out of 2TB.
Several notes: The RPM packages are only available for RHEL. Recently the public github has been updated with version of
VDO, which should work on Fedora. No RPM available for Fedora yet though.
Here are my notes:
# vdo create --name=vdo1 --device=/dev/vdb --vdoLogicalSize=1T
# mkfs.ext4 /dev/mapper/vdo1
Some slides suggest to use -E discard. This is not needed for new volumes. See vdo-devel mailing list for reasoning.
# mount -o discard /dev/mapper/vdo1 /mnt/a
Probably best scenario is to create vdo on whole disk and then make PV from whole VDO disk and put LVM on top of that.
When you already have data, you cannot convert your disk to VDO. You need create new VDO disk, format it, mount it and
copy the data.
In my case, due limited space for migration I created a small LVM volume "vdosrv":
# lvcreate -L 80G -n vdosrv vol0
I converted it to VDO which claims to have 2TB of vitual total size
# vdo create --name=srv18 --device=/dev/vol0/vdosrv --vdoLogicalSize=2T
# mkfs.ext4 /dev/mapper/srv18
See how many space is *actually* free.
# vdostats
# mkdir /mnt/srv18
# mount -o discard /dev/mapper/srv18 /mnt/srv18
Now I moved some data from old volume to /mnt/srv18. I shrank the FS of old volume, I shrank the old LV. And then I
enlarged the new LV.
# lvresize -L +400G /dev/vol0/vdosrv
and let know vdo that it can use the new space:
# vdo growPhysical -n srv18
I repeated this several times.
I have to say that my experience is so far good.
I hope that my notes help someone.
Miroslav
Hi,
When clicking the "Login" button on the src.fedoraproject.org, I see
the following error. Is it expected behavior?
https://src.fedoraproject.org/
```
500 - Internal Server Error
The Fedora Accounts Ipsilon encountered an unexpected internal error
while trying to fulfill your request.
Please retry again.
If the error persists, contact Fedora Infra to resolve the problem.
```
--
Jun | He/Him | Timezone: UTC+1 or +2
Hi folks,
A quick fyi that F40 will go EOL tomorrow, May 13 2025. Bugzillas opened
against this version have already received warning message that this date
was approaching ~2 weeks ago, so this is just another heads up that after
tomorrow, all open bugs against F40 will be automatically closed.
If you are still running on F40, we recommend you upgrade[1].
Kind regards,
Aoife
[1]
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-releas…
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney