From owner-freebsd-current@FreeBSD.ORG  Tue Sep 23 18:43:15 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 72A8F16A4B3
	for <current@freebsd.org>; Tue, 23 Sep 2003 18:43:15 -0700 (PDT)
Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8321B43FFD
	for <current@freebsd.org>; Tue, 23 Sep 2003 18:43:13 -0700 (PDT)
	(envelope-from apeiron@comcast.net)
Received: from comcast.net
	(pcp05043495pcs.levtwn01.pa.comcast.net[68.86.252.216])
	by comcast.net (sccrmhc12) with SMTP
	id <2003092401431301200f06mte>          (Authid: apeiron);
	Wed, 24 Sep 2003 01:43:13 +0000
Message-ID: <3F70F6B1.6010004@comcast.net>
Date: Tue, 23 Sep 2003 21:43:13 -0400
From: Christopher Nehren <apeiron@comcast.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
	rv:1.5b) Gecko/20030909 Thunderbird/0.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: current@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Inode number inconsistencies on UFS1 filesystem
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2003 01:43:15 -0000

I'm running 5.1-R, and having forgot to set up UFS2 for my file systems 
(doh!) I'm using ACLs the UFS1 way. All is well and good, for the most 
part, except that I'm getting a lot of messages like these:


/var/log/messages:Sep 22 20:38:01 <kern.crit> prophecy kernel: 
ufs_extattr_get (/var): inode number inconsistency (-1493839883, 
-1493839880)
/var/log/messages:Sep 22 20:38:01 <kern.crit> prophecy kernel: 
ufs_extattr_get (/var): inode number inconsistency (-462848829, -462848826)
/var/log/messages:Sep 22 20:38:21 <kern.crit> prophecy kernel: 
ufs_extattr_rm (/var): inode number inconsistency (-462848829, -462848826)

These messages _seem_ to show up when the system is under heavy load, 
but I haven't done extensive testing to verify that. What's peculiar, 
though, is that I haven't actually set up any extended attributes on my 
/var partition as of yet, but I have on /usr/home and it's not showing 
these errors. I checked the source, and from what I can see, it appears 
that the extended attribute checking code is expecting to find extended 
attribute(s) on the inodes specified -- but because no attributes exist 
on the entire partition, that check of course fails, with ENOATTR. The 
data on the partition appears to be fine: I've fscked it multiple times, 
and haven't seen any errors. If there's anything else that I can do to 
check the file system's integrity, I'd be delighted to learn of it and 
try whatever it is. Thanks in advance for any assistance with this.