At 05:14 PM 11/3/2012, Jeff Roberson wrote:
The journal entries are 32 bytes per in SUJ. So the number of
extra writes is down in the noise. The journaling also gets you
asynchronous partial truncation and a few other asynchronous
operations that are sync in SU. It does cost slightly more cpu
time and more memory. I'm not saying you're making the wrong
choice. I'm just saying that it's not clear that you should or
should not use it with SSDs.
This is what I would expect, and with wear leveling it is unlikely
that the wear on the SSD would be significant anyway. In my case,
the most important thing is not to lose logs in a crash (which
could happen with just fsck), so journaling is worth it for me.
The only reason I could see not to use SU+J with SSDs (or any disk,
for that matter) is if there are bugs which harm stability. A look at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&severity=&priority=&class=&state=open&sort=none&text=&responsible=&multitext=&originator=&release=
shows several open PRs mentioning panics, corruption, and reboots.
Are they still open because problems exist? Or have the committers
simply neglected to close them?
--Brett Glass
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
