08-09-2011
The man seems to day you can pull them all offline, but is otherwise terse, so maybe they assume if you want to limp without the bad drive, you just pull it? Maybe the facility you want is lower down, in the system device layer not the md virtual device layer.
This User Gave Thanks to DGPickett For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I've recently mirrored the 4 disks in a V440. Disks 0 + 1 have been mirrored with hardware mirroring using the command raidctl -c c1t0d0 c1t2d0, the other 2 disks have been mirrored using Soltisce Disk Suite. I know how to check the progress for the SDS mirroring but how can I find the... (2 Replies)
Discussion started by: Chains
2 Replies
2. Solaris
Hello Gurus!!
Very recently i tried to mount a USB pen drive onto my solaris 10 (X4170 model) server. As i understand, in ideal scenarios it should get mounted automatically, but it did not happen. Neither anything is shown in "iostat -En" output or "rmformat -l" about the pen drive.
I also... (10 Replies)
Discussion started by: EmbedUX
10 Replies
3. UNIX for Advanced & Expert Users
Hello, I have 4 drives (500G each) in a raid 10, I got a power failior and this is the result?
cat /proc/mdstat
Personalities :
md126 : inactive sdb sdc sdd sde
1953536528 blocks super external:-md127/0
md127 : inactive sdd(S) sde(S) sdb(S) sdc(S)
9028 blocks super... (3 Replies)
Discussion started by: rmokros
3 Replies
4. UNIX for Advanced & Expert Users
Hi everyone,
I am not sure if I understand how mdadm --create /dev/md0 --level=container works?
A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device?
I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies
5. Debian
Trying to mount an external 160GB Toshiba drive but....
this is my dmesg tail output:
usb 2-2: new high speed USB device using ehci_hcd and address 3
usb 2-2: New USB device found, idVendor=13fd, idProduct=1618
usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 2-2:... (4 Replies)
Discussion started by: Ridson
4 Replies
6. Red Hat
had this RHEL 5 installation with /dev/sda1 and /dev/sda2 running..
created two more partitions /dev/sdj1 and /dev/sdj2 , the same sized partition as /dev/sda
trying to use mdadm to create RAID1 ..
I cannot even do it in "rescue" mode, I wonder if it can be done..
it kept... (2 Replies)
Discussion started by: ppchu99
2 Replies
7. UNIX for Dummies Questions & Answers
Hi
I am using SUSE 11 linux
I have couple of "nfs" entries in /etc/fstab which are automatically loaded after system restart.
One of the entry is windows drive mounted using cifs as shown below
//IP-Address/Partition /mnt/x cifs credentials=/creds/.creds,rw,uid=<name> 0 0
I want to... (1 Reply)
Discussion started by: rakeshkumar
1 Replies
8. Filesystems, Disks and Memory
Hello,
i have a system with 6 sata3 seagate st3000dm01 disks running on stable Debian with software raid mdadm. i have md0 for root and md1 for swap and md2 for the files. i now want to add one more disk = sdh4 for md2 but i got this errors:
The new disk is connected to an 4 port sata... (7 Replies)
Discussion started by: Sunghost
7 Replies
9. Solaris
I am connecting a USB mass storage removeable drive to Solaris 10 x86 machine.
The device is detected and i am able to perform standard read and write functions.
But i want to use a code to send IOCTL based SCSI commands to the same device to read and write the data. Which i am unable to do so.... (17 Replies)
Discussion started by: danish2012
17 Replies
10. Solaris
Hi fellow members!
I have a oracle solaris server with two internal disks, that acts as an authentication server only, and for now the server seems to be doing its job, but when typing metastat -c I get some notifications.
I am not familiar with SVM, I wonder if someone can help me on this:... (3 Replies)
Discussion started by: fretagi
3 Replies
XPT(4) BSD Kernel Interfaces Manual XPT(4)
NAME
xpt -- CAM transport layer interface
SYNOPSIS
None.
DESCRIPTION
The xpt driver provides a way for userland applications to issue certain CAM CCBs to the kernel.
Since the xpt driver allows direct access to the CAM subsystem, system administrators should exercise caution when granting access to this
driver. If used improperly, this driver can allow userland applications to crash a machine or cause data loss.
KERNEL CONFIGURATION
There is no kernel configuration required for the xpt driver. It is enabled when SCSI support is enabled in the kernel. There is one
instance of the xpt driver per CAM transport layer instance. Since there is currently only one CAM transport layer, there will only be one
instance of this driver.
IOCTLS
CAMIOCOMMAND This ioctl takes certain kinds of CAM CCBs and passes them through to the CAM transport layer for action. Only the following
CCB types are supported:
XPT_SCAN_BUS
XPT_RESET_BUS
XPT_SCAN_LUN
XPT_ENG_INQ
XPT_ENG_EXEC
XPT_DEBUG
XPT_DEV_MATCH
XPT_PATH_INQ
The above CCBs are the only ones supported since it makes more sense to send them through a generic passthrough device rather
than a passthrough device tied to a particular underlying SCSI device.
CAMGETPASSTHRU This ioctl takes an XPT_GDEVLIST CCB, and returns the passthrough device corresponding to the device in question.
FILES
/dev/xpt0 Character device node for the xpt driver.
DIAGNOSTICS
None.
SEE ALSO
cam(3), cam_cdbparse(3), pass(4), camcontrol(8)
HISTORY
The CAM transport layer driver first appeared in FreeBSD 3.0.
AUTHORS
Kenneth Merry <ken@FreeBSD.org>
BSD October 10, 1998 BSD