07-30-2008 08:00 AM
Solid state drives (SSD) have many advantages over traditional spinning-platter hard drives including no noise, low power and heat generation, good resistance to shock, and most importantly, extremely low seek times. To see just how much an SSD might improve performance, I used Bonnie++ to benchmark a contemporary SSD as it might be used in a laptop computer.
I'm running glusterfs on CentOS 6.6 two nodes, (the SSD (samsung 840 1TB x2) is RAID 0 on the HP DL380 G6) x2, and trimming is not enable on it by checking /dev/sdb1/xxxxx/discard_max_bytes=0. Do I still need trimming? Somehow my filesystem is fine with 35-30% free space and running very fast.
... (1 Reply)
Hello,
I want to delete a RAID configuration an old server has.
Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton?
I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Nowadays the fastest SSDs achieve read-speeds of between 1500 MB/s to 1900 MB/s. Let's say that two such SSDs in RAID 0 achieve roughly double the throughput, ie 3000 MB/s. That is only half an order of magnitude removed from RAM ((10)^(1/2) * 3000 = 10.000), very broadly speaking.
So for the... (6 Replies)
I have an upgrade path in mind for a new computer that will be stocked with a 2TB SATA 300 hard disk. This is a choice based on information that SATA 300 is not necessarily faster than SATA 600. The upgrade path in a year time or so would then involve the purchase of an SSD that would contain the... (4 Replies)
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Hello everybody,
I need to connect a laptop 2.5 SATA hard drive to a Desktop board (which uses 3.5' SATA hard drives). I've tried the connectors and they fit excellent in the 2.5 SATA connectors.
The problem is that the laptop hard drive uses 5v and the PC's power source sends 12v. So, my... (4 Replies)
Hello all
We just built a storage cluster for our new xenserver farm. Using 3ware 9650SE raid controllers with 8 x 1TB WD sata disks in a raid 5, 256KB stripe size.
While making first performance test on the local storage server using dd (which simulates the read/write access to the disk... (1 Reply)
trying to setup a sata drive using a sata to scsi adaptor
I have a sata 1TB Deskstar that I had setup before and during shipment from a facilty to another, the disk failed. The handling was not great, lots of throwing boxes, etc. I have a new disk from Hitachi (thankyou Hitachi) anyway, I don't... (1 Reply)
sata(7D) Devices sata(7D)NAME
sata - Solaris SATA framework
DESCRIPTION
Serial ATA is an interconnect technology designed to replace parallel ATA technology. It is used to connect hard drives, optical drives,
removable magnetic media devices and other peripherals to the host system. For complete information on Serial ATA technology, visit the
Serial ATA web site at http://www.serialata.org.
Up to 32 SATA devices may be plugged directly to each SATA HBA supported by the Solaris SATA framework. The actual number of pluggable
devices my be lower, and is limited by a number of device ports on the SATA HBA. The maximum data rate is either 1.5Gb/sec. or 3.0Gb/sec.,
depending on the capability of a SATA device and SATA HBA controller.
The Solaris SATA framework adheres to the Serial ATA 1.0a specification and supports SATA-2 signaling speed 3.0Gb/sec. SATA devices that
are connected to SATA HBAs controlled by a SATA framework-compliant HBA driver are treated by the system as SCSI devices. The Solaris SCSI
disk driver (sd(7D)) is attached as a target driver for each device node created by the SATA framework. You can use the cfgadm(1M) utility
to manage hot plugged and unplugged SATA devices.
FILES
/kernel/misc/sata 32-bit ELF kernel module (x86).
/kernel/misc/amd64/sata 64-bit ELF kernel module (x86).
ATTRIBUTES
See attributes(5) for descriptions of the following attribute:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
|Availability |SUNWckr |
+-----------------------------+-----------------------------+
SEE ALSO cfgadm(1M), prtconf(1M), cfgadm_sata(1M), attributes(5), ahci(7D), marvell88sx(7D), nv_sata(7D), sd(7D), si3124(7D)
Serial ATA 1.0a Specification -- Serial ATA International Organization.
Serial ATA II (Extension to Serial ATA 1.0.a.) -- Serial ATA International Organization.
http://www.sun.com/io
DIAGNOSTICS
The messages described below may appear on the system console as well as being logged. All messages are presented in one of the following
formats and are followed by the diagnostic message:
sata: WARNING: <controller/devices/.. path>:
or:
sata: NOTICE: <controller/devices/.. path>:
...where <controller/devices/.. path> identifies a specific SATA HBA issuing a diagnostic message shown below.
SATA port X: link lost.
Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost.
SATA port X: link established.
Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been established.
SATA port X: device reset.
The device plugged to the specified SATA device port has been reset. The reset may be due to a communication or command error, command
timeout, or an explicit request from the host.
SATA port X failed.
The specified SATA device port failed and is in an unusable state. You can change the port state by deactivating the port and activat-
ing it again using cfgadm SATA hardware-specific commands (see cfgadm_sata(1M)).
SATA port X error.
An error was detected in specified SATA device port operations.
SATA device detached at port X.
Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost and could not
be re-established. The SATA framework assumes that the device is unplugged from the specified SATA device port.
SATA device detected at port X.
Communication( via serial link) between the HBA and the device plugged to the specified empty SATA device port has been established.
The SATA framework assumes that the new device is plugged to the specified SATA device port.
SATA disk device at port X.
This message is followed by a disk description specifying the disk vendor, serial number, firmware revision number and the disk capa-
bilities.
SATA CD/DVD (ATAPI) device at port X.
This message is followed by a SATA CD/DVD description specifying the DVD vendor, serial number, firmware revision number and the DVD
capabilities.
SATA device at port X cannot be configured. Application(s) accessing previously attached device have to release it before newly inserted
device can be made accessible.
The port cannot be configured because there is application using the previous attached device, so the application must release it, then
the newly inserted device can be configured.
Application(s) accessing previously attached SATA device have to release it before newly inserted device can be made accessible.
The target node remained and it belongs to a previously attached device. This happens when the file was open or the node was waiting
for resources at the time the associated device was removed. Instruct event daemon to retry the cleanup later.
sata: error recovery request for non-attached device at cport X.
When error recovery is requested, the device is not yet attached.
SATA device at port X will not be power-managed.
When property "pm-capable" on the target device node setting fails, the SATA device won't be power-managed.
SATA disk device at port X does not support LBA.
The disk device plugged into specified SATA device port does not support LBA addressing and cannot be used.
Cannot identify SATA device at port X - device will not be attached.
IDENTIFY (PACKET) DEVICE data cannot be retrieved successfully after the device is attached to the SATA port.
sata: <HBA driver name><instance number>:hba attached failed.
The SATA HBA instance attach operation failed. This HBA instance cannot be configured and is not available.
sata: invalid ATAPI cdb length<command cdb length>.
The length of the command cdb is greater than that the device can support.
sata: invalid sata_hba_tran version X for driver <HBA driver name>.
The specified SATA HBA driver and the SATA framework are incompatible. The driver cannot attach and SATA HBAs controlled by this driver
(and devices plugged to this SATA HBA ports) are not available.
sata_hba_attach: cannot create SATA attachment point for port X.
The specified SATA device port cannot be configured in the system and a device plugged to this port could not be not be configured and
used.
sata_create_target_node: cannot create target node for device at port X.
The device target node for the device plugged to the specified SATA device port could not be created. As a result, the device cannot be
configured and used.
SunOS 5.11 5 Sep 2007 sata(7D)