Displaying 2 results from an estimated 2 matches for "name_count".
2010 Feb 03
1
[PATCH] Re: 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...
2019 Sep 17
0
audit freeing multiple contexts (when running certbot)
...6.10
One has kernel 2.6.32-754.11.1.el6.i686 and the other has 2.6.32-754.18.2.el6.i686
Both have selinux, currently in permissive mode.
On both machines we have noticed messages like the following appear in /var/log/messages
from time to time:
Sep 17 10:32:28 merlin kernel: audit(:0): major=252 name_count=0: freeing multiple contexts (1)
Sep 17 10:32:28 merlin kernel: audit(:0): major=355 name_count=0: freeing multiple contexts (2)
Sep 17 10:32:29 merlin kernel: audit(:0): major=252 name_count=0: freeing multiple contexts (1)
Sep 17 10:32:29 merlin kernel: audit(:0): major=355 name_count=0: freeing...