11-12-2008
IMHO an LV Type of "jfs" is misleading if one wants to create raw devices and should be avoided therefore. Preferably one uses another name for Type, e.g. "raw", so that it is easily visible in the LV's properties what this LV is.
What probably happened is: sbdy created that LV and either assigned the Type or left the Type field empty in which case the default type (i.e. jfs) was chosen. The Informix DB did something to the LV (perhaps the DB did not use a leading offset but wrote over the LV's first 512 byte destroying the Logical Volume Control Block LVCB that way). When exporting the VG you deleted every information of that VG from the server's ODM. As there was nothing to read from the LV during import the Type field now is empty.
That LV handling might have caused a drawback. If you just lost the information about that type you may be lucky. Older versions of AIX had problems when importing/changing LVs who's LVCB was destroyed. I don't know if/how that changed with AIX 5L onwards but you might not be able to import/change the LV's correctly. So check thoroughly that your DB can use the raw devices as it should.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies
2. AIX
Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies
3. AIX
Hi!
Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes?
What items should I check, like where do I look at in smit? Or are there commands that I should execute?
I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies
4. AIX
Hello,
I am a french computer technician, and i speak English just a little.
On Aix 5.3, I encounter a name conflict logical volume on two volume group.
The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM
root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies
5. HP-UX
Dear all,
I have a server where all the space in the volume group got filled.
I have another server where I have got some space.
Can I use the logical volume of server B to a directory under server A.
Pl let me know if there are steps to do this.
Rgds
Rj (9 Replies)
Discussion started by: jegaraman
9 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies
7. AIX
Hello everyone,
I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created.
When I say region I mean: outer edge - outer middle - center - inner middle and inner edge.
Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies
8. UNIX for Dummies Questions & Answers
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies
9. Red Hat
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
LEARN ABOUT DEBIAN
config::model::models::debian::dpkg::control::binary
Config::Model::models::Debian::Dpkg::Control::Binary(3pmUser Contributed Perl DocumentatiConfig::Model::models::Debian::Dpkg::Control::Binary(3pm)
NAME
Config::Model::models::Debian::Dpkg::Control::Binary - Configuration class Debian::Dpkg::Control::Binary
VERSION
version 2.021
DESCRIPTION
Configuration classes used by Config::Model
Elements
Architecture
If a program needs to specify an architecture specification string in some place, it should select one of the strings provided by dpkg-
architecture -L. The strings are in the format os-arch, though the OS part is sometimes elided, as when the OS is Linux. A package may
specify an architecture wildcard. Architecture wildcards are in the format any (which matches every architecture), os-any, or any-cpu. For
more details, see http://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-arch-specMandatory. Type string.
Multi-Arch
This field is used to indicate how this package should behave on a multi-arch installations. This field should not be present in packages
with the Architecture: all field.Optional. Type enum. choice: 'same', 'foreign', 'allowed'.
Here are some explanations on the possible values:
'allowed'
allows reverse-dependencies to indicate in their Depends field that they need a package from a foreign architecture, but has no effect
otherwise.
'foreign'
the package is not co-installable with itself, but should be allowed to satisfy the dependency of a package of a different arch from
itself.
'same'
the package is co-installable with itself, but it must not be used to satisfy the dependency of any package of a different architecture
from itself.
Section
Optional. Type uniline.
Priority
Optional. Type enum. choice: 'required', 'important', 'standard', 'optional', 'extra'.
Essential
Optional. Type boolean.
Depends
Optional. Type list of uniline.
Recommends
Optional. Type list of uniline.
Suggests
Optional. Type list of uniline.
Enhances
Optional. Type list of uniline.
Pre-Depends
Optional. Type list of uniline.
Breaks
Optional. Type list of uniline.
Conflicts
Optional. Type list of uniline.
Provides
Optional. Type list of uniline.
Replaces
Optional. Type list of uniline.
Package-Type - The type of the package, if not a regular Debian one
If this field is present, the package is not a regular Debian package, but either a udeb generated for the Debian installer or a tdeb
containing translated debconf strings.Optional. Type enum. choice: 'tdeb', 'udeb'.
Note: Package-Type is migrated with '$xc' and with $xc => ""- XC-Package-Type""
XC-Package-Type - The type of the package, if not a regular Debian one
If this field is present, the package is not a regular Debian package, but either a udeb generated for the Debian installer or a tdeb
containing translated debconf strings.Deprecated Optional. Type enum. choice: 'tdeb', 'udeb'.
Synopsis
Mandatory. Type uniline.
Description
Mandatory. Type string.
SEE ALSO
o cme
AUTHOR
Dominique Dumont
COPYRIGHT
2010,2011 Dominique Dumont
LICENSE
LGPL2
perl v5.14.2 2012-11-09 Config::Model::models::Debian::Dpkg::Control::Binary(3pm)