I can reproducibly trigger this error on the server by doing multiple
instances of pvfs2-cp over various IB hardware.
For this one, I did:
pvfs2-cp -t /pvfs2/1node/test2 /dev/null & pvfs2-cp -t
/pvfs2/1node/test2 /dev/null & pvfs2-cp -t /pvfs2/1node/test2 /dev/null
& pvfs2-cp -t /pvfs2/1nod
Right now that backtrace isn't very useful. I think the backtrace on
segfault will print source files and lines if you compile with
debugging. Configure with --enable-strict or build with CFLAGS=-g.
It looks like the segfault might not be directly related to the bmi
ib error that you're
Hi Phil,
Good idea to look at the other file systems. My (admittedly limited)
understanding of disconnected dentries is based on the Documentation/
filesystems/Exporting doc, which may be a bit outdated. It suggests
that lookup should return whatever d_splice_alias returns (assuming the
On Apr 4, 2007, at 4:37 PM, Phil Carns wrote:
Hi Phil,
Good idea to look at the other file systems. My (admittedly
limited) understanding of disconnected dentries is based on the
Documentation/ filesystems/Exporting doc, which may be a bit
outdated. It suggests that lookup should re
