> On Jan 23, 2008, at 8:01 AM, UNIX admin wrote: > > There's this great new utility available on Solaris > 10 Update 2, and > Nevada call "zpool".
*Chuckle* I've been using ZFS since it first came out... you could easily label me as one of the early adopters... we have a production enterprise storage server using ZFS that was set up not a week after ZFS officially showed up in S10 U2. > Seriously, run the following two > commands, and > once complete, you can then do whatever you want with > the disk without > seeing additional errors. > > # zpool create delete_me c2t0d0 > # zpool destroy delete_me Let me show you what happened (and what, among other things, started this whole tread - and my rant): [EMAIL PROTECTED]/]> zpool create -f scratch /dev/dsk/c2t0d0 cannot label 'c2t0d0': failed to write EFI label use fdisk(1M) to partition the disk, and provide a specific slice [EMAIL PROTECTED]/]> zpool create -f scratch c2t0d0 cannot label 'c2t0d0': failed to write EFI label use fdisk(1M) to partition the disk, and provide a specific slice [EMAIL PROTECTED]/]> Of course, I offlined and detached c2t0d0s0 from the "space" pool before I attempted this. It appears that even ZFS resp. zpool(1M), when it sees a USB disk, believes that somehow, for whichever bizzarre illogical reason, USB disks should be treated differently from other disks. Personally, I'd love to know the logic behind this decision! Is this another bug I stumbled upon? This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
