Thanks Kevin,
No, It's not that simple. This test program is not enough ;-)
DB2 is listed in the bug and actually the originator of the bz 165140.
I am still looking for some easy way to trigger this kernel AIO bug.
>>> On 1/10/2007 at 7:03 AM, "Kevin Closson" <kevinc@(protected)>
wrote:
> Seems somehting simple like
> http://oem.suse.com/pub/people/mason/utils/aio-stress.c would hit it.
I know
> libodm.so doesn't :-)
>
> -----Original Message-----
> From: Frank Westheider [mailto:frank.westheider@(protected)]
> Sent: Wednesday, January 10, 2007 3:50 AM
> To: 'Arun Singh'; suse-oracle@(protected)
> Subject: AW: AW: [suse-oracle] Kernel Bug
>
> Hi Warren,
> Hi Arun,
>
> As we saw while googling for this bug, IBM-DB2 is having the same
problem
> with exactly the same problem: aio.c:733.
>
> So it's not only an suse-oracle-problem!
>
> Bye
> Frank
>
> -----Urspr?ngliche Nachricht-----
> Von: Arun Singh [mailto:Arun.Singh@(protected)]
> Gesendet: Dienstag, 9. Januar 2007 22:16
> An: suse-oracle@(protected)
> Betreff: RE: AW: [suse-oracle] Kernel Bug
>
> Thanks Warren,
>
> Is there anyone who nailed this kernel bug in non-database
environment
> i.e. some sort of aio program?
>
>
>>>> On 1/9/2007 at 12:44 PM, "Stout, Warren" <WStout@(protected):
>
>> I've found it rather easy to create this problem. Just having
archive
>
>> logging on and running heavy I/O ( such as doing several imports )
> will
>> create this async problem. I had to turn off archive logging to get
> rid of
>> the errors.
>>
>> Warren
>>
>> -----Original Message-----
>> From: Arun Singh [mailto:Arun.Singh@(protected)]
>> Sent: Tue 1/9/2007 11:41 AM
>> To: Frank Westheider
>> Cc: 'Anton Dischner'; suse-oracle@(protected)
>> Subject: Re: AW: [suse-oracle] Novell - it is VERY SERIOUS!
> Weshouldadvise
>> against using SuSe and Oracle if
>>
>> Hi Frank,
>>
>> I can understand the frustration here as I am following this in the
>> bugzilla. You are right in asserting the complexity of the bug.
>>
>> Regards,
>> Arun
>>
>>>>> On 1/9/2007 at 11:11 AM, "Frank Westheider"
>> <frank.westheider@(protected)>
>> wrote:
>>> Hi Arun,
>>>
>>> Sorry...but cool down is not an option.
>>>
>>> We have this bug on 3 machines since beginning of september (!!!)
> and
>> opened
>>> novell and oracle support-cases....without any success/effort.
>>>
>>> We escalated these cases at novell and got 2 kernel-ptf-fixes...we
>> tested
>>> both and diffed the ptf-kernel-source with the original buggy
>>> kernel-source...and even we saw, that the difference were not
>> concerning the
>>> aio-kernel-part.
>>>
>>> We can reproduce the problem (and wrote this to the support too)
> with
>> heavy
>>> async-io-load over a duration of several days (batch-processes).
So
> i
>> think,
>>> this would be possible to Novell/Oracle/the kernel-guys as well
> with
>> simple
>>> db-jobs using aio and firing until the aio-bug is shown....
>>>
>>> Head-shaking about the support...beginning of september and no
> really
>> effort
>>> to fix this thing. I hope you know, what aio is doing for really
>> busy
>>> databases...
>>>
>>> Frank
>>>
>>> -----Urspr?ngliche Nachricht-----
>>> Von: Arun Singh [mailto:Arun.Singh@(protected)]
>>> Gesendet: Dienstag, 9. Januar 2007 16:34
>>> An: suse-oracle@(protected)
>>> Betreff: RE: [suse-oracle] Novell - it is VERY SERIOUS! We
>> shouldadvise
>>> against using SuSe and Oracle if suc
>>>
>>> Cool down folks. Do any of you have any easy way to trigger this
>> kernel bug?
>>> I can promise fix will take no time, If we can find a way to
> simulate
>> this
>>> bug internally. SUSE support/kernel team is aware of the
> seriousness
>> of this
>>> bug.
>>>
>>> -Arun
>>>
>>>
>>>
>>>>>> On 1/9/2007 at 1:16 AM, "Yoav Givon" <YGivon@(protected)>
wrote:
>>>> I strongly support you Alexei on this one. This is not very
>> business
>>>> like and I believe Novell Officials should make some strong
>> commitment
>>>> here other wise they will loose us . Loud and Clear.
>>>>
>>>> Yoav Givon
>>>>
>>>> -----Original Message-----
>>>> From: Alexei_Roudnev [mailto:Alexei_Roudnev@(protected)]
>>>> Sent: Monday, January 08, 2007 10:40 PM
>>>> To: Anton Dischner; Didier Boiteux
>>>> Cc: SuSE MailingList
>>>> Subject: [suse-oracle] Novell - it is VERY SERIOUS! We should
>> advise
>>>> against using SuSe and Oracle if such bugs are not fixed
> PROMPTLY!!
>> Re:
>>>> AW: [suse-oracle] kernel bug
>>>>
>>>> This is a critical bug - why it takes so long to fix it?
>>>>
>>>> Novell is not primary Linux in Oracle (it is not tested with it
>>>> automatically by internal users, as they do with RHEL4.4), so it
>> makes
>>>> a very important to fix such problems ASAP when they arise!)
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Anton Dischner" <Anton.Dischner@(protected)>
>>>> To: "Didier Boiteux" <dboiteux@(protected)>
>>>> Cc: "SuSE MailingList" <suse-oracle@(protected)>
>>>> Sent: Monday, January 08, 2007 12:54 AM
>>>> Subject: Re: AW: [suse-oracle] kernel bug
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> we had a kernel crash with a system which had the last kernel
>> patches
>>>>> installed.
>>>>>
>>>>> Kernel 2.6.5-7.283 did -not- fix the kernel BUG at fs/aio.c:733
>>>>> with bug number 165140
>>>>>
>>>>> regards,
>>>>>
>>>>> Toni
>>>>>
>>>>>
>>>>> --
>>>>>
>> +-----------------------------------------------------------------+
>>>>> | Anton Dischner, Unix admin, Oracle-DBA Phone: +49 89
>> 70953202|
>>>>> | Institut fuer Klinische Chemie Fax : +49 89
>> 70958888|
>>>>> | Klinikum Grosshadern Home : +49 89
>> 69708766|
>>>>> | Ludwig Maximilians Universitaet Muenchen Mobil: +49 172
>> 8388880|
>>>>> | 81366 Muenchen Germany
>> |
>>>>> | Marchioninistr. 15 Anton.Dischner"at"med.uni-muenchen.de
>
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting
