APAR Number: IZ13342

——————————————————————————–

APAR status
Closed as program error.

Error description
Various filesystem corruption can be observed, if a filesystem
with AIX ACL(eav1) is shrinked.
Whole filesystem could be unusable or may lead to crashes.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED:
* AIX 6.1 systems with JFS2 filesystems with AIX ACLs (eav1)
* with the bos.mp64 fileset below the level of 6.1.0.4.
****************************************************************
* PROBLEM DESCRIPTION:
* Various filesystem corruption can occur when shrinking a JFS2
* filesystem with AIX ACLs. The filesystem may become unusable
* or may lead to system crashes.
****************************************************************
* RECOMMENDATION:
* Do not attempt to shrink JFS2 filesystems with AIX ACLs before
* installing the fix for APAR IZ13342.
****************************************************************
Problem conclusion
Intitialize eA extent array properly.
Temporary fix
*********
* HIPER *
*********
Comments
APAR information
APAR number IZ13342
Reported component name AIX 610
Reported component ID 5765G6200
Reported release 610
Status CLOSED PER
PE NoPE
HIPER YesHIPER
Submitted date 2008-01-17
Closed date 2008-01-17
Last modified date 2008-02-14

APAR is sysrouted FROM one or more of the following:
IZ08676

APAR is sysrouted TO one or more of the following:

Fix information
Fixed component name AIX 610
Fixed component ID 5765G6200

Applicable component levels
R610 PSY U815292 UP08/02/14 I 1000

APAR Number: IZ14395
While building a NIM spot, this error might be encountered:
warning: 0042-175 c_instspot: An unexpected result was
returned by the “/usr/sbin/unmount” command:
unmount: 0506-349 Cannot unmount /dev: The requested
resource is busy

APAR Number: IZ13376
Crash in scsidisk_process_sense when using non-MPIO disks

AIX OpenSSH creates trusted X11 cookie instead of untrusted

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA1

IBM SECURITY ADVISORY

First Issued: Tue Feb 5 14:00:03 CST 2008
===============================================================================
VULNERABILITY SUMMARY

VULNERABILITY: AIX OpenSSH creates trusted X11 cookie instead of untrusted

PLATFORMS: AIX 5.2, 5.3, 6.1

SOLUTION: Apply the fix or workaround as described below.

THREAT: Privilege elevation

CERT VU Number: n/a
CVE Number: CVE-2007-4752
===============================================================================
DETAILED INFORMATION

I. DESCRIPTION

OpenSSH could allow a remote attacker to gain elevated
privileges. Trusted X11 cookies are created when untrusted cookies
cannot be created, which could allow an attacker to bypass
security restrictions and gain elevated privileges using an
untrusted X client.

II. PLATFORM VULNERABILITY ASSESSMENT

To determine if your system is vulnerable, execute the following
command:

lslpp -L openssh.base.server

The following fileset levels are vulnerable:

AIX 6.1: all versions less than or equal to 4.5.0.5301
AIX 5.3: all versions less than or equal to 4.5.0.5301
AIX 5.2: all versions less than or equal to 4.5.0.5201

III. FIXES

A fix is available for AIX 6.1 and 5.3. The fix can be downloaded
from:

http://downloads.sourceforge.net/openssh-aix/openssh-4.5p1-r2.tar.Z

A fix for AIX 5.2 is not yet available. Please check this site
for updates:

http://sourceforge.net/projects/openssh-aix

IV. WORKAROUNDS

There are no workarounds.

V. CONTACT INFORMATION

If you would like to receive AIX Security Advisories via email,
please visit:

http://www14.software.ibm.com/webapp/set2/subscriptions/pqvcmjd

Comments regarding the content of this announcement can be
directed to:

security-alert@austin.ibm.com

To request the PGP public key that can be used to communicate
securely with the AIX Security Team you can either:

A. Send an email with “get key” in the subject line to:

security-alert@austin.ibm.com

B. Download the key from a PGP Public Key Server. The key ID is:

0xA6A36CCC

Please contact your local IBM AIX support center for any
assistance.

eServer is a trademark of International Business Machines
Corporation. IBM, AIX and pSeries are registered trademarks of
International Business Machines Corporation. All other trademarks
are property of their respective holders.

VI. ACKNOWLEDGMENTS

This security vulnerability in OpenSSH was found and fixed by Jan
Pechanec.

—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.4.7 (AIX)

iD8DBQFHqNr+8lficKajbMwRAv6SAJ933urcZNdzrPbM6/e+gLOXSyYNaACgieDO
6c+5H9mrC+XvWAjO4aDFXdY=
=yE8j
—–END PGP SIGNATURE—–

Interesting redbook released on ‘PowerVM’. This is the first I’ve heard of it, must be some marketing tactics. I hate marketing. =]

http://www.redbooks.ibm.com/redpieces/abstracts/sg247590.html

‘PowerVM™ is a combination of hardware and software that supports and manages the virtual environment s on POWER5™ , POWER5+™ and POWER6™ systems. It can help simplify and optimize your IT infrastructure.’

Chapter 1. Overview
Part 1. PowerVM virtualization management
Chapter 2. Virtual storage management
Chapter 3. Virtual network management
Chapter 4. Virtual I/O Server security
Chapter 5. Virtual I/O Server maintenance
Chapter 6. Dynamic operations
Chapter 7. PowerVM Live Partition Mobility
Chapter 8. System Planning Tool
Chapter 9. Automated management
Chapter 10. High level management
Part 2. PowerVM virtualization monitoring
Chapter 11. Monitoring global system resources allocations
Chapter 12. Monitoring commands on the Virtual I/O Server
Chapter 13. CPU monitoring
Chapter 14. Memory monitoring
Chapter 15. Virtual storage monitoring
Chapter 16. Virtual network monitoring
Chapter 17. AIX performance workbench
Chapter 18. Linux monitoring and useful third party tools
Chapter 19. Virtual I/O Server integration to IBM Tivoli
Appendix A. mkldap manual page
Appendix B. Example script for disc recovery on the AIX virtual client

Subsystem Device Driver Path Control Module

‘entstat ‘ will show you general Ethernet statistics in AIX. This will also give you link status, and show you the configured port speed/duplex settings.
Below you will see the output from entstat. The two important lines when determining speed and duplex are the ‘Media Speed Selected’ and ‘Media Speed Running’. The selected line displays the configuration of the adapter, whether its set to autonegotiate or configured to a specific setting. The one below is forced to 100/full. The running line will display what the adapter is actually running at. If this card were set to auto, you would see the negotiated speed.

-bash-2.05b$ entstat -d en1
————————————————————-
ETHERNET STATISTICS (en1) :
Device Type: 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
Hardware Address: xxx
Elapsed Time: 7 days 12 hours 47 minutes 48 seconds

Transmit Statistics: Receive Statistics:
——————– ——————-
Packets: 68946739 Packets: 56414525
Bytes: 182351384185 Bytes: 7089209177
Interrupts: 0 Interrupts: 52662037
Transmit Errors: 0 Receive Errors: 0
Packets Dropped: 0 Packets Dropped: 0
Bad Packets: 0
Max Packets on S/W Transmit Queue: 399
S/W Transmit Queue Overflow: 0
Current S/W+H/W Transmit Queue Length: 0

Broadcast Packets: 376 Broadcast Packets: 0
Multicast Packets: 1 Multicast Packets: 0
No Carrier Sense: 0 CRC Errors: 0
DMA Underrun: 0 DMA Overrun: 0
Lost CTS Errors: 0 Alignment Errors: 0
Max Collision Errors: 0 No Resource Errors: 0
Late Collision Errors: 0 Receive Collision Errors: 0
Deferred: 0 Packet Too Short Errors: 0
SQE Test: 0 Packet Too Long Errors: 0
Timeout Errors: 0 Packets Discarded by Adapter: 0
Single Collision Count: 0 Receiver Start Count: 0
Multiple Collision Count: 0
Current HW Transmit Queue Length: 0

General Statistics:
——————-
No mbuf Errors: 0
Adapter Reset Count: 0
Adapter Data Rate: 200
Driver Flags: Up Broadcast Running
Simplex 64BitSupport ChecksumOffload
PrivateSegment LargeSend DataRateSet

2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902) Specific Statistics:
————————————————————————
Link Status : Up
Media Speed Selected: 100 Mbps Full Duplex
Media Speed Running: 100 Mbps Full Duplex
PCI Mode: PCI-X (100-133)
PCI Bus Width: 64-bit
Latency Timer: 144
Cache Line Size: 128
Jumbo Frames: Disabled
TCP Segmentation Offload: Enabled
TCP Segmentation Offload Packets Transmitted: 2893566
TCP Segmentation Offload Packet Errors: 0
Transmit and Receive Flow Control Status: Disabled
Transmit and Receive Flow Control Threshold (High): 45056
Transmit and Receive Flow Control Threshold (Low): 24576
Transmit and Receive Storage Allocation (TX/RX): 16/48

The Ethernet failover configuration basically combines two physical adapters into one virtual adapter. If you have one link fail, the traffic will failover automatically to the second running adapter. The output below is a failover adapter, en4. This is configured using ent0 and ent2. The speed and duplex are set per adapter, prior to configuring the failover adapter.

Here’s an example of an ‘Etherchannel’ failover configuration:

-bash-2.05b$ entstat -d en4
————————————————————-
ETHERNET STATISTICS (en4) :
Device Type: EtherChannel
Hardware Address: xxxx
Elapsed Time: 7 days 12 hours 51 minutes 19 seconds

Transmit Statistics: Receive Statistics:
——————– ——————-
Packets: 279573147 Packets: 285159987
Bytes: 118141661339 Bytes: 64784751636
Interrupts: 0 Interrupts: 268857629
Transmit Errors: 0 Receive Errors: 0
Packets Dropped: 0 Packets Dropped: 0
Bad Packets: 0
Max Packets on S/W Transmit Queue: 84
S/W Transmit Queue Overflow: 0
Current S/W+H/W Transmit Queue Length: 2

Elapsed Time: 0 days 0 hours 0 minutes 0 seconds
Broadcast Packets: 55 Broadcast Packets: 1135188
Multicast Packets: 1 Multicast Packets: 0
No Carrier Sense: 0 CRC Errors: 0
DMA Underrun: 0 DMA Overrun: 0
Lost CTS Errors: 0 Alignment Errors: 0
Max Collision Errors: 0 No Resource Errors: 0
Late Collision Errors: 0 Receive Collision Errors: 0
Deferred: 0 Packet Too Short Errors: 0
SQE Test: 0 Packet Too Long Errors: 0
Timeout Errors: 0 Packets Discarded by Adapter: 0
Single Collision Count: 0 Receiver Start Count: 0
Multiple Collision Count: 0
Current HW Transmit Queue Length: 2

General Statistics:
——————-
No mbuf Errors: 0
Adapter Reset Count: 0
Adapter Data Rate: 200
Driver Flags: Up Broadcast Running
Simplex 64BitSupport ChecksumOffload
PrivateSegment LargeSend DataRateSet

=============================================================
=============================================================

Statistics for every adapter in the EtherChannel:
————————————————-

Number of adapters: 2
Active channel: primary channel
Operating mode: Network interface backup mode

————————————————————-

ETHERNET STATISTICS (ent0) :
Device Type: 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
Hardware Address: xxxx

Transmit Statistics: Receive Statistics:
——————– ——————-
Packets: 279573211 Packets: 284507186
Bytes: 118141675002 Bytes: 64731620778
Interrupts: 0 Interrupts: 268350807
Transmit Errors: 0 Receive Errors: 0
Packets Dropped: 0 Packets Dropped: 0
Bad Packets: 0
Max Packets on S/W Transmit Queue: 83
S/W Transmit Queue Overflow: 0
Current S/W+H/W Transmit Queue Length: 1

Broadcast Packets: 55 Broadcast Packets: 567594
Multicast Packets: 1 Multicast Packets: 0
No Carrier Sense: 0 CRC Errors: 0
DMA Underrun: 0 DMA Overrun: 0
Lost CTS Errors: 0 Alignment Errors: 0
Max Collision Errors: 0 No Resource Errors: 0
Late Collision Errors: 0 Receive Collision Errors: 0
Deferred: 0 Packet Too Short Errors: 0
SQE Test: 0 Packet Too Long Errors: 0
Timeout Errors: 0 Packets Discarded by Adapter: 0
Single Collision Count: 0 Receiver Start Count: 0
Multiple Collision Count: 0
Current HW Transmit Queue Length: 1

General Statistics:
——————-
No mbuf Errors: 0
Adapter Reset Count: 1
Adapter Data Rate: 200
Driver Flags: Up Broadcast Running
Simplex 64BitSupport ChecksumOffload
PrivateSegment LargeSend DataRateSet

2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902) Specific Statistics:
————————————————————————
Link Status : Up
Media Speed Selected: 100 Mbps Full Duplex
Media Speed Running: 100 Mbps Full Duplex
PCI Mode: PCI-X (100-133)
PCI Bus Width: 64-bit
Latency Timer: 144
Cache Line Size: 128
Jumbo Frames: Disabled
TCP Segmentation Offload: Enabled
TCP Segmentation Offload Packets Transmitted: 2709970
TCP Segmentation Offload Packet Errors: 0
Transmit and Receive Flow Control Status: Disabled
Transmit and Receive Flow Control Threshold (High): 45056
Transmit and Receive Flow Control Threshold (Low): 24576
Transmit and Receive Storage Allocation (TX/RX): 16/48

————————————————————-
Backup adapter - ent2:
======================

ETHERNET STATISTICS (ent2) :
Device Type: 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
Hardware Address: xxxx

Transmit Statistics: Receive Statistics:
——————– ——————-
Packets: 0 Packets: 652845
Bytes: 0 Bytes: 53137302
Interrupts: 0 Interrupts: 506852
Transmit Errors: 0 Receive Errors: 0
Packets Dropped: 0 Packets Dropped: 0
Bad Packets: 0
Max Packets on S/W Transmit Queue: 1
S/W Transmit Queue Overflow: 0
Current S/W+H/W Transmit Queue Length: 1

Broadcast Packets: 0 Broadcast Packets: 567594
Multicast Packets: 0 Multicast Packets: 0
No Carrier Sense: 0 CRC Errors: 0
DMA Underrun: 0 DMA Overrun: 0
Lost CTS Errors: 0 Alignment Errors: 0
Max Collision Errors: 0 No Resource Errors: 0
Late Collision Errors: 0 Receive Collision Errors: 0
Deferred: 0 Packet Too Short Errors: 0
SQE Test: 0 Packet Too Long Errors: 0
Timeout Errors: 0 Packets Discarded by Adapter: 0
Single Collision Count: 0 Receiver Start Count: 0
Multiple Collision Count: 0
Current HW Transmit Queue Length: 1

General Statistics:
——————-
No mbuf Errors: 0
Adapter Reset Count: 1
Adapter Data Rate: 200
Driver Flags: Up Broadcast Running
Simplex 64BitSupport ChecksumOffload
PrivateSegment LargeSend DataRateSet

2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902) Specific Statistics:
————————————————————————
Link Status : Up
Media Speed Selected: 100 Mbps Full Duplex
Media Speed Running: 100 Mbps Full Duplex
PCI Mode: PCI-X (100-133)
PCI Bus Width: 64-bit
Latency Timer: 144
Cache Line Size: 128
Jumbo Frames: Disabled
TCP Segmentation Offload: Enabled
TCP Segmentation Offload Packets Transmitted: 0
TCP Segmentation Offload Packet Errors: 0
Transmit and Receive Flow Control Status: Disabled
Transmit and Receive Flow Control Threshold (High): 45056
Transmit and Receive Flow Control Threshold (Low): 24576
Transmit and Receive Storage Allocation (TX/RX): 16/48

For some reason, I tend to forget about fcstat. This is a very useful command when troubleshooting fiber channel issues.

firmo1# fcstat fcs0

FIBRE CHANNEL STATISTICS REPORT: fcs0

Device Type: FC Adapter (df1000fa)
Serial Number: XXXXX
Option ROM Version: 02881914
Firmware Version: T1D1.90A4
World Wide Node Name: XXX
World Wide Port Name: XXX

FC-4 TYPES:
Supported: 0×0000012000000000000000000000000000000000000000000000000000000000
Active: 0×0000010000000000000000000000000000000000000000000000000000000000
Class of Service: 3
Port Speed (supported): 2 GBIT
Port Speed (running): 2 GBIT
Port FC ID: 0×010E00
Port Type: Fabric

Seconds Since Last Reset: 158286

Transmit Statistics Receive Statistics
——————- ——————
Frames: 80972 247978
Words: 1071104 84101632

LIP Count: 0
NOS Count: 0
Error Frames: 0
Dumped Frames: 0
Link Failure Count: 1
Loss of Sync Count: 5
Loss of Signal: 0
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 12
Invalid CRC Count: 0

IP over FC Adapter Driver Information
No DMA Resource Count: 0
No Adapter Elements Count: 0

FC SCSI Adapter Driver Information
No DMA Resource Count: 0
No Adapter Elements Count: 0
No Command Resource Count: 0

IP over FC Traffic Statistics
Input Requests: 0
Output Requests: 0
Control Requests: 0
Input Bytes: 0
Output Bytes: 0

FC SCSI Traffic Statistics
Input Requests: 4145
Output Requests: 12
Control Requests: 63356
Input Bytes: 330206300
Output Bytes: 49152

Pretty simple stuff, sort of like in Linux where you can run ‘ifconfig eth0:1 x.x.x.x’ and so on. In AIX, you can assign multiple IPs to an interface by using the following command syntax:

mktcpip -h $hostname -a $virtual_ip -m 255.255.255.0 -i $interface

where
$hostname = Your system hostanme, example: testhost
$virtual_ip = IP to assign to interface, example: 10.10.10.3
$interface = Interface you wish to assign the IP to, example: ent0

This is just a brief example of how to install AIX 6.1 SP2. For a more thorough install, you should always follow IBMs installation documentation.

That being said, you will first have to grab the SP2 filesets at http://www-912.ibm.com/eserver/support/fixes/fixcentral/pfixpacks/61

Go through the menus and grab the fileset for level 6100-00-02-0750 from December 2007. This is what you want.

First verify that you are at SP1 or lower by running the following:

bash-3.00# oslevel -s
6100-00-01-0748

At this point, you would have probably already created a backup, just in case things go south. If not, you should probably create a mksysb of the system now.

You’ll most likely want to commit all existing filesets too by running:

bash-3.00# installp -c all
+—————————————————————————–+
Pre-commit Verification…
+—————————————————————————–+
Verifying selections…done
Verifying requisites…done
Results…

WARNINGS
——–
Problems described in this section are not likely to be the source of any
immediate or serious failures, but further actions may be necessary or
desired.

Nothing to Commit
—————–
There is nothing in the APPLIED state that needs to be committed.

<< End of Warning Section >>

+—————————————————————————–+
BUILDDATE Verification …
+—————————————————————————–+
Verifying build dates…done

You’ll want to create a table of contents by running:

bash-3.00# inutoc ./
bash-3.00# ls -lart .toc
-rw-r–r– 1 root system 40540 Jan 09 21:24 .toc

Next you’re all ready to install SP2. Pretty simple huh?

I generally use the following flags with installp, or you can even do this through ’smit install’

bash-3.00# installp -a -d ./ -Y -p all

The ‘-a’ will apply packages only, ‘-d ./’ will specify the current directory for the filesets to install, -Y will say ‘Yes’ to all licenses, -p will preview, and of course ‘all’ will apply all filesets within the ‘-d’ location. Once you preview the install, you can remove -p and do the actual installation.

bash-3.00# installp -a -d ./ -Y -p all
*******************************************************************************
installp PREVIEW: installation will not actually occur.
*******************************************************************************

+—————————————————————————–+
Pre-installation Verification…
+—————————————————————————–+
Verifying selections…done
Verifying requisites…done
Results…

WARNINGS
——–
Problems described in this section are not likely to be the source of any
immediate or serious failures, but further actions may be necessary or
desired.

Already Installed
—————–
The following filesets which you selected are either already installed
or effectively installed through superseding filesets.

invscout.rte 2.2.0.12 # Inventory Scout Runtime
bos.alt_disk_install.boot_images 6.1.0.1 # Alternate Disk Installation …
devices.pci.02105e51.diag 6.1.0.1 # Native Display Graphics Adap…
bos.rte.boot 6.1.0.1 # Boot Commands
devices.common.rspcbase.rte 6.1.0.1 # RISC PC Common Base System D…
devices.pci.02105e51.rte 6.1.0.1 # Native Display Adapter Software
X11.base.lib 6.1.0.1 # AIXwindows Runtime Libraries
X11.apps.xdm 6.1.0.1 # AIXwindows xdm Application
sysmgt.websm.apps 6.1.0.1 # Web-based System Manager App…
X11.base.rte 6.1.0.1 # AIXwindows Runtime Environment
X11.base.smt 6.1.0.1 # AIXwindows Runtime Shared Me…
bos.rte.bosinst 6.1.0.1 # Base OS Install Commands
devices.scsi.tape.diag 6.1.0.1 # SCSI Tape Device Diagnostics
devices.chrp.base.diag 6.1.0.1 # RISC CHRP Base System Device…
devices.pci.77102224.com 6.1.0.1 # PCI-X FC Adapter (77102224) …
devices.pci.14106902.rte 6.1.0.1 # 10/100/1000 Base-TX PCI-X Ad…
devices.pci.df1000f7.com 6.1.0.1 # Common PCI FC Adapter Device…

NOTE: Base level filesets may be reinstalled using the “Force”
option (-F flag), or they may be removed, using the deinstall or
“Remove Software Products” facility (-u flag), and then reinstalled.

<< End of Warning Section >>

SUCCESSES
———
Filesets listed in this section passed pre-installation verification
and will be installed.

Mandatory Fileset Updates
————————-
(being installed automatically due to their importance)
bos.rte.install 6.1.0.2 # LPP Install Commands

<< End of Success Section >>

FILESET STATISTICS
——————
75 Selected to be installed, of which:
1 Passed pre-installation verification
17 Already installed (directly or via superseding filesets)
57 Deferred (see *NOTE below)
—-
1 Total to be installed

*NOTE The deferred filesets mentioned above will be processed after the
installp update and its requisites are successfully installed.

RESOURCES
———
Estimated system resource requirements for filesets being installed:
(All sizes are in 512-byte blocks)
Filesystem Needed Space Free Space
/usr 4200 168040
/tmp 424 129760
—– ——– ——
TOTAL: 4624 297800

NOTE: “Needed Space” values are calculated from data available prior
to installation. These are the estimated resources required for the
entire operation. Further resource checks will be made during
installation to verify that these initial estimates are sufficient.
Use the option to extend filesystems (-X flag) to ensure that any
additional resources which may be needed are automatically allocated.

******************************************************************************
End of installp PREVIEW. No apply operation has actually occurred.
******************************************************************************

bash-3.00# installp -a -d ./ -Y all

Once the installation is complete, you will see something similar to the following:

0503-409 installp: bosboot verification starting…
installp: bosboot verification completed.
0503-408 installp: bosboot process starting…

bosboot: Boot image is 36418 512 byte blocks.
0503-292 This update will not fully take effect until after a
system reboot.

* * * A T T E N T I O N * * *
System boot image has been updated. You should reboot the
system as soon as possible to properly integrate the changes
and to avoid disruption of current functionality.

installp: bosboot process completed.
+—————————————————————————–+
Summaries:
+—————————————————————————–+

Pre-installation Failure/Warning Summary
—————————————-
Name Level Pre-installation Failure/Warning
——————————————————————————-
ndaf.base.server 6.1.0.1 Requisite failure
ndaf.base.client 6.1.0.1 Requisite failure
ndaf.base.admin 6.1.0.1 Requisite failure
bos.net.nfs.cachefs 6.1.0.2 Requisite failure
bos.net.nfs.adt 6.1.0.1 Requisite failure
bos.mls.cfg 6.1.0.1 Requisite failure
bos.adt.prof 6.1.0.2 Requisite failure
bos.adt.debug 6.1.0.1 Requisite failure
X11.fnt.fontServer 6.1.0.1 Requisite failure
X11.Dt.lib 6.1.0.1 Requisite failure
bos.rte.install 6.1.0.2 Already installed

Installation Summary
——————–
Name Level Part Event Result
——————————————————————————-
bos.rte.mlslib 6.1.0.1 USR APPLY SUCCESS
bos.suma 6.1.0.1 USR APPLY SUCCESS
bos.suma 6.1.0.1 ROOT APPLY SUCCESS
ICU4C.rte 6.1.0.1 USR APPLY SUCCESS
bos.net.tcp.server 6.1.0.1 USR APPLY SUCCESS
bos.net.tcp.server 6.1.0.1 ROOT APPLY SUCCESS
invscout.rte 2.2.0.12 USR APPLY SUCCESS
invscout.rte 2.2.0.12 ROOT APPLY SUCCESS
bos.rte.boot 6.1.0.1 USR APPLY SUCCESS
bos.rte.boot 6.1.0.1 ROOT APPLY SUCCESS
devices.common.rspcbase.rte 6.1.0.1 USR APPLY SUCCESS
devices.pci.02105e51.diag 6.1.0.1 USR APPLY SUCCESS
devices.pci.02105e51.rte 6.1.0.1 USR APPLY SUCCESS
X11.apps.xdm 6.1.0.1 USR APPLY SUCCESS
bos.64bit 6.1.0.2 USR APPLY SUCCESS
devices.pci.1410ec02.rte 6.1.0.1 USR APPLY SUCCESS
bos.sysmgt.sysbr 6.1.0.2 USR APPLY SUCCESS
bos.sysmgt.sysbr 6.1.0.2 ROOT APPLY SUCCESS
bos.aixpert.cmds 6.1.0.2 USR APPLY SUCCESS
bos.aixpert.cmds 6.1.0.2 ROOT APPLY SUCCESS
bos.perf.libperfstat 6.1.0.1 USR APPLY SUCCESS
devices.chrp.IBM.lhea.rte 6.1.0.1 USR APPLY SUCCESS
devices.common.IBM.mpio.rte 6.1.0.2 USR APPLY SUCCESS
devices.fcp.disk.rte 6.1.0.2 USR APPLY SUCCESS
bos.perf.perfstat 6.1.0.1 USR APPLY SUCCESS
bos.rte.libc 6.1.0.2 USR APPLY SUCCESS
bos.rte.tty 6.1.0.2 USR APPLY SUCCESS
bos.pmapi.events 6.1.0.1 USR APPLY SUCCESS
bos.pmapi.lib 6.1.0.1 USR APPLY SUCCESS
bos.pmapi.pmsvcs 6.1.0.1 USR APPLY SUCCESS
bos.pmapi.tools 6.1.0.1 USR APPLY SUCCESS
bos.pmapi.tools 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.shell 6.1.0.2 USR APPLY SUCCESS
bos.rte.shell 6.1.0.2 ROOT APPLY SUCCESS
bos.rte.date 6.1.0.1 USR APPLY SUCCESS
bos.rte.date 6.1.0.1 ROOT APPLY SUCCESS
bos.perf.tune 6.1.0.1 USR APPLY SUCCESS
bos.perf.tune 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.security 6.1.0.2 USR APPLY SUCCESS
bos.rte.security 6.1.0.2 ROOT APPLY SUCCESS
bos.rte.control 6.1.0.2 USR APPLY SUCCESS
bos.rte.control 6.1.0.2 ROOT APPLY SUCCESS
devices.chrp.IBM.lhca.rte 6.1.0.2 USR APPLY SUCCESS
devices.pci.df1000f7.diag 6.1.0.1 USR APPLY SUCCESS
bos.perf.tools 6.1.0.2 USR APPLY SUCCESS
bos.perf.tools 6.1.0.2 ROOT APPLY SUCCESS
bos.adt.include 6.1.0.2 USR APPLY SUCCESS
bos.rte.serv_aid 6.1.0.2 USR APPLY SUCCESS
bos.rte.serv_aid 6.1.0.2 ROOT APPLY SUCCESS
bos.mp64 6.1.0.3 USR APPLY SUCCESS
bos.mp64 6.1.0.3 ROOT APPLY SUCCESS
bos.wpars 6.1.0.2 USR APPLY SUCCESS
bos.wpars 6.1.0.2 ROOT APPLY SUCCESS
bos.acct 6.1.0.2 USR APPLY SUCCESS
bos.acct 6.1.0.2 ROOT APPLY SUCCESS
bos.rte.filesystem 6.1.0.1 USR APPLY SUCCESS
bos.rte.filesystem 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.SRC 6.1.0.1 USR APPLY SUCCESS
bos.rte.SRC 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.archive 6.1.0.2 USR APPLY SUCCESS
bos.rte.archive 6.1.0.2 ROOT APPLY SUCCESS
bos.sysmgt.serv_aid 6.1.0.2 USR APPLY SUCCESS
bos.sysmgt.serv_aid 6.1.0.2 ROOT APPLY SUCCESS
bos.rte.commands 6.1.0.1 USR APPLY SUCCESS
bos.rte.lvm 6.1.0.2 USR APPLY SUCCESS
bos.rte.lvm 6.1.0.2 ROOT APPLY SUCCESS
bos.sysmgt.trace 6.1.0.2 USR APPLY SUCCESS
bos.sysmgt.trace 6.1.0.2 ROOT APPLY SUCCESS
sysmgt.pconsole.rte 6.1.0.1 USR APPLY SUCCESS
devices.common.IBM.ib.rte 6.1.0.2 USR APPLY SUCCESS
devices.usbif.08025002.rte 6.1.0.1 USR APPLY SUCCESS
devices.vdevice.IBM.v-scsi. 6.1.0.2 USR APPLY SUCCESS
devices.pci.00105000.com 6.1.0.1 USR APPLY SUCCESS
devices.chrp.base.rte 6.1.0.2 USR APPLY SUCCESS
devices.common.IBM.sissas.r 6.1.0.1 USR APPLY SUCCESS
bos.net.tcp.client 6.1.0.2 USR APPLY SUCCESS
bos.net.tcp.client 6.1.0.2 ROOT APPLY SUCCESS
bos.net.nfs.client 6.1.0.2 USR APPLY SUCCESS
bos.net.nfs.client 6.1.0.2 ROOT APPLY SUCCESS
X11.base.lib 6.1.0.1 USR APPLY SUCCESS
sysmgt.websm.apps 6.1.0.1 USR APPLY SUCCESS
X11.base.rte 6.1.0.1 USR APPLY SUCCESS
X11.base.smt 6.1.0.1 USR APPLY SUCCESS
bos.rte.bosinst 6.1.0.1 USR APPLY SUCCESS
devices.scsi.tape.diag 6.1.0.1 USR APPLY SUCCESS
bos.alt_disk_install.boot_i 6.1.0.1 USR APPLY SUCCESS
devices.chrp.base.diag 6.1.0.1 USR APPLY SUCCESS
devices.pci.df1000f7.com 6.1.0.1 USR APPLY SUCCESS
devices.pci.77102224.com 6.1.0.1 USR APPLY SUCCESS
devices.pci.14106902.rte 6.1.0.1 USR APPLY SUCCESS

installp: * * * A T T E N T I O N ! ! !
Software changes processed during this session require this system
and any of its diskless/dataless clients to be rebooted in order
for the changes to be made effective.

You now have SP2 applied.

bash-3.00# oslevel -s
6100-00-02-0750

AIX 6.1 allows you to mount a JFS2 filesystem without logging. This can increase performance by not requiring the FS to write metadata or log details. You could probably benefit by using this feature on temporary non-critical filesystems such as frequently used tmp space or a backup/restore tmp type of filesystem. With using this feature, you should assume that if the machine were to crash or you have other system related issues, you could potentially lose the entire non-logging filesystem.

If you still feel you can use this feature, you can mount by using the following:

To mount on the fly:

mount -o log=NULL /testfs

You will need to modify /etc/filesystems in order to make this change persistent across boots.