Correct, if you upgraded this pool, you would not be able to import
it back on your existing Solaris 10 system.
My advice would be to wait.
Cindy
On 02/25/10 13:05, Ray Van Dolson wrote:
On Thu, Feb 25, 2010 at 11:55:35AM -0800, Cindy Swearingen wrote:
Ray,
Log removal integrated into build
+--
| On 2010-02-25 12:05:03, Ray Van Dolson wrote:
|
| Thanks Cindy. I need to stay on Solaris 10 for the time being, so I'm
| guessing I'd have to Live boot into an OpenSolaris build, fix my pool
| then hope it re-impor
On Thu, Feb 25, 2010 at 11:55:35AM -0800, Cindy Swearingen wrote:
> Ray,
>
> Log removal integrated into build 125, so yes, if you upgraded to at
> least OpenSolaris build 125 you could fix this problem. See the syntax
> below on my b133 system.
>
> In this particular case, importing the pool fro
Ray,
Log removal integrated into build 125, so yes, if you upgraded to at
least OpenSolaris build 125 you could fix this problem. See the syntax
below on my b133 system.
In this particular case, importing the pool from b125 or later media
and attempting to remove the log device could not fix thi
Well, it doesn't seem like this is possible -- I was hoping there was
some "hacky" way to do it via zdb or something.
Sun support pointed me to a document[1] that leads me to believe this
might have worked on OpenSolaris. Anyone out there in Sun-land care to
comment?
To recap, I accidentally cre
Had a two-device SSD (mirrored) slog/zil and needed to pull each disk
to read some numbers off of them. Unfortunately, when I placed the
devices back in the system, I used "zpool add" and created a separate
log device instead of reattaching the device to the existing log device
which would have re
