public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marc Stürmer" <mail@marc-stuermer.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Good/better/best filesystem for large, static video library?
Date: Tue, 25 Dec 2012 21:09:00 +0100	[thread overview]
Message-ID: <CAN+qToCKstXG47B3bcPQdsk_-mxTvRs=PqX7EsK-8EVqVd3aYw@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+ed5cP77s=ciCC8a+5MCB3DDay_c5hNfTdk5VxfhL4Sozg@mail.gmail.com>

2012/12/25 Mark Knecht <markknecht@gmail.com>:

>    Upgrading an external USB2 drive at home this Christmas morning to
> 1TB for more video storage space. One large partition, non-raid, files
> are around 1GB. The drive holds only static video files that get
> written once and don't change or get erased. No MythTV stuff or
> anything like that.
>
>    This disk reside on my main desktop machine and gets backed up
> every couple of days to another USB2 drive (FAT formatted
> unfortunately) which attaches to the TV.

Well in your usage case ext3 is still well suited enough.

Ext4 though is the superior filesystem, since it is more advanced in
technical terms. Maximum file system size in ext3 is around 16
Terabyte, something not so far ahead now even more in homes. Ext4 has
the maximum file system size of 1024 Petabyte.

ext4 also uses extents, which ext3 has not - meaning file system
checks are able to run faster. Erasing big files on ext4 works
therefore faster than on ext3. It also tends to fragment less than
ext3.

ext4 has persistent preallocation when writing large files, meaning
space is being guaranteed and most probably contiguous.

tl;dr: ext3 should be well suited enough for your computer, but if you
can reformat your hard disk drive, using ext4 will not hurt either and
you gain some faster speed.


  parent reply	other threads:[~2012-12-25 20:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-25 15:41 [gentoo-user] Good/better/best filesystem for large, static video library? Mark Knecht
2012-12-25 16:33 ` Pandu Poluan
2012-12-25 17:07   ` Mark Knecht
2012-12-25 17:18     ` Michael Orlitzky
2012-12-25 17:56       ` Dale
2012-12-25 18:26       ` Mark Knecht
2012-12-25 18:58         ` Florian Philipp
2012-12-25 16:46 ` Florian Philipp
2012-12-25 17:15   ` Dale
2012-12-25 19:04     ` Florian Philipp
2012-12-25 19:45       ` Dale
2012-12-25 20:09 ` Marc Stürmer [this message]
2012-12-27  0:18 ` Alan McKinnon
2012-12-27 10:01   ` Stefan G. Weichinger
2012-12-27 13:57   ` Michael Hampicke
2012-12-27 22:48     ` Alan McKinnon
2013-01-02 13:04   ` Neil Bothwick
2013-01-02 13:38     ` Alan McKinnon
2013-01-02 14:08       ` Volker Armin Hemmann
2013-01-02 14:39         ` Neil Bothwick
2012-12-27  0:44 ` Alecks Gates

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='CAN+qToCKstXG47B3bcPQdsk_-mxTvRs=PqX7EsK-8EVqVd3aYw@mail.gmail.com' \
    --to=mail@marc-stuermer.de \
    --cc=gentoo-user@lists.gentoo.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