[OpenAFS-port-darwin] 10.4.11 troubles

Derrick Brashear shadow@gmail.com
Mon, 10 Dec 2007 09:13:41 -0500


------=_Part_19046_21563469.1197296022022
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

disable spotlight on /afs; really, if someone is bored and wants to make
plutil suitable we should be able to make the installer do this, but i have
no scriptable way to add stuff to the exclusions plist.

On Dec 10, 2007 6:00 AM, Jonas Maebe <jonas.maebe@elis.ugent.be> wrote:

> Hello,
>
> Since upgrading to Mac OS X 10.4.11, I've already twice experienced
> the following problem: suddenly, both the kernel and mds go full
> blast (both using close to 100% cpu on my dual G5), with the system
> log being deluged by a barrage of the following message:
>
> Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
> is full! dropping events.
> Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
> is full! dropping events.
> Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
> is full! drog events.
> Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
> is full! dropping events.
> Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
> is full! dropping events.
> Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
> is full! dropping events.
> Dec 10 11:31:38 bigmac kernel[0]: fs_eve add_event: event queue is
> full! dropping events.
> Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
> is full! dropping events.
> Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
> is full! dropping events.
> [etc]
>
> (as you can see, syslogd sometimes can't even keep up)
>
> The first time this happened, it was while running a test program (on
> an AFS volume) which first opens and then closes as many files as
> possible (I believe with an upper limit of 100 files, but I'm not
> certain and currently cannot find it anymore). The second time, it
> was at the very end of an "svn update" (again on an AFS volume). It
> had apparently fully completed, as after the reboot "svn cleanup" did
> not mention anything that had to be cleaned up. Afaik, svn also
> closes a lot of locking files at the end of an update.
>
> I cannot reproduce the problem reliably though.
>
> Once the kernel and mds are in that cycle, there's no way to kill -9
> the triggering process, and killing mds doesn't help either.
> Rebooting doesn't work either (it hangs, presumably while trying to
> kill the hanging process), and a forced reboot is required.
>
> One more thing: both cases was with a prerelease of OpenAFS 1.4.5
> (the cvs version in which all the panics had been fixed). I don't
> know if later on some more things were committed which could solve
> this problem, so now I've installed the official 1.4.5 release.
>
> Is there anything I can do to further debug this problem?
>
>
> Jonas
> _______________________________________________
> port-darwin mailing list
> port-darwin@openafs.org
> https://lists.openafs.org/mailman/listinfo/port-darwin
>

------=_Part_19046_21563469.1197296022022
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

disable spotlight on /afs; really, if someone is bored and wants to make plutil suitable we should be able to make the installer do this, but i have no scriptable way to add stuff to the exclusions plist.<br><br><div class="gmail_quote">
On Dec 10, 2007 6:00 AM, Jonas Maebe &lt;<a href="mailto:jonas.maebe@elis.ugent.be">jonas.maebe@elis.ugent.be</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br><br>Since upgrading to Mac OS X 10.4.11, I&#39;ve already twice experienced<br>the following problem: suddenly, both the kernel and mds go full<br>blast (both using close to 100% cpu on my dual G5), with the system
<br>log being deluged by a barrage of the following message:<br><br>Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue<br>is full! dropping events.<br>Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue
<br>is full! dropping events.<br>Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue<br>is full! drog events.<br>Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue<br>is full! dropping events.
<br>Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue<br>is full! dropping events.<br>Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue<br>is full! dropping events.<br>Dec 10 11:31:38 bigmac kernel[0]: fs_eve add_event: event queue is
<br>full! dropping events.<br>Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue<br>is full! dropping events.<br>Dec 10 11:31:38 bigmac kernel[0]: fs_events: add_event: event queue<br>is full! dropping events.
<br>[etc]<br><br>(as you can see, syslogd sometimes can&#39;t even keep up)<br><br>The first time this happened, it was while running a test program (on<br>an AFS volume) which first opens and then closes as many files as
<br>possible (I believe with an upper limit of 100 files, but I&#39;m not<br>certain and currently cannot find it anymore). The second time, it<br>was at the very end of an &quot;svn update&quot; (again on an AFS volume). It
<br>had apparently fully completed, as after the reboot &quot;svn cleanup&quot; did<br>not mention anything that had to be cleaned up. Afaik, svn also<br>closes a lot of locking files at the end of an update.<br><br>I cannot reproduce the problem reliably though.
<br><br>Once the kernel and mds are in that cycle, there&#39;s no way to kill -9<br>the triggering process, and killing mds doesn&#39;t help either.<br>Rebooting doesn&#39;t work either (it hangs, presumably while trying to
<br>kill the hanging process), and a forced reboot is required.<br><br>One more thing: both cases was with a prerelease of OpenAFS 1.4.5<br>(the cvs version in which all the panics had been fixed). I don&#39;t<br>know if later on some more things were committed which could solve
<br>this problem, so now I&#39;ve installed the official 1.4.5 release.<br><br>Is there anything I can do to further debug this problem?<br><br><br>Jonas<br>_______________________________________________<br>port-darwin mailing list
<br><a href="mailto:port-darwin@openafs.org">port-darwin@openafs.org</a><br><a href="https://lists.openafs.org/mailman/listinfo/port-darwin" target="_blank">https://lists.openafs.org/mailman/listinfo/port-darwin</a><br></blockquote>
</div><br>

------=_Part_19046_21563469.1197296022022--