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

2018-03-07 Thread Rick Macklem
NAGY Andreas wrote: >attached the trace. If I see it correct it uses FORE_OR_BOTH. (bctsa_dir: >>CDFC4_FORE_OR_BOTH (0x0003)) Yes. The scary part is the ExchangeID before the BindConnectiontoSession. (Normally that is only done at the beginning of a new mount to get a ClientID, followed immed

Re: Problem with USB <---> UPS management connection

2018-03-07 Thread Glen Barber
On Wed, Mar 07, 2018 at 08:04:47PM -0500, Mark Saad wrote: > > On Mar 7, 2018, at 6:55 AM, wishmaster wrote: > > > > Hi, colleagues! > > > > Something strange happens with a server. I am attempting to connect > > management interface of UPS with server via USB. > > In console I see a lot of err

Re: Problem with USB <---> UPS management connection

2018-03-07 Thread Mark Saad
All I lost power at home and noticed that nut didn’t work right . I had a similar dmesg . My box is running 11.1-stable amd64 built from svn 7-8 days ago . When I get power back I’ll post details . --- Mark Saad | nones...@longcount.org > On Mar 7, 2018, at 6:55 AM, wishmaster wrote: > > Hi

F5 Networks Users List.

2018-03-07 Thread Amy Hodge
Hi, I would like to know if you are interested in acquiring F5 Networks Users List. We have also new technology like: Juniper Networks, Cisco, Citrix, Check Point, Fortinet, VMware, Palo Alto Networks, NetApp, Brocade Communications Systems, Blue Coat Systems, Brocade Communications Systems

Re[2]: Problem with USB <---> UPS management connection

2018-03-07 Thread wishmaster
  --- Original message --- From: "tech-lists" Date: 7 March 2018, 20:12:13 > On 07/03/2018 11:55, wishmaster wrote: > > I have changed USB-cables, USB port on the server - without success. > > On another server this problem is absent. > > It looks like a broken or shorting connection but y

Re: Problem with USB <---> UPS management connection

2018-03-07 Thread tech-lists
On 07/03/2018 11:55, wishmaster wrote: > I have changed USB-cables, USB port on the server - without success. > On another server this problem is absent. It looks like a broken or shorting connection but you say you've tried different ports on the machine and changed cables. I dunno, maybe the usb

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

2018-03-07 Thread NAGY Andreas
Hi, attached the trace. If I see it correct it uses FORE_OR_BOTH. (bctsa_dir: CDFC4_FORE_OR_BOTH (0x0003)) The trace is only with the first patch, have not compiled the wantdeleg patches so far. I think this is related to the BIND_CONN_TO_SESSION; after a disconnect the ESXi cannot connec

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

2018-03-07 Thread Rick Macklem
NAGY Andreas wrote: >Okay, that was the main reason for using NFS 4.1. >Is it planned to implement it, or is the focus on pNFS? I took a quick look and implementing this for some cases will be pretty easy. Binding a FORE channel is implied, so for that case all the server does is reply OK to the BI

Targeted Companies Emails List

2018-03-07 Thread cathy . pearson
Hi, This is Cheryl from pre-sales team. Hope this email finds well. I am wondering if you would be interested in reaching your targeted PeopleSoft/SuccessFactors Users for your Marketing Approach Strategy. We can provide you with 100% opt in emails. You may also be interested in database of

Problem with USB <---> UPS management connection

2018-03-07 Thread wishmaster
Hi, colleagues! Something strange happens with a server. I am attempting to connect management interface of UPS with server via USB. In console I see a lot of errors: Mar  7 13:42:04 xxx kernel: ugen2.2: at usbus2 Mar  7 13:42:05 xxx kernel: uhid0 on uhub6 Mar  7 13:42:05 xxx kernel: uhid0: o

Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE

2018-03-07 Thread Jan Bramkamp
On 28.02.18 18:03, Hadi Rezaee wrote: Hello there, My laptop is running FreeBSD-12 CURRENT, and i hadnt any problem with my graphic before upgrading drm-next (g20180117_3 -> 4.11.g20180224). But now it getting failed. Tried to build from source, but same result. Laptop model: Lenovo E470 I j

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

2018-03-07 Thread Christian Ullrich
* Marek Zarychta wrote: * Warner Losh wrote: I'd suggest *NOT* setting CPUTYPE and instead using TARGET_CPUTYPE to do these sorts of things. CPUTYPE is known to only work on native builds Maybe you should try to build using different make.conf(5) files for each build? It can be improved WI