Re: ctld: only 579 iSCSI targets can be created

2017-10-02 Thread Edward Napierala
Thanks for the packet trace. What happens there is that the Windows initiator logs in, requests Discovery ("SendTargets=All"), receives the list of targets, as expected, and then... sends "SendTargets=All" again, instead of logging off. This results in ctld(8) dropping the session. The initiator

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

2017-10-02 Thread Andriy Gapon
On 01/10/2017 00:38, Harry Schmalzbauer wrote: > Now my striped mirror has all 4 devices healthy available, but all > datasets seem to be lost. > No problem for 450G (99,9_%), but there's a 80M dataset which I'm really > missing :-( If it's not too late now, you may try to experiment with an "unwi

Hengdian Dongyang City

2017-10-02 Thread Qmqvz
RenChengxin ___ 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: panic: Solaris(panic): blkptr invalid CHECKSUM1

2017-10-02 Thread Harry Schmalzbauer
Bezüglich Scott Bennett's Nachricht vom 01.10.2017 15:20 (localtime): > On Sat, 30 Sep 2017 23:38:45 +0200 Harry Schmalzbauer > > wrote: … >> >> OpenIndiana also panics at regular import. >> Unfortunately I don't know the aequivalent of vfs.zfs.recover in OI. >> >> panic[cpu1]/thread=ff

Re: panic: Solaris(panic): blkptr invalid CHECKSUM1

2017-10-02 Thread Harry Schmalzbauer
Bezüglich Andriy Gapon's Nachricht vom 02.10.2017 13:49 (localtime): > On 01/10/2017 00:38, Harry Schmalzbauer wrote: >> Now my striped mirror has all 4 devices healthy available, but all >> datasets seem to be lost. >> No problem for 450G (99,9_%), but there's a 80M dataset which I'm really >> mis

my build time impact of clang 5.0

2017-10-02 Thread Dan Mack
Another significant change in build times this week - not complaining, just my observations on build times; same server doing buildworld during the various phases of compiler changes over the last year or so FWIW: |--+--+---+--+---| | Ver (svn-i

Re: my build time impact of clang 5.0

2017-10-02 Thread Mike Tancsa
On 10/2/2017 2:34 PM, Dan Mack wrote: > > Another significant change in build times this week - not complaining, > just my observations on build times; same server doing buildworld during > the various phases of compiler changes over the last year or so FWIW: Kernel seems to be about the same sin

Re: my build time impact of clang 5.0

2017-10-02 Thread Dan Mack
Mike Tancsa writes: > On 10/2/2017 2:34 PM, Dan Mack wrote: >> >> Another significant change in build times this week - not complaining, >> just my observations on build times; same server doing buildworld during >> the various phases of compiler changes over the last year or so FWIW: > > Kernel

Re: my build time impact of clang 5.0

2017-10-02 Thread Andy Farkas
On 03/10/2017 06:18, Dan Mack wrote: My scripts are pretty coarse grained so I only have timings at the macro build steps so far (buildworld, buildkernel, installkernel, and installworld) I'm going to update them so I can a little more granularity; should be easy to get timings wrapped around t

Re: my build time impact of clang 5.0

2017-10-02 Thread Andriy Gapon
On 02/10/2017 21:34, Dan Mack wrote: > > Another significant change in build times this week - not complaining, > just my observations on build times; same server doing buildworld during > the various phases of compiler changes over the last year or so FWIW: > > |--+--+---