VDO - Revision history

Michael.mast at 18:42, 18 October 2020

2020-10-18T18:42:05Z

Michael.mast: /* Encryption with LUKS */

2020-10-15T21:40:54Z

Encryption with LUKS

Michael.mast: /* Purpose */

2020-10-15T21:35:49Z

Purpose

Michael.mast: /* Encryption with LUKS */

2020-10-15T20:34:18Z

Encryption with LUKS

Michael.mast: /* Encryption with LUKS */

2020-10-15T20:28:30Z

Encryption with LUKS

Michael.mast at 20:28, 15 October 2020

2020-10-15T20:28:15Z

Michael.mast: Created page with "==Purpose== General notes on using VDO https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo-ig-administering-vdo..."

2020-06-02T14:57:03Z

Created page with "==Purpose== General notes on using VDO <ref>https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo-ig-administering-vdo..."

New page

==Purpose==
General notes on using VDO
<ref>https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo-ig-administering-vdo</ref>
==Grow Logical VDO Size==
I have a SAMBA share used to mirror a directory from another server. This was intended to test VDO. The problem is that the kernel reports the disk is now full, but the physical usage is no where near full.
*Size of the disk.
<pre>
sudo lsblk /dev/nvme2n1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme2n1 259:3 0 300G 0 disk
└─datafeed 253:0 0 295.4G 0 vdo /mnt/data
</pre>
*Here I am told the mount point is full.
<pre>
sudo df -hT /dev/mapper/datafeed
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/datafeed xfs 296G 296G 160K 100% /mnt/data
</pre>
*But when checking vdo stats, we see it very much empty
<pre>
sudo vdostats --human-readable
Device Size Used Available Use% Space saving%
/dev/mapper/datafeed 300.0G 80.3G 219.7G 26% 74%
</pre>
*Now I grow the logical volume size
<pre>
sudo vdo growLogical --name=datafeed --vdoLogicalSize=500G
sudo lsblk /dev/nvme2n1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme2n1 259:3 0 300G 0 disk
└─datafeed 253:0 0 500G 0 vdo /mnt/data
</pre>
*Grow XFS and check changes
<pre>
sudo xfs_growfs /dev/mapper/datafeed
.........
sudo df -hT /dev/mapper/datafeed
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/datafeed xfs 500G 296G 205G 60% /mnt/data
</pre>

@@ Line 3: / Line 3: @@
 <ref>https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo-ig-administering-vdo</ref>
 <ref>https://blog.delouw.ch/2018/12/17/using-data-deduplication-and-compression-with-vdo-on-rhel-7-and-8/</ref>
 ==Encryption with LUKS==

@@ Line 57: / Line 57: @@
 Writing superblocks and filesystem accounting information: done
 </pre>
 ==Grow Logical VDO Size==

@@ Line 33: / Line 33: @@
 Starting compression on VDO backup_vdo
 VDO instance 0 volume is ready at /dev/mapper/backup_vdo
 </pre>

@@ Line 19: / Line 19: @@
 Verify passphrase:
-</pre
+</pre>
 *Open the encrypted volume, and setup VDO.
 <pre>
@@ Line 35: / Line 35: @@
 </pre>
 ==Grow Logical VDO Size==
 I have a SAMBA share used to mirror a directory from another server. This was intended to test VDO. The problem is that the kernel reports the disk is now full, but the physical usage is no where near full.