In fact you can start partition by any number x where x >= 64 and is ^2. Thus 64, 128, 256, ... 2048 etc. For completeness I have also tested Advanced Format Hard Drive Utility for WindowsXP developed by Western Digital and this piece of software aligns a first partition to a 2048 sector.
TRIM on solid state drives (SSD)
Keeping-things-TRIM asks: I've heard that without TRIM SSD performance will degrade over time. TRIM is now supported in some SSD firmware, and recently has been enhanced to support RAID systems. But TRIM does not work without OS support. Some TRIM support is available in the Linux kernel, but people are having trouble figuring out what is going on. So what's happening with TRIM?
DistroWatch answers: The issues facing solid state drives (SSD) and TRIM can be a little difficult to explain, but I'll try to give a quick overview here. Hard drives tend to be fairly dumb devices as far as hardware goes. So, traditionally, when an operating system decides to delete a file, it removes references to that file rather than telling the hard disk that the data should be removed. This is a bit like going to a library and destroying a book's index card without actually removing the physical book from the library. This means that, in some cases, it's possible to get your data back after a file has been deleted by carefully searching through the physical drive. Trying to find the contents of a deleted file is a little like searching through an entire library looking for a book which no longer has an index card.
Treating the hard disk as being dumb has worked fairly well for us up to this point because it means the operating system can keep track of things while the disk simply reads or writes to certain areas without concerning itself with what was there before. To a traditional hard disk, over-writing existing data isn't really any different than writing to a blank part of the disk. But then solid state drives came along and they work a little differently. To an SSD, over-writing data is different (and slower) than simply writing to a blank area of the drive. Much the same way it takes longer for a person to erase a chalk board before writing something new.
The problem is that if the operating system is still treating the SSD as a dumb device, the drive doesn't know which parts of its storage have been used before (and can now be erased). This is where TRIM comes in. It's a way for the operating system to bring the solid state drive up to speed on which blocks aren't in use and can be wiped. This way the SSD can perform house cleaning and we don't run into cases where the drive is trying to wipe data immediately prior to writing.
Now that the Linux kernel has TRIM support, this should all fade into the background, right? Almost. Except in cases where the feature has been backported, only the most recent kernels (2.6.33 and above) have TRIM support. Likewise, I think FreeBSD users will have to wait for FreeBSD 9.0 to get the same feature. Linux users who are on older kernels can get TRIM support via a program called hdparm. The hdparm program (versions 9.17 and up) will search for free blocks in the file system and let the SSD know which areas should be cleaned. If your distribution doesn't supply a recent release of hdparm, you can get a copy from here.
So now we have kernel support and, as a backup, hdparm, so we're covered? Almost. Older SSDs may not support TRIM commands. In those cases, you'll either need to get updated firmware for the SSD or buy a newer drive. When in doubt, check with the manufacturer to see if your device supports TRIM and, if it does not, ask if the device can be upgraded.
slux ha scritto:Ciao Mario,
ho 2 hd wd da 1Tb proprio con questa nuova features dei blocchi a 4kb.Essendo abbastanza ignorante ho semplicemente impostato il jumper dei 2 dischi in modalitÃ legacy, diciamo cosÃ¬, e vado molto bene con le prestazioni.Ho punte di quasi 100Mb/s (hdparm -t ), per quanto puÃ² valere questo test comunque sia.
Una domanda da completo ignorante,ma l'opzione -b di mke2fs o -I(inode size),non aiuta ?
fdisk -H 224 -S 56 /dev/sdX
Trotto@81 ha scritto:Risolve il problema consentendo di installarci anche un bootloader?
Come mai lo usi per archiviazione dati?
Da quello che ho letto in giro Ã¨ proprio sconsigliato per questo tipo di utilizzo.
erio ha scritto:Ã¨ da un po che girano schede pci con vari tagli di storage,l'hard disk tipico andra sicuramente in pensione....ma non per ora,le schede pci tecnologia ssd arrivano a due terabite,sono costose,e credo per un bel pezzo.ma l'integrita dei dati Ã¨ garantita.
8GB 4.38 yrs @50GB write-erase/day
15GB 8.22 yrs @ 50GB write-erase/day
30GB 16.44 yrs @ 50GB write-erase/day
60GB 32.88 yrs @ 50GB write-erase/day
120GB 65.75 yrs @ 50GB write-erase/da
Trotto@81 ha scritto:Si usurano molto in fretta, Ã¨ bene ridurre al minimo le operazioni di lettura e scrittura, la tecnologia sta prendendo piede, ma non Ã¨ affidabile come i classici hdd.
Ecco perchÃ¨ si consiglia di non usarlo come storage, per evitare di minare l'integritÃ dei dati, e se ci pensi bene, che te ne fai della velocitÃ di accesso su un disco storage?
Visitano il forum: Google [Bot] e 2 ospiti