Re: Logical Volume closed upon creation

From: Bob Booth - CITES (booth_at_UIUC.EDU)
Date: 08/27/04

  • Next message: Miller, Dave (I.S.): "Re: Script question" 
    Date:         Fri, 27 Aug 2004 12:10:02 -0500
To: aix-l@Princeton.EDU

    On Fri, Aug 27, 2004 at 12:01:08PM -0400, Vipin Khushu - SuSe wrote:
    > Holger,
    >
    > Good Point. I scoured the documentation for anything that would tell me how to change the state, but found nothing.
    >
    > My problem may be the sequence of steps I am following in order to make ready a filesystem for use.
    >
    > Here's what I have done so far:
    >
    > 1] Created a volume group. See details below:
    >
    > # lsvg abcvg
    >
    > VOLUME GROUP: abcvg VG IDENTIFIER: 00005815a0b8c994
    >
    > VG STATE: active PP SIZE: 2 megabyte(s)
    >
    > VG PERMISSION: read/write TOTAL PPs: 818 (1636 megabytes)
    >
    > MAX LVs: 256 FREE PPs: 0 (0 megabytes)
    >
    > LVs: 1 USED PPs: 818 (1636 megabytes)
    >
    > OPEN LVs: 0 QUORUM: 2
    >
    > TOTAL PVs: 2 VG DESCRIPTORS: 3
    >
    > STALE PVs: 0 STALE PPs 0
    >
    > ACTIVE PVs: 2 AUTO ON: yes
    >
    >
    > 2] Created a logical volume. See details below:
    >
    >
    > # lslv abclv
    >
    > LOGICAL VOLUME: abclv VOLUME GROUP: abcvg
    >
    > LV IDENTIFIER: 00005815a0b8c994.1 PERMISSION: read/write
    >
    > VG STATE: active/complete LV STATE: closed/syncd
    >
    > TYPE: jfs WRITE VERIFY: off
    >
    > MAX LPs: 818 PP SIZE: 2 megabyte(s)
    >
    > COPIES: 1 SCHED POLICY: parallel
    >
    > LPs: 818 PPs: 818
    >
    > STALE PPs: 0 BB POLICY: relocatable
    >
    > INTER-POLICY: minimum RELOCATABLE: yes
    >
    > INTRA-POLICY: middle UPPER BOUND: 32
    >
    > MOUNT POINT: N/A LABEL: None
    >
    > MIRROR WRITE CONSISTENCY: on
    >
    > EACH LP COPY ON A SEPARATE PV ?: yes
    >
    >
    >
    > 3] Please see attachment that shows the distribution of the logical volume over the physical partitions. All 818 partitions are used.
    >
    > A question at this point - Do I need to create a jfslog logical volume in this volume group?
    >

    If there is no jfslog in the VG it will be created for you when you make your
    first filesystem. Make sure that you leave at least one PP of space for the
    log lv, or more than one PP depending on your filesystem sizes and the type
    of performance you need. You can resize the jfslog before you mount the
    filesystem.

    > 4] In order to achieve the final objective of mounting a filesystem on these disks, what is the next required step?
    >
    > mkfs or crfs or something else?

    Once you have created the LV as your step above you can use the crfs command
    or #smit crfs to create the filesystem on your already existing LV. If there
    is enough space in the VG, and this is the first filesystem you create, like
    I said, the jfslog will be created for you.

    Once the filesystem is mounted (you will have to do that yourself after
    creation), the LV will be opened/syncd.

    In your above example you would use the following command to create your
    filesystem

    # crfs -j jfs -d abclv -g abcvg -m /yourfilesystemname -A (if you want mount
    at reboot)

    There are a host of other parameters to the -a option of crfs that you
    should review to get the best performanc/size from the jfs that you
    create. See the man page for crfs, or look in the system management guide
    for more details.

    cheers,

    bob

  • Next message: Miller, Dave (I.S.): "Re: Script question"

    Relevant Pages