linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Miguel González Castaños" <mgc@tid.es>
To: Agus Budy Wuysang <fswmis@fasw.co.id>
Cc: linux-admin@vger.kernel.org
Subject: Storage systems
Date: Wed, 20 Nov 2002 15:20:58 +0100	[thread overview]
Message-ID: <3DDB9A4A.92A12D62@tid.es> (raw)
In-Reply-To: 3DDB50B1.2080709@fasw.co.id

Dear all,

 I am addressing to you guys, to see if you could give some ideas...

 We are dessigning a system where we will need to store loads of tiff format image
files. We havent estimated yet which will be the amount of the image files that
there will be around 40-60 Gb/ a year. The problem is that those images should be
always accesible, we have thought about to create a database system to retrieve
those images and that way to develop a kind of image file server for the rest of
applications that need to get those image files.

 The environment is using linux and systems of low cost. We presumably would use
IDE hard disk drives.

 We have consider several ways to achieve it, clustering, etc...but,  After
considering using volume striping with LVM, the problem that we envisaged is that
such image file server would be working lot of hours, that means that IDE hard
disk drives after a few years could start to have disk failures (I think they are
meant to be use around 3-5 years)...

 Then we started to think about a massive storage system for small systems...but
that choice could be a bit expensive...

 I suppose you guys maybe you should have faced the deployment of such system. We
only are thinking about other possibilites we havent taken into account.

 If massive storage systems are our solution, we would like to know which
possibilities I could found for Linux (red hat if possible).

 Sorry for the lenght of my email.

 Many thanks

 Miguel








  reply	other threads:[~2002-11-20 14:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18  8:01 difference btw CGI and HTML scripts simon Shaw
2002-11-18 16:42 ` Tyler
2002-11-19 17:09   ` Geoff Torres
2002-11-19 20:34     ` Linux Backups Ed Walsh
2002-11-19 20:46       ` Marshall Lake
2002-11-19 20:51       ` terry white
     [not found]       ` <3DD9414B0000536D@vader.se.ilan.cogent.net>
2002-11-19 21:09         ` Ed Walsh
2002-11-19 21:55       ` Milan P. Stanic
2002-11-20  9:06       ` Agus Budy Wuysang
2002-11-20 14:20         ` Miguel González Castaños [this message]
2002-12-10 16:19         ` terminal problems with escape characters Miguel González Castaños
2002-12-11  1:04           ` dashielljt
2002-12-11  8:54             ` Miguel González Castaños
2002-12-12  1:11               ` dashielljt
2002-11-20 13:36       ` Linux Backups djh
2002-11-20  2:43     ` difference btw CGI and HTML scripts Michael Luevane
2002-11-18 18:18 ` - Luis -
2002-11-19 20:43 ` terry white

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DDB9A4A.92A12D62@tid.es \
    --to=mgc@tid.es \
    --cc=fswmis@fasw.co.id \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).