scsi disk errors
From: email@example.com (Matt Schalit)
Subject: Re: vxfs problems like: mesg 017: vx_iupderr - /home2 file system inode 1588 marked bad
Date: Wed, 26 Sep 2001 15:41:06 GMT
On Wed, 26 Sep 2001 10:01:13 GMT, proORGA-Leimen.firstname.lastname@example.org (Peter Michel) wrote:
>I really need help!
I don't think you *really* need help. You got it pretty
well figured out, though I don't know if it's a
vxfs question, as versus comp.ibm.pc.hardware.
> We have an UW2.1.3 box (very stable and fast,
>Ppro200/512) and from time to time we got errors
>from the adsl-driver (adaptec 2940UW) in the
>form see subject.
If you don't lose any data when that happens, and
if it happens rarely, then you could monitor it
for dramatic increases in frequency or number and
leave it at that.
If people are concerned about it or it's causing
problems with data, then throw some money at it.
Scsi problems hate money.
> Now i tested the drive of /home2 (IBM DCAS-34330W)
>with the IBM's "Drive Fitness Test" (DFT), codeupdt
>(last Version) and scsitool (last version, too).
>On all this tools, where i was able to get/show the
>defect-map i have zero defects in the growing list!
Very nice. And don't expect any either :-)
(with good ventilation and no banging on the PC
while it's running, that is...)
>So my question: what does "marked bad" mean?
OS can't access it for some reason.
>Is it only in the fs marked?
I though it was. I think that's what one of
those other tiny fs's is used for, storing bad area
information. Then again, I thought it was for
"badtracks" not bad inodes.
>My deeper thinging is:
>The errors came up - so my feeling - after replacing the Tanberg SLR4
>with a SLR5 tape and adding a 2.device IBM DNES-309170W to the
>scsi-bus before the 1.drive, with was and is the (only) terminated.
>All other things, like cable devices are the same all the time.
>Any ideas, help?
>Thanks a lot Peter
Yes, you just said it. "All other things, like cable devices are
the same all the time." Why not try the best scsi cables you can
find. Use those and see if the problem goes away. Try a differnt
2940UW. Want to borrow mine? :) There's a slight chance that it
could be an intermittent electical failure on the circuit board
of the hard drive somewhere, but that a real longshot. Try cables,
a different 2940, or patching the OS.
If this page was useful to you, please help others find it:
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site:
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Publishing your articles here
Jump to Comments
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.