GFS2 Error while cp

[hal]

Ubuntu 8.04 - 2.6.24-19-generic

When copying files from or to the GFS2 volume often the gfs2 starts to look empty.
Reboot required to recover.

log says:

Oct 14 08:34:58 NAS1 kernel: [ 2091.778454] GFS2: fsid=nas:userhomes.0: warning: assertion "gl->gl_state != LM_ST_UNLOCKED" failed
Oct 14 08:34:58 NAS1 kernel: [ 2091.778457] GFS2: fsid=nas:userhomes.0: function = gfs2_glock_drop_th, file = /build/buildd/linux-2.6.24/fs/gfs2/glock.c, line = 935
Oct 14 08:34:58 NAS1 kernel: [ 2091.778463] Pid: 5114, comm: glock_workqueue Not tainted 2.6.24-19-generic #1
Oct 14 08:34:58 NAS1 kernel: [ 2091.778466]
Oct 14 08:34:58 NAS1 kernel: [ 2091.778467] Call Trace:
Oct 14 08:34:58 NAS1 kernel: [ 2091.778475] [do_writepages+0x2b/0x40] do_writepages+0x2b/0x40
Oct 14 08:34:58 NAS1 kernel: [ 2091.778509] [gfs2:gfs2_assert_warn_i+0x98/0xc0] :gfs2:gfs2_assert_warn_i+0x98/0xc0
Oct 14 08:34:58 NAS1 kernel: [ 2091.778530] [gfs2:gfs2_glock_drop_th+0x108/0x1a0] :gfs2:gfs2_glock_drop_th+0x108/0x1a0
Oct 14 08:34:58 NAS1 kernel: [ 2091.778546] [gfs2:xmote_bh+0x20a/0x3c0] :gfs2:xmote_bh+0x20a/0x3c0
Oct 14 08:34:58 NAS1 kernel: [ 2091.778565] [gfs2:run_queue+0x208/0x250] :gfs2:run_queue+0x208/0x250
Oct 14 08:34:58 NAS1 kernel: [ 2091.778582] [gfs2:glock_work_func+0x41/0x70] :gfs2:glock_work_func+0x41/0x70
Oct 14 08:34:58 NAS1 kernel: [ 2091.778598] [gfs2:glock_work_func+0x0/0x70] :gfs2:glock_work_func+0x0/0x70
Oct 14 08:34:58 NAS1 kernel: [ 2091.778604] [run_workqueue+0xcc/0x170] run_workqueue+0xcc/0x170
Oct 14 08:34:58 NAS1 kernel: [ 2091.778608] [worker_thread+0x0/0x110] worker_thread+0x0/0x110
Oct 14 08:34:58 NAS1 kernel: [ 2091.778615] [worker_thread+0x0/0x110] worker_thread+0x0/0x110
Oct 14 08:34:58 NAS1 kernel: [ 2091.778620] [worker_thread+0xa3/0x110] worker_thread+0xa3/0x110
Oct 14 08:34:58 NAS1 kernel: [ 2091.778626] [<ffffffff80253a00>] autoremove_wake_function+0x0/0x30
Oct 14 08:34:58 NAS1 kernel: [ 2091.778632] [worker_thread+0x0/0x110] worker_thread+0x0/0x110
Oct 14 08:34:58 NAS1 kernel: [ 2091.778638] [worker_thread+0x0/0x110] worker_thread+0x0/0x110
Oct 14 08:34:58 NAS1 kernel: [ 2091.778642] [kthread+0x4b/0x80] kthread+0x4b/0x80
Oct 14 08:34:58 NAS1 kernel: [ 2091.778649] [child_rip+0xa/0x12] child_rip+0xa/0x12
Oct 14 08:34:58 NAS1 kernel: [ 2091.778661] [kthread+0x0/0x80] kthread+0x0/0x80
Oct 14 08:34:58 NAS1 kernel: [ 2091.778666] [child_rip+0x0/0x12] child_rip+0x0/0x12
Oct 14 08:34:58 NAS1 kernel: [ 2091.778671]

P.S. Looks like this happens most often when GFS2 is mounted with quota=on and is exported via NFS and is written by root . It seems that if the user writing to the FS is not root there is no problem also if mounted without quota there is no problem too

[kernel-janitor (kernel-janitor)]

Hi hal,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 283854

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]