Messages in this thread |  | | From | Keith Owens <> | Subject | Re: Corrupt ext2/ext3 directory entries not recovered by e2fsck | Date | Sat, 13 Oct 2001 22:59:09 +1000 |
| |
On Sat, 13 Oct 2001 22:44:34 +1000, Keith Owens <kaos@ocs.com.au> wrote: >The filesystem was created as ext3 but is currently being accessed as >ext2 while I work on XFS and kdb for IA64. After multiple power rests, >several directory entries are corrupt. Attempts to access the files >get I/O error with nothing in the log. Running e2fsck does not correct >the broken directory entry, neither does booting a kernel that supports >ext3.
I forgot to mention that both fsck.ext2 and fsck.ext3 report
1: Entry 'sendmail.pid' in /var/run (686849) has deleted/unused inode 688415. CLEARED. /1: Entry 'crond.pid' in /var/run (686849) has deleted/unused inode 688416. CLEARED. /1: Entry 'xfs.pid' in /var/run (686849) has deleted/unused inode 688417. CLEARED. /1: Entry 'atd.pid' in /var/run (686849) has deleted/unused inode 688418. CLEARED.
but the entries are still corrupt.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |