Hi!
I did the following experiment:
1) make an ext3 filesystem
2) everything works OK
3) start copying a big file
4) reset the system while it is still copying
5) boot, then mount ext3 filesystem - it says:
JFS DEBUG: (recovery.c, 411): journal_recover: JFS: recovery, exit status 0,
recovered transactions 130 to 133
6) unmount the fs, and with debugfs turn off journalling
7) "e2fsck -f" the filesystem
And fsck returned some errors. Is this normal?
Miklos
--
e2fsck 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 6122 has zero dtime. Fixy? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -24844
Fixy? yes
Free blocks count wrong for group #3 (0, counted=1).
Fixy? yes
Free blocks count wrong (63583, counted=63584).
Fixy? yes
Inode bitmap differences: -6122
Fixy? yes
Free inodes count wrong for group #3 (1563, counted=1564).
Fixy? yes
Free inodes count wrong (202168, counted=202169).
Fixy? yes
/dev/hda5: * FILE SYSTEM WAS MODIFIED *
/dev/hda5: 40591/242760 files (2.5% non-contiguous), 904064/967648 blocks
