IBM - AIX - List File System
We can list file system details using lsfs command
#lsfs – List all filesystems in the /etc/filesystems entry
#lsfs –q (List all filesystems with detailed info)
#lsfs –a (list all filesystems (default)
#lsfs –l (specify the output in the list format)
#lsfs –c (specify the output in the column format)
#lsfs –v jfs (List all jfs filesystems)
Sunday, April 26, 2009
AIX - LVM - Change File System
AIX - LVM - Change File System
Using chfs command we can rename and increase the size of the file system online
We want to increase file system size
#chfs –a size=+block size /filesystem name
#chfs –a size=+32m /filesystem name
#chfs-a size=+4g /filesystem name
+block size – We can mention the size using blocks (2048 blocks = 1MB)
+32m – We can mention the size using MB
+4g – We can mention the size using GB
After increasing the file system size, we can verify using commands
#df –k
#ls –q /newfs
Rename the file system using chfs command
#lsfs /newfs
It will display /newfs details
#
Now we want to rename /newfs to /testfs then your command will be
#chfs –m /testfs /newfs
After executing the above command /newfs renamed as /testfs
We can auto mount the file system while booting using chfs command
#chfs –A /testfs
Using chfs command we can rename and increase the size of the file system online
We want to increase file system size
#chfs –a size=+block size /filesystem name
#chfs –a size=+32m /filesystem name
#chfs-a size=+4g /filesystem name
+block size – We can mention the size using blocks (2048 blocks = 1MB)
+32m – We can mention the size using MB
+4g – We can mention the size using GB
After increasing the file system size, we can verify using commands
#df –k
#ls –q /newfs
Rename the file system using chfs command
#lsfs /newfs
It will display /newfs details
#
Now we want to rename /newfs to /testfs then your command will be
#chfs –m /testfs /newfs
After executing the above command /newfs renamed as /testfs
We can auto mount the file system while booting using chfs command
#chfs –A /testfs
AIX - LVM - Create File System
AIX - LVM - Create File System
Create FS
Using crfs command we can create a file system. File systems belongs to LV’s
Whenever we create the file system we should mention the LV name
#crfs –v jfs2 –d testlv –m /newfs (Normal creation)
The /newfs file system created on testlv.
#crfs –v jfs2 –g testvg –a size=64465 –m /newfs (Directly we can create /fs from VG
This case lv name will be lv00 or lv01 like this after that also we can rename the lv name)
Create FS
Using crfs command we can create a file system. File systems belongs to LV’s
Whenever we create the file system we should mention the LV name
#crfs –v jfs2 –d testlv –m /newfs (Normal creation)
The /newfs file system created on testlv.
#crfs –v jfs2 –g testvg –a size=64465 –m /newfs (Directly we can create /fs from VG
This case lv name will be lv00 or lv01 like this after that also we can rename the lv name)
AIX - LVM - Remove Logical Volume
AIX - LVM - Remove Logical Volume
If we want to LV testlv from server
#rmlv testlv (If data is available in testlv It will ask confirmation)
#rmlv –f testlv (It won’t ask any confirmation, directly it will delete the data)
After executing the above command testlv removed from the server.
If we want to LV testlv from server
#rmlv testlv (If data is available in testlv It will ask confirmation)
#rmlv –f testlv (It won’t ask any confirmation, directly it will delete the data)
After executing the above command testlv removed from the server.
Friday, April 24, 2009
AIX Supported Hardware Platforms
IBM 6150 RT
The original AIX (sometimes called AIX/RT) was developed for the IBM 6150 RT workstation by IBM in conjunction with INTERACTIVE Systems Corporation, who had previously ported UNIX System III to the IBM PC for IBM as PC/IX. Installation media consisted of eight 1.2M floppy disks. The RT was based on the ROMP chip, the first commercial RISC chip, based on a design, the IBM 801, pioneered at IBM Research.
One of the novel aspects of the RT design was the use of a microkernel, called Virtual Resource Manager (VRM). The keyboard, mouse, display, disk drives and network were all controlled by a microkernel. One could "hotkey" from one operating system to the next using the Alt-Tab key combination. Each OS in turn would get possession of the keyboard, mouse and display. Besides AIX v2, the PICK OS also utilized this microkernel.
Much of the AIX v2 kernel was written in the PL/I programming language, which proved troublesome during the migration to AIX v3.[citation needed] AIX v2 included full TCP/IP networking, as well as SNA and two networking file systems: NFS, licensed from Sun Microsystems, and Distributed Services (DS). DS had the distinction of being built on top of SNA, and thereby being fully compatible with DS on the IBM midrange AS/400 and mainframe systems. For the graphical user interfaces, AIX v2 came with the X10R3 and later the X10R4 and X11 versions of the X Window System from MIT, together with the Athena widget set. Compilers for Fortran and C were available. One of the more popular desktop applications was the PageMaker desktop publishing software.
IBM PS/2 series
AIX PS/2 (also known as AIX/386) was developed by Locus Computing Corporation under contract to IBM. AIX PS/2, first released in 1989, ran on IBM PS/2 personal computers with Intel 386 and faster processors.
IBM mainframes
In 1988, IBM announced AIX/370, also developed by Locus Computing. AIX/370 was IBM's first attempt to offer Unix-like functionality for their mainframe line, specifically the System/370. AIX/370 was released in 1990 with functional equivalence to System V Release 2 and 4.3BSD as well as IBM enhancements. With the introduction of the ESA/390 architecture, AIX/370 was replaced by AIX/ESA in 1991, which was based on OSF/1, and also ran on the System/390 platform. This development effort was made partly to allow IBM to compete with Amdahl UTS. Unlike AIX/370, AIX/ESA ran both natively as the host operating system, and as a guest under VM. AIX/ESA, while technically advanced, had little commercial success, partially because UNIX functionality was added as an option to the existing mainframe operating system, MVS, which became MVS/ESA Open Edition in 1999.
POWER/PowerPC-based systems
The release of AIX version 3 (sometimes called AIX/6000) coincided with the announcement of the first IBM RS/6000 models. The RS/6000 was unique in that it not only outperformed all other machines in integer compute performance, but also beat the competition by a factor of 10 in floating-point performance.
Releases of AIX version 3 also took advantage of the developments in the POWER architecture.
AIX v3 innovated in several ways on the software side. It was the first operating system to introduce the idea of a journaling file system, JFS, which allowed for fast boot times by avoiding the need to fsck the disks on every reboot. Another innovation was the introduction of shared libraries, which avoided the need for an application to statically link to the libraries it used. The resulting smaller binaries used less of the hardware RAM, to run, and used less of the disk space to install. Besides improving performance, it was a boon to developers: executable binaries could be in the 10s of kilobytes instead of a megabyte for an executable statically linked to the C library. AIX v3 also ditched the microkernel of AIX v2, a contentious move that resulted in v3 being somewhat more "pure" (and containing no PL/1 code) than v2.
Apple Network Servers
The Apple Network Server systems were PowerPC-based systems designed by Apple Computer to have numerous high-end features that standard Apple hardware did not have, including swappable hard drives, redundant power supplies, and external monitoring capability. These systems were more or less based on the Power Macintosh hardware available at the time but were designed to use AIX (versions 4.1.4 or 4.1.5) as their native operating system in a specialized version specific to the ANS.
AIX was only compatible with the Network Servers and was not ported to standard Power Macintosh hardware. Not to be confused is A/UX, Apple's earlier version of Unix for 68k-based Macintoshes.
IA-64 systems
As part of Project Monterey, a beta test version of AIX 5L was released for the IA-64 (Itanium) architecture in 2001, but this was abandoned before it became an official product due to the lack of interest in the finished Project Monterey system, as well as the overall lack of uptake of the IA-64 architecture by a skeptical marketplace, which largely gravitated towards the Project Trillian port of Linux as the primary platform OS.
The original AIX (sometimes called AIX/RT) was developed for the IBM 6150 RT workstation by IBM in conjunction with INTERACTIVE Systems Corporation, who had previously ported UNIX System III to the IBM PC for IBM as PC/IX. Installation media consisted of eight 1.2M floppy disks. The RT was based on the ROMP chip, the first commercial RISC chip, based on a design, the IBM 801, pioneered at IBM Research.
One of the novel aspects of the RT design was the use of a microkernel, called Virtual Resource Manager (VRM). The keyboard, mouse, display, disk drives and network were all controlled by a microkernel. One could "hotkey" from one operating system to the next using the Alt-Tab key combination. Each OS in turn would get possession of the keyboard, mouse and display. Besides AIX v2, the PICK OS also utilized this microkernel.
Much of the AIX v2 kernel was written in the PL/I programming language, which proved troublesome during the migration to AIX v3.[citation needed] AIX v2 included full TCP/IP networking, as well as SNA and two networking file systems: NFS, licensed from Sun Microsystems, and Distributed Services (DS). DS had the distinction of being built on top of SNA, and thereby being fully compatible with DS on the IBM midrange AS/400 and mainframe systems. For the graphical user interfaces, AIX v2 came with the X10R3 and later the X10R4 and X11 versions of the X Window System from MIT, together with the Athena widget set. Compilers for Fortran and C were available. One of the more popular desktop applications was the PageMaker desktop publishing software.
IBM PS/2 series
AIX PS/2 (also known as AIX/386) was developed by Locus Computing Corporation under contract to IBM. AIX PS/2, first released in 1989, ran on IBM PS/2 personal computers with Intel 386 and faster processors.
IBM mainframes
In 1988, IBM announced AIX/370, also developed by Locus Computing. AIX/370 was IBM's first attempt to offer Unix-like functionality for their mainframe line, specifically the System/370. AIX/370 was released in 1990 with functional equivalence to System V Release 2 and 4.3BSD as well as IBM enhancements. With the introduction of the ESA/390 architecture, AIX/370 was replaced by AIX/ESA in 1991, which was based on OSF/1, and also ran on the System/390 platform. This development effort was made partly to allow IBM to compete with Amdahl UTS. Unlike AIX/370, AIX/ESA ran both natively as the host operating system, and as a guest under VM. AIX/ESA, while technically advanced, had little commercial success, partially because UNIX functionality was added as an option to the existing mainframe operating system, MVS, which became MVS/ESA Open Edition in 1999.
POWER/PowerPC-based systems
The release of AIX version 3 (sometimes called AIX/6000) coincided with the announcement of the first IBM RS/6000 models. The RS/6000 was unique in that it not only outperformed all other machines in integer compute performance, but also beat the competition by a factor of 10 in floating-point performance.
Releases of AIX version 3 also took advantage of the developments in the POWER architecture.
AIX v3 innovated in several ways on the software side. It was the first operating system to introduce the idea of a journaling file system, JFS, which allowed for fast boot times by avoiding the need to fsck the disks on every reboot. Another innovation was the introduction of shared libraries, which avoided the need for an application to statically link to the libraries it used. The resulting smaller binaries used less of the hardware RAM, to run, and used less of the disk space to install. Besides improving performance, it was a boon to developers: executable binaries could be in the 10s of kilobytes instead of a megabyte for an executable statically linked to the C library. AIX v3 also ditched the microkernel of AIX v2, a contentious move that resulted in v3 being somewhat more "pure" (and containing no PL/1 code) than v2.
Apple Network Servers
The Apple Network Server systems were PowerPC-based systems designed by Apple Computer to have numerous high-end features that standard Apple hardware did not have, including swappable hard drives, redundant power supplies, and external monitoring capability. These systems were more or less based on the Power Macintosh hardware available at the time but were designed to use AIX (versions 4.1.4 or 4.1.5) as their native operating system in a specialized version specific to the ANS.
AIX was only compatible with the Network Servers and was not ported to standard Power Macintosh hardware. Not to be confused is A/UX, Apple's earlier version of Unix for 68k-based Macintoshes.
IA-64 systems
As part of Project Monterey, a beta test version of AIX 5L was released for the IA-64 (Itanium) architecture in 2001, but this was abandoned before it became an official product due to the lack of interest in the finished Project Monterey system, as well as the overall lack of uptake of the IA-64 architecture by a skeptical marketplace, which largely gravitated towards the Project Trillian port of Linux as the primary platform OS.
AIX LVM - Remove Logical Volume copy
AIX LVM - Remove Logical Volume copy
Remove LV copy
Using rmlvcopy we can remove the lvcopy from the PV’s
If we want to remove testlv copy from hdisk0
#rmlvcopy testlv 3 hdisk0
After executing the above command third copy of the testlv removed from PV hdisk0, like this we can remove
Remove LV copy
Using rmlvcopy we can remove the lvcopy from the PV’s
If we want to remove testlv copy from hdisk0
#rmlvcopy testlv 3 hdisk0
After executing the above command third copy of the testlv removed from PV hdisk0, like this we can remove
AIX - LVM - Create Logical Volume Copy
AIX - Create LV copy
We can create LV content copy to another PV, after this same LV content is available in Lvcopy configured PV.
#lspv
Hdisk0
Hdisk1
Hdisk2
#lspv –l hdisk1
Assume testlv available in hdisk1, now we will make testlv copy to hdisk2, using
After this testlv data available in both PV, hdisk1 and hdisk2, If hdisk1 is fail, we can recover testlv data from hdisk2
#mklvcopy testlv 2 hdisk2
Testlv –lv name
2- No of copies, (we can make 3 copies also; this case you put 3 and mention hdisk0 then third copy will be available in hdisk0)
##mklvcopy testlv 3 hdisk0 ( It will make third lvcopy on hdisk0
After executing above command testlv is copied to hdisk2
If you want to confirm, execute the following command
#lslv –m testlv (it will show lvcopy details for testlv)
Hdiks1 hdisk2 hdisk0
Testlv (copy1) testlv (copy2) testlv (copy3)
We can create LV content copy to another PV, after this same LV content is available in Lvcopy configured PV.
#lspv
Hdisk0
Hdisk1
Hdisk2
#lspv –l hdisk1
Assume testlv available in hdisk1, now we will make testlv copy to hdisk2, using
After this testlv data available in both PV, hdisk1 and hdisk2, If hdisk1 is fail, we can recover testlv data from hdisk2
#mklvcopy testlv 2 hdisk2
Testlv –lv name
2- No of copies, (we can make 3 copies also; this case you put 3 and mention hdisk0 then third copy will be available in hdisk0)
##mklvcopy testlv 3 hdisk0 ( It will make third lvcopy on hdisk0
After executing above command testlv is copied to hdisk2
If you want to confirm, execute the following command
#lslv –m testlv (it will show lvcopy details for testlv)
Hdiks1 hdisk2 hdisk0
Testlv (copy1) testlv (copy2) testlv (copy3)
AIX - LVM - Change Logical Volume
AIX - LVM - Change Logical Volume
In this change LV option we can change LV name and permissions for the LV using chlv command.
#chlv –n newlvname oldlvname
#lslv testlv
Output is some details about testlv
#chlv –n newlv testlv
After executing the above command the testlv renamed to newlv
#lslv testlv
Some error message will come i.e. testlv is not found
#lslv newlv
It will show newlv details, because testlv is renamed as newlv.
Changing the LV permissions: If we want to change LV permissions to read only then the command will be
#chlv –p r testlv
After executing the above command testlv permissions changed as read only , so we can only read the LV, we can not copy new files into this LV.
In this change LV option we can change LV name and permissions for the LV using chlv command.
#chlv –n newlvname oldlvname
#lslv testlv
Output is some details about testlv
#chlv –n newlv testlv
After executing the above command the testlv renamed to newlv
#lslv testlv
Some error message will come i.e. testlv is not found
#lslv newlv
It will show newlv details, because testlv is renamed as newlv.
Changing the LV permissions: If we want to change LV permissions to read only then the command will be
#chlv –p r testlv
After executing the above command testlv permissions changed as read only , so we can only read the LV, we can not copy new files into this LV.
AIX - LVM - Extend Logical Volume
AIX - LVM - Extend Logical Volume
If we want to increase LV size using extendlv command
#lslv newlv
The above command shows LV size, no of LP’s and some other information about LV, suppose LV has 10 LP’s and usage is up to 95% full, that time we can increase the LV size online by adding no of LP’s in newlv i.e.
#extendlv newlv 5
After executing the above command 5 PP’s added with newlv, then some additional space will available in newlv. Suppose you want to see this changes again use the lslv command
#lslv newlv (it will show no of LV’s is 15 and some additional space)
If we want to increase LV size using extendlv command
#lslv newlv
The above command shows LV size, no of LP’s and some other information about LV, suppose LV has 10 LP’s and usage is up to 95% full, that time we can increase the LV size online by adding no of LP’s in newlv i.e.
#extendlv newlv 5
After executing the above command 5 PP’s added with newlv, then some additional space will available in newlv. Suppose you want to see this changes again use the lslv command
#lslv newlv (it will show no of LV’s is 15 and some additional space)
Subscribe to:
Posts (Atom)