Chris's Wiki :: blog/solaris/ZFSForRootGrump Commentshttps://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSForRootGrump?atomcommentsDWiki2011-02-27T07:52:25ZRecent comments in Chris's Wiki :: blog/solaris/ZFSForRootGrump.From 66.92.52.243 on /blog/solaris/ZFSForRootGrumptag:CSpace:blog/solaris/ZFSForRootGrump:124ac41b159928120c378b94c5687a6c5cca56beFrom 66.92.52.243<div class="wikitext"><p>Having recovered a pool with a busted slog last year, import -m and -F work pretty well. Keeping backups of zpool.cache so you can reference them during recovery would definitely be a good idea, though (it's in /etc, so presumably your normal system backups will have it already).</p>
<p>I've been running zfsroot in production since 12/2007, and have yet to loose a pool irrevocably, or even have anything I would term a moderate problem. Since the new metaslab allocator went in, I haven't had near-full performance issues either.</p>
<p>The scare late last year was due to my own stupidity: <a href="http://mirrorshades.net/post/1485951163">http://mirrorshades.net/post/1485951163</a></p>
<p>Shit happens, sure, but so far the shit has been rare and the benefits major.</p>
<p>The real problem with ZFS from a systems perspective has always been Live Upgrade and upgrading zones. But of course, that particular problem has been shot in the face.</p>
</div>2011-02-27T07:52:25ZFrom 173.28.98.13 on /blog/solaris/ZFSForRootGrumptag:CSpace:blog/solaris/ZFSForRootGrump:dc4a29cefd18116132471d805b82fde78ff06342From 173.28.98.13<div class="wikitext"><p>The newer versions of zpool that ship with solaris 10u9 and Solaris 11 Express can import a pool with corrupted metadata by going back to a older version of the uberblock. Some transactions will be lost, but the data will be consistent with the previous point in time.</p>
</div>2011-02-25T23:00:33ZBy trs80 on /blog/solaris/ZFSForRootGrumptag:CSpace:blog/solaris/ZFSForRootGrump:ef849e78e9545d215efdff4953aa303c6dab6c3btrs80<div class="wikitext"><p>If you (can) boot from a previous snapshot or boot environment you should be able to get access to an old version of <code>/etc/zfs/zpool.cache</code>, correct? If nothing else they provide a convenient rescue environment to munge the current boot environment's cachefile.</p>
</div>2011-02-25T16:21:50ZBy Chris Siebenmann on /blog/solaris/ZFSForRootGrumptag:CSpace:blog/solaris/ZFSForRootGrump:93c46f1f33429642f62cdc8f973f974d507fce36Chris Siebenmann<div class="wikitext"><p><a href="https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSShatteringProblem">Oh yes indeed</a>. I expect to lose a pool to
recoverable corruption at some point over the lifetime of ZFS here. I
don't like it, but I'm resigned to it in exchange for the benefits
that ZFS gives us.</p>
</div>2011-02-25T15:40:25ZFrom 216.93.205.25 on /blog/solaris/ZFSForRootGrumptag:CSpace:blog/solaris/ZFSForRootGrump:1e1b36c71a11908b634a155a9bc215ed17c5adc5From 216.93.205.25<div class="wikitext"><p><a href="http://newsgroups.derkeiler.com/Archive/Alt/alt.sysadmin.recovery/2008-05/msg00411.html">A cautionary tale</a><br>
-- <br>
Charles Polisher</p>
</div>2011-02-25T14:56:43Z