On Wed, May 09, 2018 at 05:53:19PM +0100, Andrew Price wrote:
> You should be able to fix this by using the configure.ac and
> gfs2/libgfs2/meta.c files from master. The diff should be very small. It'll
> need an ./autogen.sh to rebuild the configure script.
> 
> The downside of that approach is that the new fields will be recognised but
> not used in the utils. The next release of gfs2-utils will add that
> functionality.

As I feared, the gfs2 kernel module does not want to mount the
filesystem created with patched gfs2-utils. I guess that I will
need to take the current master branch to get it working again?

[   51.435041] gfs2: GFS2 installed
[   51.435534] gfs2: fsid=debian:test: Trying to join cluster "lock_dlm", 
"debian:test"
[   51.438526] dlm: Using TCP for communications
[   51.438945] dlm: test: joining the lockspace group...
[   51.443191] dlm: test: group event done 0 0
[   51.443555] dlm: test: dlm_recover 1
[   51.443859] dlm: test: add member 2130706433
[   51.444484] dlm: test: dlm_recover_members 1 nodes
[   51.444882] dlm: test: join complete
[   51.445204] dlm: test: generation 1 slots 1 1:2130706433
[   51.445630] dlm: test: dlm_recover_directory
[   51.445975] dlm: test: dlm_recover_directory 0 in 0 new
[   51.446395] dlm: test: dlm_recover_directory 0 out 0 messages
[   51.447376] dlm: test: dlm_recover 1 generation 1 done: 0 ms
[   51.968133] gfs2: fsid=debian:test: first mounter control generation 0
[   51.968882] gfs2: fsid=debian:test: Joined cluster. Now mounting FS...
[   51.969802] gfs2: fsid=debian:test.0: journal 0 mapped with 1 extents
[   51.970365] gfs2: fsid=debian:test.0: jid=0, already locked for use
[   51.970851] gfs2: fsid=debian:test.0: jid=0: Looking at journal...
[   52.025589] gfs2: fsid=debian:test.0: fatal: filesystem consistency error
                 inode = 1 18
                 function = find_good_lh, file = 
/build/linux-hny3SU/linux-4.16.5/fs/gfs2/recovery.c, line = 200
[   52.027113] gfs2: fsid=debian:test.0: about to withdraw this file system
[   52.030045] gfs2: fsid=debian:test.0: telling LM to unmount
[   52.030496] dlm: test: leaving the lockspace group...
[   52.032696] dlm: test: group event done 0 0
[   52.033093] dlm: test: release_lockspace final free
[   52.033595] gfs2: fsid=debian:test.0: withdrawn
[   52.033978] CPU: 0 PID: 109 Comm: kworker/0:2 Not tainted 4.16.0-1-amd64 #1 
Debian 4.16.5-1
[   52.034619] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.11.1-1 04/01/2014
[   52.035270] Workqueue: gfs_recovery gfs2_recover_func [gfs2]
[   52.035710] Call Trace:
[   52.036326]  dump_stack+0x5c/0x85
[   52.037073]  gfs2_lm_withdraw+0x15f/0x170 [gfs2]
[   52.037841]  gfs2_consist_inode_i+0x35/0x40 [gfs2]
[   52.038605]  find_good_lh+0x6d/0x80 [gfs2]
[   52.039307]  gfs2_find_jhead+0x8a/0x170 [gfs2]
[   52.040036]  gfs2_recover_func+0x426/0x910 [gfs2]
[   52.040781]  ? sysfs_slab_add+0x257/0x270
[   52.041494]  ? update_load_avg+0x563/0x6c0
[   52.042182]  ? update_load_avg+0x563/0x6c0
[   52.042857]  ? set_next_entity+0x96/0x1b0
[   52.043570]  ? pick_next_task_fair+0x2fc/0x5f0
[   52.044322]  ? __switch_to+0xa2/0x450
[   52.044988]  ? process_one_work+0x17b/0x360
[   52.045675]  ? gfs2_find_jhead+0x170/0x170 [gfs2]
[   52.046388]  process_one_work+0x17b/0x360
[   52.047068]  worker_thread+0x2e/0x390
[   52.047704]  ? process_one_work+0x360/0x360
[   52.048369]  kthread+0x113/0x130
[   52.048958]  ? kthread_create_worker_on_cpu+0x70/0x70
[   52.049708]  ? kthread_create_worker_on_cpu+0x70/0x70
[   52.050428]  ret_from_fork+0x35/0x40
[   52.051059] gfs2: fsid=debian:test.0: jid=0: Failed
[   52.055033] gfs2: fsid=debian:test.0: error recovering journal 0: -5
[   52.421441] dlm: closing connection to node 2130706433

-- 
Valentin

Reply via email to