SplitFS icon indicating copy to clipboard operation
SplitFS copied to clipboard

SplitFS: persistent-memory file system that reduces software overhead (SOSP 2019)

Results 37 SplitFS issues
Sort by recently updated
recently updated
newest added

Bumps zookeeper from 3.4.5 to 3.4.14. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.zookeeper:zookeeper&package-manager=maven&previous-version=3.4.5&new-version=3.4.14)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...

dependencies

There is any posibility to make SplitFS run with linux kernel version 5.7 (for example)? I guess I'll have to compile the right kernel along with the external modules needed...

Currently compiling SplitFS with gcc 10.3.0 results in multiple definition issues. This PR allows multiple definitions of symbols.

There appears to be a bug in rename atomicity in SplitFS. Occurs in the following sequence of operations: 1. Create `file1` 2. Create `file2` 3. rename `file1 -> file2` SplitFS...

The append recovery logic currently depends on inode numbers of the file and the staging file stored in the append log. But the inode number of the file may change...

Bumps hadoop-common from 2.2.0 to 3.2.3. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.hadoop:hadoop-common&package-manager=maven&previous-version=2.2.0&new-version=3.2.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...

dependencies

I am trying to test splitfs in strict mode. ``` export LEDGER_DATAJ=0 export LEDGER_POSIX=1 ``` However, in this mode, splitfs always encounters ``` fio: tbl_mmaps.c:424: clear_overlapping_entry: Assertion `0' failed. ```...

Some issues on checksum calculation 1. Looks like we are calculating the checksum based on the in-memory contents of op log struct [here](https://github.com/utsaslab/SplitFS/blob/f7411b09d22877d914e96a6c763cd7ee1cef8c74/splitfs/log.c#L82). When the `entry_size` value goes beyond the...