Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!howland.reston.ans.net!vixen.cso.uiuc.edu!uwm.edu!src.honeywell.com!The-Star.honeywell.com!flame.cfsmo.honeywell.com!news3.mr.net!mr.net!news.mr.net!skypoint.com!News.Minn.Net!mpp.minn.net!mpp From: mpp@mpp.minn.net (Mike Pritchard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: dos2unixtime fatal bug in 2.0.5-R Date: 15 Sep 1995 18:37:17 -0500 Organization: Minn Net Lines: 46 Message-ID: <mpp.811207680@mpp.minn.net> References: <APC&63'0'18d7dd12'9b9@glas.apc.org> <42p18b$gbp@bonnie.tcd-dresden.de> NNTP-Posting-Host: mpp.minn.net X-Newsreader: NN version 6.5.0 #4 (NOV) In <42p18b$gbp@bonnie.tcd-dresden.de> j@bonnie.heep.sax.de (J Wunsch) writes: >Vlad D. Nebolsin <vega@glas.apc.org> wrote: >>Sep 2 03:30:46 cuckoo /kernel: dos2unixtime(): month value out of range (14) >>Sep 2 03:30:49 cuckoo /kernel: dos2unixtime(): month value out of range (14) >>Sep 2 03:30:56 cuckoo /kernel: dos2unixtime(): month value out of range (0) >>Sep 2 03:30:57 cuckoo last message repeated 2 times >>... >> >>then it was just rebooted. >Reboot, or panic? >In case of a panic, give us as much information as you can. >>P.S. I hope it will be fixed in next release or SNAP, isn't it Jordan? >Not unless somebodys's got both: the time to fix it, and a DOS >partition. Don't laugh, the latter would be a big problem for example >for me... >-- >cheers, J"org private: joerg_wunsch@uriah.heep.sax.de Since I'm the last one to touch the "dos2unixtime()" routine: The "month value out of range" warning is telling you that that date field for the file in question had value that was not between 1 and 12 (inclusive) (DOS stores dates as separate month/day/year fields). When that is detected, the month is simply assumed to be 1. Looking at the code, I don't see how dos2unixtime() coule be causing a crash, but since you obviously have some files in your DOS file system that are damaged in some manner, probably something else in the msdosfs code it choking on those bad files. I would suggest booting DOS and running chkdsk/scandisk to see if you can identify the bad files, but don't let them fix the files! First go find out as much about the bad files as possible so that someone might be able to track down the cause of the reboot. E.g. the output from a "DIR" command for the files, any information chkdsk/scandisk report about them, etc. -- Mike Pritchard The Dart Shop - Darts & Supplies mpp@mpp.minn.net "Go that way. Really fast. If something gets in your way, turn"