Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mkdir problem when unionfs on top (permissions) #8

Closed
diseq opened this issue Dec 9, 2015 · 1 comment
Closed

mkdir problem when unionfs on top (permissions) #8

diseq opened this issue Dec 9, 2015 · 1 comment

Comments

@diseq
Copy link

diseq commented Dec 9, 2015

Hi,

let me first thank you for your great work! I'm very impressed what you achieved. :)
i want to report a small bug when creating directories when unionfs-fuse is layered on top.

without unionfs-fuse:
2015/12/09 21:01:26 Dispatch: MKDIR, NodeId: 1. data: {0775 (02)} names: [test3] 6 bytes

with layered unionfs-fuse:
2015/12/09 21:00:12 Dispatch: MKDIR, NodeId: 1. data: {00 (00)} names: [test2] 6 bytes

and unfortunately, the directory cannot be accessed.
i'm not sure if this is a problem of unionfs-fuse or gocryptfs.

@rfjakob
Copy link
Owner

rfjakob commented Dec 11, 2015

unionfs has an interesting way of creating directories: It first creates it with 000 permissions and afterwards chmods it. That's certainly valid and now supported (commit e99e841).

Edit: link to correct commit

@rfjakob rfjakob closed this as completed Dec 11, 2015
rfjakob added a commit that referenced this issue Dec 11, 2015
This patch also splits off Mkdir and Rmdir into its own file.

Fixes issue #8, thanks to @diseq for the bug report.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants