home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!sun4nl!orcenl!dk.oracle.com!bengsig
- From: bengsig@dk.oracle.com (Bjorn Engsig)
- Newsgroups: comp.unix.aix
- Subject: Re: AIX LVM Metadata Area
- Message-ID: <1992Sep15.145717.14932@dk.oracle.com>
- Date: 15 Sep 92 14:57:17 GMT
- References: <webIbvv0Bwx3M1871b@transarc.com> <1992Sep1.152635.8639@awdprime.austin.ibm.com>
- Sender: news@dk.oracle.com (News Administrator)
- Reply-To: bengsig@dk.oracle.com (Bjorn Engsig)
- Organization: Oracle Denmark
- Lines: 22
- Nntp-Posting-Host: dkunix9.dk.oracle.com
-
- Article <1992Sep1.152635.8639@awdprime.austin.ibm.com> by julie@levell.austin.ibm.com (Julie L. Craft) says:
- |Block 0 of the logical volume is used to store data about the logical
- |volume that is not stored in the VGDA. We call it the logical volume
- |control block. It's 1 512 byte block. Most applications we have
- |usually start at block 1 to avoid writing over this block. The real
- |importance of this block is for importing a volume group. If you have
- |a raw logical volume that is overwriting this block, I wouldn't worry
- |about it unless you want to import it on another system, but even then
- |you can just fix it up with chlv later.
- I'm sorry but this information is both confusing and incorrect. Rudy
- Chukran and I have both given the correct information that basicly is:
-
- - The entire Logical Volume is available as a raw device (/dev/lvXXX
- as a blocked device, /dev/rlvXXX is a true raw, direct access, device)
-
- - Don't try to access the Volume Groups (/dev/XXXvg) or Physical Volumes
- (/dev/hdiskXXX or /dev/rhdiskXXX). Neither are meant to be directly
- accessed.
- --
- Bjorn Engsig, Internet: bengsig@oracle.com
- ORACLE Corporation. BANG-net: uunet!oracle!bengsig
- Private : bjorn@login.dkuug.dk.
-