search for: c0d0s1

...that I partitioned this disk as EFI disk in Windows (mostly just because). c0d0s0 was the emergency, boot or whatever partition automatically created according to the recommended EFI partitioning scheme. So it added the minimal space of that partition to the pool. The real whole disk partition was c0d0s1. Since there''s no device removal in ZFS yet, I had to replace slice 0 with slice 1 since destroying the pool was out of the question. Two things now: a) ZFS would have added EFI labels anyway. Will ZFS figure things out for itself, or did I lose write cache control because I didn''...

...x:thread_start+8 () Apr 3 16:37:56 columbia unix: [ID 100000 kern.notice] Apr 3 16:37:56 columbia genunix: [ID 672855 kern.notice] syncing file systems... Apr 3 16:37:56 columbia genunix: [ID 904073 kern.notice] done Apr 3 16:37:57 columbia genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c0d0s1, offset 419495936, content: kernel I am running nv_38 and I was wondering if this error was fixed in nv_60 or not. I tried to search the forums for something, but couldn''t find anything. Thanks a lot in advance for your help. Bertrand. This message posted from opensolaris.org

...d51e5dd8 unix:thread_start+8 () Nov 19 09:09:34 fugly unix: [ID 100000 kern.notice] Nov 19 09:09:34 fugly genunix: [ID 672855 kern.notice] syncing file systems... Nov 19 09:09:34 fugly genunix: [ID 904073 kern.notice] done Nov 19 09:09:35 fugly genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c0d0s1, offset 123863040, content: kernel Nov 19 09:09:56 fugly genunix: [ID 409368 kern.notice] ^M100% done: 69052 pages dumped, compression ratio 1.58, Nov 19 09:09:56 fugly genunix: [ID 851671 kern.notice] dump succeeded I''ve got the core if anyone wants it. Thanks, John This message posted...