Sponsored Content
Operating Systems Linux kernel: Additional sense: Scsi parity error () Post 302271220 by sbn on Wednesday 24th of December 2008 09:28:53 AM
Old 12-24-2008
kernel: Additional sense: Scsi parity error ()

Hey guys how do you troubleshoot this kind of problem

kernel: Additional sense: Scsi parity error ()
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCSI Tape Error

When I am trying to read any tape I getthe following message on my screen: "stp: Error on SCSI tape=0 (ha=0 id=6 lun=0)" Does anybody know how to solve this problem and what the message means. I already have rebooted the server and cleaned the heads of the tape unit. HELP!!!! (1 Reply)
Discussion started by: Andre
1 Replies

2. Solaris

Sense Key: Media Error

Hi all, We have below WARNING in /var/adm/messages file from our Solaris server. WARNING: /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0 (sd0): Error for Command: write(10) Error Level: Fatal Requested Block: 16745265 Error Block: 16745269 Vendor: SEAGATE Serial Number:... (8 Replies)
Discussion started by: summerboy
8 Replies

3. Solaris

probe-scsi => error

i have a new netra 240 server when i make probe-scsi in obp i have this output : ERROR: /pci@1c,600000: Last Trap: Fast Data Access MMU Miss am upgarading obp firmware but the problem is always here the os solaris 10) is installed correctely and i can use it , when i type #format i can see... (2 Replies)
Discussion started by: lid-j-one
2 Replies

4. Shell Programming and Scripting

Replacing all occurences depending on parity

I want to replace all occurences of '$' in a LaTeX source code in the following way: The dollars on odd position in the file must be changed in '$latex ' and the other dollars can remain the same. I was thinking to make a script which replaces all odd occurences of a given character with a... (4 Replies)
Discussion started by: beni22sof
4 Replies

5. Solaris

Booting from wrong SCSI-disk. Error -256 Stack Underflow

Hi. I need to boot on Sun Blade 150 from scsi-disk, that ran on old Sun Ultra 10. It is necessary to take some the information from an old disk and something to study. The workstation is booted and I receive the following issue::mad: Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard (tip... (3 Replies)
Discussion started by: wolfgang
3 Replies

6. Solaris

solaris raids parity

what actually stored in the parity reserved on each slice in raid 5 configuration. how to restore the data if a disk is failed in raid5 configuration (1 Reply)
Discussion started by: revathireddy
1 Replies

7. Programming

This Makes NO sense. I'm making a game and getting an error, need help.

Okay so I'm making a simple text based game that branches into different scenarios. By branching I mean branching off into whole different files with that part of the game in it. I got tired of working on scenario 1 so I'm working on scenario 2. As I get started and try to test it, I get an error... (1 Reply)
Discussion started by: lemonoid
1 Replies

8. Shell Programming and Scripting

Shell Text Based Game, This Error Makes NO sense. Please help

Okay so I'm making a simple text based game that branches into different scenarios. By branching I mean branching off into whole different files with that part of the game in it. I got tired of working on scenario 1 so I'm working on scenario 2. As I get started and try to test it, I get an... (3 Replies)
Discussion started by: lemonoid
3 Replies

9. AIX

Readcd: Error 0. Cannot open SCSI driver.

i'm trying to burn an DVD ISO into a VIOS virtual optical drive when i try a scanbus i have a failure message : Can u help me please guys ---------- Post updated at 03:38 PM ---------- Previous update was at 12:20 PM ---------- I can't burn in ISO format, so i have to type... (0 Replies)
Discussion started by: Tharsan
0 Replies
IO::Wrap(3)						User Contributed Perl Documentation					       IO::Wrap(3)

NAME
IO::Wrap - wrap raw filehandles in IO::Handle interface SYNOPSIS
use IO::Wrap; ### Do stuff with any kind of filehandle (including a bare globref), or ### any kind of blessed object that responds to a print() message. ### sub do_stuff { my $fh = shift; ### At this point, we have no idea what the user gave us... ### a globref? a FileHandle? a scalar filehandle name? $fh = wraphandle($fh); ### At this point, we know we have an IO::Handle-like object! $fh->print("Hey there!"); ... } DESCRIPTION
Let's say you want to write some code which does I/O, but you don't want to force the caller to provide you with a FileHandle or IO::Handle object. You want them to be able to say: do_stuff(*STDOUT); do_stuff('STDERR'); do_stuff($some_FileHandle_object); do_stuff($some_IO_Handle_object); And even: do_stuff($any_object_with_a_print_method); Sure, one way to do it is to force the caller to use tiehandle(). But that puts the burden on them. Another way to do it is to use IO::Wrap, which provides you with the following functions: wraphandle SCALAR This function will take a single argument, and "wrap" it based on what it seems to be... o A raw scalar filehandle name, like "STDOUT" or "Class::HANDLE". In this case, the filehandle name is wrapped in an IO::Wrap object, which is returned. o A raw filehandle glob, like "*STDOUT". In this case, the filehandle glob is wrapped in an IO::Wrap object, which is returned. o A blessed FileHandle object. In this case, the FileHandle is wrapped in an IO::Wrap object if and only if your FileHandle class does not support the "read()" method. o Any other kind of blessed object, which is assumed to be already conformant to the IO::Handle interface. In this case, you just get back that object. If you get back an IO::Wrap object, it will obey a basic subset of the IO:: interface. That is, the following methods (note: I said methods, not named operators) should work on the thing you get back: close getline getlines print ARGS... read BUFFER,NBYTES seek POS,WHENCE tell NOTES
Clearly, when wrapping a raw external filehandle (like *STDOUT), I didn't want to close the file descriptor when the "wrapper" object is destroyed... since the user might not appreciate that! Hence, there's no DESTROY method in this class. When wrapping a FileHandle object, however, I believe that Perl will invoke the FileHandle::DESTROY when the last reference goes away, so in that case, the filehandle is closed if the wrapped FileHandle really was the last reference to it. WARNINGS
This module does not allow you to wrap filehandle names which are given as strings that lack the package they were opened in. That is, if a user opens FOO in package Foo, they must pass it to you either as "*FOO" or as "Foo::FOO". However, "STDIN" and friends will work just fine. VERSION
$Id: Wrap.pm,v 1.2 2005/02/10 21:21:53 dfs Exp $ AUTHOR
Primary Maintainer David F. Skoll (dfs@roaringpenguin.com). Original Author Eryq (eryq@zeegee.com). President, ZeeGee Software Inc (http://www.zeegee.com). POD ERRORS
Hey! The above document had some coding errors, which are explained below: Around line 212: '=item' outside of any '=over' =over without closing =back perl v5.18.2 2005-02-10 IO::Wrap(3)
All times are GMT -4. The time now is 04:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy