Re: repeated failure to properly shutdown

On 7/22/2016 2:41 PM, Martin Husemann wrote: On Fri, Jul 22, 2016 at 11:37:56AM -0700, bch wrote: How does that happen, how does one fix it ? It is created by init if there is no /dev/console. Boot some install media, mount your root file system (say on /mnt) then: cd /mnt/dev

Re: repeated failure to properly shutdown

Iirc, where I *noticed* it was /etc/defaults/rc.d On Jul 22, 2016 5:03 PM, "Robert Elz" wrote: > Date:Fri, 22 Jul 2016 16:27:19 -0700 > From:bch > Message-ID: < >

Re: repeated failure to properly shutdown

It could be that for some reason it's missing, and a first attempt to write to it just creates a regular file... On Jul 22, 2016 4:25 PM, "Robert Elz" wrote: > Date:Sat, 23 Jul 2016 04:38:42 +0700 > From:Robert Elz >

Re: repeated failure to properly shutdown

On Jul 22, 2016 2:39 PM, "Robert Elz" wrote: > > Date:Fri, 22 Jul 2016 12:52:58 -0700 > From:bch > Message-ID: < cabfrot-qp37szwwfrj+zedjqxf5e2troxmh0lmqc+dckb0k...@mail.gmail.com> > > | I think that biggest concern

Re: repeated failure to properly shutdown

mknod null c 2 2 did the trick, things boot/reboot alright now. I think that biggest concern (unclean shutdown/reboot) is solved (collision of /dev and a tmpfs mount, caused by default behavior of init in face of missing /dev/console). This disk was prepared remotely (I.e. from another running

Re: repeated failure to properly shutdown

I see what you're saying, did it (and do have a console device), but now my etc/defaults/rc.d is barfing on: cannot create /dev/null: read only file system On Jul 22, 2016 11:41 AM, "Martin Husemann" wrote: > On Fri, Jul 22, 2016 at 11:37:56AM -0700, bch wrote: > > How does

Re: repeated failure to properly shutdown

Date:Fri, 22 Jul 2016 22:15:02 -0700 From:Michael Plass Message-ID: <3c6b1155-00df-420d-82da-6227d62d7...@plass-family.net> | Hmm, it looks like doing "shutdown now" to get into single-user | will force-unmount the tmpfs file systems

Re: repeated failure to properly shutdown

On Jul 22, 2016, at 5:02 PM, Robert Elz wrote: > the question is just where is that first attempt. Hmm, it looks like doing "shutdown now" to get into single-user will force-unmount the tmpfs file systems (/etc/rc.d/swap1), so you could be left in a state where creating a regular /dev/null

Re: repeated failure to properly shutdown

Date:Fri, 22 Jul 2016 17:09:30 -0700 From:bch Message-ID: | Iirc, where I *noticed* it was /etc/defaults/rc.d Yes, that (/etc/defaults/rc.conf I assume you mean) writes to

Re: repeated failure to properly shutdown

Date:Fri, 22 Jul 2016 16:27:19 -0700 From:bch Message-ID: | It could be that for some reason it's missing, and a first attempt to write | to it just creates a regular

Re: repeated failure to properly shutdown

On Jul 22, 2016, at 4:24 PM, Robert Elz wrote: >Date:Sat, 23 Jul 2016 04:38:42 +0700 >From:Robert Elz >Message-ID: <20406.1469223...@andromeda.noi.kre.to> > > | That /dev/null turned into a regular file is another bug [...] > | (This turns out

Re: repeated failure to properly shutdown

Date:Sat, 23 Jul 2016 04:38:42 +0700 From:Robert Elz Message-ID: <20406.1469223...@andromeda.noi.kre.to> | That /dev/null turned into a regular file is another bug [...] | (This turns out to be a bug in MAKEDEV [...] Actually, not, it must be

Re: repeated failure to properly shutdown

On Sat 23 Jul 2016 at 04:38:42 +0700, Robert Elz wrote: > That /dev/null turned into a regular file is another bug - it is being > created before the tmpfs /dev is made, I have seen that before as well, > but just corrected and ignored the problem until now. Similarly, I noticed that if /var

Re: repeated failure to properly shutdown

Date:Fri, 22 Jul 2016 12:52:58 -0700 From:bch Message-ID: | I think that biggest concern (unclean shutdown/reboot) is solved (collision | of /dev and a tmpfs mount,

Re: repeated failure to properly shutdown

On Fri, Jul 22, 2016 at 11:37:56AM -0700, bch wrote: > How does that happen, how does one fix it ? It is created by init if there is no /dev/console. Boot some install media, mount your root file system (say on /mnt) then: cd /mnt/dev sh MAKEDEV all (hoping there is a MAKEDEV

Re: repeated failure to properly shutdown

Wow -- there -is- a tmpfs on /dev kamloops# mount /dev/wd0a on / type ffs (log, local) -> tmpfs on /dev type tmpfs (union, local) /dev/wd0e on /var type ffs (log, local) /dev/wd0f on /usr type ffs (log, local) /dev/wd0g on /home type ffs (log, local)

Re: repeated failure to properly shutdown

On Fri, Jul 22, 2016, at 14:00, Robert Elz wrote: > Date:Fri, 22 Jul 2016 07:11:50 -0400 From:"Ian D. > Leroux" Message-ID: > <20160722071150.5248712b562feea8d5c89...@fastmail.fm> > > | Might this be a good moment to test them out and commit

Re: repeated failure to properly shutdown

Date:Fri, 22 Jul 2016 07:11:50 -0400 From:"Ian D. Leroux" Message-ID: <20160722071150.5248712b562feea8d5c89...@fastmail.fm> | Might this be a good moment to test them out and commit them? Perhaps, but not really as a fix for the current

Re: repeated failure to properly shutdown

Date:Fri, 22 Jul 2016 00:33:01 -0700 From:bch Message-ID: | Confirm this stack frame is the/a one we care about? It looks right, yes, though one level further up should

Re: repeated failure to properly shutdown

On Fri, 22 Jul 2016 16:57:08 +0700 Robert Elz wrote: > "J. Hannken-Illjes" said: > > | No populated "/dev" so it uses dev on tmpfs? > > Ah yes, very possible - the output from mount will tell us that, but I > remember earlier reports of problems

Re: repeated failure to properly shutdown

I can do that tomorrow, yes. Confirm this stack frame is the/a one we care about? Regards, -bch On Jul 21, 2016 11:42 PM, "Martin Husemann" wrote: On Thu, Jul 21, 2016 at 04:38:57PM -0700, bch wrote: > and the v_mount refcounts and flags are: > > (gdb) print vp->v_mount >

Re: repeated failure to properly shutdown

Date:Fri, 22 Jul 2016 08:45:44 + From:co...@sdf.org Message-ID: <20160722084544.ga14...@sdf.org> | probably good to remember that it's also saying it's double freed. | is it garbage data because it was freed before? Perhaps, we will get a better idea when we

Re: repeated failure to properly shutdown

> On 22 Jul 2016, at 10:39, Robert Elz wrote: > >Date:Thu, 21 Jul 2016 16:38:57 -0700 >From:bch >Message-ID: >

Re: repeated failure to properly shutdown

On Fri, Jul 22, 2016 at 03:39:26PM +0700, Robert Elz wrote: > Date:Thu, 21 Jul 2016 16:38:57 -0700 > From:bch > Message-ID: >

Re: repeated failure to properly shutdown

Date:Thu, 21 Jul 2016 16:38:57 -0700 From:bch Message-ID:

Re: repeated failure to properly shutdown

bch wrote: >I have kernel cores, but I'm not as familiar w/ crash(8) as gdb. You can use gdb instead of crash if you want:

Re: repeated failure to properly shutdown

On 7/21/16, bch wrote: > Alright -- I'm in (recompiled kernel with proper options, induced > crash, loaded w/ gdb). What frame and data are we interested in ? OK -- I roughly reviewed the mail thread and it looks (to me) like frame 6: > #6 0x808ca91d in vclean

Re: repeated failure to properly shutdown

Alright -- I'm in (recompiled kernel with proper options, induced crash, loaded w/ gdb). What frame and data are we interested in ? -bch /usr/obj/sys/arch/amd64/compile/GENERIC kamloops# gdb ./netbsd.gdb GNU gdb (GDB) 7.10.1 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+:

Re: repeated failure to properly shutdown

On Jul 21, 2016 1:08 PM, "J. Hannken-Illjes" wrote: > > > > On 21 Jul 2016, at 19:26, co...@sdf.org wrote: > > > > On Thu, Jul 21, 2016 at 10:15:32AM -0700, bch wrote: > >> Jul 20 23:55:59 kamloops /netbsd: wapbl_discard() at > >> netbsd:wapbl_discard+0x20c > >> Jul 20

Re: repeated failure to properly shutdown

> On 21 Jul 2016, at 19:26, co...@sdf.org wrote: > > On Thu, Jul 21, 2016 at 10:15:32AM -0700, bch wrote: >> Jul 20 23:55:59 kamloops /netbsd: wapbl_discard() at >> netbsd:wapbl_discard+0x20c >> Jul 20 23:55:59 kamloops /netbsd: vclean() at netbsd:vclean+0x2ae > ... >> Jul 20 23:55:59 kamloops

Re: repeated failure to properly shutdown

Well -- that fixed the fault-on-exit (and therefore the dirty filesystems on reboot) -- now to figure out why the tmpfs is so problematic for me... Thanks! -bch On 7/21/16, Robert Swindells wrote: > > bch wrote: >>On 7/21/16, Robert Elz

Re: repeated failure to properly shutdown

bch wrote: >On 7/21/16, Robert Elz wrote: >> Do you perhaps have /tmp mounted as a tmpfs with -o log ? >> (Can you show us /etc/fstab in its entirety?) > >For your viewing pleasure... > >=== ># NetBSD /etc/fstab ># See /usr/share/examples/fstab/

Re: repeated failure to properly shutdown

On 7/21/16, Robert Elz wrote: > Do you perhaps have /tmp mounted as a tmpfs with -o log ? > (Can you show us /etc/fstab in its entirety?) For your viewing pleasure... === # NetBSD /etc/fstab # See /usr/share/examples/fstab/ for more examples. /dev/wd0a /

Re: repeated failure to properly shutdown

On Thu, Jul 21, 2016 at 10:15:32AM -0700, bch wrote: > Jul 20 23:55:59 kamloops /netbsd: wapbl_discard() at > netbsd:wapbl_discard+0x20c > Jul 20 23:55:59 kamloops /netbsd: vclean() at netbsd:vclean+0x2ae ... > Jul 20 23:55:59 kamloops /netbsd: tmpfs_unmount() at netbsd:tmpfs_unmount+0x2f For

Re: repeated failure to properly shutdown

More information... Jul 20 23:55:59 kamloops /netbsd: panic: kernel diagnostic assertion "bp->b_freelistindex == -1" failed: file "/usr/src/sys/kern/vfs_bio.c", line 334 double free of buffer? bp=0xfe811ca935a0, b_freelistindex=0 Jul 20 23:55:59 kamloops /netbsd: Jul 20 23:55:59 kamloops

Re: repeated failure to properly shutdown

Do you perhaps have /tmp mounted as a tmpfs with -o log ? (Can you show us /etc/fstab in its entirety?) kre

Re: repeated failure to properly shutdown

Further, here is a copy of my superblock info (for /, in this case) for review if necessary. I'm running w/ the "log" option in fstab. kamloops$ dumpfs -s / file system: /dev/rwd0a format FFSv1 endian little-endian magic 11954 timeWed Jul 20 20:52:58 2016 superblock location