> On a FFSv2/WAPBL file system successfully fsck -f'd less than two hours > before, I got a "bad dir: mangled entry" panic. > I fsck'd again, finding missing dot/dotdot entries [...] > Just within minutes after going live again, I experienced the same panic, > and fsck found missing dot/dotdot in exactly the same directory. Would a mis-behaving NFS client be able to unlink dot or dotdot?
- Re: panic: bad dir: mangled entry, fsck: missing dot/dotd... Edgar Fuß
