EVMS 2.5.5 questions

[thomas62186218]

Hi all,

I have been using EVMS 2.5.5 on Fedora 7 x64 with great success for a
while now, but I've been collecting some questions along the way that I
cannot seem to find online answers for. I look forward to any insight
from the EVMS community. Thank you in advance!

1) Is there a way, from the EVMS CLI, to find out the % full of a
snapshot? I've run a query:region command on the snapshot region, but
I'm not getting anything there about the % full. (attached is the dump
from the query command)

2) Similarly, is there a way to get a % full on an EVMS volume, even if
there is no file system on it?

3) What method does the snapshot feature use? Is it copy on write, or
something else?

4) When starting EVMS, the EVMS engine log gets full of messages about
failed plug-in loads and failing to open /dev/evms/.nodes/ram devices
(see attached). Is there a way to suppress these messages, maybe
through some setting in evms.conf? Or another way?

5) A previous RAID 6 plug-in for EVMS 2.5.3 was posted by an EVMS
community member. Have people been able to use this with success? I've
noticed that it does seem to work..sort of. Often, volumes created on
RAID 6 regions become deactivated for some reason (don't know why), and
need to be manually reactivated. This does not happen with any other
RAID types.

6) Launching EVMS from the CLI gets slower and slower as more objects
(volumes, regions, etc) are created. Is there any way around this? It
can take 10 seconds or more to start EVMS from the CLI, if I have 30
volumes or more.

Thank you in advance for any input!

EVMS Command Line Interpreter Version 2.5.5

EVMS: query:regions,region="lvm2/vmwarepool2/RegSNAP__snap1b",lo

Region Name: lvm2/vmwarepool2/RegSNAP__snap1b
Major: 254
Minor: 40
Active: TRUE
Region Size: 2.00 GB
Region Type: Data

This region may be used to produce a volume with the Create command.

This region may be deleted using the Delete command.

This region may be used to produce a storage object with the Create command.

This region may be used to produce a container with the Create command.

This region may be used to produce another region with the Create command.

The following options for this region may be changed:
Option Name: name
Description: (null)
Option Type: Character String
The current value for this option is not available.

This region may be expanded using the Expand command.
The following options are available for expanding this region:
Option Name: size
Description: Extra size must be a multiple of the container's extent-size and
cannot exceed the amount of freespace in the container. If not, it will be
rounded down as appropriate.
Option Type: A 64 bit positive integer number.
The current value is: 1385431040
Option Name: stripes
Description: One stripe implies a linear region. Number of stripes cannot exceed
the number of objects consumed by the container.
Option Type: A 64 bit positive integer number.
The current value is: 1
Option Name: stripe_size
Description: Size of each stripe "chunk". Only available when "stripes" option
is greater than 1.
Option Type: A 64 bit positive integer number.
The current value is: 0
Option Name: pvs
Description: Region will be expanded only onto these objects. Leave blank for
automatic allocation.
Option Type: Character String
The current value is:

This region may be shrunk using the Shrink command.
The following options are available for shrinking this region:
Option Name: size
Description: Removed size must be a multiple of the container's extent-size. If
not, it will be rounded down as appropriate.
Option Type: A 64 bit positive integer number.
The current value is: 65536

The following plug-in defined tasks are available for this disk:
Task Name:  split_mapping
Task Title: Split Mapping
Task Description: Split one physically contiguous logical-mapping into two
mappings.

The following options are available for this task:
Option Name: mapping
Description: Display extended details for this region to see information about
the mappings and determine which mapping you wish to split.
Option Type: A 32 bit positive integer number.
The current value is: 0
Option Name: extent
Description: Display extended details for this region to determine where within
this mapping to make the split.
Option Type: A 64 bit positive integer number.
The current value is: 1

Task Name:  move_mapping
Task Title: Move Mapping
Task Description: Move a logical portion of the region from its current physical
location to a different physical location.

The following options are available for this task:
Option Name: mapping
Description: Display extended details for this region to see information about
the mappings and determine which mapping you wish to move.
Option Type: A 32 bit positive integer number.
The current value is: 0
Option Name: stripe
Description: Only one stripe per mapping can be moved at a time. Display
extended details for this region to see information about the mappings and
determine which stripe within this mapping you wish to move.
Option Type: A 64 bit positive integer number.
The current value is: 0
Option Name: object
Description: Display extended details for this region's container and PVs to
determine which PV has space available to move this mapping.
Option Type: Character String
The current value is: md/md1
Option Name: extent
Description: Display extended details for this region's container and the
selected PV object to determine where within the PE-map has space available to
move this mapping.
Option Type: A 64 bit positive integer number.
The current value is: 1216
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: Engine version:           2.5.5
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: External API version:    10.1.0
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: Engine services version: 15.0.0
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: Plug-in API version:     13.1.0
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: Container API version:   10.1.0
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: FSIM API version:        11.0.0
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: Cluster API version:      1.0.0
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: Daemon protocol version:  5.1.0
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: Requested open mode is 0x3. ENGINE_READ ENGINE_WRITE
Mar 11 09:28:12 fedorabox _5_ Engine: evms_open_engine: Open mode is 0x3. ENGINE_READ ENGINE_WRITE
Mar 11 09:28:12 fedorabox _5_ Engine: dm_check_version: Device-Mapper interface version: 4.11.0
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/bsd-1.0.9.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  BSD
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   BSD Segment Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.9
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/ntfs-1.0.3.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  NTFS
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   NTFS File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.3
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/jfs-1.1.15.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  JFS
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   JFS File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.15
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/ogfs-1.0.5.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  OGFS
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   OpenGFS File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.5
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/ocfs2-1.0.0.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  OCFS2
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   OCFS2 File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.0
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/bbr_seg-1.1.13.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  BBRseg
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Bad Block Relocation Segment Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.13
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/bbr-1.1.15.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  BBR
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Bad Block Relocation Feature
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.15
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/drivelink-3.0.6.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  DriveLink
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Drive Linking Feature
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     3.0.6
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/lvm-1.1.15.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  LvmRegMgr
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   LVM Region Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.15
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/csm-1.0.13.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  CSM
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Cluster Segment Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.13
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/error-1.0.2.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  Error
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Error Device Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.2
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/gpt-1.1.12.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  GptSegMgr
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   GPT Segment Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.12
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/dos-1.1.16.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  DosSegMgr
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   DOS Segment Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.16
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/snapshot-3.1.11.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  Snapshot
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Snapshot Feature
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     3.1.11
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/fat-1.0.0.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  FAT32
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   FAT32 File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.0
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/fat-1.0.0.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  FAT16
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   FAT16 File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.0
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/multipath-1.0.4.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  Multipath
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Multipath Segment Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.4
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/replace-1.1.3.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  Replace
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   EVMS Replace
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.3
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/mac-1.0.9.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  MAC
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   MAC Segment Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.9
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/disk-1.2.13.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  LocalDskMgr
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Local Disk Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.2.13
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/md-1.1.20.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  MDLinearRegMgr
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   MD Linear Raid Region Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.20
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/md-1.1.20.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  MDRaid1RegMgr
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   MD Raid 1 Region Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.20
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/md-1.1.20.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  MDRaid0RegMgr
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   MD RAID0 Region Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.20
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/md-1.1.20.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  MDRaid5RegMgr
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   MD RAID 4/5/6 Region Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.20
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/md-1.1.20.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  MD Multipath
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   MD Multipath Region Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.20
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/swap-1.1.13.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  SWAPFS
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Swap File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.13
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/lvm2-1.0.5.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  LVM2
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   LVM2 Region Manager
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.5
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/reiser-1.1.15.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  ReiserFS
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   ReiserFS File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.15
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/xfs-1.0.12.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  XFS
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   XFS File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.0.12
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins: Loaded from /usr/evms/lib/evms/2.5.5/ext2-1.1.13.so.
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   short name:  Ext2/3
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   long name:   Ext2/3 File System Interface Module
Mar 11 09:28:12 fedorabox _5_ Engine: load_module_plugins:   version:     1.1.13
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ NTFS: try_run_get_version: "mkntfs -V" completed with exit code 2.
Mar 11 09:28:12 fedorabox _5_ NTFS: try_run_get_version: mkntfs version is (none)
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ NTFS: try_run: "ntfsfix -V" completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ NTFS: try_run: "ntfsinfo -V" completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ NTFS: try_run: "ntfsclone -V" completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ NTFS: try_run: "ntfsresize -V" completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ JFS: fsim_test_version: mkfs.jfs test version completed with exit code 2
Mar 11 09:28:12 fedorabox _5_ JFS: fsim_test_version: JFS utilities version: (none)
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _2_ OGFS: ogfs_exec_utility: mkfs.ogfs completed with exit code 2
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ Bad plug-in pointer: try_run: mkdosfs completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ Bad plug-in pointer: try_run: dosfsck completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ Bad plug-in pointer: try_run: fatresize completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ Bad plug-in pointer: try_run: mkdosfs completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ Bad plug-in pointer: try_run: dosfsck completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _5_ Bad plug-in pointer: try_run: fatresize completed with exit code 2.
Mar 11 09:28:12 fedorabox _3_ Engine: do_fork_and_execvp: execvp() failed.  errno is 2: No such file or directory
Mar 11 09:28:12 fedorabox _3_ ReiserFS: reiser_setup: ReiserFS utils were either not found or not at the proper version.
Mar 11 09:28:12 fedorabox _3_ ReiserFS: reiser_setup: The fsck and mkfs utilities must be installed using the standard names
Mar 11 09:28:12 fedorabox _3_ ReiserFS: reiser_setup: of mkreiserfs and reiserfsck.
Mar 11 09:28:12 fedorabox _3_ ReiserFS: reiser_setup: ReiserFS utils must be version 3.x.0 or later to function properly with this FSIM.
Mar 11 09:28:12 fedorabox _3_ ReiserFS: reiser_setup: Please get the current version of ReiserFS utils from http://www.namesys.com
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram0 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram1 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram10 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram11 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram12 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram13 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram14 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram15 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram2 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram3 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram4 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram5 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram6 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram7 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram8 failed with error code 22: Invalid argument
Mar 11 09:28:12 fedorabox _3_ Engine: engine_open_object: Open of /dev/evms/.nodes/ram9 failed with error code 22: Invalid argument
Mar 11 09:28:13 fedorabox _3_ LVM2: check_pv_size: Object lvm2/vmwarepool/Regxenservervol recorded size (146821246) does not match actual size (146800640)
Mar 11 09:28:14 fedorabox _5_ Engine: initial_discovery: Discovery time: 00:00:02.163695
Mar 11 09:29:03 fedorabox _2_ Engine: isa_valid_task: Command 7 cannot be targeted at an object.
Mar 11 09:29:03 fedorabox _2_ Engine: isa_valid_task: Command 8 cannot be targeted at an object.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel

[LeJacq, Jean Pierre]

On Tuesday 2008-03-11 12:40:47 thomas62186218@... wrote:
>
> 4) When starting EVMS, the EVMS engine log gets full of messages about
> failed plug-in loads and failing to open /dev/evms/.nodes/ram devices
> (see attached). Is there a way to suppress these messages, maybe
> through some setting in evms.conf? Or another way?

I can help with this one. You can suppress these messages by preventing evms
from trying to activate devices like ram. Take a look at the activate,
legacy_devices, and sysfs_devices sections in /etc/evms.conf. I usually
disable all legacy devices and list only the devices I have in sysfs and
activate sections.

--
JP


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel

[Dirk Heinrichs-3]

Am Dienstag, 11. März 2008 schrieb ext
evms-devel-bounces@...:

> 2) Similarly, is there a way to get a % full on an EVMS volume, even if
> there is no file system on it?

% full with what? No fs, no data.

Bye...

        Dirk
--
Dirk Heinrichs          | Tel:  [phone]
Configuration Manager   | Fax:  [phone]
Capgemini Deutschland   | Mail: dirk.heinrichs@...
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel

[thomas62186218]

Hi Dirk, thanks for the note. You can still have data on volumes even
without a file system. For example, I store SQL databases on raw, file
system-less EVMS volumes. But I'll assume from your response, it will
be difficult to determine utilization without a file system.

Can you share your thoughts/experience on the other queries I raised?
Thanks again everyone!


-----Original Message-----
From: Dirk Heinrichs <dirk.heinrichs.ext@...>
To: evms-devel@...
Sent: Tue, 11 Mar 2008 11:58 pm
Subject: Re: [Evms-devel] EVMS 2.5.5 questions










Am Dienstag, 11. März 2008 schrieb ext
evms-devel-bounces@...:

> 2) Similarly, is there a way to get a % full on an EVMS volume, even
if
> there is no file system on it?

% full with what? No fs, no data.

Bye...

    Dirk
--
Dirk Heinrichs          | Tel:  [phone]
Configuration Manager   | Fax:  [phone]
Capgemini Deutschland   | Mail: dirk.heinrichs@...
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net









-------------------------------------------------------------------------

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/









_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel






-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel

[Dirk Heinrichs-3]

Am Mittwoch, 12. März 2008 schrieb ext thomas62186218@...:

> Hi Dirk, thanks for the note. You can still have data on volumes even
> without a file system. For example, I store SQL databases on raw, file
> system-less EVMS volumes. But I'll assume from your response, it will
> be difficult to determine utilization without a file system.

In this case, EVMS would need to have knowledge about how the database
system stores its data.

Bye...

        Dirk
--
Dirk Heinrichs          | Tel:  [phone]
Configuration Manager   | Fax:  [phone]
Capgemini Deutschland   | Mail: dirk.heinrichs@...
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel

[thomas62186218]

Hi all,

Just wanted to reach out again and see if anyone out there had any
insights on my queries below (besides #2 which had been
addressed).....thanks!

-Thomas


-----Original Message-----
From: thomas62186218@...
To: evms-devel@...; thomas62186218@...
Sent: Tue, 11 Mar 2008 9:40 am
Subject: EVMS 2.5.5 questions

Hi all,


I have been using EVMS 2.5.5 on Fedora 7 x64 with great success for a
while now, but I've been collecting some questions along the way that I
cannot seem to find online answers for. I look forward to any insight
from the EVMS community. Thank you in advance!


1) Is there a way, from the EVMS CLI, to find out the % full of a
snapshot? I've run a query:region command on the snapshot region, but
I'm not getting anything there about the % full. (attached is the dump
from the query command)


2) Similarly, is there a way to get a % full on an EVMS volume, even if
there is no file system on it?


3) What method does the snapshot feature use? Is it copy on write, or
something else?


4) When starting EVMS, the EVMS engine log gets full of messages about
failed plug-in loads and failing to open /dev/evms/.nodes/ram devices
(see attached). Is there a way to suppress these messages, maybe
through some setting in evms.conf? Or another way?


5) A previous RAID 6 plug-in for EVMS 2.5.3 was posted by an EVMS
community member. Have people been able to use this with success? I've
noticed that it does seem to work..sort of. Often, volumes created on
RAID 6 regions become deactivated for some reason (don't know why), and
need to be manually reactivated. This does not happen with any other
RAID types.


6) Launching EVMS from the CLI gets slower and slower as more objects
(volumes, regions, etc) are created. Is there any way around this? It
can take 10 seconds or more to start EVMS from the CLI, if I have 30
volumes or more.


Thank you in advance for any input!






-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel

[Andrew Schulman-4]

> 3) What method does the snapshot feature use? Is it copy on write, or
> something else?

The EVMS manual, sections 11.1 and 11.2
(http://evms.sourceforge.net/user_guide/#whatissnapshotting), implies that the
method is copy-on-write.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel

[thomas62186218]

Hi all,

Thought I would try again regarding some EVMS questions I have below.
Any guidance would be hugely appreciated!

1) Is there a way, from the EVMS CLI, to find out the % full of a
snapshot? I've run a query:region command on the snapshot region, but
I'm not getting anything there about the % full.

2) A previous RAID 6 plug-in for EVMS 2.5.3 was posted by an EVMS
community member. Have people been able to use this with success? I've
noticed that it does seem to work..sort of. Often, volumes created on
RAID 6 regions become deactivated for some reason (don't know why), and
need to be manually reactivated. This does not happen with any other
RAID types.


3) Launching EVMS from the CLI gets slower and slower as more objects
(volumes, regions, etc) are created. Is there any way around this? It
can take 10 seconds or more to start EVMS from the CLI, if I have 30
volumes or more.


Thank you in advance for any input!






-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel

[Steve Dobbelstein]

thomas62186218@... wrote on 04/26/2008 08:42:59 PM:

> Hi all,

Hi, Thomas.

> Thought I would try again regarding some EVMS questions I have below.
> Any guidance would be hugely appreciated!
>
> 1) Is there a way, from the EVMS CLI, to find out the % full of a
> snapshot? I've run a query:region command on the snapshot region, but
> I'm not getting anything there about the % full.

If you are using the EVMS snapshot feature, query:object will display the % full as part of the information about the object.

I took a quick look through the code for the LVM and LVM2 plug-ins and did not see any code for returning the % full.  I also didn't see any fields in the headers that would track the % full.  I am no LVM expert, but it may be that LVM does not keep track of the % full for a snapshot.

> 2) A previous RAID 6 plug-in for EVMS 2.5.3 was posted by an EVMS
> community member. Have people been able to use this with success? I've
> noticed that it does seem to work..sort of. Often, volumes created on
> RAID 6 regions become deactivated for some reason (don't know why), and
> need to be manually reactivated. This does not happen with any other
> RAID types.

The RAID 6 plug-in that was posted was a good start, but it lacks some key functionality, which is why it hasn't been checked in to the CVS tree.  For example, it doesn't properly handle the case when a RAID 6 region already exists and is active.  From what I remember, it does the right thing when creating a brand new RAID 6 region, so a new RAID 6 region should work properly.  I am not surprised that it might have issues with an existing RAID 6 region.

A while back I had started on filling out the RAID 6 plug-in, but that work has been put on the shelf due to my current responsibilities. :(

> 3) Launching EVMS from the CLI gets slower and slower as more objects
> (volumes, regions, etc) are created. Is there any way around this? It
> can take 10 seconds or more to start EVMS from the CLI, if I have 30
> volumes or more.

Do you seen the same slowdown if you run evmsn or evmsgui?  I suspect so since all the user interfaces call the same Engine to do the discovery of the disk configuration.  If you don't see a slowdown in the other user interfaces, then something is slowing down in the CLI itself.

Discovery is a complex, iterative process.  (Check out engine/discover.c if you want to know the details. :) )  The discovery process naturally takes longer as the number of things (disks, segments, regions, EVMS object, volumes) increases since there are more things to examine.  It can also take longer if the number of things and the way they are structured leads to more iterations.  Plus, each examination of a thing results in a read from the disk(s), so the speed of the disk access also plays a part in the discovery time.  The discovery process does keep a cache of sectors read from the disks, which helps speed up the process.

> Thank you in advance for any input!

Hope this helps.

Steve D.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Evms-devel mailing list
Evms-devel@...
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel