Re: Bad Inode Map on /tmp

• Previous message: Mark Lamport: "Re: 64-bit Mode on AIX 4.3.3"
• Maybe in reply to: Aron, Iming W.: "Bad Inode Map on /tmp"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date:         Thu, 22 Sep 2005 12:01:31 +0200
To: aix-l@Princeton.EDU

fsck on an open filesystem can be misleading: if files are open and being
updated you will often see these sorts of errors. If the fsck says it's
clean, then it really is but if it shows errors they may not really be
there.
 
If you've done an fsck when /tmp was closed you can be confident that it's
OK.
 

-- 
Simon Green
Altria ITSC Europe s.a.r.l.
AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
 
N.B. Unsolicited email from vendors will not be appreciated.
Please post all follow-ups to the list.
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
Aron, Iming W.
Sent: 18 September 2005 17:06
To: aix-l@Princeton.EDU
Subject: Bad Inode Map on /tmp
We did a fsck (and verifying the file system in smit) of /tmp, and got the
message "File system inode map is corrupt (NOT FIXED) on AIX 5.3 (5300-02)
and /dev/hd3 (/tmp): Bad Inode Map (NOT SALVAGED) on AIX 5.2 (5200-05). All
the 20+ partitions on our P570s, P690 and a newly installed AIX 5.3 (@
5300-02) test box (7026-H80) have the same message about bad inode map on
/tmp.
 
We brought one partition to single user mode and did an fsck on /tmp, it
indicated that the /tmp file system is clean, rebooted the system to
multiple user, still have the same message on /tmp. We repeated the same for
another partition, same result.
 
Do any of you seeing the same message? Thanks in advance. 

• Previous message: Mark Lamport: "Re: 64-bit Mode on AIX 4.3.3"
• Maybe in reply to: Aron, Iming W.: "Bad Inode Map on /tmp"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]