Sponsored Content
Full Discussion: Rescan for scsi
Operating Systems Linux Red Hat Rescan for scsi Post 302843298 by kilobyter on Monday 12th of August 2013 05:18:52 PM
Old 08-12-2013
Rescan for scsi

Hi All,

is there a way of rescanning for newly attached SCSI without rebooting the server?

any help greatly appreciated

thanks in advance

Kb
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Scsi

How can you get a scsi card to initalize or decome available at boot up on AIX 4.3 (1 Reply)
Discussion started by: truma1
1 Replies

2. UNIX for Advanced & Expert Users

Scsi

I would like to install a AIT drive to the scsi connector on our solaris box. I am very new to the unix world and would be greatful if someone could help or lead me in the right direction. Thanks (4 Replies)
Discussion started by: vpyle
4 Replies

3. Solaris

Which SCSI Adapter?

Hi. I need to find a simple SCSI adapter card for a Sun Ultra 5 workstation. I don't need the type w/ ethernet attached (e.g. X1032) as I already have ethernet onboard & they are more spendy. I know Adaptec is out, but what unit would work? I am attaching an external SCSI tape unit to this... (4 Replies)
Discussion started by: Plain Person
4 Replies

4. Solaris

Scsi cables - which ones?

Is there any specific scsi cables that you need to get when connecting a tape drive or external storage or does one type of cable fit all? ie. I can buy the following: HD68 to HD68 with Ferrites supports S-E Ultra/Wide transfer rates. But will this work for tape drives and storage? I... (1 Reply)
Discussion started by: frustrated1
1 Replies

5. AIX

how to use a scsi disk??

hi, i removed a FC disk (it has a single VG on it) from a AIX 6.1 server and exported it to another AIX server. after doing cfgmgr -v .. the disk showed up in the second AIX 6.1 server. Now how can i see the data which is on the disk from the second AIX server. (5 Replies)
Discussion started by: navadeep
5 Replies

6. Programming

SCSI interfacing by C

how can I make interfacing with the SCSI controller on linux system using C language to send or recieve data via this SCSI port like I made with serial port and socket ???:confused: how can I deal with this port ??:rolleyes: how can I get its address or its device name ???:eek: thanks for help. (2 Replies)
Discussion started by: Ahmed waheed
2 Replies

7. Linux

Rescan LUNs on Linux VM

Hi, I have presented a new 70GB LUN to my RedHat Linux VM server. How do I rescan for the new LUN? Thanks, Sparcman:confused: (2 Replies)
Discussion started by: sparcman
2 Replies

8. BSD

How to rescan scsi bus without reboot on OpenBSD

Hello, My question as title, I don't know the exact command, anyone could tell me about it? Kevin (0 Replies)
Discussion started by: guixingyi
0 Replies

9. Red Hat

Rescan scsi not working in Redhat 9

Hi all i am adding one more scsi hdd in my vmware testing environment with Redhat 9 . But the following commands are not working i found that these commands working on rhel 6. ls /sys/class/scsi_host echo "- - -" > /sys/class/scsi_host/host0/scan please let me know the commands for rehat... (0 Replies)
Discussion started by: Vaibhav.T
0 Replies

10. Red Hat

FC Luns rescan issue

Hi all we have two Rac cluster in our environment. we have asked our storage team to provide luns for adding space to our rac. Right now in one our server luns are visible but not in another. But if i see dmesg in servers i can see disk attached but not able to see them. even iostat showing... (6 Replies)
Discussion started by: sumit6in
6 Replies
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 3.10 June 2014 FC_REMOTE_PORT_DELET(9)
All times are GMT -4. The time now is 05:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy