Sponsored Content
Top Forums UNIX for Dummies Questions & Answers What should I format my SSD with? Post 302922866 by achenle on Tuesday 28th of October 2014 06:48:28 PM
Old 10-28-2014
Quote:
Originally Posted by Corona688
SMART statistics are just index numbers. The drive doesn't actually tell the computer "flying head time is too long", it just spits out some numbers -- a test number, a value, and the acceptable ranges(so your program doesn't have to know what it is to know it's bad). So, whatever test number "flying head hours" is may mean something totally different for your SSD. Look up the manual for your drive or ask the manufacturer.

I reccomend ext4 over ext3 for heavy-duty things since it's faster for large partitions (ever tried to fsck a 100GB ext3 partition? Takes a while). Also, it can be defragmented without unmounting it, which could end up being very important for the long-term performance of your virtual machines.

Otherwise, making a filesystem work well with an ssd is mostly about fine-tuning it to match its block sizes and boundaries. If you get it wrong, it won't explode, but performance might be just slightly worse. See SSD - Gentoo Wiki for some general advice.

Also, an fstrim once in a while is good for the SSD, it helps wear-levelling work better by informing the SSD which blocks it doesn't have to care about anymore. See the wiki again for that.
Except that defragging really doesn't matter for SSDs because without a head to seek, non-contiguous access is the same as contiguous access. Smilie
This User Gave Thanks to achenle For This Post:
 

10 More Discussions You Might Find Interesting

1. BSD

Using SSD in FreeBSD

Now that SSD drives are becoming mainstream, I had a few questions on installing a SSD drive in a FreeBSD environment. Can FreeBSD be made SSD aware, that is, somehow let FreeBSD know that reads and writes should be limited or deferred to extend the disk's life? Is there a setting for wear... (0 Replies)
Discussion started by: figaro
0 Replies

2. Hardware

Use of SSD for serving webpages

I have seen research articles and forum postings that demonstrate that SSDs are poor at reading large files: the larger the file, the slower the SSD compared to traditional hard disk drives. The difference with hard disk drives becomes apparent at medium size files, say 20KB. Does this mean that... (2 Replies)
Discussion started by: figaro
2 Replies

3. AIX

SSD with GPFS ?

Hi, does anyone here happen to know if I could run GLVM or GPFS on Solid State Disks? I have a high volume / high transaction Sybase HACMP cluster currently setup with SRDF to the DR datacentre. My business now considers to move everything to SSD storage but we still need to get the data to... (0 Replies)
Discussion started by: zxmaus
0 Replies

4. Hardware

SSD - motherboard compatibility question

I am planning on purchasing an OCZ SSD that runs on the PCI Express lane. Now, while the motherboard it is to be installed on is not listed in the compatibility table, this does not mean it will not work, because the table only lists the motherboards that have been tested. Still, is there a way... (4 Replies)
Discussion started by: figaro
4 Replies

5. Programming

Program to test SSD

Hi, I want to use SSD as storage to replace hard disk in server(Linux system). Need some help how to code the pgm(C or C ++)to test the SSD functionality (eg: Badblocks ). As im new to this line. i dont have much experience. Any input from experts/pro much appreciated. thanks a lot. :confused: (4 Replies)
Discussion started by: crazydude80
4 Replies

6. Hardware

mobo with built-in ssd and linux

hi, thinking of building a system around this mobo: GA-Z68XP-UD3-iSSD. this has an ssd built-in to the mobo that serves as a cache for the sata drives. does linux have a chance of working on this? or is it going to get confused. thanks (6 Replies)
Discussion started by: rtayek
6 Replies

7. Filesystems, Disks and Memory

RAID 0 for SSD

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)
Discussion started by: figaro
6 Replies

8. Solaris

Install ssd hdd on Solaris 5.8

Hi, I want to install an SSD on my hdd ULTRA SPARK 10 with solaris 5.8. I can not format it because to complete the operation is necessary to enter the number of sectors and cylinders ... I also tried to make a copy disk2disk but goes wrong ... someone has an idea? Has anyone ever done such a... (0 Replies)
Discussion started by: stirux
0 Replies

9. Filesystems, Disks and Memory

SSD Caching, how its done, right choice?

Hello, someone needed VPS with SSD caching, he want to use server for websites hosting. What does that mean, this SSD caching and is it optimal solution for this? Also i listen some SSD dont like too much of writting so how one can recognise certain SSD is made the way that its not destroyed... (1 Reply)
Discussion started by: postcd
1 Replies

10. Hardware

SAS or SSD for Ubuntu 14.04 and data analysis

I am in the process of building a workstation and have a question related to performance. I am a scientist who deals with big data (average file size 30-50gb). My OS is ubuntu 14.04 and so far I have a 128gb dual xeon E5-2630 with 6 cores each. I/O buffering is an issue so I am adding a 256/512?... (6 Replies)
Discussion started by: cmccabe
6 Replies
RESIZE2FS(8)                                                  System Manager's Manual                                                 RESIZE2FS(8)

NAME
resize2fs - ext2/ext3/ext4 file system resizer SYNOPSIS
resize2fs [ -fFpPMbs ] [ -d debug-flags ] [ -S RAID-stride ] [ -z undo_file ] device [ size ] DESCRIPTION
The resize2fs program will resize ext2, ext3, or ext4 file systems. It can be used to enlarge or shrink an unmounted file system located on device. If the filesystem is mounted, it can be used to expand the size of the mounted filesystem, assuming the kernel and the file system supports on-line resizing. (Modern Linux 2.6 kernels will support on-line resize for file systems mounted using ext3 and ext4; ext3 file systems will require the use of file systems with the resize_inode feature enabled.) The size parameter specifies the requested new size of the filesystem. If no units are specified, the units of the size parameter shall be the filesystem blocksize of the filesystem. Optionally, the size parameter may be suffixed by one of the following the units designators: 's', 'K', 'M', or 'G', for 512 byte sectors, kilobytes, megabytes, or gigabytes, respectively. The size of the filesystem may never be larger than the size of the partition. If size parameter is not specified, it will default to the size of the partition. Note: when kilobytes is used above, I mean real, power-of-2 kilobytes, (i.e., 1024 bytes), which some politically correct folks insist should be the stupid-sounding ``kibibytes''. The same holds true for megabytes, also sometimes known as ``mebibytes'', or gigabytes, as the amazingly silly ``gibibytes''. Makes you want to gibber, doesn't it? The resize2fs program does not manipulate the size of partitions. If you wish to enlarge a filesystem, you must make sure you can expand the size of the underlying partition first. This can be done using fdisk(8) by deleting the partition and recreating it with a larger size or using lvextend(8), if you're using the logical volume manager lvm(8). When recreating the partition, make sure you create it with the same starting disk cylinder as before! Otherwise, the resize operation will certainly not work, and you may lose your entire filesystem. After running fdisk(8), run resize2fs to resize the ext2 filesystem to use all of the space in the newly enlarged partition. If you wish to shrink an ext2 partition, first use resize2fs to shrink the size of filesystem. Then you may use fdisk(8) to shrink the size of the partition. When shrinking the size of the partition, make sure you do not make it smaller than the new size of the ext2 filesystem! The -b and -s options enable and disable the 64bit feature, respectively. The resize2fs program will, of course, take care of resizing the block group descriptors and moving other data blocks out of the way, as needed. It is not possible to resize the filesystem concurrent with changing the 64bit status. OPTIONS
-b Turns on the 64bit feature, resizes the group descriptors as necessary, and moves other metadata out of the way. -d debug-flags Turns on various resize2fs debugging features, if they have been compiled into the binary. debug-flags should be computed by adding the numbers of the desired features from the following list: 2 - Debug block relocations 4 - Debug inode relocations 8 - Debug moving the inode table 16 - Print timing information 32 - Debug minimum filesystem size (-M) calculation -f Forces resize2fs to proceed with the filesystem resize operation, overriding some safety checks which resize2fs normally enforces. -F Flush the filesystem device's buffer caches before beginning. Only really useful for doing resize2fs time trials. -M Shrink the file system to minimize its size as much as possible, given the files stored in the file system. -p Prints out a percentage completion bars for each resize2fs operation during an offline resize, so that the user can keep track of what the program is doing. -P Print an estimate of the number of file system blocks in the file system if it is shrunk using resize2fs's -M option and then exit. -s Turns off the 64bit feature and frees blocks that are no longer in use. -S RAID-stride The resize2fs program will heuristically determine the RAID stride that was specified when the filesystem was created. This option allows the user to explicitly specify a RAID stride setting to be used by resize2fs instead. -z undo_file Before overwriting a file system block, write the old contents of the block to an undo file. This undo file can be used with e2undo(8) to restore the old contents of the file system should something go wrong. If the empty string is passed as the undo_file argument, the undo file will be written to a file named resize2fs-device.e2undo in the directory specified via the E2FSPROGS_UNDO_DIR environment variable. WARNING: The undo file cannot be used to recover from a power or system crash. KNOWN BUGS
The minimum size of the filesystem as estimated by resize2fs may be incorrect, especially for filesystems with 1k and 2k blocksizes. AUTHOR
resize2fs was written by Theodore Ts'o <tytso@mit.edu>. COPYRIGHT
Resize2fs is Copyright 1998 by Theodore Ts'o and PowerQuest, Inc. All rights reserved. As of April, 2000 Resize2fs may be redistributed under the terms of the GPL. SEE ALSO
fdisk(8), e2fsck(8), mke2fs(8), lvm(8), lvextend(8) E2fsprogs version 1.44.1 March 2018 RESIZE2FS(8)
All times are GMT -4. The time now is 03:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy