TheArchive/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2025-08-27 09:50:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #4255 from greatroar/fuse-hash

Browse Source 
fuse: Mix inode hashes in a non-symmetric way
This commit is contained in:
Michael Eischer
2023-04-07 12:56:57 +02:00
committed by GitHub
parent 7896e50301 a0885d5d69
commit 26a3c47c5c
3 changed files with 33 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
changelog/unreleased/issue-4253 Normal file
View File

@@ -0,0 +1,18 @@
Bugfix: Mount command should no longer create spurious filesystem loops
When a backup contains a directory that has the same name as its parent,
say, a/b/b, and the GNU find command were run on this backup in a restic
mount, find command would refuse to traverse the lowest "b" directory,
instead printing "File system loop detected". This is due to the way the
restic mount command generates inode numbers for directories in the mount
point.
The rule for generating these inode numbers was changed in 0.15.0. It has
now been changed again to avoid this issue. A perfect rule does not exist,
but the probability of this behavior occurring is now extremely small.
When it does occur, the mount point is not broken, and scripts that traverse
the mount point should work as long as they don't rely on inode numbers for
detecting filesystem loops.
https://github.com/restic/restic/issues/4253
https://github.com/restic/restic/pull/4255