Date: Mon, 5 Mar 2018 08:19:24 -0500 (EST) From: Daniel Eischen <deischen@freebsd.org> To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Cc: FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: DDD hangs on start on 11.1-R Message-ID: <Pine.GSO.4.64.1803050816400.27683@sea.ntplx.net> In-Reply-To: <alpine.BSF.2.21.1803050814570.97064@mail.fig.ol.no> References: <20180303170941.GC9421@beast.freibergnet.de> <alpine.BSF.2.21.1803050814570.97064@mail.fig.ol.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Mar 2018, Trond Endrest=F8l 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. > > I build custom kernels containing "device pty", but I'm not sure if > that directive is being honoured these days. > > It's a shame, 'cos ddd is very good at visualizing data structures. > Maybe it's possible to patch ddd to use pts instead of pty. I used to like ddd also. You might try devel/gps. It's more than just a debugger, but you can use it just for debugging. Note, it's been a while since I've used it, but worked similarly to ddd. --=20 DE From owner-freebsd-stable@freebsd.org Mon Mar 5 13:22:15 2018 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AA26F2EDF4 for <freebsd-stable@mailman.ysv.freebsd.org>; Mon, 5 Mar 2018 13:22:15 +0000 (UTC) (envelope-from Andreas.Nagy@frequentis.com) Received: from mail2.frequentis.com (mail2.frequentis.com [195.20.158.51]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "spamquarantine.frequentis.frq", Issuer "Frequentis Enterprise Issuing CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F34A8795A8 for <freebsd-stable@freebsd.org>; Mon, 5 Mar 2018 13:22:14 +0000 (UTC) (envelope-from Andreas.Nagy@frequentis.com) X-IronPort-AV: E=Sophos;i="5.47,427,1515452400"; d="scan'208";a="2433812" Received: from vie191nt.frequentis.frq ([172.16.1.191]) by mail2.frequentis.com with ESMTP; 05 Mar 2018 14:22:11 +0100 Received: from vie196nt.frequentis.frq ([172.16.1.196]) by vie191nt.frequentis.frq ([172.16.1.191]) with mapi id 14.03.0382.000; Mon, 5 Mar 2018 14:22:11 +0100 From: NAGY Andreas <Andreas.Nagy@frequentis.com> To: Rick Macklem <rmacklem@uoguelph.ca>, "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org> Subject: =?iso-8859-1?Q?RE:_NFS_4.1_RECLAIM=5FCOMPLETE_FS=A0failed_error_in_combin?= =?iso-8859-1?Q?ation_with_ESXi_client?= Thread-Topic: =?iso-8859-1?Q?NFS_4.1_RECLAIM=5FCOMPLETE_FS=A0failed_error_in_combinatio?= =?iso-8859-1?Q?n_with_ESXi_client?= Thread-Index: AdOx8zAe5+TceuOWQkax+IhJZhNDgQAnzopHABn27/AAIBzCQgAP8SUgAAmzYWAADy6jKgAZTvpA Date: Mon, 5 Mar 2018 13:22:10 +0000 Message-ID: <D890568E1D8DD044AA846C56245166780124AFC0E2@vie196nt> References: <c5c624de-42bb-45cf-8cf0-b25be56e5f58@frequentis.com> <YQBPR0101MB1042DEF0825996764CBCA829DDC40@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>, <D890568E1D8DD044AA846C56245166780124AFB90E@vie196nt> <YQBPR0101MB1042479407CAA253674BBAEBDDDB0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> <D890568E1D8DD044AA846C56245166780124AFBD21@vie196nt>, <D890568E1D8DD044AA846C56245166780124AFBD91@vie196nt> <YQBPR0101MB104225B6884FEC70A03C61CCDDDA0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <YQBPR0101MB104225B6884FEC70A03C61CCDDDA0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> Accept-Language: de-AT, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.72.193] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 05 Mar 2018 13:22:15 -0000 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 expor= ts for the same mountpoint on both subnets. Now I get the following errors in the vmkernel.log: 2018-03-05T13:06:07.488Z cpu10:66503)WARNING: NFS41: NFS41_Bug:2361: BUG - = Invalid BIND_CONN_TO_SESSION error: NFS4ERR_NOTSUPP Is there session trunking available in the FreeBSD NFS41 implementation? Br, andi -----Original Message----- From: Rick Macklem [mailto:rmacklem@uoguelph.ca]=20 Sent: Montag, 5. M=E4rz 2018 02:16 To: NAGY Andreas <Andreas.Nagy@frequentis.com>; 'freebsd-stable@freebsd.org= ' <freebsd-stable@freebsd.org> Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS=A0failed error in combination with= ESXi client NAGY Andreas wrote: [stuff snipped] >In the source I saw nfs_async =3D 0; is it right that NFS will work in asy= nc mode if I >compile the kernel with nfs_async =3D 1? > >I know the risk of running it async, but is it not the same risk having th= e datastore >connected via iSCSI which standard is also not sync? If you want to use it, you can just set it by setting the sysctl vfs.nfsd.a= sync=3D1. - If the server crashes/reboots you can lose data. Also, after the reboot, = the client will only see an temporarily unresponsive server and will not have= any indication of data loss. (I am not familiar with iSCSI, so I can't comment on how safe that is.) - If you are using ZFS, there is also a ZFS config (sync=3Ddisabled). I'm n= ot a ZFS guy, so I don't know anything more, but I'm sure others reading this list= can tell you how to set it. [more stuff snipped] >So far I did not see any issue with the mount. Only in the vmkernel.log th= ere are >often following entrees: >WARNING: NFS41: NFS41ValidateDelegation:608: Server returned improper=20 >>reason for no delegation: 2 The attached patch *might* get rid of these, although I don't think it matt= ers much, since it is just complaining about the "reason" the server return= s for not issuing a delegation (issuing delegations is entirely at the disc= retion of the server and is disabled by default). [more stuff snipped] Good luck with it, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.1803050816400.27683>