From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Good/better/best filesystem for large, static video library?
Date: Tue, 25 Dec 2012 10:26:20 -0800 [thread overview]
Message-ID: <CAK2H+efOdGN8bMXKaj4z1e1HxodtNY9UUrMBmuXvD9yxsTW1aQ@mail.gmail.com> (raw)
In-Reply-To: <50D9DFE4.3020009@orlitzky.com>
On Tue, Dec 25, 2012 at 9:18 AM, Michael Orlitzky <michael@orlitzky.com> wrote:
> On 12/25/2012 12:07 PM, Mark Knecht wrote:
>> On Tue, Dec 25, 2012 at 8:33 AM, Pandu Poluan <pandu@poluan.info> wrote:
>>>
>>> On Dec 25, 2012 10:44 PM, "Mark Knecht" <markknecht@gmail.com> wrote:
>> <SNIP>
>>>> With the previous local drive I used ext3 and have had no problems.
>>>> I'm just wondering if there's a better choice & why.
>> <SNIP>
>>>
>>> For your usage, I think ext3 is the most suitable.
>>>
>>> Do you have another fs in mind?
>>
>> Really, no. ext3 has been fine. I didn't see any real advantage to
>> ext4 myself. Florian offers the removal argument but I've never
>> removed files from this database. It's just movies so the systems just
>> grows over time.
>>
>> I suppose I wondered whether some other filesystem might get through
>> an fsck _much_ faster.
>>
>
> There's really no reason to use ext3 over ext4. Ext4 does have a faster
> fsck.
>
>
If the graph here
http://kerneltrap.org/Linux/Improving_fsck_Speeds_in_Ext4
represents real speed improvement then it's likely worth it to me. The
drive is doubling in size but initially the data isn't. (500GB getting
rsync'ed to 1TB)
As I have no immediate needs for the older drive I will give ext4 a
try and just hang on to the old drive&data for a few months and see
how it goes. I'd do that anyway in case the new drive has an infant
mortality issue show up, but really the backup is the 1TB on the TV
which is stable and in use for over a year with no smartctl issues.
(yet) However that drive is FAT formatted so I don't really want to
depend on it for anything long term.
I wonder if there's anything to be said for changing block sizes, etc.
away from whatever the defaults are? All of the files are currently
between 350MB & 1.2GB so there's never going to be many more than 2K
files on the drive and I'm assuming the rsync operation if file by
file so fragmentation in the beginning, and probably over time, is
going to be pretty low I think.
Thanks for the info.
Cheers,
Mark
next prev parent reply other threads:[~2012-12-25 18:27 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 [this message]
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
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=CAK2H+efOdGN8bMXKaj4z1e1HxodtNY9UUrMBmuXvD9yxsTW1aQ@mail.gmail.com \
--to=markknecht@gmail.com \
--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