melbogia wrote:
There is no "panic" or "syncing filesystems" in /var/adm/messages. Here is what I see 
after I execute the command "mkfile 100g /datapool/testfile"

I was on the machine at 1600 hours yesterday and the next entry after that at 
8:43 AM is system startup information, it seems it can't even write anything to 
/var/adm/messages before it reboots?

Also this may be relevant, the datapool pool doesn't exist after it comes up from crash. 
I have to do a "zpool import -f datapool" to import it.

This may be multiple issues. The fact a reboot happens with no trace in /var/adm/messages is somewhat worrying to me. However, we need to frame the issue. Things like:

When you were using the system on the 10th, how were you connected to it? Were you logged in remotely (via ssh/telnet/etc...)?
   Where you on the console? (graphics console, or text mode)?
   What did you see on the screen around 16:19 ?


Can you check any alternate boot environments, and make sure you are running from the BE you expect to be running from? e.g. did you have a pending beadm activate, and the reboot simply booted into the new environment?

Also, are there any known "hardware reset" issues for your platform? There have been bugs occasionally in the past where a driver will cause a system-wide reset without going through the panic mechanism. I can't recall any, but do remember one or two cropping up occasionally.


Dec 11 08:43:36 dirt zfs: [ID 427000 kern.warning] WARNING: pool 'datapool' 
could not be loaded as it was last accessed by another system (host: dirt 
hostid: 0x409a4c). See: http://www.sun.com/msg/ZFS-8000-EY

Whilst I can't comment on this line myself, it does (IMO) explain why you had to force import the pool after the reboot. Assuming there is only one host with name "dirt", then this would seem to be a bug.

Regards,
Brian



--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG

_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to