Re: recommendations for file server based zfs appliance

2017-08-18 Thread Outback Dingo 
On Fri, Aug 18, 2017 at 8:03 AM, Stefan Hagen
 wrote:
> * Patrick M. Hausen wrote:
>>>
>>> Am 18.08.2017 um 11:19 schrieb Pete French :
>>> The HP micro servers work very well, and you can pick them up remakably
>>> cheaply [...]
>>> Not sure about ECC memory support there though.
>>
>>
>> They do support ECC, no problem.
>>
>> They are available with different CPU configurations from
>> as Pete said remarkably cheap Celeron D based systems
>> up to Xeon CPUs.
>
>
> I've just sold my Microserver Gen8 (Xeon) just recently.
> It's a beautiful little machine, but I didn't make me happy in the long run.
>
> Reasons:
> - Limited to 8GB Ram in total
> - Only 4 HDDs
> - JBOD support is not great
> - Harddrives are never going to sleep (not supported)
>
> Installing FreeBSD was harder than expected. The machine refused to boot
> FreeBSD
> from the internal non-raid SATA ports. I didn't try FreeNAS though.
>
> Also, in case you go with a Microserver - I think all non-xeon models do not
> support AES-NI, which will cut the throughput in case you plan to encrypt
> your
> drives.
>
> iX-Systems would have been my choice to replace this machine until I found
> out
> that I can build something myself that suits my needs even better.
>
> Note, I was looking at the 8 bay model and I would have to add around $280
> for
> shipping and tax to Germany.
>
> I'm now going for this custom build:
> - Fractal Design Define R5
>   Reason: Silent, enough space for 12 drives
> - SuperMicro MBD-A1SAI-2550F-O
>   Reason: IPMI, ECC, AES-NI, 64GB Ram, Intel NIC, low power consumption
> - 4x 8GB Kingson ECC SODIMM
>   Reason: 16GB modules are not yet available
> - Seasonic X-Series Fanless X-400FL 400W passiv
>   Reason: Fanless -> silent
>
> The complete order was around 1000€
>
> That being said, I'm planning to put an older 3ware controller in JBOD mode
> in
> it and I also have SSDs and drives already. The board has only 6 SATA ports.
> But that would be enough for you.
>
> This might be a little big for you. But maybe it gives you ideas.
>
> Best Regards,
> Stefan
>

Sorry but  need to as do yo want some under powered atom system? or a
core i3i7 cpu and 16 Gbs memoery, with 8 GB ports and 6 SATA ports in
a small custom build.
because thats exactly what we sell and we sell it for less the an XL
 by a few hundred bucs, less the drives. it will easly take 6 3.5
drives and 2 2.5. IF you really
want the specs on a sweet low end system with higher specs then the
miniXL and cheaper also then say a super micro or HP box let me know.

> ___
> 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"
___
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: patch to improve AES-NI performance

2013-08-27 Thread Outback Dingo 
On Sun, Aug 25, 2013 at 10:19 AM, Ollivier Robert robe...@keltia.freenix.fr
 wrote:

 According to Ollivier Robert:
  You are right, I wanted to say r226837 which is the code one.

 FYI I've finally merged r226837,r226839 as r254856 in stable/9 as it is a
 prerequesite to apply jmg's patch.  I've asked re@ whether they would
 consider this for 9.2.  It is very late in the 9.2 release circle but that
 patch has been in 10 for more than a year now...


So this patch can now be applied to STABLE/9 for testing on a local system
since these 3 revisions are now in??


 --
 Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=-
 robe...@keltia.freenix.fr
 In memoriam to Ondine : http://ondine.keltia.net/
 ___
 freebsd-curr...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: status of autotuning freebsd for 9.2

2013-08-19 Thread Outback Dingo 
On Mon, Aug 19, 2013 at 10:26 AM, Alfred Perlstein alf...@ixsystems.comwrote:



 On Aug 19, 2013, at 2:52 AM, Andre Oppermann an...@freebsd.org wrote:

  On 16.08.2013 10:29, Andre Oppermann wrote:
  On 16.08.2013 08:32, Alfred Perlstein wrote:
  Andre, I'm kind of bummed out this didn't make it into 9.2, I'm
 wondering can I commit this to
  9-stable now?  (or is it already in?)
 
  It didn't make it because there was only sparse feedback after the
  call for testers.  There were a couple of replies that it is being
  tested but no statements either way if it was good or not.  Hence
  I erred on the side of caution and refrained from committing it.
 
  Revisiting the history of this after vacation absence actually shows
  that we straddled the release code freeze deadline and you had provided
  good testing feedback.  However the MFC got rejected by RE on the fear
  of introducing unknown regressions into the release process.
 
  Would you do the honors?
 
  Yes, will do later today.
 
  Committed to stable/9 as r254515.
 
  Let me know if there are any issues.

 Thanks Andre.

  Maybe we can do a point release/patch release with this in a few weeks
 for 9.2.1 or 9.2p1 because 9.2 out of the box performance is abysmal not
 only in networking but also disk as maxvnodes is clipped way too small even
 with plenty of ram.


So your saying, 9.2-RELEASE performance suffers degradation against say 9.1
?? are you referring to with this patch enabled? or just in general
9.2-RELEASE


 
  --
  Andre
 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: status of autotuning freebsd for 9.2

2013-08-19 Thread Outback Dingo 
On Mon, Aug 19, 2013 at 12:05 PM, Alfred Perlstein alf...@ixsystems.comwrote:

 Performance is bad for large memory requirements period.

 Vnodes and mbufs on a machine with 24gb ram is limited to the same amount
 as a machine with less than 4GB ram.

 This was fixed in head but not merged back in time.


is there a patch set i can backport on my own, do we know what revision(s)
are required? Ive got boxes with
128GB and 10Gbe Intel... so im willing to do some work..



 This results in poor out of the box performance on 10gige and servers with
 high vnode requirements.

 Sent from my iPhone

 On Aug 19, 2013, at 7:30 AM, Outback Dingo outbackdi...@gmail.com wrote:




 On Mon, Aug 19, 2013 at 10:26 AM, Alfred Perlstein 
 alf...@ixsystems.comwrote:



 On Aug 19, 2013, at 2:52 AM, Andre Oppermann an...@freebsd.org wrote:

  On 16.08.2013 10:29, Andre Oppermann wrote:
  On 16.08.2013 08:32, Alfred Perlstein wrote:
  Andre, I'm kind of bummed out this didn't make it into 9.2, I'm
 wondering can I commit this to
  9-stable now?  (or is it already in?)
 
  It didn't make it because there was only sparse feedback after the
  call for testers.  There were a couple of replies that it is being
  tested but no statements either way if it was good or not.  Hence
  I erred on the side of caution and refrained from committing it.
 
  Revisiting the history of this after vacation absence actually shows
  that we straddled the release code freeze deadline and you had provided
  good testing feedback.  However the MFC got rejected by RE on the fear
  of introducing unknown regressions into the release process.
 
  Would you do the honors?
 
  Yes, will do later today.
 
  Committed to stable/9 as r254515.
 
  Let me know if there are any issues.

 Thanks Andre.

  Maybe we can do a point release/patch release with this in a few weeks
 for 9.2.1 or 9.2p1 because 9.2 out of the box performance is abysmal not
 only in networking but also disk as maxvnodes is clipped way too small even
 with plenty of ram.


 So your saying, 9.2-RELEASE performance suffers degradation against say
 9.1 ?? are you referring to with this patch enabled? or just in general
 9.2-RELEASE


 
  --
  Andre
 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: status of autotuning freebsd for 9.2

2013-08-19 Thread Outback Dingo 
On Mon, Aug 19, 2013 at 12:17 PM, Andre Oppermann an...@freebsd.org wrote:

 On 19.08.2013 18:09, Outback Dingo wrote:




 On Mon, Aug 19, 2013 at 12:05 PM, Alfred Perlstein alf...@ixsystems.com
 mailto:alf...@ixsystems.com wrote:

 Performance is bad for large memory requirements period.

 Vnodes and mbufs on a machine with 24gb ram is limited to the same
 amount as a machine with less
 than 4GB ram.

 This was fixed in head but not merged back in time.


 is there a patch set i can backport on my own, do we know what
 revision(s) are required? Ive got
 boxes with
 128GB and 10Gbe Intel... so im willing to do some work..


 I have committed it to 9-stable this morning with r254515.  No backporting
 necessary.


Okay so wait, your saying the autotune commit this morning resolves Alfreds
claims of abysmal
performance in general, or is there other additional fixes in head aside
from the autotune hes mentioning


 --
 Andre

  This results in poor out of the box performance on 10gige and servers
 with high vnode requirements.

 Sent from my iPhone

 On Aug 19, 2013, at 7:30 AM, Outback Dingo outbackdi...@gmail.com
 mailto:outbackdi...@gmail.com** wrote:




 On Mon, Aug 19, 2013 at 10:26 AM, Alfred Perlstein 
 alf...@ixsystems.com
 mailto:alf...@ixsystems.com wrote:



 On Aug 19, 2013, at 2:52 AM, Andre Oppermann an...@freebsd.org
 mailto:an...@freebsd.org wrote:

  On 16.08.2013 10:29, Andre Oppermann wrote:
  On 16.08.2013 08:32, Alfred Perlstein wrote:
  Andre, I'm kind of bummed out this didn't make it into 9.2,
 I'm wondering can I commit
 this to
  9-stable now?  (or is it already in?)
 
  It didn't make it because there was only sparse feedback
 after the
  call for testers.  There were a couple of replies that it is
 being
  tested but no statements either way if it was good or not.
  Hence
  I erred on the side of caution and refrained from committing
 it.
 
  Revisiting the history of this after vacation absence actually
 shows
  that we straddled the release code freeze deadline and you had
 provided
  good testing feedback.  However the MFC got rejected by RE on
 the fear
  of introducing unknown regressions into the release process.
 
  Would you do the honors?
 
  Yes, will do later today.
 
  Committed to stable/9 as r254515.
 
  Let me know if there are any issues.

 Thanks Andre.

  Maybe we can do a point release/patch release with this in a
 few weeks for 9.2.1 or 9.2p1
 because 9.2 out of the box performance is abysmal not only in
 networking but also disk as
 maxvnodes is clipped way too small even with plenty of ram.


 So your saying, 9.2-RELEASE performance suffers degradation against
 say 9.1 ?? are you
 referring to with this patch enabled? or just in general 9.2-RELEASE

 
  --
  Andre
 
 __**_
 freebsd-stable@freebsd.org 
 mailto:freebsd-stable@**freebsd.orgfreebsd-stable@freebsd.org
 mailing list

 
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**stablehttp://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscribe@**
 freebsd.org freebsd-stable-unsubscr...@freebsd.org
 
 mailto:freebsd-stable-**unsubscr...@freebsd.orgfreebsd-stable-unsubscr...@freebsd.org
 





___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: status of autotuning freebsd for 9.2

2013-08-16 Thread Outback Dingo 
On Fri, Aug 16, 2013 at 10:08 AM, Harald Schmalzbauer 
h.schmalzba...@omnilan.de wrote:

  Bezüglich Pascal Drecker's Nachricht vom 16.07.2013 21:42 (localtime):
  ...
  IMHO, this is considered a new feature, and not a critical bug
 fix. re@
  asked from the start of the code slush to avoid new features, and
 at
  this point, it is too late. It is not worth introducing possible
  regressions, which will only delay the 9.2-RELEASE.
 
  Glen
 
  OK, then we need a release notes telling people a sane value for
  nmbclusters and friends so that they know how to make 10gigE work.
 
  I'll poll my team for a value if someone else has one, that would
 be
 even
  better.
 
  --
  Alfred Perlstein
  VP Software Engineering, iXsystems
 
 
 Is there a possibility that a separate unofficial patch set could be
 released for people who want the autotuning but do not want to run 9
 stable after 9.2 is released.
 I would like the autotuning, but i am a little reluctent to use other
 stable stuff i will get when tracking stable.
 
 Regards
 Johan
 
 Hi,
 
 I think that's a good point.
 
 In our company, it�s not allowed to use the stable tree for any
 production system. Little and useful patches are still allowed.
 
 Having a central point with a description of each patch it would be
 much easier to update the release version with the needed patches.

 You're welcome using my deploy-tools patchsets.
 I'm deploying RELENG only, but with local patchset-policy. Originally,
 these are automtically handled during build-process with deploy-tools,
 but of course you can selective/manually apply the desired patches from
 the local-patches directory:

 ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools/

 Best regards,


can you maybe define what exactly, this is and or where the specific
patches are derived? Ive seen the autotune
but whats the rest in here??


 -Harry


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: status of autotuning freebsd for 9.2

2013-07-15 Thread Outback Dingo 
On Mon, Jul 15, 2013 at 10:13 AM, Glen Barber g...@freebsd.org wrote:

 On Mon, Jul 15, 2013 at 05:48:40AM -0700, Alfred Perlstein wrote:
  On 7/15/13 5:44 AM, Andre Oppermann wrote:
  On 15.07.2013 08:38, Andre Oppermann wrote:
  On 13.07.2013 09:47, Alfred Perlstein wrote:
  Andre, we have a number of people running this patch in the
  following configurations:
  
  6-8GB ram + 10gigE ethernet using iozone over NFS.
  
  As you haven't seen any problems yet I've asked RE to green light
  the MFC.
  
  RE has rejected the MFC out of fears for unexpected regressions.
  
 
  That is unfortunate.  I guess re@ doesn't understand that FreeBSD
  9.2 will be unusable out of the box for doing 10gigE for more than a
  few microseconds.
 
  Can we not just do my original patch that has the check for 64bit
  pointers before unscaling maxusers?  That would be dirt simple and
  just work with minimal risk.
 

 IMHO, this is considered a new feature, and not a critical bug fix.  re@
 asked from the start of the code slush to avoid new features, and at
 this point, it is too late.  It is not worth introducing possible
 regressions, which will only delay the 9.2-RELEASE.


Its kinda sad that it wount be MFC'd though I understand, it does help
10Gbe environments
Id give it a vote, and its perceived to have possible regressions, though
it might need more testing
other then a handful of users. we can always patch until its
MFCd



 Glen


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Stable/9 from today mpssas_scsiio timeouts

2013-07-09 Thread Outback Dingo 
as of stable today im seeing alot of new mps time outs

9.1-STABLE FreeBSD 9.1-STABLE #0 r253035M: Mon Jul  8 16:34:28 UTC 2013
root@:/usr/obj/nas/usr/src/sys/

mps1@pci0:130:0:0:  class=0x010700 card=0x30201000 chip=0x00721000
rev=0x03 hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]'
class  = mass storage
subclass   = SAS


mps0: mpssas_scsiio_timeout checking sc 0xff8002145000 cm
0xff80021a6b78
(probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983
command timeout cm 0xff80021a6b78 ccb 0xfe002bb5f800
mps0: mpssas_alloc_tm freezing simq
mps0: timedout cm 0xff80021a6b78 allocated tm 0xff80021587b0
(probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983
completed timedout cm 0xff80021a6b78 ccb 0xfe002bb5f800 during
recovery ioc 8048 scsi 0 state c xfer 0
(noperiph:mps0:0:40:0): SMID 6 abort TaskMID 983 status 0x4a code 0x0 count
1
(noperiph:mps0:0:40:0): SMID 6 finished recovery after aborting TaskMID 983
mps0: mpssas_free_tm releasing simq
(probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00
(probe40:mps0:0:40:0): CAM status: Command timeout
(probe40:mps0:0:40:0): Retrying command
mps1: mpssas_scsiio_timeout checking sc 0xff8002384000 cm
0xff80023e5b78
(probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983
command timeout cm 0xff80023e5b78 ccb 0xfe002be14800
mps1: mpssas_alloc_tm freezing simq
mps1: timedout cm 0xff80023e5b78 allocated tm 0xff80023977b0
(probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983
completed timedout cm 0xff80023e5b78 ccb 0xfe002be14800 during
recovery ioc 8048 scsi 0 state c xfer 0
(noperiph:mps1:0:37:0): SMID 6 abort TaskMID 983 status 0x4a code 0x0 count
1
(noperiph:mps1:0:37:0): SMID 6 finished recovery after aborting TaskMID 983
mps1: mpssas_free_tm releasing simq
(probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00
(probe292:mps1:0:37:0): CAM status: Command timeout
(probe292:mps1:0:37:0): Retrying command
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Stable/9 from today mpssas_scsiio timeouts

2013-07-09 Thread Outback Dingo 
On Tue, Jul 9, 2013 at 8:39 AM, Jeremy Chadwick j...@koitsu.org wrote:

 On Tue, Jul 09, 2013 at 05:32:39AM -0400, Outback Dingo wrote:
  as of stable today im seeing alot of new mps time outs
 
  9.1-STABLE FreeBSD 9.1-STABLE #0 r253035M: Mon Jul  8 16:34:28 UTC 2013
  root@:/usr/obj/nas/usr/src/sys/
 
  mps1@pci0:130:0:0:  class=0x010700 card=0x30201000 chip=0x00721000
  rev=0x03 hdr=0x00
  vendor = 'LSI Logic / Symbios Logic'
  device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]'
  class  = mass storage
  subclass   = SAS
 
 
  mps0: mpssas_scsiio_timeout checking sc 0xff8002145000 cm
  0xff80021a6b78
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983
  command timeout cm 0xff80021a6b78 ccb 0xfe002bb5f800
  mps0: mpssas_alloc_tm freezing simq
  mps0: timedout cm 0xff80021a6b78 allocated tm 0xff80021587b0
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 983
  completed timedout cm 0xff80021a6b78 ccb 0xfe002bb5f800 during
  recovery ioc 8048 scsi 0 state c xfer 0
  (noperiph:mps0:0:40:0): SMID 6 abort TaskMID 983 status 0x4a code 0x0
 count
  1
  (noperiph:mps0:0:40:0): SMID 6 finished recovery after aborting TaskMID
 983
  mps0: mpssas_free_tm releasing simq
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00
  (probe40:mps0:0:40:0): CAM status: Command timeout
  (probe40:mps0:0:40:0): Retrying command
  mps1: mpssas_scsiio_timeout checking sc 0xff8002384000 cm
  0xff80023e5b78
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID
 983
  command timeout cm 0xff80023e5b78 ccb 0xfe002be14800
  mps1: mpssas_alloc_tm freezing simq
  mps1: timedout cm 0xff80023e5b78 allocated tm 0xff80023977b0
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID
 983
  completed timedout cm 0xff80023e5b78 ccb 0xfe002be14800 during
  recovery ioc 8048 scsi 0 state c xfer 0
  (noperiph:mps1:0:37:0): SMID 6 abort TaskMID 983 status 0x4a code 0x0
 count
  1
  (noperiph:mps1:0:37:0): SMID 6 finished recovery after aborting TaskMID
 983
  mps1: mpssas_free_tm releasing simq
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00
  (probe292:mps1:0:37:0): CAM status: Command timeout
  (probe292:mps1:0:37:0): Retrying command

 1. What revision were you running before (i.e. what were you on prior to
 the upgrade)?



i was on 253035



 2. Something in your /usr/src differs from stock r253035, hence the M
 at the end.  What is it?

 a KERNEL configuration



 Answer to #1 will help me narrow down the commits; there have been CAM
 and mps changes fairly recently.  Otherwise you can dig through the
 commits yourself (you'll need to go through many, many pages, as there
 was a recent massive influx of SCTP changes (50+ commits)):

 http://www.freshbsd.org/?branch=RELENG_9project=freebsd

 --
 | Jeremy Chadwick   j...@koitsu.org |
 | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
 | Making life hard for others since 1977. PGP 4BD6C0CB |


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Stable/9 from today mpssas_scsiio timeouts

2013-07-09 Thread Outback Dingo 
On Tue, Jul 9, 2013 at 9:44 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Tue, Jul 9, 2013 at 8:39 AM, Jeremy Chadwick j...@koitsu.org wrote:

 On Tue, Jul 09, 2013 at 05:32:39AM -0400, Outback Dingo wrote:
  as of stable today im seeing alot of new mps time outs
 
  9.1-STABLE FreeBSD 9.1-STABLE #0 r253035M: Mon Jul  8 16:34:28 UTC 2013
  root@:/usr/obj/nas/usr/src/sys/
 
  mps1@pci0:130:0:0:  class=0x010700 card=0x30201000 chip=0x00721000
  rev=0x03 hdr=0x00
  vendor = 'LSI Logic / Symbios Logic'
  device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]'
  class  = mass storage
  subclass   = SAS
 
 
  mps0: mpssas_scsiio_timeout checking sc 0xff8002145000 cm
  0xff80021a6b78
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID
 983
  command timeout cm 0xff80021a6b78 ccb 0xfe002bb5f800
  mps0: mpssas_alloc_tm freezing simq
  mps0: timedout cm 0xff80021a6b78 allocated tm 0xff80021587b0
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID
 983
  completed timedout cm 0xff80021a6b78 ccb 0xfe002bb5f800 during
  recovery ioc 8048 scsi 0 state c xfer 0
  (noperiph:mps0:0:40:0): SMID 6 abort TaskMID 983 status 0x4a code 0x0
 count
  1
  (noperiph:mps0:0:40:0): SMID 6 finished recovery after aborting TaskMID
 983
  mps0: mpssas_free_tm releasing simq
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00
  (probe40:mps0:0:40:0): CAM status: Command timeout
  (probe40:mps0:0:40:0): Retrying command
  mps1: mpssas_scsiio_timeout checking sc 0xff8002384000 cm
  0xff80023e5b78
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID
 983
  command timeout cm 0xff80023e5b78 ccb 0xfe002be14800
  mps1: mpssas_alloc_tm freezing simq
  mps1: timedout cm 0xff80023e5b78 allocated tm 0xff80023977b0
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID
 983
  completed timedout cm 0xff80023e5b78 ccb 0xfe002be14800 during
  recovery ioc 8048 scsi 0 state c xfer 0
  (noperiph:mps1:0:37:0): SMID 6 abort TaskMID 983 status 0x4a code 0x0
 count
  1
  (noperiph:mps1:0:37:0): SMID 6 finished recovery after aborting TaskMID
 983
  mps1: mpssas_free_tm releasing simq
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00
  (probe292:mps1:0:37:0): CAM status: Command timeout
  (probe292:mps1:0:37:0): Retrying command

 1. What revision were you running before (i.e. what were you on prior to
 the upgrade)?



 Sorry I was on 252595 from July 3



 2. Something in your /usr/src differs from stock r253035, hence the M
 at the end.  What is it?

 a KERNEL configuration



 Answer to #1 will help me narrow down the commits; there have been CAM
 and mps changes fairly recently.  Otherwise you can dig through the
 commits yourself (you'll need to go through many, many pages, as there
 was a recent massive influx of SCTP changes (50+ commits)):

 http://www.freshbsd.org/?branch=RELENG_9project=freebsd

 --
 | Jeremy Chadwick   j...@koitsu.org |
 | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
 | Making life hard for others since 1977. PGP 4BD6C0CB |



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Stable/9 from today mpssas_scsiio timeouts

2013-07-09 Thread Outback Dingo 
On Tue, Jul 9, 2013 at 10:46 AM, Jeremy Chadwick j...@koitsu.org wrote:

 On Tue, Jul 09, 2013 at 09:47:01AM -0400, Outback Dingo wrote:
  On Tue, Jul 9, 2013 at 9:44 AM, Outback Dingo outbackdi...@gmail.com
 wrote:
   On Tue, Jul 9, 2013 at 8:39 AM, Jeremy Chadwick j...@koitsu.org
 wrote:
  
   On Tue, Jul 09, 2013 at 05:32:39AM -0400, Outback Dingo wrote:
as of stable today im seeing alot of new mps time outs
   
9.1-STABLE FreeBSD 9.1-STABLE #0 r253035M: Mon Jul  8 16:34:28 UTC
 2013
root@:/usr/obj/nas/usr/src/sys/
   
mps1@pci0:130:0:0:  class=0x010700 card=0x30201000
 chip=0x00721000
rev=0x03 hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]'
class  = mass storage
subclass   = SAS
   
   
mps0: mpssas_scsiio_timeout checking sc 0xff8002145000 cm
0xff80021a6b78
(probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36
 SMID
   983
command timeout cm 0xff80021a6b78 ccb 0xfe002bb5f800
mps0: mpssas_alloc_tm freezing simq
mps0: timedout cm 0xff80021a6b78 allocated tm 0xff80021587b0
(probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36
 SMID
   983
completed timedout cm 0xff80021a6b78 ccb 0xfe002bb5f800
 during
recovery ioc 8048 scsi 0 state c xfer 0
(noperiph:mps0:0:40:0): SMID 6 abort TaskMID 983 status 0x4a code
 0x0
   count
1
(noperiph:mps0:0:40:0): SMID 6 finished recovery after aborting
 TaskMID
   983
mps0: mpssas_free_tm releasing simq
(probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00
(probe40:mps0:0:40:0): CAM status: Command timeout
(probe40:mps0:0:40:0): Retrying command
mps1: mpssas_scsiio_timeout checking sc 0xff8002384000 cm
0xff80023e5b78
(probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36
 SMID
   983
command timeout cm 0xff80023e5b78 ccb 0xfe002be14800
mps1: mpssas_alloc_tm freezing simq
mps1: timedout cm 0xff80023e5b78 allocated tm 0xff80023977b0
(probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36
 SMID
   983
completed timedout cm 0xff80023e5b78 ccb 0xfe002be14800
 during
recovery ioc 8048 scsi 0 state c xfer 0
(noperiph:mps1:0:37:0): SMID 6 abort TaskMID 983 status 0x4a code
 0x0
   count
1
(noperiph:mps1:0:37:0): SMID 6 finished recovery after aborting
 TaskMID
   983
mps1: mpssas_free_tm releasing simq
(probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00
(probe292:mps1:0:37:0): CAM status: Command timeout
(probe292:mps1:0:37:0): Retrying command
  
   1. What revision were you running before (i.e. what were you on prior
 to
   the upgrade)?
  
  
  
   Sorry I was on 252595 from July 3

 And does rolling back to r252595 resolve the problem for you?

 Because the only commit I see between r253035 and r252595 that might
 account for some kind of behavioural change, unless I missed one while
 skimming the commit history, is the following:

 r252730 -- http://www.freshbsd.org/commit/freebsd/r252730

 If at all possible, please try updating to r253037 or newer to see
 if that has some effect/improvement.  Why I mention that commit:

 r253037 -- http://www.freshbsd.org/commit/freebsd/r253037

 Because the only mps(4) changes done in recent days are:

 http://svnweb.freebsd.org/base/stable/9/sys/dev/mps/mps_sas.c?view=log

 r253037
 r251899
 r251874


i can say this its between July 4, and 253048, im rolling back to 252723 to
validate a good known working state




 Else I'd say what you're experiencing is legitimate/unrelated to kernel
 changes.  I can only speculate.

 The messages to me indicate that some part of the kernel is submitting a
 SCSI INQUIRY request to the underlying device(s) which results in a CAM
 timeout, i.e. the disk attached to the controller did not respond
 promptly (while the controller seemed to be alive/well).

 If these disks (which we do not know the type of -- no dmesg provided,
 etc.) are SSDs then TRIM behaviour is possibly causing the drive to take
 too long to perform its TRIM cleanup, or, the drives themselves are
 doing some kind of garbage collection which is taking quite a long time.

 Steven et all may have a different (and almost certainly more accurate)
 analysis.

 It would really help if you could provide dmesg from the machine, as
 well as any details about your setup (if ZFS, zpool status, etc.), in
 addition to (if SSDs) sysctl -a | grep -i trim.  All this matters.

 --
 | Jeremy Chadwick   j...@koitsu.org |
 | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
 | Making life hard for others since 1977. PGP 4BD6C0CB |


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr

Re: Stable/9 from today mpssas_scsiio timeouts

2013-07-09 Thread Outback Dingo 
On Tue, Jul 9, 2013 at 11:30 AM, Jeremy Chadwick j...@koitsu.org wrote:

 On Tue, Jul 09, 2013 at 11:20:45AM -0400, Outback Dingo wrote:
  On Tue, Jul 9, 2013 at 10:46 AM, Jeremy Chadwick j...@koitsu.org wrote:
 
   On Tue, Jul 09, 2013 at 09:47:01AM -0400, Outback Dingo wrote:
On Tue, Jul 9, 2013 at 9:44 AM, Outback Dingo 
 outbackdi...@gmail.com
   wrote:
 On Tue, Jul 9, 2013 at 8:39 AM, Jeremy Chadwick j...@koitsu.org
   wrote:

 On Tue, Jul 09, 2013 at 05:32:39AM -0400, Outback Dingo wrote:
  as of stable today im seeing alot of new mps time outs
 
  9.1-STABLE FreeBSD 9.1-STABLE #0 r253035M: Mon Jul  8 16:34:28
 UTC
   2013
  root@:/usr/obj/nas/usr/src/sys/
 
  mps1@pci0:130:0:0:  class=0x010700 card=0x30201000
   chip=0x00721000
  rev=0x03 hdr=0x00
  vendor = 'LSI Logic / Symbios Logic'
  device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]'
  class  = mass storage
  subclass   = SAS
 
 
  mps0: mpssas_scsiio_timeout checking sc 0xff8002145000 cm
  0xff80021a6b78
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36
   SMID
 983
  command timeout cm 0xff80021a6b78 ccb 0xfe002bb5f800
  mps0: mpssas_alloc_tm freezing simq
  mps0: timedout cm 0xff80021a6b78 allocated tm
 0xff80021587b0
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36
   SMID
 983
  completed timedout cm 0xff80021a6b78 ccb 0xfe002bb5f800
   during
  recovery ioc 8048 scsi 0 state c xfer 0
  (noperiph:mps0:0:40:0): SMID 6 abort TaskMID 983 status 0x4a
 code
   0x0
 count
  1
  (noperiph:mps0:0:40:0): SMID 6 finished recovery after aborting
   TaskMID
 983
  mps0: mpssas_free_tm releasing simq
  (probe40:mps0:0:40:0): INQUIRY. CDB: 12 00 00 00 24 00
  (probe40:mps0:0:40:0): CAM status: Command timeout
  (probe40:mps0:0:40:0): Retrying command
  mps1: mpssas_scsiio_timeout checking sc 0xff8002384000 cm
  0xff80023e5b78
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length
 36
   SMID
 983
  command timeout cm 0xff80023e5b78 ccb 0xfe002be14800
  mps1: mpssas_alloc_tm freezing simq
  mps1: timedout cm 0xff80023e5b78 allocated tm
 0xff80023977b0
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00 length
 36
   SMID
 983
  completed timedout cm 0xff80023e5b78 ccb 0xfe002be14800
   during
  recovery ioc 8048 scsi 0 state c xfer 0
  (noperiph:mps1:0:37:0): SMID 6 abort TaskMID 983 status 0x4a
 code
   0x0
 count
  1
  (noperiph:mps1:0:37:0): SMID 6 finished recovery after aborting
   TaskMID
 983
  mps1: mpssas_free_tm releasing simq
  (probe292:mps1:0:37:0): INQUIRY. CDB: 12 00 00 00 24 00
  (probe292:mps1:0:37:0): CAM status: Command timeout
  (probe292:mps1:0:37:0): Retrying command

 1. What revision were you running before (i.e. what were you on
 prior
   to
 the upgrade)?



 Sorry I was on 252595 from July 3
  
   And does rolling back to r252595 resolve the problem for you?
  
   Because the only commit I see between r253035 and r252595 that might
   account for some kind of behavioural change, unless I missed one while
   skimming the commit history, is the following:
  
   r252730 -- http://www.freshbsd.org/commit/freebsd/r252730
  
   If at all possible, please try updating to r253037 or newer to see
   if that has some effect/improvement.  Why I mention that commit:
  
   r253037 -- http://www.freshbsd.org/commit/freebsd/r253037
  
   Because the only mps(4) changes done in recent days are:
  
   http://svnweb.freebsd.org/base/stable/9/sys/dev/mps/mps_sas.c?view=log
  
   r253037
   r251899
   r251874
  
 
  i can say this its between July 4, and 253048, im rolling back to 252723
 to
  validate a good known working state

 Looking at your dmesg, it looks like the errors might be for SAS ports
 which don't have any actual devices (disks) attached to them, yet parts
 of the kernel (not sure which layer) are still trying to submit INQUIRY
 commands to those ports as if they did have disks attached.

 It looks like you see this behaviour on boot up, and then later during
 normal operation at some point (a LUN scan or rescan or bus taste
 might cause this to happen; for example I know that zpool import in
 effect can sometimes cause this behaviour -- on one of my systems zpool
 import would cause the servers' floppy drive to spin up/chunk briefly).

 I'm hoping Steven or mav@ might be able to confirm/deny my theory here.


I see it even trying to write to the pool via NFS or FTP, which even times
out on large files
now, it was all working, and there are 2 controllers setup in an HA
configuration, but they did
work fine before, so ill roll back and try an earlier kernel then walk
forward till i hit the problem.
my only issue was i moved forward

Re: status of autotuning freebsd for 9.2

2013-07-08 Thread Outback Dingo 
On Mon, Jul 8, 2013 at 10:37 AM, Andre Oppermann an...@freebsd.org wrote:

 On 07.07.2013 20:24, Alfred Perlstein wrote:

 On 7/7/13 1:34 AM, Andre Oppermann wrote:

 Can you help me with with testing?

  Yes.  Please give me your proposed changes and I'll stand up a machine
 and give feedback.


 http://people.freebsd.org/~**andre/mfc-autotuning-20130708.**diffhttp://people.freebsd.org/~andre/mfc-autotuning-20130708.diff

 This is functional bundle MFC of these original commits:

 MFC r242029 (alfred):

  Allow autotune maxusers  384 on 64 bit machines.

 MFC r242847 (alfred):

  Allow maxusers to scale on machines with large address space.

 MFC r243631 (andre):

  Base the mbuf related limits on the available physical memory or
  kernel memory, whichever is lower.  The overall mbuf related memory
  limit must be set so that mbufs (and clusters of various sizes)
  can't exhaust physical RAM or KVM.

  At the same time divorce maxfiles from maxusers and set maxfiles to
  physpages / 8 with a floor based on maxusers.  This way busy servers
  can make use of the significantly increased mbuf limits with a much
  larger number of open sockets.

 MFC r243639 (andre):

  Complete r243631 by applying the remainder of kern_mbuf.c that got
  lost while merging into the commit tree.

 MFC r243668 (andre):

  Using a long is the wrong type to represent the realmem and maxmbufmem
  variable as they may overflow on i386/PAE and i386 with  2GB RAM.

 MFC r243995, r243996, r243997 (pjd):

  Style cleanups, Make use of the fact that uma_zone_set_max(9) already
  returns actual limit set.

 MFC r244080 (andre):

  Prevent long type overflow of realmem calculation on ILP32 by forcing
  calculation to be in quad_t space.  Fix style issue with second parameter
  to qmin().

 MFC r245469 (alfred):

  Do not autotune ncallout to be greater than 18508.

 MFC r245575 (andre):

  Move the mbuf memory limit calculations from init_param2() to
  tunable_mbinit() where it is next to where it is used later.

 MFC r246207 (andre):

  Remove unused VM_MAX_AUTOTUNE_NMBCLUSTERS define.

 MFC r249843 (andre):

  Base the calculation of maxmbufmem in part on kmem_map size
  instead of kernel_map size to prevent kernel memory exhaustion
  by mbufs and a subsequent panic on physical page allocation
  failure.



would it be safe to throw a couple of high end storage systems into this
testing pool ??
each has 128G Memory, and dual quad core procs, with 10GB Intel interfaces
all they
are design to do it samba and nfs and ive been fighting performance with
samba and
nfs on these systems, Id be curious if autotuning might help, to be honest,
theres so
much to tweak for samba, nfs, zfs alone in different formats, im surprised
anyone has
it running efficiently.


 --
 Andre


 __**_
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**stablehttp://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to 
 freebsd-stable-unsubscribe@**freebsd.orgfreebsd-stable-unsubscr...@freebsd.org
 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: FreeBSD Quarterly Status Report, January-March 2013

2013-05-12 Thread Outback Dingo 
 __


 FreeNAS

URL: http://www.FreeNAS.org/

Contact: Alfred Perlstein alf...@freebsd.org
Contact: Josh Paetzel jpaet...@freebsd.org

FreeNAS 8.3.1-RELEASE-p2 will hit Sourceforge the second week of April,
and should end up as the last FreeNAS release based on FreeBSD 8.X It's
currently the only Free Open Source NAS product available with any form
of ZFS encryption (provided by GELI).

 Open tasks:

 1. The team is hard at work on getting a FreeBSD 9.X-based release of
FreeNAS ready. Currently there are several nightly snapshots
available.
 2. Add HAST to the webinterface.
 3. Migrate to NFSv4.
 4. Integrate foundation sponsored kernel iSCSI target.



Uhmm WHAT??? FreeNAS is not the only Free Open Source NAS product
available with any form
   of ZFS encryption (provided by GELI). NAS4Free has been doing it.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: Make buildworld broken on RELENG_9?

2013-04-18 Thread Outback Dingo 
On Thu, Apr 18, 2013 at 4:59 PM, Paul van der Zwan pa...@vanderzwan.orgwrote:

 Since last weekend or so my make buildworld terminate at the following
 error:
 === share/tabset (all)
 uudecode  /usr/src/share/tabset/3101.uu
 uudecode  /usr/src/share/tabset/9837.uu
 uudecode  /usr/src/share/tabset/aa.uu
 uudecode  /usr/src/share/tabset/aed512.uu
 uudecode  /usr/src/share/tabset/beehive.uu
 uudecode  /usr/src/share/tabset/diablo.uu
 uudecode  /usr/src/share/tabset/dtc382.uu
 uudecode  /usr/src/share/tabset/hp700-wy.uu
 uudecode  /usr/src/share/tabset/ibm3101.uu
 uudecode  /usr/src/share/tabset/std.uu
 uudecode  /usr/src/share/tabset/stdcrt.uu
 uudecode  /usr/src/share/tabset/tandem653.uu
 uudecode  /usr/src/share/tabset/teleray.uu
 uudecode  /usr/src/share/tabset/vt100.uu
 uudecode  /usr/src/share/tabset/vt100-w.uu
 uudecode  /usr/src/share/tabset/wyse-adds.uu
 uudecode  /usr/src/share/tabset/xerox1720.uu
 uudecode  /usr/src/share/tabset/xerox1730.uu
 uudecode  /usr/src/share/tabset/xerox1730-lm.uu
 uudecode  /usr/src/share/tabset/zenith29.uu
 === share/termcap (all)
 gzip -cn /usr/src/share/termcap/termcap.5  termcap.5.gz
 TERM=dumb TERMCAP=dumb: ex - /usr/src/share/termcap/termcap.src 
 /usr/src/share/termcap/reorder
 script, 2: Pattern not found
 *** [termcap] Error code 1

 Stop in /usr/src/share/termcap.
 *** [all] Error code 1

 Stop in /usr/src/share.
 *** [share.all__D] Error code 1

 Stop in /usr/src.
 *** [everything] Error code 1

 Stop in /usr/src.
 *** [buildworld] Error code 1

 Stop in /usr/src.

 Even after updateing /usr/src using svn I keep this.
 Before this build I updated it:
 $ cd /data/src ; svn up ;
 Usys/sys/vnode.h
  U   sys/sys
 Usys/geom/geom_disk.c
 Usys/geom/geom_int.h
 Usys/geom/geom_subr.c
 Usys/geom/geom_dev.c
 Usys/geom/geom_event.c
 Usys/ufs/ufs/ufs_lookup.c
 Usys/ufs/ffs/ffs_softdep.c
 Usys/cam/cam_xpt.c
 Usys/cam/cam_periph.c
 Usys/cam/cam_sim.c
 Usys/cam/cam_periph.h
 Usys/cam/cam_sim.h
 Usys/cam/scsi/scsi_xpt.c
 Usys/cam/scsi/scsi_da.c
 Usys/cam/scsi/scsi_pass.c
 Usys/cam/scsi/scsi_cd.c
 Usys/cam/ata/ata_da.c
 Usys/cam/ata/ata_all.c
 Usys/cam/ata/ata_xpt.c
 Usys/dev/usb/controller/xhci_pci.c
  U   sys/dev
 Usys/kern/vfs_cache.c
  U   sys
 Updated to revision 249624.

 /etc/make.conf is almost empty :
 $ cat /etc/make.conf
 KERNCONF=vbox
 CFLAGS= -O2 -fno-strict-aliasing -pipe
 COPTFLAGS= -O -pipe

 # added by use.perl 2013-03-12 18:50:12
 PERL_VERSION=5.14.2


 Any ideas ?

 Paul

 Odd because i just completed a build world kernel this morning

svn info
Path: .
Working Copy Root Path: /usr/src
URL: http://svn.freebsd.org/base/stable/9
Repository Root: http://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 249621
Node Kind: directory
Schedule: normal
Last Changed Author: mav
Last Changed Rev: 249621
Last Changed Date: 2013-04-18 11:13:48 + (Thu, 18 Apr 2013)



 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org