Automate Snapshots
All,
My boss has asked me to automate Hyper-V Snapshots. I know this is not a built in feature of Hyper-V or SCVMM (which we are using)... I have seen some powershell scripts to do this, but I would like to stay away from scripts. Can anybody help me with this project with any suggesstions/guidance? I believe Microsoft should have added this feature to begin with!
Thanks!
Hey Floris!!
i did like ur post said, but now my sistem is doing one snapshot per minute.
I have used the command: powershell.exe -File "Path\To\SnapShotMgmt.ps1" -ExecutionPolicy Unrestricted
How can i delete or disable this task?? Im looking on Task Scheduler and i cant locate it.
Im using Windows Server 2012!!
Thanks!!
Similar Messages
-
Hi all, we are running are OWB design repository on Unix. We want to setup a cron job that will log into the oracle database and take a snapshot of the project for us every other night or so.
Anyone offhand know a SQLPLus command that will take a snapshot of a project? Or any easy way to do this
ThanksYou should use the OWB's scripting language to do this. It allows you the access to most of the features available through UI. Please refer to the scripting guide for this (http://download.oracle.com/docs/html/B12152_01/toc.htm). Also take a look at the scripting introduction/examples:
http://otn.oracle.com/products/warehouse/sdk/Scripting%20Pages/Scripting_home.htm
You will particularly be interested in the OMBCREATE SNAPSHOT command:
OMBCREATE SNAPSHOT 'SS1' SET PROPERTIES (DESCRIPTION, TYPE) VALUES ('Complete snapshot', 'FULL') ADD TABLE '/PROJECT1/MODULE_WH1/ORDERS'
Regards:
Igor -
Automatic Snapshot File Deletion
Would like to know how to delete snapshot files created during a “push subscription”.
The current path for these are: D:\mssqldata\MSSQL.1\MSSQL\repldata\unc\SQLSERVER_TEST_DB_TEST_DB\2013122700…, 2013122800….
In the replication setup wizard, did not see any options to set the file retention.
Is there a way this can be accomplished without manual intervention.
Any suggestions or recommendations would be greatly appreciated.
Thank you in advance.Where is that located? It's not listed under "SQL Server Agent -> Jobs".
Hello,
The Replication maintenance jobs are created after configure a replication. The jobs should be listed under SQL Server Agent Jobs folder. Please try to click the refresh button of the Jobs folder to check where the jobs are
created successfully.
Reference:How to: Run Replication Maintenance Jobs (SQL Server Management Studio)
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support -
How to enable snapshot-schedule in Soalris 10
Hi,
I have installed Solaris 10 with ZFS as root file system.
In the same ref. I would like to enable the automatic snapshot schedule rpool.
While checking I found GUI option only to do the same, can any one help me out to enable the above option with command line.
Thanks in advance.
Note: I do not have GUI access of the server.
Thanks
RajanHi,
What about using cron?
To snapshot everyday at 19:00 all zfs under zones_pool, we just add these lines in crontab:
00 19 * * 1 /usr/sbin/zfs destroy -r zones_pool@monday_19:00;/usr/sbin/zfs snapshot -r zones_pool@monday_19:00
00 19 * * 2 /usr/sbin/zfs destroy -r zones_pool@tuesday_19:00;/usr/sbin/zfs snapshot -r zones_pool@tuesday_19:00
00 19 * * 3 /usr/sbin/zfs destroy -r zones_pool@wednesday_19:00;/usr/sbin/zfs snapshot -r zones_pool@wednesday_19:00
00 19 * * 4 /usr/sbin/zfs destroy -r zones_pool@thursday_19:00;/usr/sbin/zfs snapshot -r zones_pool@thursday_19:00
00 19 * * 5 /usr/sbin/zfs destroy -r zones_pool@friday_19:00;/usr/sbin/zfs snapshot -r zones_pool@friday_19:00
Marco -
Hiii..
Im having a oracle apps 11.5.10.2 and Database 10.2.0.4 on a Windows 2003 server.
When i try to run awrrpt.sql it is not showing any snapshots for the day, i think automatic snapshots are not getting created.
The following is the scrshot when i run awrrpt.sql script
SQL> @awrrpt.sql
Current Instance
*~~~~~~~~~~~~~~~~*
DB Id DB Name Inst Num Instance
*101806506 PROD 1 prod*
Specify the Report Type
*~~~~~~~~~~~~~~~~~~~~~~~*
Would you like an HTML report, or a plain text report?
Enter 'html' for an HTML report, or 'text' for plain text
Defaults to 'html'
Enter value for report_type: html
Type Specified: html
Instances in this Workload Repository schema
*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~*
DB Id Inst Num DB Name Instance Host
** 101806506 1 PROD prod DIWAF-PRD-ER*
PDB
** 101806506 1 PROD prod DIWERPDB01*
*94285532 1 PROD prod DIWERPDB01*
Using 101806506 for database Id
Using 1 for instance number
Specify the number of days of snapshots to choose from
*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~*
Entering the number of days (n) will result in the most recent
*(n) days of snapshots being listed. Pressing <return> without*
specifying a number lists all completed snapshots.
Enter value for num_days: 1
Listing the last day's Completed Snapshots
Specify the Begin and End Snapshot Ids
*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~*
Enter value for begin_snap:
What could be the problem can anyone help me in solving this issue.
Thanks in advanceHi;
Why you dont enable EM and check it from there?
Also see:
5.3.1 Managing Snapshots
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/autostat.htm#i26958
http://www.rampant-books.com/t_oracle_awr_statspack_manual_command.htm
Regard
Helios -
Is there any way to automate snapshots for multiple images.
I am a travel and event photographer and it is not unusual for me to have 100+ final images from a job. Remembering to save a snapshot of each image while I am editing is time consuming and frequently forgotten. When I have the complete shoot finished and have done a quick review to make sure the set is finished I would like to select all and create a date and time based a snapshot each image in the whole set. If there is no way to automate this can it be put on a wish list for a future update?
JimHello John,
Thanks for the reply. There are many reasons I would like a dated snapshot of the final edit of a group of images. I have a love hate relationship with Lightroom (mostly on the love side). Non destructive editing wonderful, however if you are not careful it is also quite easy to accidently lose all your work through a set of edits or reset. I work in dng to preserve my edits without having to track the side car. Unfortunately I have had a number of instances where my edits were not saved in the dng. In addition, I would like to have a way to do collections of different effects applied to full sets that I can go back to.
I am located in Germany and teach introduction to digital photography at the Stuttgart Media University. I would use this function regularly for illustration purposes.
My thought was that not only would it be nice to have an easy way to identify (by date) the final edit to each image in a set but with this automation, I would also be able to do an edit reset by running automation that set each image in the set (similar to sync) according to the name of the snapshot.
Is there a technical reason that a snapshot of the most recent edits cannot be automated. Anything that can be done with a single action or combination of defined actions can be automated. Do you know if there are plans for definable Automate > batch functionality for lightroom similar to that in Photoshop?
One last question, are the same John McWilliams affiliated with the Atlanta Photography Group.
Jim -
ISCSI Target Scheduled Snapshots
I know there are cmdlets to snapshot a target but is there a built in way to schedule snapshots?
Alternatively, is there a cmdlet to list snapshots for a target so I can create a script to run on a schedule to remove old snapshots and create new ones.I know there are cmdlets to snapshot a target but is there a built in way to schedule snapshots?
Alternatively, is there a cmdlet to list snapshots for a target so I can create a script to run on a schedule to remove old snapshots and create new ones.
Yes, you can use Schedule Snapshot Wizard to have automatic snapshots. See:
Creating and Managing Snapshots
and Schedules
http://technet.microsoft.com/en-us/library/gg232620(v=ws.10).aspx
Creating
and Scheduling Snapshots of Virtual Disks
http://technet.microsoft.com/en-us/library/gg232610(v=ws.10).aspx
Alternatively you can use cmdlets to deal with these tasks (PowerShell would give you more control over
creation / deletion of a snapshots. See:
iSCSI Target Cmdlets in Windows PowerShell
http://technet.microsoft.com/en-us/library/jj612803.aspx
The ones should be of your interest are Checkpoint-IscsiVirtualDisk and Remove-IscsiVirtualDiskSnapshot cmdlets.
Also you may use SMI-S and WMI if you want to use say C# or C++ and not PowerShell.
Some more of the cmdlets use links (including samples). See:
PowerShell
cmdlets for the Microsoft iSCSI Target 3.3 (included in Windows Storage Server 2008 R2)
http://blogs.technet.com/b/josebda/archive/2010/09/29/powershell-cmdlets-for-the-microsoft-iscsi-target-3-3-included-in-windows-storage-server-2008-r2.aspx
(that's for Windows Server 2008 R2 and up)
Managing
iSCSI Target Server through Storage Cmdlets
http://blogs.technet.com/b/filecab/archive/2013/09/28/managing-iscsi-target-server-through-storage-cmdlets.aspx
(the most recent one about Windows Server 2012 R2)
Hope this helped a bit. Good luck :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts. -
What is "autodelete_base" snapshot on aggr0 and how to disable it?
Hello colleagues,could anybody explain what is purpose of "autodelete_base" snapshot in aggr0 and how to remove it permanently?As I noticed, snap_autodelete is permanently turn ON in DOT 8.2.x 7mode. And only way, how to disable this snapshot is to set aggr snap reserve to 0.Is there any other solution? I noticed those only on single systems, HA pairs, but not on metrocluster gateway filer with syncmirror aggregates. Thanks in advance for feedback. RegardsPetr Jaros
The purpose of “Autodelete_base” is : If Aggregate snapshot autodelete is leaving you with no snapshots, the storage system will automatically create a snapshot called autodelete_base at the aggregate level when a snapshot is removed as a result of autodeletion. This ensures that there is always a new snapshot in the aggregate after a snapshot is deleted.If aggregate snapshots are enabled and there is not adequate space reserved for these snapshots, a situation may develop where a very large aggregate snapshot is created. This may occur if large volumes are deleted.If SyncMirror triggers an aggregate level snapshot and there is not enough space for two snapshots, the existing snapshot is deleted by the autodeletion feature and instantly replaced by the autodelete_base snapshot. However, there is still not enough space for the SyncMirror triggered snapshot. This will cause a loop of autodeletion which can only be interrupted by manually deleting the autodelete_base snapshot.StepsDisable automatic aggregate Snapshot copy creation by entering the following command:aggr options aggr_name nosnap onaggr_name is the name of the aggregate for which you want to disable automatic Snapshot copy creation.Delete all Snapshot copies in the aggregate by entering the following command:snap delete -A -a aggr_nameSet the aggregate Snapshot reserve to 0 percent by entering the following command:snap reserve -A aggr_name 0
-
Hello,
I'm having an issue deleting a file from my home directory.
This the file I want to delete .shapshot. It looks like it is shapshoting my files in my home directory. Anyway how do I stop these snapshots?
This is the command I used.
rm -rf /home/cyberninja/.snapshot
ls -la /home/cyberninja/
drwxrwxrwx 10 root root 4096 mar 8 12:00 .snapshot
ls -la /home/cyberninja/.snapshot
drwxr-x--- 26 cyberninja users 8192 Mar 6 14:17 hourly.0
drwxr-x--- 26 cyberninja users 8192 Mar 6 14:17 hourly.1
drwxr-x--- 26 cyberninja users 8192 Mar 6 14:17 hourly.2
drwxr-x--- 26 cyberninja users 8192 Mar 6 14:17 hourly.3
drwxr-x--- 26 cyberninja users 8192 Mar 6 14:17 hourly.4
drwxr-x--- 26 cyberninja users 8192 Mar 6 14:17 hourly.5
drwxr-x--- 26 cyberninja users 8192 Mar 6 14:17 nightly.0
drwxr-x--- 26 cyberninja users 8192 Mar 6 14:17 nightly.1If I remove the file as root it just comes back. Can someone point me in the right direction?
Edited by: CyberNinja on Mar 8, 2012 9:40 AMHi Ninja,
.snapshot isn't a file, it is a directory. Is this a Solaris 10 release?
The .snapshot directory is generally used for ongoing snapshots or automatic
snapshots. The contents of your .snapshot directory look like automatic snapshots
to me, where you have hourly.* and nightly.* directories for those hourly and nightly
snapshots.
If you want to remove the contents of the .snapshot directory, you can, but you
need to disable whatever is creating these snapshots if you don't want them.
Thanks,
Cindy -
LVM Volumes not available after update
Hi All!
I haven't updated my system for about two months and today I updated it. Now I have the problem that I cannot boot properly. I have my root partition in an LVM volume and on boot I get the message
ERROR: device 'UUID=xxx' not found. Skipping fs
ERROR: Unable to find root device 'UUID=xxx'
After that I land in the recovery shell. After some research I found, that "lvm lvdisplay" showed that my volumes where not available and I had to reenable them with "lvm vgchange -a y".
Issuing any lvm command also produced the following warning:
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
Anyway, after issuing the commands and exiting the recovery shell, the system booted again. However, I would prefer being able to boot without manual actions.
Thanks in advance!
Further information:
vgdisplay
--- Volume group ---
VG Name ArchLVM
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 232.69 GiB
PE Size 4.00 MiB
Total PE 59568
Alloc PE / Size 59568 / 232.69 GiB
Free PE / Size 0 / 0
VG UUID SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5
lvdisplay (LV Status was 'not available' right after booting)
--- Logical volume ---
LV Path /dev/ArchLVM/Swap
LV Name Swap
VG Name ArchLVM
LV UUID XRYBrz-LojR-k6SD-XIxV-wHnY-f3VG-giKL6V
LV Write Access read/write
LV Creation host, time archiso, 2014-05-16 14:43:06 +0200
LV Status available
# open 0
LV Size 8.00 GiB
Current LE 2048
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Path /dev/ArchLVM/Root
LV Name Root
VG Name ArchLVM
LV UUID lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv
LV Write Access read/write
LV Creation host, time archiso, 2014-05-16 14:43:27 +0200
LV Status available
# open 1
LV Size 224.69 GiB
Current LE 57520
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
/etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/ArchLVM-Root
UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 / ext4 rw,relatime,data=ordered 0 1
#/dev/mapper/ArchLVM-Root / ext4 rw,relatime,data=ordered 0 1
# /dev/sda1
UUID=72691888-a781-4cdd-a98e-2613d87925d0 /boot ext2 rw,relatime 0 2
/etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
/boot/grub/grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod lvm
insmod ext2
set root='lvmid/SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5/lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='lvmid/SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5/lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv' 2db82d1a-47a4-4e30-a819-143e8fb75199
else
search --no-floppy --fs-uuid --set=root 2db82d1a-47a4-4e30-a819-143e8fb75199
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2db82d1a-47a4-4e30-a819-143e8fb75199' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
else
search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-2db82d1a-47a4-4e30-a819-143e8fb75199' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-2db82d1a-47a4-4e30-a819-143e8fb75199' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
else
search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-2db82d1a-47a4-4e30-a819-143e8fb75199' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
else
search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Last edited by Kirodema (2014-07-16 07:31:34)use_lvmetad = 0
lvm2-lvmetad is not enabled or running on my system. Shall I activate it?
# This is an example configuration file for the LVM2 system.
# It contains the default settings that would be used if there was no
# /etc/lvm/lvm.conf file.
# Refer to 'man lvm.conf' for further information including the file layout.
# To put this file in a different directory and override /etc/lvm set
# the environment variable LVM_SYSTEM_DIR before running the tools.
# N.B. Take care that each setting only appears once if uncommenting
# example settings in this file.
# This section allows you to set the way the configuration settings are handled.
config {
# If enabled, any LVM2 configuration mismatch is reported.
# This implies checking that the configuration key is understood
# by LVM2 and that the value of the key is of a proper type.
# If disabled, any configuration mismatch is ignored and default
# value is used instead without any warning (a message about the
# configuration key not being found is issued in verbose mode only).
checks = 1
# If enabled, any configuration mismatch aborts the LVM2 process.
abort_on_errors = 0
# Directory where LVM looks for configuration profiles.
profile_dir = "/etc/lvm/profile"
# This section allows you to configure which block devices should
# be used by the LVM system.
devices {
# Where do you want your volume groups to appear ?
dir = "/dev"
# An array of directories that contain the device nodes you wish
# to use with LVM2.
scan = [ "/dev" ]
# If set, the cache of block device nodes with all associated symlinks
# will be constructed out of the existing udev database content.
# This avoids using and opening any inapplicable non-block devices or
# subdirectories found in the device directory. This setting is applied
# to udev-managed device directory only, other directories will be scanned
# fully. LVM2 needs to be compiled with udev support for this setting to
# take effect. N.B. Any device node or symlink not managed by udev in
# udev directory will be ignored with this setting on.
obtain_device_list_from_udev = 1
# If several entries in the scanned directories correspond to the
# same block device and the tools need to display a name for device,
# all the pathnames are matched against each item in the following
# list of regular expressions in turn and the first match is used.
preferred_names = [ ]
# Try to avoid using undescriptive /dev/dm-N names, if present.
# preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath", "^/dev/[hs]d" ]
# A filter that tells LVM2 to only use a restricted set of devices.
# The filter consists of an array of regular expressions. These
# expressions can be delimited by a character of your choice, and
# prefixed with either an 'a' (for accept) or 'r' (for reject).
# The first expression found to match a device name determines if
# the device will be accepted or rejected (ignored). Devices that
# don't match any patterns are accepted.
# Be careful if there there are symbolic links or multiple filesystem
# entries for the same device as each name is checked separately against
# the list of patterns. The effect is that if the first pattern in the
# list to match a name is an 'a' pattern for any of the names, the device
# is accepted; otherwise if the first pattern in the list to match a name
# is an 'r' pattern for any of the names it is rejected; otherwise it is
# accepted.
# Don't have more than one filter line active at once: only one gets used.
# Run vgscan after you change this parameter to ensure that
# the cache file gets regenerated (see below).
# If it doesn't do what you expect, check the output of 'vgscan -vvvv'.
# If lvmetad is used, then see "A note about device filtering while
# lvmetad is used" comment that is attached to global/use_lvmetad setting.
# By default we accept every block device:
filter = [ "a/.*/" ]
# Exclude the cdrom drive
# filter = [ "r|/dev/cdrom|" ]
# When testing I like to work with just loopback devices:
# filter = [ "a/loop/", "r/.*/" ]
# Or maybe all loops and ide drives except hdc:
# filter =[ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
# Use anchors if you want to be really specific
# filter = [ "a|^/dev/hda8$|", "r/.*/" ]
# Since "filter" is often overridden from command line, it is not suitable
# for system-wide device filtering (udev rules, lvmetad). To hide devices
# from LVM-specific udev processing and/or from lvmetad, you need to set
# global_filter. The syntax is the same as for normal "filter"
# above. Devices that fail the global_filter are not even opened by LVM.
# global_filter = []
# The results of the filtering are cached on disk to avoid
# rescanning dud devices (which can take a very long time).
# By default this cache is stored in the /etc/lvm/cache directory
# in a file called '.cache'.
# It is safe to delete the contents: the tools regenerate it.
# (The old setting 'cache' is still respected if neither of
# these new ones is present.)
# N.B. If obtain_device_list_from_udev is set to 1 the list of
# devices is instead obtained from udev and any existing .cache
# file is removed.
cache_dir = "/etc/lvm/cache"
cache_file_prefix = ""
# You can turn off writing this cache file by setting this to 0.
write_cache_state = 1
# Advanced settings.
# List of pairs of additional acceptable block device types found
# in /proc/devices with maximum (non-zero) number of partitions.
# types = [ "fd", 16 ]
# If sysfs is mounted (2.6 kernels) restrict device scanning to
# the block devices it believes are valid.
# 1 enables; 0 disables.
sysfs_scan = 1
# By default, LVM2 will ignore devices used as component paths
# of device-mapper multipath devices.
# 1 enables; 0 disables.
multipath_component_detection = 1
# By default, LVM2 will ignore devices used as components of
# software RAID (md) devices by looking for md superblocks.
# 1 enables; 0 disables.
md_component_detection = 1
# By default, if a PV is placed directly upon an md device, LVM2
# will align its data blocks with the md device's stripe-width.
# 1 enables; 0 disables.
md_chunk_alignment = 1
# Default alignment of the start of a data area in MB. If set to 0,
# a value of 64KB will be used. Set to 1 for 1MiB, 2 for 2MiB, etc.
# default_data_alignment = 1
# By default, the start of a PV's data area will be a multiple of
# the 'minimum_io_size' or 'optimal_io_size' exposed in sysfs.
# - minimum_io_size - the smallest request the device can perform
# w/o incurring a read-modify-write penalty (e.g. MD's chunk size)
# - optimal_io_size - the device's preferred unit of receiving I/O
# (e.g. MD's stripe width)
# minimum_io_size is used if optimal_io_size is undefined (0).
# If md_chunk_alignment is enabled, that detects the optimal_io_size.
# This setting takes precedence over md_chunk_alignment.
# 1 enables; 0 disables.
data_alignment_detection = 1
# Alignment (in KB) of start of data area when creating a new PV.
# md_chunk_alignment and data_alignment_detection are disabled if set.
# Set to 0 for the default alignment (see: data_alignment_default)
# or page size, if larger.
data_alignment = 0
# By default, the start of the PV's aligned data area will be shifted by
# the 'alignment_offset' exposed in sysfs. This offset is often 0 but
# may be non-zero; e.g.: certain 4KB sector drives that compensate for
# windows partitioning will have an alignment_offset of 3584 bytes
# (sector 7 is the lowest aligned logical block, the 4KB sectors start
# at LBA -1, and consequently sector 63 is aligned on a 4KB boundary).
# But note that pvcreate --dataalignmentoffset will skip this detection.
# 1 enables; 0 disables.
data_alignment_offset_detection = 1
# If, while scanning the system for PVs, LVM2 encounters a device-mapper
# device that has its I/O suspended, it waits for it to become accessible.
# Set this to 1 to skip such devices. This should only be needed
# in recovery situations.
ignore_suspended_devices = 0
# ignore_lvm_mirrors: Introduced in version 2.02.104
# This setting determines whether logical volumes of "mirror" segment
# type are scanned for LVM labels. This affects the ability of
# mirrors to be used as physical volumes. If 'ignore_lvm_mirrors'
# is set to '1', it becomes impossible to create volume groups on top
# of mirror logical volumes - i.e. to stack volume groups on mirrors.
# Allowing mirror logical volumes to be scanned (setting the value to '0')
# can potentially cause LVM processes and I/O to the mirror to become
# blocked. This is due to the way that the "mirror" segment type handles
# failures. In order for the hang to manifest itself, an LVM command must
# be run just after a failure and before the automatic LVM repair process
# takes place OR there must be failures in multiple mirrors in the same
# volume group at the same time with write failures occurring moments
# before a scan of the mirror's labels.
# Note that these scanning limitations do not apply to the LVM RAID
# types, like "raid1". The RAID segment types handle failures in a
# different way and are not subject to possible process or I/O blocking.
# It is encouraged that users set 'ignore_lvm_mirrors' to 1 if they
# are using the "mirror" segment type. Users that require volume group
# stacking on mirrored logical volumes should consider using the "raid1"
# segment type. The "raid1" segment type is not available for
# active/active clustered volume groups.
# Set to 1 to disallow stacking and thereby avoid a possible deadlock.
ignore_lvm_mirrors = 1
# During each LVM operation errors received from each device are counted.
# If the counter of a particular device exceeds the limit set here, no
# further I/O is sent to that device for the remainder of the respective
# operation. Setting the parameter to 0 disables the counters altogether.
disable_after_error_count = 0
# Allow use of pvcreate --uuid without requiring --restorefile.
require_restorefile_with_uuid = 1
# Minimum size (in KB) of block devices which can be used as PVs.
# In a clustered environment all nodes must use the same value.
# Any value smaller than 512KB is ignored.
# Ignore devices smaller than 2MB such as floppy drives.
pv_min_size = 2048
# The original built-in setting was 512 up to and including version 2.02.84.
# pv_min_size = 512
# Issue discards to a logical volumes's underlying physical volume(s) when
# the logical volume is no longer using the physical volumes' space (e.g.
# lvremove, lvreduce, etc). Discards inform the storage that a region is
# no longer in use. Storage that supports discards advertise the protocol
# specific way discards should be issued by the kernel (TRIM, UNMAP, or
# WRITE SAME with UNMAP bit set). Not all storage will support or benefit
# from discards but SSDs and thinly provisioned LUNs generally do. If set
# to 1, discards will only be issued if both the storage and kernel provide
# support.
# 1 enables; 0 disables.
issue_discards = 0
# This section allows you to configure the way in which LVM selects
# free space for its Logical Volumes.
allocation {
# When searching for free space to extend an LV, the "cling"
# allocation policy will choose space on the same PVs as the last
# segment of the existing LV. If there is insufficient space and a
# list of tags is defined here, it will check whether any of them are
# attached to the PVs concerned and then seek to match those PV tags
# between existing extents and new extents.
# Use the special tag "@*" as a wildcard to match any PV tag.
# Example: LVs are mirrored between two sites within a single VG.
# PVs are tagged with either @site1 or @site2 to indicate where
# they are situated.
# cling_tag_list = [ "@site1", "@site2" ]
# cling_tag_list = [ "@*" ]
# Changes made in version 2.02.85 extended the reach of the 'cling'
# policies to detect more situations where data can be grouped
# onto the same disks. Set this to 0 to revert to the previous
# algorithm.
maximise_cling = 1
# Whether to use blkid library instead of native LVM2 code to detect
# any existing signatures while creating new Physical Volumes and
# Logical Volumes. LVM2 needs to be compiled with blkid wiping support
# for this setting to take effect.
# LVM2 native detection code is currently able to recognize these signatures:
# - MD device signature
# - swap signature
# - LUKS signature
# To see the list of signatures recognized by blkid, check the output
# of 'blkid -k' command. The blkid can recognize more signatures than
# LVM2 native detection code, but due to this higher number of signatures
# to be recognized, it can take more time to complete the signature scan.
use_blkid_wiping = 1
# Set to 1 to wipe any signatures found on newly-created Logical Volumes
# automatically in addition to zeroing of the first KB on the LV
# (controlled by the -Z/--zero y option).
# The command line option -W/--wipesignatures takes precedence over this
# setting.
# The default is to wipe signatures when zeroing.
wipe_signatures_when_zeroing_new_lvs = 1
# Set to 1 to guarantee that mirror logs will always be placed on
# different PVs from the mirror images. This was the default
# until version 2.02.85.
mirror_logs_require_separate_pvs = 0
# Set to 1 to guarantee that cache_pool metadata will always be
# placed on different PVs from the cache_pool data.
cache_pool_metadata_require_separate_pvs = 0
# Specify the minimal chunk size (in kiB) for cache pool volumes.
# Using a chunk_size that is too large can result in wasteful use of
# the cache, where small reads and writes can cause large sections of
# an LV to be mapped into the cache. However, choosing a chunk_size
# that is too small can result in more overhead trying to manage the
# numerous chunks that become mapped into the cache. The former is
# more of a problem than the latter in most cases, so we default to
# a value that is on the smaller end of the spectrum. Supported values
# range from 32(kiB) to 1048576 in multiples of 32.
# cache_pool_chunk_size = 64
# Set to 1 to guarantee that thin pool metadata will always
# be placed on different PVs from the pool data.
thin_pool_metadata_require_separate_pvs = 0
# Specify chunk size calculation policy for thin pool volumes.
# Possible options are:
# "generic" - if thin_pool_chunk_size is defined, use it.
# Otherwise, calculate the chunk size based on
# estimation and device hints exposed in sysfs:
# the minimum_io_size. The chunk size is always
# at least 64KiB.
# "performance" - if thin_pool_chunk_size is defined, use it.
# Otherwise, calculate the chunk size for
# performance based on device hints exposed in
# sysfs: the optimal_io_size. The chunk size is
# always at least 512KiB.
# thin_pool_chunk_size_policy = "generic"
# Specify the minimal chunk size (in KB) for thin pool volumes.
# Use of the larger chunk size may improve performance for plain
# thin volumes, however using them for snapshot volumes is less efficient,
# as it consumes more space and takes extra time for copying.
# When unset, lvm tries to estimate chunk size starting from 64KB
# Supported values are in range from 64 to 1048576.
# thin_pool_chunk_size = 64
# Specify discards behaviour of the thin pool volume.
# Select one of "ignore", "nopassdown", "passdown"
# thin_pool_discards = "passdown"
# Set to 0, to disable zeroing of thin pool data chunks before their
# first use.
# N.B. zeroing larger thin pool chunk size degrades performance.
# thin_pool_zero = 1
# This section that allows you to configure the nature of the
# information that LVM2 reports.
log {
# Controls the messages sent to stdout or stderr.
# There are three levels of verbosity, 3 being the most verbose.
verbose = 0
# Set to 1 to suppress all non-essential messages from stdout.
# This has the same effect as -qq.
# When this is set, the following commands still produce output:
# dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck, pvdisplay,
# pvs, version, vgcfgrestore -l, vgdisplay, vgs.
# Non-essential messages are shifted from log level 4 to log level 5
# for syslog and lvm2_log_fn purposes.
# Any 'yes' or 'no' questions not overridden by other arguments
# are suppressed and default to 'no'.
silent = 0
# Should we send log messages through syslog?
# 1 is yes; 0 is no.
syslog = 1
# Should we log error and debug messages to a file?
# By default there is no log file.
#file = "/var/log/lvm2.log"
# Should we overwrite the log file each time the program is run?
# By default we append.
overwrite = 0
# What level of log messages should we send to the log file and/or syslog?
# There are 6 syslog-like log levels currently in use - 2 to 7 inclusive.
# 7 is the most verbose (LOG_DEBUG).
level = 0
# Format of output messages
# Whether or not (1 or 0) to indent messages according to their severity
indent = 1
# Whether or not (1 or 0) to display the command name on each line output
command_names = 0
# A prefix to use before the message text (but after the command name,
# if selected). Default is two spaces, so you can see/grep the severity
# of each message.
prefix = " "
# To make the messages look similar to the original LVM tools use:
# indent = 0
# command_names = 1
# prefix = " -- "
# Set this if you want log messages during activation.
# Don't use this in low memory situations (can deadlock).
# activation = 0
# Some debugging messages are assigned to a class and only appear
# in debug output if the class is listed here.
# Classes currently available:
# memory, devices, activation, allocation, lvmetad, metadata, cache,
# locking
# Use "all" to see everything.
debug_classes = [ "memory", "devices", "activation", "allocation",
"lvmetad", "metadata", "cache", "locking" ]
# Configuration of metadata backups and archiving. In LVM2 when we
# talk about a 'backup' we mean making a copy of the metadata for the
# *current* system. The 'archive' contains old metadata configurations.
# Backups are stored in a human readable text format.
backup {
# Should we maintain a backup of the current metadata configuration ?
# Use 1 for Yes; 0 for No.
# Think very hard before turning this off!
backup = 1
# Where shall we keep it ?
# Remember to back up this directory regularly!
backup_dir = "/etc/lvm/backup"
# Should we maintain an archive of old metadata configurations.
# Use 1 for Yes; 0 for No.
# On by default. Think very hard before turning this off.
archive = 1
# Where should archived files go ?
# Remember to back up this directory regularly!
archive_dir = "/etc/lvm/archive"
# What is the minimum number of archive files you wish to keep ?
retain_min = 10
# What is the minimum time you wish to keep an archive file for ?
retain_days = 30
# Settings for the running LVM2 in shell (readline) mode.
shell {
# Number of lines of history to store in ~/.lvm_history
history_size = 100
# Miscellaneous global LVM2 settings
global {
# The file creation mask for any files and directories created.
# Interpreted as octal if the first digit is zero.
umask = 077
# Allow other users to read the files
#umask = 022
# Enabling test mode means that no changes to the on disk metadata
# will be made. Equivalent to having the -t option on every
# command. Defaults to off.
test = 0
# Default value for --units argument
units = "h"
# Since version 2.02.54, the tools distinguish between powers of
# 1024 bytes (e.g. KiB, MiB, GiB) and powers of 1000 bytes (e.g.
# KB, MB, GB).
# If you have scripts that depend on the old behaviour, set this to 0
# temporarily until you update them.
si_unit_consistency = 1
# Whether or not to display unit suffix for sizes. This setting has
# no effect if the units are in human-readable form (global/units="h")
# in which case the suffix is always displayed.
suffix = 1
# Whether or not to communicate with the kernel device-mapper.
# Set to 0 if you want to use the tools to manipulate LVM metadata
# without activating any logical volumes.
# If the device-mapper kernel driver is not present in your kernel
# setting this to 0 should suppress the error messages.
activation = 1
# If we can't communicate with device-mapper, should we try running
# the LVM1 tools?
# This option only applies to 2.4 kernels and is provided to help you
# switch between device-mapper kernels and LVM1 kernels.
# The LVM1 tools need to be installed with .lvm1 suffices
# e.g. vgscan.lvm1 and they will stop working after you start using
# the new lvm2 on-disk metadata format.
# The default value is set when the tools are built.
# fallback_to_lvm1 = 0
# The default metadata format that commands should use - "lvm1" or "lvm2".
# The command line override is -M1 or -M2.
# Defaults to "lvm2".
# format = "lvm2"
# Location of proc filesystem
proc = "/proc"
# Type of locking to use. Defaults to local file-based locking (1).
# Turn locking off by setting to 0 (dangerous: risks metadata corruption
# if LVM2 commands get run concurrently).
# Type 2 uses the external shared library locking_library.
# Type 3 uses built-in clustered locking.
# Type 4 uses read-only locking which forbids any operations that might
# change metadata.
# N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
# supported in clustered environment. If use_lvmetad=1 and locking_type=3
# is set at the same time, LVM always issues a warning message about this
# and then it automatically disables lvmetad use.
locking_type = 1
# Set to 0 to fail when a lock request cannot be satisfied immediately.
wait_for_locks = 1
# If using external locking (type 2) and initialisation fails,
# with this set to 1 an attempt will be made to use the built-in
# clustered locking.
# If you are using a customised locking_library you should set this to 0.
fallback_to_clustered_locking = 1
# If an attempt to initialise type 2 or type 3 locking failed, perhaps
# because cluster components such as clvmd are not running, with this set
# to 1 an attempt will be made to use local file-based locking (type 1).
# If this succeeds, only commands against local volume groups will proceed.
# Volume Groups marked as clustered will be ignored.
fallback_to_local_locking = 1
# Local non-LV directory that holds file-based locks while commands are
# in progress. A directory like /tmp that may get wiped on reboot is OK.
locking_dir = "/run/lock/lvm"
# Whenever there are competing read-only and read-write access requests for
# a volume group's metadata, instead of always granting the read-only
# requests immediately, delay them to allow the read-write requests to be
# serviced. Without this setting, write access may be stalled by a high
# volume of read-only requests.
# NB. This option only affects locking_type = 1 viz. local file-based
# locking.
prioritise_write_locks = 1
# Other entries can go here to allow you to load shared libraries
# e.g. if support for LVM1 metadata was compiled as a shared library use
# format_libraries = "liblvm2format1.so"
# Full pathnames can be given.
# Search this directory first for shared libraries.
# library_dir = "/lib"
# The external locking library to load if locking_type is set to 2.
# locking_library = "liblvm2clusterlock.so"
# Treat any internal errors as fatal errors, aborting the process that
# encountered the internal error. Please only enable for debugging.
abort_on_internal_errors = 0
# Check whether CRC is matching when parsed VG is used multiple times.
# This is useful to catch unexpected internal cached volume group
# structure modification. Please only enable for debugging.
detect_internal_vg_cache_corruption = 0
# If set to 1, no operations that change on-disk metadata will be permitted.
# Additionally, read-only commands that encounter metadata in need of repair
# will still be allowed to proceed exactly as if the repair had been
# performed (except for the unchanged vg_seqno).
# Inappropriate use could mess up your system, so seek advice first!
metadata_read_only = 0
# 'mirror_segtype_default' defines which segtype will be used when the
# shorthand '-m' option is used for mirroring. The possible options are:
# "mirror" - The original RAID1 implementation provided by LVM2/DM. It is
# characterized by a flexible log solution (core, disk, mirrored)
# and by the necessity to block I/O while reconfiguring in the
# event of a failure.
# There is an inherent race in the dmeventd failure handling
# logic with snapshots of devices using this type of RAID1 that
# in the worst case could cause a deadlock.
# Ref: https://bugzilla.redhat.com/show_bug.cgi?id=817130#c10
# "raid1" - This implementation leverages MD's RAID1 personality through
# device-mapper. It is characterized by a lack of log options.
# (A log is always allocated for every device and they are placed
# on the same device as the image - no separate devices are
# required.) This mirror implementation does not require I/O
# to be blocked in the kernel in the event of a failure.
# This mirror implementation is not cluster-aware and cannot be
# used in a shared (active/active) fashion in a cluster.
# Specify the '--type <mirror|raid1>' option to override this default
# setting.
mirror_segtype_default = "raid1"
# 'raid10_segtype_default' determines the segment types used by default
# when the '--stripes/-i' and '--mirrors/-m' arguments are both specified
# during the creation of a logical volume.
# Possible settings include:
# "raid10" - This implementation leverages MD's RAID10 personality through
# device-mapper.
# "mirror" - LVM will layer the 'mirror' and 'stripe' segment types. It
# will do this by creating a mirror on top of striped sub-LVs;
# effectively creating a RAID 0+1 array. This is suboptimal
# in terms of providing redundancy and performance. Changing to
# this setting is not advised.
# Specify the '--type <raid10|mirror>' option to override this default
# setting.
raid10_segtype_default = "raid10"
# The default format for displaying LV names in lvdisplay was changed
# in version 2.02.89 to show the LV name and path separately.
# Previously this was always shown as /dev/vgname/lvname even when that
# was never a valid path in the /dev filesystem.
# Set to 1 to reinstate the previous format.
# lvdisplay_shows_full_device_path = 0
# Whether to use (trust) a running instance of lvmetad. If this is set to
# 0, all commands fall back to the usual scanning mechanisms. When set to 1
# *and* when lvmetad is running (automatically instantiated by making use of
# systemd's socket-based service activation or run as an initscripts service
# or run manually), the volume group metadata and PV state flags are obtained
# from the lvmetad instance and no scanning is done by the individual
# commands. In a setup with lvmetad, lvmetad udev rules *must* be set up for
# LVM to work correctly. Without proper udev rules, all changes in block
# device configuration will be *ignored* until a manual 'pvscan --cache'
# is performed. These rules are installed by default.
# If lvmetad has been running while use_lvmetad was 0, it MUST be stopped
# before changing use_lvmetad to 1 and started again afterwards.
# If using lvmetad, the volume activation is also switched to automatic
# event-based mode. In this mode, the volumes are activated based on
# incoming udev events that automatically inform lvmetad about new PVs
# that appear in the system. Once the VG is complete (all the PVs are
# present), it is auto-activated. The activation/auto_activation_volume_list
# setting controls which volumes are auto-activated (all by default).
# A note about device filtering while lvmetad is used:
# When lvmetad is updated (either automatically based on udev events
# or directly by pvscan --cache <device> call), the devices/filter
# is ignored and all devices are scanned by default. The lvmetad always
# keeps unfiltered information which is then provided to LVM commands
# and then each LVM command does the filtering based on devices/filter
# setting itself.
# To prevent scanning devices completely, even when using lvmetad,
# the devices/global_filter must be used.
# N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
# supported in clustered environment. If use_lvmetad=1 and locking_type=3
# is set at the same time, LVM always issues a warning message about this
# and then it automatically disables lvmetad use.
use_lvmetad = 0
# Full path of the utility called to check that a thin metadata device
# is in a state that allows it to be used.
# Each time a thin pool needs to be activated or after it is deactivated
# this utility is executed. The activation will only proceed if the utility
# has an exit status of 0.
# Set to "" to skip this check. (Not recommended.)
# The thin tools are available as part of the device-mapper-persistent-data
# package from https://github.com/jthornber/thin-provisioning-tools.
# thin_check_executable = "/usr/bin/thin_check"
# Array of string options passed with thin_check command. By default,
# option "-q" is for quiet output.
# With thin_check version 2.1 or newer you can add "--ignore-non-fatal-errors"
# to let it pass through ignorable errors and fix them later.
# thin_check_options = [ "-q" ]
# Full path of the utility called to repair a thin metadata device
# is in a state that allows it to be used.
# Each time a thin pool needs repair this utility is executed.
# See thin_check_executable how to obtain binaries.
# thin_repair_executable = "/usr/bin/thin_repair"
# Array of extra string options passed with thin_repair command.
# thin_repair_options = [ "" ]
# Full path of the utility called to dump thin metadata content.
# See thin_check_executable how to obtain binaries.
# thin_dump_executable = "/usr/bin/thin_dump"
# If set, given features are not used by thin driver.
# This can be helpful not just for testing, but i.e. allows to avoid
# using problematic implementation of some thin feature.
# Features:
# block_size
# discards
# discards_non_power_2
# external_origin
# metadata_resize
# external_origin_extend
# thin_disabled_features = [ "discards", "block_size" ]
activation {
# Set to 1 to perform internal checks on the operations issued to
# libdevmapper. Useful for debugging problems with activation.
# Some of the checks may be expensive, so it's best to use this
# only when there seems to be a problem.
checks = 0
# Set to 0 to disable udev synchronisation (if compiled into the binaries).
# Processes will not wait for notification from udev.
# They will continue irrespective of any possible udev processing
# in the background. You should only use this if udev is not running
# or has rules that ignore the devices LVM2 creates.
# The command line argument --nodevsync takes precedence over this setting.
# If set to 1 when udev is not running, and there are LVM2 processes
# waiting for udev, run 'dmsetup udevcomplete_all' manually to wake them up.
udev_sync = 1
# Set to 0 to disable the udev rules installed by LVM2 (if built with
# --enable-udev_rules). LVM2 will then manage the /dev nodes and symlinks
# for active logical volumes directly itself.
# N.B. Manual intervention may be required if this setting is changed
# while any logical volumes are active.
udev_rules = 1
# Set to 1 for LVM2 to verify operations performed by udev. This turns on
# additional checks (and if necessary, repairs) on entries in the device
# directory after udev has completed processing its events.
# Useful for diagnosing problems with LVM2/udev interactions.
verify_udev_operations = 0
# If set to 1 and if deactivation of an LV fails, perhaps because
# a process run from a quick udev rule temporarily opened the device,
# retry the operation for a few seconds before failing.
retry_deactivation = 1
# How to fill in missing stripes if activating an incomplete volume.
# Using "error" will make inaccessible parts of the device return
# I/O errors on access. You can instead use a device path, in which
# case, that device will be used to in place of missing stripes.
# But note that using anything other than "error" with mirrored
# or snapshotted volumes is likely to result in data corruption.
missing_stripe_filler = "error"
# The linear target is an optimised version of the striped target
# that only handles a single stripe. Set this to 0 to disable this
# optimisation and always use the striped target.
use_linear_target = 1
# How much stack (in KB) to reserve for use while devices suspended
# Prior to version 2.02.89 this used to be set to 256KB
reserved_stack = 64
# How much memory (in KB) to reserve for use while devices suspended
reserved_memory = 8192
# Nice value used while devices suspended
process_priority = -18
# If volume_list is defined, each LV is only activated if there is a
# match against the list.
# "vgname" and "vgname/lvname" are matched exactly.
# "@tag" matches any tag set in the LV or VG.
# "@*" matches if any tag defined on the host is also set in the LV or VG
# If any host tags exist but volume_list is not defined, a default
# single-entry list containing "@*" is assumed.
# volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
# If auto_activation_volume_list is defined, each LV that is to be
# activated with the autoactivation option (--activate ay/-a ay) is
# first checked against the list. There are two scenarios in which
# the autoactivation option is used:
# - automatic activation of volumes based on incoming PVs. If all the
# PVs making up a VG are present in the system, the autoactivation
# is triggered. This requires lvmetad (global/use_lvmetad=1) and udev
# to be running. In this case, "pvscan --cache -aay" is called
# automatically without any user intervention while processing
# udev events. Please, make sure you define auto_activation_volume_list
# properly so only the volumes you want and expect are autoactivated.
# - direct activation on command line with the autoactivation option.
# In this case, the user calls "vgchange --activate ay/-a ay" or
# "lvchange --activate ay/-a ay" directly.
# By default, the auto_activation_volume_list is not defined and all
# volumes will be activated either automatically or by using --activate ay/-a ay.
# N.B. The "activation/volume_list" is still honoured in all cases so even
# if the VG/LV passes the auto_activation_volume_list, it still needs to
# pass the volume_list for it to be activated in the end.
# If auto_activation_volume_list is defined but empty, no volumes will be
# activated automatically and --activate ay/-a ay will do nothing.
# auto_activation_volume_list = []
# If auto_activation_volume_list is defined and it's not empty, only matching
# volumes will be activated either automatically or by using --activate ay/-a ay.
# "vgname" and "vgname/lvname" are matched exactly.
# "@tag" matches any tag set in the LV or VG.
# "@*" matches if any tag defined on the host is also set in the LV or VG
# auto_activation_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
# If read_only_volume_list is defined, each LV that is to be activated
# is checked against the list, and if it matches, it as activated
# in read-only mode. (This overrides '--permission rw' stored in the
# metadata.)
# "vgname" and "vgname/lvname" are matched exactly.
# "@tag" matches any tag set in the LV or VG.
# "@*" matches if any tag defined on the host is also set in the LV or VG
# read_only_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
# Each LV can have an 'activation skip' flag stored persistently against it.
# During activation, this flag is used to decide whether such an LV is skipped.
# The 'activation skip' flag can be set during LV creation and by default it
# is automatically set for thin snapshot LVs. The 'auto_set_activation_skip'
# enables or disables this automatic setting of the flag while LVs are created.
# auto_set_activation_skip = 1
# For RAID or 'mirror' segment types, 'raid_region_size' is the
# size (in KiB) of each:
# - synchronization operation when initializing
# - each copy operation when performing a 'pvmove' (using 'mirror' segtype)
# This setting has replaced 'mirror_region_size' since version 2.02.99
raid_region_size = 512
# Setting to use when there is no readahead value stored in the metadata.
# "none" - Disable readahead.
# "auto" - Use default value chosen by kernel.
readahead = "auto"
# 'raid_fault_policy' defines how a device failure in a RAID logical
# volume is handled. This includes logical volumes that have the following
# segment types: raid1, raid4, raid5*, and raid6*.
# In the event of a failure, the following policies will determine what
# actions are performed during the automated response to failures (when
# dmeventd is monitoring the RAID logical volume) and when 'lvconvert' is
# called manually with the options '--repair' and '--use-policies'.
# "warn" - Use the system log to warn the user that a device in the RAID
# logical volume has failed. It is left to the user to run
# 'lvconvert --repair' manually to remove or replace the failed
# device. As long as the number of failed devices does not
# exceed the redundancy of the logical volume (1 device for
# raid4/5, 2 for raid6, etc) the logical volume will remain
# usable.
# "allocate" - Attempt to use any extra physical volumes in the volume
# group as spares and replace faulty devices.
raid_fault_policy = "warn"
# 'mirror_image_fault_policy' and 'mirror_log_fault_policy' define
# how a device failure affecting a mirror (of "mirror" segment type) is
# handled. A mirror is composed of mirror images (copies) and a log.
# A disk log ensures that a mirror does not need to be re-synced
# (all copies made the same) every time a machine reboots or crashes.
# In the event of a failure, the specified policy will be used to determine
# what happens. This applies to automatic repairs (when the mirror is being
# monitored by dmeventd) and to manual lvconvert --repair when
# --use-policies is given.
# "remove" - Simply remove the faulty device and run without it. If
# the log device fails, the mirror would convert to using
# an in-memory log. This means the mirror will not
# remember its sync status across crashes/reboots and
# the entire mirror will be re-synced. If a
# mirror image fails, the mirror will convert to a
# non-mirrored device if there is only one remaining good
# copy.
# "allocate" - Remove the faulty device and try to allocate space on
# a new device to be a replacement for the failed device.
# Using this policy for the log is fast and maintains the
# ability to remember sync state through crashes/reboots.
# Using this policy for a mirror device is slow, as it
# requires the mirror to resynchronize the devices, but it
# will preserve the mirror characteristic of the device.
# This policy acts like "remove" if no suitable device and
# space can be allocated for the replacement.
# "allocate_anywhere" - Not yet implemented. Useful to place the log device
# temporarily on same physical volume as one of the mirror
# images. This policy is not recommended for mirror devices
# since it would break the redundant nature of the mirror. This
# policy acts like "remove" if no suitable device and space can
# be allocated for the replacement.
mirror_log_fault_policy = "allocate"
mirror_image_fault_policy = "remove"
# 'snapshot_autoextend_threshold' and 'snapshot_autoextend_percent' define
# how to handle automatic snapshot extension. The former defines when the
# snapshot should be extended: when its space usage exceeds this many
# percent. The latter defines how much extra space should be allocated for
# the snapshot, in percent of its current size.
# For example, if you set snapshot_autoextend_threshold to 70 and
# snapshot_autoextend_percent to 20, whenever a snapshot exceeds 70% usage,
# it will be extended by another 20%. For a 1G snapshot, using up 700M will
# trigger a resize to 1.2G. When the usage exceeds 840M, the snapshot will
# be extended to 1.44G, and so on.
# Setting snapshot_autoextend_threshold to 100 disables automatic
# extensions. The minimum value is 50 (A setting below 50 will be treated
# as 50).
snapshot_autoextend_threshold = 100
snapshot_autoextend_percent = 20
# 'thin_pool_autoextend_threshold' and 'thin_pool_autoextend_percent' define
# how to handle automatic pool extension. The former defines when the
# pool should be extended: when its space usage exceeds this many
# percent. The latter defines how much extra space should be allocated for
# the pool, in percent of its current size.
# For example, if you set thin_pool_autoextend_threshold to 70 and
# thin_pool_autoextend_percent to 20, whenever a pool exceeds 70% usage,
# it will be extended by another 20%. For a 1G pool, using up 700M will
# trigger a resize to 1.2G. When the usage exceeds 840M, the pool will
# be extended to 1.44G, and so on.
# Setting thin_pool_autoextend_threshold to 100 disables automatic
# extensions. The minimum value is 50 (A setting below 50 will be treated
# as 50).
thin_pool_autoextend_threshold = 100
thin_pool_autoextend_percent = 20
# While activating devices, I/O to devices being (re)configured is
# suspended, and as a precaution against deadlocks, LVM2 needs to pin
# any memory it is using so it is not paged out. Groups of pages that
# are known not to be accessed during activation need not be pinned
# into memory. Each string listed in this setting is compared against
# each line in /proc/self/maps, and the pages corresponding to any
# lines that match are not pinned. On some systems locale-archive was
# found to make up over 80% of the memory used by the process.
# mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
# Set to 1 to revert to the default behaviour prior to version 2.02.62
# which used mlockall() to pin the whole process's memory while activating
# devices.
use_mlockall = 0
# Monitoring is enabled by default when activating logical volumes.
# Set to 0 to disable monitoring or use the --ignoremonitoring option.
monitoring = 1
# When pvmove or lvconvert must wait for the kernel to finish
# synchronising or merging data, they check and report progress
# at intervals of this number of seconds. The default is 15 seconds.
# If this is set to 0 and there is only one thing to wait for, there
# are no progress reports, but the process is awoken immediately the
# operation is complete.
polling_interval = 15
# Report settings.
# report {
# Align columns on report output.
# aligned=1
# When buffered reporting is used, the report's content is appended
# incrementally to include each object being reported until the report
# is flushed to output which normally happens at the end of command
# execution. Otherwise, if buffering is not used, each object is
# reported as soon as its processing is finished.
# buffered=1
# Show headings for columns on report.
# headings=1
# A separator to use on report after each field.
# separator=" "
# Use a field name prefix for each field reported.
# prefixes=0
# Quote field values when using field name prefixes.
# quoted=1
# Output each column as a row. If set, this also implies report/prefixes=1.
# colums_as_rows=0
# Comma separated list of columns to sort by when reporting 'lvm devtypes' command.
# See 'lvm devtypes -o help' for the list of possible fields.
# devtypes_sort="devtype_name"
# Comma separated list of columns to report for 'lvm devtypes' command.
# See 'lvm devtypes -o help' for the list of possible fields.
# devtypes_cols="devtype_name,devtype_max_partitions,devtype_description"
# Comma separated list of columns to report for 'lvm devtypes' command in verbose mode.
# See 'lvm devtypes -o help' for the list of possible fields.
# devtypes_cols_verbose="devtype_name,devtype_max_partitions,devtype_description"
# Comma separated list of columns to sort by when reporting 'lvs' command.
# See 'lvs -o help' for the list of possible fields.
# lvs_sort="vg_name,lv_name"
# Comma separated list of columns to report for 'lvs' command.
# See 'lvs -o help' for the list of possible fields.
# lvs_cols="lv_name,vg_name,lv_attr,lv_size,pool_lv,origin,data_percent,move_pv,mirror_log,copy_percent,convert_lv"
# Comma separated list of columns to report for 'lvs' command in verbose mode.
# See 'lvs -o help' for the list of possible fields.
# lvs_cols_verbose="lv_name,vg_name,seg_count,lv_attr,lv_size,lv_major,lv_minor,lv_kernel_major,lv_kernel_minor,pool_lv,origin,data_percent,metadata_percent,move_pv,copy_percent,mirror_log,convert
# Comma separated list of columns to sort by when reporting 'vgs' command.
# See 'vgs -o help' for the list of possible fields.
# vgs_sort="vg_name"
# Comma separated list of columns to report for 'vgs' command.
# See 'vgs -o help' for the list of possible fields.
# vgs_cols="vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
# Comma separated list of columns to report for 'vgs' command in verbose mode.
# See 'vgs -o help' for the list of possible fields.
# vgs_cols_verbose="vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
# Comma separated list of columns to sort by when reporting 'pvs' command.
# See 'pvs -o help' for the list of possible fields.
# pvs_sort="pv_name"
# Comma separated list of columns to report for 'pvs' command.
# See 'pvs -o help' for the list of possible fields.
# pvs_cols="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
# Comma separated list of columns to report for 'pvs' command in verbose mode.
# See 'pvs -o help' for the list of possible fields.
# pvs_cols_verbose="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
# Comma separated list of columns to sort by when reporting 'lvs --segments' command.
# See 'lvs --segments -o help' for the list of possible fields.
# segs_sort="vg_name,lv_name,seg_start"
# Comma separated list of columns to report for 'lvs --segments' command.
# See 'lvs --segments -o help' for the list of possible fields.
# segs_cols="lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
# Comma separated list of columns to report for 'lvs --segments' command in verbose mode.
# See 'lvs --segments -o help' for the list of possible fields.
# segs_cols_verbose="lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
# Comma separated list of columns to sort by when reporting 'pvs --segments' command.
# See 'pvs --segments -o help' for the list of possible fields.
# pvsegs_sort="pv_name,pvseg_start"
# Comma separated list of columns to sort by when reporting 'pvs --segments' command.
# See 'pvs --segments -o help' for the list of possible fields.
# pvsegs_cols="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
# Comma separated list of columns to sort by when reporting 'pvs --segments' command in verbose mode.
# See 'pvs --segments -o help' for the list of possible fields.
# pvsegs_cols_verbose="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size,lv_name,seg_start_pe,segtype,seg_pe_ranges"
# Advanced section #
# Metadata settings
# metadata {
# Default number of copies of metadata to hold on each PV. 0, 1 or 2.
# You might want to override it from the command line with 0
# when running pvcreate on new PVs which are to be added to large VGs.
# pvmetadatacopies = 1
# Default number of copies of metadata to maintain for each VG.
# If set to a non-zero value, LVM automatically chooses which of
# the available metadata areas to use to achieve the requested
# number of copies of the VG metadata. If you set a value larger
# than the the total number of metadata areas available then
# metadata is stored in them all.
# The default value of 0 ("unmanaged") disables this automatic
# management and allows you to control which metadata areas
# are used at the individual PV level using 'pvchange
# --metadataignore y/n'.
# vgmetadatacopies = 0
# Approximate default size of on-disk metadata areas in sectors.
# You should increase this if you have large volume groups or
# you want to retain a large on-disk history of your metadata changes.
# pvmetadatasize = 255
# List of directories holding live copies of text format metadata.
# These directories must not be on logical volumes!
# It's possible to use LVM2 with a couple of directories here,
# preferably on different (non-LV) filesystems, and with no other
# on-disk metadata (pvmetadatacopies = 0). Or this can be in
# addition to on-disk metadata areas.
# The feature was originally added to simplify testing and is not
# supported under low memory situations - the machine could lock up.
# Never edit any files in these directories by hand unless you
# you are absolutely sure you know what you are doing! Use
# the supplied toolset to make changes (e.g. vgcfgrestore).
# dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
# Event daemon
dmeventd {
# mirror_library is the library used when monitoring a mirror device.
# "libdevmapper-event-lvm2mirror.so" attempts to recover from
# failures. It removes failed devices from a volume group and
# reconfigures a mirror as necessary. If no mirror library is
# provided, mirrors are not monitored through dmeventd.
mirror_library = "libdevmapper-event-lvm2mirror.so"
# snapshot_library is the library used when monitoring a snapshot device.
# "libdevmapper-event-lvm2snapshot.so" monitors the filling of
# snapshots and emits a warning through syslog when the use of
# the snapshot exceeds 80%. The warning is repeated when 85%, 90% and
# 95% of the snapshot is filled.
snapshot_library = "libdevmapper-event-lvm2snapshot.so"
# thin_library is the library used when monitoring a thin device.
# "libdevmapper-event-lvm2thin.so" monitors the filling of
# pool and emits a warning through syslog when the use of
# the pool exceeds 80%. The warning is repeated when 85%, 90% and
# 95% of the pool is filled.
thin_library = "libdevmapper-event-lvm2thin.so"
# Full path of the dmeventd binary.
# executable = "/usr/sbin/dmeventd" -
Can't save/write Framemaker files
Hi,
I've suddenly got a major problem - I can't Save or Save As any Framemaker files.
Specifically, I am using Framemaker 9 (latest patches) under Win XP/SP3, using parallels Desktop for Mac on my MacBook Pro 17" (8GB, 2.8GHz Intel Core 2 Duo, Mac OS 10.6.2).
I can save to my Windows virtual drive, but if I try to save to my Mac world, I get an error that says "The \\.psf\Home\<path>\<filename>.fm.DE1 that FrameMaker wrote may be damaged". There is a .lck file, but can't save the .fm file, even with another name.
I have tried saving in different formats (to check it's not a network/permissions issue). I can save in .html, .txt, .xml, .pdf, .rtf. I cannot save in any of the Frame-related formats (MIF, .fm, previous versions).
I suspect the problem arose after updating Parallels Desktop to the latest version. Dumb move. It barfed at the end of the upgrade, but I thought things were OK after restarting.
I also had a disk problem on my Mac (various catalog file errors) after ejecting a recaltitrant USB pen drive. Major headache. Again, thought it was all fixed after fsck and Disk Utility checks. maybe not. Still a weird issue though. I do seem to remember having something like this before. Anyone got any ideas?
Martin Ley
martin at em-dash dot comEmDashMan wrote:
Hi,
I've suddenly got a major problem - I can't Save or Save As any Framemaker files.
Specifically, I am using Framemaker 9 (latest patches) under Win XP/SP3, using parallels Desktop for Mac on my MacBook Pro 17" (8GB, 2.8GHz Intel Core 2 Duo, Mac OS 10.6.2).
I can save to my Windows virtual drive, but if I try to save to my Mac world, I get an error that says "The \\.psf\Home\<path>\<filename>.fm.DE1 that FrameMaker wrote may be damaged". There is a .lck file, but can't save the .fm file, even with another name.
I have tried saving in different formats (to check it's not a network/permissions issue). I can save in .html, .txt, .xml, .pdf, .rtf. I cannot save in any of the Frame-related formats (MIF, .fm, previous versions).
I suspect the problem arose after updating Parallels Desktop to the latest version. Dumb move. It barfed at the end of the upgrade, but I thought things were OK after restarting.
I also had a disk problem on my Mac (various catalog file errors) after ejecting a recaltitrant USB pen drive. Major headache. Again, thought it was all fixed after fsck and Disk Utility checks. maybe not. Still a weird issue though. I do seem to remember having something like this before. Anyone got any ideas?
Martin Ley
martin at em-dash dot com
Hi, Martin:
I'm using InDesign on my MacBookPro pre-unibody under Leopard, and also under Windows 7 Vista running on VMware Fusion2.
I never save my files on the Windows virtual drive for a couple of reasons:
* too likely to crash unexpectedly - hey, it's Windows.
* because the virtual drive file is always marked changed no matter how little activity you do on it, even just opening it, Time Machine backs up the entire humongous drive file and fills up my Time Capsule needlessly.
EDIT:
* I exclude the virtual drive file from the Time Machine backup, but I do save a copy of it in case I need to replace one that goes bad. Doesn't always work, though. I also save a bunch of automatic snapshots of the virtual drive, and manual ones when I change something. I haven't got the habit yet of also making Windows Restore Points. I figure if a Fusion2 snapshot can't get me back working, it's time to start over, or copy my safety copy.
/EDIT
I always save files made on the Mac or Windows sides on my Mac file system.
One likely source of being unable to save is unwanted and unexpected permission changes. Have you tried fixing permissions with Disk Utility, or the free utility OnyX, or the free utility applejack? You run OnyX from within OS X. You run applejack from the command line that appears when you restart the Mac and hold CMD-s to go into single user mode. The command: applejack auto restart performs a bunch of cleanup operations automatically, and displays its actions as it does them. When it's done, it restarts your Mac.
Applejack is more limited in what it does, so it easier to avoid doing anything you didn't intend. OnyX offers options that can clean out stuff you might not want to, so read carefully what options you select.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices -
[SOLVED] Install to BtrFS already existing (but empty) subvolume
I currently have a Btrfs filesystem made up of /dev/sda5 and /dev/sda6. On that filesystem, there is an Ubuntu 11.10 install in the @oneiric_main subvolume and a data subvolume (with Ubuntu /home) in the @Data subvolume. Grub2 is installed in the @oneiric_main subvolume and works fine.
I would like to install arch to a new subvolume on the existing BtrFS filesystem. I would probably make a subvolume named @arch_2011.08 to install it on. (@arch is taken--I already tried to do this myself, installing using pacman -r <subvol_mount_point> -Sy base --ignore grub. Didn't work, has no initrd, kernel panics with VFS not syncing error) I would like to then boot Arch with Ubuntu's Grub2 since that install is working off BtrFS. How do I go about doing this?
On the install that failed, I generally tried to follow https://wiki.archlinux.org/index.php/In … Btrfs_root, but I didn't really need/want automatic snapshots, so I didn't think I wanted to install mkinitcpio-btrfs. For it my Grub2 entry is
menuentry "Arch (on /dev/sda6)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod btrfs
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set=root d551dbac-3c7f-4f8f-a0d4-2d1f242cc42f
linux /@arch/boot/vmlinuz-linux root=/dev/disk/by-uuid/d551dbac-3c7f-4f8f-a0d4-2d1f242cc42f rootflags=subvol=@arch ro
I've tried to chroot to the Arch install from Ubuntu and run mkinitcpio, but that gave an error that some directory was not valid. The directory it complained about had the Ubuntu kernel version in its name, so I figured I was doing something majorly wrong. Edit:I suppose it would help if I updated the /etc/fstab. I did, but I still get the same error. The first line is "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)"
I'm not sure if I should try to fix the first install or just start again. Either way would get the goal:Arch installed on the BtrFS subvolume, booted with Ubuntu's Grub2.
Last edited by Azendale (2011-12-17 22:34:16)@Teekay:I did mount /proc, /sys and /dev into the @arch subvolume before chrooting.
Here's what happens when I try to chroot into the Arch install to make an initrd:
[root@dynl:~]# mount -o subvol=@arch /dev/sda5 /mnt
[root@dynl:~]# cd /mnt
[root@dynl:/mnt]# mount -o bind /dev dev
[root@dynl:/mnt]# mount -o bind /sys sys
[root@dynl:/mnt]# mount -o bind /proc proc
[root@dynl:/mnt]# chroot .
chroot: failed to run command `/bin/zsh': No such file or directory
[root@dynl:/mnt]# chroot . bash
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
[root@dynl /]# ls
bin dev home lib64 mnt proc run srv tmp var
boot etc lib media opt root sbin sys usr
[root@dynl /]# mount
/dev/sda5 on / type btrfs (rw,relatime)
udev on /dev type devtmpfs (rw,relatime,size=693104k,nr_inodes=173276,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
[root@dynl /]# mkinitcpio
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
==> ERROR: '/lib/modules/3.1.0-030100rc10-generic' is not a valid kernel module directory
Update: I've made progress. Instead of chrooting from Ubuntu, I chooted from the arch installation live image. I was able to run mkinitcpio -p linux. I added an initrd line to grub2:
menuentry "Arch (on /dev/sda6)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod btrfs
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set=root d551dbac-3c7f-4f8f-a0d4-2d1f242cc42f
linux /@arch/boot/vmlinuz-linux root=/dev/disk/by-uuid/d551dbac-3c7f-4f8f-a0d4-2d1f242cc42f rootflags=subvol=@arch ro
initrd /@arch/boot/initramfs-linux.img
The new error is :
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: Starting udevd...
done.
:: Running Hook [udev]
:: Triggering uevents...done.
Waiting 10 seconds for device /dev/sda6 ...
mount: mounting dev/sda6 on /new_root failed: Invalid argument
ERROR: Failed to mount the real root device.
bailing out, you are on your own. Good luck.
sh: can't access tty; job control turned off
[ramfs /]#
Also, the Arch /etc/fstab is:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=d551dbac-3c7f-4f8f-a0d4-2d1f242cc42f / btrfs defaults,subvol=@arch 0 0
Last edited by Azendale (2011-11-05 06:43:49) -
UPDATE (6/10/10): http://bbs.archlinux.org/viewtopic.php? … 51#p772651
THIS POST DEPRECATED UNTIL I UPDATE IT, USE THE UPDATED POST ABOVE
available:
http://aur.archlinux.org/packages.php?ID=33376
this package will install a mkinitcpio hook intended for those who wish to have a single or multi-drive BTRFS file system as their / (root). the hook will ensure that the chosen root device from the kernel command line is intact and safe to boot. if root is not a BTRFS device, the hook is quietly skipped.
it requires btrfs-progs from here:
http://aur.archlinux.org/packages.php?ID=15635
hook supports both UUID or device based root names. UUID is safer; the entire BTRFS array only has one UUID, so referring to it means no problems. use /dev/device/by-uuid on kernel boot.
hook supports hot spares by using a dummy, spare BTRFS file system to steal devices from as needed. the spare pool can be referenced by label or UUID.**
hook supports automatic repairing of the array if possible, automatic dropping of missing/failed devices if possible, and booting the array to a degraded state (one or more devices missing) if possible.**
**NOTE: there are some bugs that may be in the hook/btrfs module/btrfs-progs that prevent raid1 (maybe others) arrays from being repaired (see http://pastebin.com/m5706f47f) however, this hook will work fine as is for single/multi-device arrays that are intact. enable experimental options manually by editing options in the hook itself (/lib/initcpio/hooks/btrfs). USE WITH CAUTION ON MULTI-DEVICE SETUPS.
the initramfs script can be seen here:
http://aur.archlinux.org/packages/mkini … btrfs_hook
its fairly commented, although there are a few things i'll point out for others who want to edit:
1) i plan to rework _btrfs_scandev() to be more flexible in the variables it produces. that function simply parses "btrfs-show" and gleans valuable information from it. it will be used to verify array states with certainty.
2) seems that btrfsctl does not have meaningful exit codes right now, do not rely, see _btrfs_register().
3) seems that after legitimately removing a device from an array (NOT using "missing" special keyword), the mount needs a "mount -o remout [mnt]" for the ***missing flag to be removed from btrfs-show. not sure the ramification of this or if its necessary.
4) some or all of this functionality may someday be provided by module/kernel
needs work + comments
add "btrfs" to HOOKS in mkinitcpio.conf
Last edited by extofme (2010-06-10 06:09:10)bleh, sorry about the late response, i usually subscribe to topics i create/join, i must have missed this one.
resi wrote:After minor problems with the mkinitcpio (lvm hook seems to conflict with the btrfs one) image and fstab (why do I have to specify the root fs there? its already mounted when fstab is examined)
i could be mistaken here, but initially your / is mounted read-only. during the init process, one of the primary scripts issues a "mount -o remount,rw /" to remount the root device as read-write. i _think_ using the mount command in this way (against a mount point and not a device) requires the mount point to exist in the fstab.
resi wrote:But what happens if I really screw it up? I'm on 2.6.33 (.2-1) and read about missing ioctl()s regarding btrfs, meaning I can't replace the "default" subvolume (whats the difference between a subvolume and a snapshot anyway?). Its also not possible to list available subvolumes/snpshots, meaning your script (or organizing snapshots in similar ways) is the only chance to keep track of them, right?
the inability to set the default subvolume is kind of a non-issue after i thought about it more, and some of the discussion on arch-general. i plan to update the hook soon to allow the "promotion" of the rollback to become the new active subvolume. ill do this by snapshotting your current / to a new subvolume called /__active, and then permanently booting into that [__active] instead of / or "." (a period is the default subvolume, like current directory).
there is no difference internally, whatsoever (AFIAK), between a subvolume and a snapshot. its just a matter of context: a subvolume starts out empty (explicitly created via a command/etc.), and a snapshot starts out with content (COW operation against an existing subvolume, i.e. "copy")
yeah without the ability to list available subvolumes, we have to make up some structure, and assume everything goes well. my script simply assumes anything within /snapshots is indeed a snapshot that can be copied (to /__rollback) and booted. even if we can list subvolumes, we'll still need some kind of predefined structure (so the script knows which snapshots are bootable, and which are not, i.e. snapshots of /home are not bootable).
resi wrote:I guess a plain "mount -t btrfs /dev/xyz" will mount the "default" subvolume then.
correct.
resi wrote:
Once I really screw up I will have to boot into a snapshot, mount the default subvolume somewhere and restore it using a full copy from the snapshot (a la rsync --delete), then reboot and I'm back at the start again.
Is this correct?
unfortunately, without modifying the script, a manual copy is necessary :-( totally defeating the advantages of btrfs. so, yes. the problem is that the default subvolume itself cannot be replace by another... note this is different from SETTING the default subvolume. i'm not sure if the real default subvolume ("." the period) will ever be replaceable/removable, i'd have to ask the btrfs list. this is why i advocate installing your system into a subvolume FROM THE BEGINNING. this gives us more flexibility.
resi wrote:Is there some way to permanently change the subvolume mounted by your hook (i.e. not running in a volatile snapshot, but actually drop the default one and always boot into a given snapshot until further notice - a new snapshot)?
this is actually how i intend to implement non-volatile rollback abilities in the hook. instead of booting the default "." subvolume, my hook will ALWAYS boot the subvolume called "__active", located at /__active. this way you can put whatever you want there, and it will be booted at the next reboot. therefore, you can boot into rollback mode (essentially booting into /__rollback), update/add/remove whatever you want, and when your satisfied, you simply snapshot /__rollback to /__active and your done. reboot, and your new __active will be in the same state as the point it was created in rollback mode.
does all this make sense? i'm told i tend to over explain/complicate things :-).
resi wrote:Before every -Syu I have to check for kernel/xorg updates, read about them, check the mailing list, wait ... wait ... wait ... loose patience, give it a shot, recompile/reinstall the necessary stuff (at least I've got PKGBUILDs prepared) and hope for the best. With btrfs, this is just a non-issue. Or at least will be once the integration is better.
i hear ya. i like the idea of riding the edge without the fear of being cut by it. unfortunately, until btrfs is supported by grub2, kernel rollbacks aren't possible (you'd have to manually backup your old kernel+initrd). something to keep in mind.
hunterthomson wrote:However, if I can just tell my clients to reboot into a snapshot "problem solved." Then I can spend the time to solve the problem, without the client siting around with a broken system.
bingo. that is pretty much my primary motivation here... less time freaking out about down time/whatever; everybody wins.
hunterthomson wrote:Did you know Fedora 13 supports Btrfs Snapshotting and Roll-Back. Super cool.
i know they have some support but i haven't tried it; from what i've read, the support is pretty weak... you can get yum to create the snapshot by installing a package, but there is no utility to actually use them later on. i could be mistaken as i don't use fedora, this is only what i've read.
what sucks is pacman doesnt have any ability to use hooks... i dont think we will see automatic snapshots by the package manager without a wrapper like clyde/powerpill/packer/etc.
C Anthony -
[solved] How to restart all services with systemd?
I had the habit of restarting all daemons after an upgrade so to make sure the newest libraries, configuration files etc were loaded. I did that with a shell script that restarted the daemons in order which they were listed in rc.conf. With systemd I could do something similar by first getting a list of running services and ordering a 'systemcrl restart <servicename>' for each. But since systemd keeps track of dependencies I wonder if that would be the way to do it. Also I would need to filter out 'one shot' type services that are only needed on bootup.
<edit>restart instead of reload</edit>
<edit>solved it with a little script</edit>
Last edited by rwd (2012-11-27 21:02:02)I think that's what systemctl snapshot does.
snapshot [NAME]
Create a snapshot. If a snapshot name is specified, the new snapshot will be named after it. If none is specified an automatic snapshot name is generated. In either case, the snapshot name used is printed to STDOUT, unless --quiet is specified.
A snapshot refers to a saved state of the systemd manager. It is implemented itself as a unit that is generated dynamically with this command and has dependencies on all units active at the time. At a later time the user may return to this state by using the isolate command on the snapshot unit.
Snapshots are only useful for saving and restoring which units are running or are stopped, they do not save/restore any other state. Snapshots are dynamic and lost on reboot.
Then, isolate emergency.target or rescue target and switch to the snapshot. -
Why??? Simple snapshot can not refresh automatically, but can refresh manually.
Server 1 : Oracle 7.3.4 (as a Master site)
Server 2 : Oracle 7.3.4 (as a Snopshot site)
Client PC: SQL*Plus (Oracle 7.3.4 Client)
Step 1: on Client PC, start 2 SQL*Plus dialog Windows,
one(Window A) for <Server 1> , another(Window B) for <Server 2>;
Step 2: on <Window A> do:
SQL>connect scott/tiger@Server1
SQL>CREATE SNAPSHOT LOG ON scott.dept ;
SQL>select * from dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
Step 3: on <Window B> do:
SQL>connect scott/tiger@Server2
SQL>CREATE DATABASE LINK oracle USING 'Server1';
SQL>CREATE SNAPSHOT all_dept REFRESH fast
start with sysdate NEXT SYSDATE+1/(24*60)
AS SELECT * FROM scott.dept@oracle;
-- refresh interval: 1 minute
SQL>select * from all_dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
Step 4: on <Window A> do:
SQL>insert into dept values (50,'MMMMMM','NNNNN');
SQL>commit;
SQL>select * from dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
50 MMMMMM NNNNN
<one or two minutes later ... ... >
Step 5: on <Window B> do:
SQL>select * from all_dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
conclusion: Simple snapshot can not refresh automatically ???????
SQL>exec DBMS_SNAPSHOT.REFRESH( list => 'all_dept',method => 'F');
SQL>select * from all_dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
50 MMMMMM NNNNN
conclusion:Simple snapshot can refresh manually.
How to solve this problem?????
Thank you very much
Zhang Ming-anWhen you are manually refreshing the snapshot as scott/tiger, and your database link was defined with a 'connect to/identified by ' clause, your login credentials will be scott/tiger. When the refresh happens from the job queue, it does not use those credentials, It uses some default set. What you should probably do is:
1. create public database link Oracle using 'server1';
2. as scott/tiger, create database link Oracle connect to scott identified by tiger;
3. your automatic refresh should work now.
Maybe you are looking for
-
How do I transfer music from my Itunes library to my Ipod?
I've manually transferred music from my library onto my Ipod in the past, but I can't remember how it's done. Anyone have/know of step-by-step instructions?
-
HT4847 Can I turn off camera roll backup?
Can I turn off and delete camera roll backup? Its taking up 4 GB of storage
-
Ken Burns Effect not working as expected.
Hi, I have created a slideshow in iPhoto 08 and want to have all of the slides use the ken burns effect except the first one (i want this to be a 20 second title photo). To get this to work, i have disabled the Automatic Ken Burns effect in the setti
-
Ok, I recieved my MacBook Pro (the stock 2.0 with maxed out ram) and took it out for a spin. OK, these results are far from benchmark-like, but will still give you a taste as of what to expect from the machine. Here's what I did: Took it out of the b
-
Wsdl soap style get RPC need document/literal
Hi, Using jdev10.1.3/jre1.3 to generate webservice wrappers How do you change style which defaults to RPC and I need document/literal ? Can't really find any properties in the IDE to do it, can anyone point me in to the relevant sections? Thanks Pete