diff options
| author | JC Lafoucriere <[email protected]> | 2013-11-21 22:24:48 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2013-11-21 07:37:29 -0800 |
| commit | 5ea17d6cb9a72fbb7e5ab75868369bade2c5f2bc (patch) | |
| tree | af098f8a8b33f8f254140c601e112d42a3a4e0c2 /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | e1970ee78c16adf39cb4d240f7745109909ff26a (diff) | |
staging/lustre/llite: Access to released file triggers a restore
When a client accesses data in a released file,
or truncate it, client must trig a restore request.
During this restore, the client must not glimpse and
must use size from MDT. To bring the "restore is running"
information on the client we add a new t_state bit field
to mdt_info which will be used to carry transient file state.
To memorise this information in the inode we add a new flag
LLIF_FILE_RESTORING.
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3432
Lustre-change: http://review.whamcloud.com/6537
Signed-off-by: JC Lafoucriere <[email protected]>
Reviewed-by: Oleg Drokin <[email protected]>
Tested-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/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions