https://bugzilla.kernel.org/show_bug.cgi?id=209005 --- Comment #3 from Eric Sandeen (sandeen@xxxxxxxxxx) --- IOWs this looks like more than just a missing "\n" - setting the first character of a directory entry to "/" is an internal flag for certain entries which is normally handled in a specific way. But it doesn't look like your filenames are overwritten; it looks like they actually started with "/" prior to repair? So it may not be handling this flagging properly when the leading "/" came from elsewhere... a metadump would be helpful. -- You are receiving this mail because: You are watching the assignee of the bug.
