Date: Mon, 31 Aug 2015 18:11:35 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: Replacing Drive with SSD Message-ID: <20150831181135.7682a810@gumby.homeunix.com> In-Reply-To: <55E4865B.1000104@sneakertech.com> References: <CEAD84AD-341A-4FB9-A3A1-D0D5A550AFFD@lafn.org> <alpine.BSF.2.20.1508281235390.74312@wonkity.com> <20150829220311.c7608be1.freebsd@edvax.de> <alpine.BSF.2.20.1508300633160.44682@wonkity.com> <55E45973.2050103@sneakertech.com> <alpine.BSF.2.20.1508311000550.42983@wonkity.com> <55E4865B.1000104@sneakertech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 31 Aug 2015 12:52:43 -0400 Quartz wrote: > > > > It provides a pool of blocks that have not and will not be > > written. > > Bbut how does the drive "know" that those blocks are not allocated by > a partition somewhere and are safe to use as spares? It's not like > the drive firmware reads into the partition table or anything. It's analogous to virtual memory. It's the unused physical blocks that form the free pool. The point of leaving the unpartitioned space is that it's a region of a logical address space with no physical blocks attached.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150831181135.7682a810>