Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: I/O Error on SAN Disk
Operating Systems Solaris I/O Error on SAN Disk Post 302474663 by Mack1982 on Thursday 25th of November 2010 01:19:44 AM
Old 11-25-2010
Code:
Nov 22 18:03:07 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8677, run fsck(1M) -o f
Nov 22 18:04:37 plumcrt01 last message repeated 3 times
Nov 23 10:35:22 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8677, run fsck(1M) -o f
Nov 23 10:36:17 plumcrt01 last message repeated 2 times
Nov 23 10:36:53 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8677, run fsck(1M) -o f
Nov 23 11:03:40 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8677, run fsck(1M) -o f
Nov 23 11:05:45 plumcrt01 last message repeated 3 times
Nov 23 12:33:28 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8677, run fsck(1M) -o f
Nov 23 20:07:38 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8677, run fsck(1M) -o f
Nov 23 20:10:27 plumcrt01 last message repeated 3 times
Nov 24 03:00:12 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8612, run fsck(1M) -o f
Nov 24 08:58:32 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8677, run fsck(1M) -o f
Nov 24 18:01:53 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8612, run fsck(1M) -o f
Nov 24 18:04:59 plumcrt01 last message repeated 4 times
Nov 25 10:01:13 plumcrt01 ufs: [ID 879645 kern.notice] NOTICE: /opt/luminis: unexpected free inode 8677, run fsck(1M) -o f

 

10 More Discussions You Might Find Interesting

1. AIX

AIX disk less with SAN

Hi All, I have mirrored SAN volume on my B80 rootvg. Can I just remove the mirror and "Remove a P V from a V G" and it will be a diskless AIX? Is that going to boot on SAN rootvg volume? Thanks in advance, itik (3 Replies)
Discussion started by: itik
3 Replies

2. Filesystems, Disks and Memory

disk errors with san snapshot

so we have a solrais 9 system attached to an HP SAN. we are using sssu to do snap clones every hour. the only problem is the we get write errors on the solrais system every time we do a snap. from /var/adm/messages Apr 21 14:37:48 svr001 scsi: WARNING:... (0 Replies)
Discussion started by: robsonde
0 Replies

3. AIX

hard disk and san

Hello everyone I got several aix boxes with aix 5.3 I got a ibm san ds4500 My question is How can I do a match between my disks on aix and the san? I try to do a match with the LUN but for example. In my san I got several 1 LUN and on one of my aix box I got this If I type lscfg... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies

4. Solaris

SAN disk failure

hi all, have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ?? thanks in advance. (3 Replies)
Discussion started by: cesarNZ
3 Replies

5. Filesystems, Disks and Memory

SAN Disk w/o Cluster

Scenario: I've got 2 M5000's connected to a 9985 SAN storage array. I have configured the SAN disks with stmsboot, format and newfs. I can access the same SAN space from both systems. I have created files from both systems on the SAN space. Question: Why can't I see the file created... (3 Replies)
Discussion started by: bluescreen
3 Replies

6. UNIX for Dummies Questions & Answers

SAN and Disk I/O ... do we care?

Hi all, My main function is as a DBA. Another person manages the server and the SAN. I just want to know if I should be worried about high disk I/O or is it irrelevant as the I/O "load balancing" will be "taken care" of by the SAN? For example, I have hdisk1-5 and I can see that there are... (2 Replies)
Discussion started by: newbie_01
2 Replies

7. Solaris

Solaris 10 booting from EMC SAN DISK

Hi All, I have server : Sun-Fire-V490 configured with Solaris 10 zfs .. and I have configured three mirror the third one from EMC storage. root@server # zpool status -v pool: rpool state: ONLINE status: The pool is formatted using an older on-disk format. The pool can ... (8 Replies)
Discussion started by: top.level
8 Replies

8. Red Hat

Sharing SAN disk with multiple severs

Hi , I had a requirement to share a san disk between two rhel severs. I am planning to discover the same disk in two rhel nodes and mount it. Is it a feasible solution? and what kind of issues we may encounter mounting same disk in two OS's parallel ? (2 Replies)
Discussion started by: nanduri
2 Replies

9. AIX

San disk appearing double in old AIX

Hi guys, :) I'm a studient in IT field (AIX) I'm trying to map a LUN from a SAN (DS3400) to an AIX server (5300-04-00) I know there is no MPIO on this version of AIX, and i see double my LUN from the SAN root@localhost # lscfg | grep hdisk + hdisk7 ... (13 Replies)
Discussion started by: Tharsan
13 Replies

10. UNIX for Beginners Questions & Answers

SAN vs. Local disk.

I am in the market looking to purchase a new E950 server and I am trying to decide between using local SSD drives or SSD based SAN. The application that will be running on this server is read-intensive so I am looking for the most optimal configuration to support this application. There are no... (2 Replies)
Discussion started by: ikx
2 Replies

LEARN ABOUT HPUX

clri_hfs

clri(1M)																  clri(1M)

NAME

       clri - clear inode

SYNOPSIS

       special i-number  ...

DESCRIPTION

       The  command  clears  the  inode i-number by filling it with zeros.  special must be a special file name referring to a device containing a
       file system.  For proper results, special should not be mounted (see WARNINGS below).  After is executed, all blocks in the  affected  file
       show up as "missing" in an of special (see fsck(1M)).  This command should only be used in emergencies.

       Read and write permission is required on the specified special device.  The inode becomes allocatable.

WARNINGS

       The  primary  purpose of this command is to remove a file that for some reason does not appear in any directory.  If it is used to clear an
       inode that does appear in a directory, care should be taken to locate the entry and remove it.  Otherwise, when the inode is reallocated to
       some  new file, the old entry in the directory will still point to that file.  At that point, removing the old entry destroys the new file,
       causing the new entry to point to an unallocated inode, so the whole cycle is likely to be repeated again.

       If the file system is mounted, is likely to be ineffective.

DEPENDENCIES

       operates only on file systems of type

SEE ALSO

       fsck(1M), fsdb(1M), ncheck(1M).

STANDARDS CONFORMANCE

       clri: SVID2, SVID3

																	  clri(1M)
All times are GMT -4. The time now is 12:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy