Hello experts, I heard that there is something called anonymous dtrace that would still be running when I do a reboot. Basically, I have the following problem: The /boot/solaris/bootenv.rc file in my alternate boot environment is getting modified when I reboot the machine after doing luactivate <ABE>. It happens only on init 6, doesn''t happen when I do a simple reboot. The set bootpath property in this file is getting changed after the machine boots up for the first time in the newly created BE resulting in kernel panic (gives error: cannot mount root path /pci at 0,0/pci-ide at 7/ide at 0/cmdk at 0,0:e) The Primary boot env is S10u3 and ABE is S10u6. I want to see at what point of time and which process is writing to the bootenv.rc file. How can I achieve it using dtrace? Thanks in advance. Regards, Nishchaya
Nishchaya, In addition to the official documentation at http://wikis.sun.com/display/DTrace/Anonymous+Tracing you could also take a look at http://www.laurustech.com/Learning%20DTrace_Part5.pdf under the title Anonymous Tracing. Chip> -----Original Message----- > From: dtrace-discuss-bounces at opensolaris.org [mailto:dtrace-discuss- > bounces at opensolaris.org] On Behalf Of Nishchaya Bahuguna > Sent: Wednesday, March 25, 2009 8:53 AM > To: dtrace-discuss at opensolaris.org > Subject: [dtrace-discuss] anonymous dtrace? > > Hello experts, > > I heard that there is something called anonymous dtrace that would > still > be running when I do a reboot. > > Basically, I have the following problem: > > The /boot/solaris/bootenv.rc file in my alternate boot environment is > getting modified when I reboot the machine after doing luactivate > <ABE>. > It happens only on init 6, doesn''t happen when I do a simple reboot. > The set bootpath property in this file is getting changed after the > machine boots up for the first time in the newly created BE resulting > in > kernel panic (gives error: cannot mount root path > /pci at 0,0/pci-ide at 7/ide at 0/cmdk at 0,0:e) > > The Primary boot env is S10u3 and ABE is S10u6. > > I want to see at what point of time and which process is writing tothe> bootenv.rc file. How can I achieve it using dtrace? > > Thanks in advance. > > Regards, > Nishchaya > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org
This doesn''t address your Dtrace question, but may set you off on the right path :-)> > The /boot/solaris/bootenv.rc file in my alternate boot environment is > getting modified when I reboot the machine after doing luactivate <ABE>. > It happens only on init 6, doesn''t happen when I do a simple reboot.That is the correct behavior. When you luactivate a boot environment, a K0 service script (/etc/init.d/rc0.d/K65lu) is run. That''s why init 6 or init 0 catches it, but reboot doesn''t (reboot doesn''t run the K0 services on shutdown). Weaving through all that it does (lu calls lu_init_d and it it finally reaches a point where it calls /etc/lu/DelayUpdate/activate.sh. I believe this is where you quest will end :-) Somewhere around here ...... /bin/cp -p "${scr_bootEnv}" "/tmp/.luactivate.scr.1.2182" /bin/egrep -v "^[ ]*setprop[ ]+bootpath[ ]+" "/tmp/.luactivate.sc r.1.2182" > "$scr_bootEnv" /bin/echo "setprop bootpath ${scr_rootPhys}" >> "$scr_bootEnv" fi ${scr_ABEmntpt}/boot/solaris/bin/create_ramdisk -R "$scr_ABEmntpt" # Unmount ABE /usr/lib/lu/luumount -f -i /etc/lu/ICF.12 This should be where your bootpath property is being changed. And it has to be on the way down and in the boot-archive because it is used very early in the boot process.> The set bootpath property in this file is getting changed after the > machine boots up for the first time in the newly created BE resulting > in kernel panic (gives error: cannot mount root path > /pci at 0,0/pci-ide at 7/ide at 0/cmdk at 0,0:e)Is this the wrong device path for the new BE ? Bob
Thanks Chip. I would try out the things listed there and get back in case of queries. Regards, Nishchaya Chip Bennett wrote:> Nishchaya, > > In addition to the official documentation at > http://wikis.sun.com/display/DTrace/Anonymous+Tracing you could also > take a look at http://www.laurustech.com/Learning%20DTrace_Part5.pdf > under the title Anonymous Tracing. > > Chip > > >> -----Original Message----- >> From: dtrace-discuss-bounces at opensolaris.org [mailto:dtrace-discuss- >> bounces at opensolaris.org] On Behalf Of Nishchaya Bahuguna >> Sent: Wednesday, March 25, 2009 8:53 AM >> To: dtrace-discuss at opensolaris.org >> Subject: [dtrace-discuss] anonymous dtrace? >> >> Hello experts, >> >> I heard that there is something called anonymous dtrace that would >> still >> be running when I do a reboot. >> >> Basically, I have the following problem: >> >> The /boot/solaris/bootenv.rc file in my alternate boot environment is >> getting modified when I reboot the machine after doing luactivate >> <ABE>. >> It happens only on init 6, doesn''t happen when I do a simple reboot. >> The set bootpath property in this file is getting changed after the >> machine boots up for the first time in the newly created BE resulting >> in >> kernel panic (gives error: cannot mount root path >> /pci at 0,0/pci-ide at 7/ide at 0/cmdk at 0,0:e) >> >> The Primary boot env is S10u3 and ABE is S10u6. >> >> I want to see at what point of time and which process is writing to >> > the > >> bootenv.rc file. How can I achieve it using dtrace? >> >> Thanks in advance. >> >> Regards, >> Nishchaya >> _______________________________________________ >> dtrace-discuss mailing list >> dtrace-discuss at opensolaris.org >> > > >