ITEM: BC2932L

No more sybase kprocs for async I/O subsystem. 3.2.5.1

ENV:    970, 3.2.5

DESC:   Sybase dataserver.
        Customer has 2 systems. one is at 3.2.5 and the other is at
        3.2.5.1.
        He also has the 9333 disk subsystem using Async I/O.
        AT 3.2.5 root has 7 kprocs and sybase owns a couple kprocs,
        one for each Logical Volume that is used by sybase.
        These kprocs are the ones used for Async I/O control and
        can be seen as aio processes using the pstat -a command.
                At 3.2.5.1 the sybase owned kprocs no longer run. So the
        customer believes that Async I/O is no longer working. 
        Customer wants to know what is wrong here and how to fix it.
        Act:    Had customer look at smit aio and he had 10 servers set for the
        max value. The two systems look the same except that at 3.2.5.1 
        the aio kprocs are not runnig. 

        As a result of PTF U436267, (APAR IX45547) aio was enhanced to
        use a fast path when the request was targeted for a raw logical 
        volume.  The fast path does not require kprocs; therefore,
        fewer kprocs are created.

Next:   close   



Support Line: No more sybase kprocs for async I/O subsystem. 3.2.5.1 ITEM: BC2932L

Dated: December 1995 Category: N/A

This HTML file was generated 99/06/24~13:30:23

Comments or suggestions?
Contact us