Messages in this thread | | | Date | Mon, 15 Jun 1998 08:56:11 -0400 (EDT) | From | "Richard B. Johnson" <> | Subject | ext2 FS problem with 2.1.105 |
| |
I have discovered a problem that is being masked by the normal SysV bootup procedure which does not normally perform a complete 'fsck' of the file-system if it was properly dismounted and the mount-count has not expired.
If I boot with /bin/bash as init, then force a 'fsck' of the root file-system, (fsck -f /), I will get multiple instances of dtime not being set for deleted inodes, plus multiple instances of counts being wrong.
I think that when the file-system is being dismounted 'umounted!', not everything essential is being written to the device. I also think that this may be the reason why some of my files have become zero-length over time, including some that should never have been opened for write at all.
It is an easy problem to duplicate. I can duplicate the problem on three independent systems, all using 2.1.105. If I boot with 2.1.101, I do not have this problem, (but 2.1.103 does (tested only one one system)).
Cheers, Dick Johnson ***** FILE SYSTEM MODIFIED ***** Penguin : Linux version 2.1.105 on an i586 machine (66.15 BogoMips). Warning : It's hard to remain at the trailing edge of technology.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |