Feature #3866
openmds: Add lazily-updated backtraces to hard links
0%
Description
As described in http://www.spinics.net/lists/ceph-devel/msg11872.html, we want hard links to contain lazily-updated backtraces. Add fields and logic so they have a backtrace on creation, and to update it whenever we do a lookup that requires reverting to lookup-by-ino from lookup-by-path.
Updated by Greg Farnum over 11 years ago
- Translation missing: en.field_position set to 27
Updated by Greg Farnum over 11 years ago
- Translation missing: en.field_position deleted (
27) - Translation missing: en.field_position set to 26
Updated by Sage Weil about 11 years ago
- Subject changed from Add lazily-updated backtraces to hard links to mds: Add lazily-updated backtraces to hard links
- Translation missing: en.field_position deleted (
26) - Translation missing: en.field_position set to 25
Updated by Greg Farnum over 10 years ago
If we create a hardline that references the "real" location of the file (as a path), and then the "real" location moves, we would like the hard link to be updated to point to the new location of the file so that we don't need to do a full recursive inode lookup on every access. Doing this as part of the move operation would suck, but it's not that expensive to update it following a lookup (basically the same way we do parent backtrace updates).
Updated by Greg Farnum almost 8 years ago
- Category changed from 47 to Performance/Resource Usage
- Component(FS) MDS added