Open TheDiscordian opened 2 years ago
So I've completely broken my MFS I guess, but I have no idea how to repair it. Running ipfs-sync normally until I got the typical FileStore issue where it's complaining that a file doesn't exist. I'd put the file there, removed it, removed it from MFS, removed the blocks, tried everything. Now I have a directory where if I perform ipfs files ls
on it, I can't perform anything else afterwards because go-ipfs is totally locked up.
Anyone following this repo note, this bug shouldn't be present in 0.7.0. This bug should only be in master. I suspect it has something to do with #38.
Steps:
Attempted fix:
ipfs block rm <cid>
(this is what caused the locking up issues, before this, I just got the "no such file/dir" error)filestore verify
After all these steps, I've had no improvement, I'm unsure how to debug further.
Note: I can't even stat the bad directory. The entry still exists in MFS, but interacting with it in any way causes go-ipfs to lock up.
What happens when you try to remove it via ipfs files rm -f /path/to/thing
? (note -f
)
@lidel thanks for the response, sorry for my slow one! Like everything else I try on it, it just hangs indefinitely.
This needs to be isolated and filed upstream.