-
Notifications
You must be signed in to change notification settings - Fork 30
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
Updation of number of inode links not persisted #22
Comments
The access control group has had a similar issue with some custom inode params. We've been adding user/group/permission fields to the inode/stat and, although they are processed properly in-memory (e.g. mlfs_object_create) when writing to a new file, these fields revert to zero when we close and reopen the same file later. It seems like these changes aren't being conveyed to the disk during digestion. |
Based on my understanding, it is updated in the cache properly in LibFS, but during digestion, some inode updates (particularly If my understanding is correct, you could attempt to add corresponding updates at the same place where I have added the fix for |
Implementing #21 worked for me, at least for the other fields. Thanks! |
Thanks for the fix. This is now merged. |
Consider the example scenario:
A new filesystem that has only
/mlfs
nlinks
for/mlfs
, it returns 1/mlfs/A
nlinks
again, it returns 2 (from DRAM)nlinks
for/mlfs
it returns 1 (This should be 2)If my understanding is correct we have not persisted it during log digestion.
I attempted a fix for this here: #21
Here's the sample program I used to test it:
create.c
check.c
The text was updated successfully, but these errors were encountered: