I have found in /usr/lpp/bos/README on AIX 5.2 that new flag for mklv command appeared. I had created a LV using the new flag and I would like to use the LV for Ingres transaction log as a raw device.
Can anyone answer what mean that "-T O" indicates that we may safely stop skiping first 512bytes of LV (LVCB)?
For test, I had re-imported the VG and still get warinng that LVCB is overwritten (by ingres):
# importvg -V112 -y genvg hdisk1
0516-1281 synclvodm: Warning, lv control block of srlogIIlv
has been over written.
0516-622 synclvodm: Warning, cannot write lv control block data.
genvg
The same warning I get without using the new flag so I don't know if the flag really changes something.
BTW: Seems that -T flag is still not documented.
2.1.6 New Flag for the mklv Command
-T O Uses a new device sub type of logical volume. An application
(such as a database) may use this new device sub type as an
indication that it may safely stop skipping the logical
volume control block (lvcb) at the beginning of the logical
volume (lv).
Can anyone answer what mean that "-T O" indicates that we may safely stop skiping first 512bytes of LV (LVCB)?
For test, I had re-imported the VG and still get warinng that LVCB is overwritten (by ingres):
# importvg -V112 -y genvg hdisk1
0516-1281 synclvodm: Warning, lv control block of srlogIIlv
has been over written.
0516-622 synclvodm: Warning, cannot write lv control block data.
genvg
The same warning I get without using the new flag so I don't know if the flag really changes something.
BTW: Seems that -T flag is still not documented.
2.1.6 New Flag for the mklv Command
-T O Uses a new device sub type of logical volume. An application
(such as a database) may use this new device sub type as an
indication that it may safely stop skipping the logical
volume control block (lvcb) at the beginning of the logical
volume (lv).