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

After an ungraceful unmount, mount shall cleanup temp-cache only if flag is set #1613

Merged
merged 1 commit into from
Jan 20, 2025

Conversation

vibhansa-msft
Copy link
Member

✅ What

File-cache as a flag cleanup-on-start. After an ungraceful unmount, next mount shall wipeout the cache only if this flag is set otherwise cache shall be reused.

🤔 Why

Flag is checked incorrectly and it wipes out cache even when flag is set to false.

👩‍🔬 How to validate if applicable

Mount, read a file, crash, restart and the tempcache shall not cleanup on mount,

🔖 Related links

NA

@vibhansa-msft vibhansa-msft added this to the v2-2.4.1 milestone Jan 20, 2025
@vibhansa-msft vibhansa-msft changed the base branch from main to blobfuse/2.4.1 January 20, 2025 07:26
@vibhansa-msft vibhansa-msft merged commit 76b69ad into blobfuse/2.4.1 Jan 20, 2025
5 checks passed
@vibhansa-msft vibhansa-msft deleted the vibhansa/clearnupstart branch January 20, 2025 10:15
vibhansa-msft added a commit that referenced this pull request Feb 3, 2025
* feat: support workload identity token (#1556)

* feat: support workload identity token

* Create block pool only once in child process (#1581)

* create block pool in child only

* Update golang.org/x/crypto to v0.31.0 (#1594)

* Update golang.org/x/crypto to v0.31.0

* sync with main (#1603)

* updated year in copyright message (#1601)

* Use ListBlob for hns accounts  (#1555)

* Optimize HNS listing

* Added statfs for block-cache (#1470)

* Added statfs for block_cache

* Add strong consistency check for data on disk (#1604)

* Add strong consistency check for data on disk

* bug in block cache open call (#1580)

* current implementation of open file when opened in O_WRONLY will truncate the file to zero. This is incorrect behaviour.
We don't see it in the normal scenario as write-back cache is on by default. Hence all the open calls with O_WRONLY will be redirected O_RDWR.
To simulate this turn of the write-back cache and then open file in O_WRONLY.

* Feature: Blob filter (#1595)

* Integrating blob filter in azstorage

* Serve getAttr call for destination file after the Copy finishes from the cache

* Cleanup on start shall be set to cleanup temp cache (#1613)

* Add Tests

* Refactor the code and refresh the cache after copying the attributes

* Automate blobfuse2 setup for new VM (#1575)

added script for blobfuse setup and azsecpack setup in VM

* * Update the Unit tests.
* Refactor the Code

* Update Changelog

* do go fmt on src

* Downgrade go version to 1.22.7 due to memory issues in 1.23 (#1619)

* Enable ETAG based validation on every block download to provide higher consistency (#1608)

* Make etag validation a defualt option

* BUG#31069208:  Fixed Prefix filtering from File Path (#1618)

* Fixed the logic to filter out folder prefix from path
* Added/Updated/Removed test case

---------

Co-authored-by: weizhi <weizhichen@microsoft.com>
Co-authored-by: Sourav Gupta <98318303+souravgupta-msft@users.noreply.github.com>
Co-authored-by: Jan Jagusch <77677602+JanJaguschQC@users.noreply.github.com>
Co-authored-by: ashruti-msft <137055338+ashruti-msft@users.noreply.github.com>
Co-authored-by: syeleti-msft <syeleti@microsoft.com>
Co-authored-by: jainakanksha-msft <jainakanksha@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants