/
) must be on an LVM
(Logical Volume Manager) or Btrfs
volume. To use the fs-snapshot plug-in on an LVM volume, take the following steps:
vgdisplay
command in the following form as root
:
vgdisplay
volume_group
Free PE / Size
line.
root
, run the pvcreate
command in the following form to initialize a physical volume for use with the Logical Volume Manager:
pvcreate
device
vgextend
command in the following form as root
to add the physical volume to the volume group:
vgextend
volume_group physical_volume
/etc/yum/pluginconf.d/fs-snapshot.conf
, and make the following changes to the [lvm]
section:
enabled
option to 1
:
enabled = 1
#
) from the beginning of the lvcreate_size_args
line, and adjust the number of logical extents to be allocated for a snapshot. For example, to allocate 80 % of the size of the original logical volume, use:
lvcreate_size_args = -l 80%ORIGIN
fs-snapshot.conf
directives” for a complete list of available configuration options.
yum
command, and make sure fs-snapshot is included in the list of loaded plug-ins (the Loaded plugins
line) before you confirm the changes and proceed with the transaction. The fs-snapshot plug-in displays a line in the following form for each affected logical volume:
fs-snapshot: snapshotting file_system (/dev/volume_group/logical_volume): logical_volume_yum_timestamp
lvremove
command as root
:
lvremove
/dev/volume_group/logical_volume_yum_timestamp
root
, run the command in the following form to merge a snapshot into its original logical volume:
lvconvert
--merge
/dev/volume_group/logical_volume_yum_timestamp
lvconvert
command will inform you that a restart is required in order for the changes to take effect.
root
:
reboot
yum
command, and make sure fs-snapshot is included in the list of loaded plug-ins (the Loaded plugins
line) before you confirm the changes and proceed with the transaction. The fs-snapshot plug-in displays a line in the following form for each affected file system:
fs-snapshot: snapshotting file_system: file_system/yum_timestamp
root
:
btrfs
subvolume
delete
file_system/yum_timestamp
root
:
btrfs
subvolume
list
file_system
root
, configure the system to mount this snapshot by default:
btrfs
subvolume
set-default
id file_system
root
:
reboot
Table 5.3. Supported fs-snapshot.conf
directives
Section | Directive | Description |
---|---|---|
[main] | enabled =value | Allows you to enable or disable the plug-in. The value must be either 1 (enabled), or 0 (disabled). When installed, the plug-in is enabled by default. |
exclude =list | Allows you to exclude certain file systems. The value must be a space-separated list of mount points you do not want to snapshot (for example, /srv /mnt/backup ). This option is not included in the configuration file by default. | |
[lvm] | enabled =value | Allows you to enable or disable the use of the plug-in on LVM volumes. The value must be either 1 (enabled), or 0 (disabled). This option is disabled by default. |
lvcreate_size_args =value | Allows you to specify the size of a logical volume snapshot. The value must be the -l or -L command line option for the lvcreate utility followed by a valid argument (for example, -l 80%ORIGIN ). |
yum
is run. The refresh-packagekit plug-in is installed by default.
RHN Classic
. This allows systems registered with RHN Classic
to update and install packages from this system.
yum
with a set of highly-useful security-related commands, subcommands and options.
~]# yum check-update --security
Loaded plugins: langpacks, presto, refresh-packagekit, security
Limiting package lists to security relevant ones
updates-testing/updateinfo | 329 kB 00:00
9 package(s) needed for security, out of 270 available
ConsoleKit.x86_64 0.4.5-1.fc15 updates
ConsoleKit-libs.x86_64 0.4.5-1.fc15 updates
ConsoleKit-x11.x86_64 0.4.5-1.fc15 updates
NetworkManager.x86_64 1:0.8.999-2.git20110509.fc15 updates
NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
[output truncated]
yum update --security
or yum update-minimal --security
to update those packages which are affected by security advisories. Both of these commands update all packages on the system for which a security advisory has been issued. yum update-minimal --security
updates them to the latest packages which were released as part of a security advisory, while yum update --security
will update all packages affected by a security advisory to the latest version of that package available.
yum update-minimal --security
will update you to kernel-2.6.38.6-22, and yum update --security
will update you to kernel-2.6.38.6-26. Conservative system administrators may want to use update-minimal
to reduce the risk incurred by updating packages as much as possible.
yum
.