06-19-2010
you cant access the system / tape drive when you're in singale user mode. you have to either you nfs mount to remotely restore from your local machine to the remote tape drive connected on another system (eg V440)
9 More Discussions You Might Find Interesting
1. Solaris
Setting up a T5240 with two disks c1t0d0 and c1t1d0.
I am trying to use raidctl but when I issue.
raidctl -l
I get
Controller 1
Disk: 0.0.0
Disk: 0.1.0
So I try
raidctl -c '0.0.0 0.1.0' -r 1 1
and I get "Array in use."
I try (4 Replies)
Discussion started by: photon
4 Replies
2. Solaris
its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file.
getting similar error on... (3 Replies)
Discussion started by: incredible
3 Replies
3. Solaris
I was trying to configure the netmgmt from the serial and set commitpending to true. However, the netmgmt port is not up and blinking.
I tried to connect using my notebook directly to the netmgmt port and am not able to ping as well. Previouly i was doing the firmware upgrade using the webconsole.... (20 Replies)
Discussion started by: incredible
20 Replies
4. Solaris
Hi,
We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions.
RJS (4 Replies)
Discussion started by: rajasekg
4 Replies
5. Solaris
Hi -
I have a T5240 with 7 LDOMS configured. One night, network comm was broken somehow. Nobody was doing anything on the machine at the time. Here is what I saw in messages:
WARNING: nxge3 : nxge_dma_mem_alloc: ddi_dma_mem_alloc kmem alloc failed
WARNING: nxge3 : nxge_alloc_rx_buf_dma:... (2 Replies)
Discussion started by: pyroman
2 Replies
6. Solaris
Hi Gurus
Can any one tell me the process of disabling the multithreading option on T5240 server and my OS is on LDOM, having one physical processor with 8 core & 8 thread per core
Regards (3 Replies)
Discussion started by: amity
3 Replies
7. Solaris
Hi !
I've been given a T5240 with 4 disks and 2 HBA cards (but no array connected). I did a factory reset on SP and NVRAM clean on OBP because the server had been used before.
I boot cdrom in single mode and try to create a hw mirror with disks from c1... but only c2 is seen by raidctl.
... (2 Replies)
Discussion started by: delavega
2 Replies
8. Solaris
I have a T5240 with 2 T2 US 8 core.. Theoretically how many ldoms can I configure? (5 Replies)
Discussion started by: Iftikhar Barrie
5 Replies
9. Solaris
Hi Folks,
Just a quick question - hopefully!
I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 Replies
LEARN ABOUT SUSE
fc_remote_port_delete
FC_REMOTE_PORT_DELET(9) SCSI mid layer FC_REMOTE_PORT_DELET(9)
NAME
fc_remote_port_delete - notifies the fc transport that a remote port is no longer in existence.
SYNOPSIS
void fc_remote_port_delete(struct fc_rport * rport);
ARGUMENTS
rport
The remote port that no longer exists
DESCRIPTION
The LLDD calls this routine to notify the transport that a remote port is no longer part of the topology. Note: Although a port may no
longer be part of the topology, it may persist in the remote ports displayed by the fc_host. We do this under 2 conditions: 1) If the port
was a scsi target, we delay its deletion by "blocking" it. This allows the port to temporarily disappear, then reappear without disrupting
the SCSI device tree attached to it. During the "blocked" period the port will still exist. 2) If the port was a scsi target and disappears
for longer than we expect, we'll delete the port and the tear down the SCSI device tree attached to it. However, we want to semi-persist
the target id assigned to that port if it eventually does exist. The port structure will remain (although with minimal information) so that
the target id bindings remails.
If the remote port is not an FCP Target, it will be fully torn down and deallocated, including the fc_remote_port class device.
If the remote port is an FCP Target, the port will be placed in a temporary blocked state. From the LLDD's perspective, the rport no longer
exists. From the SCSI midlayer's perspective, the SCSI target exists, but all sdevs on it are blocked from further I/O. The following is
then expected.
If the remote port does not return (signaled by a LLDD call to fc_remote_port_add) within the dev_loss_tmo timeout, then the scsi target is
removed - killing all outstanding i/o and removing the scsi devices attached ot it. The port structure will be marked Not Present and be
partially cleared, leaving only enough information to recognize the remote port relative to the scsi target id binding if it later appears.
The port will remain as long as there is a valid binding (e.g. until the user changes the binding type or unloads the scsi host with the
binding).
If the remote port returns within the dev_loss_tmo value (and matches according to the target id binding type), the port structure will be
reused. If it is no longer a SCSI target, the target will be torn down. If it continues to be a SCSI target, then the target will be
unblocked (allowing i/o to be resumed), and a scan will be activated to ensure that all luns are detected.
Called from normal process context only - cannot be called from interrupt.
NOTES
This routine assumes no locks are held on entry.
AUTHORS
James Bottomley <James.Bottomley@hansenpartnership.com>
Author.
Rob Landley <rob@landley.net>
Author.
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 FC_REMOTE_PORT_DELET(9)