diff options
| author | Bobi Jam <[email protected]> | 2015-03-25 21:53:21 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2015-03-26 11:10:24 +0100 |
| commit | 4345abb2c3b56eae9bcf4728dcdc0f584690c8aa (patch) | |
| tree | f7b193e34d0ac58fcc31e986db4dbd204bcb4be9 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 1c8aa54aaf2c74a28a9e427bb27fd1a12fca8536 (diff) | |
staging/lustre/mgc: detach MGC dev on error
lustre_start_mgc() creates MGC device, if error happens later on
ll_fill_super(), this device is still attached, and later mount
fails by keep complaining that the MGC device's already in the
client node.
It turns out that the device was referenced by mgc config llog data
which is arranged in the mgc lock requeue thread re-trying to get its
mgc lock, and in normal case, this llog reference only released in
mgc_blocking_ast() when the system is umount.
This patch make mgc_precleanup() to wake up requeue thread to handle
the config llog data.
This patch also makes mgc_setup() wait for mgc_requeue_thread() start
before moving on.
Signed-off-by: Bobi Jam <[email protected]>
Reviewed-on: http://review.whamcloud.com/11765
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4943
Reviewed-by: Ryan Haasken <[email protected]>
Signed-off-by: Oleg Drokin <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions