Project

General

Profile

Bug #1004

New trace can't generate in persistent memory file system

Added by jia fang about 5 years ago. Updated over 3 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Start date:
03/15/2016
Due date:
% Done:

0%

Estimated time:

Description

Using the new feature Recording trace data on persistent memory file systems in LTTng 2.7.

After the device restart due to system crash, we can read the crash log in the specific shm-path directory. When we want to trace the new log, the following debug log reported and the new data can't be traced to the specific shm-path.

DEBUG3 - 20:07:54.353680 [286/291]: mkdir() recursive /shm/lttng/mysession-20160302-182255/ust/uid/0/32-bit with mode 504 for uid 0 and gid 0 (in run_as_mkdir_recursive() at runas.c:468)
DEBUG1 - 20:07:54.353726 [286/291]: Using run_as worker (in run_as() at runas.c:449)
DEBUG3 - 20:07:54.354141 [286/291]: open() /shm/lttng/mysession-20160302-182255/ust/uid/0/32-bit/metadata with flags C1 mode 384 for uid 0 and gid 0 (in run_as_open() at runas.c:498)
DEBUG1 - 20:07:54.354202 [286/291]: Using run_as worker (in run_as() at runas.c:449)
PERROR - 20:07:54.354724 [286/291]: Opening metadata file: File exists (in ust_registry_session_init() at ust-registry.c:606)
DEBUG3 - 20:07:54.354801 [286/291]: rmdir_recursive() /shm/lttng/mysession-20160302-182255 with for uid 0 and gid 0 (in run_as_rmdir_recursive() at runas.c:524)
DEBUG1 - 20:07:54.354847 [286/291]: Using run_as worker (in run_as() at runas.c:449)
DEBUG3 - 20:07:54.355554 [287/287]: Attempting rmdir /shm/lttng/mysession-20160302-182255 (in utils_recursive_rmdir() at utils.c:1247)
DEBUG3 - 20:07:54.356905 [286/291]: Buffer registry per UID destroy with id: 0, ABI: 32, uid: 0 (in buffer_reg_uid_destroy() at buffer-registry.c:641)

For detail info, please see my attachment.


Files

lttng debug log (7.37 KB) lttng debug log jia fang, 03/15/2016 06:52 AM

Related issues

Copied to LTTng-tools - Bug #1005: New trace can't generate in persistent memory file systemResolvedJonathan Rajotte Julien03/15/2016

Actions
#1

Updated by jia fang about 5 years ago

  • Copied to Bug #1005: New trace can't generate in persistent memory file system added
#2

Updated by Mathieu Desnoyers over 3 years ago

  • Status changed from New to Invalid

Belongs to lttng-tools.

Also available in: Atom PDF