Sorry for not giving more details in the original, I was not sure how much details to provide...
I have answered each of your questions below, hope this does not cause more confusion: --- Sarah Jelinek <[EMAIL PROTECTED]> wrote: > Solaris Dummy wrote: > > >We have an E450 with 2 disks (c0t0d0 & c2t0d0) and > all the file systems are mirrored using Solaris > Volume Manager with logging turned on. To upgrade > the OS, we detach the c2t0d0 submirrors, perform a > Live Upgrade (LU) and luactivate the new BE. We have > performed the above process multiple times without > issues. After we boot into the new BE there is a > necessity to mount the old BE file systems for > reference purposes. Sometimes when we mount the > regular slices (/dev/dsk/c0t0d0s*) it panics the > system with "UFS panic free: freeing free block" > message. > > > >Here are my questions: > > > >* Are we doing something illegal when we mount the > regular slices (/dev/dsk/c0t0d0s*)? > > > > > No, this is fine. I am assuming you are mounting the > regular slices that > are not currently mounted on the active and running > be? > Yes, I am trying to mount regular slices from the other/old BE when I booted off the new BE, i.e. I am booted off of /dev/dsk/c2t0d0s0 and I try to mount /dev/dsk/c0t0d0s0 onto /mnt. > Let me ask a few questions about this mounting of > regular slices: > 1. Are these the slices that have been used as a > part of the mirror, > were detached for the LU and then never reattached? These slices that I am trying to mount are the original/old slices from the previous/old BE. I have not attached them yet in the new BE. > 2. Or... are you trying to mount the submirror > devices while in use in > the original mirror. > No, I am not trying to mount the submirrors devices while in use. > I am not sure which slices you are referring to > above? Please give me > more details about your hardware/fs/SVM mirror > layout. > > >* Are the file system getting corrupted because of > the metadevice and logging layers? > > > > > > Some questions: > 1. What version of solaris are you running? Solaris 8 2/02 > 2. Are you running logging with UFS or with SDS via > the trans logging? UFS logging > 3. Are you running SVM or SDS 4.2.1 as the volume > manager? SDS 4.2.1 > 4. Why are you detaching the the submirror? > When I am booted into the original BE (c0t0d0s0), I am detaching c2t0d0s0 submirror so that I can perform a live upgrade (LU). Once the LU is complete and after I boot off the new BE (c2t0d0s0), I am trying to mount original BE root slice (c0t0d0s0) and that's when the system panics. > >* If the file system is corrupted, why isn't mount > capturing the corruption? > > > > > The mount is catching it if I read your email > correctly. I am assuming > the mount fails with the freeing free block message > or does this happen > later? > I mean why isn't mount complaining that the file system is corrupt or can't be mounted instead of panicking? I see the "freeing free block" message in the crash. > >* How would I access the old BE file systems (which > are under Solaris Volume Manger control) from my new > BE? > > > > > Mount the device that contains the old BE on some > temporary mount point. > I am doing this: # mount /dev/dsk/c0t0d0s0 /mnt and the system panics. > thanks, > sarah > **** > > >Thanks in advance. > >This message posted from opensolaris.org > >_______________________________________________ > >ufs-discuss mailing list > >[email protected] > > > > > ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs _______________________________________________ ufs-discuss mailing list [email protected]
