This does not seem to be officially documented but makes sense that an overlay on an overlay does not work and is considered an unsupported filesystem as is even NTFS . Some admins/organizations try to use ecyptfs as a simple solution to encrypt the contents of Docker. Instead, you could probably........
Just in case, it is reocmmended to backup the original contents of the directory (especially your home dir) before proceeding.
Setup ecryptfs
Run this command: ecryptfs-setup-private
It will ask you for your login password, this is so that when you login, everything is automatically decrypted by using a passphrase that is wrapped with your login.
You can hit enter and leave things blank for an autogenerated passphrase (for mounting) or you can en........
In a lot of distros like Debian, ecryptfs will mount itself in /home/yourusername/Private
This is controlled by Private.mnt which may contain the mount path like this:
/home/yourusername/Private
Change the default mount location of ecryptfs by modifying this file:
home/.ecryptfs/yourusername/.ecryptfs/Private.mnt
After you unmount and relogin, you should find ecryptfs is now mo........
In this scenario, let's say you want to clone your OS at the filesystem level and the source system (the system you want to clone from) is in use.
Doing a blind rsync / is a big problem because it uses twice as much space for no reason.
The reason for this is that with ecryptfs you have a /home/.ecryptfs directory which has the actual encrypted versions of your files and folders. However your home directory (eg. /home/someuser) is mounted.
Doing the blind rsync will ca........
You can search for this bug and it seems like it may be related to ecryptfs and is many years old.
The symptoms are that you return to the computer and the screensaver was active or the screen was asleep/black and it doesn't seem to come back. But you check by SSH the computer is running fine and are frustrated you'll lose your running programs and have to reboot.
There is a simple solution:
Ctrl + Alt + F1
Ctrl +Alt + F8
Ba........
The easiest way to recover or mount an off-line ecryptfs directory is the built-in command from ecryptfs
sudo ecryptfs-recover-private It will find your wrapped passphrase and ask for your password and mount it in tmp. Much easier especially when your current active OS is using ecryptfs too.
This a fantastic tool when going through old backups.........
ecryptfs-mount-private
Enter your login passphrase:
Inserted auth tok with sig [ee16d84] "into the user session keyring
mount: No such file or directory"
[ 156.118113] ecryptfs_mount: kern_path() failed
[ 156.118431] Reading sb failed; rc = [-2]
[ 164.233055] traps: mate-notificati[3472] trap int3 ip:7f43d7002c13 sp:7fff162c6600 error:0
[ 166.017061] ecryptfs_mount: kern_path() failed........
1.) Replicate the number of partitions in your new drives.
gdisk /dev/sda
gdisk /dev/sdb
I created 3 partitions of the same same size.
partition #1: +1G (/boot)
partition #2: +60G (swap)
partition #3: rest of it (/)
#note if you are using GPT/gdisk you need to create separate a partition at least 1MB in size (in my case I would a 4th partition and mark it type ef02).........
I'm using ecryptfs and was suddenly unable to access or even ls my home directory (but every subfolder is accessible). It just hangs and throws this message in messages/dmesg:
Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
I read somewhere that perhaps some file or folder is owned by root somehow, sure enough there are some and sudoing to root allows me to........
It seems nearly anything can make rhythmbox crash, I've always found it buggy.
This crash seems to be something related to ecryptfs but it's hard to say. After re-opening rhythmbox so it sits in the Gnome panel/tray, and letting it load/find all of my songs let's it work again. If I show it too soon (I wait 10-15 minutes for everything to scan first) then it will crash over and over.
[171938.995645] ecryptfs_read_and_validate_header_region: Error........