On 11/12/2018 15:48, Martin Gregorie wrote:
> On Tue, 11 Dec 2018 15:18:34 +0100, Newdo wrote:
>
>> thanks for the hint, works great with my collection.
>>
> Good to hear that.
>
>> The next (hopefully last) problem is the steady access to the disk
>> drive.
>>
>> I am using an SSD drive which is permenently written to. (journalling?)
>>
>> The collection stays most of the time unchanged so there is no need to
>> write anything to disk as long as the library stays the same.
>>
> I have a single drive in my server (Dual Athlon, 4GB RAM, running Fedora
> 28 x64) with a single 500 GB HDD installed. This works well despite the
> PC being a bit long on the tooth. I've had it 10 years and according the
> smartd its original disk had 9,000 hours when I bought the PC. That disk,
> IIRC a Hitachi 3.5" 250GB unit, died at 47,000 hours at the beginning of
> last year. Its replacement is currently at 15,000 hours and is a WD Blue
> 3.5" 500GB drive, i.e. consumer grade with a MTBF of around 50,000 hours.
>
> I slipped up there: since I run the server 24x7 I should have bought a WD
> Red 3.5". The spec for this has an MTBF of 1,000,000 hours, twice the
> number of start/stop cycles of the Blue (600,000 vs 300,000) and a 3yr
> rather than a 2yr guarantee. Its not hugely more expensive either: £56.45
> against £38.22 for 1GB drives from eBuyer.
>
>
The fact that the server is up 24x7 is not so significant as the disk
being hammered 24x7 with multiple reads writes and seeks.

A friend used to blow disks doing continuous access in under a year -
8000 hours

I get about 40,000 hours our of my server disks.


--
Religion is regarded by the common people as true, by the wise as
foolish, and by the rulers as useful.

(Seneca the Younger, 65 AD)

--- SoupGate-Win32 v1.05