[zfs-discuss] Panic on snv_65

2007-06-11 Thread Borislav Aleksandrov
Panic on snv_6564 when: #mkdir /disk #mkfile 128m /disk/disk1 #mkfile 128m /disk/disk2 #zpool create data mirror /disk/disk1 /disk/disk2 #mkfile 128m /disk/disk1 #mkfile 128m /disk/disk2 #zpool scrub data panic[cpu0]/thread=2a100e33ca0: ZFS: I/O failure (write on unknown off 0: zio 30002925770

Re: [zfs-discuss] Panic on snv_65

2007-06-11 Thread Mario Goebbels
I think in your test, you have to force some IO on the pool for ZFS to recognize that your simulated disk has gone faulty, and that after the first mkfile already. Immediately overwriting both files after pool creation leaves ZFS with the impression that the disks went missing. And even if ZFS

Re: [zfs-discuss] Panic on snv_65

2007-06-11 Thread Brian Hechinger
I think this falls under the bug (of which the number I do not have handy at the moment) where ZFS needs to more gracefully fail in a situation like this. Yes, be probably broke his zpool, but it really shouldn't have paniced the machine. -brian On Mon, Jun 11, 2007 at 03:05:19PM -0100, Mario

Re: [zfs-discuss] Panic on snv_65

2007-06-11 Thread eric kustarz
On Jun 11, 2007, at 12:52 AM, Borislav Aleksandrov wrote: Panic on snv_6564 when: #mkdir /disk #mkfile 128m /disk/disk1 #mkfile 128m /disk/disk2 #zpool create data mirror /disk/disk1 /disk/disk2 #mkfile 128m /disk/disk1 #mkfile 128m /disk/disk2 At this point you have completely overwritten