- Original Message -
When gfs2 was mounted read-only and then unmounted, it was writing a
header block to the journal in the syncing gfs2_log_flush() call from
kill_sb(). This is because the journal was not being marked as idle
until the first log header was written out, and on a
Hi,
On 27/04/15 18:31, Benjamin Marzinski wrote:
On Mon, Apr 27, 2015 at 11:01:42AM +0100, Steven Whitehouse wrote:
Hi,
On 24/04/15 16:13, Benjamin Marzinski wrote:
When gfs2 was mounted read-only and then unmounted, it was writing a
header block to the journal in the syncing
Hi,
On 24/04/15 16:13, Benjamin Marzinski wrote:
When gfs2 was mounted read-only and then unmounted, it was writing a
header block to the journal in the syncing gfs2_log_flush() call from
kill_sb(). This is because the journal was not being marked as idle
until the first log header was written
On Mon, Apr 27, 2015 at 11:01:42AM +0100, Steven Whitehouse wrote:
Hi,
On 24/04/15 16:13, Benjamin Marzinski wrote:
When gfs2 was mounted read-only and then unmounted, it was writing a
header block to the journal in the syncing gfs2_log_flush() call from
kill_sb(). This is because the
When gfs2 was mounted read-only and then unmounted, it was writing a
header block to the journal in the syncing gfs2_log_flush() call from
kill_sb(). This is because the journal was not being marked as idle
until the first log header was written out, and on a read-only mount
there never was a log
- Original Message -
When gfs2 was mounted read-only and then unmounted, it was writing a
header block to the journal in the syncing gfs2_log_flush() call from
kill_sb(). This is because the journal was not being marked as idle
until the first log header was written out, and on a
