Hello Nicholas, Wednesday, January 3, 2007, 5:08:25 PM, you wrote: > I agree this needs to be corrected and am glad to see that a bug was open for it. Do you know what the bugid is for it? I don''t know the bug id however http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg05149.html " Re: [zfs-discuss] ZFS in a SAN environment Matthew Ahrens Wed, 20 Dec 2006 10:39:45 -0800 Jason J. W. Williams wrote: "INFORMATION: If a member of this striped zpool becomes unavailable or develops corruption, Solaris will kernel panic and reboot to protect your data This is a bug, not a feature. We are currently working on fixing it. " -- Best regards, Robert mailto:rmilkowski@task.gda.pl http://milek.blogspot.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Nicholas Senedzuk
2007-Jan-10 16:26 UTC
[zfs-discuss] Solaris crashes when ZFS device disappears
Skipped content of type multipart/alternative-------------- next part -------------- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Willem van Schaik
2007-Jan-10 16:26 UTC
[zfs-discuss] Solaris crashes when ZFS device disappears
Played over Xmas a bit with ZFS on mirrored USB sticks. Which was fun....
When I pulled both sticks without doing any unmount, the filesystem
seemed to be still there, all in cache of course. I even could open a
file in vi, but when I then tried to save the file, I had expected a
failure, but not that the Solaris kernel would crash.
I realize this is not what ZFS was designed for, but I wondered if the
same would happen when a normal disk fails (on a non mirrored config).
Take note, that in this case the ZFS filesystem was not the device with
the OS.
See below the log from /var/log/messages.
Willem
Dec 30 12:58:15 fornax usba: [ID 691482 kern.warning] WARNING:
/pci@0,0/pci1297,a550@2,2/storage@5 (scsa2usb0): Disconnected device was busy,
please reconnect.
Dec 30 12:58:20 fornax usba: [ID 691482 kern.warning] WARNING:
/pci@0,0/pci1297,a550@2,2/storage@6 (scsa2usb1): Disconnected device was busy,
please reconnect.
Dec 30 12:58:28 fornax scsi: [ID 107833 kern.notice] Device is gone
Dec 30 12:58:28 fornax last message repeated 7 times
Dec 30 12:58:28 fornax unix: [ID 836849 kern.notice]
Dec 30 12:58:28 fornax ^Mpanic[cpu0]/thread=fffffe8000c0dc80:
Dec 30 12:58:28 fornax genunix: [ID 809409 kern.notice] ZFS: I/O failure (write
on <unknown> off 0: zio ffffffff861102c0 [L0 ZIL intent log] 1000L/1000P
DVA[0]=<0:2f000:1000> zilog uncompressed LE contiguous birth=10095 fill=0
cksum=6bea7e056f9386b4:edf58a85f12122fd:1b:2): error 5
Dec 30 12:58:28 fornax unix: [ID 100000 kern.notice]
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0da40
zfs:zio_done+140 ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0da60
zfs:zio_next_stage+68 ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0dab0
zfs:zio_wait_for_children+5d ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0dad0
zfs:zio_wait_children_done+20 ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0daf0
zfs:zio_next_stage+68 ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0db40
zfs:zio_vdev_io_assess+129 ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0db60
zfs:zio_next_stage+68 ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0dbb0
zfs:vdev_mirror_io_done+2af ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0dbd0
zfs:zio_vdev_io_done+26 ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0dc60
genunix:taskq_thread+1a7 ()
Dec 30 12:58:28 fornax genunix: [ID 655072 kern.notice] fffffe8000c0dc70
unix:thread_start+8 ()
Dec 30 12:58:28 fornax unix: [ID 100000 kern.notice]
Dec 30 12:58:28 fornax genunix: [ID 672855 kern.notice] syncing file systems...
Dec 30 12:58:28 fornax genunix: [ID 733762 kern.notice] 1
Dec 30 12:58:29 fornax genunix: [ID 904073 kern.notice] done
Dec 30 12:58:30 fornax genunix: [ID 111219 kern.notice] dumping to
/dev/dsk/c0d0s1, offset 202375168, content: kernel
Dec 30 12:58:33 fornax genunix: [ID 409368 kern.notice] ^M100% done: 40584 pages
dumped, compression ratio 3.78,
Dec 30 12:58:33 fornax genunix: [ID 851671 kern.notice] dump succeeded
Dec 30 12:58:57 fornax genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11
Version snv_55 64-bit
Dec 30 12:58:57 fornax genunix: [ID 172907 kern.notice] Copyright 1983-2006 Sun
Microsystems, Inc. All rights reserved.
--
Willem van Schaik Sun Microsystems of Canada Inc.
Solutions Architect 112 Fourth Avenue SW, III #1200
Sun Client Solutions Calgary AB, T2P 0H3
CANADA
mailto:wvs@sun.com +1 (403) 606-9010 (cell)
http://webhome.central/wwwillem/ +1 (403) 262-0515 X57515
...................................................................COM
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Robert Milkowski
2007-Jan-10 16:26 UTC
[zfs-discuss] Solaris crashes when ZFS device disappears
An HTML attachment was scrubbed... URL: http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070103/6877d3e6/attachment-0001.html -------------- next part -------------- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Nicholas Senedzuk
2007-Jan-10 16:26 UTC
[zfs-discuss] Solaris crashes when ZFS device disappears
Skipped content of type multipart/alternative-------------- next part -------------- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss