diff options
| author | Jinshan Xiong <[email protected]> | 2016-04-12 16:14:07 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2016-04-26 15:13:13 -0700 |
| commit | 32cc01c42fc0fefaed58d22b4b1657f56e11f0fb (patch) | |
| tree | 40ae5a30a3c0a7f365b84b9737a7623d0f865c61 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 3c4b9d09729cb04070edb167c813884507f4e433 (diff) | |
staging: lustre: llite: error setting max_cache_mb at mount time
The root cause is that when max_cache_mb conf parameter is applied,
the client isn't connected to the OST yet so that sbi->ll_dt_exp is
NULL. However, it's not necessary to shrink the cache memory in this
case so success should be returned.
Signed-off-by: Jinshan Xiong <[email protected]>
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3676
Reviewed-on: http://review.whamcloud.com/7194
Reviewed-by: Andreas Dilger <[email protected]>
Reviewed-by: Bobi Jam <[email protected]>
Signed-off-by: James Simmons <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions