OpenIndiana Update
I have ran up to ONNV b145 on this system, and was able to run “zpool import” scan without issue,but for some reason a single drive in the pool was causing it to crash with OpenIndiana b147. It didn't matter if the drive was on the on-board controller or the added realtek controller. Just the existence of the drive caused the crash, I didn't notice any scsi errors. And I had not recently.
Some background on why I want to move to OpenIndiana a few versions ago, I heard that you could remove slog devices, so I decided it was safe enough to use a zvol from another pool (one made up of a single 1TB drive) as a slog device making the raidz pool much more usable for nfs based vmware ESXi storage, what I didn't relive at the time was that yes you can remove a slog device from an imported pool, but should the slog device die or the underlying zvol get wedged somehow it wasn't possible to import the pool. Of course a weeks after adding the zvol based slog device the pool refused to import after a lightning storm came through one evening and caused power to fail 5 or 6 times in a couple hours.The zvol became wedged, can't snapshot or clone the zvol or use it there may be fixes for this in post b145 builds.
Now as of b146 it is possible to import a pool with missing slog devices. This should allow me to get my 1.5TB pool of mp3's, movies along with all the data files back on line. If you choose to follow my bad example and use a zvol as a slog device, I dont recommend it, the key to importing the pool is.
zpool import -m -f -d /dev/dsk/ -d /dev/zvol/dsk/[slog zvol pool]/ poolname
Dont expect the above command to finish quicky, I started it around 10 hours, ago and it hasn't returned though I still see infrequent disk access on the system running openindiana live dvd. As soon as it returns hopefully successfully I will be backing up important data, and probably recreating the pool without the zvol slog devices.











0 Comments:
Post a Comment
<< Home