FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > EXT3 Users

 
 
LinkBack Thread Tools
 
Old 02-01-2010, 03:15 PM
Ralf Hildebrandt
 
Default name_count maxed, losing inode data: dev=00:05, inode=5221

What does
name_count maxed, losing inode data: dev=00:05, inode=5221
mean?

Today we booted from 2.6.31 -> 2.6.31.12 and got:

...
[ 66.829882] EXT3 FS on sda1, internal journal
[ 67.892792] name_count maxed, losing inode data: dev=00:05, inode=5221
[ 67.892875] name_count maxed, losing inode data: dev=00:05, inode=5214
[ 67.892883] name_count maxed, losing inode data: dev=00:05, inode=5225
[ 67.893033] name_count maxed, losing inode data: dev=00:05, inode=5225
[ 67.893045] name_count maxed, losing inode data: dev=00:05, inode=5225
[ 67.893110] name_count maxed, losing inode data: dev=00:05, inode=5214
[ 67.893118] name_count maxed, losing inode data: dev=00:05, inode=5229
[ 67.893270] name_count maxed, losing inode data: dev=00:05, inode=5229
[ 67.893278] name_count maxed, losing inode data: dev=00:05, inode=5229
[ 67.893392] name_count maxed, losing inode data: dev=00:05, inode=5214
[ 67.893401] name_count maxed, losing inode data: dev=00:05, inode=5233
[ 67.893555] name_count maxed, losing inode data: dev=00:05, inode=5233
[ 67.893563] name_count maxed, losing inode data: dev=00:05, inode=5233
[ 67.893634] name_count maxed, losing inode data: dev=00:05, inode=5214
[ 67.893643] name_count maxed, losing inode data: dev=00:05, inode=5237
[ 67.893792] name_count maxed, losing inode data: dev=00:05, inode=5237
[ 67.893801] name_count maxed, losing inode data: dev=00:05, inode=5237
[ 67.893868] name_count maxed, losing inode data: dev=00:05, inode=5214
[ 67.893877] name_count maxed, losing inode data: dev=00:05, inode=5241
[ 67.894010] name_count maxed, losing inode data: dev=00:05, inode=5241
[ 67.894019] name_count maxed, losing inode data: dev=00:05, inode=5241
[ 67.993863] name_count maxed, losing inode data: dev=00:05, inode=5258
[ 67.993934] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.993943] name_count maxed, losing inode data: dev=00:05, inode=5262
[ 67.994130] name_count maxed, losing inode data: dev=00:05, inode=5262
[ 67.994138] name_count maxed, losing inode data: dev=00:05, inode=5262
[ 67.994268] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.994277] name_count maxed, losing inode data: dev=00:05, inode=5266
[ 67.994593] name_count maxed, losing inode data: dev=00:05, inode=5266
[ 67.994602] name_count maxed, losing inode data: dev=00:05, inode=5266
[ 67.994670] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.994684] name_count maxed, losing inode data: dev=00:05, inode=5270
[ 67.995138] name_count maxed, losing inode data: dev=00:05, inode=5270
[ 67.995148] name_count maxed, losing inode data: dev=00:05, inode=5270
[ 67.995222] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.995231] name_count maxed, losing inode data: dev=00:05, inode=5274
[ 67.995369] name_count maxed, losing inode data: dev=00:05, inode=5274
[ 67.995377] name_count maxed, losing inode data: dev=00:05, inode=5274
[ 67.995440] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.995450] name_count maxed, losing inode data: dev=00:05, inode=5278
[ 67.995590] name_count maxed, losing inode data: dev=00:05, inode=5278
[ 67.995599] name_count maxed, losing inode data: dev=00:05, inode=5278
[ 67.995663] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.995672] name_count maxed, losing inode data: dev=00:05, inode=5282
[ 67.995833] name_count maxed, losing inode data: dev=00:05, inode=5282
[ 67.995841] name_count maxed, losing inode data: dev=00:05, inode=5282
[ 67.995906] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.995914] name_count maxed, losing inode data: dev=00:05, inode=5286
[ 67.996126] name_count maxed, losing inode data: dev=00:05, inode=5286
[ 67.996135] name_count maxed, losing inode data: dev=00:05, inode=5286
[ 67.996202] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.996211] name_count maxed, losing inode data: dev=00:05, inode=5290
[ 67.996391] name_count maxed, losing inode data: dev=00:05, inode=5290
[ 67.996400] name_count maxed, losing inode data: dev=00:05, inode=5290
[ 67.996483] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.996491] name_count maxed, losing inode data: dev=00:05, inode=5294
[ 67.996948] name_count maxed, losing inode data: dev=00:05, inode=5294
[ 67.996958] name_count maxed, losing inode data: dev=00:05, inode=5294
[ 67.997028] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.997036] name_count maxed, losing inode data: dev=00:05, inode=5298
[ 67.997190] name_count maxed, losing inode data: dev=00:05, inode=5298
[ 67.997198] name_count maxed, losing inode data: dev=00:05, inode=5298
[ 67.997272] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.997280] name_count maxed, losing inode data: dev=00:05, inode=5302
[ 67.997726] name_count maxed, losing inode data: dev=00:05, inode=5302
[ 67.997737] name_count maxed, losing inode data: dev=00:05, inode=5302
[ 67.997808] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.997817] name_count maxed, losing inode data: dev=00:05, inode=5306
[ 67.998233] name_count maxed, losing inode data: dev=00:05, inode=5306
[ 67.998247] name_count maxed, losing inode data: dev=00:05, inode=5306
[ 67.998322] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.998330] name_count maxed, losing inode data: dev=00:05, inode=5310
[ 67.998722] name_count maxed, losing inode data: dev=00:05, inode=5310
[ 67.998732] name_count maxed, losing inode data: dev=00:05, inode=5310
[ 67.998928] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.998937] name_count maxed, losing inode data: dev=00:05, inode=5314
[ 67.999206] name_count maxed, losing inode data: dev=00:05, inode=5314
[ 67.999216] name_count maxed, losing inode data: dev=00:05, inode=5314
[ 67.999295] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.999304] name_count maxed, losing inode data: dev=00:05, inode=5318
[ 67.999600] name_count maxed, losing inode data: dev=00:05, inode=5318
[ 67.999608] name_count maxed, losing inode data: dev=00:05, inode=5318
[ 67.999680] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.999688] name_count maxed, losing inode data: dev=00:05, inode=5322
[ 67.999844] name_count maxed, losing inode data: dev=00:05, inode=5322
[ 67.999853] name_count maxed, losing inode data: dev=00:05, inode=5322
[ 67.999915] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 67.999924] name_count maxed, losing inode data: dev=00:05, inode=5326
[ 68.000152] name_count maxed, losing inode data: dev=00:05, inode=5326
[ 68.000161] name_count maxed, losing inode data: dev=00:05, inode=5326
[ 68.000225] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 68.000233] name_count maxed, losing inode data: dev=00:05, inode=5330
[ 68.000415] name_count maxed, losing inode data: dev=00:05, inode=5330
[ 68.000423] name_count maxed, losing inode data: dev=00:05, inode=5330
[ 68.000487] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 68.000495] name_count maxed, losing inode data: dev=00:05, inode=5334
[ 68.000741] name_count maxed, losing inode data: dev=00:05, inode=5334
[ 68.000750] name_count maxed, losing inode data: dev=00:05, inode=5334
[ 68.000842] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 68.000851] name_count maxed, losing inode data: dev=00:05, inode=5338
[ 68.001034] name_count maxed, losing inode data: dev=00:05, inode=5338
[ 68.001043] name_count maxed, losing inode data: dev=00:05, inode=5338
[ 68.001104] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 68.001112] name_count maxed, losing inode data: dev=00:05, inode=5342
[ 68.001278] name_count maxed, losing inode data: dev=00:05, inode=5342
[ 68.001286] name_count maxed, losing inode data: dev=00:05, inode=5342
[ 68.001350] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 68.001359] name_count maxed, losing inode data: dev=00:05, inode=5346
[ 68.001518] name_count maxed, losing inode data: dev=00:05, inode=5346
[ 68.001527] name_count maxed, losing inode data: dev=00:05, inode=5346
[ 68.001596] name_count maxed, losing inode data: dev=00:05, inode=5251
[ 68.001604] name_count maxed, losing inode data: dev=00:05, inode=5350
[ 68.001810] name_count maxed, losing inode data: dev=00:05, inode=5350
[ 68.001819] name_count maxed, losing inode data: dev=00:05, inode=5350
[ 68.119718] EXT4-fs (dm-0): barriers enabled
...

--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebrandt@charite.de | http://www.charite.de


_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 02-02-2010, 06:40 PM
Christian Kujau
 
Default name_count maxed, losing inode data: dev=00:05, inode=5221

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.
--
BOFH excuse #196:

Me no internet, only janitor, me just wax floors.

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 02-02-2010, 06:50 PM
Eric Sandeen
 
Default name_count maxed, losing inode data: dev=00:05, inode=5221

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
",
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
");
return 1;
}
context->name_count++;
#if AUDIT_DEBUG
context->ino_count++;
#endif
return 0;
}

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 02-02-2010, 07:19 PM
Christian Kujau
 
Default name_count maxed, losing inode data: dev=00:05, inode=5221

On Tue, 2 Feb 2010 at 13:50, Eric Sandeen wrote:
> This is all from the audit subsystem; it's not an ext3 issue AFAICT.

Yeah, after grepping for it I've seen this now. However, I still don't
understand why it's printed at all and if it's something to worry about.
Well, probably not, since it's printed with KERN_DEBUG, but then these
messages should be supressed, no?

Also, can we alter the prinkt somewhat so it says where the message is
coming from? Something like:

diff --git a/linux-2.6-git/kernel/auditsc.c.orig b/linux-2.6-git/kernel/auditsc.c
index fc0f928..17d8708 100644
--- a/linux-2.6-git/kernel/auditsc.c.orig
+++ b/linux-2.6-git/kernel/auditsc.c
@@ -1893,14 +1893,14 @@ static int audit_inc_name_count(struct audit_context *context,
{
if (context->name_count >= AUDIT_NAMES) {
if (inode)
- printk(KERN_DEBUG "name_count maxed, losing inode data: "
+ printk(KERN_DEBUG "audit: name_count maxed, losing inode data: "
"dev=%02x:%02x, inode=%lu
",
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
");
+ printk(KERN_DEBUG "audit: name_count maxed, losing inode data
");
return 1;
}
context->name_count++;


Thanks,
Christian.
--
BOFH excuse #298:

Not enough interrupts

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 02-03-2010, 04:18 PM
Eric Sandeen
 
Default name_count maxed, losing inode data: dev=00:05, inode=5221

Christian Kujau wrote:
> On Tue, 2 Feb 2010 at 13:50, Eric Sandeen wrote:
>> This is all from the audit subsystem; it's not an ext3 issue AFAICT.
>
> Yeah, after grepping for it I've seen this now. However, I still don't
> understand why it's printed at all and if it's something to worry about.
> Well, probably not, since it's printed with KERN_DEBUG, but then these
> messages should be supressed, no?
>
> Also, can we alter the prinkt somewhat so it says where the message is
> coming from? Something like:

Sure, good idea - can you send that patch upstream, cc: eparis@redhat.com ?

-Eric

> diff --git a/linux-2.6-git/kernel/auditsc.c.orig b/linux-2.6-git/kernel/auditsc.c
> index fc0f928..17d8708 100644
> --- a/linux-2.6-git/kernel/auditsc.c.orig
> +++ b/linux-2.6-git/kernel/auditsc.c
> @@ -1893,14 +1893,14 @@ static int audit_inc_name_count(struct audit_context *context,
> {
> if (context->name_count >= AUDIT_NAMES) {
> if (inode)
> - printk(KERN_DEBUG "name_count maxed, losing inode data: "
> + printk(KERN_DEBUG "audit: name_count maxed, losing inode data: "
> "dev=%02x:%02x, inode=%lu
",
> 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
");
> + printk(KERN_DEBUG "audit: name_count maxed, losing inode data
");
> return 1;
> }
> context->name_count++;
>
>
> Thanks,
> Christian.

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 02-03-2010, 04:39 PM
Christian Kujau
 
Default name_count maxed, losing inode data: dev=00:05, inode=5221

Ralf Hildebrandt reported[0] the following messages on ext3-users:

name_count maxed, losing inode data: dev=00:05, inode=5221

because the filesystem in question is indeed ext3. However, this warning
is not generated by ext3 code but by the audit framework. While the
origins of these messages are discussed elsewhere[1] the following
patch modifies the printks in question so that users know where these
messages are coming from. There may be other places within the audit
framework needing the same treatment.

[0] http://www.redhat.com/archives/ext3-users/2010-February/msg00000.html
[1] https://bugzilla.redhat.com/show_bug.cgi?id=495207

Signed-off-by: Christian Kujau <lists@nerdbynature.de>
Reported-by: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Cc: Eric Paris <eparis@redhat.com>

auditsc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/linux-2.6-git/kernel/auditsc.c.orig b/linux-2.6-git/kernel/auditsc.c
index fc0f928..17d8708 100644
--- a/linux-2.6-git/kernel/auditsc.c.orig
+++ b/linux-2.6-git/kernel/auditsc.c
@@ -1893,14 +1893,14 @@ static int audit_inc_name_count(struct audit_context *context,
{
if (context->name_count >= AUDIT_NAMES) {
if (inode)
- printk(KERN_DEBUG "name_count maxed, losing inode data: "
+ printk(KERN_DEBUG "audit: name_count maxed, losing inode data: "
"dev=%02x:%02x, inode=%lu
",
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
");
+ printk(KERN_DEBUG "audit: name_count maxed, losing inode data
");
return 1;
}
context->name_count++;

--
BOFH excuse #298:

Not enough interrupts

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 

Thread Tools




All times are GMT. The time now is 10:00 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org