Bob Peterson d534300dd7 gfs2: Allow lock_nolock mount to specify jid=X
[ Upstream commit ea22eee4e6027d8927099de344f7fff43c507ef9 ]

Before this patch, a simple typo accidentally added \n to the jid=
string for lock_nolock mounts. This made it impossible to mount a
gfs2 file system with a journal other than journal0. Thus:

mount -tgfs2 -o hostdata="jid=1" <device> <mount pt>

Resulted in:
mount: wrong fs type, bad option, bad superblock on <device>

In most cases this is not a problem. However, for debugging and
testing purposes we sometimes want to test the integrity of other
journals. This patch removes the unnecessary \n and thus allows
lock_nolock users to specify an alternate journal.

Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2020-06-30 15:38:28 -04:00
..
2016-05-12 22:28:05 -04:00
2016-06-27 09:47:09 -05:00
2016-06-27 09:47:08 -05:00
2018-05-30 07:50:47 +02:00
2016-06-27 09:47:09 -05:00
2017-07-12 15:01:06 +02:00
2016-08-02 12:05:27 -05:00
2016-06-07 13:41:38 -06:00
2016-06-07 13:41:38 -06:00
2019-11-28 18:28:16 +01:00