Recent content by gileb

Hi, I often have seen problems of segmentation violation on bad writen prog that dont control the return of malloc. So, in this case, could be a memory allocation problem, therefore, a (bad) bypass could be to "unlimit" the user on stack. Sorry for not answering your question directly (i wont...

Hi, it is possible with /usr/lib/ras/ras_logger to log a message via the following command : /usr/lib/ras/ras_logger |& print -p ERRORLABEL print -p RESOURCE_NAME print -p KERNEL_M print -p DETAIL_DATA it worked for me on a 6.1. if you have HACMP it is included in the smit panels

Hi, We only have inlog jfs2 in our vg, and I've never seen this. Did you try to create the vg within the cspoc alors ?

Hi, You can also increase the ncargs value (in sys0) via a chdev. It can be too low in some case, but it solves a lot of "arg list too long" error messages to increase it.

Hello, I guess you have to be root as it uses some audit call. Did the chown work ? i didn't try, but it would be very useful

hi, i know the problem is solved, but for info, you can use the watch command, to see what files are accessed by your prog. And which one were not successfully opened. regards

Hello, Do you have the following apar installed on your aix ? IY68325 Just have a look at that, and, if installed, remove the -R flag on the piojet ...

i am not sure this parameter is taken in 4.5... You should instead modify the "smitty cm_time_before_warning" hope that helps

hi, do you have enough space in /tmp ?

hi, Do you have a dump ? how do you know it is a DMS ? As far as i know, getting in reconfiguration too long is not a problem, if cluster is only long to start, it gets correct at the end and returns to normal...

hi, just type the following to see if ^c is really generated by your keybord : trap "echo control-c" INT if when you do ^c it echoes, it means that it is trapped in your environment earlier.

Hi, This is quite an interesting thread. Do you have more details on how, we users, could pull such statistics ?

hmmm you are lucky there... i tryed to reproduce your problem and i cannot mount anymore the fs after the fsck => cannot write block xxxx while fsck'ing.... Don't try to call support after that ;-)

in cplv's man page : ... Attention: Do not copy from a larger logical volume containing data to a smaller one. Doing so results in a corrupted file system because some data (including the superblock) is not copied. ... i guess you have your answer no ? just do the getlvcb, to...

When you did the cplv, you have copied the lvcb - which contains the number of lp - so it is why you have a warning in the cplv just do a getlvcb -At small_lv and compare it to the big one. You will have 5 lp instead of 3.