From: Matthias Bodenbinder <matthias@bodenbinder.de>
To: ecryptfs@vger.kernel.org
Subject: bad file permissions: write but no read access
Date: Fri, 01 Oct 2021 13:04:58 +0200 [thread overview]
Message-ID: <e0af3fe10229d90357dd351b4348ec6af59f2e3f.camel@bodenbinder.de> (raw)
Hi,
I hundreds of files in my ecryptfs home which I can write (e.g. rename them) but I can not read them resp. open them. A chmod as
user or even as root is not working.
Example:
34# file wencke-18te.xcf
wencke-18te.xcf: writable, regular file, no read permission
35# ll wencke-18te.xcf
.rw-r--r-- matthias matthias 41 MB Thu Aug 3 16:00:46 2017 wencke-18te.xcf
36# getfacl wencke-18te.xcf
# file: wencke-18te.xcf
# owner: matthias
# group: matthias
user::rw-
group::r--
other::r--
37# chmod 644 wencke-18te.xcf
chmod: changing permissions of 'wencke-18te.xcf': Input/output error
The underlying ecryptfs directory /home/.ecryptfs/matthias/ with .Private and .ecryptfs subdirectories is readable without error.
I can rsync it to my backup server. But when I mount it from the backup server with ecryptfs-recover-private I have the same
issue.
What can I do to fix that and make the files readable again?
Matthias
next reply other threads:[~2021-10-01 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 11:04 Matthias Bodenbinder [this message]
2021-10-01 15:11 ` bad file permissions: write but no read access Matthias Bodenbinder
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=e0af3fe10229d90357dd351b4348ec6af59f2e3f.camel@bodenbinder.de \
--to=matthias@bodenbinder.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).