Date: Mon, 20 Oct 2008 11:00:26 -0700 From: "Artem Belevich" <fbsdlist@src.cx> To: JoaoBR <joao@matik.com.br> Cc: Jeremy Chadwick <koitsu@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: constant zfs data corruption Message-ID: <ed91d4a80810201100m10b2a103yf4f535c5769879b5@mail.gmail.com> In-Reply-To: <200810201518.01678.joao@matik.com.br> References: <200810171530.45570.joao@matik.com.br> <20081020164831.GA8016@icarus.home.lan> <45836B9A-CB6E-4B95-911E-0023230B8F82@mac.com> <200810201518.01678.joao@matik.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
> all right and understood but shouldn't something as fsck should correct the > error? Seems kind of problematic to me mounting zfs in single user mode, > deleting the file and restarting the OS ? According to Sun's documents, removing corrupted file seems to be 'official' way to get rid of the problem http://docs.sun.com/app/docs/doc/819-5461/gbctx?a=view If the damage is within a file data block, then the file can safely be removed, thereby clearing the error from the system. If the files have something important and you want to recover uncorrupted parts, here's what you can try: http://blogs.sun.com/relling/entry/holy_smokes_a_holey_file --Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ed91d4a80810201100m10b2a103yf4f535c5769879b5>