Date: Mon, 08 Nov 2010 22:02:47 +0100 From: "Svein Skogen (Listmail account)" <svein-listmail@stillbilde.net> To: freebsd-questions@freebsd.org Subject: Re: ZFS License and Future Message-ID: <4CD86577.4070107@stillbilde.net> In-Reply-To: <AANLkTikcCFr4GttjNrq9Kxxz1pyZbPc82BsJ6a3siw5t@mail.gmail.com> References: <AANLkTi=dKatHYLFhC35VTT4fCAKgYLKEri2yVCPtSv7g@mail.gmail.com> <AANLkTinxLcrRoB6b2AcTrxHLqRCkyoWUhU=EmuvzEZQ8@mail.gmail.com> <20101106203016.GB13095@guilt.hydra> <20101106213836.GA77198@slackbox.erewhon.net> <AANLkTi=7MhvRTLP1NzGaHQFsV=FU8QDn5K73EmLPZH2k@mail.gmail.com> <4CD8194D.7080208@qeng-ho.org> <4CD82081.50309@stillbilde.net> <20101108183821.GA48373@slackbox.erewhon.net> <AANLkTikcCFr4GttjNrq9Kxxz1pyZbPc82BsJ6a3siw5t@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8AA1DD145AB650E7A0E7E9D0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 08.11.2010 21:44, C. P. Ghost wrote: > On Mon, Nov 8, 2010 at 7:38 PM, Roland Smith <rsmith@xs4all.nl> wrote: >> On Mon, Nov 08, 2010 at 05:08:33PM +0100, Svein Skogen (Listmail accou= nt) wrote: >>> But it's still not capable of true forward-error-correction. If we ar= e >>> to embark upon creating a new solution, using something that is cheap= >>> for "normal cases" but can still be used (albeit more expensively) fo= r >>> error recovery would (imho) be better. Even if that means we get less= >>> net storage out of the gross pool (it could perhaps be configurable?)= >> >> I'm not sure what you mean by "true forward-error-correction". But if = you want >> to make _really sure_ that a spinning disk hasn't mangled the data you= should: >=20 > Maybe something like Reed-Solomon ECC in different blocks. > Should a data block go bad, it could be rebuilt on-the-fly from > those ECC blocks: >=20 > http://en.wikipedia.org/wiki/Reed%E2%80%93Solomon_error_correction > http://www.eccpage.com/ Something along those lines was what I had in mind. ;) //Svein --=20 --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg =D8stli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE --------+-------------------+------------------------------- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ------------------------------------------------------------ Picture Gallery: https://gallery.stillbilde.net/v/svein/ ------------------------------------------------------------ --------------enig8AA1DD145AB650E7A0E7E9D0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzYZXsACgkQODUnwSLUlKS/WwCfW+AuoMz6hKjpxx2FXwhdbc89 MjQAn3zrR3RamXLXnL5vp28BdhiRnsni =YDRE -----END PGP SIGNATURE----- --------------enig8AA1DD145AB650E7A0E7E9D0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CD86577.4070107>