|
|
Sponsored Content
Operating Systems
Solaris
Missing ASM Disks in Solaris 11.3 LDOM
Post 303025041 by Peasant on Tuesday 23rd of October 2018 10:13:29 AM
10-23-2018
Moderator
Use options slice if you are using slices, as mentioned !
Or use entire device (s2) without options=slice, then partition s0 inside LDOM (or outside) and give it to ASM.
Never give s2 to anything except zpools on VTOC labels.
ZFS when s2 (full scsi lun) or without slice, will repartition disk(s) properly and create zpool (EFI)
When using s2 or no slice at all, ZFS will be endianess aware, you will be able to import the zpool on both solaris architectures (SPARC or x86).
Also, clusters that do SCSI reservation and fencing (like Solaris cluster) will require s2 inside LDOM, or else it will not work.
As for recovering, well, i have no good news about that.
Perhaps some hackery could be done if you had original intact disks without creating zpools out of ASM disk(s)
Why did you do that ... it's like having bad UFS and creating ZFS out of it to recover, it just doesn't make sense
Hackery in a way that you could (from primary domain) :
Present a bit bigger lun, label them, create slice 0 matching the size of entire old lun exactly
Using dd copy entire s2 disk (broken) to s0 slice (new presented and labeled above)
At the end, you would have a labeled disk with s0 slice containing ASM label.
See if ASM now recognizes those luns as proper ones present to LDOM with options=slice
I haven't tried this, get back with results
In my opinion, it is just easier and less prone to error to create from scratch and restore backup and continue with standby DB.
I presume you are replicating with database tools, not storage backend, since if you used storage, you would get properly labeled disks on DR site.
Regards
Peasant.
Or use entire device (s2) without options=slice, then partition s0 inside LDOM (or outside) and give it to ASM.
Never give s2 to anything except zpools on VTOC labels.
ZFS when s2 (full scsi lun) or without slice, will repartition disk(s) properly and create zpool (EFI)
When using s2 or no slice at all, ZFS will be endianess aware, you will be able to import the zpool on both solaris architectures (SPARC or x86).
Also, clusters that do SCSI reservation and fencing (like Solaris cluster) will require s2 inside LDOM, or else it will not work.
As for recovering, well, i have no good news about that.
Perhaps some hackery could be done if you had original intact disks without creating zpools out of ASM disk(s)
Why did you do that ... it's like having bad UFS and creating ZFS out of it to recover, it just doesn't make sense
Hackery in a way that you could (from primary domain) :
Present a bit bigger lun, label them, create slice 0 matching the size of entire old lun exactly
Using dd copy entire s2 disk (broken) to s0 slice (new presented and labeled above)
At the end, you would have a labeled disk with s0 slice containing ASM label.
See if ASM now recognizes those luns as proper ones present to LDOM with options=slice
I haven't tried this, get back with results
In my opinion, it is just easier and less prone to error to create from scratch and restore backup and continue with standby DB.
I presume you are replicating with database tools, not storage backend, since if you used storage, you would get properly labeled disks on DR site.
Regards
Peasant.
This User Gave Thanks to Peasant For This Post:
|
|
9 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have issues installing Solaris into a LDom using a Solaris10u5/08 DVD. I have been troubleshooting for the past 2 days and I still cannot get it up.
Here is the logs:
root@eld-app2# ldm add-vdsdev /cdrom/sol_10_508_sparc/s0 cdrom0@primary-vds0
root@eld-app2# ldm add-vdisk cdrom0... (4 Replies)
Discussion started by: bolasutra
4 Replies
2. Solaris
Hi, Here is the issue: There are 4 disks on this Sun x4150 system under Solaris 10, but only 1 disk can be seen by the OS. I've tried commands disks and devfsadm but not working. It's an important production server, so 'reboot -r' is not a choice.
# format < /dev/null
Searching for... (6 Replies)
Discussion started by: aixlover
6 Replies
3. Solaris
Hey everyone. First, let me start by saying I'm primarily focused on linux boxes, and just happened to get pulled into building two T5220's. I'm not super educated on sun boxes.
Both T5220's have 8 146GB 15k SAS drives. Inside the service processor, I can run SHOW /SYS/HDD{0-7} and they all come... (2 Replies)
Discussion started by: msarro
2 Replies
4. Solaris
Apologies if this is the wrong forum..
I have some LDOMs running on a Sparc server. I copied the disk0 file from one chassis over to another, stopped the ldom on the source system and started it on the 2nd one. All fine. Shut it down and flipped back. We then did a fair bit of work on the... (4 Replies)
Discussion started by: tommyq
4 Replies
5. Solaris
Help Please!
I picked up a V440 and it has 4 disks. I installed Solaris fine to disk 3, but I cannot see the other disks in Solaris.
I have run probe-scsi-all from OBP and I see the other disks and they have names in devalias AFAIK. It's just in Solaris they do not appear. I have run... (6 Replies)
Discussion started by: greg1975
6 Replies
6. Solaris
I have an Oracle VM set up with 1 virtual disk. I am trying to add 2 new disks to it. I was able to successfully add 1 (it appears when I run "format" in the VM) but when I add the second and third disks they do not appear in my VM.
Here are the commands I ran:
ldm add-vdsdev... (3 Replies)
Discussion started by: unblockable
3 Replies
7. Solaris
Hi,
Our existing environment is having primary domain and 3 guest domains are running over it. See the attached image.
Now we want to add a new primary virtual switch and move LDOM3 to be connected with new primary switch.
So, I am not sure how to achieve this because. If I remove the... (7 Replies)
Discussion started by: praveensharma21
7 Replies
8. Solaris
Hi Folks,
I've just built a Solaris 11.3 server with a number of LDOM's, all good and well and not any serious issues so far.
On our older Solaris 10 systems we ran Oracle 11g using ASM disks, these disks were the raw device meta disks and came in very nicely as "/dev/md/rdsk/dnn" all worked... (4 Replies)
Discussion started by: gull04
4 Replies
9. Solaris
I have a Sun T4-1 running Solaris 11.4 with a static IP 192.168.0.183. On this machine is a Solaris 10 LDOM with a static IP of 192.168.0.78. The other day I had to stop the LDOM to do a memory reconfigure. When I rebooted it I got an error that the IP 192.168.0.78 was already in use and so... (4 Replies)
Discussion started by: Michele31416
4 Replies
LEARN ABOUT V7
cmdk
cmdk(7D) Devices cmdk(7D) NAME
cmdk - common disk driver SYNOPSIS
cmdk@target, lun : [ partition | slice ] DESCRIPTION
The cmdk device driver is a common interface to various disk devices. The driver supports magnetic fixed disks and magnetic removable disks. The block-files access the disk using the system's normal buffering mechanism and are read and written without regard to physical disk records. There is also a "raw" interface that provides for direct transmission between the disk and the user's read or write buffer. A sin- gle read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are transmit- ted. The names of the block files are found in /dev/dsk; the names of the raw files are found in /dev/rdsk. I/O requests to the magnetic disk must have an offset and transfer length that is a multiple of 512 bytes or the driver returns an EINVAL error. Slice 0 is normally used for the root file system on a disk, slice 1 as a paging area (for example, swap), and slice 2 for backing up the entire fdisk partition for Solaris software. Other slices may be used for usr file systems or system reserved area. Fdisk partition 0 is to access the entire disk and is generally used by the fdisk(1M) program. FILES
/dev/dsk/cndn[s|p]n block device (IDE) /dev/rdsk/cndn[s|p]n raw device (IDE) where: cn controller n dn lun n (0-7) sn UNIX system slice n (0-15) pn fdisk partition(0) /kernel/drv/cmdk 32-bit kernel module. /kernel/drv/amd64/cmdk 64-bit kernel module. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ SEE ALSO
fdisk(1M), mount(1M), lseek(2), read(2), write(2), readdir(3C), scsi(4), vfstab(4), attributes(5), dkio(7I) SunOS 5.10 9 Oct 2004 cmdk(7D)