931
Setup & Installation / Re: Problems with JFS
« on: May 12, 2016, 05:34:38 pm »Quote
and 1.09.06 was supposed to fix this problem.
I don't know about THIS problem. It is supposed to fix a problem where the file system gets damaged beyond repair. Since that is very rare, all I can say is that it hasn't happened to me again.
Quote
We also established that the problem is not fixed by the current XWP beta.
That would be the shutdown problem where the final data never gets to the disk. We also don't know if that is what is causing your problem.
Quote
Interesting that you have seen something similar - and probably related - when booting eCS within a virtualbox. I guess I should point David at this discussion in the hope that he can formulate some ideas about this problem.
I am not sure that I would say "Probably" related. More like "possibly" related. I am more inclined to think that is a VBOX problem where it doesn't attach the drive on the first try. It never needs a CHKDSK when it does get attached. A normal warm reboot, gets it attached.
Quote
Far easier if the server has a crash to simply let the config.sys statement
IFS=M:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:+*
sort out any problems that the crash may have caused the filesystem. Of course, you need JFS-1.09.05 or earlier to do that.
Personally, I have never, yet, seen any reason to even think about forcing a CHKDSK on reboot (real, or virtual, machines). The normal CHKDSK, if the disk is found dirty, rarely finds anything to fix, other than to mark it clean.
My "headless server" does have the devices attached, but they might as well not be there. I do have a problem with that machine where the BIOS, and the OS, don't agree on which disk is first, but LVM seems to look after that (but an Air Boot programed restart is confused). It is my eCS based NAS box. An old P4 with a SATA adapter card, and a 2 TB disk for storage (it was 1 TB until recently). Booting is done from an older 200 GB IDE drive.
Quote
If you like you can test this version or I can compile you a version with 1s delay. I guess you will not like to make much testing with your server but if yes, let me know.
I am pretty sure that 500 ms is not enough, and 4s is too much (but it seems to be safe). It is my opinion that a minimum of 1 second should be implemented, with an option of 2 seconds (for slow disks, in fast machines). One (or 4) extra second(s) to get it turned off will never be a problem, while having corrupted INI data, or having to wait for a CHKDSK on boot, can waste a LOT of time.