Re: Logical Volume closed upon creation
From: Green, Simon (Simon.Green_at_EU.ALTRIA.COM)
Date: 08/27/04
- Previous message: Vipin Khushu - SuSe: "Re: Copying files over the Network"
- Maybe in reply to: Vipin Khushu - SuSe: "Logical Volume closed upon creation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 Aug 2004 18:33:50 +0200 To: aix-l@Princeton.EDU
Normally, I would now use the crfs command to create a JFS. (You could also
use smitty to do this, if you prefer.)
When the first JFS is created, LVM will automatically create a JFSlog in the
volume group. Since you have used all of the partitions in your VG it will
be unable to do this, so you cannot create a JFS.
You might be able to create a JFS2, since that can have an in-line JFSlog,
which is part of the main LV.
For a normal JFS, first delete your LV, (rmlv), then re-create it, leaving
one or more partitions - preferably on the outer edge of a disk if you're
mirroring, or in the centre if you are not - for the JFSlog.
Now, use the crfs command to create your JFS. It will automatically create
a JFSlog, so you don't need to.
Finally, mount the filesystem.
-- Simon Green Altria ITSC Europe Ltd AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html <https://new-lists.princeton.edu/listserv/aix-l.html> New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX <http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX> N.B. Unsolicited email from vendors will not be appreciated. Please post all follow-ups to the list. -----Original Message----- From: Vipin Khushu - SuSe [mailto:vkhushu@GUERNSEYOP.COM] Sent: 27 August 2004 17:01 To: aix-l@Princeton.EDU Subject: Re: Logical Volume closed upon creation 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: 2] Created a logical volume. See details below: 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? 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?
- Previous message: Vipin Khushu - SuSe: "Re: Copying files over the Network"
- Maybe in reply to: Vipin Khushu - SuSe: "Logical Volume closed upon creation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: All JFS partitions unreadable
... partitions on 2 disks and 3 HPFS partitions to find that ... for all the JFS
partitions and the FAT one. ... If I boot to the command line from the boot blob, ...
I took the non-system disk out and put it into ... (comp.os.os2.bugs) - Re: Strange SIGSEGV problem around dmcrypt, evms and jfs
... Then I tested different ciphers performance by doing dmcrypt mappings on ...
final mapping and created and mounted jfs on it. ... evms was on and was detecting partitions
and created it's mappings on booting. ... against code that hasn't been annotated for lockdep.
... (Linux-Kernel) - Re: All JFS partitions unreadable
... partitions on 2 disks and 3 HPFS partitions to find that ... He needs to take
the data files that the Dfsee author requires to figure this out. ... for all the JFS
partitions and the FAT one. ... If I boot to the command line from the boot blob, ...
(comp.os.os2.bugs) - Re: All JFS partitions unreadable
... A few days ago I booted a box with a mixture of 3 JFS ... partitions
on 2 disks and 3 HPFS partitions to find that ... FWIW all the HPFS partitions are ok.
... then jfschk32 will not fix the problem and may say that the disks are dirty. ...
(comp.os.os2.bugs) - Re: All JFS partitions unreadable
... A few days ago I booted a box with a mixture of 3 JFS ... partitions
on 2 disks and 3 HPFS partitions to find that ... FWIW all the HPFS partitions are ok.
... then jfschk32 will not fix the problem and may say that the disks are dirty. ...
(comp.os.os2.bugs)