<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri, sans-serif" size="2">
<div>hi All,</div>
<div> </div>
<div>Re below – thanks for the replies to the fsck question.</div>
<div> </div>
<div>I have run fsck –r /data and this eventually completed with several changes made.</div>
<div> </div>
<div>Now I am getting the following error from the qla2xxx driver on boot </div>
<div> </div>
<div>.</div>
<div>.</div>
<div>.</div>
<div>qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.</div>
<div>qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.</div>
<div>.</div>
<div>etc</div>
<div>.</div>
<div> </div>
<div> </div>
<div>It looks like some administration of the HSV controlled SAN device layer itself is required – we </div>
<div>are now not even getting the boot process as far as the filesystem layer.</div>
<div> </div>
<div>(Anybody know exactly what that message indicates – e.g. whether a hardware fault or</div>
<div>HSV SAN config issue ?) </div>
<div> </div>
<div>googling this , somebody suggested a media scan from my storage array firmware, </div>
<div>then backing up the array and reinitializing logical disks and started fresh….however</div>
<div>if anybody has some more specific info than that, that would be great. (I don’t </div>
<div>have administrative access to these devices in any case)</div>
<div> </div>
<div>Looks like may have fsck’d on top of a wobbly device layer which probably does not</div>
<div>bode well :-(</div>
<div> </div>
<div>(I will summarise all of this to the list at some stage )</div>
<div> </div>
<div>Cheers</div>
<div> </div>
<div>AMcC</div>
<div> </div>
<div> </div>
<div>(Original post : )</div>
<div> </div>
<div>>A fault on our SAN dropped us down to a read-only filesystem and after reboot,</div>
<div>>we have an “Unexpected Inconsistency” and I am being instructed by the boot to run fsck manually</div>
<div>>without –a or –p (this was after I think processing around 15% of the filesystem)</div>
<div> </div>
<div>>The specific message is “inode 27344909 has illegal blocks”</div>
<div> </div>
<div>>I recall running fsck some years ago on smaller and simpler systems – am broadly</div>
<div>>familiar with what it is but have no expertise in using it to repair a filesystem.</div>
<div> </div>
<div>>Would be grateful for advice on whats the quickest / usual way to get us back up from </div>
<div>>this. We do have a good backup for restoring unrecoverable files – i.e. I assume I am going </div>
<div>>to end up asking fsck to repair the filesystem itself and then clean up any mess that </div>
<div>>results.</div>
<div> </div>
<div>>This is fsck 1.39 , Linux version 2.6.18-92.1.18.el5 , Red Hat 4.1.2-42</div>
<div> </div>
<div>>thanks for any tips.</div>
<div> </div>
<div>>Cheers</div>
<div> </div>
<div>>AMcC</div>
<div>>Bioinformatics Software Engineer</div>
<div>>AgResearch NZ</div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
</font>
<P align=left><FONT face=Arial size=1></FONT> </P><FONT face=Arial size=1>
<P align=left>
<HR>
</P>
<P align=left><STRONG>Attention: </STRONG>The information contained in this
message and/or attachments from AgResearch Limited is intended only for the
persons or entities to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other use of,
or taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch Limited.
If you have received this message in error, please notify the sender
immediately.</P>
<P align=left>
<HR>
</P>
<P> </P></FONT>
</body>
</html>