(Sorry, hit send too early) I did, I pulled out all of my old books on Solaris, then googled, then illumos docs and even the oracle docs. As far as I can tell, Solaris fully support GPT partitions, and therefore without the old "8 slices on a disk, s2 is the whole disk for backup, etc.". That is great. But the OS commands like zpool all work off of the old c0t0d0s* devices, so how do you map those to the GPT partitions?
As for the coherent threads... I want to, quite; I know it is annoying. It is the damn listbox listserve software. I am set for "digest" on the list, and bloody listbox does not support the very basic and sane, "if you are on this thread, automatically cc you.". So I am stuck checking the Web UI, hitting refresh, and then copying/pasting into an email thread. Feh. On Wed, Dec 9, 2015 at 12:21 AM, Avi Deitcher <[email protected]> wrote: > Hey Ian, > > I did, I pulled out all of my old books on Solaris, then googled, then > illumos docs and even the oracle docs. > > But I do need some way of knowing how to work > > On Wed, Dec 9, 2015 at 12:20 AM, Ian Collins <[email protected]> wrote: > >> Avi Deitcher wrote: >> >>> I have a gpt partitioned disk. ls /dev/dsk (and /dev/rdsk) gives: >>> >>> c0t0d0 >>> c0t0d0p0 >>> c0t0d0p1 >>> c0t0d0p2 >>> c0t0d0p3 >>> c0t0d0p4 >>> c0t0d0s0 >>> . >>> (skips s7) >>> . >>> c0t0d0s15 >>> >>> How do these map to the actual partitions? >>> >>> They don't, at least not the sxx slices which are slices withing a >> partition. >> >> <snip> >> >>> >>> 1- How do these map to the actual partitions? >>> >> >> I suggest yo google for Solaris disk partitioning or such like and read >> up on how Solaris derived OSs manage their disks. >> >> 2- The actual disk has partitions 0-7,9-17 (skipping the 9th from >>> beginning), but /dev/dsk and /devices/ skip h and s7, or 8th from beginning >>> (unless it ignores the 0th partition?) >>> 3- What happens if I have 25 or 30 partitions, or more than the 20 >>> listed here. EFI/GPT support it, format -e supports it, what would the >>> /dev/dsk devices be? >>> >> >> On a typical SmartOS deployment, you will be using whole drives. As >> above, I suggest to look up more generic Solaris disk management. >> >> >>> (please reply-all so I get the message, doesn't get lost in digest) >>> >> >> And please try and maintain coherent threads in your replies! >> >> -- >> Ian. >> >> > > > -- > Avi Deitcher > [email protected] > Follow me http://twitter.com/avideitcher > Read me http://blog.atomicinc.com > -- Avi Deitcher [email protected] Follow me http://twitter.com/avideitcher Read me http://blog.atomicinc.com ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
