Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!actcsiro!news.nsw.CSIRO.AU!wabbit.its.uow.edu.au!news.ci.com.au!newshost.telstra.net!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!inquo!vyzynz!newsfeed.concentric.net!winternet.com!mr.net!news.mr.net!gw.dgii.com!mpp From: mpp@digibd.com (Mike Pritchard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: dos2unixtime() error Date: 22 Apr 1996 21:50:17 GMT Organization: Digi International Lines: 44 Message-ID: <4lguup$fdf@gw.dgii.com> References: <ts-2204960846300001@mac.infodirekt.de> NNTP-Posting-Host: engin.dgii.com X-Newsreader: NN version 6.5.0 #6 (NOV) In <ts-2204960846300001@mac.infodirekt.de> ts@infodirekt.de (Thomas Schreiber) writes: >I occasionly get this error message: >Apr 20 03:30:07 rio /kernel: dos2unixtime(): month value out of range (0) >Sometimes - as this time on Apr 20 - the computer hangs totally after >that. >I tryed to figure out in the source /sys/msdosfs/msdosfs_conv.c >whats going on but got no idea of how to help myself. >Anybody seen this kind of problem? - FreeBSD version is 2.1.0. >Here are the last entries of this error (in these cases no crash): >/var/log/messages.0:Apr 13 03:30:06 rio /kernel: dos2unixtime(): month >value out of range (0) >/var/log/messages.1:Apr 6 03:30:06 rio /kernel: dos2unixtime(): month >value out of range (0) >/var/log/messages.2:Mar 30 03:30:07 rio /kernel: dos2unixtime(): month >value out of range (0) >/var/log/messages.3:Mar 23 03:30:06 rio /kernel: dos2unixtime(): month >value out of range (0) >/var/log/messages.3:Mar 23 13:59:47 rio /kernel: dos2unixtime(): month >value out of range (0) This means that dos2unixtime() was asked to examine a file that has an invalid time stamp. Dos stores the file date in mm/dd/yy format, and the file in question has a month field of zero. Dos2unixtime will default to something valid (1 maybe?, I don't recall off hand), and is not the direct cause of the crash. You probably have some bad files in your dos file system, and accessing them eventually causes the FreeBSD dos file system code to go out to lunch. You should boot up dos and run chkdisk/scandisk on your dos partition and see what it comes up with. -- Mike Pritchard mpp@dgii.com or mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn"