GFS2: Fix error handling when reading an invalid block from the journal
authorSteven Whitehouse <steve@chygwyn.com>
Tue, 29 May 2012 09:47:51 +0000 (10:47 +0100)
committerSteven Whitehouse <swhiteho@redhat.com>
Wed, 6 Jun 2012 10:27:49 +0000 (11:27 +0100)
commit1b8ba31a88c5115687095ca2a01bfcaecb489b5a
treec32f35c93758abaeea64430d3ef824d9a2ef8fb4
parent23d0bb834e264f38335f19fe601564b8422431e7
GFS2: Fix error handling when reading an invalid block from the journal

When we read an invalid block from the journal, we should not call
withdraw, but simply print a message and return an error. It is
up to the caller to then handle that error. In the case of mount
that means a failed mount, rather than a withdraw (requiring a
reboot). In the case of recovering another nodes journal then
we return an error via the uevent.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/gfs2/lops.c
fs/gfs2/util.h
This page took 0.244486 seconds and 5 git commands to generate.