[SOLVED] LVM physical volume not available during early boot
Note to self:
Of course it's not available - it's in an encrypted LVM container!
Hi,
I'm trying to get myself a working hibernate but I'm stuck on resume hook not seeing my swap partition.
The swap partition is on an LVM logical volume (LV) which is on one physical volume PV created on a different harddrive than the root partition is. During the bootup I get something similar to "ERROR: hibernation partition '/dev/mapper/volgrp-swap' not found".
Further debugging gave out that for some reason the early userspace has no access to LVM physical volume. I managed to run a shell using break=premount boot parameter. From there I found out that "lvm pvscan" shows no physical volumes at all. I suspect that mkinitcpio does not give a damn about non-root harddrive though I was unable to confirm that and neither was I able to find any other reason for this behaviour.
Relevant lines from mkinitcpio.conf:
MODULES="dm_mod btrfs"
HOOKS="base udev block lvm2 autodetect keyboard encrypt resume filesystems fsck"
Any help would be appreciated, including any tips on where to get more debug data.
cheers,
-miky
Last edited by mr.MikyMaus (2013-09-25 21:32:32)
Fackamato wrote:
Do you have the correct "root=" line in your bootloader's kernel line? Is it in fstab?
Perhaps try with rootdelay=5 as well?
Yes I have root=/dev/mapper/hdgroup0-volroot, and its in fstab (not that fstab is even being read)
root delay wouldn't help at all because after it drops me to a busybox shell I can't do a manual mount.
Similar Messages
-
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" -
How can I fix my iphone's sound I plugged it in to my radio and the sound came out fine but when I took it out the volume bar dissapered and ever seince all it says volume not available, but it work with headphones in. What can I do to fix it?
Try reset all settings.
Settings > General > Reset > Reset all settings. It won't delete any data. -
SAP LSO - Time integration; Error Participant not available during course
Dear Gurus,
I have requirement to enable employees to book the course irrespective of the Workshedule he is available in. Please let me know how to acheive it.
Thanks and regards
Saravanan KHello Saravanan,
You have mentioned participant not available during course
the reason for this may be check any future action was done on the participant or check whether the participant is reserved/booked as a trainer on that day.
Time integration will show impact on attendance only.
thanks
rafi -
OVM 3.3.1: NFS storage is not available during repository creation
Hi, I have OVM Manager running on a separate machines managing 3 servers running OVM server in a server pool. One of the server also exports a NFS share that all other machines are able to mount and read/write to. I want to use this NFS share to create a OVM repository but so far unable to get it to work.
From this first screen shot we can see that the NFS file system was successfully added under storage tab and refreshed.
https://www.dropbox.com/s/fyscj2oynud542k/Screenshot%202014-10-11%2013.40.00.png?dl=0
But its is not available when adding a repository as shown below. What can I did to make it show up here.
https://www.dropbox.com/s/id1eey08cdbajsg/Screenshot%202014-10-11%2013.40.19.png?dl=0
No luck with CLI either. Any thoughts?
OVM> create repository name=myrepo fileSystem="share:/" sharepath=myrepo - Configurable attribute by this name can't be found.
== NFS file system refreshed via CLI ===
OVM> refresh fileServer name=share
Command: refresh fileServer name=share
Status: Success
Time: 2014-10-11 13:28:14,811 PDT
JobId: 1413059293069
== file system info
OVM> show fileServer name=share
Command: show fileServer name=share
Status: Success
Time: 2014-10-11 13:28:28,770 PDT
Data:
FileSystem 1 = ff5d21be-906d-4388-98a2-08cb9ac59b43 [share]
FileServer Type = Network
Storage Plug-in = oracle.generic.NFSPlugin.GenericNFSPlugin (1.1.0) [Oracle Generic Network File System]
Access Host = 1.2.3.4
Admin Server 1 = 44:45:4c:4c:46:00:10:31:80:51:c6:c0:4f:35:48:31 [dev1]
Refresh Server 1 = 44:45:4c:4c:46:00:10:31:80:51:c6:c0:4f:35:48:31 [dev1]
Refresh Server 2 = 44:45:4c:4c:47:00:10:31:80:51:b8:c0:4f:35:48:31 [dev2]
Refresh Server 3 = 44:45:4c:4c:33:00:10:34:80:38:c4:c0:4f:53:4b:31 [dev3]
UniformExports = Yes
Id = 0004fb0000090000fb2cf8ac1968505e [share]
Name = share
Description = NFS exported /dev/sda1 (427GB) on dev1
Locked = false
== version details ==
OVM server:3.3.1-1065
Agent Version:3.3.1-276.el6.7Kernel Release:3.8.13-26.4.2.el6uek.x86_64
Oracle VM Manager
Version: 3.3.1.1065
Build: 20140619_1065Actually, OVM, as is with all virtualization servers, is usually only the head on a comprehensive infrastructure. OVM seems quite easy from the start, but I'd suggest, that you at least skim trough the admin manual, to get some understanding of the conecpts behind it. OVS thus usually only provides the CPU horse power, but not the storage, unless you only want to setup a single-server setup. If you plan on having a real multi-server setup, then you will need shared storage.
The shared storage for the server pool, as well as the storage repository can be served from the same NFS server without issues. If you want to have a little testbed, then NFS is for you. It lacks some features that OCFS2 benefits from, like thin provisioning, reflinks and sparse files.
If you want to remove the NFS storage, then you'll need to remove any remainders of any OVM object, like storage repositories or server pool filesystems. Unpresent and storage repo and delete it afterwards… Also, I hope that you didn't create the NFS export directly on the root of the drive, since OVM wants to remove any file on the NFS export and on any root of ony volume there's the lost-found folder, which OVM, naturally, can't remove. Getting rid of such a storage repo can be a bit daunting…
Cheers,
budy -
DPM 2012 R2 All backups fail with recovery point volume not available after resizing OS disk
I resized the C drive partition of my DPM server (the data is on a separate dedicated array) and everything failed. I put it back but everything is still failing with the same problem as here:
DPM 2007: The recovery point volume is not available?
I've run chkdsk for a couple and both have given the following after doing 3 stages:
Windows has scanned the file system and found no problems.
No further action is required.
The backups still fail and the only error information I can find in the event logs is:
Backup job for datasource: Online\<VM name> on production server: <host FQDN> failed.
How can I find out what the problem actually is?
Is it possible to resize the C drive containing a DPM install? If so what can it be safely resized to? It easily met the minimum requirements and I don't know of anything in the documentation that says resizing the OS disk may cause issues.
Preparing your environment for System Center 2012 R2 Data Protection Manager (DPM)Hi,
Resizing the boot partition (usually C:) should not effect DPM in any way. DPM writes directly to it's volumes contained in the storage pool and not through the mount points on the C: drive. So is the DPM UI showing
missing volume next to some data sources ? Try doing a DPM disk rescan and see if that removes the missing volume flag.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights. -
"ignore ownership on this volume" not available
I have a large external (Firewire) volume that is in the process of converting to core storage (FileVault) encryption. (I did not want to convert it, but did so by accident). It has been converting for a couple of days, and I have days more until the conversion is finished.
Currently the permissions on the volume (as I said, it is an external volume) are completely whacked out
* "Ignore ownership on this volume" is NOT available in the Finder Get Info window
* Permissions for most folders and files are
You have custom access
Name Privledge
<Fetching> Read & write
staff Read only
everyone Read only
That is, it can't seem to figure out who the owner is for most of the files and folders. This means I cannot easily write files on the disk.
Any thoughts other than (1) wait for encryption to finish and see if the problem goes away or (2) restore from back-ups? Restoring takes a couple of days, so I'd rather not do that.I attempted to uncheck ignore ownership for the same reason you describe for DiskWarrior 4.1. I followed the instructions in the panel "to unckeck ignore ownership for DW v 4.1". But since ignore ownership is not listed under Sharing & Permissions, I failed. Ignore ownership, as far as I can see, is no longer an option under Sharing & Permissions. I recall some one saying this was so, but at the time I did not pay enough attention to the remark.
-
Error 8201 (Database version not available) during ODatabase() in VC++
Hello all,
I'm Beginner and i think i have a stupid problem,
when i execute under VC++ V6 SP5 (and IE 5.5 SP2) Under W98se :
OStartup();
ODatabase odb("essai","SYSTEM","manager"); // 'essai' is an existing database, no problem with sql*plus
if (!odb.IsOpen()) {
long err = odb.ErrorNumber();
char chaine[100];
sprintf(chaine,"Error n0=%ld",err);
::MessageBox(0,chaine,"DataBase",0);
Displaying 'Error n08201' : 'Database version not available' ???
PLEASE, THIS PROBLEM TURN ON MY MIND DURING ALL THIS WEEK-END AND I TEST, I RELEASE, I SEARCHE, AND NOTING...My Reponse from My Question :
It was so easy to run 'lsnrctl start'.
(Listen Module Manager).
2 days to find this.
VB doesn't work anymore.
I've executed an pre-compiled example 'login.exe' which display --> 'No Listen Module'.
Bye All. -
SOLVED - Servlet MessageBrokerServlet is not available on Ubuntu AMD64
Hello,
I have downloaded blazeds-bin-3.3.0.11688.zip and deployed blazeds.war on winXP tomcat 6.20.
There http://localhost:8080/blazeds/messagebroker/amf url in browser gives me blank screen as expected.
My production deployment will be Kubuntu 9.10 AMD 64 so I wanted to test same on it.
The installation for same is Kubuntu 9.10, tomcat 6.20 installed through repositories.
I deployed same .war in catalina/localhost but I get following error
Servlet MessageBrokerServlet is not available
instead of blankscreen as expected.
What might be wrong ?
Edited ------- 16 Nov 2009 22:08 (IST +5:30 GMT)
The Tomcat Log is As Follows. Hope Somebody will be able to decode this
16 Nov, 2009 10:05:39 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextDestroyed()
16 Nov, 2009 10:05:39 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextDestroyed()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.ApplicationContext log
INFO: Marking servlet MessageBrokerServlet as unavailable
16 Nov, 2009 10:05:47 PM org.apache.catalina.core.StandardContext loadOnStartup
SEVERE: Servlet /blazeds threw load() exception
javax.servlet.UnavailableException
at flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:170)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:115)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1167)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4149)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4458)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:123)
at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:145)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:769)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
Edited -------
Thanks and best regards.
Raja
Edited on 18 Nov 2009 13:50 IST (+5:30 GMT)
There is No Problem with either BlazeDS, Tomcat or Kubuntu OS as such.
The repository Install of Tomcat has the problem. What I did is as follows.
1. First I removed the repository Install of all Tomcat packages.
2. Downloaded the stable tar.gz distribution from Apache website.
3. Followed Instructions at this Link (states that repository Install of tomcat do not work properly.)
4. deployed the blazeds war on linux
5. Started Tomcat and tested http://localhost:8080/blazeds/messagebroker/amf
It gave me blank screen as expected.
Hope this helps to someone who stumbles on Ubuntu Linux Blazeds Installation.
Moderators may put this in FAQ section so that it helps Ubuntu Users.
Thanks and best Regards
RajaIt's not that hard to fix/work around, you just need to add a line in /etc/default/tomcat6, I just made a post about it.
http://eveliten.se/node/1
//Snigelkott -
Cluster Not Available error when booting OVM server DOM0 from USB
Hi all,
I have been wanting to run OVM 2.2 from a USB stick for a while now. I ran through the install CD today and saw there was a 'minimal USB install' option on the installation screen. So I plugged in a 4GB USB stick, rebooted, and ran the USB install.
After a while, the install completed, OVM booted up perfectly it seemed, and I was happy.
The server had no local storage apart from this USB stick as we are going to be hooking it up to an iSCSI target for guest VM storage.
This was a new lab setup, so I got the VM Manager running on another system, connected to the USB booted OVM server, and went to create a pool.
Running the 'test connection' that worked fine.
Trying to add the pool - failed. I got the error 'Cluster Not Available'
On the OVM server I did a repos.py -l and nothing gets listed.
I understand that for HA you need a repository with shared storage. However, before I have used these same install CDs with a singe local hard disk, to get OVM server running, and it did so fine.
So what's different with the USB disk install that means you don't get a repository?
Do I have to create a special repository LUN, manually connect the OVM server to this, and then use repos.py to create it?
Cheers,
JeffOk I have read, re-read related parts of the underground manual and have hit a brick wall with the 'simple' task of setting up a NIC for dedicated iSCSI traffic. The manual does not cover this task in the iSCSI SAN section.
So I'm in a catch 22.
My OVM server boots up, with it's single management NIC configured, but once booted - I don't want to connect to the iSCSI target via this network - I need it completely closed off.
I want to use another NIC (or bond of two) for dedicated iSCSI traffic to and from the OVM Server.
However, the underground manual strangely only seems to cover a single NIC configuration! It looks like he assumes you are going to be running iSCSI on your management NIC, which I can only think is incredibly bad practice.
I have installed OVM with the linux asknetwork - this did not give me the option to configure additional interfaces.
I then manually edited /etc/sysconfig/network-scripts/ifcfg-eth1 on the OVMServer, restarted network, restarted the entire box - I can ping my new NIC / IP locally from within the OVM server, but I can not connect to the iSCSI target, nor can I ping the iSCSI NIC on the OVM server from the target.
This is such a simple thing to try to achieve - super frustrating...
Jeff -
[solved] Large number of services enabled during first boot
I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.
To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.
Any ideas as to what might be causing this?
Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.
Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711
Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.
Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable [email protected].
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.
Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):
getty.target.wants:
* [email protected]
multi-user.target.wants:
* [email protected]
* iptables.service
* remote-fs.target
* sshd.service
sysinit.target.wants:
(none)
Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):
default.target.wants:
* systemd-readahead-collect.service
* systemd-readahead-replay.service
multi-user.target.wants:
* dhcpcd.service * krb5-kpropd.service
* fstrim.service * nscd.service
* ftpd.service * rsyncd.service
* gpm.service * systemd-journal-upload.service
* ip6tables.service * systemd-networkd.service
* krb5-kadmind.service * systemd-resolved.service
* krb5-kdc.service
sockets.target.wants:
* krb5-kpropd.socket * systemd-journal-remote.socket
* rlogin.socket * talk.socket
* rsh.socket * telnet.socket
* rsyncd.socket * uuidd.socket
* sshd.socket
sysinit.target.wants:
* dm-event.service
* systemd-timesyncd.service
system-update.target.wants:
* systemd-readahead-drop.service
Explicitly installed packages:
dhcpcd iputils procps-ng systemd-sysvcompat
diffutils linux-grsec psmisc tar
dnsutils logrotate reflector vim-systemd
file mlocate rsync wget
gradm mtr s-nail which
grub openssh screen whois
inetutils pacman
Last edited by tazmanian (2014-09-10 23:11:42)+1.
Here is the ports these services are listening:
$ ss -tpl
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 *:llmnr *:*
LISTEN 0 128 *:ssh *:*
LISTEN 0 128 :::llmnr :::*
LISTEN 0 128 :::19532 :::*
LISTEN 0 128 :::tell :::*
LISTEN 0 128 :::ssh :::*
LISTEN 0 128 :::telnet :::*
LISTEN 0 128 :::login :::*
LISTEN 0 128 :::shell :::*
LISTEN 0 128 :::rsync :::*
LISTEN 0 128 :::git :::* -
Drop Ship across OUs - Operating Unit not available during Requisition Import
Hi,
I am trying to execute Drop Shipment across OUs on Vision Instance R12.1.1.
1) Responsibility - Order Management Super User, Vision Operations (USA)
Create SO in Vision Operations. In Others tab selected Warehouse as D1 ( Singapore Distribution Centre ). Line Item Source Type is External.
Order Booked. Order line status is 'Awaiting Receipt'.
2) Responsibility - Purchasing Super User.
Request - Requisition Import.
Issue - The Operating Unit LOV for Requisition Import is listing only 'Vision Operation'. The OU 'Singapore Distribution Centre' is not listed.
The responsibility Purchasing Super User has access to Org D1.
Please refer to attached screenshots for details.
Kindly help me with this process.user12214874 wrote:
We are on Oracle EBS 11.5.10 and the requirement is that the US OU wants to drop ship a SO from our supplier in Japan(not part of Oracle installation) directly to our OU in Canada. (part of same Oracle installation). As per as per Oracle Order management users guide 11i; pg 1-7 drop ship across OU's and SOB's is possible. (Introduction chapter.) However when I read metalink note 225434.1, this is not possible. This looks to be a drawback with Oracle EBS since it is a very common requirement with most business going global these days. However, I may be wrong and the flow might very well be supported. If anybody has an idea, and provide some insights if this is supported in oracle or if there is a workaround available it would be appreciated.
*****Update******** I could create a Drop Ship So with Receiving Warehouse in another operating unit; I could also create the Internal Requistion and PO in the shipping OU. Also, the Payables Invoices to Selling OU was created. AR invoice against the Drop SO billed to Shipping OU was created. However I am still stuck as to the generation of Intercompany AR invoice. Also, I am wondering why is there a need for Intercompany AR invoice when the AR invoice is issued against the Drop SO?
Edited by: user12214874 on Feb 16, 2012 12:34 PMMy question is why would US OU want to drop ship to Canada OU...why can't canada OU directly raise a PO to a supplier in Japan?? -
DTD not available during deployment
Hello
We had a problem that during the deployment of our ear, some dtd's of struts where not accessible on the internet. It seems that xml files are validated, during deployment, so the application was not deployed properly.
Is there a way to either :
- configure the container that no validatio should be done when deploying the ear
- put the dtd in the application itself, so we don't depend on the struts site wether we can deploy or not
grtz
Chris.The problem is I am trying to use JavaMail in an EJB and it gives me the error if I create a javax.mail.Session. If I comment out the Session, deployment is fine. I am thinking that maybe the problem is I am using 8i version 8.1.5 and it only supports java 1.1.8.
-
[solved] Module usb-eth not available
Hi everyone,
I am using Arch for about a week now and must say that I love it. Before I was using Ubuntu for half a year and earlier Gentoo.
So now to my question. Our router at home is a FritzBox SL that has one USB port and one LAN port. Ubuntu had a module called "usb-eth" that enabled a device eth1 and let me connect to the internet. Any ideas how to find that? I couldn't find it in usb documentation of the arch kernel.
Thanks in advance
David
EDIT: solved. the module is called cdc_ether, everything works fine.
Last edited by dcrabs (2008-12-01 19:56:50)vilefridge wrote:And now 2.6.28.3-1. Haven't tried either yet since, I too, became frustrated with upgrading and downgrading. If nobody else can confirm, I will give it a go this weekend.
Thanx, I'm waiting for your report :)
EDIT: I have found solution for me. I'm using Logitech USB Keyboard, so I have done this steps:
1] Upgrade mkinitcpio to 0.5.23-1
2] cd /lib/initcpio/install
3] cp usbinput usbinput.backup
4] vim usbinput
and add this: MODULES="${MODULES} hid-logitech" (you will probably need another hid module, depend on your keyboard - try ls /lib/modules/2.6.27-ARCH/kernel/drivers/hid) after line with MODULES=" $(checked_modules "/usb/host ..." and save it.
5] pacman -S kernel26 (I'm using 2.6.28.2)
6] reboot :)
Good luck!
Last edited by lian (2009-02-03 01:30:47) -
[SOLVED] pacman error: database not found (during an install)
i am trying to install an app
when installing
# pacman -S /path/to/dir/app.tar.gz
error: database not found
when i look inside the tar, theres only one file, app.bin
im sure its some fundamental that im missing. so i have to makepkg first , or am i missing a command during the intallation, or is the file broken?
Last edited by wolfdogg (2011-06-04 05:50:09)well, im geting some errors with the program, im wondering if i need to make a package? i think i will try that next.
heres the beginning of the log, Java errors mainly
eclipse.buildId=unknown
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86
!ENTRY org.eclipse.equinox.ds
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: org.eclipse.equinox.internal.util.event; version="1.0.0"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)
ok, i downloaded a different binary of this program, and it installed successfully. thanks for the help
Last edited by wolfdogg (2011-06-04 05:49:37)
Maybe you are looking for
-
Not sure why I am getting this message anyway. I wasn't trying to buy anything. I just upgraded and then I tried to access the store. I had two purchases that I had previously made from a different computer. I was going to download them to this compu
-
Cannot use Standby option on my Satellite Pro P200
Hi I have installed XP SP2 on my P200, but it can not go into standby, it says something about RAM parity check or something? What can be wrong? Standby in Vista works fine. *Hardware malfunction* *Call your hardware vendor for support* *nmi: parity
-
When pressing the power button to start- front white led lights up & doesn't blink at any point. The chime can be heard and it tries to boot with no graphics output. The fans spin up as normal, but after some time a red led on the board behind the CP
-
Why does Twitter operate and look inferior on Firefox when compared to Internet Explorer?
When I send a Tweet on Twitter on Firefox, my server said that the message could not be delivered when in fact is was. The layout of Twitter also looks and acts differently when I use Internet Explorer (it is superior.) My friend was having such a ha
-
Remove the close button in upper right corner
How do I remove the close button in the upper right corner?