On Wed, Oct 27, 2010 at 9:31 AM, Harry Putnam <rea...@newsguy.com> wrote: > Marion Hakanson <hakan...@ohsu.edu> writes: > >> As someone else mentioned, most of this stuff will end up in the >> /var/adm/messages file. Except, of course, for the very interesting >> lowest-level boot problems. > > yeah... I got a little carried away there... I had long ago setup a > /var/adm/debug.log that catches everything log message issued. with > > *.debug /var/adm/debug.log > > in /etc/syslog.conf > > Then forgot I had done so... The messages are there alright but now > I'm finding they are not all that helpful... an example at the end. > >> The reason why it's so primitive is that at this point (in Solaris, >> OpenSolaris, Linux, or Windows), you're still pretty much dependent >> on whatever features the BIOS provides you, which limits you just >> to the old-fashioned, low-tech text-only console. There's just not >> enough software running yet to give you a GUI. > > I'm not sure what you mean here.... With the same bios, linux manages > to provide a text console that is vastly more useful... ie, it has gpm > running. I wasn't asking for a gui, I like a text console... but do > like to be able to mouse copy from the buffer. > > About the console messages; they were concerning how to find the > output using fmdump, and using the `Event ID' to do so. > > Now armed with the Event IDs that had scrolled off the screen: > > I still learn nothing very useful, that is, unless by pounding away on > man fmdump and probably a number of other man pages this can be made > sense of. But not at all obvious what any of this might mean: > > fmdump -v -u 4021154c-2d57-c54e-ae82-ea27fc2d19fa > > TIME UUID SUNW-MSG-ID > Oct 14 04:14:02.1292 4021154c-2d57-c54e-ae82-ea27fc2d19fa ZFS-8000-GH > 100% fault.fs.zfs.vdev.checksum > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 > Affects: zfs://pool=z3/vdev=e35825af18775fc2 > FRU: - > Location: -
It looks to me like you got a checksum error in a zpool named z3. > > Oct 25 17:06:24.7775 4021154c-2d57-c54e-ae82-ea27fc2d19fa FMD-8000-4M Repaired > 100% fault.fs.zfs.vdev.checksum Repair Attempted > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 > Affects: zfs://pool=z3/vdev=e35825af18775fc2 > FRU: - > Location: - It was repaired > > Oct 25 17:06:24.8987 4021154c-2d57-c54e-ae82-ea27fc2d19fa FMD-8000-6U Resolved > 100% fault.fs.zfs.vdev.checksum Repair Attempted > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 > Affects: zfs://pool=z3/vdev=e35825af18775fc2 > FRU: - > Location: - And it has been resolved - you don't have to worry about it any more. But, I would run "zpool status z3" to confirm that it says everything is healthy. It may also be advisable to run "zpool scrub z3" to have zfs look for any more problems (hopefully all correctable) before they pile up to a point where they aren't correctable. If you keep having problems, it may point to hardware problems (disk, cable, disk controller, memory, etc.). -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
