-
Notifications
You must be signed in to change notification settings - Fork 0
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
Make setattr silently fail on remote inodes #3
Conversation
This commit changes the setattr behavior so that if an inode is remote, the operation is a no-op. This means that programs like `wget` that used to fail on our s3 mounts will now succeed, but some of their operations will not do anything.
I have tested that this fixes our
|
if sync.write_status == WriteStatus::Remote { | ||
return Err(InodeError::SetAttrNotPermittedOnRemoteInode(inode.err())); | ||
let stat = sync.stat.clone(); | ||
drop(sync); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this drop
needed to address a compiler complaint? It gets dropped when this setattr
returns doesn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it's for the compiler. Not sure how else to handle it.
This commit changes the setattr behavior so that if an inode is remote, the operation is a no-op. This means that programs like
wget
that used to fail on our s3 mounts will now succeed, but some of their operations will not do anything.