name_count maxed, losing inode data: dev=00:05, inode=5221
Eric Sandeen
sandeen at redhat.com
Tue Feb 2 19:50:25 UTC 2010
Christian Kujau wrote:
> On Mon, 1 Feb 2010 at 17:15, Ralf Hildebrandt wrote:
>
>> What does
>> name_count maxed, losing inode data: dev=00:05, inode=5221
>> mean?
>
> I don't know *what* it means exactly, but this has been reported earlier
> and it's still an open issue:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=445757
> https://bugzilla.redhat.com/show_bug.cgi?id=495207
>
> Christian.
This is all from the audit subsystem; it's not an ext3 issue AFAICT.
I'd push on those bugs if you're concerned. :)
-Eric
/* AUDIT_NAMES is the number of slots we reserve in the audit_context
* for saving names from getname(). */
#define AUDIT_NAMES 20
static int audit_inc_name_count(struct audit_context *context,
const struct inode *inode)
{
if (context->name_count >= AUDIT_NAMES) {
if (inode)
printk(KERN_DEBUG "name_count maxed, losing inode data: "
"dev=%02x:%02x, inode=%lu\n",
MAJOR(inode->i_sb->s_dev),
MINOR(inode->i_sb->s_dev),
inode->i_ino);
else
printk(KERN_DEBUG "name_count maxed, losing inode data\n");
return 1;
}
context->name_count++;
#if AUDIT_DEBUG
context->ino_count++;
#endif
return 0;
}
More information about the Ext3-users
mailing list