Date: Sun, 29 Jul 2012 13:06:35 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: RW <rwmaillists@googlemail.com> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD on SSD Message-ID: <alpine.BSF.2.00.1207291305220.3860@wojtek.tensor.gdynia.pl> In-Reply-To: <20120729011426.0d31fe19@gumby.homeunix.com> References: <CAMxhPyt-gF228nX0DNrdsFVXKVx6YjZVa7obfov5vf%2BdtV71zw@mail.gmail.com> <alpine.BSF.2.00.1207281229260.6801@wojtek.tensor.gdynia.pl> <CAKB6gVgEyvVYaUvLkvE_AU-aViJxHAiLu6drcodLjOOBeNEYLg@mail.gmail.com> <CAMxhPysfghi-0ufy0OU0nonqha5mFeRacPVXM0MBDe6fqxmjUg@mail.gmail.com> <alpine.BSF.2.00.1207282016110.9859@wojtek.tensor.gdynia.pl> <20120729011426.0d31fe19@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> From what I've read the cache is divided into two part. One part holds > blocks that are consistently read during boot-ups. The other part holds how does it know when it is "bootup" and when it ends? >> documented. > > Well, it is intended to be completely transparent. transparency is one, documentation is another. >> but does it clear SSD cache? > > That isn't guaranteed to clear any modern disk since they started using > spare sectors so? >> i don't think so. Someone sophisticated >> enough would perform raw read of cache chips and get cached data, >> which can actually be the most important part > > If you're that paranoid use geli, or don't sell. of course i use geli. and this is not a paranoia.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1207291305220.3860>