This is a discussion on Problems adding filesystems within the AIX Operating System forums, part of the Unix Operating Systems category; --> Hey, I'm having some issues increasing the size of filesystems for a VG on an AIX 5.2 box (ML ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hey, I'm having some issues increasing the size of filesystems for a VG on an AIX 5.2 box (ML 3, soon to be ML 6). I think it's related to the fact that I've recently increased the size of the SAN partition on which the volume groups is in. For instance, here's the error I receive attempting to add a new filesytem: mknod: /dev/loglv00: Do not specify an existing file. 0516-822 mklv: Unable to create logical volume. crfs: 0506-902 Cannot create logical volume. Also, the lsvg output is funny--it was coming out with the type as "???" instead of the appropriate type. I ran synclvodm on the VG, and now lsvg -l shows the type as jfs (instead of jfs2) for a filesystem and the jfs log LV: LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT loglv02 jfs 1 1 1 open/syncd N/A fslv07 jfs 306 306 1 open/syncd N/A Like I said above, this is a SAN partition and I've recently increased its size and run chvg -g on it. Do I need to run logform on the JFS2 log LV? How do you do this safely? Or am I totally off base here? |
| |||
| did you CTRL C while creating the new file system? Whatever the reason, synclvodm could just be resetting the LV characteristics to the default values while updating the LVCB. Assuming you dont have any trouble with the FS, you could change the type of the LV to jfs2 (chlv -t) As for the error, is there a device file called /dev/loglv00 ? if not, check the name of the file system. For E.G, if the file system you are trying to create is called /test, make sure there is not a 'file' in the same path as your FS name.. in this case /test Hope that helps. Guido von Guido wrote: > Hey, I'm having some issues increasing the size of filesystems for a > VG on an AIX 5.2 box (ML 3, soon to be ML 6). I think it's related to > the fact that I've recently increased the size of the SAN partition on > which the volume groups is in. > > For instance, here's the error I receive attempting to add a new filesytem: > > mknod: /dev/loglv00: Do not specify an existing file. > 0516-822 mklv: Unable to create logical volume. > crfs: 0506-902 Cannot create logical volume. > > Also, the lsvg output is funny--it was coming out with the type as "???" instead of the appropriate type. I ran synclvodm on the VG, and now lsvg -l shows the type as jfs (instead of jfs2) for a filesystem and the jfs log LV: > > LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT > loglv02 jfs 1 1 1 open/syncd N/A > fslv07 jfs 306 306 1 open/syncd N/A > > Like I said above, this is a SAN partition and I've recently increased > its size and run chvg -g on it. Do I need to run logform on the JFS2 > log LV? How do you do this safely? Or am I totally off base here? |