Almost sounds like the network is being removed before the filesystem
shuts down. Would this be the case? If so, we should have init
scripts that take care of that.
brassow
On Jan 19, 2006, at 11:07 AM, O'Sullivan, Damian wrote:
If I ever reboot a node on a cluster it panics on the way down:
Process umount (pid: 22814, threadinfo 00000100775fe000, task
000001007fb95030)
Stack: 0000000000000084 ffffffff801f5163 0000000000000058
ffffff00102fe000
00000100276d7cf0 ffffffffa0295b96 0000000000000001
ffffffffa025c8c4
0000000000000001 ffffffffa02533c3
Call Trace:<ffffffff801f5163>{vgacon_cursor+0}
<ffffffffa0295b96>{:lock_dlm:lm_d
lm_unlock+21}
<ffffffffa025c8c4>{:gfs:gfs_lm_unlock+41}
<ffffffffa02533c3>{:gfs:gfs_glo
ck_drop_th+290}
<ffffffffa0251b70>{:gfs:run_queue+314}
<ffffffffa02528ca>{:gfs:gfs_glock_
dq+323}
<ffffffffa0252908>{:gfs:gfs_glock_dq_uninit+9}
<ffffffffa0272ee0>{:gfs:gf
s_make_fs_ro+118}
<ffffffffa026b1a0>{:gfs:gfs_put_super+654}
<ffffffff8017c4b1>{generic_shu
tdown_super+202}
<ffffffffa0268c6d>{:gfs:gfs_kill_sb+42}
<ffffffff801cbe58>{dummy_inode_pe
rmission+0}
<ffffffff8017c3ce>{deactivate_super+95}
<ffffffff80191847>{sys_umount+925
}
<ffffffff80110aed>{error_exit+0}
<ffffffff80110052>{system_call+126}
Code: 0f 0b 4e a1 29 a0 ff ff ff ff 65 01 48 c7 c7 53 a1 29 a0 31
RIP <ffffffffa0295819>{:lock_dlm:do_dlm_unlock+167} RSP
<00000100775ffca8>
<0>Kernel panic - not syncing: Oops
Kernel : 2.6.9-22.0.1.Elsmp
GFS-6.1.2-0
D.
--
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
