Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: File corruption?



On Sun, Jan 19, 2020 at 05:17:25PM +0000, Andrew Doran wrote:

> Hi Robert,
> 
> On Sun, Jan 19, 2020 at 10:42:37AM -0600, Robert Nestor wrote:
> 
> > Sorry for not being specific.  When I do the shutdown on a subsequent
> > reboot all the filesystems are dirty forcing fsck to run.  Sometimes it
> > finds some minor errors and repairs them.
> > 
> > I?m running xfce4, so when I do the ?shutdown -r now?  I see xfce4 and X
> > exit bringing me back to the console display that was active when I booted
> > the system.  As it goes thru the normal shutdown process it reaches a
> > point where I get the assertion error (something like ?uvm_page locked
> > against owner?) followed by a stack trace and then quickly followed by the
> > system rebooting.  There is no crash file generated.
> 
> Could you please do a "sysctl -w ddb.onpanic=1" first, and then trigger the
> problem?  It shouldn't leave the stack trace there and not reboot then.  If

Argh. I mean to say it will leave the stack trace there and not reboot.

> you don't feel like typing it all in you could use a camera phone to take a
> picture of the backtrace or something like that.  If you don't have
> somewhere to upload the image you could e-mail it to me directly.
> 
> Andrew
>  
> > I haven?t changed any crash parameters from the stock setup.  I seem to
> > recall there used to be one for kernel crashes, but can?t find it now.  I
> > guess next step is to boot up with the ?-d?  flag and see if I can get
> > something useful.  Is that correct?
> > 
> > -bob
> > 
> > On Jan 19, 2020, at 9:52 AM, Greg Troxel <gdt%lexort.com@localhost> wrote:
> > 
> > > Robert Nestor <rnestor%mac.com@localhost> writes:
> > > 
> > >> I?ve downloaded and installed 9.99.38 (Jan 17 build) and the original
> > >> problem I was seeing with ?git? is gone.  However, I?m now seeing a
> > >> new problem with file corruption, but it only seems to happen when I
> > >> do a normal shutdown.  If I do a ?shutdown -r now? to shutdown and
> > > 
> > > You say "corruption", but then you say "filesystems are dirty".  Are you
> > > actually finding files with bad contents?
> > > 
> > >> reboot the system I see a crash during the shutdown phase and on
> > >> subsequent reboot the filesystems are all dirty. There is an assertion
> > >> about uvm_page I think, but it quickly disappears on the reboot.
> > > 
> > > Are you saying that if you "shutdown now", that the system shuts down
> > > with the crash?  And that there are then files with bad contents?
> > > 
> > > 
> > >> Is there a log file someplace that is written on the shutdown or is
> > >> there an easy way for me to capture the traceback before it disappears
> > >> off my screen?  There?s no crash file produced.
> > > 
> > > crash dumps may not be enabled.  You could also enable ddb and do the
> > > shutdown not using X, and then get a trace there.
> > 


Home | Main Index | Thread Index | Old Index