07-07-2009
The best is to make a ls -ltr /dev/rdsk . The attached LUN will be at the bottom with the date.
The format command is not a good choice if you have lots of drives connected. It can be that the new presented LUN is #58 or so. It's not that the not labeled drives are on top.
10 More Discussions You Might Find Interesting
1. Solaris
Is there a limit to the number of LUNS that can be concatenated using Solaris Volume manager with Soft partitions?
I have worked with some AIX admins in the past and there was such a limitation therefore limiting the size the filesystem could grow to.
Is there such a limitation in Solaris 9... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
2. Programming
i wrote a tiny version of tail command using a large buffer statically allocated but, in a second time, i found another version in which i use a bidimensional array dynamically allocated.
here is the first version
/*my tiny tail, it prints the last 5 line of a file
*/
#include<stdio.h>... (4 Replies)
Discussion started by: lucasclaus
4 Replies
3. Solaris
Hi guys!
Could you tell me what's this figure about? (See the attached figure below.)
This is a representation of block allocation filesystem and extent allocation filesystem in Solaris.
Does this mean that in a block-based allocation, data are placed in individual blocks while in... (0 Replies)
Discussion started by: arah
0 Replies
4. Solaris
hi,
what are the steps to detect and configure a new attached lun in Solaris 10.
Is there any difference between cfgadm and luxadm command ?
rgds,
snjksh (5 Replies)
Discussion started by: snjksh
5 Replies
5. Solaris
Hi,
As per my knowledge, the maximum number of groups that can be allocated to a folder (in Solaris 10) is 16. But I wonder how this rule is applicable to folders which are mounted on NFS which can be accessed by 100s of groups? or is there is a restriction present? I have never handled such a... (5 Replies)
Discussion started by: poga
5 Replies
6. Solaris
Hi All,
I'm using Solaris server, SunOS 5.10 Generic_144488-08 sun4u sparc SUNW, SPARC-Enterprise.
There is a newly created LUN of 250GB (EMC). I've scanned the system and able to see the new LUN.
For example:
103. emcpower19a <DGC-VRAID-0430 cyl 48638 alt 2 hd 256 sec 16>... (4 Replies)
Discussion started by: superHonda123
4 Replies
7. Red Hat
Hi All,
I am new for this blog and this is my first Query on this blog. I would like to dael with graet masters on linux.
Here we go,
After storage people created the LUN, How to add that LUN to Linux server. (Make that LUN visibility on linux server.) ?
How to view the LUN... (5 Replies)
Discussion started by: abhay1983
5 Replies
8. Solaris
How to get LUN WWN (i.e LUN mapped from a storage box say Symmetrix or clariion) in Solaris. fcinfo command does give the Target port wwn but what i'm looking for is the LUN WWN. Any help is appreciated. (2 Replies)
Discussion started by: Manish00712
2 Replies
9. Linux
I have created a lun on Storage and connected it to server using fiber channel.
LUN is presented on new Server .
How do i check and mount this newly created LUN? (1 Reply)
Discussion started by: pinga123
1 Replies
10. Red Hat
I have NetApp LUN that was presented to a Red Hat Enterprise Linux Server release 5.7 (Tikanga) machine.
But this LUN has already data, because it was being used on another server.
I can see the new LUN when running fdisk:
fdisk -l | egrep '^Disk' | egrep -v 'dm-' | grep -v identifier
Disk... (15 Replies)
Discussion started by: fretagi
15 Replies
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 tell 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 <gurney_j@efn.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry
<ken@FreeBSD.org>.
BSD
September 2, 2003 BSD