Changes between Version 32 and Version 33 of Doc/BasicConfig/AII

Timestamp:

Aug 20, 2009, 6:31:21 PM (15 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Doc/BasicConfig/AII

@@ -60 +60 @@
 
 Some useful hints helping to maitain `DISK_VOLUME_PARAMS`:
- *  There is no need to explicitly declare charatacteristics of  disk partitions or logical volumes. This is why you will not see entry for them in the examples. If an entry is using a disk partition (eg. a file system) and has a size attribute defined, a block device corresponding to the declared size will be created. If the partition number is greater or equal to 5, an extended partition will automatically be added as the fourth partition on the device. The same applies to LVM logical volumes but a file system using a logical volume is required to have an attribute `volgroup` defined.
+ *  There is no need to explicitly declare charatacteristics of  disk partitions or logical volumes. This is why you will not see entry for them in the examples. If an entry is using a disk partition (eg. a file system) and has a size attribute defined, a block device corresponding to the declared size will be created. If the partition number is greater or equal to 5, an extended partition will automatically be added as the fourth partition on the device. This is true in particular for file systems and software raid 1 (md) devices.The same applies to LVM logical volumes but a file system using a logical volume is required to have an attribute `volgroup` defined.
  * A special value for the size attribute is -1. This means you want to use all the remaining unused space in the underlying block device (eg. partition or logical volume). The file system [source:templates/trunk/standard/filesystem/config.tpl configuration template] will ensure that this entry is created last in the underlying block device and that there is not 2 entries with a size of -1 in the same block device.