Date: Fri, 23 Oct 2015 14:24:03 -0500 From: Brandon J. Wandersee <brandon.wandersee@gmail.com> To: Julien Cigar <jcigar@ulb.ac.be> Cc: Adam Vande More <amvandemore@gmail.com>, FreeBSD Questions <freebsd-questions@freebsd.org>, krad <kraduk@gmail.com> Subject: Re: gjournal and TRIM: A safe combination? Message-ID: <86bnbpjsmk.fsf@WorkBox.Home> In-Reply-To: <20151022131510.GY87605@mordor.lan> References: <867fmh12nq.fsf@WorkBox.Home> <CALfReyfg-71nCg4K0dKmUK-YmZ8yi0ppeGGv4WOD-2Mt8NP9HQ@mail.gmail.com> <86pp081glq.fsf@WorkBox.Home> <CA%2BtpaK0ezoi7wBBD9VZwREq9Qp0YaJNfJY42=tZAYi5VSL8rCA@mail.gmail.com> <20151021143525.GX87605@mordor.lan> <86lhaw107r.fsf@WorkBox.Home> <20151022131510.GY87605@mordor.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Julien Cigar writes:
> This is where gjournal (and data=journal on EXT-like FS) comes in as
> datas and metadatas are written in the journal _before_, so you avoid
> corruption and data loss.
This was my rationale when opting for gjournal. I figured the extra
layer of journaling rather than soft updates alone might be worthwhile,
but if it's not intended for use on an SSD, not necessarily better than
soft updates alone, and overkill on an old laptop, then I'll just do
without it. Thanks for the input, folks. Take care.
--
=================================================================
:: Brandon Wandersee ::
:: brandon.wandersee@gmail.com ::
==================================================================
'A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.'
- Douglas Adams
==================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86bnbpjsmk.fsf>