On Fri, 10 Sep 2004 14:40:45 +0200
"Frank B. Scholl" <frank.b.scholl@web.de> wrote:

> On Fri, 10 Sep 2004 12:11:36 +0200
> Martin Husemann <martin@duskware.de> wrote:
> 
> > On Fri, Sep 10, 2004 at 01:59:27PM +0200, Frank B. Scholl wrote:
> > 
> > > if i MAKEDEV all devices from new, well, the problem seems to be solved
> > > at first, but even if i do not plug in my harddisk, sd0 gets large again.
> > 
> > What does "ls -l" say about that "device" directly after a "MAKEDEV all"
> > and again when it grew big?
> 
> 
> the rights are set like one expects them to be set, always:
> 
> -rw-r--r--  1 root  wheel  54878535680 Sep  8 17:13 sd0
> 
> as you see, its growing, another few hundred mb more..
> 
>  
> > Some script (run by cron?) is doing something stupid, apparently.
> 
> 
> i thought that too, at first, but crontab has no entries on that machine.
> 
>  
> > If the culprit is still running you can use fstat(1) to find the process.
> 
> fstat doesnt show anything active on /dev/sd0.
> 
> to complete my problem description, i want to add that when i wanted to remove
> the device, i powered it off, the machine was still runing, but when i actually
> plugged out the usb connecter, it turned off completely. not a "normal" crash,
> but just like a power-outage. zoooom, thats it, blackness. :) well, sounds like
> a win32 user's description of a hardware problem, but i cant say anymore. no traces
> were left, kernel didnt even drop into db> so i could have been able get some info here.
> 
> maybe its just umass code that behaves a bit strange, maybe it dislikes the usb2
> controller, but all of that is no reasonable explanation why sd0 still grows.
> 
> i thought about reinstalling the box, but before i wanted to drop some lines here,
> maybe somebody wants that information.
> 

hm, actually it isnt even a device.. its just a plain file, that is created (thanks
to stix, i remarked that now, dont know why i didnt earlier, but that doesnt make it
less strange..)

frank (again)