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?
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?
2. Or... are you trying to mount the submirror devices while in use in
the original mirror.
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?
2. Are you running logging with UFS or with SDS via the trans logging?
3. Are you running SVM or SDS 4.2.1 as the volume manager?
4. Why are you detaching the the submirror?
* 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?
* 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.
thanks,
sarah
****
Thanks in advance.
This message posted from opensolaris.org
_______________________________________________
ufs-discuss mailing list
[email protected]
_______________________________________________
ufs-discuss mailing list
[email protected]
