> hello > > i have had this problem this week. our zil ssd died (apt slc ssd 16gb). > because we had no spare drive in stock, we ignored it. > > then we decided to update our nexenta 3 alpha to beta, exported the > pool and made a fresh install to have a clean system and tried to > import the pool. we only got a error message about a missing drive. > > we googled about this and it seems there is no way to acces the pool > !!! > (hope this will be fixed in future) > > we had a backup and the data are not so important, but that could be a > real problem. > you have a valid zfs3 pool and you cannot access your data due to > missing zil.
If you have zpool less than version 19 (when ability to remove log device was introduced) and you have a non-mirrored log device that failed, you had better treat the situation as an emergency. Normally you can find your current zpool version by doing "zpool upgrade," but you cannot now if you're in this failure state. Do not attempt "zfs send" or "zfs list" or any other zpool or zfs command. Instead, do "man zpool" and look for "zpool remove." If it says "supports removing log devices" then you had better use it to remove your log device. If it says "only supports removing hotspares or cache" then your zpool is lost permanently. If you are running Solaris, take it as given, you do not have zpool version 19. If you are running Opensolaris, I don't know at which point zpool 19 was introduced. Your only hope is to "zpool remove" the log device. Use tar or cp or something, to try and salvage your data out of there. Your zpool is lost and if it's functional at all right now, it won't stay that way for long. Your system will soon hang, and then you will not be able to import your pool. Ask me how I know. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
