Re: Help, tbtape is trashing my rootdbs!

davek@informix.com (David Kosenko) writes: : I will speculate that the reason the second database seems to "cause" the : problem is that the space allocated for the tables in that database contain : the problem area. Since tbtape will only try to read allocated space, it : does not encounter the problem until the second database is created. I am : not sure why the bad block was not encountered at the create time - it must : be that the space allocated is not all read at the create time. : : What you should do is run a low-level disk surface check on the devices you : are using for your chunks. Typically, this problem is caused by bad blocks : present on the device. I suspected bad blocks on the device as well. I haven't low leveled the device just yet, but I figured I could easily find out if in fact there were bad blocks by using dd. Using dd I had it read the entire surface area and never got a hick-up. Since OnLine consistently has this problem during back-up I would assume that dd should have a problem reading the device as well--but that wasn't the case. Is my logic flawed in assuming dd would report some sort of error condition if it couldn't read some blocks on the partition? : As per bringing your system back up after a "bad block experience": if you : edit your tbconfig file and set MIRROR to 1, you will be able to restart : your system even though the chunk is marked as down. Thanks for the tip! -- +--------------------+-------------------------------------------------------+ | Michael Faurot | Domain: mfaurot@bogart.UUCP | | ------- ------ | UUCP: ...{irscscm|mimsy}!bogart!mfaurot | +--------------------+-------------------------------------------------------+