On Tue, 6 Jun 2000, Alan Cox wrote:
> 2.3.5x/2.3.99 somewhere. 2.3.42 would be a good one to check
(one evening of compiling and rebooting later ...)
Here is my list of kernels I have tested 'db2 restore database ...' on.
"bad" good
2.3.42
2.3.33 (hmm, is it all 2.3's !?)
2.3.18 (nope)
2.3.24
2.3.27
2.3.30
2.3.29-pre2
2.3.29
2.3.30 (again, just to be sure)
2.4.0-test1-ac10
Each of these have been left for several minutes (should take < 10
seconds) before being considered as bad. Kernel cfgs are basically the
same around 2.3.30.
Does this make any sense? I'm a bit further back than I thought I would
be. There are 7 pre-patches from 2.3.29 to 2.3.30, but I won't be doing
that tonight. If someone has a better idea, please stop me.
Also, I'd like to repeat that other db2 stuff is working fine for me and
has for most 2.3.99/2.4.0's (not sure which I have tested, but I know I
have run it every now and then).
New shm in 2.3.5x, so that's not it. Right?
Anyone out there with a db2 that could test if 2.3.30 breaks db2 restore
and 2.3.29 works? and 2.4.0-test1-ac<current> ? I'd love to know it's not
just me.
Oh, and I just tested this:
% db2 backup database xyz to `pwd`
SQL2044N An error occurred while accessing a message queue. Reason code: ""
(the "" is supposed to tell you why ... "" = no problem? :)
ipcs says:
...
------ Message Queues --------
key msqid owner perms used-bytes messages
0x00000000 0 root 666 0 0
0x7707ee9e 2523142 db2inst1 765 0 0
But this could be some effect of restore failing earlier. Message queue
changes in 2.3.30?
/Urban
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:26 EST