anchor.diff:  metadata:
     labels:
       machineconfiguration.openshift.io/role: worker
  -  name: 98-var-log-partition
  +  name: 98-var-partition
   spec:
     config:
       ignition:
         version: 3.1.0
       storage:
         disks:
  -      - device: /dev/nvme0n1
  -        wipeTable: false
  +      - device: /dev/<device_name> <1>
           partitions:
  -        - sizeMiB: 47000
  -          startMiB: 47000
  -          label: var-log
  +        - sizeMiB: <partition_size>
  +          startMiB: <partition_start_offset> <2>
  +          label: var
         filesystems:
  -        - path: /var/log
  -          device: /dev/disk/by-partlabel/var-log
  +        - path: /var
  +          device: /dev/disk/by-partlabel/var
             format: xfs
       systemd:
         units:
  -        - name: var-log.mount
  +        - name: var.mount
             enabled: true
             contents: |
               [Unit]
               Before=local-fs.target
               [Mount]
  -            Where=/var/log
  -            What=/dev/disk/by-partlabel/var-log
  +            Where=/var
  +            What=/dev/disk/by-partlabel/var
               [Install]
               WantedBy=local-fs.target
   ----
  ++
  +<1> The storage device name of the disk that you want to partition.
  +<2> When adding a data partition to the boot disk, a minimum value of 25000 mebibytes is recommended. The root filesystem is automatically resized to fill all available space up to the specified offset. If no value is specified, or if the specified value is smaller than the recommended minimum, the resulting root filesystem will be too small, and future reinstalls of {op-system} might overwrite the beginning of the data partition.
   
   . Run `openshift-install` again to create Ignition configs from a set of files in the `manifest` and
   `openshift` subdirectories:
  
positive.code: auth  bootstrap.ign  master.ign  metadata.json  worker.ign
  ----
  
  At this point, you can use the Ignition config files as input to the ISO or PXE bare
  metal installation procedures to install {op-system-first} systems.
  
  [id="installation-user-infra-machines-advanced_retaindisk_{context}"]
  === Retaining existing partitions
  For an ISO installation, you can add options to the `coreos-installer`
  that causes the installer to maintain one or more existing partitions.
  For a PXE installation, you can APPEND coreos.inst options to preserve partitions.
  
  Saved partitions might be partitions from an existing {product-title}
  system that has data partitions that you want to keep or partitions
  that you just manually created. Here are a few tips:
  
  * Make sure you assign at least the recommended amount of disk space to the
  
negative.code: 
  For an ISO installation:
  
  The following example illustrates running `coreos-installer` in a way that preserves
  the sixth (6) partition on the disk:
  
  [source,terminal]
  