Re: v4.2.2.2 - problems with expire inventory

2002-05-15 Thread Burak Demircan

Hi Everybody, 
I am very disappointed with 4.2.2 patch levels. I upgraded to 4.2.2.1 and saw 
the worst version 
I have ever seen. I think we all should stick to 4.2.2.0 for a time or upgrade 
5.1.x.x 
Regards, 
Burak 





[EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED] 

15.05.2002 17:24 
Please respond to ADSM-L 
        
        To:        [EMAIL PROTECTED] 
        cc:         
        Subject:        v4.2.2.2 - problems with expire inventory

On our well-behaved and moderately loaded system, I am not seeing a
problem with anything in v4.2.2.2 (AIX 4.3.3). However, on the more
'abused' systems, ones that are constantly migrating and have users
on them all the time, the expiration hangs whenever there is a
migration, reclamation or move data going on. Simultaneous expiration
and migration wasn't a problem on the well-behaved server.
 
I am letting one run with a migration right now to see if it
eventually resolves itself (deadlock?). Right now, it's going on
15 minutes and has locked up the other migration process. I'm not
sure if backups to the disk pool are affected yet. At 30 minutes or
so, I'll halt the server, restart and call the problen in.
 
Gretchen Thiele
Princeton University
 




v4.2.2.2 - problems with expire inventory

2002-05-15 Thread Gretchen L. Thiele

On our well-behaved and moderately loaded system, I am not seeing a
problem with anything in v4.2.2.2 (AIX 4.3.3). However, on the more
'abused' systems, ones that are constantly migrating and have users
on them all the time, the expiration hangs whenever there is a
migration, reclamation or move data going on. Simultaneous expiration
and migration wasn't a problem on the well-behaved server.

I am letting one run with a migration right now to see if it
eventually resolves itself (deadlock?). Right now, it's going on
15 minutes and has locked up the other migration process. I'm not
sure if backups to the disk pool are affected yet. At 30 minutes or
so, I'll halt the server, restart and call the problen in.

Gretchen Thiele
Princeton University