<div> </div> <div> I always get these annoying messages with EMC storages.</div> <div> </div> <div> They seem to have a unusable lun that appears for the operating system and the kernel keeps trying to access it.</div> <div> </div> <div> On RH 4.0 these messages appears on dmesg, I remember that RH 3.0 showed them on /var/log/messages also:</div> <div> </div> <div>SCSI error : <0 0 0 0> return code = 0x20000<BR>SCSI error : <0 0 0 0> return code = 0x20000<BR>SCSI error : <1 0 0 1> return code = 0x20000<BR>SCSI error : <0 0 0 0> return code = 0x20000<BR>SCSI error : <0 0 0 0> return code = 0x20000<BR>SCSI error : <1 0 0 0> return code = 0x20000<BR></div> <div> Anyone knows how to prevent the kernel from trying to access this lun?</div> <div> </div> <div>Regards,</div> <div>Luis Freitas<BR><BR><B><I>Daniel <daniel.anderzen@gmail.com></I></B>
wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello<BR><BR>System: Two brand new Dell 1950 servers with dual Intel Quadcore Xeon connected to an EMC CX3-20 SAN. Running CentOS 5 x86_64 - both with kernel 2.6.18-8.1.6-el5 x86_64.<BR><BR>I just noticed a panic on one of the servers: <BR><BR>Jul 2 04:08:52 megasrv2 kernel: (3568,2):dlm_drop_lockres_ref:2289 ERROR: while dropping ref on 87B24E40651A4C7C858EF03ED6F3595F:M00000000000000021af916b7dfbde4 (master=0) got -22.<BR>Jul 2 04:08:52 megasrv2 kernel: (3568,2):dlm_print_one_lock_resource:294 lockres: M00000000000000021af916b7dfbde4, owner=0, state=64 <BR>Jul 2 04:08:52 megasrv2 kernel: (3568,2):__dlm_print_one_lock_resource:309 lockres: M00000000000000021af916b7dfbde4, owner=0, state=64<BR>Jul 2 04:08:52 megasrv2 kernel: (3568,2):__dlm_print_one_lock_resource:311 last used: 4747810336, on purge list: yes <BR>Jul 2
04:08:52 megasrv2 kernel: (3568,2):dlm_print_lockres_refmap:277 refmap nodes: [ ], inflight=0<BR>Jul 2 04:08:52 megasrv2 kernel: (3568,2):__dlm_print_one_lock_resource:313 granted queue: <BR>Jul 2 04:08:52 megasrv2 kernel: (3568,2):__dlm_print_one_lock_resource:328 converting queue: <BR>Jul 2 04:08:52 megasrv2 kernel: (3568,2):__dlm_print_one_lock_resource:343 blocked queue: <BR>Jul 2 04:08:52 megasrv2 kernel: ----------- [cut here ] --------- [please bite here ] ---------<BR><BR>After booting the server I'm getting a lot of the following messages: <BR><BR>Jul 5 11:09:54 megasrv2 kernel: Additional sense: Logical unit not ready, manual intervention required<BR>Jul 5 11:09:54 megasrv2 kernel: end_request: I/O error, dev sdd, sector 0<BR>Jul 5 11:09:54 megasrv2 kernel: Buffer I/O error on device sdd, logical block 0 <BR>Jul 5 11:09:54 megasrv2 kernel: sd
1:0:0:2: Device not ready: <6>: Current: sense key: Not Ready<BR><BR>But I guess this one has something to do with EMC PowerPath as sdd is not a valid device. And there is no PowerPath for use with RHEL5 yet... <BR><BR>I'm sorry I haven't had the time to investigate this much. But right now I have no clue what caused this panic, or if it will happen again...<BR>_______________________________________________<BR>Ocfs2-users mailing list<BR>Ocfs2-users@oss.oracle.com<BR>http://oss.oracle.com/mailman/listinfo/ocfs2-users</BLOCKQUOTE><BR><p> 
<hr size=1>Luggage? GPS? Comic books? <br>
Check out fitting <a href="http://us.rd.yahoo.com/evt=48249/*http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz"> gifts for grads</a> at Yahoo! Search.