Re: ELF binary type "3" not known.

2017-03-21 Thread Chris H
On Tue, 21 Mar 2017 13:47:23 +0100 Gary Jennejohn wrote > On Tue, 21 Mar 2017 10:15:35 +0100 > Mathieu Arnold wrote: > > > Le 21/03/2017 __ 06:22, Chris H a __crit : > > > On Tue, 21 Mar 2017 13:14:56 +0800 Kevin Lo wrote > > > > >

Re: process killed: text file modification

2017-03-21 Thread Konstantin Belousov
On Tue, Mar 21, 2017 at 02:30:38AM +, Rick Macklem wrote: > Konstantin Belousov wrote: > [stuff snipped] > > Yes, I have to somewhat retract my claims, but then I have another set > > of surprises. > Righto. > > > I realized (remembered) that nfs has its own VOP_PUTPAGES() method. > >

Re: NFSv2 boot & OLD_NFSV2

2017-03-21 Thread Daniel Braniss
> On 20 Mar 2017, at 23:53, Rick Macklem wrote: > > Baptiste Daroussin wrote: >> On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote: >>> Hi! >>> >>> The current boot code is building NFSv3, with preprocessor conditional >>> OLD_NFSV2. Should NFSv2 code still be

Re: NFSv2 boot & OLD_NFSV2

2017-03-21 Thread Baptiste Daroussin
On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: > > > On 20 Mar 2017, at 23:55, Toomas Soome wrote: > > > >> > >> On 20. märts 2017, at 23:53, Rick Macklem wrote: > >> > >> Baptiste Daroussin wrote: > >>> On Mon, Mar 20, 2017 at 08:22:12PM

Re: NFSv2 boot & OLD_NFSV2

2017-03-21 Thread Toomas Soome
> On 21. märts 2017, at 10:50, Daniel Braniss wrote: > > >> On 21 Mar 2017, at 10:13, Baptiste Daroussin > > wrote: >> >> On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: >>> On 20 Mar 2017, at 23:55,

Re: NFSv2 boot & OLD_NFSV2

2017-03-21 Thread Daniel Braniss
> On 21 Mar 2017, at 10:13, Baptiste Daroussin wrote: > > On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: >> >>> On 20 Mar 2017, at 23:55, Toomas Soome wrote: >>> On 20. märts 2017, at 23:53, Rick Macklem

Re: ELF binary type "3" not known.

2017-03-21 Thread Mathieu Arnold
Le 21/03/2017 à 06:22, Chris H a écrit : > On Tue, 21 Mar 2017 13:14:56 +0800 Kevin Lo wrote > >> On Mon, Mar 20, 2017 at 09:11:44PM -0700, Chris H wrote: >>> On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote >>> I'm not sure which of the two

Re: NFSv2 boot & OLD_NFSV2

2017-03-21 Thread Daniel Braniss
> On 20 Mar 2017, at 23:55, Toomas Soome wrote: > >> >> On 20. märts 2017, at 23:53, Rick Macklem wrote: >> >> Baptiste Daroussin wrote: >>> On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote: Hi! The current boot code is

Re: NFSv2 boot & OLD_NFSV2

2017-03-21 Thread Toomas Soome
> On 21. märts 2017, at 10:13, Baptiste Daroussin wrote: > > On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: >> >>> On 20 Mar 2017, at 23:55, Toomas Soome wrote: >>> On 20. märts 2017, at 23:53, Rick Macklem

Re: why are the GEOM secondary GPT tables always corrupt?

2017-03-21 Thread O. Hartmann
On Mon, 20 Mar 2017 19:08:41 -0700 "Chris H" wrote: > I've seen this discussed before, but there were so many > "solutions", I was left feeling this *must* be some sort > of bug in GEOM/gpart. So. I just blew away the tables on > a USB3 flash drive: > > # gpart destroy

Re: ELF binary type "3" not known.

2017-03-21 Thread Gary Jennejohn
On Tue, 21 Mar 2017 10:15:35 +0100 Mathieu Arnold wrote: > Le 21/03/2017 __ 06:22, Chris H a __crit : > > On Tue, 21 Mar 2017 13:14:56 +0800 Kevin Lo wrote > > > >> On Mon, Mar 20, 2017 at 09:11:44PM -0700, Chris H wrote: > >>> On Mon, 20 Mar 2017

Re: process killed: text file modification

2017-03-21 Thread Rick Macklem
Konstantin Belousov wrote: [stuff snipped] > By 'impossible' I mean some arbitrary combination of bytes which were > written by many means to the file at arbitrary moments. In other words, > the file content, or even a single page/block content is not atomic > WRT the client updates. Yes. For

Re: arm64 fork/swap data corruptions: A ~110 line C program demonstrating an example (Pine64+ 2GB context) [Corrected subject: arm64!]

2017-03-21 Thread Mark Millard
On 2017-Mar-18, at 9:10 PM, Mark Millard wrote: > > On 2017-Mar-18, at 5:53 PM, Mark Millard wrote: > >> A new, significant discovery follows. . . >> >> While checking out use of procstat -v I ran >> into the following common property for the 3 >>

Re: effect of strip(1) on du(1)

2017-03-21 Thread Julian Elischer
On 3/3/17 8:31 am, Rodney W. Grimes wrote: On Fri, Mar 3, 2017 at 2:04 AM, Peter Jeremy wrote: On 2017-Mar-02 22:29:46 +0300, Subbsd wrote: During some interval after strip call, du will show 512B for any file. If execute du(1) after strip(1) without

sysctl -a hangs ?

2017-03-21 Thread Kurt Jaeger
Hello, I have a freshly installed/updated FreeBSD 11.0p8 on a supermicro X11SSZ-TLN4F board, and pkg install intel-ixl-kmod and now: sysctl -a hangs. Any quick ideas how to debug this ? -- p...@opsec.eu+49 171 3101372 3 years to go !

Re: sysctl -a hangs ?

2017-03-21 Thread Kurt Jaeger
Hi! > >> I have a freshly installed/updated FreeBSD 11.0p8 on a supermicro > >> X11SSZ-TLN4F board, and > >> > >> pkg install intel-ixl-kmod > >> > >> and now: > >> > >> sysctl -a > >> > >> hangs. Any quick ideas how to debug this ? > > > > If it's just not responding to anything, you can try to

Re: sysctl -a hangs ?

2017-03-21 Thread hiren panchasara
On 03/21/17 at 05:04P, Kurt Jaeger wrote: > Hello, > > I have a freshly installed/updated FreeBSD 11.0p8 on a supermicro > X11SSZ-TLN4F board, and > > pkg install intel-ixl-kmod > > and now: > > sysctl -a > > hangs. Any quick ideas how to debug this ? If it's just not responding to anything,

Re: sysctl -a hangs ?

2017-03-21 Thread Hans Petter Selasky
On 03/21/17 17:14, hiren panchasara wrote: On 03/21/17 at 05:04P, Kurt Jaeger wrote: Hello, I have a freshly installed/updated FreeBSD 11.0p8 on a supermicro X11SSZ-TLN4F board, and pkg install intel-ixl-kmod and now: sysctl -a hangs. Any quick ideas how to debug this ? If it's just not