On 10/30/18 05:01 PM, Udo Grabowski (IMK) wrote:
On 30/10/2018 16:46, Predrag Zečević - Technical Support Analyst wrote:


On 10/30/18 16:28, Bob Friesenhahn wrote:
On Tue, 30 Oct 2018, Udo Grabowski (IMK) wrote:

P.S: During this e-mail writing, number of file grew further:
$ find /var/cache/fontconfig/ -type f | wc -l
526905

man fam:
...
DESCRIPTION
      FAM, the File Alteration Monitor, is a subsystem that applications can       use to be notified when specific files or directories are changed.  It       is intended as a replacement for mechanisms such as poll and select.
....

So indeed that potentially can have something to do with your
problem if the process polluting your cache wants the FAM service
and doesn't get it and then falls back to something insane.

Recent illumos has added Linux compatibility functions to support LX Zone functionality and these compatibility functions might be picked up and used by
accident by software which targets Linux.  I don't know if there is an
emulation of inotify(7) but it seems like something important to emulate for
LX Zones.

Regardless, the Dtrace Toolkit provides scripts (opensnoop and iosnoop) which
allows observing all I/O activity on the system and so it should quickly
reveal the offender.

Bob
Hi,

no idea how I have missed opensnoop (probably because iosnoop I have tried was
useless):
$ /opt/DTT/Bin/iosnoop
  UID   PID D    BLOCK   SIZE       COMM PATHNAME
...
    0   381 W 275526024  32768 zpool-pz512 <none>
    0   381 W 283297216  32768 zpool-pz512 <none>
 2903 28881 R 256458773   7168 thunderbird <none>
 2903 28881 R 256795291   6656 thunderbird <none>
    0   381 W 322684424   4096 zpool-pz512 <none>

BUT, opensnoop showed guilty processes: firefox and thunderbird (which explains
no data increase, when logged off): Example

 2903  28883 firefox       53
/var/cache/fontconfig/d937d800-0615-4b33-a228-a4e53ca4493d-le32d4.cache-7
 2903  28883 firefox       53
...
Any suggestion?


This one ?
<https://bugzilla.mozilla.org/show_bug.cgi?id=1411338>


Predrag, considering the last comment in the Mozilla bug above (claiming the bug went away when updating fontconfig), would you care applying patches [1] newer than 2.13.1 release on top of userland fontconfig component, build it and testing? At lease some of them look to be related to your problem.

Michal

[1] https://cgit.freedesktop.org/fontconfig/log/

_______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to