Package: xfsprogs Version: 2.6.20-1 Severity: normal Hi,
I have a filesystem that stores (a backup) of my maildir with about 900k files. This filesystem somehow (bad disk most likely) got corrupted a bit so I tried to xfs_repair it. | Phase 6 - check inode connectivity... | - resetting contents of realtime bitmap and summary inodes | - ensuring existence of lost+found directory | - traversing filesystem starting at / ... | bad hash table for directory inode 119782815 (no leaf entry): rebuilding | rebuilding directory inode 119782815 | rebuilding directory inode 187306538 | rebuilding directory inode 67122641 | rebuilding directory inode 134364167 | rebuilding directory inode 222199735 | rebuilding directory inode 23536180 | rebuilding directory inode 257248905 | rebuilding directory inode 51980172 | rebuilding directory inode 184752564 | Terminated In the 'traversing filesystem starting at /' state, xfs_repair started to eat enormous amounts of memory, and got OOM killed at about using 1.4 gigs of virtual memory. It seems that it tries to store the entire tree in RAM? Maybe this could be changed to not require that much ram. -- Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
