I have a one-partition setup and my whole home folder is encrypted. I did a fsck and that didn't help. I removed zero-size files from ~/.Private and that didn't help. I backed data, deleted user and its home folder, created user again and copied data back, and error was still there.
Booting to previous kernel 3.2.0-29 solved the issue. This is why I consider this bug a regression.
Now I know there's a bug #870326 which is pretty much identical to this. I couldn't find "reopen" button however and I don't know how you guys like to track regressions in launchpad. I'm sorry for creating a duplicate. Please advise me what to do? If I just add new comment to the resolved bug, won't it get lost?
After upgrading to 3.2.0-30 I started seeing error messages like this in my syslog:
Sep 7 11:56:28 artemy-tregubenko kernel: [ 318.675991] ecryptfs_ encrypt_ page: Error attempting to write lower page; rc = [-5] 0000]) encrypt_ page: Error attempting to write lower page; rc = [-5] 0001]) encrypt_ page: Error attempting to write lower page; rc = [-5] 0000]) encrypt_ page: Error attempting to write lower page; rc = [-5] 0001])
Sep 7 11:56:28 artemy-tregubenko kernel: [ 318.675997] ecryptfs_writepage: Error encrypting page (upper index [0x000000000000
Sep 7 11:56:28 artemy-tregubenko kernel: [ 318.676058] ecryptfs_
Sep 7 11:56:28 artemy-tregubenko kernel: [ 318.676061] ecryptfs_writepage: Error encrypting page (upper index [0x000000000000
Sep 7 11:56:28 artemy-tregubenko kernel: [ 318.676119] ecryptfs_
Sep 7 11:56:28 artemy-tregubenko kernel: [ 318.676122] ecryptfs_writepage: Error encrypting page (upper index [0x000000000000
Sep 7 11:56:28 artemy-tregubenko kernel: [ 318.676179] ecryptfs_
Sep 7 11:56:28 artemy-tregubenko kernel: [ 318.676182] ecryptfs_writepage: Error encrypting page (upper index [0x000000000000
I have a one-partition setup and my whole home folder is encrypted. I did a fsck and that didn't help. I removed zero-size files from ~/.Private and that didn't help. I backed data, deleted user and its home folder, created user again and copied data back, and error was still there.
Booting to previous kernel 3.2.0-29 solved the issue. This is why I consider this bug a regression.
Now I know there's a bug #870326 which is pretty much identical to this. I couldn't find "reopen" button however and I don't know how you guys like to track regressions in launchpad. I'm sorry for creating a duplicate. Please advise me what to do? If I just add new comment to the resolved bug, won't it get lost?
ProblemType: Bug ature: Ubuntu 3.2.0-30.48-generic 3.2.27 dules: nvidia
DistroRelease: Ubuntu 12.04
Package: ecryptfs-utils 96-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-30-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Fri Sep 7 11:56:48 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
SourcePackage: ecryptfs-utils
UpgradeStatus: Upgraded to precise on 2012-08-11 (26 days ago)