Come listen to Sun Learning Services contractor Michael Ernest (SecondLife: Siddhu Jinx) of Inkling Research, Inc. speak about Solaris DTrace: Friday, April 3rd at 9am SLT
Michael's upcoming book The Book on DTrace will be released later this year. Michael has been teaching the Advanced Solaris System Administration, Java Programming and Performance Management classes at Sun for over fifteen years and is the resident authority on Solaris DTrace, a diagnostic tool used in the Solaris Operating System. Michael also co-authored The Complete Java 2 Certification Study Guide with Simon Roberts.
Location: Sun Solaris Campus in Second Life (SLURL) http://slurl.com/secondlif
See you there!
UPDATE: Here is the presentation that took place during the event.
Thank you, Solaris Campus blog! I'm flattered.
I don't know about 'resident authority' though. I've read everything I can find by the Dtrace Three -- Bryan Cantrill, Adam Leventhal, and Mike Shapiro -- and front-line experts like Jim Mauro, Richard McDougall, Jon Haslam, Jarod Jensen and many other contributors. Those are resident authorities in the best sense of both terms.
I have taught Dtrace for several years though and have focused in particular on making Dtrace more accessible to admins and programmers who believe Dtrace is only an elite power tool. I enjoy getting audiences to take a closer look and see in Dtrace the future of their practices. If that sounds like the kind of discussion you'd benefit from, please attend.
Posted by Michael Ernest on March 19, 2009 at 12:14 PM PDT #
Please tell me that Michael will capitalize DTrace correctly in his book.
Posted by Adam Leventhal on March 19, 2009 at 12:14 PM PDT #
Oops. He sure will.
Posted by Michael Ernest on March 19, 2009 at 12:58 PM PDT #
I recently came across your blog and have been reading along. I thought I would leave my first comment. I don't know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.
Alanna
http://www.craigslistsimplified.info
Posted by Alanna on March 21, 2009 at 04:40 AM PDT #
Can someone break this sar info down for me?
My interest is in the device definitions. I was copying from the "root" drive to a multi-pathed SAN LUN when this sar was collected.
Average sd3.t1.m 0 0.0 18995 626227 0.0 0.0
ssd7.t3. 0 0.0 541 35792 0.0 0.0
ssd7.t5. 0 0.0 534 37103 0.0 0.0
ssd7.t8. 0 0.0 534 34953 0.0 0.0
ssd7.t9. 0 0.0 536 34362 0.0 0.0
sd3 75 1.4 898 29612 0.0 1.5
sd3,a 75 1.4 898 29612 0.0 1.5
ssd7 14 4.0 760 50410 0.0 5.3
ssd7,a 14 4.0 760 50410 0.0 5.3
Posted by Lon Krall on March 25, 2009 at 12:01 PM PDT #
Hi Lon,
There's an 8-character limit on device names, so you have some truncated stuff. The ssd driver manages disks over Fibre Channel; those are your SAN disks. The target IDs represent disks, or LUNs presented as disk. Targets 3, 5, 8, 9 appear to be organized into a RAID volume. I could determine more (and infer less) if I knew the OS release you're using (Sol 9 comes to mind, but I don't know why), the SAN model, and what LUN/RAID software you're using.
Posted by Michael Ernest on March 26, 2009 at 02:27 PM PDT #