Topic
  • 8 replies
  • Latest Post - ‏2006-12-15T15:48:24Z by SystemAdmin
SystemAdmin
SystemAdmin
6902 Posts

Pinned topic Unable to remove a lv

‏2006-12-14T01:59:47Z |
In my AIX 5.3L, I must made some mistake during the creation of a lv, then when I tried to remove or rename it, the system did not allow me to do, always failed. here are the screen shows
at the rmove lv step in smit storage
0516-306 getlvodm: Unable to find oradump in the Device Configuration Database.
0516-912 rmlv: Unable to remove logical volume oradump.
however the liste (F4) show the oradump is there
oradump ??? 94 94 1 closed/syncd N/A
at the rename lv step
1800-106 An error occurred:
0516-306 /usr/sbin/getlvodm: Unable to find oradump in the Device Configuration Database
but the oradump is on the list with F4
Also a dump question is how to create filesystem that will be associated with a newly created lv, not use or create a default lv00? or another way around. I spent hours in the smitty, but find no clue how to do that. there is no option in the filesystem allows me to assign the specific lv or in the lv to assign a specific filesystem.
Updated on 2006-12-15T15:48:24Z at 2006-12-15T15:48:24Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    6902 Posts

    Re: Unable to remove a lv

    ‏2006-12-14T02:07:16Z  
    The lv has no filesystem attached- N/A and it is not on the rootvg, it is on the secondary vg, not mirrored.
  • SystemAdmin
    SystemAdmin
    6902 Posts

    Re: Unable to remove a lv

    ‏2006-12-14T02:22:25Z  
    Found the solution:
    #update the ODM with the LV details from the LVCB
    synclvodm -v baanvg oradump
    1. remove the lv
    rmlv oradump

    But I still do not know hot to create a filesystem and assign a specific lv to it. Can anyone help? REALLY appreciated.
  • orphy
    orphy
    480 Posts

    Re: Unable to remove a lv

    ‏2006-12-14T02:35:19Z  
    Found the solution:
    #update the ODM with the LV details from the LVCB
    synclvodm -v baanvg oradump
    1. remove the lv
    rmlv oradump

    But I still do not know hot to create a filesystem and assign a specific lv to it. Can anyone help? REALLY appreciated.
    I was going to suggest synclvodm but looks like you beated me to it.
    I'm not a SMIT guy so I don't remember all those menu options and I don't feel
    like signing on so here's how you can do it from CLI. This example shows how
    to do JFS2 but you can simply change that to JFS if you like.

    1. mklv -t jfs2 -y oradump baanvg 94 <hdiskX>
    2. crfs -v jfs2 -d oradump -m </FSName> -A yes

    I suggest you looking at the man pages before actually running them.
    Orphy! :-)
  • SystemAdmin
    SystemAdmin
    6902 Posts

    Re: Unable to remove a lv

    ‏2006-12-14T16:56:30Z  
    • orphy
    • ‏2006-12-14T02:35:19Z
    I was going to suggest synclvodm but looks like you beated me to it.
    I'm not a SMIT guy so I don't remember all those menu options and I don't feel
    like signing on so here's how you can do it from CLI. This example shows how
    to do JFS2 but you can simply change that to JFS if you like.

    1. mklv -t jfs2 -y oradump baanvg 94 <hdiskX>
    2. crfs -v jfs2 -d oradump -m </FSName> -A yes

    I suggest you looking at the man pages before actually running them.
    Orphy! :-)
    Thanks. Your suggestion works. I read the man of both commands. Here are what I run
    1. mklv -t jfs2 -y fslv05 rootvg 47 hdisk1
    fslv05
    1. crfs -v jfs2 -g rootvg -d fslv05 -m /oradump -A yes
    crfs: 0506-919 Specify only one of volumegroup or device.
    1. crfs -v jfs2 -d fslv05 -m /oradump -A yes
    File system created successfully.
    6159992 kilobytes total disk space.
    New File System size is 12320768

    The only problem in the smit(ty) is not to associated the hdisk1 for the filesytem creation, and there is no option I can link the lv, which can assign a hdisk, to the filesystem. Maybe I should try again, look more carefully.

    However it puzzles me how comes a jfs hd can also put a jfs2 file type on? Because another filesystem on the hdisk1 was created with jfs type.
  • orphy
    orphy
    480 Posts

    Re: Unable to remove a lv

    ‏2006-12-14T17:32:09Z  
    Thanks. Your suggestion works. I read the man of both commands. Here are what I run
    1. mklv -t jfs2 -y fslv05 rootvg 47 hdisk1
    fslv05
    1. crfs -v jfs2 -g rootvg -d fslv05 -m /oradump -A yes
    crfs: 0506-919 Specify only one of volumegroup or device.
    1. crfs -v jfs2 -d fslv05 -m /oradump -A yes
    File system created successfully.
    6159992 kilobytes total disk space.
    New File System size is 12320768

    The only problem in the smit(ty) is not to associated the hdisk1 for the filesytem creation, and there is no option I can link the lv, which can assign a hdisk, to the filesystem. Maybe I should try again, look more carefully.

    However it puzzles me how comes a jfs hd can also put a jfs2 file type on? Because another filesystem on the hdisk1 was created with jfs type.
    First of all, if you have other non-rootvg disks, I would suggest putting this
    /oradump filesystem there. You typically don't want to stick any non-OS data
    in rootvg unless you have no choice.

    1. If you want to have a particular FS living on a particular hdisk,
    the way to do it is to create an LV first and then create a filesystem using
    the following SMIT path:

    1. smitty crfs
    --> Add an Enhanced Journaled File System # or pick the JFS path
    --> Add an Enhanced Journaled File System on a Previously Defined Logical Volume

    Or, you can create a FS in one step (without mklv first) and use migratepv
    to move the LV later.

    2. The PV (hd) doesn't really have much to do, directly, with a JFS/JFS2 since
    PV really talks to LV and LV talks to FS (JFS/JFS2). That's why as long as
    you have an LV, you can create an FS on top of it and both JFS & JFS2 can live
    on the same VG. Assuming that you don't use INLINE log, the only requirement
    is that you need a jfslog or jfs2log for each type of FS.
    Orphy! :-)
  • SystemAdmin
    SystemAdmin
    6902 Posts

    Re: Unable to remove a lv

    ‏2006-12-15T00:10:48Z  
    • orphy
    • ‏2006-12-14T17:32:09Z
    First of all, if you have other non-rootvg disks, I would suggest putting this
    /oradump filesystem there. You typically don't want to stick any non-OS data
    in rootvg unless you have no choice.

    1. If you want to have a particular FS living on a particular hdisk,
    the way to do it is to create an LV first and then create a filesystem using
    the following SMIT path:

    1. smitty crfs
    --> Add an Enhanced Journaled File System # or pick the JFS path
    --> Add an Enhanced Journaled File System on a Previously Defined Logical Volume

    Or, you can create a FS in one step (without mklv first) and use migratepv
    to move the LV later.

    2. The PV (hd) doesn't really have much to do, directly, with a JFS/JFS2 since
    PV really talks to LV and LV talks to FS (JFS/JFS2). That's why as long as
    you have an LV, you can create an FS on top of it and both JFS & JFS2 can live
    on the same VG. Assuming that you don't use INLINE log, the only requirement
    is that you need a jfslog or jfs2log for each type of FS.
    Orphy! :-)
    Apparently I do not have too much choice. Because my other two hd, under other vg, do not have enough space and one is used for the oracle data. So i create the oradump under the roovg but differnt hd, not the same one of OS, /tmp, /user, /home, /. Hope it works OK. What is the most like problem if I create such filesystem and non-OR data under the rootvg?
  • orphy
    orphy
    480 Posts

    Re: Unable to remove a lv

    ‏2006-12-15T01:05:43Z  
    Apparently I do not have too much choice. Because my other two hd, under other vg, do not have enough space and one is used for the oracle data. So i create the oradump under the roovg but differnt hd, not the same one of OS, /tmp, /user, /home, /. Hope it works OK. What is the most like problem if I create such filesystem and non-OR data under the rootvg?
    It's not likely that having any non-OS FS in rootvg would cause any major
    problem. However, depending on how busy the FS is, it could possibly cause
    performance issues. It also looks like you are not mirroring rootvg which
    is not a very good thing to do. I would strongly recommend you taking the
    time to mirror the OS. For that, look into the mirrorvg command. If you
    don't have the space to mirrorvg, you should have a mksysb procedure in place
    and do execute it regularly. Since you have a non-OS FS in rootvg, look into
    putting that in /etc/exclude.rootvg (man mksysb) so that you are not saving
    those files in the mksysb.

    You can always talk to your boss about getting some more disks, though
    they don't always listen...

    Good luck!
    Orphy! :-)
  • SystemAdmin
    SystemAdmin
    6902 Posts

    Re: Unable to remove a lv

    ‏2006-12-15T15:48:24Z  
    • orphy
    • ‏2006-12-15T01:05:43Z
    It's not likely that having any non-OS FS in rootvg would cause any major
    problem. However, depending on how busy the FS is, it could possibly cause
    performance issues. It also looks like you are not mirroring rootvg which
    is not a very good thing to do. I would strongly recommend you taking the
    time to mirror the OS. For that, look into the mirrorvg command. If you
    don't have the space to mirrorvg, you should have a mksysb procedure in place
    and do execute it regularly. Since you have a non-OS FS in rootvg, look into
    putting that in /etc/exclude.rootvg (man mksysb) so that you are not saving
    those files in the mksysb.

    You can always talk to your boss about getting some more disks, though
    they don't always listen...

    Good luck!
    Orphy! :-)
    I knew it could cause the performance problem, but according to the iostat and my ps size, and the operations of those applications, I made the best choice now. Just double check my OS, it is mirrored. Only filesystems not mirrored are those I created. I hope they can buy more HD in here, Mexican. But this is a different place, budget planning is a problem. I, or them, just have to live with the situation and make the best out of it.