hammer2: ls reports "No such file or directory"

[Aleksej Lebedev]

I already did hammer2 destroy on those three directory entries but I still see some errors when I run bulkfree. So I am going to reformat and restore.  Fortunately all of this is happening on a machine that is solely used for backups and its root is also backed up. So I am not loosing any data. Thanks the information.

--
Aleksej Lebedev

On Tue, Oct 13, 2020, at 00:26, Matthew Dillon wrote:
> Theoretically as long as the RAID system properly handles the FLUSH command, it should be ok to run it with a volatile write cache.  But if it just accepts the FLUSH command without flushing the write cache, then bad things can happen.
> 
> That error is a CRC failure.  Sorry, I wasn't clear before.  CHECK FAIL is typically a CRC failure.  The CRCs don't match.  In terms of what you can do... usually its best to backup and reformat.  In this case it looks like a single inode #49686 is messed up.  You can try destroying that inode with 'hammer2 -s <fsroot> destroy-inum 49686', then re-run the bulkfree and see if there are any more issues.
> 
> Generally speaking, if the CHECK FAIL is at an inode you can 'hammer2 destroy-inode ...' the inode and then 'hammer2 destroy ...' any directory entries that were pointing to that inode, but if it is at an indirect block then the filesystem is probably really messed up and the only real choice is to backup, reformat, and restore.
> 
> Those hammer2 directives are extremely dangerous, I recommend making a full backup before messing around any further.
> 
> -Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20201013/5487bbe0/attachment-0002.htm>