Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was looking at dm-crypt and have seen that you can use whatever filesystem you like on top of the encrypted drive. So I was wondering if a journaled filesystem is a good idea as opposed to a non-journaled one. Also, what filesystem would be best to deal with power failures with an encrypted drive?

share|improve this question
I've had quite a few issues where my dm-encrypted drives have lost power and/or there was an issue requiring me to hard reboot suddenly. After luksOpen you just run fsck as if – LawrenceC May 18 '11 at 11:07
up vote 11 down vote accepted

Journaling is a technique that helps with recovery from problems that occur when multi-write operations are interrupted. Such interruptions can leave the file system in an inconsistent state between writes.

Interruptions can happen with "normal" block devices and dm-crypt block devices alike. For a file system, a block device is a block device. Block device encryption and file system journaling are completely separate concerns.

share|improve this answer

Journaling is orthogonal to encryption. You would run an encrypted device to protect your files private, and you would use a journaling FS to protect the integrity of the data. Given the advancements over the last decade in Linux-based journaling systems, there's really no reason not to use one, except for possibly special scenarios like embedded systems or specially tuned database environments.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.