From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Good/better/best filesystem for large, static video library?
Date: Tue, 25 Dec 2012 20:04:52 +0100 [thread overview]
Message-ID: <50D9F8D4.10000@binarywings.net> (raw)
In-Reply-To: <50D9DF30.1090609@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2074 bytes --]
Am 25.12.2012 18:15, schrieb Dale:
> Florian Philipp wrote:
>> Am 25.12.2012 16:41, schrieb Mark Knecht:
>>> Hi,
>>> Merry Christmas to all.
>>>
>>> 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.
>>>
>>> With the previous local drive I used ext3 and have had no problems.
>>> I'm just wondering if there's a better choice & why.
>>>
>>> Cheers,
>>> Mark
>>>
>> Ext4 offers better performance for large files. This is especially
>> notable when you remove them but other operations are faster, too. XFS
>> would be the traditional large-file choice but since the arrival of
>> Ext4, I don't see a point in putting up with its quirks anymore.
>>
>> Regards,
>> Florian Philipp
>>
>
>
> For those who keep up with my adventures, I use ext4 for my home
> directory which has a LOT of videos. Some videos are small and some are
> large but I can say this, it is really fast. No fragmentation either.
>
> I also use ext4 for my backup drive. I accidentally deleted some stuff
> one day and I can say this, it is VERY fast. I'm just glad it was only
> a backup.
>
> I would second the idea for ext4. It works great for me.
>
> Dale
>
On an amusing side note: I once was very happy that I happened to be
running ext3 at work. I accidentally started `rm -rf ~/*` and after more
than a minute I wondered why my disk was so busy ...
Anyway, thanks to its slow speed, rm only had time to eat away my rather
unimportant "archive" and "bin" directories and hasn't reached "doc"
yet. Thankfully bash sorts its glob expansions alphabetically. :D
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-12-25 19:06 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 [this message]
2012-12-25 19:45 ` Dale
2012-12-25 20:09 ` Marc Stürmer
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=50D9F8D4.10000@binarywings.net \
--to=lists@binarywings.net \
--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