On 6-Jun-10, at 7:11 AM, Thomas Maier-Komor wrote:
On 06.06.2010 08:06, devsk wrote:
I had an unclean shutdown because of a hang and suddenly my pool is
degraded (I realized something is wrong when python dumped core a
couple of times).
This is before I ran scrub:
pool: mypool
state: DE
I think both Bob and Thomas have it right. I am using VIrtualbox and just
checked, the host IO is cached on the SATA controller, although I thought I had
it enabled (this is VB-3.2.0).
Let me run this mode for a while and see of this happens again.
--
This message posted from opensolaris.org
__
On Sun, 6 Jun 2010, Roy Sigurd Karlsbakk wrote:
I mean I don't mind if I create or modify a file and it doesn't land
on disk because on unclean shutdown happened but a bunch of unrelated
files getting corrupted, is sort of painful to digest.
ZFS guarantees consistency in a redundant setup, but
On 06.06.2010 08:06, devsk wrote:
> I had an unclean shutdown because of a hang and suddenly my pool is degraded
> (I realized something is wrong when python dumped core a couple of times).
>
> This is before I ran scrub:
>
> pool: mypool
> state: DEGRADED
> status: One or more devices has ex
> Few of questions:
>
> 1. Have the errors really gone away? Can I just clear and be content
> that errors are really gone?
Looks like they're fixed now, yes.
> 2. Why did the errors occur anyway if ZFS guarantees on-disk
> consistency? I wasn't writing anything. Those files were definitely
> not
I had an unclean shutdown because of a hang and suddenly my pool is degraded (I
realized something is wrong when python dumped core a couple of times).
This is before I ran scrub:
pool: mypool
state: DEGRADED
status: One or more devices has experienced an error resulting in data
corru
