From: thegeezer <thegeezer@thegeezer.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Tuneing ext4 for reliability (not necessaryly speed)
Date: Fri, 27 Jun 2014 09:53:48 +0100 [thread overview]
Message-ID: <53AD311C.6010401@thegeezer.net> (raw)
In-Reply-To: <20140626161348.GA3886@solfire>
On 06/26/2014 05:13 PM, meino.cramer@gmx.de wrote:
> Hi,
>
> for backup storage (see previous thread) I decided to use ext4. After
> craling the net the reports I found about brtfs seemed to mixed to me.
> If there are alternatives I overlooked...
>
> I searched the net for answeres to the following question, but only
> found outdated answeres...:
>
> What options are recommended to set while initializing the filesystem
> and later via tune2fs to increase the reliability of the filesystem?
>
> Thank you very much in advance for any help! :)
> Best regards,
> mcc
>
>
>
>
>
>
you might want to look up
# tune2fs -o journal_data_ordered
prev parent reply other threads:[~2014-06-27 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 16:13 [gentoo-user] Tuneing ext4 for reliability (not necessaryly speed) meino.cramer
2014-06-26 21:34 ` Alan McKinnon
2014-06-27 8:53 ` thegeezer [this message]
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=53AD311C.6010401@thegeezer.net \
--to=thegeezer@thegeezer.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