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

Problem after recursively deleting content and then trying to add new content #7

Closed
benhj opened this issue Jan 19, 2014 · 1 comment
Labels

Comments

@benhj
Copy link
Owner

benhj commented Jan 19, 2014

Strange behaviour; steps to reproduce --

(i) recursively copy content to a newly created image
(ii) recursively delete it,
(iii) create a new sub folder
(iv) cd into the new sub folder.
(v) attempt to recursively copy content in to the newly created sub folder

Step (v) results in a freeze; subsequently killing the teasafe process and re-mounting the image then appears to be impossible. Suggests that there is a problem with how entries are deleted and subsequently cleared after deleting (inc. metadata) all of which appears to secondarily corrupt the image

@benhj
Copy link
Owner Author

benhj commented Feb 11, 2014

This bug occurred because the 'next' index of each unlinked block was not being reset to the 'current' index. Have introduced code to do the reset in a FileBlock unlink function which is called from the FileEntry unlink function during file unlinking. This apparent fix has actually broken the test 'TeaSafeTest::testThatDeletingEverythingDeallocatesEverything() blocks in use sizes', I'm not sure why. Needs investigating.

@benhj benhj closed this as completed Feb 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant