Optimizing Systems to Use Flash Memory as a Hard Drive Replacement


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Optimizing Systems to Use Flash Memory as a Hard Drive Replacement
# 1  
Old 10-07-2008
Optimizing Systems to Use Flash Memory as a Hard Drive Replacement

When implemented properly, flash devices can boot systems faster and provide higher performance than disk drives. The guidelines in this Sun BluePrints article describe how a system with flash technology can exceed the performance of a server with a hard drive and operate over a similar lifespan.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Big difference between UNIX systems? Which one as OSX replacement for a developer?

Hello Everyone I am a software developer and private OS X user. I was enthusiastic with what I learned about Linux (on my OS X) during the operating system module at school and I am using some of it. But I may not want to go the Apple way till the end. And OS X is a little too big to run on a... (5 Replies)
Discussion started by: JacobPhelps
5 Replies

2. Solaris

Sun Ultra 2 Hard Drive Replacement

Hi all...I have an old Sun Ultra 2 running SunOS 5.7 (I know old). These machines have 2 hard drives and one of my drives fried. I bought some replacement drives and wanted to a simple "dd" command from my one good drive to copy all to the new replacement drive. The new drives however give me a... (11 Replies)
Discussion started by: psantinello
11 Replies

3. Solaris

removable flash drive

I have a removable usb flash drive which is visible below as no. 2 # rmformat Looking for devices... 1. Volmgt Node: /vol/dev/aliases/cdrom0 Logical Node: /dev/rdsk/c0t0d0s2 Physical Node: /pci@0,0/pci-ide@1f,1/ide@0/sd@0,0 Connected Device: HL-DT-ST DVD+-RW... (4 Replies)
Discussion started by: seyiisq
4 Replies

4. Ubuntu

Flash drive space issues

Hello, I have a 2 GB RealTek flash drive that has worked well in the past. It's about 1 year old but lately when I plug it into my Ubuntu Intrepid system it only shows 50 MB available even though there are no files on it: $ df -k /media/disk-1 Filesystem 1K-blocks Used... (1 Reply)
Discussion started by: mgb
1 Replies

5. Red Hat

Hard disk replacement

Hi all, I need some help with a RHEL 4 on a Sun Fire v65x machine. Some of the disks is damaged or has a hardware issue. This disk is connected to a hardware raid. The problem is that I don't know what is the brand, model and capacity of the disk. I've read the raid manual, but says... (3 Replies)
Discussion started by: adelgadom
3 Replies

6. SCO

mounting USB floppy drive /Flash drive in OSR 6.0

Can anybody help me out to mount USB flash /floppy drive in sco openserver 6.0 . (5 Replies)
Discussion started by: sureshdrajan
5 Replies

7. Solaris

USB flash Drive

Hello all.. I have a Verbatim 2 GB flash drive. I also have Solaris 10 running on my workstation. If I am in the Windows environment, it detects the flash drive. But when I plug it while I am in solaris, nothing happens. How will solaris 10 detect my flash drive? What do I have to do? any... (4 Replies)
Discussion started by: vr76413
4 Replies

8. Filesystems, Disks and Memory

The best partitioning schem for a 250GB Sata hard drive & a 75GB SCSI hard drive

Hi I have 2 75GB SCSI hard drives and 2 250GB SATA hard drives which are using RAID Level 1 respectively. I wana have both FTP and Apache installed on them as services. I'm wondering what's the best partitioning schem? I wana use FC3 as my OS, so, I thought I can use the 75GB hard drive as the /... (0 Replies)
Discussion started by: sirbijan
0 Replies

9. UNIX for Dummies Questions & Answers

Trying to copy old hard drive to new hard drive.

:confused: ........I have a new hard drive and I need to copy ALL info from the old to the new. I would like to use the dd command. I know the command is as follows...... dd if=/dev/rdsk/c1t1d0s0 of=/dev/rdsk/???????? Where I have the question marks is the problem. How do I find out what the... (4 Replies)
Discussion started by: shorty
4 Replies
Login or Register to Ask a Question
UDISKS(7)							      udisks								 UDISKS(7)

NAME
udisks - Storage Management DESCRIPTION
udisks provides an interface to enumerate storage devices and perform operations on them. Any application can access the org.freedesktop.UDisks service on the system message bus. Some operations (such as formatting disks etc.) is restricted using polkit. DEVICE INFORMATION
On Linux, udisks relies on recent versions of udev(7) and the kernel. Influential device properties in the udev database include: UDISKS_PRESENTATION_HIDE If set to 1 this is a hint to presentation level software that the device should not be shown to the user. UDISKS_PRESENTATION_NOPOLICY If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device). UDISKS_DISABLE_POLLING If set to 1 this will disable the polling of drives for media changes, for devices which do not send out media notifications by themselves (this mostly affects CD drives). Some CD drives cause bad effects such as very high CPU usage when being polled. UDISKS_PRESENTATION_NAME The name to user for the device when presenting it to the user. UDISKS_PRESENTATION_ICON_NAME The icon to use when presenting the device to the user. If set, the name must follow the freedesktop.org icon theme specification. The ID_DRIVE_* properties are used to describe what kind of physical media can be used in a device. These are typically set on the main block device (e.g. /dev/sdb) and more than one these properties can be set if the device supports multiple kinds of media. ID_DRIVE_EJECTABLE Whether the media in the drive is physically ejectable. Only set this to 1 (or 0) if the drive truly uses (or doesn't) ejectable media. In particular, it is not necessary to set this for e.g. iPod or Kindle devices where it is necessary to send a command via eject(1) since the desktop user session will offer this option for removable devices regardless of whether they are ejectable. If this property is not set, a heuristic will be used to determine if the media is ejectable (drives using optical, Zip or Jaz media are considered ejectable). ID_DRIVE_DETACHABLE Whether the device is detachable. It is only meaningful to set this to 0 (to avoid marking a device as detachable) since the code for detaching the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive is detachable (currently only devices connected through USB are detachable). ID_DRIVE_CAN_SPINDOWN Whether the device can spin down. It is only meaningful to set this to 0 (to avoid marking a device as being capable of spinning down) since the code for spinning down the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive can spin down (currently only ATA devices, including those USB devices with a SAT layer) can be spun down). ID_DRIVE_FLASH The device is compatible with flash. ID_DRIVE_FLASH_CF The device is compatible with Compact Flash. ID_DRIVE_FLASH_MS The device is compatible with Memory Stick. ID_DRIVE_FLASH_SM The device is compatible with SmartMedia. ID_DRIVE_FLASH_SD The device is compatible with SecureDigital. ID_DRIVE_FLASH_SDHC The device is compatible with High-Capicity SecureDigital. ID_DRIVE_FLASH_MMC The device is compatible with MultiMediaCard. ID_DRIVE_FLOPPY The device is compatible with floppy disk. ID_DRIVE_FLOPPY_ZIP The device is compatible with Zip. ID_DRIVE_FLOPPY_JAZ The device is compatible with Jaz. The ID_DRIVE_MEDIA_* properties describe the current media in a device. As with the ID_DRIVE_* properties, these properties are typically set on the main block device (e.g. /dev/sdb). Typically only one of these properties are set. ID_DRIVE_MEDIA_FLASH The physical media currently inserted into the device is flash. ID_DRIVE_MEDIA_FLASH_CF The physical media currently inserted into the device is Compact Flash. ID_DRIVE_MEDIA_FLASH_MS The physical media currently inserted into the device is Memory Stick. ID_DRIVE_MEDIA_FLASH_SM The physical media currently inserted into the device is SmartMedia. ID_DRIVE_MEDIA_FLASH_SD The physical media currently inserted into the device is SecureDigital. ID_DRIVE_MEDIA_FLASH_SDHC The physical media currently inserted into the device is High-Capicity SecureDigital. ID_DRIVE_MEDIA_FLASH_MMC The physical media currently inserted into the device is MultiMediaCard. ID_DRIVE_MEDIA_FLOPPY The physical media currently inserted into the device is floppy disk. ID_DRIVE_MEDIA_FLOPPY_ZIP The physical media currently inserted into the device is Zip. ID_DRIVE_MEDIA_FLOPPY_JAZ The physical media currently inserted into the device is Jaz. REMOTE CLIENTS
TODO: write me. AUTHOR
Written by David Zeuthen david@fubar.dk with a lot of help from many others. BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at http://bugs.freedesktop.org/enter_bug.cgi?product=udisks. SEE ALSO
udev(7), polkit(8), udisks-daemon(8), udisks-tcp-bridge(1), udisks(1) udisks March 2008 UDISKS(7)