[no subject]

2018-03-05 Thread Yoshimoto
___ 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: zfs problems after rebuilding system [SOLVED]

2018-03-05 Thread Dimitry Andric
On 3 Mar 2018, at 13:56, Bruce Evans wrote: > > On Sat, 3 Mar 2018, tech-lists wrote: >> On 03/03/2018 00:23, Dimitry Andric wrote: ... >>> Whether this is due to some sort of BIOS handover trouble, or due to >>> cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate >>> disks!),

[Bug 183817] [patch] [mac] [panic] kernel compiled with options INVARIANTS and MAC_PORTACL panices if loader loads mac_portacl.ko too

2018-03-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183817 --- Comment #6 from commit-h...@freebsd.org --- A commit references this bug: Author: eugen Date: Mon Mar 5 12:16:37 UTC 2018 New revision: 330499 URL: https://svnweb.freebsd.org/changeset/base/330499 Log: MFC r329994: mac_portacl(4): s

Re: zfs problems after rebuilding system [SOLVED]

2018-03-05 Thread Eugene Grosbein
05.03.2018 19:10, Dimitry Andric wrote: >> When no boot drive is detected early enough, the kernel goes to the >> mountroot prompt. That seems to hold a Giant lock which inhibits >> further progress being made. Sometimes progress can be made by trying >> to mount unmountable partitions on other

[Bug 183817] [patch] [mac] [panic] kernel compiled with options INVARIANTS and MAC_PORTACL panices if loader loads mac_portacl.ko too

2018-03-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183817 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: eugen Date: Mon Mar 5 12:21:36 UTC 2018 New revision: 330500 URL: https://svnweb.freebsd.org/changeset/base/330500 Log: MFC r329994: mac_portacl(4): s

[Bug 183817] [patch] [mac] [panic] kernel compiled with options INVARIANTS and MAC_PORTACL panices if loader loads mac_portacl.ko too

2018-03-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183817 Eugene Grosbein changed: What|Removed |Added Resolution|--- |FIXED Status|Open

Re: DDD hangs on start on 11.1-R

2018-03-05 Thread Daniel Eischen
On Mon, 5 Mar 2018, Trond Endrest?l wrote: On Sat, 3 Mar 2018 18:09+0100, Holm Tiffe wrote: can anyone get ddd get to work in 11.1-R or stable? I've more or less given up on devel/ddd, since it relies on the old pty subsystem, now replaced by the new pts subsystem, to communicate with gdb.

RE: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi client

2018-03-05 Thread NAGY Andreas
Thanks, I am actually compiling with both patches. I try now to get NFS 4.1 multipathing working. So I have now two connection on different subnets between the ESXi host and the FreeBSD host with exports for the same mountpoint on both subnets. Now I get the following errors in the vmkernel.log:

RE: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi client

2018-03-05 Thread NAGY Andreas
Compiling with the last patch also failed: error: use of undeclared identifier 'NFSV4OPEN_WDSUPPFTYPE' -Original Message- From: NAGY Andreas Sent: Montag, 5. März 2018 14:22 To: Rick Macklem ; 'freebsd-stable@freebsd.org' Subject: RE: NFS 4.1 RECLAIM_COMPLETE FS failed error in combi

Re: zfs problems after rebuilding system [SOLVED]

2018-03-05 Thread Mark Millard via freebsd-stable
Eugene Grosbein eugen at grosbein.net wrote on Mon Mar 5 12:20:47 UTC 2018 : > 05.03.2018 19:10, Dimitry Andric wrote: > >>> When no boot drive is detected early enough, the kernel goes to the >>> mountroot prompt. That seems to hold a Giant lock which inhibits >>> further progress being made.

Re: "Cross" building for same architecture, different CPUTYPE

2018-03-05 Thread Marek Zarychta
On Sun, Mar 04, 2018 at 07:32:09PM +0100, Christian Ullrich wrote: > * Warner Losh wrote: > > > On Sun, Mar 4, 2018 at 10:43 AM, Dimitry Andric > > wrote: > > > > Again, this depends on how exactly you are overriding CPUTYPE. > > > > I'd suggest *NOT* setting CPUTYP

Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi client

2018-03-05 Thread Rick Macklem
Nope, that isn't supported, rick (Hope no one is too upset by a top post.) From: NAGY Andreas Sent: Monday, March 5, 2018 8:22:10 AM To: Rick Macklem; 'freebsd-stable@freebsd.org' Subject: RE: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ES