That's probably because the umount fails.
We'll have a solution for it in the next drop of ocfs2-tools
which will have a service to specifically mount/umount
ocfs2 volumes. That service will kill processes on stop.
Not perfect but should work.
Hartmut Wöhrle wrote:
What did you do at this time?
I realized some problems if a session (bash) is open and you are on the
filesystem (pwd). Then a shutdown of this maschine without closing the
session makes the maschine hang with this errormessage.
CU
Hartmut Woehrle
Am Donnerstag, 10. November 2005 19:08 schrieb Peter Sylvester:
System config:
Dell PE2850 server
(4) 36GB SCSI drives in (onboard) RAID-5
RHEL4-U2
Dell ATI Video Driver update 10/2005
ocfs2-2.6.9-22.ELsmp-1.0.7-1.i686.rpm
ocfs2-tools-1.0.2-1.i386.rpm
ocfs2console-1.0.2-1.i386.rpm
Note that this is a single node cluster, nothing else installed/running
except iozone.
I was running some "iozone" tests on the OCFS2 volume for about a day,
and the system locked up completely.
The following messages were transcribed from the console (nothing
written to /var/log/messages):
usb4-2: device not accepting address 4, error -71
(11,1): o2hb_write_timeout: 164 ERROR: heartbeat write timeout to device
sda6 after 12000 miliseconds
(11,1): o2hb_stop_all_regions: 1724 ERROR: stopping heartbeat on all
active regeons
Kernel Panic - not syncing: ocfs2 is very sorry to be fencing the system
by panicing
Questions:
What does all this mean?
Why is nothing getting written to /var/log/messages?
If this software really ready for prime time (honestly...)?
thanks,
Peter Sylvester
MITRE Corp.
_______________________________________________
Ocfs2-users mailing list
[EMAIL PROTECTED]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[EMAIL PROTECTED]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
