Re: freebsd-update from 9.3 to 11.0

[Doug Hardie]

> On 7 August 2016, at 21:27, Zoran Kolic  wrote:
> 
>> However, that patch works and I am now able to upgrade to 11.0-BETA4.
> 
> Would you continue informing us with the end result of your procedure.
> Personally, I will go the same way on my home nodes. I'm sure latter
> RCs would be more friendly regarding this upgrade. Since I have desktop
> and laptop, I'm not able to play and miss.

The patch (correctly applied by hand) worked fine.  The update completed and 
the server is running 11.0-BETA4.


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update from 9.3 to 11.0

[Zoran Kolic]

> However, that patch works and I am now able to upgrade to 11.0-BETA4.

Would you continue informing us with the end result of your procedure.
Personally, I will go the same way on my home nodes. I'm sure latter
RCs would be more friendly regarding this upgrade. Since I have desktop
and laptop, I'm not able to play and miss.
Best regards

Zoran

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: leapsecond file

[Kevin Oberman]

On 11.0-BETA4 I have:
> grep expires /var/db/ntpd.leap-seconds.list
#File expires on:  1 Jun 2017

But I see what you do on 10.3-RELEASE.  Looks like the update has not made
it into 10 (an I would guess 9).


Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

On Sun, Aug 7, 2016 at 7:31 PM, Randy Bush  wrote:

> >> Aug  7 04:13:06 cache0 ntpd[576]: leapsecond file
> ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago
> >>
> >> # grep ntp /etc/periodic.conf.local
> >> # 480.leapfile-ntpd
> >> daily_ntpd_leapfile_enable="YES"
> >> daily_ntpd_avoid_congestion="NO"
> >
> > For whatever reason, /etc/periodic/daily/480.leapfile-ntpd enters the
> > check phase on every invocation (daily), sleeps some random time less
> > than one day (if "avoid_congestion" true) and then decides that the file
> > is too young to replace (the current file expires June 1st, 2017). Logs
> > that to syslog .. rinse and repeat .. every day .. 
>
> /me is not understanding
>
> # grep expires /var/db/ntpd.leap-seconds.list
> #   File expires on:  1 Jun 2016
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: leapsecond file

[Randy Bush]

>> Aug  7 04:13:06 cache0 ntpd[576]: leapsecond file 
>> ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago
>> 
>> # grep ntp /etc/periodic.conf.local 
>> # 480.leapfile-ntpd
>> daily_ntpd_leapfile_enable="YES"
>> daily_ntpd_avoid_congestion="NO"
>
> For whatever reason, /etc/periodic/daily/480.leapfile-ntpd enters the
> check phase on every invocation (daily), sleeps some random time less
> than one day (if "avoid_congestion" true) and then decides that the file
> is too young to replace (the current file expires June 1st, 2017). Logs
> that to syslog .. rinse and repeat .. every day .. 

/me is not understanding

# grep expires /var/db/ntpd.leap-seconds.list
#   File expires on:  1 Jun 2016
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: leapsecond file

[Michael Butler]

On 08/07/16 22:11, Randy Bush wrote:
> i get these on all fbsd 10.3 hosts
> 
> Aug  7 04:13:06 cache0 ntpd[576]: leapsecond file 
> ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago
> 
> i have
> 
> # grep ntp /etc/periodic.conf.local 
> # 480.leapfile-ntpd
> daily_ntpd_leapfile_enable="YES"
> daily_ntpd_avoid_congestion="NO"
> 
> consulting the net of a thousand lies did not bring enlightenment.
> maybe someone here has a clue bat?  thanks.

"Broken" as designed :-(

For whatever reason, /etc/periodic/daily/480.leapfile-ntpd enters the
check phase on every invocation (daily), sleeps some random time less
than one day (if "avoid_congestion" true) and then decides that the file
is too young to replace (the current file expires June 1st, 2017). Logs
that to syslog .. rinse and repeat .. every day .. 

imb




___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

leapsecond file

[Randy Bush]

i get these on all fbsd 10.3 hosts

Aug  7 04:13:06 cache0 ntpd[576]: leapsecond file 
('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago

i have

# grep ntp /etc/periodic.conf.local 
# 480.leapfile-ntpd
daily_ntpd_leapfile_enable="YES"
daily_ntpd_avoid_congestion="NO"

consulting the net of a thousand lies did not bring enlightenment.
maybe someone here has a clue bat?  thanks.

randy
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:1905

[Rick Macklem]

Harry Schmalzbauer wrote:
> Hello,
>
> I had another crash which I'm quite sure was triggered by mount_unionfs:
Just in case you are not already aware, unionfs is always broken. Read the BUGS
section at the end of "man mount_unionfs". If it were easy to fix, someone would
have done so long ago. Yes, some use it successfully, but if not...

Sorry, but I suspect that is how it will remain, rick

Unread portion of the kernel message buffer:
panic: __lockmgr_args: downgrade a recursed lockmgr nfs @
/usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:1905
- Crash info deleted for brevity.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update from 9.3 to 11.0

[Doug Hardie]

> On 7 August 2016, at 13:59, Florian Ermisch 
>  wrote:
> 
> 
> 
> Am 7. August 2016 08:37:45 MESZ, schrieb Kurt Jaeger :
>> […]
>>> I have a number of production systems on 9.3 that need to be
>>> upgraded.  I can't go to 10.x as it won't boot on that hardware.
>>> However, 11.0 does boot.  I can't afford the downtime to completely
>>> rebuild them.
>> 
>> Uh, that sounds complicated.
> 
> Maybe it's worth the hassle to set up
> a freebsd-update server which provides 
> a 11.0 Kernel with a 10.x userland as
> 10.x-RELEASE? It's a hack, but only
> needed for the upgrade…
> 
> Regards, Florian


Comment #5 to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211398 has a 
patch that gets you very close to the right place for 9.3.  However, that patch 
works and I am now able to upgrade to 11.0-BETA4.  I have one server almost 
completed.  There are a couple of issues with packages, but they are being 
worked out.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update from 9.3 to 11.0

[Florian Ermisch]

Am 7. August 2016 08:37:45 MESZ, schrieb Kurt Jaeger :
> […]
> > I have a number of production systems on 9.3 that need to be
> > upgraded.  I can't go to 10.x as it won't boot on that hardware.
> > However, 11.0 does boot.  I can't afford the downtime to completely
> > rebuild them.
> 
> Uh, that sounds complicated.

Maybe it's worth the hassle to set up
a freebsd-update server which provides 
a 11.0 Kernel with a 10.x userland as
10.x-RELEASE? It's a hack, but only
needed for the upgrade…

Regards, Florian
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:1905

[Harry Schmalzbauer]

 Hello,

I had another crash which I'm quite sure was triggered by mount_unionfs:

Unread portion of the kernel message buffer:
panic: __lockmgr_args: downgrade a recursed lockmgr nfs @
/usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:1905

cpuid = 3
KDB: stack backtrace:
#0 0x80b2d887 at kdb_backtrace+0x67
#1 0x80ae5332 at vpanic+0x182
#2 0x80ae51a3 at panic+0x43
#3 0x80ab6987 at __lockmgr_args+0xe87
#4 0x80ba3c7c at vop_stdlock+0x3c
#5 0x82cd at VOP_LOCK1_APV+0x8d
#6 0x80a17c1c at unionfs_lock+0x48c
#7 0x82cd at VOP_LOCK1_APV+0x8d
#8 0x80bc8703 at _vn_lock+0x43
#9 0x80a17380 at unionfs_readdir+0x140
#10 0x81110e6f at VOP_READDIR_APV+0x8f
#11 0x80bc59ab at kern_getdirentries+0x21b
#12 0x80bc5768 at sys_getdirentries+0x28
#13 0x80fab6ae at amd64_syscall+0x4ce
#14 0x80f8dc0b at Xfast_syscall+0xfb
Uptime: 44m36s
Dumping 337 out of 2002 MB:..5%..15%..24%..34%..43%..53%..62%..72%..81%..91%

#0  doadump (textdump=) at pcpu.h:221
221 pcpu.h: Permission denied.
in pcpu.h
(kgdb) backtrace
#0  doadump (textdump=) at pcpu.h:221
#1  0x80ae4db9 in kern_reboot (howto=260) at
/usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c:366
#2  0x80ae536b in vpanic (fmt=, ap=)
at
/usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c:759
#3  0x80ae51a3 in panic (fmt=0x0) at
/usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c:690
#4  0x80ab6987 in __lockmgr_args (lk=,
flags=, ilk=, wmesg=,
pri=, timo=, file=, line=)
at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_lock.c:992
#5  0x80ba3c7c in vop_stdlock (ap=) at
lockmgr.h:98
#6  0x82cd in VOP_LOCK1_APV (vop=,
a=) at vnode_if.c:2087
#7  0x80a17c1c in unionfs_lock (ap=0xfe2296a0) at
vnode_if.h:859
#8  0x82cd in VOP_LOCK1_APV (vop=,
a=) at vnode_if.c:2087
#9  0x80bc8703 in _vn_lock (vp=,
flags=66560, file=, line=) at
vnode_if.h:859
#10 0x80a17380 in unionfs_readdir (ap=) at
/usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:1531
#11 0x81110e6f in VOP_READDIR_APV (vop=,
a=) at vnode_if.c:1822
#12 0x80bc59ab in kern_getdirentries (td=,
fd=, buf=0x800a35000 ,
count=, basep=0xfe229980, residp=0x0)
at vnode_if.h:758
#13 0x80bc5768 in sys_getdirentries (td=0x0,
uap=0xfe229a40) at
/usr/local/share/deploy-tools/RELENG_11/src/sys/kern/vfs_syscalls.c:3940
#14 0x80fab6ae in amd64_syscall (td=,
traced=0) at subr_syscall.c:135
#15 0x80f8dc0b in Xfast_syscall () at
/usr/local/share/deploy-tools/RELENG_11/src/sys/amd64/amd64/exception.S:396
#16 0x0045da4a in ?? ()
Previous frame inner to this frame (corrupt stack?)
Current language:  auto; currently minimal

Analyzing is out of my scope, sorry.
But I hope somebody else can before 11-RELEASE ships with this problem.

Thanks,

-Harry
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Call for testing: VM bugs in 10.3

[Andrea Venturoli]

On 08/02/16 21:25, Konstantin Belousov wrote:

Below is the merge of some high-profile virtual memory subsystem bug
fixes from stable/10 to 10.3. I merged fixes for bugs reported by
users, issues which are even theoretically unlikely to occur in real
world loads, are not included into the patch set. The later is mostly
corrections for the handling of radix insertion failures. Included fixes
are for random SIGSEGV delivered to processes, hangs on "vodead" state
on filesystem operations, and several others.

List of the merged revisions:
r301184 prevent parallel object collapses, fixes object lifecycle
r301436 do not leak the vm object lock, fixes overcommit disable
r302243 avoid the active object marking for vm.vmtotal sysctl, fixes
"vodead" hangs
r302513 vm_fault() race with the vm_object_collapse(), fixes spurious SIGSEGV
r303291 postpone BO_DEAD, fixes panic on fast vnode reclaim

I am asking for some testing, it is not necessary for your system to
exhibit the problematic behaviour for your testing to be useful. I am
more looking for smoke-testing kind of confirmation that patch is fine.
Neither I nor people who usually help me with testing,  run 10.3 systems.

If everything appear to be fine, my intent is to ask re/so to issue
Errata Notice with these changes in about a week from now.


Hello and thanks for your work.

Has this anything to do with

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204764

?

 bye & Thanks
av.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update from 9.3 to 11.0

[Doug Hardie]

> On 6 August 2016, at 23:37, Kurt Jaeger  wrote:
> 
> Hi!
> 
>> Is there any information available on when freebsd-update might
>> be corrected to upgrade some 9.3 systems to 11.0?
> 
> Does
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211354
> 
> help ?
> 
>> I have a number of production systems on 9.3 that need to be
>> upgraded.  I can't go to 10.x as it won't boot on that hardware.
>> However, 11.0 does boot.  I can't afford the downtime to completely
>> rebuild them.
> 
> Uh, that sounds complicated.

 No that didn't fix it.  That change was in the EN which was applied and while 
the line numbers are different in 9.3, the extra character is in my copy.




___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update from 9.3 to 11.0

[Kurt Jaeger]

Hi!

> Is there any information available on when freebsd-update might
> be corrected to upgrade some 9.3 systems to 11.0?

Does

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211354

help ?

> I have a number of production systems on 9.3 that need to be
> upgraded.  I can't go to 10.x as it won't boot on that hardware.
> However, 11.0 does boot.  I can't afford the downtime to completely
> rebuild them.

Uh, that sounds complicated.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

freebsd-update from 9.3 to 11.0

[Doug Hardie]

Is there any information available on when freebsd-update might be corrected to 
upgrade some 9.3 systems to 11.0?  I have tried all the beta's and none of them 
will do the upgrade even with the EN applied.  Bug 211398 has the details.

I have a number of production systems on 9.3 that need to be upgraded.  I can't 
go to 10.x as it won't boot on that hardware.  However, 11.0 does boot.  I 
can't afford the downtime to completely rebuild them.

— Doug

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

freebsd-update from 9.3 to 11.0

[Doug Hardie]

Is there any information available on when freebsd-update might be corrected to 
upgrade some 9.3 systems to 11.0?  I have tried all the beta's and none of them 
will do the upgrade even with the EN applied.  Bug 211398 has the details.

I have a number of production systems on 9.3 that need to be upgraded.  I can't 
go to 10.x as it won't boot on that hardware.  However, 11.0 does boot.  I 
can't afford the downtime to completely rebuild them.

— Doug

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"