home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!news.sei.cmu.edu!drycas.club.cc.cmu.edu!cantaloupe.srv.cs.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!<UNAUTHENTICATED>+
- Newsgroups: comp.unix.aix
- Subject: Re: AIX LVM Metadata Area
- Message-ID: <8eeKJUP0BwxaEIDllI@transarc.com>
- From: Barry_Wolman@transarc.com
- Date: Sat, 5 Sep 1992 21:56:48 -0400
- References: <webIbvv0Bwx3M1871b@transarc.com>
- Organization: Carnegie Mellon, Pittsburgh, PA
- In-Reply-To: <webIbvv0Bwx3M1871b@transarc.com>
- Lines: 21
-
- Barry_Wolman@transarc.com writes:
- > An AIX Logical Volume has N-bytes of metadata at the start of the
- > volume. User code that writes to a logical volume is supposed to
- > avoid writing in this area. I need to determine the value of N.
- > I've heard "don't write in the first page" ... does this mean N=4096?
- >
- > Thanks,
- > Barry Wolman
-
- N=512. The info in the first block of a LV is there for information
- purposes only. AIX does not depend on this data. If AIX finds the
- string "AIX LVCB" at the start of a logical volume, it assumes the
- meta data area is still valid and updates the date fields. If AIX
- doesn't find this string, it assumes that a user program over-wrote
- the header info and doesn't modify this header. This may result in
- warning messages from LV operations, e.g. extend logical volume, but
- the requested operation is correctly performed. smit has a problem
- because it doesn't distinguish between warnings and fatal errors from
- the commands that it runs. If you perform an operation on a LV from
- smit and the LV header was over-written, smit will tell you the
- operation failed evern though it actually completed successfully.
-