Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Reserve Failed error for HD
Operating Systems Solaris Reserve Failed error for HD Post 85851 by Perderabo on Friday 7th of October 2005 12:49:11 PM
Old 10-07-2005
Well, I'm not sure. I have been looking at the source code for format. It looks like the format program issued a SCSI Reserve command to the disk via a uscsi ioctl() call and this failed. Previous to this, the format program issued a SCSI Inquiry command which succeeded. Looking the SCSI-2 Standard, it does not look like the Reserve command will actually do I/O. And you can do an Inquiry while another Inititator has a device reserved.

So I am guessing that somehow the system thinks that the drive is reserved. This could be legitimate if the SCSI chain connected to two hosts in a cluster or something like that. Maybe the drive just is in a confused state... a power cycle is susposed to reset any reservations. Maybe the drive is broken is some way that makes it always look reserved. Few of us actually ever use the "format" menu item in the format command, so maybe it has a bug.

But I would try some other stuff before I conclude that the drive is bad.
 

8 More Discussions You Might Find Interesting

1. Linux

proper way to reserve ports in linux

How do you debug a perl script non interactively, similar to bash -x? (1 Reply)
Discussion started by: marcpascual
1 Replies

2. Solaris

Reserve Memory for Global Zone

We have several containers on one machine and would like to reserve some memory for the global zone. capped-memory only allows max physical/swap and setting a max on each container isn't an option. The server has 32GB physical and 30GB swap. Currently there are ten containers on it. Normally... (6 Replies)
Discussion started by: kharjahn
6 Replies

3. Filesystems, Disks and Memory

Create file for space Reserve

Hi All, I want to make a 3GB of space reserve on Solaris. Let me know whether there is a way by creating empty file of 3GB so that i can delete that file in future to utilize that space. Or any other better ways for space reserve. -Vinodh' Kumar (4 Replies)
Discussion started by: vino_hymi
4 Replies

4. Shell Programming and Scripting

Reserve resources (memory and processes)

I have a shell script which sets some variables and then calls modules of a program in succession, one by one. Problem is that the script is executed on servers with many users, so sometimes the script starts running, runs for 10 minutes and then breaks due to lack of resources when other users run... (1 Reply)
Discussion started by: tetreb
1 Replies

5. Solaris

Cygwin X Server error: xdmcp fatal error session failed session 23 failed for display

Hi, i got the following error when i tried to access the cygwin x server from a windows XP PC. "xdmcp fatal error session failed session 23 failed for display" Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies

6. AIX

Reserve Ports

Hi I have a ticket to Reserve ports for SAS install in SAS servers. Does anyone knows the procedure how to do it. it will be helpful for me please Thanks in Advance (4 Replies)
Discussion started by: gulamibrahim
4 Replies

7. UNIX for Advanced & Expert Users

Reserve Ephemeral ports

my apps use port 40001; however, for example, firstly, I ftp to other server, it made a high port locally, remote is port 21, unfortunately, it hit my port 40001 and my apps is unable to startup. This chance is very very little, but I hit it. Can resevse my port 40001? otherwise command don't use it (5 Replies)
Discussion started by: goodbid
5 Replies

8. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies

LEARN ABOUT FREEBSD

cd

CD(9)							   BSD Kernel Developer's Manual						     CD(9)

NAME

     cd -- CDROM driver for the CAM SCSI subsystem

DESCRIPTION

     The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com-
     mands.  Some drives do not behave as the driver expects.  See the QUIRKS section for information on possible flags.

QUIRKS

     Each CD-ROM device can have different interpretations of the SCSI spec.  This can lead to drives requiring special handling in the driver.
     The following is a list of quirks that the driver recognize.

     CD_Q_NO_TOUCH    This flag tells the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what
		      size it is.  This flag is currently unimplemented in the CAM cd driver.

     CD_Q_BCD_TRACKS  This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal.  If the drive seems
		      to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag.

     CD_Q_NO_CHANGER  This flag tells the driver that the device in question is not a changer.	This is only necessary for a CDROM device with
		      multiple luns that are not a part of a changer.

     CD_Q_CHANGER     This flag tells the driver that the given device is a multi-lun changer.	In general, the driver will figure this out auto-
		      matically when it sees a LUN greater than 0.  Setting this flag only has the effect of telling the driver to run the initial
		      read capacity command for LUN 0 of the changer through the changer scheduling code.

     CD_Q_10_BYTE_ONLY
		      This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands.  In general these
		      types of quirks should not be added to the cd(4) driver.	The reason is that the driver does several things to attempt to
		      determine whether the drive in question needs 10 byte commands.  First, it issues a CAM Path Inquiry command to determine
		      whether the protocol that the drive speaks typically only allows 10 byte commands.  (ATAPI and USB are two prominent exam-
		      ples of protocols where you generally only want to send 10 byte commands.)  Then, if it gets an ILLEGAL REQUEST error back
		      from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead.	The only
		      reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6
		      byte commands.

FILES

     /sys/cam/scsi/scsi_cd.c  is the driver source file.

SEE ALSO

     cd(4), scsi(4)

HISTORY

     The cd manual page first appeared in FreeBSD 2.2.

AUTHORS

     This manual page was written by John-Mark Gurney <jmg@FreeBSD.org>.  It was updated for CAM and FreeBSD 3.0 by Kenneth Merry
     <ken@FreeBSD.org>.

BSD
								  March 25, 2014							       BSD
All times are GMT -4. The time now is 06:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy