Bug #1047
closedbabeltrace error reading trace on a NFS filesystem
0%
Description
Trying to run babeltrace on the cubietruck:
master 97b9d59e8ae35c548281af4f0b40647027019214
root@linaro-nano:~/lttng-traces/auto-20160715-195804# babeltrace .
Error on fpathconf: Value too large for defined data type
[error] Failed to get _PC_NAME_MAX for path "./ust/uid/0/32-bit".
[warning] [Context] Cannot open_trace of format ctf at path ./ust/uid/0/32-bit.
[warning] [Context] cannot open trace "./ust/uid/0/32-bit" from . for reading.
[error] Cannot open any trace for reading.
[error] opening trace "." for reading.
[error] none of the specified trace paths could be opened.
Updated by Mathieu Desnoyers almost 8 years ago
Seems to happen when the trace is in a NFS filesystem. Happens with stable-1.4 too.
Works fine if I move the trace to a ext4 filesystem on the same machine.
Updated by Mathieu Desnoyers almost 8 years ago
- Subject changed from babeltrace error on arm32 to babeltrace error reading trace on a NFS filesystem
Updated by Mathieu Desnoyers almost 8 years ago
Seems to be the culprit:
pc_name_max = fpathconf(td->dirfd, _PC_NAME_MAX);
if (pc_name_max < 0) {
perror("Error on fpathconf");
fprintf(stderr, "[error] Failed to get _PC_NAME_MAX for path \"%s\".\n", path);
ret = -1;
goto error_metadata;
}
The question is why fpathconf fails on NFS ?
Updated by Jonathan Rajotte Julien about 4 years ago
- Status changed from New to Invalid
State of babeltrace moved a lot since.
Closing this ticket as invalid. Reopen it if it stills apply to Babeltrace 2.