Date: Sun, 24 Jan 2010 14:04:51 +1100 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Rich <rincebrain@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: Errors on a file on a zpool: How to remove? Message-ID: <20100124030451.GB88876@dereel.lemis.com> In-Reply-To: <5da0588e1001231638i349f8f17t297e970b08825441@mail.gmail.com> References: <ed91d4a81001230011t7aef2da8h3be13d2494c06550@mail.gmail.com> <5da0588e1001230014k1b8a32f8v42046497265429ed@mail.gmail.com> <alpine.BSF.2.00.1001231519110.91898@ibyngvyr> <5da0588e1001231415t403f29ceq6e8dcd16edb4a28@mail.gmail.com> <alpine.BSF.2.00.1001231733570.2160@ibyngvyr> <5da0588e1001231541l246769eao410c5ea6ccca0de4@mail.gmail.com> <A43CB93C-06D6-406D-A8C0-4E10E85661A2@gmail.com> <5da0588e1001231615t37c22575uedaae938be40f530@mail.gmail.com> <4B5B94B8.7070509@modulus.org> <5da0588e1001231638i349f8f17t297e970b08825441@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--DKU6Jbt7q3WqK7+M Content-Type: text/plain; charset=us-ascii Content-Disposition: inline [sequence recovered] On Saturday, 23 January 2010 at 19:38:47 -0500, Rich wrote: > On Sat, Jan 23, 2010 at 7:30 PM, Andrew Snow <andrew@modulus.org> wrote: >> Rich wrote: >>> >>> I claim this is still Bad Behavior, and should be resolvable without >>> doing something like that. >> >> I cannot agree that silent corruption (which would have happened with any >> other filesystem) is preferable to what ZFS is doing here. >> >> You had bad RAM, and no redundancy in a huge RAID0, I think it would be >> reasonable to have to restore from backups or recreate the data and not pin >> blame on ZFS. > > I'm not claiming that restoring data from backups is unreasonable, or > that silent data corruption is better. > > I'm claiming that my inability to delete the corrupted data in order > to restore from backups without nuking unaffected data or remaking the > filesystem is unreasonable. You have a file system with broken metadata. How can ZFS know how to work around this corruption? By continuing things could get worse. I haven't been following this thread, but the way I see it: Reasonable: to be able to mount the file system read-only and recover what data you can from it. Unreasonable: to expect the file system to repair corruption of an unknown type. The only safe path is to create the file system from scratch. This has nothing to do with how you recover the data. Greg -- See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft MUA reports problems, please read http://tinyurl.com/broken-mua --DKU6Jbt7q3WqK7+M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAktbuNMACgkQIubykFB6QiPQMgCeLGly2NzemOpmhGFy/gMZsq7E E/MAn0Xjji6KbsY2btFmlYxFlCoGK0Ad =EMrR -----END PGP SIGNATURE----- --DKU6Jbt7q3WqK7+M--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100124030451.GB88876>