Package: evms
Version: 2.5.0-1
Severity: important
I have installed evms on a 2.6.10 system while it was busy
reconstructing a plain kernel-based md0 device (root device). After restart
(reconstruction was not completed) the EVMS service was not able to
start, it was just discovering and discovering. I hit Ctrl-C and the
boot continued. After reconstruction finished, EVMS was able to start.
This is now only annoying but if a drive fails and reconstruction has to
be made, then user-intervention is required to start up the machine
fast. And without evms running I guess my evms-based volumes will not be
usable till reconstruction of root finished.
Regards,
Akos
-- Package-specific info:
engine log:
-----------
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: Engine version:
2.5.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: External API
version: 10.1.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: Engine services
version: 15.0.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: Plug-in API
version: 13.1.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: Container API
version: 10.1.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: FSIM API
version: 11.0.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: Cluster API
version: 1.0.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: Daemon protocol
version: 5.1.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: Requested open
mode is 0xffffffff. (default)
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: evms_open_engine: Open mode is
0x3. ENGINE_READ ENGINE_WRITE
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: dm_check_version: Device-Mapper
interface version: 4.3.0
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/swap-1.1.12.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: SWAPFS
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Swap File System Interface Module
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.12
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/multipath-1.0.2.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: Multipath
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Multipath Segment Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.2
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/xfs-1.0.11.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: XFS
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
XFS File System Interface Module
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.11
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/error-1.0.1.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: Error
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Error Device Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.1
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/reiser-1.1.13.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: ReiserFS
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
ReiserFS File System Interface Module
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.13
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/drivelink-3.0.5.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: DriveLink
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Drive Linking Feature
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
3.0.5
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/lvm-1.1.12.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: LvmRegMgr
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
LVM Region Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.12
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/ntfs-1.0.1.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: NTFS
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
NTFS File System Interface Module
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.1
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/dos-1.1.13.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: DosSegMgr
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
DOS Segment Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.13
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/bbr_seg-1.1.11.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: BBRseg
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Bad Block Relocation Segment Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.11
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/gpt-1.1.10.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: GptSegMgr
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
GPT Segment Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.10
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/replace-1.1.1.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: Replace
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
EVMS Replace
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.1
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/ext2-1.1.12.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: Ext2/3
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Ext2/3 File System Interface Module
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.12
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/csm-1.0.11.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: CSM
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Cluster Segment Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.11
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/mac-1.0.7.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: MAC
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
MAC Segment Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.7
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/bbr-1.1.13.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: BBR
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Bad Block Relocation Feature
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.13
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/ogfs-1.0.4.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: OGFS
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
OpenGFS File System Interface Module
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.4
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/bsd-1.0.7.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: BSD
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
BSD Segment Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.7
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/lvm2-1.0.2.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: LVM2
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
LVM2 Region Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.0.2
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/jfs-1.1.14.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: JFS
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
JFS File System Interface Module
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.14
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/disk-1.2.10.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: LocalDskMgr
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Local Disk Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.2.10
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/md-1.1.16.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: MDLinearRegMgr
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
MD Linear Raid Region Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.16
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/md-1.1.16.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: MDRaid1RegMgr
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
MD Raid 1 Region Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.16
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/md-1.1.16.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: MDRaid0RegMgr
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
MD Raid 0 Region Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.16
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/md-1.1.16.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: MDRaid5RegMgr
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
MD RAID 4/5 Region Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.16
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/md-1.1.16.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: MD Multipath
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
MD Multipath Region Manager
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
1.1.16
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: Loaded from
/lib/evms/2.5.0/snapshot-3.1.9.so.
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: short
name: Snapshot
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: long name:
Snapshot Feature
Jan 27 02:45:19 debian.ilogic.int _5_ Engine: load_module_plugins: version:
3.1.9
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: do_fork_and_execvp: execvp()
failed. errno is 2: No such file or directory
Jan 27 02:45:19 debian.ilogic.int _5_ NTFS: try_run_get_version: "mkntfs -V"
completed with exit code 0.
Jan 27 02:45:19 debian.ilogic.int _5_ NTFS: try_run_get_version: mkntfs version
is 1.9.2
Jan 27 02:45:19 debian.ilogic.int _5_ NTFS: try_run: "ntfsfix -V" completed
with exit code 1.
Jan 27 02:45:19 debian.ilogic.int _5_ NTFS: try_run: "ntfsinfo -V" completed
with exit code 1.
Jan 27 02:45:19 debian.ilogic.int _5_ NTFS: try_run: "ntfsclone -V" completed
with exit code 1.
Jan 27 02:45:19 debian.ilogic.int _5_ NTFS: try_run: "ntfsresize -V" completed
with exit code 1.
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: do_fork_and_execvp: execvp()
failed. errno is 2: No such file or directory
Jan 27 02:45:19 debian.ilogic.int _2_ OGFS: ogfs_exec_utility: mkfs.ogfs
completed with exit code 2
Jan 27 02:45:19 debian.ilogic.int _5_ JFS: fsim_test_version: mkfs.jfs test
version completed with exit code 0
Jan 27 02:45:19 debian.ilogic.int _5_ JFS: fsim_test_version: JFS utilities
version: 1.1.7
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram0 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram1 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram10 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram11 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram12 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram13 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram14 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram15 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram2 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram3 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram4 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram5 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram6 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram7 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram8 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _3_ Engine: engine_open_object: Open of
/dev/evms/.nodes/ram9 failed with error code 22: Invalid argument
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(2) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(3) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(4) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(5) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(6) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(7) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(8) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(9) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(10) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(11) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(12) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(13) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(14) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(15) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(16) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(17) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(18) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(19) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(20) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(21) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(22) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(23) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(24) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(25) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Superblock has disk number(0) major(0) minor(0) raid_disk(0) state(0x00000000)
Jan 27 02:45:19 debian.ilogic.int _5_ MDRaid1RegMgr: md_sync_sbs: [md/md0]
Kernel has disk number(26) major(0) minor(0) raid_disk(-1) state(0x00000008)
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=2) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=3) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=4) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=5) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=6) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=7) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=8) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=9) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=10) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=11) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=12) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=13) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=14) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=15) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=16) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=17) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=18) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=19) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=20) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=21) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=22) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=23) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=24) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=25) had been removed
Jan 27 02:45:19 debian.ilogic.int _3_ MDRaid1RegMgr: md_analyze_volume: Disk
(index=26) had been removed
Jan 27 02:45:19 debian.ilogic.int _2_ Engine: isa_valid_anchor: List is NULL.
Jan 27 02:45:20 debian.ilogic.int _5_ Engine: initial_discovery: Discovery
time: 00:00:00.473695
Jan 27 02:45:28 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:28 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:28 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:28 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:39 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:39 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:39 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:39 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:53 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:53 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:53 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:45:53 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:46:08 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:46:08 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:46:08 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:46:08 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:46:28 debian.ilogic.int _3_ Engine: evms_create_task: Error
initializing options.
Jan 27 02:46:28 debian.ilogic.int _3_ Engine: free_option_descriptor_contents:
Collection says it has a list but the list pointer is NULL.
Jan 27 02:46:32 debian.ilogic.int _5_ Engine: is_object_change_pending: Change
pending: Object hde_mbr is dirty.
Jan 27 02:46:32 debian.ilogic.int _5_ Engine: is_object_change_pending: Change
pending: Object hde2 needs to be activated.
Jan 27 02:46:32 debian.ilogic.int _5_ Engine: is_object_change_pending: Change
pending: Object hdg_mbr is dirty.
Jan 27 02:46:32 debian.ilogic.int _5_ Engine: is_object_change_pending: Change
pending: Object hdg2 needs to be activated.
Jan 27 02:46:33 debian.ilogic.int _5_ Engine: is_object_change_pending: Change
pending: Object hde_mbr is dirty.
Jan 27 02:46:33 debian.ilogic.int _5_ Engine: is_object_change_pending: Change
pending: Object hde2 needs to be activated.
Jan 27 02:46:33 debian.ilogic.int _5_ Engine: is_object_change_pending: Change
pending: Object hdg_mbr is dirty.
Jan 27 02:46:33 debian.ilogic.int _5_ Engine: is_object_change_pending: Change
pending: Object hdg2 needs to be activated.
EVMS Command Line Interpreter Version 2.5.0
Plug-in ID: 531652618
Full Name: Swap File System Interface Module
Short Name: SWAPFS
OEM: IBM
Version 1.1.12
This plug-in can be used to format a volume for use with the SWAPFS filesystem.
When used to format a volume, this plug-in supports the following options:
Option Name: badblocks
Description: Check for bad blocks when making swap space
Option Type: TRUE or FALSE
Plug-in ID: 531636233
Full Name: Multipath Segment Manager
Short Name: Multipath
OEM: IBM
Version 1.0.2
Plug-in ID: 531652619
Full Name: XFS File System Interface Module
Short Name: XFS
OEM: IBM
Version 1.0.11
XFS: xfsutils were either not found or not at the proper version. xfsutils must
be version 2.0.0 or later to function properly with this FSIM. xfsutils must
also reside in the search path specified by PATH. Please get/install the current
version of xfsutils from http://oss.sgi.com/projects/xfs
The EVMS Command Line Interpreter is processing a command file - therefore user
interaction is not allowed. Thus, the EVMS Command Line Interpreter has
accepted the default choice. The default choice is: Ok
Plug-in ID: 531632131
Full Name: Error Device Manager
Short Name: Error
OEM: IBM
Version 1.0.1
This plug-in is used to create Logical Disks.
This plug-in supports the following options when creating Logical Disks:
Option Name: name
Description: (null)
Option Type: Character String
Option Name: size
Description: (null)
Option Type: A 64 bit positive integer number.
Option Name: type
Description: (null)
Option Type: Character String
Plug-in ID: 531652617
Full Name: ReiserFS File System Interface Module
Short Name: ReiserFS
OEM: IBM
Version 1.1.13
This plug-in can be used to format a volume for use with the ReiserFS
filesystem. When used to format a volume, this plug-in supports the following
options:
Option Name: version
Description: Informational only: this is the current version of ResierFS
utitlities found on your system.
Option Type: Character String
Option Name: vollabel
Description: Set the volume label for the file system.
Option Type: Character String
Option Name: logsize
Description: Set log size (in kilobytes). Default log size is 8193 4k Blocks.
Option Type: A 32 bit positive integer number.
Plug-in ID: 531644417
Full Name: Drive Linking Feature
Short Name: DriveLink
OEM: IBM
Version 3.0.5
This plug-in is used to create EVMS Objects.
This plug-in supports the following options when creating EVMS Objects:
Option Name: Name
Description: The name to be given to the drivelink object.
Option Type: Character String
Plug-in ID: 531640321
Full Name: LVM Region Manager
Short Name: LvmRegMgr
OEM: IBM
Version 1.1.12
This plug-in is used to create Regions.
This plug-in supports the following options when creating Regions:
Option Name: name
Description: (null)
Option Type: Character String
Option Name: extents
Description: Extents are the unit of allocation of space for LVM regions.
Specify number of Extents, and Size will be adjusted accordingly.
Option Type: A 32 bit positive integer number.
Option Name: size
Description: Specify Size, and the number of Extents will be adjusted
accordingly.
Option Type: A 32 bit positive integer number.
Option Name: stripes
Description: Number of objects (PVs) to use in a striped volume. Leave at 1 for
a linear volume.
Option Type: A 32 bit positive integer number.
Option Name: stripe_size
Description: Granularity at which data is striped across the underlying objects.
Option Type: A 32 bit positive integer number.
Option Name: pv_names
Description: Region will be allocated on only these objects. Leave blank for
automatic allocation.
Option Type: Character String
This plug-in can be used to create containers.
This plug-in, when used to create containers, supports the following options:
Option Name: name
Description: (null)
Option Type: Character String
Option Name: pe_size
Description: Acceptable range: 8kB to 16GB. Must be a power of 2.
Option Type: A 32 bit positive integer number.
Plug-in ID: 531652621
Full Name: NTFS File System Interface Module
Short Name: NTFS
OEM: IBM
Version 1.0.1
This plug-in can be used to format a volume for use with the NTFS filesystem.
When used to format a volume, this plug-in supports the following options:
Option Name: label
Description: Set the label for the volume.
Option Type: Character String
Option Name: cluster-size
Description: Set the cluster size.
Option Type: A positive integer number.
Option Name: mft-zone-mult
Description: Set the MFT zone multiplier.
Option Type: A 32 bit floating point number.
Option Name: compress
Description: Enable compression on the volume.
Option Type: TRUE or FALSE
Option Name: quick
Description: Skip both zeroing of the volume and bad sector checking.
Option Type: TRUE or FALSE
Plug-in ID: 531636225
Full Name: DOS Segment Manager
Short Name: DosSegMgr
OEM: IBM
Version 1.1.13
This plug-in is used to create Segments.
This plug-in supports the following options when creating Segments:
Option Name: Size
Description: This option allows you to set the size of the segment that you are
creating.
Option Type: A 64 bit positive integer number.
Option Name: Offset
Description: Use this option if you don't want the segment you are creating to
start at the beginning of freespace. It allows you to specifiy the number of
sectors to skip before creating the segment.
Option Type: A 64 bit positive integer number.
Option Name: TypeByName
Description: Select from a list of common partition types
Option Type: Character String
Option Name: TypeByNumber
Description: The type of partition you are creating, e.g. 6 = FAT16
Option Type: An 8 bit positive integer number.
Option Name: Bootable
Description: Choose Yes if the primary partition should be marked active so that
you can boot from it.
Option Type: TRUE or FALSE
Option Name: Primary
Description: This option allows you to choose between creating a logical or
primary partition. Choose Yes if you would like a primary partition created.
Option Type: TRUE or FALSE
Option Name: PartitionName
Description: OS/2 partition name
Option Type: Character String
Option Name: VolumeName
Description: Name of OS/2 volume this segment will reside in
Option Type: Character String
Option Name: DriveLetter
Description: OS/2 drive letter for this new segment
Option Type: Character String
This plug-in implements one or more partitioning schemes. It can be used to
subdivide the storage provided by a disk or segment. The assign command is used
to associate this plug-in with a disk or segment. When being assigned to a disk
or segment, this plug-in supports the following options:
Option Name: TypeByName
Description: Choose between OS/2 and Linux disk types. An OS/2 disk will
maintain extra metadata that is used by OS/2.
Option Type: Character String
Option Name: DiskName
Description: OS/2 requires that you choose a name for the disk that is no more
than 20 characters.
Option Type: Character String
Plug-in ID: 531636230
Full Name: Bad Block Relocation Segment Manager
Short Name: BBRseg
OEM: IBM
Version 1.1.11
This plug-in can be used to create Segments.
This plugin implements one or more partitioning schemes. It can be used to
subdivide a disk or segment.
Plug-in ID: 531636227
Full Name: GPT Segment Manager
Short Name: GptSegMgr
OEM: IBM
Version 1.1.10
This plug-in is used to create Segments.
This plug-in supports the following options when creating Segments:
Option Name: Size
Description: This option allows you to set the size of the segment that you are
creating.
Option Type: A 64 bit positive integer number.
Option Name: Offset
Description: Use this option if you dont want the segment you are creating to
start at the beginning of freespace. It allows you to specifiy the number of
sectors to skip before creating the segment.
Option Type: A 64 bit positive integer number.
This plug-in implements one or more partitioning schemes. It can be used to
subdivide the storage provided by a disk or segment. The assign command is used
to associate this plug-in with a disk or segment. When being assigned to a disk
or segment, this plug-in supports the following options:
Option Name: Create System Partition
Description: Choose Yes if an EFI system partition should be created. Probably
only useful on IA64 systems.
Option Type: TRUE or FALSE
Plug-in ID: 531632140
Full Name: EVMS Replace
Short Name: Replace
OEM: IBM
Version 1.1.1
This plug-in can be used to create Logical Disks.
Plug-in ID: 531652615
Full Name: Ext2/3 File System Interface Module
Short Name: Ext2/3
OEM: IBM
Version 1.1.12
This plug-in can be used to format a volume for use with the Ext2/3 filesystem.
When used to format a volume, this plug-in supports the following options:
Option Name: badblocks
Description: Check the volume for bad blocks before building the file system.
Option Type: TRUE or FALSE
Option Name: badblocks_rw
Description: Do a read/write check for bad blocks before building the file
system.
Option Type: TRUE or FALSE
Option Name: vollabel
Description: Set the volume label for the file system.
Option Type: Character String
Option Name: journal
Description: Create a journal for use with the ext3 file system.
Option Type: TRUE or FALSE
Plug-in ID: 531636229
Full Name: Cluster Segment Manager
Short Name: CSM
OEM: IBM
Version 1.0.11
Plug-in ID: 531636232
Full Name: MAC Segment Manager
Short Name: MAC
OEM: IBM
Version 1.0.7
Plug-in ID: 531644422
Full Name: Bad Block Relocation Feature
Short Name: BBR
OEM: IBM
Version 1.1.13
Plug-in ID: 531652628
Full Name: OpenGFS File System Interface Module
Short Name: OGFS
OEM: IBM
Version 1.0.4
This plug-in can be used to format a volume for use with the OGFS filesystem.
When used to format a volume, this plug-in supports the following options:
Option Name: blocksize
Description: Acceptable range: 512 to 65536 bytes. Must be a power of 2.
Option Type: A 32 bit positive integer number.
Option Name: journals
Description: Journal volumes (one for each node).
Option Type: Character String
Option Name: protocol
Description: Name of the locking protocol
Option Type: Character String
Option Name: lockdev
Description: Shared volume containing locking metadata
Option Type: Character String
Plug-in ID: 531636231
Full Name: BSD Segment Manager
Short Name: BSD
OEM: IBM
Version 1.0.7
Plug-in ID: 531640330
Full Name: LVM2 Region Manager
Short Name: LVM2
OEM: IBM
Version 1.0.2
This plug-in can be used to create containers.
This plug-in, when used to create containers, supports the following options:
Option Name: name
Description: (null)
Option Type: Character String
Option Name: extent_size
Description: Extent-size must be a power-of-2 and at least 8kB.
Option Type: A 64 bit positive integer number.
Plug-in ID: 531652614
Full Name: JFS File System Interface Module
Short Name: JFS
OEM: IBM
Version 1.1.14
This plug-in can be used to format a volume for use with the JFS filesystem.
When used to format a volume, this plug-in supports the following options:
Option Name: badblocks
Description: Check the volume for bad blocks before building the file system.
Option Type: TRUE or FALSE
Option Name: vollabel
Description: Set the volume label for the file system.
Option Type: Character String
Option Name: caseinsensitive
Description: Mark the file system as case insensitive (for OS/2 compatibility).
Option Type: TRUE or FALSE
Option Name: journalvol
Description: Set the volume for the journal if other than the JFS file system
volume.
Option Type: Character String
Option Name: logsize
Description: Set inline log size (in megabytes). Default log size is 0.4% of
volume size. Used only if no external journal volume is specified.
Option Type: An integer number.
Plug-in ID: 531632130
Full Name: Local Disk Manager
Short Name: LocalDskMgr
OEM: IBM
Version 1.2.10
Plug-in ID: 531640324
Full Name: MD Linear Raid Region Manager
Short Name: MDLinearRegMgr
OEM: IBM
Version 1.1.16
This plug-in can be used to create Regions.
Plug-in ID: 531640325
Full Name: MD Raid 1 Region Manager
Short Name: MDRaid1RegMgr
OEM: IBM
Version 1.1.16
This plug-in is used to create Regions.
This plug-in supports the following options when creating Regions:
Option Name: sparedisk
Description: Object to use as a spare disk in the array
Option Type: Character String
Plug-in ID: 531640326
Full Name: MD Raid 0 Region Manager
Short Name: MDRaid0RegMgr
OEM: IBM
Version 1.1.16
This plug-in is used to create Regions.
This plug-in supports the following options when creating Regions:
Option Name: chunksize
Description: Size of IO to each member of the array (also refered to as stripe
size).
Option Type: A 32 bit positive integer number.
Plug-in ID: 531640327
Full Name: MD RAID 4/5 Region Manager
Short Name: MDRaid5RegMgr
OEM: IBM
Version 1.1.16
This plug-in is used to create Regions.
This plug-in supports the following options when creating Regions:
Option Name: sparedisk
Description: Object to use as a spare disk in the array
Option Type: Character String
Option Name: chunksize
Description: Size of the chunks in the RAID array
Option Type: A 32 bit positive integer number.
Option Name: level
Description: RAID Level -- RAID4 or RAID5
Option Type: Character String
Option Name: algorithm
Description: RAID5 Parity algorithm
Option Type: Character String
Plug-in ID: 531640329
Full Name: MD Multipath Region Manager
Short Name: MD Multipath
OEM: IBM
Version 1.1.16
This plug-in can be used to create Regions.
Plug-in ID: 531648616
Full Name: Snapshot Feature
Short Name: Snapshot
OEM: IBM
Version 3.1.9
This plug-in is used to create EVMS Objects.
This plug-in supports the following options when creating EVMS Objects:
Option Name: original
Description: The volume you wish to take a snapshot of.
Option Type: Character String
Option Name: snapshot
Description: The name you wish to assign to the object being created.
Option Type: Character String
Option Name: chunksize
Description: Chunksize is the amount of data that will be copied at a time to
the snapshot.
Option Type: A 32 bit positive integer number.
Option Name: writeable
Description: Enableing this option allows writes to the snapshot.
Option Type: TRUE or FALSE
Logical Disk Name: hda
Major: 3
Minor: 0
Active: TRUE
Logical Disk Size: 149.05 GB
Logical Disk Geometry: 19457 Cylinders, 255 Heads, 63 Sectors per Track, 512
Bytes per Sector
LBA of the 1024 Cylinder Limit: 16434495
Parents:
hda_mbr
hda1
hda2
hda3
hda_freespace1
Children:
Logical Disk Name: hdc
Major: 22
Minor: 0
Active: TRUE
Logical Disk Size: 149.05 GB
Logical Disk Geometry: 19457 Cylinders, 255 Heads, 63 Sectors per Track, 512
Bytes per Sector
LBA of the 1024 Cylinder Limit: 16434495
Parents:
hdc_mbr
hdc1
hdc2
hdc3
hdc_freespace1
Children:
Logical Disk Name: hde
Major: 33
Minor: 0
Active: TRUE
Logical Disk Size: 149.05 GB
Logical Disk Geometry: 19457 Cylinders, 255 Heads, 63 Sectors per Track, 512
Bytes per Sector
LBA of the 1024 Cylinder Limit: 16434495
Parents:
hde_mbr
hde1
hde2
hde_freespace1
Children:
Logical Disk Name: hdg
Major: 34
Minor: 0
Active: TRUE
Logical Disk Size: 149.05 GB
Logical Disk Geometry: 19457 Cylinders, 255 Heads, 63 Sectors per Track, 512
Bytes per Sector
LBA of the 1024 Cylinder Limit: 16434495
Parents:
hdg_mbr
hdg1
hdg2
hdg_freespace1
Children:
Segment Name: hda_mbr
Major: 0
Minor: 0
Active: FALSE
Segment Size: 31.50 KB
Starting LBA: 0
Segment Type: Metadata
Parents:
Children:
hda
Segment Name: hda1
Major: 253
Minor: 0
Active: TRUE
Segment Size: 243.14 MB
Starting LBA: 63
Segment Type: Data
This segment may be shrunk using the Shrink command.
The following options are available for shrinking this segment:
Option Name: Size
Description: Use this option to specify how much space to remove from the
segment. Remember that segments shrink by cylinder size amounts.
Option Type: A 64 bit positive integer number.
Parents:
/dev/evms/hda1
Children:
hda
Segment Name: hda2
Major: 253
Minor: 8
Active: TRUE
Segment Size: 114.25 GB
Starting LBA: 498015
Segment Type: Data
Parents:
md/md0
Children:
hda
Segment Name: hda3
Major: 253
Minor: 1
Active: TRUE
Segment Size: 34.56 GB
Starting LBA: 240107490
Segment Type: Data
This segment may be shrunk using the Shrink command.
The following options are available for shrinking this segment:
Option Name: Size
Description: Use this option to specify how much space to remove from the
segment. Remember that segments shrink by cylinder size amounts.
Option Type: A 64 bit positive integer number.
Parents:
/dev/evms/hda3
Children:
hda
Segment Name: hda_freespace1
Major: 0
Minor: 0
Active: FALSE
Segment Size: 2.49 MB
Starting LBA: 312576705
Segment Type: Freespace
This segment may be used with the Allocate command, as well as the Create
command, to create a segment.
Parents:
Children:
hda
Segment Name: hdc_mbr
Major: 0
Minor: 0
Active: FALSE
Segment Size: 31.50 KB
Starting LBA: 0
Segment Type: Metadata
Parents:
Children:
hdc
Segment Name: hdc1
Major: 253
Minor: 2
Active: TRUE
Segment Size: 243.14 MB
Starting LBA: 63
Segment Type: Data
This segment may be shrunk using the Shrink command.
The following options are available for shrinking this segment:
Option Name: Size
Description: Use this option to specify how much space to remove from the
segment. Remember that segments shrink by cylinder size amounts.
Option Type: A 64 bit positive integer number.
Parents:
/dev/evms/hdc1
Children:
hdc
Segment Name: hdc2
Major: 253
Minor: 9
Active: TRUE
Segment Size: 114.25 GB
Starting LBA: 498015
Segment Type: Data
Parents:
md/md0
Children:
hdc
Segment Name: hdc3
Major: 253
Minor: 5
Active: TRUE
Segment Size: 34.56 GB
Starting LBA: 240107490
Segment Type: Data
This segment may be used with the Create command to create a Volume, Region,
EVMS Object, or Container.
This segment may be deleted using the Delete command.
This segment may be shrunk using the Shrink command.
The following options are available for shrinking this segment:
Option Name: Size
Description: Use this option to specify how much space to remove from the
segment. Remember that segments shrink by cylinder size amounts.
Option Type: A 64 bit positive integer number.
Parents:
Children:
hdc
Segment Name: hdc_freespace1
Major: 0
Minor: 0
Active: FALSE
Segment Size: 2.49 MB
Starting LBA: 312576705
Segment Type: Freespace
This segment may be used with the Allocate command, as well as the Create
command, to create a segment.
Parents:
Children:
hdc
Segment Name: hde_mbr
Major: 0
Minor: 0
Active: FALSE
Segment Size: 31.50 KB
Starting LBA: 0
Segment Type: Metadata
Parents:
Children:
hde
Segment Name: hde1
Major: 253
Minor: 4
Active: TRUE
Segment Size: 494.16 MB
Starting LBA: 63
Segment Type: Data
This segment may be shrunk using the Shrink command.
The following options are available for shrinking this segment:
Option Name: Size
Description: Use this option to specify how much space to remove from the
segment. Remember that segments shrink by cylinder size amounts.
Option Type: A 64 bit positive integer number.
Parents:
/dev/evms/hde1
Children:
hde
Segment Name: hde2
Major: 253
Minor: 3
Active: TRUE
Segment Size: 148.57 GB
Starting LBA: 1012095
Segment Type: Data
This segment may be used with the Create command to create a Volume, Region,
EVMS Object, or Container.
This segment may be deleted using the Delete command.
This segment may be shrunk using the Shrink command.
The following options are available for shrinking this segment:
Option Name: Size
Description: Use this option to specify how much space to remove from the
segment. Remember that segments shrink by cylinder size amounts.
Option Type: A 64 bit positive integer number.
Parents:
Children:
hde
Segment Name: hde_freespace1
Major: 0
Minor: 0
Active: FALSE
Segment Size: 2.49 MB
Starting LBA: 312576705
Segment Type: Freespace
This segment may be used with the Allocate command, as well as the Create
command, to create a segment.
Parents:
Children:
hde
Segment Name: hdg_mbr
Major: 0
Minor: 0
Active: FALSE
Segment Size: 31.50 KB
Starting LBA: 0
Segment Type: Metadata
Parents:
Children:
hdg
Segment Name: hdg1
Major: 253
Minor: 6
Active: TRUE
Segment Size: 494.16 MB
Starting LBA: 63
Segment Type: Data
This segment may be shrunk using the Shrink command.
The following options are available for shrinking this segment:
Option Name: Size
Description: Use this option to specify how much space to remove from the
segment. Remember that segments shrink by cylinder size amounts.
Option Type: A 64 bit positive integer number.
Parents:
/dev/evms/hdg1
Children:
hdg
Segment Name: hdg2
Major: 253
Minor: 7
Active: TRUE
Segment Size: 148.57 GB
Starting LBA: 1012095
Segment Type: Data
This segment may be used with the Create command to create a Volume, Region,
EVMS Object, or Container.
This segment may be deleted using the Delete command.
This segment may be shrunk using the Shrink command.
The following options are available for shrinking this segment:
Option Name: Size
Description: Use this option to specify how much space to remove from the
segment. Remember that segments shrink by cylinder size amounts.
Option Type: A 64 bit positive integer number.
Parents:
Children:
hdg
Segment Name: hdg_freespace1
Major: 0
Minor: 0
Active: FALSE
Segment Size: 2.49 MB
Starting LBA: 312576705
Segment Type: Freespace
This segment may be used with the Allocate command, as well as the Create
command, to create a segment.
Parents:
Children:
hdg
Region Name: md/md0
Major: 9
Minor: 0
Active: TRUE
Region Size: 114.25 GB
Region Type: Data
The following plug-in defined tasks are available for this disk:
Task Name: addspare
Task Title: Add spare object
Task Description: Use this function to add an object as a spare object for this
RAID array.
Task Name: markfaulty
Task Title: Mark object faulty
Task Description: Use this function to mark an object faulty in this RAID array.
If the RAID array has a spare object, the spare object will be brought on-line
to replace the faulty object.
Parents:
/dev/evms/md/md0
Children:
hda2
hdc2
Volume Name: /dev/evms/hda1
Major: 253
Minor: 0
Active: TRUE
Volume Size: 243.14 MB
Minor Number: 0
This volume is not mounted.
Filesystem: SWAPFS
Max Filesystem Size: 16.00 PB
Min Filesystem Size: 20.00 MB
The following commands may be used with this volume:
Check
Convert
Delete
Format
Revert
Shrink
Unformat
Children:
hda1
Volume Name: /dev/evms/hda3
Major: 253
Minor: 1
Active: TRUE
Volume Size: 34.56 GB
Minor Number: 1
This volume is not mounted.
Filesystem: ReiserFS
Max Filesystem Size: 16.00 TB
Min Filesystem Size: 33.16 MB
The following commands may be used with this volume:
Check
Convert
Delete
Format
Revert
Shrink
Unformat
Children:
hda3
Volume Name: /dev/evms/hdc1
Major: 253
Minor: 2
Active: TRUE
Volume Size: 243.14 MB
Minor Number: 2
This volume is not mounted.
Filesystem: SWAPFS
Max Filesystem Size: 16.00 PB
Min Filesystem Size: 20.00 MB
The following commands may be used with this volume:
Check
Convert
Delete
Format
Revert
Shrink
Unformat
Children:
hdc1
Volume Name: /dev/evms/hde1
Major: 253
Minor: 4
Active: TRUE
Volume Size: 494.16 MB
Minor Number: 4
This volume is not mounted.
Filesystem: SWAPFS
Max Filesystem Size: 16.00 PB
Min Filesystem Size: 20.00 MB
The following commands may be used with this volume:
Check
Convert
Delete
Format
Revert
Shrink
Unformat
Children:
hde1
Volume Name: /dev/evms/hdg1
Major: 253
Minor: 6
Active: TRUE
Volume Size: 494.16 MB
Minor Number: 6
This volume is not mounted.
Filesystem: SWAPFS
Max Filesystem Size: 16.00 PB
Min Filesystem Size: 20.00 MB
The following commands may be used with this volume:
Check
Convert
Delete
Format
Revert
Shrink
Unformat
Children:
hdg1
Volume Name: /dev/evms/md/md0
Major: 9
Minor: 0
Active: TRUE
Volume Size: 114.25 GB
Minor Number: 0
Mount Point: /
Filesystem: ReiserFS
Max Filesystem Size: 16.00 TB
Min Filesystem Size: 101.06 GB
The following commands may be used with this volume:
Check
Format
Unformat
Children:
md/md0
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-20050127evms
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages evms depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libevms-2.5 2.5.0-1 Enterprise Volume Management Syste
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
