Zach Brown 434cbb9c78 scoutfs: create dirty items for inode updates ...

Inode updates weren't persistent because they were being stored in clean
segments in memory.  This was triggered by the new hashed dirent
mechanism returning -ENOENT when the inode still had a 0 max dirent hash
nr.

We make sure that there is a dirty item in the dirty segment at the
start of inode modification so that later updates will store in the
dirty segment.  Nothing ensures that the dirty segment won't be written
out today but that will be added soon.

Signed-off-by: Zach Brown <zab@versity.com>

2016-03-25 10:08:34 -07:00

..

src

scoutfs: create dirty items for inode updates

2016-03-25 10:08:34 -07:00

.gitignore

Initial commit

2016-02-05 14:12:14 -08:00

Makefile

scoutfs: require sparse builds

2016-03-24 21:45:08 -07:00