Kent Overstreet - 31.05.25, 01:16:04 CEST: > > I have a directory entry that according to ls -l is quite big: > > > > drwxrwxr-x 5 martin martin 18446744073709551400 DATE DIRECTORY > > Yes, this is due to a leftover from the directory i_size patchset that > had to be reverted. As long as it's not causing issues it'll be a bit > before I get to it, I've got higher priority bugs I'm working on right > now (as usual).
On 6.15.2. How can I trigger repair code from commit bcachefs: Repair code for directory i_size 66c36452163871360f15dc4042dd00612e42cd66 ? Currently still has that odd size. I tried "bcachefs fsck -k" so far, but so far only while filesystem is mounted, as after I dismount it I get back the device node from LVM would be busy. But I see no indication as to why. If fsck in dismounted state would do the trick I can try disabling automatic mount on boot. Again no priority. I do not use SSHFS on that filesystem. I suppose I could just create a new directory and move over the files from the one with the odd size. However, keeping as is for now. Maybe I can help testing repair code. :) Best, -- Martin
