El Dec 20, 2008, a las 12:56 PM, Richard McClellan escribió: On Dec 20, 2008, at 08:35 , Christian Kendi wrote: -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Noel,
this was my laptop HD. As this occurs i was writing in Word, therefore
no sleep or remove.
Don't laptops spin down/sleep hard drives if they're inactive? If you stop for a long moment and think while you're writing, it may be long enough (especially if on battery) for the OS to do something to the drive that ZFS doesn't like.
I'm pretty sure it didn't spin down as i was doing intensive drive work. I was just switching to the Word app while compiling in background. I wasnt on battery either. Anyways, just to let you know what i've done. The hardware failiure is possible, but will this happen every time on a non-disasterous
hardware failure ? It was nothing dramatic, as the SMART of the HD is fine this time.
What would happen if i get continous read/write errors due to damaged sectors.
How will ZFS react on this?
If ZFS encounters read errors (comparing checksums from different copies of the same block when reading or doing a scrub) it will flag the drive, but it won't take it offline. But... your laptop probably only has the one drive, so unless you set the ZFS copies property > 1 you won't know there's a problem.
thought so. I was just curious in regards to this panic(), what would happen once there are faulty sectors and the read/write may get async. As you said this could have happend because of a spin down/sleep. Once you have bad sectors the HD automatically stop's and restarts its reading/writing activity i.e. try to recover. Would the system continue to function or would it panic? Are there any tests for this bahaviour? Rich
Greets,
Chris.
>
>
> looks like you've either ripped out a drive prematurely, your drive
> went to sleep, or your drive had a hardware failure. At any rate, ZFS
> can't find it to write to it so panic ensues since they were
> ansynchronous writes we've already returned success on and this would
> make disk state inconsistent.
>
> In Snow Leopard we are thinking of changing this so that we will
> actually freeze the pipleline if this occurs and be alerted you've
> lost data.
>
> Noel
On Dec 19, 2008, at 2:28 PM, Christian Kendi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> im just off to report a kernel panic. The website wont send me an
> activation mail, so i just do it here.
>
> Thu Dec 18 15:28:26 2008
> panic(cpu 0 caller 0x00C08D21): "ZFS: I/O failure (write on
> <unknown> off 0: zio 0x4a2eab0 [L0 ZFS plain file] 1800L/1800P
> DVA[0]=<0:144b278800:1800> fletcher2 uncompressed LE contiguous
> birth=26685 fill=1
> cksum=758849a10b2fd5b6:4bfc8c90062499f1:c0fc06747bfaa98b:
> 1cf76936dedc736d): error " "5"@/Volumes/pixie_dust/home/ndellofano/
> zfs-work/zfs-119/zfs_kext/zfs/zio.c:918
> Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
> 0x38893e38 : 0x12b4f3 (0x45b13c 0x38893e6c 0x1335e4 0x0)
> 0x38893e88 : 0xc08d21 (0xc786b0 0xc786a4 0xc74400 0xca5670)
> 0x38893f08 : 0xc053fb (0x4a2eab0 0x16f5 0x38893f28 0xc4c18a)
> 0x38893f48 : 0xc644a6 (0x4a2eab0 0x47f8800 0x271356 0xc8d5f4)
> 0x38893fc8 : 0x1a017c (0x481c500 0x0 0x1a30b5 0xd2036b0)
> Backtrace terminated-invalid frame pointer 0
> Kernel loadable modules in backtrace (with dependencies):
> com.apple.filesystems.zfs(8.0)@0xbf1000->0xcbcfff
>
> BSD process name corresponding to current thread: kernel_task
>
> Mac OS version:
> 9G55
>
> Kernel version:
> Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008;
> root:xnu-1228.9.59~1/RELEASE_I386
> System model name: MacBook1,1 (Mac-F4208CC8)
>
> Regards,
> Chris.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
>
> iD8DBQFJTB/1p+9ff145KVIRAkJnAJ9DDhnUj9s7K0HBz28G/lkU9CkhEQCfQCfP
> UbNbwThBjfpx4N389JqfcD4=
> =/qFD
> -----END PGP SIGNATURE-----
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/zfs-discuss
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFJTR7Dp+9ff145KVIRApysAJ9I9U1oKnpWR6wh4EOFeu1tBWt74wCdH5rL
4sE/J26J/tK1m8BacbA7czg=
=lMRB
-----END PGP SIGNATURE-----
_______________________________________________
zfs-discuss mailing list
address@hidden
http://lists.macosforge.org/mailman/listinfo.cgi/zfs-discuss
|
PGP.sig