aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorPatrick Farrell <[email protected]>2013-11-26 10:04:57 +0800
committerGreg Kroah-Hartman <[email protected]>2013-11-25 19:14:47 -0800
commitad8dbc93a464869f64365a2123b3491965df3b3e (patch)
treeaa58ec17c3449cee32c4d15c2634c808be8e5f0b /tools/perf/scripts/python
parent65f1c7816db85db02b2069f9d0e5111de52f5ee3 (diff)
staging/lustre/nfs: writing to new files will return ENOENT
This happend with SLES11SP2 Lustre client, which in turn acts as an NFS server, exporting a subtree of an Lustre fs through NFS. We detected that whenever we are writing to a new file using, fx, 'echo blah > newfile', it will return ENOENT error. We found out that this was caused by the anonymous dentry. In SLESS11SP2, anonymous dentries are assigned '/' as the name, instead of an empty string. When MDT handles the intent_open call, it will look up the obj by the name if it is not an empty string, and thus couldn't find it. As MDS_OPEN_BY_FID is always set on this request, we never need to send the name in this request. The fid is already available and should be used in case the file has been renamed. Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3544 Lustre-change: http://review.whamcloud.com/6920 Signed-off-by: Cheng Shao <[email protected]> Signed-off-by: Patrick Farrell <[email protected]> Reviewed-by: Bob Glossman <[email protected]> Reviewed-by: Alexey Shvetsov <[email protected]> Reviewed-by: Lai Siyao <[email protected]> Reviewed-by: James Simmons <[email protected]> Reviewed-by: Oleg Drokin <[email protected]> Signed-off-by: Peng Tao <[email protected]> Signed-off-by: Andreas Dilger <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions