Daniel Veillard
2000-Nov-06 19:07 UTC
Please make the journal file unmodified by user processes
Please forbid user level process to touch or unling the journal file when the partition is ext3 mounted ... at all ! So far this weakness has been my main problem when using ext3 on production systems. Happened to rpmfind machines a couple of times, at best a program removed the journal inode from the FS list and it cannot be mounted at next reboot. At worse the content of the journal.dat is modified and the machine oopses and crash. This just arrived again on one of the W3C web servers where and rsync removed it and the server could not found the partition at next reboot. please fix this, just relying on chattr +i is far too weak for real use ! thanks, Daniel -- Daniel.Veillard@w3.org | W3C, INRIA Rhone-Alpes | libxml Gnome XML toolkit Tel: +33 476 615 257 | 655, avenue de l'Europe | http://xmlsoft.org/ Fax: +33 476 615 207 | 38330 Montbonnot FRANCE | Rpmfind search site http://www.w3.org/People/all#veillard%40w3.org | http://rpmfind.net/
Stephen C. Tweedie
2000-Nov-06 22:33 UTC
Re: Please make the journal file unmodified by user processes
Hi, On Mon, Nov 06, 2000 at 08:07:57PM +0100, Daniel Veillard wrote:> > Please forbid user level process to touch or unling the journal > file when the partition is ext3 mounted ... at all !I will do --- the current e2fsprogs snapshot has preliminary mke3fs support which already uses a hidden internal inode for the journal. Cheers, Stephen