Re: repeated failure to properly shutdown

2016-07-22 Thread Martin Husemann
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

panic after 6.x -> 7.x upgrade

2016-07-22 Thread Manuel Bouyer
Hello, I've upgraded a server from 6.x to 7.x and it became unstable. I first did upgrade the kernel (7.0_STABLE from some time ago), keeping the 6.x userland, and it did run for more than 24h without troubles. Then I did upgrade the userland and problems started. Some filesystems are plain ffs,

Re: repeated failure to properly shutdown

2016-07-22 Thread bch
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

2016-07-22 Thread Robert Elz
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

2016-07-22 Thread Robert Elz
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

2016-07-22 Thread Rhialto
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

2016-07-22 Thread Michael Plass
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

2016-07-22 Thread Robert Elz
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

2016-07-22 Thread Robert Elz
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

daily CVS update output

2016-07-22 Thread NetBSD source update
Updating src tree: P src/etc/rc.d/mountcritlocal P src/sys/arch/amd64/amd64/machdep.c P src/sys/arch/amd64/include/pmap.h P src/sys/arch/mips/mips/bus_dma.c P src/sys/arch/x86/x86/pmap.c P src/sys/dev/ata/wd.c P src/sys/dev/ata/wdvar.h P src/sys/net/if.c P src/sys/net/if.h Updating xsrc tree:

Re: repeated failure to properly shutdown

2016-07-22 Thread Michael Plass
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

2016-07-22 Thread Robert Elz
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

2016-07-22 Thread Robert Elz
Date:Thu, 21 Jul 2016 16:38:57 -0700 From:bch Message-ID:

Re: repeated failure to properly shutdown

2016-07-22 Thread coypu
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

2016-07-22 Thread Robert Elz
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

2016-07-22 Thread J. Hannken-Illjes
> 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

2016-07-22 Thread Robert Elz
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

2016-07-22 Thread bch
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

2016-07-22 Thread Ian D. Leroux
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

2016-07-22 Thread Ian D. Leroux
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