lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: "nils.doering--- via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] Deleted files held open by LTTng
Date: Mon, 12 Oct 2020 09:04:04 +0000	[thread overview]
Message-ID: <DB8P191MB1016B09FD65AF6B091A78C729D070@DB8P191MB1016.EURP191.PROD.OUTLOOK.COM> (raw)

Hi all,

I have recently started using LTTng and stumbled upon the fact, that
LTTng is keeping a lot of open file pointers to a single deleted file.

Specifically the process that holds these open is the lttng-consumerd and its
threads. The file that is held open, but is deleted is
/dev/shm/ust-shm-consumer-${PID} with the PID of the lttng-comsumerd. The
number of open file descriptors is dependent on the number of CPUs the
system has and results to 16 + (#CPUs * 16). Is this behavior expected?

# lsof | grep lttng | grep DEL
lttng-con  2280             root  DEL       REG               0,18               11128
        /dev/shm/ust-shm-consumer-2280
lttng-con  2280             root  DEL       REG               0,18               11127
        /dev/shm/ust-shm-consumer-2280
lttng-con  2280             root  DEL       REG               0,18               11126
        /dev/shm/ust-shm-consumer-2280
[...]

I have tested this on a Xen-Dom0 system running SLES 12 SP5 and on a
SLES12 SP5 without Xen.

Best regards,
Nils Döring
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2020-10-12  9:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12  9:04 nils.doering--- via lttng-dev [this message]
2020-10-12 13:17 ` [lttng-dev] Deleted files held open by LTTng Mathieu Desnoyers via lttng-dev
2020-10-13  6:47   ` nils.doering--- via lttng-dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DB8P191MB1016B09FD65AF6B091A78C729D070@DB8P191MB1016.EURP191.PROD.OUTLOOK.COM \
    --to=lttng-dev@lists.lttng.org \
    --cc=nils.doering@fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).