From: Cork Soaker on
Given that a lot of hardware is now coming with SSDs, and we all know
Windows will wear one of those little buggers out faster than anything
else, is it (already) possible to set options that will only write back
to the disk when it needs to, preferably at shutdown only?

I know there are some options to reduce the amount of writes to a disk,
but how long can a write be avoided?

Related:
http://blog.wired.com/gadgets/2008/06/toshiba-crams-1.html
From: Jim Moe on
On 06/22/08 12:25 pm, Cork Soaker wrote:
> Given that a lot of hardware is now coming with SSDs, and we all know
> Windows will wear one of those little buggers out faster than anything
> else, [...]
>
Really? "Wear out" a solid state device? Perhaps you can expound further
how Windows manages to do such a thing?

--
jmm (hyphen) list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)
From: Robert Heller on
At Sun, 22 Jun 2008 13:46:45 -0700 Jim Moe <jmm-list.AXSPAMGN(a)sohnen-moe.com> wrote:

>
> On 06/22/08 12:25 pm, Cork Soaker wrote:
> > Given that a lot of hardware is now coming with SSDs, and we all know
> > Windows will wear one of those little buggers out faster than anything
> > else, [...]
> >
> Really? "Wear out" a solid state device? Perhaps you can expound further
> how Windows manages to do such a thing?

If the "Solid State Drive" is implemented with an EEPROM, then it is
possible -- EEPROMs have a limited number of re-write cycles.

>

--
Robert Heller -- Get the Deepwoods Software FireFox Toolbar!
Deepwoods Software -- Linux Installation and Administration
http://www.deepsoft.com/ -- Web Hosting, with CGI and Database
heller(a)deepsoft.com -- Contract Programming: C/C++, Tcl/Tk

From: Andrew Halliwell on
Robert Heller <heller(a)deepsoft.com> wrote:
> At Sun, 22 Jun 2008 13:46:45 -0700 Jim Moe <jmm-list.AXSPAMGN(a)sohnen-moe.com> wrote:
>
>>
>> On 06/22/08 12:25 pm, Cork Soaker wrote:
>> > Given that a lot of hardware is now coming with SSDs, and we all know
>> > Windows will wear one of those little buggers out faster than anything
>> > else, [...]
>> >
>> Really? "Wear out" a solid state device? Perhaps you can expound further
>> how Windows manages to do such a thing?
>
> If the "Solid State Drive" is implemented with an EEPROM, then it is
> possible -- EEPROMs have a limited number of re-write cycles.

As do "FLASH" rom. Sometimes as low as 100,000 writes.
Better not make a swap partition or swap file on those things...

--
| spike1(a)freenet.co.uk | "I'm alive!!! I can touch! I can taste! |
| Andrew Halliwell BSc | I can SMELL!!! KRYTEN!!! Unpack Rachel and |
| in | get out the puncture repair kit!" |
| Computer Science | Arnold Judas Rimmer- Red Dwarf |
From: Måns Rullgård on
Andrew Halliwell <spike1(a)ponder.sky.com> writes:

> Robert Heller <heller(a)deepsoft.com> wrote:
>> At Sun, 22 Jun 2008 13:46:45 -0700 Jim Moe <jmm-list.AXSPAMGN(a)sohnen-moe.com> wrote:
>>
>>>
>>> On 06/22/08 12:25 pm, Cork Soaker wrote:
>>> > Given that a lot of hardware is now coming with SSDs, and we all know
>>> > Windows will wear one of those little buggers out faster than anything
>>> > else, [...]
>>> >
>>> Really? "Wear out" a solid state device? Perhaps you can expound further
>>> how Windows manages to do such a thing?
>>
>> If the "Solid State Drive" is implemented with an EEPROM, then it is
>> possible -- EEPROMs have a limited number of re-write cycles.
>
> As do "FLASH" rom. Sometimes as low as 100,000 writes.
> Better not make a swap partition or swap file on those things...

A flash device without a wear-levelling controller will wear out in a
very short time if used with a normal filesystem. Filesystems like
jffs have wear-levelling built in, so they are suitable for such
devices. I would assume that flash-based storage devices intended as
hard drive replacements have suitable controllers.

--
M�ns Rullg�rd
mans(a)mansr.com