I had a rather large ext4 partition on an Areca RAID shut down uncleanly while it was writing. When I mount it again, it recommends fsck, which I do, and I get the following error: Failed to optimize directory ... EXT2 directory corrupted This error shows up every time I run fsck.ext4 on this partition. How can I fix this? The file system seems to work ok otherwise, I can mount it and it doesn't complain, using it looks like it's ok, etc. -- Joakim Ziegler - Supervisor de postproducci?n - Terminal joakim at terminalmx.com - 044 55 2971 8514 - 5264 0864
Anyone have an idea about this? It keeps complaining every time I mount the file system. -- Joakim Ziegler - Supervisor de postproducci?n - Terminal joakim at terminalmx.com - 044 55 2971 8514 - 5264 0864 On 21/08/13 16:45, Joakim Ziegler wrote:> I had a rather large ext4 partition on an Areca RAID shut down uncleanly > while it was writing. When I mount it again, it recommends fsck, which I > do, and I get the following error: > > Failed to optimize directory ... EXT2 directory corrupted > > This error shows up every time I run fsck.ext4 on this partition. > > How can I fix this? The file system seems to work ok otherwise, I can > mount it and it doesn't complain, using it looks like it's ok, etc. >
Joakim Ziegler <joakim at ...> writes:> ... > Failed to optimize directory ... EXT2 directory corrupted > ...Disable dir_index (tune2fs(8)): # tune2fs -O ^dir_index /dev/??? and run (e2fsck(8)): # e2fsck -fD Some more, perhaps unrelated hints: http://lists.lustre.org/pipermail/lustre-discuss/2010-October/014397.html jb