| commit | 7bc5c414fe6627ec518c82d154c796f0981f5b02 | |
| author | Abhijith Das <adas@redhat.com> | |
| Fri, 18 Jan 2008 20:06:37 +0000 (18 14:06 -0600) | ||
| committer | Steven Whitehouse <swhiteho@redhat.com> | |
| Fri, 25 Jan 2008 08:21:22 +0000 (25 08:21 +0000) | ||
| tree | affd4857934df6c86b6fde572de0370700e6fe9a | treesnapshot (tar.gz zip) |
| parent | 1b8177ec1e779bcc3ed89419ff7c80dbc3dcc489 | commitdiff |
[GFS2] Allow journal recovery on read-only mount
This patch allows gfs2 to perform journal recovery even if it is mounted
read-only. Strictly speaking, a read-only mount should not be writing to
the filesystem, but we do this only to perform journal recovery. A
read-only mount will fail if we don't recover the dirty journal. Also,
when gfs2 is used as a root filesystem, it will be mounted read-only
before being mounted read-write during the boot sequence. A failed
read-only mount will panic the machine during bootup.
Signed-off-by: Abhijith Das <adas@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
This patch allows gfs2 to perform journal recovery even if it is mounted
read-only. Strictly speaking, a read-only mount should not be writing to
the filesystem, but we do this only to perform journal recovery. A
read-only mount will fail if we don't recover the dirty journal. Also,
when gfs2 is used as a root filesystem, it will be mounted read-only
before being mounted read-write during the boot sequence. A failed
read-only mount will panic the machine during bootup.
Signed-off-by: Abhijith Das <adas@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
| fs/gfs2/recovery.c | diffblobblamehistory |