Date: Fri, 29 Apr 2016 10:05:11 -0500 (CDT) From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us> To: Andrew Berg <aberg010@my.hennepintech.edu> Cc: freebsd-fs@freebsd.org Subject: Re: How to speed up slow zpool scrub? Message-ID: <alpine.GSO.2.20.1604291000270.26476@freddy.simplesystems.org> In-Reply-To: <57236998.5090908@my.hennepintech.edu> References: <381846248.2672053.1461695277122.JavaMail.yahoo.ref@mail.yahoo.com> <381846248.2672053.1461695277122.JavaMail.yahoo@mail.yahoo.com> <1461736217.1121.17.camel@michaeleichorn.com> <alpine.GSO.2.20.1604290821210.23612@freddy.simplesystems.org> <08d59afe-c835-fa8d-0e52-78afcb1cc030@denninger.net> <57236998.5090908@my.hennepintech.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Apr 2016, Andrew Berg wrote: > > On a side note, ZFS uses lots of RAM for *caching*. Any corruption there > might affect your applications and/or system, but not your on-disk data. It's > also highly unlikely that you will have bad data written, but then never have > any bit flips on reads later. You *will* know something is wrong. ZFS uses RAM for caching the pool and filesystem structures, and metadata. If this data becomes correct, then innocent data may be overwritten with corrupted data because zfs made the wrong decisions. It is true that you are likely to soon know that something is wrong, but by then it may be too late. For proper operation of ZFS one needs: o Reliable RAM o Reliable disk cache sync request Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.20.1604291000270.26476>