From: Martin Steigerwald <ms@teamix.de>
To: ecryptfs@vger.kernel.org
Subject: ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-13]
Date: Mon, 19 Dec 2011 13:26:19 +0100 [thread overview]
Message-ID: <201112191326.20172.ms@teamix.de> (raw)
Hi!
Today I tested again whether ecryptfs would be suitable to replace encfs on my
laptop. But I found several problems. The blocking one is:
ms@merkaba:~/Training/TXS-svn/Linux_15_Performance_Tuning#2> LANG=C make
[…]
sed: couldn't open temporary file ./sedhqlAcd: Permission denied
[…]
ms@merkaba:~/Training/TXS-svn/Linux_15_Performance_Tuning> LANG=C ls -l | tail
-6
ls: cannot access sedhqlAcd: No such file or directory
ls: cannot access sedChky0a: No such file or directory
ls: cannot access sed1eW8Ek: No such file or directory
ls: cannot access sedEjR2oA: No such file or directory
ls: cannot access sedb4JEiI: No such file or directory
ls: cannot access sedy0KQnt: No such file or directory
-????????? ? ? ? ? ? sedChky0a
-????????? ? ? ? ? ? sedEjR2oA
---------- 1 ms teamix 1143445 Dec 5 10:01 sedNL1bTk
-????????? ? ? ? ? ? sedb4JEiI
-????????? ? ? ? ? ? sedhqlAcd
-????????? ? ? ? ? ? sedy0KQnt
Output in dmesg is:
ms@merkaba:~/Training/TXS-svn/Linux_15_Performance_Tuning> sudo tail -2
/var/log/syslog
Dec 19 13:23:30 merkaba kernel: [50999.570071] ecryptfs_write_metadata: Error
writing metadata out to lower file; rc = [-13]
Dec 19 13:23:30 merkaba kernel: [50999.570083] Error writing headers; rc =
[-13]
Ecryptfs is configured as follows:
merkaba:~> cat .ecryptfsrc
ecryptfs_unlink_sigs
ecryptfs_sig=[…]
ecryptfs_fnek_sig=[…]
ecryptfs_xattr
ecryptfs_key_bytes=32
ecryptfs_cipher=aes
ecryptfs_passthrough=n
I am using extended attributes to avoid the space waste of 8 KiB per file.
The underlying filesystem is:
merkaba:~> grep /home /proc/mounts
/dev/mapper/merkaba-home /home ext4
rw,noatime,user_xattr,acl,barrier=1,stripe=128,data=ordered 0 0
/home/.ms /home/ms ecryptfs
rw,relatime,ecryptfs_fnek_sig=[…],ecryptfs_sig=[…],ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_xattr_metadata,ecryptfs_unlink_sigs
0 0
Kernel is:
ms@merkaba:~> cat /proc/version
Linux version 3.2.0-rc4-amd64 (Debian 3.2~rc4-1~experimental.1)
(ben@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-5) ) #1 SMP Sun Dec 4
18:38:24 UTC 2011
With encfs or from my local workstation via NFS there is no such issue.
Ciao,
--
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90
next reply other threads:[~2011-12-19 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 12:26 Martin Steigerwald [this message]
2011-12-20 1:06 ` ecryptfs_write_metadata: Error writing metadata out to lower file; rc = [-13] Tyler Hicks
2011-12-20 8:46 ` Martin Steigerwald
2011-12-20 9:45 ` Martin Steigerwald
2011-12-20 12:05 ` Alexis Hafner
2011-12-20 12:27 ` Martin Steigerwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201112191326.20172.ms@teamix.de \
--to=ms@teamix.de \
--cc=ecryptfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox