[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 filesystem lost.



"Stephen C. Tweedie" <sct redhat com> writes:

server:/tmp/sbin# ./e2fsck /dev/rd/c0d1p1
e2fsck 1.20-WIP, 10-May-2001 for EXT2 FS 0.5b, 95/08/09
JFS DEBUG: (journal.c, 170): e2fsck_journal_init_inode: Using journal inode 12
Superblock has a bad ext3 journal (inode 12).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Clearing orphaned inode 12 (uid=0, gid=0, mode=0100644, size=67108864)
/dev/rd/c0d1p1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/rd/c0d1p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/rd/c0d1p1: 276590/4447744 files (0.6% non-contiguous), 4924671/8886268 bloc
ks
server:/tmp/sbin# mount /dev/rd/c0d1p1 ...
(success:-)

Thanks a lot. This made my day.

-- 
Per Andreas Buer





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]