In article <YvydnRaPRMfSgSfbRVnygAA@infopact.nl>,
R.Smits <smitsr@gmail.com> wrote:
>One of our iscsi stacks had a fault. So the disk was gone for a couple
>of minutes.
>
>Now everything is back up. But when we want to access the disk we see
>the folowing with the format command:
>We can choose the disk, but it says "not formatted"
>
>4. c2t0690A018E0F14991125844847700D063d0 <drive not available>
> /scsi_vhci/ssd@g0690a018e0f14991125844847700d063
>
>In messages file :
>Aug 8 21:35:51 srv1 scsi: [ID 107833 kern.warning] WARNING:
>/scsi_vhci/ssd@g0690a018e0f1499112
>5844847700d063 (ssd0):
>Aug 8 21:35:51 srv1 offline or reservation conflict
>
>We have not rebooted the machine because this would cause a lot of
>trouble for our customers, so we want to avoid this.
>
>What is this and how can we make this disk available again ?
>
>We tried : "devfsadm -C" but no luck.

I wouldn't really expect the above to work - at least, not by itself.

After you experience a failure of the iSCSI server, you need to ensure that
the iSCSI client (in this case, the system that is displaying the "drive
not available" message) attempts to log back into the iSCSI server to
re-establish the iSCSI SAN connection. If this doesn't happen, the LUN will
remain in an offline state. If the connection is still offline (as seems to
be indicated by your log messages, above), you can run `devfsadm` until
you're blue in the face and it won't help as there are no device nodes
available to configure. You need to verify that you have actually restored
the iSCSI initiator's connection to the remote LUN (this may require a
rerunning of the remote LUN discovery - dunno for sure). Once you've
restored the connection to the LUN, things *should* go back to normal.

--

"You can only be -so- accurate with a claw-hammer." --me