Ubuntu :: Is There A Way That Can Verify That TRIM Is Working?
Aug 26, 2010
I have an OCZ Vertex SSD...the 30GB variety. recently I upgraded my kernel to 2.6.33. I have read that that is all that is needed in order for trim to just start working. Is there a way that I can verify that TRIM is working?I'm debating getting the Vertex2 100GB model because I love my SSD now, but would love to have a little more storage space. I just don't want to buy it without TRIM working.
I have a web application that I am trying to upgrade. Part of their upgrade process involves using a migration tool to transfer data from one version to another. This tool relies on cronjobs for it to function.According to them, the migration is not working because my cronjobs are not working properly.Is there a way to verify this?Below is what I had to paste in my crontab:MAILTO=webmaster@mymailhost.com* * * * * cd /srv/www/whiterhino/d7/periodic; /usr/bin/php -q cron.php
How do I verify that my 6 GB/s SATA ports are working under Linux?
Linux detects the ports, and I can use them for disks but I would like to figure out if they are using a 6 GB/s controller/driver instead of the slower, more common speed.
I was running it portable on a 4gb usb drive via virtual box which worked great unless I used a computer that had virtualbox on it. The portable version would remove files that the original version needed. I decided to try Qemu. The problem is that the portable version only allows 1gb of space to install regardless the size of a usb drive. so the question is: Is there was a way to trim ubuntu 9.10 down to less than 1gb of disk space? If not is there another portable emulator that could be used instead? the only uses for this are for the use of evolution and opera in a linux environment.
I followed this tutorial [URL] to enable my TRIM support and now my fstab looks like this:
Quote:
# /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5).
[Code].....
but when I follow the second half of the tutorial http://lightrush.ndoytchev.com/rando...bledandworking to check and make sure it's working I don't get all zeros like I'm supposed. I tried waiting a while like I saw in another tutorial as well and check it again.. Still random numbers and no zeros.
The situation with TRIM in Ubuntu has me utterly confused. I don't know whether I need to manually run it or not. Sources I've found are disparate and unclear. I have Ubuntu 10.04 with latest updates (including kernel 2.6.32-26). I have an Intel X-25M drive with latest firmware, and it is formatted as ext4. So, does TRIM support run automatically? If not, how do I check if I need to run it, and then how do I run it if necessary?
In windows the only controllers that really work with TRIM is the onboard Intel ones, Jmicron, Marvell, Nvidia and AMD's don't pass the command to the drives if you use their own drivers. (And from what Ive read, the Micron sata6 controllers don't work with TRIM even using the default Microsoft drivers). In Linux do more then just Intel drives work with TRIM? I have a Nvidia 790i Ultra motherboard, the SATA controller is an Nvidia one which has 2 settings, ATA and Raid (if the drives aren't added to an array it runs them in AHCI) and has an additional Jmicron sata port.
If I enabled TRIM in the OS, would it work on either of those controllers? Also if anyone knows this, in Windows if you set an Intel controller to raid, you wont get TRIM on SSD's that are on the controller (but not in an array) with the default Microsoft driver like you would if it was set to AHCI, you only get it with the Intel RST drivers. Would a SSD on an Intel controller set to raid but not in an array get the TRIM command passed to it in Ubuntu?
We're planning to install CentOS on a new server that will be based on two Solid-State Disks in a RAID1 configuration. The RAID management will be handled by a hardware Adaptec controller. I've learnt that the TRIM function for SSD drives is supported starting from kernel 2.6.28.
But FFmpeg is not accurate and it started the video from a nearby point instead (from 00:24:46~). I tried to add 2 seconds to my starting point and it took another frame (not what I wanted).
Ok, Im likely to buy SSD 128gb drive and install Fedora 14 on it...but I have a question. If I go with ext4 will I get TRIM to work out of the box? Whats the status of kernel support on trim?
First system specs. Gateway Solo Pro 9300, 433Mhz, 288megs. OS Slackware 13.1 32-bit and KDE.
As I get more comfortable with Linux I find that I am doing more waiting for the computer to catch up.
Would it be better to trim down KDE or change to a lighter GUI? If I change to a lighter GUI will I have to reinstall things I have installed under KDE?
Does CentOS 5 support the ATA TRIM command for use with SSDs? Is the support automatic by default, or would I need to do something specific in order to enable the TRIM feature be used?
I am trying to set up an atom D525 low power PC 64-bit with a 40 GB solid state disk drive. Is it possible to specify ext4 during the install for proper SSD suupport? I read somewhere that after install I can place a -discard line in fstab to enable trim.
Edit: should I have asked this in the x86_64 forum, as I was planning on installing 64 bit?
I just bought a Samsung 850 Pro 250GB SSD drive and have since then found out that Linux has/had a faulty implementation of queued trim (which is a synonym for NCQ I think). I'm using kernel 4.1.0 (the default selected by the Debian 8.1 installer) and I've read that Samsung drives are blacklisted for queued trim by the recent kernels. However, the output of dmesg contains the following lines, with and without TRIM enabled for the drive (i.e. with or without the "discard" option in fstab for the drive):
Code: Select all[ 1.012287] ata6.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.013438] ata5.00: failed to get NCQ Send/Recv Log Emask 0x1 [ 1.013440] ata5.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA [ 1.015037] ata5.00: failed to get NCQ Send/Recv Log Emask 0x1
Since the depth is not 1 but rather 31, it looks like NCQ is enabled. I've disabled TRIM on the drive for now, and whether it's safe to enable TRIM or not.
Does Suse have any software based TRIM support available or that is in the works?I know there is to a degree new firmware becoming available that supports TRIM (although some are pretty rudimentary) but windows 7 does a fairly good job software side and upgrading the firmware occasionally involves the unbridled joy that is wiping the drive and starting again.
There are not SSDs with TRIM support available in my region that fit into my laptop (1.8", IDE, ZIF). I'm running Ubuntu 10.10.
Most articles (or questions on superuser) I've come across concering TRIM (or the lack thereof) date back to 2009, when not many SSDs with TRIM support were available and OS support was still very fresh.
I'm interested in the current situation, but I couldn't find too much information about it.
What are currently the "best practices" for using an SSD without TRIM under Linux? I've read about the wiper script included with hdparm. Do I understand correctly that I could use this to free unused blocks, e.g. by running it once a month? Some sources state that HFS+ (the default-filesystem of Mac OS X) doesn't suffer as badly from lack of TRIM as other filesystems. How about linux filesystems? Are there filesystems that are better suited for SSDs without TRIM than others?
My partition /dev/sda3 on an SSD drive doesn't contain any filesystem, but it contains garbage. How do I do a TRIM/DISCARD operation on the whole partition?
does Debian Lenny 5.0.4 stable supports SSD TRIM? If not, what package i need to add if i buy a new SSD and dont want to loose Hard Disk Performance over time?
I have a bunch of files (around 900) that have some special characters. Some of the files contains example, and quoting "[useless] filename (something)"so what I want is just to strip the brackets and parenthesis, some are folders, others are text files
I wrote this script which works but it should run automatically about once per week. I hunted and experimented with KDE Task Scheduler (no dice and no help anywhere) and cron (confusing instructions and cannot edit crontab -e with vim, and cannot enter cron folders/files). I would settle for a desktop shortcut to run the script but found no for that.
I'm looking for a way to launch "TRIM" commands to a SSD drive myself, from a c++ code I'm going to write, for flash erasing an SSD drive (and not to wait for others things that "should do it automatically in some circumstances if this or this, this and this have been enabled and [..]" but will never tell me if it worked or not
I know there is thousands of complicated ways to test and check if it worked, and also software that needs money to do so, that's why I just want to call myself the TRIM functions and read the return value (like true or false) in order to know if it worked !
Where I can find the c++ call that could permit me to do so ? I heard about the GLibC that gives a way to access every user space function related to Linux Kernel (poll, select and others) as standard c++ functions, I suppose that, if there is a way, it will be on the GLibC but how to find it ?
With the new Intel G2 SSDs coming out, I'm thinking about upgrading my hard drive. However, there seems to be an extra level of software support needed for SSD drives. From what I have read there can be performance degradation over time and other issues. Does anyone know how well SSD drives are supported in Linux and also if there is support for the TRIM command or if it is planned?
I am in the process of cloning a HD. Before I wipe the original drive I was wondering if there was a tool to create something like a md5 hash of the entire drive to verify that I have an exact copy. It does not necessarily have to be an md5 hash and any command line BASH options would work for me as well.
I am experiencing some strange behaviour with sound, and I have been messing around with installing some ALSA drivers. I suspect that I might have corrupted some part of the installed Ubuntu packages. Is there a way to check all the packages on the system for integrity using apt-get or similar?
I am not able to find any information to verify a downloaded .iso file for security and integrity at [URL]../download/ubuntu/download .Are they supplied elsewhere?