Date: Mon, 08 Nov 2010 21:01:58 +0100 From: "Svein Skogen (Listmail account)" <svein-listmail@stillbilde.net> To: Arthur Chance <freebsd@qeng-ho.org> Cc: freebsd-questions@freebsd.org Subject: Re: ZFS License and Future Message-ID: <4CD85736.1000207@stillbilde.net> In-Reply-To: <4CD837C9.6090800@qeng-ho.org> 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> <4CD837C9.6090800@qeng-ho.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4DAEEF70CA1A44E265BC4861
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 08.11.2010 18:47, Arthur Chance wrote:
*snip*
>=20
> Presuming you're talking about ZFS, the hash isn't intended to correct
> hardware errors, it's only there to detect them. Correction comes from
> mirroring or the use of RAIDZ{1,2,3}. (I have personal experience of ho=
w
> well that works, as I had a disk in a RAIDZ array go bad suddenly, and =
I
> didn't lose any data.) Any new solution would almost certainly mimic
> ZFS's approach of arranging the data as a Merkel tree, and using
> multiple copies or N out of M shares for correction. I'm not sure GEOM'=
s
> block orientation fits well with Merkel trees though, although I'd be
> happy to be corrected by a GEOM expert.
No, I'm talking about knowing that a file has been corrupted is a little
better than not knowing it has been corrupted. But it still won't help
bring back the file.
And I'm ... all too familiar with redundancy strategies (and backups).
Including their shortcomings. Speaking of which: Has there been any
progress on properly backing up ZFS on FreeBSD yet? (including the metada=
ta)
//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/
------------------------------------------------------------
--------------enig4DAEEF70CA1A44E265BC4861
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/
iEYEARECAAYFAkzYVzoACgkQODUnwSLUlKTacgCfXpsbvPBqXlaqp/XwCgAA+CpF
0aoAoJuwyLyehHLEylZ1eycv85Y9G2US
=Z59d
-----END PGP SIGNATURE-----
--------------enig4DAEEF70CA1A44E265BC4861--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CD85736.1000207>