Sponsored Content
Full Discussion: Problem with storage
Operating Systems Solaris Problem with storage Post 302311541 by incredible on Wednesday 29th of April 2009 03:30:32 AM
Old 04-29-2009
Check with your Data Centre ppl.. Smilie
Then you might also want to check the event/logs from the servers on the same rack as your storage to see see if its a genuine outage/power strip problem.
If thats not the case, then push in the power cords firmly, monitor your system. If its happening too often for no reason, replace the power supply
 

7 More Discussions You Might Find Interesting

1. Linux

Some problem about usb mass storage device

Dear linuxers, I have a usb mess storage device. My OS is rh as3 update2. Each time I use the command mount -t vfat /dev/sda1 /mnt/usb I got the error "the device is not a valid block device". I found from google that I should install the module sd_mod I use the command insmod sd_mod... (2 Replies)
Discussion started by: niukun
2 Replies

2. Shell Programming and Scripting

Problem with storage of PID's to variables

I have the following problem to be solved: I read a .csv file (tempfile), fetch the values into variables F1 to F5. Variables F1, F2, F3 are parameters used for running a program (blablaprogram). Variable F4 I want to use to store the PID-value in and variable F5 is used for storing the return... (3 Replies)
Discussion started by: zwiebertje11
3 Replies

3. Solaris

Sun storage L7 Problem

Dear Expert , We have L7 , when we power on we see on lcd messages "drive Post E" , According sun Doc SunSolve , there problem picker or Driver , I try move slot to slot successfully, On Lcd panel i can not see load drive (look like any inside tape in drive , but when i am select eject menu,... (0 Replies)
Discussion started by: hadibn
0 Replies

4. Solaris

problem with storage error

Hi gurus I don't understand the below messages as what is going on with my storage Plz kindly suggest what could be the problem Script started on Tue 12 May 2009 09:22:13 AM GMT OMP-root-/salil> uptime 9:22am up 19:44, 2 users, load average: 0.10, 0.08, 0.08 OMP-root-/salil> uname -a... (4 Replies)
Discussion started by: girish.batra
4 Replies

5. AIX

IVM Storage Virtual disk problem

Hi, When I try to create a virtual disk in IVM ( integrated Virtual Machine VIO ) I get this message Problems occurred while processing the data. A summary of all problems for this page are listed below. Additional details for each problem may be located next to the field causing the... (0 Replies)
Discussion started by: filosophizer
0 Replies

6. UNIX for Dummies Questions & Answers

Problem to recognize a storage A5100

People i have solaris 9 in a sparc platform i`m tryng to conect a stora edge a5100.When i do a format i don't see the disk, later i do a touch /reconfigure reboot and nothing cant anybody help me? thank you (4 Replies)
Discussion started by: enkei17
4 Replies

7. Solaris

Perl problem while installing Veritas Storage Foundation

Hi Guys, I am getting some Perl problems during my Veritas Storage Foundation installation on Solaris 10, 64 Bit. The Solaris is running in a Virtual Machine on a MAC: bash-3.00# ./installer Can't load 'perl/lib/5.10.0/i86pc-solaris-thread-multi-64int/auto/threads/threads.so' for module... (0 Replies)
Discussion started by: Korko
0 Replies
power(9E)							Driver Entry Points							 power(9E)

NAME
power - power a device attached to the system SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> int prefixpower(dev_info_t *dip, int component, int level); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If the driver writer does not supply this entry point, the value NULL must be used in the cb_ops(9S) structure instead. PARAMETERS
dip Pointer to the device's dev_info structure. component Component of the driver to be managed. level Desired component power level. DESCRIPTION
The power(9E) function is the device-specific Power Management entry point. This function is called when the system wants the driver to set the power level of component to level. The level argument is the driver-defined power level to which the component needs to be set. Except for power level 0, which is inter- preted by the framework to mean "powered off," the interpretation of level is entirely up to the driver. The component argument is the component of the device to be power-managed. The interpretation of component is entirely up to the driver. When a requested power transition would cause the device to lose state, the driver must save the state of the device in memory. When a requested power transition requires state to be restored, the driver must restore that state. If a requested power transition for one component requires another component to change power state before it can be completed, the driver must call pm_raise_power(9F) to get the other component changed, and the power(9E) entry point must support being re-entered. If the system requests an inappropriate power transition for the device (for example, a request to power down a device which has just become busy), then the power level should not be changed and power should return DDI_FAILURE. RETURN VALUES
The power() function returns: DDI_SUCCESS Successfully set the power to the requested level. DDI_FAILURE Failed to set the power to the requested level. CONTEXT
The power() function is called from user or kernel context only. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), cb_ops(9S) Writing Device Drivers Using Power Management SunOS 5.10 12 Dec 2003 power(9E)
All times are GMT -4. The time now is 07:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy