bad btree node

Hello out there, and HELP! We have had some hardware problems, which may or may not be fixed (AST 33pc). One table in particular has problems when we try to insert a row. We get a -271 error (could not insert row into table). I could add a row thru isql, but attempts to retrieve it caused isql to core dump in a malloc call. I unloaded the table and rebuilt it, but I am still getting the -271 error, along with the following yukky stuff in the Online error log. We have run a series of tbchecks, but they show no problems (cd, ci, ce, cr). 18:50:24 Logical Log 5523 Backed Up 18:52:35 bfcheck: bad page: pg_addr 10c80d != bp->bf_pagenum 120149, userp = 80401cb4, pid = 382, uid = 21710 18:52:35 buffer header: 18:52:35 805e2888: 00000000 00000000 f0385e80 04c85d80 ........ .8^...]. 18:52:35 805e2898: 64034080 08e55d80 02000000 0d0a0000 d.@...]. ........ 18:52:35 805e28a8: 49011200 00b86980 00000000 00000000 I.....i. ........ 18:52:35 805e28b8: 01000000 37585e80 00010000 ....7X^. .... 18:52:35 page header: 18:52:35 8069b800: 0dc81000 1ce74f01 24009000 08046403 ......O. $.....d. 18:52:35 8069b810: 5b020000 3c020000 [...<... 18:52:35 slot table and stamp: 18:52:35 8069bffc: 1ce74f01 ..O. 18:52:35 -- Fail Consistency Check -- btsearch:bad btree node -- pid=382 user=21710 us=80401cb4 18:55:12 Checkpoint Completed 19:00:32 Checkpoint Completed My only choice now, I think, is to tbunload the databases in the partition, initialize, and put it all back. I'm worried the tbunload will pick up the bad goop (good tekkie talk, huh). I may try anyway, out of desperation. What now? What should one do when you get bad btree nodes? I do not have enough unix file system space to unload and reload, and it would take hours and hours, close to days. This is a production system. Arggghhhh! Any hints would be most appreciated. p.s. We are run Online 4.1.UD3. -- Naomi Walker (aka N7FSA) naomi@anasazi.com Phoenix, Arizona To get the full value of joy, you must have someone to divide it with. ---Mark Twain