diff options
| author | David Teigland <teigland@redhat.com> | 2012-01-09 20:40:06 +0100 |
|---|---|---|
| committer | Steven Whitehouse <swhiteho@redhat.com> | 2012-01-11 10:23:40 +0100 |
| commit | e8ca5cc571a60339491f8c273a01093096ff8704 (patch) | |
| tree | e5133a5600113e8c2849675ab96dce0e6521aa09 /REPORTING-BUGS | |
| parent | GFS2: Fix a use-after-free that coverity spotted (diff) | |
| download | linux-e8ca5cc571a60339491f8c273a01093096ff8704.tar.xz linux-e8ca5cc571a60339491f8c273a01093096ff8704.zip | |
GFS2: let spectator mount do read only recovery
Previously, a spectator mount would not even attempt to do
journal recovery for a failed node. This meant that if all
mounted nodes were spectators, everyone would be stuck after
a node failed, all waiting for recovery to be performed.
This is unnecessary since the failed node had a clean journal.
Instead, allow a spectator mount to do a partial "read only"
recovery, which means it will check if the failed journal is
clean, and if so, report a successful recovery. If the failed
journal is not clean, it reports that journal recovery failed.
This makes it work the same as a read only mount on a read only
block device.
Signed-off-by: David Teigland <teigland@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions