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.
-------------------------------------------
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
