Re: Portsnap no updates since 3/31/2021 ?

[Charles Sprickman via freebsd-stable]

> On Apr 6, 2021, at 7:10 AM, Gary Palmer  wrote:
> 
> On Tue, Apr 06, 2021 at 06:49:17AM -0400, Robert Blayzor via freebsd-stable 
> wrote:
>> I have several servers running 11.4 and 12.2 that do nightly portsnap
>> updates and the last time they've seen anything new is 3/31/2021, since
>> then, nothing.
>> 
>> This seems highly unusual since seems like there was always SOMETHING
>> updated daily now nothing.
> 
> git transition
> 
> https://wiki.freebsd.org/git 

Is portsnap still going to be supported?

I was noticing my local ports tree (which autoupdates every night with 
portsnap) was looking pretty dated, so I started googling and found talk on the 
forums that portsnap was going away (this was late 2020) and folks were 
suggesting svnlite and fetching updates via svn. Based on that, I just nuked my 
ports tree and grabbed it again via git, which seems to have worked.

What’s odd is that looking at that wiki entry, this port should have been up to 
date if I was using portsnap:

https://www.freshports.org/multimedia/plexmediaserver-plexpass/ 


But portsnap kept insisting that I was up to date even though I was seeing 
version 1.21.3.4015…

Anyhow, if anyone can confirm portsnap status, I’d love to know what the 
official line is and whether I should expect to see it around for awhile.

Is the git transition impacting freebsd-update at all? etcupdate?

Thanks,

Charles

> 
> Regular service should resume soon
> 
> Regards,
> 
> Gary
> ___
> 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: Deprecating base system ftpd?

[Charles Sprickman via freebsd-stable]

> On Apr 5, 2021, at 3:01 PM, Patrick M. Hausen  wrote:
> 
> Hi all,
> 
> I absolutely freaked out when Apple removed the telnet and ftp clients
> from Mac OS and I needed to reinstall them via MacPorts.

Yep, and what I think many miss IRT to the stock ftpd is that it’s dumb simple 
and “just works”.

For web hosting stuff I generally use something like Proftpd or vsftpd, and, 
IMHO, that’s when you should have to expend brain power to choose something 
from ports - when your use-case (supporting hosting customers, virtual users, 
etc.) requires a non-trivial ftp implementation.

Also I can count on my left hand the number of web hosting customers I’ve run 
into that actually use scp for sftp or even know what that is. They’re using 
the same ftp client they’ve always used (ws-ftp quite often) and the last thing 
they want to do is learn something new.

> People who manage any larger collection of networking gear *depend*
> on these outdated but simple services. Client and server side alike.

I frequently work with people who have limited budgets, and I don’t think I’m 
alone in that. Ebay is chock full of high-volume sellers turning over old 
networking gear that is amazingly good stuff that’s just outdated. I can grab a 
48 port GigE switch with 10gb/s uplink ports for under $200. The market is 
gigantic, and putting old stuff to use on an internal network with proper 
safeguards is not totally crazy. Customers can have multiple fully-loaded 
spares on-site for less than what a year of SmartNet coverage would cost.

My server platform of choice when I want a “support server” for this old stuff 
has always been FreeBSD. Stock tftpd and ftpd are wonderful, and anyone 
professing that those two tiny daemons are “bloat” just hasn’t used Linux.

> TFTP is not going away, neither is FTP. I'm dead serious. Remote media
> via Supermicro IPMI in 2021? SMB1. Firmware updates for my UPS? FTP.
> Scanner/printer/fax all-in-one thingy? Uploads received fax transmissions
> via FTP. PBX? Uploads usage reports via FTP. This stuff is here to stay.
> In local networks, of course.

Preach! And plenty of VoIP gear too!

There are absolutely real world uses for these simple daemons, and I trust some 
stock FreeBSD daemon like this more than something I might fetch from ports - 
both in terms of knowing it’s had some kind of auditing/maintenance by 
qualified people and that it’s going to have an accurate manpage, sane 
defaults, and remain relatively simple/minimal.

I think as everyone has moved to the cloud and devops and all that they forget 
about sysadmins standing up servers as simple utility boxes that support a 
bunch of other gear.

> But still even on "the Internet", FTP is the most used method for customers
> of static website hosting. You cannot teach these people what an SSH key is.
> Just my experience, but backed by a load of customer interactions over more
> than 20 years …

I think some people mean well, and they imagine that if we just tell people to 
move to some monstrosity like Filezilla the problem is solved, but 
realistically it’s just a good way to lose paying customers.

Charles

> 
> Kind regards,
> Patrick
> --
> punkt.de GmbH
> Patrick M. Hausen
> .infrastructure
> 
> Kaiserallee 13a
> 76133 Karlsruhe
> 
> Tel. +49 721 9109500
> 
> https://infrastructure.punkt.de
> i...@punkt.de
> 
> AG Mannheim 108285
> Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein
> 



signature.asc
Description: Message signed with OpenPGP

Re: Deprecating base system ftpd?

[Charles Sprickman via freebsd-stable]

> On Apr 4, 2021, at 8:05 PM, Daniel Morante via freebsd-stable 
>  wrote:
> 
> My vote is for no.
> 
> Reasoning is simple... at what point does it stop?  By continuously moving 
> stuff from base to ports, FreeBSD slowly becomes just a Kernel. 

That’s a +1 here, both for the “keep it” and for the comment above regarding 
complete OS vs. kernel and a teeny userland.

Ideally, we’d modernize ftpd to support TLS.

The PITA with ports solutions is you immediate run into the issue of which of 
the many ftp daemons is going to fit your needs and not require some 
non-trivial amount of configuration. The stock ftpd ‘just works’ for local user 
accounts and has a simple method for blocking of swaths of users from using it 
if that sort of restriction is needed.

This reminds me of Apple removing the telnet client. Sure, most people don’t 
*need* telnet, but it’s handy to have, both as a simple test tool and as a way 
to get into old crufty network gear that never moved on to ssh.

Charles

> 
> On 4/3/2021 4:39 PM, Ed Maste wrote:
>> I propose deprecating the ftpd currently included in the base system
>> before FreeBSD 14, and opened review D26447
>> (https://reviews.freebsd.org/D26447) to add a notice to the man page.
>> I had originally planned to try to do this before 13.0, but it dropped
>> off my list. FTP is not nearly as relevant now as it once was, and it
>> had a security vulnerability that secteam had to address.
>> 
>> I'm happy to make a port for it if anyone needs it. Comments?
>> ___
>> 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"
>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: git, $FreeBSD$ and mergemaster

[Charles Sprickman via freebsd-stable]

> On Dec 23, 2020, at 9:04 PM, Kyle Evans  wrote:
> 
> On Wed, Dec 23, 2020 at 8:02 PM Jonathan Chen  wrote:
>> 
>> Hi,
>> 
>> With the transition to git, I'm now getting a lot of prompts for
>> differences against an empty $FreeBSD$, eg:
>> 
>>  *** Displaying differences between installed version and ./.cshrc:
>> 
>> --- /.cshrc 2020-09-03 19:14:19.258107000 +1200
>> +++ ./.cshrc2020-12-24 14:52:16.751245000 +1300
>> @@ -1,4 +1,4 @@
>> -# $FreeBSD: stable/12/bin/csh/dot.cshrc 363525 2020-07-25 11:57:39Z pstef $
>> +# $FreeBSD$
>> #
>> # .cshrc - csh resource script, read at beginning of execution by each shell
>> #
>> 
>> While I can simply run a "mergemaster -F" to get past this particular
>> update, how will mergemaster operate in the future when there are
>> changes in /etc if it can't inspect the $FreeBSD$ tag anymore?
>> 
> 
> mergemaster only uses it as an optimization, if they're unexpanded
> throughout then it falls back to diff(1) -- i.e. it's slower without.

Is this a permanent change with git? I’d miss being able to see a path,
date and some indication of revision in config files and anything else
that’s text-based.

Charles

> Thanks,
> 
> Kyle Evans
> ___
> 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: The spkr driver

[Charles Sprickman via freebsd-stable]

> On Aug 28, 2020, at 12:36 PM, Eugene Grosbein  wrote:
> 
> 28.08.2020 23:25, Warner Losh wrote:
> 
>> I'd like to retire the spkr driver. It was a cute hack before sound cards
>> were ubiquitous, but it's not been kept up to date, and it's not clear that
>> it still works It is still Giant locked, and though it's not a huge
>> effort to do the locking I literally have no way to test it that I trust...
>> 
>> Is anybody using it these days for anything? If not, I'd propose we
>> de-orbit it before 13. If so, I need people to test patches to remove
>> Giant...
> 
> spkr works just fine in my stable/11 systems. I use it for routers on modern 
> fanless hardware
> to audio signalling like successfull completition of reboot (going to 
> multi-user mode).

Is this what pfsense/opnsense uses for the “booting complete” signal as well?

If so, it’s very handy.

Charles

> 
> I'd like to keep it working. I'm ready to test patches. However, my CURRENT 
> system lives in bhyve for the moment.
> Though, I could try running CURRENT with one of my less important wireless AP 
> systems built as NanoBSD,
> so I can build and boot CURRENT-based image.
> 
> 
> ___
> 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: vnet jail crash

[Charles Sprickman via freebsd-stable]

On Aug 24, 2020, at 11:30 AM, Mason Loring Bliss  wrote:
> 
> On Mon, Aug 24, 2020 at 09:46:26AM +0200, Nikos Vassiliadis wrote:
> 
>> After updating to 12-STABLE I am getting kernel panics when re-starting
>> the jail service. Here's a backtrace:
> 
> This is a known issue. There are a couple relevant bugs:
> 
>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237656
> 
> There are some workaround available too. I detail the one I use here:
> 
>https://wiki.freebsd.org/MasonLoringBliss/JailsEpair
> 
> ...but there are others. In short, you need to dispose of your epair before
> the jail is destroyed.

This seems like something that’s a big enough deal to merit inclusion in the 
release docs or errata… I was playing around with a VNET jail at home and just 
gave up at some point because of the panics, it would have been good to know 
the devs are aware of this bug (looks like it’s been around for over a year?).

Charles

> 
> --
> Mason Loring Bliss ma...@blisses.orgEwige Blumenkraft!
> (if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scene I



signature.asc
Description: Message signed with OpenPGP

Re: 12.1p7 no longer boots after doing zpool upgrade -a

[Charles Sprickman via freebsd-stable]

> On Jul 10, 2020, at 2:44 PM, Guido van Rooij  wrote:
> 
> On Fri, Jul 10, 2020 at 08:29:03PM +0200, Guido van Rooij wrote:
>> On Thu, Jul 09, 2020 at 08:24:54AM -0500, Kyle Evans wrote:
>>> On Thu, Jul 9, 2020 at 8:12 AM Guido van Rooij  wrote:
 
 I did a zpool upgrade -a to enable large_dnode and spacemap_v2.
 After that, I did:
 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 ada0
 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 ada1
 and:
 gpart bootcode -p /boot/boot1.efifat -i 1 ada0
 gpart bootcode -p /boot/boot1.efifat -i 1 ada1
 
 Now the system no longer boots from either disk and drops to the efi shell.
>>> 
>>> This method of updating the ESP is no longer recommended for new 12.x
>>> installations -- we now more carefully construct the ESP with an
>>> /EFI/FreeBSD/loader.efi where loader.efi is /boot/loader.efi. You will
>>> want to rebuild this as such, and that may fix part of your problem.
>> 
>> Hi Kyle,
>> 
>> Thnaks for your asnwer. I have not got it to work with that
>> configuration. What did work was to replace the  /efi/boot/BOOTx64.efi
>> with loader.efi and and change the content of startup.nsh with
>> loader.efi. Withoyt the above answer I wouldn't have figure it out
>> that quickly so thanks!
>> 
>> I will investigate further once I have more time (early next week probably).
> 
> There was one question I forgot to ask:
> Could I have known that my method of updating the ESP was not correct?
> If so, where is this documented?

+1

I have a few new servers and I figured that to keep with the times I should be 
doing EFI instead of legacy boot, but if this is one of those features where 
you have to be subbed to a number of email lists to know what state the feature 
is in, then maybe legacy boot is the right direction.

I don’t see any upgrade tips here:

https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports

This handbook seems to have no upgrade info:

https://www.freebsd.org/doc/handbook/updating-upgrading.html
https://www.freebsd.org/doc/handbook/boot-introduction.html
https://www.freebsd.org/doc/handbook/book.html

And I’m still not sure if the wiki is considered a canonical source for this 
info or if it’s more of a developer’s notebook.

Thanks,

Charles

> 
> -Guido
> ___
> 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: Long-shot: repeatable macOS samba share unmounting during Lightroom import

[Charles Sprickman via freebsd-stable]

> On Nov 24, 2019, at 10:19 AM, peter.b...@bsd4all.org wrote:
> 
> The fruit module forces avahi or mdns_responder to be compiled as well. A 
> share dispappearing could be due to some interaction with avahi. It could be 
> that the combination samba+fruit+avahi and samba+avahi is having different 
> behavior.

You guys are making feel like my laziness in sticking with AFP is actually 
paying off. :)

Apple’s QA is really garbage these days. I have a hackintosh at home that by 
some fluke of its uniqueness can cause a kernel panic on any mac connecting to 
it via SMB. Can reproduce it all day. Connect, do stuff, and after about 5 
minutes idle, the connecting machine will panic. Report it every time, existed 
since at least 10.12...

Charles

> Peter
> 
> 
> 
>> On 24 Nov 2019, at 12:15, Pete French  wrote:
>> 
>> I have a very similar setup to you for serving files to my Mac from a 
>> FreeBSD server. I haven't seen the unmount problem, but I di have a few 
>> oddities until I added the 'fruit' module on the Samba side, which helps 
>> with compatbiloty with the Mac. The appropriate bit of my config looks like 
>> this:
>> 
>>  vfs objects = fruit streams_xattr zfsacl
>>  fruit:resource = xattr
>>  fruit:encoding = private
>> 
>> Don't ask me what they do anymore, I added them ages ago, but it does work 
>> very nicely for me. You may already have this of course, but worth pointing 
>> out just in case as it took me a few years to discover it!
>> 
>> As someone else has said though, this may well be a Catalina bug. I am not 
>> running that (MacBook too old, and not buying another until the new 
>> keyboards are avilable n the replacement I want).
>> 
>> -pete.
>> ___
>> 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"

___
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: FreeBSD flood of 8 breakage announcements in 3 mins.

[Charles Sprickman via freebsd-stable]

> On May 16, 2019, at 5:41 AM, Miroslav Lachman <000.f...@quip.cz> wrote:
> 
> Alan Somers wrote on 2019/05/16 05:16:
>> On Wed, May 15, 2019 at 9:14 PM Miroslav Lachman <000.f...@quip.cz> wrote:
> 
>>> It would also be good if base system vulnerabilities are first published
>>> in FreeBSD vuxml. Then it can be reported to sysadmins by package
>>> security/base-audit.
>> +1.  Reporting base + ports vulnerabilities in a common way would be
>> great.  I assume that this is already part of the pkgbase project
>> being worked on by brd and others.
> 
> The functionality is already there. The only part missing is Security Office 
> should fill the data in to vuxml at the time of publishing new SA.
> 
> Thanks to Mark Felder 
> https://blog.feld.me/posts/2016/08/monitoring-freebsd-base-system-vulnerabilities-with-pkg-audit/
> Then I provided periodic script 
> https://www.freshports.org/security/base-audit/ 
> 

There’s also this as a “right now” solution if you use nagios:

https://github.com/frlen/nagios-plugins/blob/master/check_freebsd_version 


You do have to adjust it to check only once or twice a day and to provide for a 
large number of retries, as the remote portion of the check to find the current 
version often times out.

Thanks,

Charles

> Miroslav Lachman
> ___
> 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: CFT: FreeBSD Package Base

[Charles Sprickman via freebsd-stable]

> On Apr 28, 2019, at 6:21 PM, Paul Mather  wrote:
> 
> On Apr 28, 2019, at 3:52 PM,   wrote:
> 
>> FreeBSD Community,
>> 
>> 
>> 
>> I'm pleased to announce a CFT for builds of FreeBSD 12-stable and 13-current
>> using "TrueOS-inspired" packaged base. These are stock FreeBSD images which
>> will allow users to perform all updating via the 'pkg' command directly.
>> Rather than trying to answer all questions in this announcement, we've
>> created a FAQ page with more details. Please refer to this page, and let us
>> know if you have additional questions that we can include on that page going
>> forward.
> 
> 
> I currently keep my FreeBSD/arm and FreeBSD/arm64 systems up to date via 
> PkgBase in FreeBSD 12.  It works well for me (crossbuilding and hosting the 
> PkgBase repository on a FreeBSD/amd64 system).
> 
> What is the difference between the above CFT-created PkgBase and one created 
> via "make packages" using the native build system 
> (https://wiki.freebsd.org/PkgBase)?  Looking at the FAQ you linked 
> (https://trueos.github.io/pkgbase-docs/), it seems the above CFT system is 
> less granular than the one currently produced via the in-tree "make packages" 
> (which could be a good thing from a simplicity standpoint).  Is there 
> anything else?
> 
> Is the above CFT-produced packages the system that will ultimately become the 
> way packaged base is produced in FreeBSD 13.0-RELEASE, or is it just an 
> alternative you want people to try out and evaluate?  I guess I'm not clear 
> what "TrueOS-inspired" packaged base means. :-)

What are the plans to get rid of the hellscape known as “mergemaster”?  Is 
there anything exciting and new there either in base or any of the ixSystems 
projects?

Thanks,

Charles

> 
> Cheers,
> 
> Paul.
> 
> ___
> 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"

State of NVMe/NVMe hot-swap

[Charles Sprickman via freebsd-stable]

Hi folks,

I’ve been looking at mailing list archives, talking to my server vendor, 
looking at the official forums and I’m not finding lots of folks talking about 
NVMe drives. My forum query on hot-swap got a total of one response (and not 
from a NVMe user).

I’m looking at new servers and we really tend to use them until they drop, and 
it seems not too crazy to think that SATA and SAS SSDs will start growing 
scarce in 5-8 years (or at least get more expensive than NVMe when it’s 
mainstream). It seems like laptops and even many desktops are now using NVMe 
drives in the m.2 format.  IOW, it’s the future.

So can anyone comment on using NVMe in production, specifically the “u.2” 
format that gives you a nice 2.5” drive with hot swap capability? And more 
specifically, can you comment on how well (if at all) hot swap works?  Really 
open to any feedback before I commit to buying a few servers based on NVMe 
drives.

Thanks,

Charles
___
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: php56

[Charles Sprickman via freebsd-stable]

> On Jan 13, 2019, at 3:19 PM, Randy Bush  wrote:
> 
>> I have a mission critical app server running an old PHP 5.6
>> application which will not work on PHP 7+.
> 
> wordpress 5.x and nfsen are dying on the php 7.x hill here

WordPress folks highly encourage 7.x, is this something FreeBSD-specific?

https://wordpress.org/about/requirements/ 


Charles

> 
> randy
> ___
> 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: FCP-0101: Deprecating most 10/100 Ethernet drivers

[Charles Sprickman via freebsd-stable]

> On Oct 4, 2018, at 11:52 AM, Cy Schubert  wrote:
> 
> I have rl, fxp, xl, dc, bge (which I have an uncommitted patch for), nfe, and 
> sk. Not all are scheduled for removal but this is my inventory for which I 
> can test and am willing to help out with. Add iwn and ath too.

I also have a stack of old stuff (almost certain there’s at least one vx in 
there - VORTEX power!).  If anyone needs cards, please contact me and if I have 
it, I’ll send it your way.  Also have some old video (AGP), sound (ISA), SATA 
(PCI-X) and other total rando stuff.

One place I see the older cards are in some firewall boxes that are in SFF 
boxes. Old PCI 10/100 NICs are more than adequate for backup WAN purposes 
(xDSL, cable, etc.) and some of the SFF boxes have one pci-e plus one pci slot 
and that’s it.

Charles

> 
> ---
> Sent using a tiny phone keyboard.
> Apologies for any typos and autocorrect.
> Also, this old phone only supports top post. Apologies.
> 
> Cy Schubert
>  or 
> The need of the many outweighs the greed of the few.
> ---
> 
> -Original Message-
> From: Rick Macklem
> Sent: 04/10/2018 07:41
> To: Warner Losh; Alexey Dokuchaev
> Cc: FreeBSD Net; freebsd-...@freebsd.org; Brooks Davis; FreeBSD-STABLE 
> Mailing List; freebsd-a...@freebsd.org
> Subject: Re: FCP-0101: Deprecating most 10/100 Ethernet drivers
> 
> Warner Losh wrote:
> [lots of stuff snipped]
>> That's why that one way to get the driver off the list is to convert to
>> iflib. That greatly reduces the burden by centralizing all the stupid,
>> common things of a driver so that we only have to change one place, not
>> dozens.
> 
> I can probably do this for bfe and fxp, since I have both.
> Can someone suggest a good example driver that has already been converted,
> so I can see what needs to be done?
> 
> Again, I don't care if they stay in the current/head tree.
> 
> [more stuff snipped]
> 
> rick
> 
> ___
> freebsd-a...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-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"

___
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: bad hash in repo

[Charles Sprickman via freebsd-stable]

> On Sep 2, 2018, at 6:46 AM, Randy Bush  wrote:
> 
> someone asked if the failures were limited to update5.freebsd.org
> 
> today's batch were both 4 and 5

Is there any possibility there’s something between these you and these update 
hosts?

This thread has some interesting info, but specifically, note the description 
of how phttpget works at the bottom - it is NOT at all picky about what it 
receives, and seems to have some quirks:

https://lists.freebsd.org/pipermail/freebsd-stable/2015-December/083882.html 


Charles

> randy
> ___
> 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: bad hash in repo

[Charles Sprickman via freebsd-stable]

> On Sep 1, 2018, at 1:09 PM, Randy Bush  wrote:
> 
> seeing a lot of these
> 
> Looking up update.FreeBSD.org mirrors... 2 mirrors found.
> Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... 
> done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
> Fetching 2 patches.. done.
> Applying patches... done.
> Fetching 2 files... 
> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
> incorrect hash.
 these continue; like for a week.  for multiple servers, all on the
 global internet no filters other than samba etc.
>>> 
>>> have you forced pulling down metadata from the pkg servers?  i have
>>> gotten into this state in the past and a "pkg update -f" would get me
>>> out of that scenario.
>> 
>> # pkg update -f
>> Updating FreeBSD repository catalogue...
>> Fetching meta.txz: 100%944 B   0.9kB/s00:01
>> Fetching packagesite.txz: 100%6 MiB   2.2MB/s00:03
>> Processing entries: 100%
>> FreeBSD repository update completed. 32029 packages processed.
>> All repositories are up to date.
>> # freebsd-update fetch
>> Looking up update.FreeBSD.org mirrors... 2 mirrors found.
>> Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... 
>> done.
>> Fetching metadata index... done.
>> Inspecting system... done.
>> Preparing to download files... done.
>> Fetching 2 patches.. done.
>> Applying patches... done.
>> Fetching 2 files... 
>> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
>> incorrect hash.
> 
> this is now over two weeks.  still multiple systems on public net, v4
> and dual stack.

The other brute-force approach is:

rm -rf /var/db/freebsd-update/*

Also, is it always fetching from "update5.freebsd.org”?

Charles

> 
> randy
> ___
> 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: Bind to port <1024 in jail

[Charles Sprickman via freebsd-stable]

> On Aug 20, 2018, at 11:04 AM, Ian Lepore  wrote:
> 
> On Mon, 2018-08-20 at 16:47 +0200, Stefan Bethke wrote:
>> I have a Go program (acme-dns) that wants to bind 53, 80, and 443,
>> and I´d rather have it run as a non-privileged user.  The program
>> doesn´t provide a facility to drop privs after binding the ports. I´m
>> planning to run it in a jail.
>> 
>> After some googling, it appears that a couple of years ago I should
>> have been able to do:
>> sysctl net.inet.ip.portrange.reservedhigh=0
>> and allow all processes to bind to „low“ ports. This does not work in
>> my jails on a 11-stable host.
>> 
>> $ sudo sysctl net.inet.ip.portrange.reservedhigh=0
>> net.inet.ip.portrange.reservedhigh: 1023
>> sysctl: net.inet.ip.portrange.reservedhigh=0: Operation not permitted
>> 
>> Securelevel should not interfere:
>> $ sysctl kern.securelevel
>> kern.securelevel: -1
>> 
>> Is there a way to allow regular processes to bind to low ports?
>> 
>> 
>> Stefan
>> 
> 
> You might be able to set up a specific local userid for this process,
> then use mac_portacl(4) to allow it to bind to those ports. I'm not
> certain that works inside a jail, however.

I am so behind on all the new toys in the system.  I was very embarrassed
to find out about this feature from someone who’s primarily working
with Linux in his day job.  He was just looking to bind an Elixir app to 80/443
without running as root and he shared this:

security.mac.portacl.rules=gid:2001:tcp:80,gid:2001:tcp:443

We stuck that in sysctl.conf and that was that.

I wish FreeBSD still had the evangelism folks that would go out and
tell the userbase and anyone else that would listen about all the cool
new stuff. :)

Charles

> 
> -- Ian
> ___
> 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: 802.1X authenticator for FreeBSD

[Charles Sprickman via freebsd-stable]

> On Oct 18, 2017, at 1:10 PM, Peter Ankerstål  wrote:
> 
>> 
>> I’m under the impression that the authenticator function in a wired network 
>> is usually part of the switch, and the switch will talk to some 
>> authentication server like RADIUS, giving it the port number of the 
>> connected device and additional information.
>> 
>> If FreeBSD had such a function, I think it would be limited to 
>> point-to-point Ethernet links, 802.1x being a link-layer protocol.
>> 
> 
> Yes I know, but this is functional in hostapd for Linux and it would be nice 
> to have it in FreeBSD as well. 

I’m not seeing this in FreeBSD, but pfsense does claim to support 802.1x for 
wifi.

I just happen to be reading about radius (last I used it was for dialup) for 
wifi auth and the quick overview on the radius side of things is that the AP 
software sends your auth info as well as MAC and a bunch of other stuff, and 
the radius server (much like dialup) sends back all sorts of info beyond auth 
success/fail - session timeout, info on what VLAN the client may be on, 
firewall policies, etc. Pretty cool stuff.

Charles

> 
> Thanks anyway!
> ___
> 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: Circular dependency between local_unbound and ntpd?

[Charles Sprickman]

On Jul 14, 2015, at 10:47 AM, Paul Mather p...@gromit.dlib.vt.edu wrote:

 On Jul 14, 2015, at 10:33 AM, krad kra...@gmail.com wrote:
 
 As
 
 $ grep REQUIRE /etc/rc.d/ntpd
 # REQUIRE: DAEMON ntpdate FILESYSTEMS devfs
 
 
 You could set something similar to the following in the rc.conf
 
 ntpdate_hosts=a.b.c.d w.x.y.z
 ntpdate_enable=yes
 
 Thanks for that suggestion.  I assume the a.b.c.d w.x.y.z are IP addresses, 
 not hostnames, otherwise we'd have the same problem.
 
 The /etc/rc.d/ntpdate startup script has a REQUIRE: NETWORKING ... and 
 /etc/rc.d/local_unbound has a BEFORE: NETWORKING in it, meaning it will be 
 running before ntpdate runs.  That means DNS resolution will require an 
 accurate clock and, I assume, mean that ntpdate will require IP addresses, 
 too?
 
 So, it still comes down to this: do I need to know the IP address of an NTP 
 server to be able to use local_unbound safely with NTP?

Hopefully not.  I have a client with a number of Mikrotik routers sprinkled 
around upstate.  They did not have an NTP server to point to, so I used a pool 
server.  Mikrotik will take a hostname, but it saves an IP.  A year later I see 
a few not reestablish OpenVPN connections after power failures, spend an hour 
troubleshooting, turns out that those IPs were no longer NTP servers, the box 
thought it was 1970, and that causes the VPN to fail.

TL;DR, don’t save NTP servers by IP in config files.

Charles

 
 Cheers,
 
 Paul.
 
 
 
 
 
 
 On 14 July 2015 at 14:43, Paul Mather p...@gromit.dlib.vt.edu 
 mailto:p...@gromit.dlib.vt.edu wrote:
 I believe I ran afoul of a circular dependency between local_unbound and 
 ntpd on my 10.2-PRERELEASE system.  I use a stock /etc/ntp.conf and use 
 ntpd_sync_on_start=YES.
 
 Last night, a BIOS settings reset cause my CMOS clock to go WAY out of synch 
 for the first time.  No problem, I thought: NTP will correct it at boot.
 
 Wrong!
 
 When my system booted, the time was not corrected.  Also, DNS resolution was 
 not working.  I figured out it was because local_unbound relies on an 
 accurately set clock, but the clock could not be set accurately because my 
 stock ntp.conf requires working DNS resolution to reach the NTP servers.
 
 That sounds like a potential circular dependency to me.
 
 My workaround at the time was to look up 0.freebsd.pool.ntp.org 
 http://0.freebsd.pool.ntp.org/ on another system; stop ntpd; then do a 
 ntpdate using the IP addresses to set the clock. Once the clock was set 
 accurately, things were all hunky dory.
 
 Does anyone have any suggestion for an automatic way around this?  I guess 
 one way would be to put the IP address of an NTP server into my ntp.conf 
 file, so at least one would be reachable without needing a working DNS?
 
 My main concern is for those systems like my Raspberry Pi and Beaglebone 
 Black that don't have a battery-backed clock.  I currently don't use 
 local_unbound on those, but it seems like I'd encounter this problem 
 routinely if I did.
 
 Cheers,
 
 Paul.
 ___
 freebsd-stable@freebsd.org mailto:freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable 
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org 
 mailto: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

___
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: 9.2-PRE: switch off that stupid Nakatomi Socrates

[Charles Sprickman]

On Sep 29, 2013, at 3:28 PM, C. P. Ghost wrote:

 On 28.09.2013 11:32, Phil Regnauld wrote:
 Teske, Devin (Devin.Teske) writes:
 If you work seriously on serious issues long enough... you'll become burned-
 out. Let me just come right out and say it...
 
 I coded it.
  And thanks, you got me chuckling - nice to see some humor once in a 
 while.
 
  To the offended poster: read the last line of tunefs(8) - there's 
 probably
  many more places you could use serious time looking for deviations from
  corporate correctnes.
 
 Humor can even be etched in silicon, like e.g. on an IC created by Siemens:
 
 http://micro.magnet.fsu.edu/creatures/pages/bunny.html

Cisco too, besides weird Star Wars ROM messages, you have stuff like the
BFR (Big F*cking Router, after Big F*cking Gun in Doom) screened on the PCB:

https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2_001
https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2

I have no idea what Sluggo and Nancy are doing on this board:

https://www.kumari.net/gallery/index.php/Technology/Networking/CIMG0988

Charles

 
 ;-)
 
 -cpghost.
 
 -- 
 Cordula's Web. http://www.cordula.ws/
 
 ___
 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: Boot problem if a ZFS log device is missing

[Charles Sprickman]

On Aug 29, 2013, at 5:01 AM, Andriy Gapon wrote:

 on 29/08/2013 11:27 Maurizio Vairani said the following:
 
 I am able to boot the PC without a cache device but not without a log 
 device. Why ?
 
 The log could potentially contain uncommitted entries.  Without the log device
 there is no knowing if it did or did not.  And if it did then the pool is
 inconsistent state without the log device and so it can not be imported.

If one is willing to accept that data is lost (like the log device is totally 
smoked), is there a way to boot knowing that you may have some data loss, or is 
the only option to boot alternate media and force a pool import (assuming that 
works without the log device)?

Charles

 
 The cache is not persistent and so there is nothing needed from it upon a 
 boot.
 
 -- 
 Andriy Gapon
 ___
 freebsd...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-fs
 To unsubscribe, send any mail to freebsd-fs-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: Change in loader or kernel: won't boot with kfreebsd in grub2

[Charles Sprickman]

On Aug 14, 2013, at 11:40 PM, Thomas Mueller wrote:

 On 14.08.2013 07:22, Thomas Mueller wrote:
 How do I make a photo when I don't have a digital camera?
 
 If I had a digital camera, how would I convert the picture to text?
 
 You can attach images to email, or just share somewhere,
 e.g. http://imm.io
 
 I looked at man gpart and didn't see list in the list of
 commands: a little deficiency in the man page.
 
 This is generic geom's command, it is described in geom(8).
 
 --
 WBR, Andrey V. Elsukov
 
 But as I said, I don't have a digital camera.
 
 In any case, sending a graphic image of what ought to be a small text file is 
 very clumsy and inefficient.
 
 There ought to be a way to capture loader-command output to a file.  Question 
 is how to do that at the loader level.

Might I humbly suggest a serial console?  You can then capture the data as text.

If this is a server, it's rare these days to not have an IP-KVM solution 
built-in, and even more rare to not have full console to serial redirection 
from the first BIOS screen all the way to the OS grabbing the port.

Or you can borrow someone's cell phone, I can't recall the last time I saw one 
without a camera.

Charles

 
 I will try again later this week or weekend and post what I can of lsdev 
 output.
 
 Tom
 
 ___
 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: request for your comments on release documentation

[Charles Sprickman]

On Jun 27, 2013, at 7:24 PM, Miroslav Lachman wrote:

 Mark Felder wrote:
 On Wed, 12 Jun 2013 12:49:21 -0500, Hiroki Sato h...@freebsd.org wrote:
 
 [...]
 
 3. Is there missing information which should be in the relnotes?
 Probably there are some missing items for each release, but this
 question is one at some abstraction level. Link to commit log and
 diff, detailed description of major incompatible changes, and so
 on.
 
 I try to keep up with the development and changes in releases as best I
 can and I haven't noticed any glaring omissions over the last several
 releases. I think you're doing a fine job.
 
 Also, is there a reason this isn't a living document that can be
 updated as things get MFC'd to STABLE? It would help take load off your
 end and maybe speed up release once the freeze has happened and we begin
 the final grind through release candidates.
 
 It would be nice if all release related documents (relnotes, errata, hardware 
 notes etc.) will be living after release (in online version) and not 
 considered as set in stone. There are sometimes missing items which should be 
 included online as soon as possible, but rarely are.
 
 For example, I found two issues with OpenSSH in 8.4 release. (bugs or 
 features, or just incompatibilities with older versions) None of them is 
 listed anywhere and I think it is really bad, because one issue can cause 
 sshd not started after upgrade.
 
 So the online version of these docs should be living and updated as some 
 issues and questions arises on the mailing lists and forums few days / weeks 
 after release.

Additionally, it would be nice if the documentation for beta and RCs was posted 
before the actual release as well.  Just like the OS itself, docs can be beta 
and open for feedback from the community.  It's also nice to know about changes 
before you upgrade a box for testing as well - for example, the jail changes 
and zfs version bump in 8.4 were something of a surprise for me (I follow 
-stable, but not much else).  If the project wants people to test before 
release, having a list of changes, major and minor to focus on would probably 
net the project more useful feedback.

I'm also all for the living document idea.  It seems like the mailing lists 
always have a few issues that are documented nowhere else because they don't 
quite merit a ERRATA notice (eg: dhclient/fxp issue).

Thanks,

Charles

 
 
 On the other hand, FreeBSD has good quality of docs included Release Notes. 
 (thank you for your work!)
 If there is some man power, some items can be more detailed with links to 
 other online resources like FreeBSD wiki, but only for some important items.
 
 Miroslav Lachman
 ___
 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: sshd didn't run after upgrade to FreeBSD 8.4

[Charles Sprickman]

On Jun 19, 2013, at 7:37 PM, Adam Vande More wrote:

 On Wed, Jun 19, 2013 at 6:32 PM, Kimmo Paasiala kpaas...@gmail.com wrote:
 
 You're missing my point totally. The line is commented out in the
 official source of 8.4 and there for I have very hard time believing
 that it would show up uncommented on a fresh 8.4 installation.
 
 
 I don't think this warrants a mention in the Release Notes for exactly this
 point, however it should probably be mentioned in UPDATING.  If nothing
 else, that would at least keep UPDATING consistent with previous ssh major
 upgrades.

+1

Even if you ran mergemaster and saw the change, without a comment above the 
VersionAddendum line or mention in UPDATING, you might make any number of 
assumptions about why it's commented out now.Given the behavior (ie: sshd 
does not start) for those that have chosen in the past not to tell the world 
what OS and build date they are running.

Not really the best choice by the OpenSSH folks either, IMHO.  I skim the 
OpenSSH release notes sent to the -announce list and totally missed this change.

Charles

 
 -- 
 Adam Vande More
 ___
 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: Possible 8.4 regression

[Charles Sprickman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


On Jun 8, 2013, at 5:45 PM, Hiroki Sato wrote:

 Alexander Pyhalov a...@rsu.ru wrote
  in 4fffaaf8a6667175fca94ce32f25a...@sfedu.ru:
 
 al Hello.
 al
 al Just wanted to share a notice.
 al I had a 8.3 system with PostgreSQL running in a jail.
 al rc.conf has the following lines:
 al
 al jail_enable=YES
 al jail_sysvipc_allow=YES
 al jail_mount_enable=YES
 al jail_devfs_enable=YES
 al
 al jail_pgsql_rootdir=/jails/run/pgsql
 al jail_pgsql_hostname=pgsql.freebsd
 al jail_pgsql_ip=my.ip
 al jail_pgsql_interface=em0
 al
 al It was running normally. However, after update to 8.4 I had to add the
 al following parameter
 al jail_pgsql_parameters=allow.sysvipc
 al
 al Without it shmget in jail didn't work.
 
 Thank you for the report.  This affects jail_set_hostname_allow and
 jail_socket_unixiproute_only as well.  I will add it to Errata.

And allow.raw_sockets…

Charles

 
 -- Hiroki

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJRs7OaAAoJEMfwH0dqLIp2w+kIAKn1LW9nUZHlv9Hpm4+M/+j/
OhITQDkTqUcvQZcXyUN3wMmWLSJTL0eYpu57pMp3tsfr61rv/GS3t51Lw0aUPwG3
LDLNZ5rslURffbad+vTlUA2RYfcu0aNk1bvEQxRobdA4ql2BoC59K2vkOzE9WB59
YXvG0Pl1Y7MiSrGZMGiKGDDUJqllBzHCl7PwSvSBK9JBPh0A2LS9mEzTRc3clUIh
bm3WvPhfuAvgypxncOkVk4OARpbYunHlC70AkOqohvdqFQzw4BaVXFUru5yvTJ+Y
h8t4LtYu5px015brZEox61ECrIavvA1ujv7mQNyWDrgFzNI1IS3eLGx4mr/01io=
=bbMA
-END PGP SIGNATURE-
___
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: Apparent fxp regression in FreeBSD 8.4-RC3

[Charles Sprickman]

On May 24, 2013, at 1:47 AM, YongHyeon PYUN wrote:

 On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
 On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
 On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
 On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
 If someone wants me to test DHCP via fxp(4) on the above system (I can
 do so with both NICs), just let me know; it should only take me half an
 hour or so.
 
 I'll politely wait for someone to say please do so else won't bother.
 
 
 For the sake of completeness...
 
 Please do so.  :)
 
 Issue reproduced 100% reliably, even within sysinstall.
 
 {snip} 
 
 Forgot to add:
 
 This issue ONLY happens when using DHCP.
 
 Statically assigning the IP address works fine; fxp0 goes down once,
 up once, then stays up indefinitely.
 
 I asked Mike to try backing out dhclient(8) change(r247336) but it
 seems he missed that. Jeremy, could you try that?

I have a system up and running and showing the problem (that was
non-trival, just for the record - one machine blew the PSU after
POST, the other refused to boot off an IDE drive, and then required
two CD-ROM drives before I found a functional one, and it took a
good half-hour to find what's apparently the last piece of writable
CD-R media I own).

I am not awesome with svn, but I'll see if I can manually undo
r247336 and give it a spin.

Charles

 
 I guess dhclient(8) does not like flow-control negotiation of
 fxp(4) after link establishment.
 
 
 I also tested network I/O in the statically-assigned scenario.  Pinging
 the box from another machine on the LAN:
 
 $ ping 192.168.1.192
 PING 192.168.1.192 (192.168.1.192): 56 data bytes
 64 bytes from 192.168.1.192: icmp_seq=0 ttl=64 time=0.180 ms
 64 bytes from 192.168.1.192: icmp_seq=1 ttl=64 time=0.138 ms
 64 bytes from 192.168.1.192: icmp_seq=2 ttl=64 time=0.214 ms
 64 bytes from 192.168.1.192: icmp_seq=3 ttl=64 time=0.165 ms
 64 bytes from 192.168.1.192: icmp_seq=4 ttl=64 time=0.114 ms
 ^C
 --- 192.168.1.192 ping statistics ---
 5 packets transmitted, 5 packets received, 0.0% packet loss
 round-trip min/avg/max/stddev = 0.114/0.162/0.214/0.034 ms
 ___
 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: Apparent fxp regression in FreeBSD 8.4-RC3

[Charles Sprickman]

On May 24, 2013, at 1:47 AM, YongHyeon PYUN wrote:

 On Thu, May 23, 2013 at 09:49:19PM -0700, Jeremy Chadwick wrote:
 On Thu, May 23, 2013 at 09:40:35PM -0700, Jeremy Chadwick wrote:
 On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
 On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
 If someone wants me to test DHCP via fxp(4) on the above system (I can
 do so with both NICs), just let me know; it should only take me half an
 hour or so.
 
 I'll politely wait for someone to say please do so else won't bother.
 
 
 For the sake of completeness...
 
 Please do so.  :)
 
 Issue reproduced 100% reliably, even within sysinstall.
 
 {snip} 
 
 Forgot to add:
 
 This issue ONLY happens when using DHCP.
 
 Statically assigning the IP address works fine; fxp0 goes down once,
 up once, then stays up indefinitely.
 
 I asked Mike to try backing out dhclient(8) change(r247336) but it
 seems he missed that. Jeremy, could you try that?
 
 I guess dhclient(8) does not like flow-control negotiation of
 fxp(4) after link establishment.

Confirmed here that removing the linkstate stuff from r247336 fixes it.

Before:

May 24 08:00:17 fxptest dhclient: New Subnet Mask (fxp0): 255.255.255.0
May 24 08:00:17 fxptest dhclient: New Broadcast Address (fxp0): 10.3.2.255
May 24 08:00:17 fxptest dhclient: New Routers (fxp0): 10.3.2.1
May 24 08:00:19 fxptest kernel: fxp0: link state changed to UP
May 24 08:00:19 fxptest kernel: fxp0: link state changed to DOWN
May 24 08:00:19 fxptest dhclient: New IP Address (fxp0): 10.3.2.109
May 24 08:00:19 fxptest dhclient: New Subnet Mask (fxp0): 255.255.255.0
May 24 08:00:19 fxptest dhclient: New Broadcast Address (fxp0): 10.3.2.255
May 24 08:00:19 fxptest dhclient: New Routers (fxp0): 10.3.2.1
May 24 08:00:21 fxptest kernel: fxp0: link state changed to UP
May 24 08:00:21 fxptest dhclient: New IP Address (fxp0): 10.3.2.109
May 24 08:00:21 fxptest kernel: fxp0: link state changed to DOWN
May 24 08:00:21 fxptest dhclient: New Subnet Mask (fxp0): 255.255.255.0
May 24 08:00:21 fxptest dhclient: New Broadcast Address (fxp0): 10.3.2.255
May 24 08:00:21 fxptest dhclient: New Routers (fxp0): 10.3.2.1
May 24 08:00:23 fxptest kernel: fxp0: link state changed to UP
May 24 08:00:23 fxptest dhclient: New IP Address (fxp0): 10.3.2.109
May 24 08:00:23 fxptest kernel: fxp0: link state changed to DOWN

After:

May 24 08:07:05 fxptest kernel: fxp0: link state changed to DOWN
May 24 08:07:07 fxptest kernel: fxp0: link state changed to UP
May 24 08:07:12 fxptest dhclient: New IP Address (fxp0): 10.3.2.109
May 24 08:07:12 fxptest kernel: fxp0: link state changed to DOWN
May 24 08:07:12 fxptest dhclient: New Subnet Mask (fxp0): 255.255.255.0
May 24 08:07:12 fxptest dhclient: New Broadcast Address (fxp0): 10.3.2.255
May 24 08:07:12 fxptest dhclient: New Routers (fxp0): 10.3.2.1
May 24 08:07:14 fxptest kernel: fxp0: link state changed to UP
root@fxptest:/usr/home/spork # date
Fri May 24 08:10:32 UTC 2013

Note there is still a down/up/down/up transition on starting dhclient…

Am I correct that the linkstate changes are meant to allow for an automatic 
retry for a lease when the ethernet connection is dropped?  That doesn't seem 
wrong, it just seems like somewhere we should be waiting a few seconds.  It 
appears that each time dhclient gets a lease, even without the linkstate code, 
the connection briefly drops…'

Charles
___
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: Apparent fxp regression in FreeBSD 8.4-RC3

[Charles Sprickman]

On May 24, 2013, at 12:40 AM, Jeremy Chadwick wrote:

 On Thu, May 23, 2013 at 11:42:44PM -0400, Glen Barber wrote:
 On Thu, May 23, 2013 at 08:38:06PM -0700, Jeremy Chadwick wrote:
 If someone wants me to test DHCP via fxp(4) on the above system (I can
 do so with both NICs), just let me know; it should only take me half an
 hour or so.
 
 I'll politely wait for someone to say please do so else won't bother.
 
 
 For the sake of completeness...
 
 Please do so.  :)
 
 Issue reproduced 100% reliably, even within sysinstall.
 
 ISO image used:
 
 ftp://ftp4.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.4/FreeBSD-8.4-RC3-i386-disc1.iso
 
 I just chose to Configure the system, selected Networking, chose NO to
 the IPv6 configuration choice, and YES to the DHCP configuration choice,
 then hit Alt-F2 to watch relevant output.
 
 This was the result:
 
 http://imgbin.org/index.php?page=imageid=13718
 
 ...with the fxp0 physif up/down messages continuing indefinitely.
 
 fxp0 on the system is the Intel 82559.  Shot of console's dmesg:
 
 http://imgbin.org/index.php?page=imageid=13720
 
 Nothing is connected to fxp1.
 
 Key points for those asking me to help debug:
 
 - I only have VGA console on this box
 - I do not have an IDE hard disk of any sort for temporary OS

There are machines in my garage that are supposed to go to the recycling dump.

I have old boot messages from one P-III box that indicates there's an Intel 
82559 chip onboard.

I do have drives, and I do have a CD drive, although I'm uncertain as to its 
condition.

I can make a serial console available.

USB booting is out of the question.

I am currently out of blank CD-R's, but might be able to find my meager stash 
of CD-RWs that I couldn't find last week…  Failing that, can I dd a memstick 
image onto a drive?

Mr. Barber loves these machines, they are his favorites. :)

C

  installation, setup, kernel testing, etc..
 - The system cannot boot USB media of any sort, so memsticks are out
 - The ATAPI drive is CD-only; there is no DVD support, so there's no
  easy way to get a real shell with full utilities (i.e. Fixit)
 
 So if someone wants to take a stab at this, they'll need to do so and
 make me an ISO.  Sorry that I can't make things easier.  :-(
 
 This definitely needs to get fixed before 8.4-RELEASE.
 
 -- 
 | Jeremy Chadwick   j...@koitsu.org |
 | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
 | Mountain View, CA, US|
 | 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

___
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: So I whip out a FTDI-based multiport Serial USB Adapter....

[Charles Sprickman]

On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote:

 On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote:
 On 2/4/2013 2:06 PM, Ian Lepore wrote:
 On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote:
 ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD
 9.1-STABLE #16 r244942
 
 and it returns
 
 ugen4.4: vendor 0x0409 at usbus4
 uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4
 on usbus4
 uhub_attach: port 1 power on failed, USB_ERR_STALLED
 uhub_attach: port 2 power on failed, USB_ERR_STALLED
 uhub_attach: port 3 power on failed, USB_ERR_STALLED
 uhub_attach: port 4 power on failed, USB_ERR_STALLED
 uhub_attach: port 5 power on failed, USB_ERR_STALLED
 uhub_attach: port 6 power on failed, USB_ERR_STALLED
 uhub_attach: port 7 power on failed, USB_ERR_STALLED
 uhub6: 7 ports with 7 removable, self powered
 
 Yuck.
 
 The last time it was working was on a FreeBSD 7 box (yeah, I know,
 rather old) but I never had problems there.  And it appears that all of
 the device declarations that I used to have to put in the kernel as
 non-standard stuff are now in GENERIC, so I would expect it to work.
 
 Ideas as to what may have gotten hosed up here?
 
 Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC.
 
 FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and
 10; I use it all the time.  Sometimes aftermarket vendors who use FTDI's
 parts program different vendor/product info and IDs have to be added to
 code to recognize them, that's the only trouble one usually encounters.
 
 -- Ian
 Well, that sorta kinda worked. 
 
 Except that it still is identifying it as a hub too, and the two collide
 and crash the stack.
 
 But I can't find anything that is looking at the PID (0x0050) or the
 definition (HUB_0050) anywhere in the code. 
 
 I'll go pull the NEC defs and set up something else instead of simply
 adding it to the FTDI probe list.
 
 
 It seems to me you have a problem with a hub (perhaps the root hub or a
 motherboard hub if you don't have an external one) and this has nothing
 to do with the ftdi device at all.

I assume we're talking about a multi-port usb to serial adapter, correct?

If so, they generally do have a hub included in the device.

Example:

ugen1.3: vendor 0x0409 at usbus1
uhub4: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 3 on 
usbus1
uhub4: 7 ports with 7 removable, self powered

Then the individual ports look like this:

ugen1.4: FTDI at usbus1
uftdi0: FT232R USB UART on usbus1
ugen1.5: FTDI at usbus1
uftdi1: FT232R USB UART on usbus1
(etc.)

We use these for serial console ports, they're (relatively) cheap and have 
generally been well supported.

The above info is from an 8.3 box.

Just wanted to clarify that there is likely a hub in the serial box Karl is 
working with…

Charles

  Or the usb serial device is damaged
 somehow so that the vendor and product ID are reading as garbage and
 being mistaken for a hub.
 
 Have you tried the ftdi adapter on another port/hub/computer?  Have you
 tried plugging something else into the port you're trying to use for the
 ftdi adapter, like a thumb drive or something?
 
 -- Ian
 
 
 ___
 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: So I whip out a FTDI-based multiport Serial USB Adapter....

[Charles Sprickman]

On Feb 4, 2013, at 5:00 PM, Ian Lepore wrote:

 On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote:
 On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote:
 
 On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote:
 On 2/4/2013 2:06 PM, Ian Lepore wrote:
 On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote:
 ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD
 9.1-STABLE #16 r244942
 
 and it returns
 
 ugen4.4: vendor 0x0409 at usbus4
 uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4
 on usbus4
 uhub_attach: port 1 power on failed, USB_ERR_STALLED
 uhub_attach: port 2 power on failed, USB_ERR_STALLED
 uhub_attach: port 3 power on failed, USB_ERR_STALLED
 uhub_attach: port 4 power on failed, USB_ERR_STALLED
 uhub_attach: port 5 power on failed, USB_ERR_STALLED
 uhub_attach: port 6 power on failed, USB_ERR_STALLED
 uhub_attach: port 7 power on failed, USB_ERR_STALLED
 uhub6: 7 ports with 7 removable, self powered
 
 Yuck.
 
 The last time it was working was on a FreeBSD 7 box (yeah, I know,
 rather old) but I never had problems there.  And it appears that all of
 the device declarations that I used to have to put in the kernel as
 non-standard stuff are now in GENERIC, so I would expect it to work.
 
 Ideas as to what may have gotten hosed up here?
 
 Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC.
 
 FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and
 10; I use it all the time.  Sometimes aftermarket vendors who use FTDI's
 parts program different vendor/product info and IDs have to be added to
 code to recognize them, that's the only trouble one usually encounters.
 
 -- Ian
 Well, that sorta kinda worked. 
 
 Except that it still is identifying it as a hub too, and the two collide
 and crash the stack.
 
 But I can't find anything that is looking at the PID (0x0050) or the
 definition (HUB_0050) anywhere in the code. 
 
 I'll go pull the NEC defs and set up something else instead of simply
 adding it to the FTDI probe list.
 
 
 It seems to me you have a problem with a hub (perhaps the root hub or a
 motherboard hub if you don't have an external one) and this has nothing
 to do with the ftdi device at all.
 
 I assume we're talking about a multi-port usb to serial adapter, correct?
 
 If so, they generally do have a hub included in the device.
 
 Example:
 
 ugen1.3: vendor 0x0409 at usbus1
 uhub4: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 3 on 
 usbus1
 uhub4: 7 ports with 7 removable, self powered
 
 Then the individual ports look like this:
 
 ugen1.4: FTDI at usbus1
 uftdi0: FT232R USB UART on usbus1
 ugen1.5: FTDI at usbus1
 uftdi1: FT232R USB UART on usbus1
 (etc.)
 
 We use these for serial console ports, they're (relatively) cheap and have 
 generally been well supported.
 
 The above info is from an 8.3 box.
 
 Just wanted to clarify that there is likely a hub in the serial box Karl is 
 working with…
 
 Charles
 
 Oh, interesting.  The biggest ftdi dongle I have is 4 ports, using the
 ftdi 4232 chip.  I guess to get more ports than that, folks are now
 using an internal hub and multiple ftdi chips.

These multiport things have been around for a long time.  Someone at ISC 
recommended them when we were looking to replace some unsupported RocketPort 
cards.  Not affiliated with this place, but it's the largest collection of USB 
to serial stuff I've ever seen (and they document for the most part what chips 
are involved):

http://usbgear.com/USB-Serial.html

Our first 16 ports are on one of these:

http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RMcats=199catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601
(the tx/rx blinky lights are handy in troubleshooting)

Then the rest on this cheaper model:

http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-Mcats=199catid=494%2C199%2C474%2C2345%2C1009

 So for some reason there's a problem with the hub, and that's probably
 preventing it from getting as far as seeing the ftdi parts that are
 downstream of that.

My dmesg snippet is from the latter box.  Note that the vendor and product ID 
are the same as Karl's.  Perhaps there is a regression, as I am running 8.3 and 
have had no issues there (previously it was on a 4.11 box).

Charles

 
 -- Ian
 

___
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 wiki offline for a bit

[Charles Sprickman]

On Jan 8, 2013, at 3:10 AM, Bas Smeelen wrote:

 On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:
 http://wiki.freebsd.org/ZFSTuningGuide
 
 Seems not working :)
 
 
 Works here!

What's odd is that it looks like some changes were reverted.  I'd asked someone 
with write privs on it to include a link to mm@'s zfs-stats tool 
(http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/zfs-stats/) and it was 
added, but is now gone.

Things in general feel a little wonky though - the main freebsd page initially 
had issues getting some of the css to me, and svnweb was really laggy.  No idea 
if either thing is hosted in the same location as the wiki though.

Charles

 
 ___
 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: Documenting 'make config' options

[Charles Sprickman]

On Jun 6, 2012, at 7:43 PM, Warren Block wrote:

 On Wed, 6 Jun 2012, Vincent Hoffman wrote:
 
 On 06/06/2012 22:23, Glen Barber wrote:
 On Wed, Jun 06, 2012 at 02:14:46PM -0700, Doug Barton wrote:
 On 06/06/2012 11:59, Dave Hayes wrote:
 I'm describing more of a use case here, not attempting to specify an
 implementation. If a user invokes 'make', a window is presented to them
 with various options. It's probably very common that this is met with an
 initial reaction of what the hell do these do?, even from the most
 seasoned of admins (presuming they are unfamiliar with the software they
 have been asked to install). I claim it would be an improvement to have
 that information at the fingertips of the make invoker.
 What manner of providing this information would meet your needs?
 
 IMHO, something informing what THAT is in devel/subversion option
 MOD_DONTDOTHAT would be nice.  :)
 
 Not something I had bothered looking up till now as I hadnt wanted to
 use it but the 2nd hit on google,
 http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2009-April/161673.html
 describes it quite well.
 I tend to go with, If i dont know what it is, and its not default, I
 probably dont need it.
 Unless it looks interesting, then I google it ;)
 
 Maybe an (optional) new file with a longer descriptions of the make
 options so as not to crowd the make config dialog?
 I dont mind looking up compile time options for software I am installing
 but I can see how having a precis available locally might be handy.
 
 Here's an idea: if the description is too long to show in the very limited 
 space, cut it off, show a ..., and show the entire description in a two- or 
 three-line text box below the main one.  The  indicate a highlight here:
 
  ---
  [ ] GOOFY Build with support for the...  
   [ ] EXAMPLES  Install the examples
 
  ---
 OKCancel
 
   -
   Build with support for the GOOFY framework
   that provides concurrent whoopsies integrated
   with a Perubython interpreter, and stuff.
  ---
 
 The description at the bottom is from whatever option is currently 
 highlighted, and changes as the user scrolls through the options.  It would 
 be blank if the entire description could be displayed in the space available 
 above.
 
 The advantage of this is that it would work with existing ports, and give the 
 ability to use longer descriptions.  The disadvantage is that dialog(1) would 
 probably need modifications.

If we're talking about changing dialog(1), let's make sure there's also an 
uncheck all/check all option.

I'm looking at you, ghostscript:

wc -l /var/db/ports/ghostscript9/options
 315 /var/db/ports/ghostscript9/options

Charles

 ___
 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

--
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet www.bway.net
sp...@bway.net - 212.655.9344





___
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: Support for releases

[Charles Sprickman]

On Mar 27, 2012, at 2:25 PM, Brett Glass wrote:

 Everyone:
 
 I've just noted that as of this month, there is no release of FreeBSD -- on 
 any branch --  whose EOL is less than a year away. Should there not be at 
 least one release with extended support?

That will be 8.3:


• 20120205 - Ping SecurityOfficer about expected support for 8.3 
(BjoernZeeb).
• 20120205 - ACK from SecurityOfficer on extended support 
(ColinPercival).


http://wiki.freebsd.org/Releng/8.3TODO

I assume once it's released, this will be updated:

http://www.freebsd.org/security/#sup

Charles

 
 --Brett Glass
 
 ___
 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: zfs, 1 gig of RAM and periodic weekly

[Charles Sprickman]

On Feb 27, 2012, at 5:48 PM, Freddie Cash wrote:

 On Mon, Feb 27, 2012 at 11:02 AM, Nenhum_de_Nos
 math...@eternamente.info wrote:
 On Mon, February 27, 2012 15:33, Chuck Swiger wrote:
 On Feb 26, 2012, at 9:07 PM, Eugene M. Zheganin wrote:
 [ ... ]
 all with zfs and one gig of RAM.
 
 This isn't a sensible combination; I wouldn't try to run ZFS on anything 
 less than 4GB...
 
 regardless of the pool size ?
 
 I was planning on making an atom board a file server for my home, and I have 
 two options: soekris
 net6501 2GB RAM and intel board powered by the 330 atom (says 2GB limited as 
 well). My plans are
 to use from 4 up to 8 disks, and they should be 2TB at least.
 
 As its for home use, some p2p software and mostly music listening and 
 sometimes movie streaming.
 
 should 2GB be that bad, that I should drop it and use UFS instead ?
 
 I may run any version of FreeBSD on it, was planning on 9-STABLE or 9.1.
 
 You can get away with 2 GB of RAM, if you spend a lot of time manually
 tuning things to prevent kmem exhaustion and prevent ZFS ARC from
 starving the rest of the system (especially on the network side of
 things).
 
 Definitely go with a 64-bit install.  Even with less than 4 GB of RAM,
 you'll benefit from the large kmem size and better auto-tuning.
 
 Do not, under any circumstances, enable dedupe on a system with less
 than 16 GB of RAM.  :)
 
 If at all possible, find a motherboard that will let you use more RAM.
 2 GB is usable.  But 4 GB is the sweet spot for a simple file server.
 And 16 GB is best for a system with over 10 TB of storage in the
 pool.
 
 My home media server is a 32-bit install of FreeBSD 8-STABLE (Dec 2011
 vintage) with only 2 GB of RAM, using 4x 500 GB SATA drives in 2
 mirror vdevs (boot off USB stick).  Every couple of weeks it'll lock
 up, usually under heavy torrent load.  Prior to doing a bunch of tune
 loader.conf; reboot; crash; repeat cycles, the box was very unstable.
 2 GB is barely enough for ZFS + NFS + Samba + torrents + whatever.

Sounds very familiar.  Substitute afp for samba and torrents for sabnzbd
furiously unpacking things and we're probably doing much the same.  3 1TB
Samsungs (+1 spare), 2 gmirror'd CF cards for boot.

[spork@media ~]$ uptime
 6:41PM  up 60 days,  8:36, 1 user, load averages: 0.00, 0.02, 0.00
[spork@media ~]$ zpool list
NAMESIZE   USED  AVAILCAP  HEALTH  ALTROOT
tank1  2.72T  1.89T   850G69%  ONLINE  -
[spork@media ~]$ grep avail /var/run/dmesg.boot 
avail memory = 2087931904 (1991 MB)
[spork@media ~]$ uname -a
FreeBSD media..com 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Tue Feb 22 04:44:55 EST 
2011 sp...@media..com:/usr/obj/usr/src/sys/MEDIA  i386

Just in case I've hit on some special sauce in the loader.conf,
here you go:

[spork@media ~]$ cat /boot/loader.conf 
zfs_load=YES
#vfs.root.mountfrom=zfs:zroot
vm.kmem_size_max=1000M
vm.kmem_size=1000M
vfs.zfs.arc_max=200M

I used to be able to panic it regularly, but I just kept stepping the 
kmem up and the arc down until it behaved.  The uptime would be longer
if my power wasn't as flakey.

Charles


 
 -- 
 Freddie Cash
 fjwc...@gmail.com
 ___
 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: 9-stable from i386 to amd64

[Charles Sprickman]

On Feb 11, 2012, at 12:48 AM, Doug Barton wrote:

 On 02/10/2012 20:56, Randy Bush wrote:
 is there a recipe for moving from i386 to amd64?
 
 Other than backup and reinstall, no. As you already discovered the old
 world won't run on the new kernel. Installing the new world before
 reboot isn't safe either, as at some point in the process it'll blow up.

I recall doing it and then going on to do other bad things (like
putting a 4.9/i386 jail on the 7.2 amd64 host).  I'm pretty sure I
had some back and forth about it on this list, but I'm having no
luck finding it.  I was local to the box though, so errors were a
bit easier to work around.

A few vague snippets I remember:

-grabbing lib32 from somewhere and installing it
-ensuring COMPAT_FREEBSD32 was in the kernel
-possibly something complicated with /libexec/ld-elf.so.1 and 
 its 32-bit friend

I wish I could remember more.  It was one of those you
cannot/should not do this challenges that often suck down many
hours.  Maybe I misremembered the whole thing and gave in and
reinstalled even.  I do recall finding a few encouraging hacks in
the archives though.

Thanks,

Charles

 
 Sorry,
 
 Doug
 
 -- 
 
   It's always a long day; 86400 doesn't fit into a short.
 
   Breadth of IT experience, and depth of knowledge in the DNS.
   Yours for the right price.  :)  http://SupersetSolutions.com/
 
 ___
 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

--
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet www.bway.net
sp...@bway.net - 212.655.9344





___
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: zfs arc and amount of wired memory

[Charles Sprickman]

On Feb 8, 2012, at 7:11 PM, Miroslav Lachman wrote:

 Andriy Gapon wrote:
 on 08/02/2012 12:31 Eugene M. Zheganin said the following:
 Hi.
 
 On 08.02.2012 02:17, Andriy Gapon wrote:
 [output snipped]
 
 Thank you.  I don't see anything suspicious/unusual there.
 Just case, do you have ZFS dedup enabled by a chance?
 
 I think that examination of vmstat -m and vmstat -z outputs may provide 
 some
 clues as to what got all that memory wired.
 
 Nope, I don't have deduplication feature enabled.
 
 OK.  So, did you have a chance to inspect vmstat -m and vmstat -z?
 
 By the way, today, after eating another 100M of wired memory this server 
 hanged
 out with multiple non-stopping messages
 
 swap_pager: indefinite wait buffer
 
 Since it's swapping on zvol, it looks to me like it could be the mentioned 
 in
 another thread here (Swap on zvol - recommendable?) resource starvation 
 issue;
 may be it happens faster when the ARC isn't limited.
 
 It could be very well possible that swap on zvol doesn't work well when the
 kernel itself is starved on memory.
 
 So I want to ask - how to report it and what should I include in such pr ?
 
 I am leaving swap-on-zvol issue aside.  Your original problem doesn't seem 
 to be
 ZFS-related.  I suspect that you might be running into some kernel memory 
 leak.
  If you manage to reproduce the high wired value again, then vmstat -m and
 vmstat -z may provide some useful information.
 
 In this vein, do you use any out-of-tree kernel modules?
 Also, can you try to monitor your system to see when wired count grows?
 
 I am seeing something similar on one of our machine. This is old 7.3 with ZFS 
 v13, that's why I did not reported it.
 
 The machine is used as storage for backups made by rsync. All is running fine 
 for about 107 days. Then backups are slower and slower because of some 
 strange memory situation.
 
 Mem: 15M Active, 17M Inact, 3620M Wired, 420K Cache, 48M Buf, 1166M Free
 
 ARC Size:
 Current Size: 1769 MB (arcsize)
 Target Size (Adaptive):   512 MB (c)
 Min Size (Hard Limit):512 MB (zfs_arc_min)
 Max Size (Hard Limit):3584 MB (zfs_arc_max)
 
 The target size is going down to the min size and after few more days, the 
 system is so slow, that I must reboot the machine. Then it is running fine 
 for about 107 days and then it all repeat again.
 
 You can see more on MRTG graphs
 http://freebsd.quip.cz/ext/2012/2012-02-08-kiwi-mrtg-12-15/
 You can see links to other useful informations on top of the page 
 (arc_summary, top, dmesg, fs usage, loader.conf)
 
 There you can see nightly backups (higher CPU load started at 01:13), 
 otherwise the machine is idle.
 
 It coresponds with ARC target size lowering in last 5 days
 http://freebsd.quip.cz/ext/2012/2012-02-08-kiwi-mrtg-12-15/local_zfs_arcstats_size.html
 
 And with ARC metadata cache overflowing the limit in last 5 days
 http://freebsd.quip.cz/ext/2012/2012-02-08-kiwi-mrtg-12-15/local_zfs_vfs_meta.html

I'm not having luck finding it, but there's some known issue that exists even 
in 8.2 where some 32-bit counter overflows or something. I don't truly remember 
the logic in it, but when you hit it, it's around 110 days or so.  Before it 
gets really bad (to the point where you either reboot or get some memory 
exhaustion panic), you can see zfs evict skips incrementing rapidly.  Looking 
at that graph, that would be my guess as to what's happening to you.  It's easy 
to check - run one of the arc stats scripts, look for evict_skips, note the 
number and then run it a few minutes later.  If it increases by more than a few 
hundred, you've hit the bug.  You'll find at that point the kernel is no longer 
evicting ARC from the kernel and it will just continue to grow until bad 
things happen.

Charles

 
 I don't know what's going on and I don't know if it is something know / fixed 
 in newer releases. We are running a few more ZFS systems on 8.2 without this 
 issue. But those systems are in different roles.
 
 Miroslav Lachman
 ___
 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: zfs arc and amount of wired memory

[Charles Sprickman]

On Feb 8, 2012, at 7:43 PM, Artem Belevich wrote:

 On Wed, Feb 8, 2012 at 4:28 PM, Jeremy Chadwick
 free...@jdc.parodius.com wrote:
 On Thu, Feb 09, 2012 at 01:11:36AM +0100, Miroslav Lachman wrote:
 ...
 ARC Size:
  Current Size: 1769 MB (arcsize)
  Target Size (Adaptive):   512 MB (c)
  Min Size (Hard Limit):512 MB (zfs_arc_min)
  Max Size (Hard Limit):3584 MB (zfs_arc_max)
 
 The target size is going down to the min size and after few more
 days, the system is so slow, that I must reboot the machine. Then it
 is running fine for about 107 days and then it all repeat again.
 
 You can see more on MRTG graphs
 http://freebsd.quip.cz/ext/2012/2012-02-08-kiwi-mrtg-12-15/
 You can see links to other useful informations on top of the page
 (arc_summary, top, dmesg, fs usage, loader.conf)
 
 There you can see nightly backups (higher CPU load started at
 01:13), otherwise the machine is idle.
 
 It coresponds with ARC target size lowering in last 5 days
 http://freebsd.quip.cz/ext/2012/2012-02-08-kiwi-mrtg-12-15/local_zfs_arcstats_size.html
 
 And with ARC metadata cache overflowing the limit in last 5 days
 http://freebsd.quip.cz/ext/2012/2012-02-08-kiwi-mrtg-12-15/local_zfs_vfs_meta.html
 
 I don't know what's going on and I don't know if it is something
 know / fixed in newer releases. We are running a few more ZFS
 systems on 8.2 without this issue. But those systems are in
 different roles.
 
 This sounds like the... damn, what is it called... some kind of internal
 counter or ticks thing within the ZFS code that was discovered to
 only begin happening after a certain period of time (which correlated to
 some number of days, possibly 107).  I'm sorry that I can't be more
 specific, but it's been discussed heavily on the lists in the past, and
 fixes for all of that were committed to RELENG_8.  I wish I could
 remember the name of the function or macro or variable name it pertained
 to, something like LTHAW or TLOCK or something like that.  I would say
 I don't know why I can't remember, but I do know why I can't remember:
 because I gave up trying to track all of these problems.
 
 Does someone else remember this issue?  CC'ing Martin who might remember
 for certain.
 
 It's LBOLT. :-)
 
 And there was more than one related integer overflow. One of them
 manifested itself as L2ARC feeding thread hogging CPU time after about
 a month of uptime. Another one caused issue with ARC reclaim after 107
 days. See more details in this thread:
 
 http://lists.freebsd.org/pipermail/freebsd-fs/2011-May/011584.html

This would be an excellent piece of information to have on one of the ZFS
wiki pages.  The 107 day issue exists post-8.2, correct?  Anyone on this 
cc: list have permissions to edit those pages?

Thanks,

Charles

 
 --Artem
 ___
 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

8.1R possible zfs snapshot livelock?

[Charles Sprickman]

Hello,

Not sure if it's worth troubleshooting this too much before upgrading, but 
we recently had an 8.1R/amd64 box hang in a way that suggested everything 
was waiting on disk access.  It's remote and we had to resort to a 
power-cycle to bring it back (we have serial console, but it hung after 
accepting the root password).


We run hourly/daily/weekly/monthly snapshots on about a half dozen 
filesystems using RSE's snaphot script 
(see http://people.freebsd.org/~rse/snapshot/ - we only use the zfs 
snapshotting and do not use the amd portion).  We have some basic stats 
logged on all our boxes every 5 minutes and I saw a pile of cron jobs 
stuck in disk I/O wait.  I suspect these were the snapshots.  Shortly 
after that it seems as if all disk I/O got hung.


Some additional info about what the main tasks are on this box:

-qmail deliveries (lots)
-postgres (light use)
-nfs export of qmail log dirs to another box that does log analysis

All services are spread amongst a handful of jails.  Each jail has it's 
out zfs filesystem.


Does this sound familiar to anyone running ZFS with snapshots?  Anything I 
should log to get more data if this happens again?  I have output from 
arc_summary.pl running every 5 minutes as part of our general status 
logging.


Any pointers to known issues in ZFS (both 8.1 an 8.2) would be helpful.

Also, anywhere to look for the general state of ZFS besides this page?

http://wiki.freebsd.org/ZFS

Thanks,

Charles
___
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: 8.1R possible zfs snapshot livelock?

[Charles Sprickman]

On Tue, 17 May 2011, Andriy Gapon wrote:


on 17/05/2011 15:23 Jeremy Chadwick said the following:

So for Charles' situation, the next time it happens what would be useful
for him to provide?  The best I could come up with was to induce doadump
then reboot to get the system up/working again, and then use kgdb
after-the-fact.


This is one of the best things to do, if possible.
In this case all the potentially useful info would be preserved.


Will do.  Just have to verify I understand the break to debugger stuff 
with serial consoles and ensure it's not easy to accidentally trigger 
(vauge memories of Sun boxes doing funny things if someone messes with the 
console).


We're also going to start in on upgrading to 8.2 and see what that brings. 
Still sounds like a good idea to be able to force a dump if things lock up 
like this again, regardless of what we're running.



Less drastic approach to hanged I/O debugging is to find out where
processes/threads are actually stuck.  E.g. using procstat -kk.


Odd you say that because we've got an old 32-bit 8.1 box that's running 
spamassassin and some devel stuff that looks like it's getting a little 
wedged:


  PID USERNAME  THR PRI NICE   SIZERES STATETIME   WCPU COMMAND
6 root4  -8- 0K36K tx-tx 126.0H 76.37% zfskern

And I'm not sure procstat is meant for this, but the output is 
interesting:


[root@h22 /home/spork]# procstat -k 6
  PIDTID COMM TDNAME   KSTACK
6 100053 zfskern  arc_reclaim_thre mi_switch sleepq_switch 
sleepq_timedwait _cv_timedwait arc_reclaim_thread fork_exit 
fork_trampoline
6 100054 zfskern  l2arc_feed_threa mi_switch sleepq_switch 
sleepq_timedwait _cv_timedwait l2arc_feed_thread fork_exit fork_trampoline
6 100093 zfskern  txg_thread_enter mi_switch sleepq_switch 
sleepq_wait _cv_wait txg_thread_wait txg_quiesce_thread fork_exit 
fork_trampoline
6 100094 zfskern  txg_thread_enter mi_switch sleepq_switch 
sleepq_timedwait _cv_timedwait txg_thread_wait txg_sync_thread fork_exit 
fork_trampoline


Makes me curious about the patch mm@ has for 8.2 here:

http://blog.vx.sk/archives/24-Backported-patches-for-FreeBSD-82-RELEASE.html 
(item c in the list)


Anyhow, thank you *all* for an interesting discussion.  We do want to 
forge ahead with using snapshots since it's a really nice luxury, 
especially on boxes with lots of jails.  Makes it very easy to roll things 
back without having to go to the tapes.


Thanks,

Charles


--
Andriy Gapon
___
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: Kernel memory leak in 8.2-PRERELEASE?

[Charles Sprickman]

On Mon, 4 Apr 2011, Jeremy Chadwick wrote:


Finally, please note that most of the stuff you'll read online for ZFS
tuning on FreeBSD is outdated with 8.2.  E.g. you should not need to set
vm.kmem_size and you should never need to adjust vm.kmem_size_max.


Slight tangent, does this apply to i386 as well or just amd64?

Someone should open the zfs wiki page to a broader range of editors I 
think - it seems like this mailing list is the only decent reference for 
tuning these days.


Charles


--
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| 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


___
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: mps(4) driver (LSI 6Gb SAS) commited to stable/8

[Charles Sprickman]

On Sat, 19 Feb 2011, Dmitry Morozovsky wrote:


On Fri, 18 Feb 2011, Kenneth D. Merry wrote:

KDM I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb
KDM SAS hardware.

[snip]

Again, thank you very much Ken.  I'm planning to stress test this on 846 case
filled with 12 (yet) WD RE4 disks organized as raidz2, and will post the
results.

Any hints to particularly I/O stressing patterns?  Out of my mind, I'm planning
multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- what else
could you suppose?


benchmarks/iozone is nice, and you can get nifty graphs out of it.  It 
walks through various block sizes and is very long running.  It can 
probably tickle lots of stuff.  The results are also pretty informative - 
you can see very clearly in the graphs whatever your weak spots are.


http://www.iozone.org/

Charles



--
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: ma...@freebsd.org ]

*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***

___
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: ZFS - benchmark tuning before and after doubling RAM

[Charles Sprickman]

On Sat, 8 Jan 2011, Dan Langille wrote:

I've been running a ZFS array for about 10 months on a system with 4GB of 
RAM.  I'm about to add another 4GB of RAM.


I think this might be an opportune time to run some simple benchmarks and do 
some tuning.  Getting more out of the system is not a priority for me.  It 
does what I need now.  However, I do see some merit in writing something up 
for others to see/follow/learn.


The system is running FreeBSD 8.2-PRERELEASE #1: Tue Nov 30 22:07:59 EST 2010 
on a 64 bit box.  The ZFS array consists of 7x2TB commodity drives on two 
SiI3124 SATA controllers.  The OS runs off a gmirror RAID-1.


More details here: http://www.freebsddiary.org/zfs-benchmark.php

First, up, I've done a simple bonnie++ benchmark before I add more RAM.  I 
ran this on two different datasets; one with compression enabled, one 
without.


If anyone has suggestions for various tests, option settings, etc, I'm happy 
to run them and include the results.  We have lots of time to play with this.


iozone is interesting.  I bought the excel plugin from the developer to 
generate the nice 3D graphs.  I'd love to put some of my graphs up 
somewhere for comparison...  It's a very time-consuming test though.


Charles


--
Dan Langille - http://langille.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


___
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: unable to pwd in ZFS snapshot

[Charles Sprickman]

On Sun, 26 Dec 2010, Daniel Braniss wrote:


On Sun, Dec 26, 2010 at 09:26:13AM +0200, Daniel Braniss wrote:

this is still broken in 8.2-PRERELEASE, there seems to be a patch, but
it's almost a year old.
http://people.freebsd.org/~jh/patches/zfs-ctldir-vptocnp.diff


Setting snapdir to visible should fix this right away:
# zfs set snapdir=visible tank/foo


it did indeed!
any reason why this should not be the default behaviour?


Others mentioned rsync or cp (used recursively) might pick up these 
directories.  These are good reasons, especially if you've got a few 
hundred snapshots, which would not be uncommon when using ZFS on a host 
that's doing disk-based backups.


Other gotchas would be some of the periodic scripts - you don't want 
locate.updatedb traversing all that, or the setuid checks.  Also I know 
I'm prone to sometimes doing a brute-force find which can also dip into 
those hundreds of snapshot dirs.  In general, I think having the 
directories hidden is a good default.


Wouldn't be opposed to having the pwd issue fixed though...

Thanks,

Charles


thanks,
danny


___
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: Supported SAS controllers (single port)

[Charles Sprickman]

On Wed, 8 Dec 2010, Daniel O'Connor wrote:



On 08/12/2010, at 3:51, Mike Andrews wrote:

On 12/7/2010 8:00 AM, Daniel O'Connor wrote:

Does anyone have a recommendation for one?

I am looking to connect a LTO tape drive to a FreeBSD 7 or 8 box and I've only 
ever used Adaptec 19160 and similar cards and LVDS SCSI.

Our supplier has an LSI SAS3081E-R which is not outrageously expensive, has 
anyone used one?


Yes, I've got one, it works fine :)


Ahh, good news, thanks :)

Have you used it with a tape drive?


You may want to flash the non-raid firmware from LSI onto it.


OK thanks.

I just realised it doesn't have any external connectors so I'll have to 
find another candidate.


Have a look here, you might find something to bring an internal port out 
of the chassis:


http://www.scsi4me.com/sas-serial-attached-scsi-adapters.html?osCsid=fda686b95b73fe275aaa7bec038e1dbc

Charles


However I do see the LSI spec sheet for it lists the chip which is listed in 
mpt(4) so I should be able to find something.

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
 -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C








___
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: Using GTP and glabel for ZFS arrays

[Charles Sprickman]

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0:SiI 3124 SATA300 controller  port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on pci7

atapci1:SiI 3124 SATA300 controller  port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on pci3

I added ahci_load=YES to loader.conf and rebooted.  Now I see:


You can add siis_load=YES to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that the ZFS 
array will be messed up.  But I do plan to do that for the system after my 
plan is implemented.  Thank you.  :)


You may even get hotplug support if you're lucky. :)

I just built a box and gave it a spin with the old ata stuff and then 
with the new (AHCI) stuff.  It does perform a bit better and my BIOS 
claims it supports hotplug with ahci enabled as well...  Still have to 
test that.


Charles


--
Dan Langille - http://langille.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


___
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: Using GTP and glabel for ZFS arrays

[Charles Sprickman]

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 3:30 AM, Charles Sprickman wrote:

On Thu, 22 Jul 2010, Dan Langille wrote:


On 7/22/2010 2:59 AM, Andrey V. Elsukov wrote:

On 22.07.2010 10:32, Dan Langille wrote:

I'm not sure of the criteria, but this is what I'm running:

atapci0:SiI 3124 SATA300 controller port 0xdc00-0xdc0f mem
0xfbeffc00-0xfbeffc7f,0xfbef-0xfbef7fff irq 17 at device 4.0 on
pci7

atapci1:SiI 3124 SATA300 controller port 0xac00-0xac0f mem
0xfbbffc00-0xfbbffc7f,0xfbbf-0xfbbf7fff irq 19 at device 4.0 on
pci3

I added ahci_load=YES to loader.conf and rebooted. Now I see:


You can add siis_load=YES to loader.conf for SiI 3124.


Ahh, thank you.

I'm afraid to do that now, before I label my ZFS drives for fear that
the ZFS array will be messed up. But I do plan to do that for the
system after my plan is implemented. Thank you. :)


You may even get hotplug support if you're lucky. :)

I just built a box and gave it a spin with the old ata stuff and then
with the new (AHCI) stuff. It does perform a bit better and my BIOS
claims it supports hotplug with ahci enabled as well... Still have to
test that.


Well, I don't have anything to support hotplug.  All my stuff is internal.

http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs430.ash1/23778_106837706002537_10289239443_171753_3508473_n.jpg


The frankenbox I'm testing on is a retrofitted 1U (it had a scsi 
backplane, now has none).


I am not certain, but I think with 8.1 (which it's running) and all the 
cam integration stuff, hotplug is possible.  Is a special backplane 
required?  I seriously don't know...  I'm going to give it a shot though.


Oh, you also might get NCQ.  Try:

[r...@h21 /tmp]# camcontrol tags ada0
(pass0:ahcich0:0:0:0): device openings: 32

Charles




--
Dan Langille - http://langille.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: Using GTP and glabel for ZFS arrays

[Charles Sprickman]

On Thu, 22 Jul 2010, Boris Samorodov wrote:


On Wed, 21 Jul 2010 23:15:41 -0400 Dan Langille wrote:

On 7/21/2010 11:05 PM, Dan Langille wrote (something close to this):



First, create a new GUID Partition Table partition scheme on the HDD:
gpart create -s GPT ad0

Let's see how much space we have. This output will be used to determine
SOMEVALUE in the next command.

gpart show

Create a new partition within that scheme:
gpart add -b 34 -s SOMEVALUE -t freebsd-zfs ad0

Now, label the thing:
glabel label -v disk00 /dev/ad0


That command will destroy secondary GPT.


I was just reading about GUID partitioning last night and saw that one of 
the benefits is that there's a copy of the partition table kept at the end 
of the disk.  That seems like a pretty neat feature.


Do you by any chance have a reference I can point to (I was documenting 
stuff about GPT in an internal wiki and this is a nice piece of info to 
have)?


Also, how does one access/use the backup partition table?

Thanks,

Charles


Or, is this more appropriate?
  glabel label -v disk00 /dev/ad0s1


--
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: Problems replacing failing drive in ZFS pool

[Charles Sprickman]

On Tue, 20 Jul 2010, alan bryan wrote:




--- On Mon, 7/19/10, Dan Langille d...@langille.org wrote:


From: Dan Langille d...@langille.org
Subject: Re: Problems replacing failing drive in ZFS pool
To: Freddie Cash fjwc...@gmail.com
Cc: freebsd-stable freebsd-stable@freebsd.org
Date: Monday, July 19, 2010, 7:07 PM
On 7/19/2010 12:15 PM, Freddie Cash
wrote:
 On Mon, Jul 19, 2010 at 8:56 AM, Garrett Mooregarrettmo...@gmail.com 
wrote:

 So you think it's because when I switch from the
old disk to the new disk,
 ZFS doesn't realize the disk has changed, and
thinks the data is just
 corrupt now? Even if that happens, shouldn't the
pool still be available,
 since it's RAIDZ1 and only one disk has gone
away?
 
 I think it's because you pull the old drive, boot with

the new drive,
 the controller re-numbers all the devices (ie da3 is
now da2, da2 is
 now da1, da1 is now da0, da0 is now da6, etc), and ZFS
thinks that all
 the drives have changed, thus corrupting the
pool.  I've had this
 happen on our storage servers a couple of times before
I started using
 glabel(8) on all our drives (dead drive on RAID
controller, remove
 drive, reboot for whatever reason, all device nodes
are renumbered,
 everything goes kablooey).

Can you explain a bit about how you use glabel(8) in
conjunction with ZFS?  If I can retrofit this into an
exist ZFS array to make things easier in the future...

8.0-STABLE #0: Fri Mar  5 00:46:11 EST 2010

]# zpool status
  pool: storage
 state: ONLINE
 scrub: none requested
config:

        NAME 
STATE     READ WRITE CKSUM

        storage
   ONLINE
   0     0
   0
          raidz1 
ONLINE       0

   0     0
            ad8
   ONLINE
   0     0
   0
            ad10 
ONLINE       0

   0     0
            ad12 
ONLINE       0

   0     0
            ad14 
ONLINE       0

   0     0
            ad16 
ONLINE       0

   0     0

 Of course, always have good backups.  ;)

In my case, this ZFS array is the backup.  ;)

But I'm setting up a tape library, real soon now

-- Dan Langille - http://langille.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



Dan,

Here's how to do it after the fact:

http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2009-07/msg00623.html


Two things:

-What's the preferred labelling method for disks that will be used with 
zfs these days?  geom_label or gpt labels?  I've been using the latter and 
I find them a little simpler.


-I think that if you already are using gpt partitioning, you can add a 
gpt label after the fact (ie: gpart -i index# -l your_label adaX).  gpart 
list will give you a list of index numbers.


Charles


--Alan Bryan
___
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: Problems replacing failing drive in ZFS pool

[Charles Sprickman]

On Wed, 21 Jul 2010, Charles Sprickman wrote:


On Tue, 20 Jul 2010, alan bryan wrote:




--- On Mon, 7/19/10, Dan Langille d...@langille.org wrote:


From: Dan Langille d...@langille.org
Subject: Re: Problems replacing failing drive in ZFS pool
To: Freddie Cash fjwc...@gmail.com
Cc: freebsd-stable freebsd-stable@freebsd.org
Date: Monday, July 19, 2010, 7:07 PM
On 7/19/2010 12:15 PM, Freddie Cash
wrote:
 On Mon, Jul 19, 2010 at 8:56 AM, Garrett Mooregarrettmo...@gmail.com 
wrote:

 So you think it's because when I switch from the
old disk to the new disk,
 ZFS doesn't realize the disk has changed, and
thinks the data is just
 corrupt now? Even if that happens, shouldn't the
pool still be available,
 since it's RAIDZ1 and only one disk has gone
away?
  I think it's because you pull the old drive, boot with
the new drive,
 the controller re-numbers all the devices (ie da3 is
now da2, da2 is
 now da1, da1 is now da0, da0 is now da6, etc), and ZFS
thinks that all
 the drives have changed, thus corrupting the
pool.  I've had this
 happen on our storage servers a couple of times before
I started using
 glabel(8) on all our drives (dead drive on RAID
controller, remove
 drive, reboot for whatever reason, all device nodes
are renumbered,
 everything goes kablooey).

Can you explain a bit about how you use glabel(8) in
conjunction with ZFS?  If I can retrofit this into an
exist ZFS array to make things easier in the future...

8.0-STABLE #0: Fri Mar  5 00:46:11 EST 2010

]# zpool status
  pool: storage
 state: ONLINE
 scrub: none requested
config:

        NAME STATE     READ WRITE CKSUM
        storage
   ONLINE
   0     0
   0
          raidz1 ONLINE       0
   0     0
            ad8
   ONLINE
   0     0
   0
            ad10 ONLINE       0
   0     0
            ad12 ONLINE       0
   0     0
            ad14 ONLINE       0
   0     0
            ad16 ONLINE       0
   0     0

 Of course, always have good backups.  ;)

In my case, this ZFS array is the backup.  ;)

But I'm setting up a tape library, real soon now

-- Dan Langille - http://langille.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



Dan,

Here's how to do it after the fact:

http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2009-07/msg00623.html


Two things:

-What's the preferred labelling method for disks that will be used with zfs 
these days?  geom_label or gpt labels?  I've been using the latter and I find 
them a little simpler.


-I think that if you already are using gpt partitioning, you can add a gpt 
label after the fact (ie: gpart -i index# -l your_label adaX).  gpart list 
will give you a list of index numbers.


Oops.

That should be gpart modify -i index# -l your_label adax.


Charles


--Alan Bryan
___
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: Using GTP and glabel for ZFS arrays

[Charles Sprickman]

On Wed, 21 Jul 2010, Adam Vande More wrote:


On Wed, Jul 21, 2010 at 10:05 PM, Dan Langille d...@langille.org wrote:


Why '-b 34'?  Randi pointed me to
http://en.wikipedia.org/wiki/GUID_Partition_Table where it explains what
the first 33 LBA are used for.  It's not for us to use here.

Where SOMEVALUE is the number of blocks to use.  I plan not to use all the
available blocks but leave a few hundred MB free at the end. That'll allow
for the variance in HDD size.

Any suggestions/comments?  Is there any advantage to using the -l option on
'gpart add' instead of the glabel above?



You'll want to make sure your partitions are aligned, discussion here(says
4k drives, but info pertinent to all):

http://lists.freebsd.org/pipermail/freebsd-hackers/2010-March/031154.html



From that thread:


http://lists.freebsd.org/pipermail/freebsd-hackers/2010-March/031173.html

(longer explanation)

I'm not really understanding the alignment issue myself on a few levels:

-Does it only affect the new drives with 4K blocks?
-If it does not, is it generally good to start your first partition at 1MB 
in?  How exactly does doing this fix the alignment issue?



My understanding is that you weren't booting from zfs, just using it as an
data file system.  In that case, you'd want to use gpart add -b 512 ...
or some other multiple of 16.  Even 1024 would be a good safe number.  Also
GPT creates partitions not slices.  Your resulting partitions with be
labeled something like ad0p1, ad0p2, etc.


I assume the same can be applied if you do boot from zfs; you'd still 
create the freebsd-boot partition starting at 34, but your next 
partition (be it swap or zfs) would start either 512 or 1024 sectors in?


Thanks,

Charles




--
Adam Vande More
___
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

amd64 mainboard compatibility list

[Charles Sprickman]

While trying to find how not to get burned like we did with some older 
oddball Supermicro boards, I came across this page:


http://www.freebsd.org/platforms/amd64/motherboards.html

There is a request up top for new submissions (there are no 8.x 
entries), is feedback still wanted?  If so, I've got a number of bad 
boards to add.


I cannot stress enough how great it would be if this were updated.  I'm 
server shopping at the moment and after running into various SMP and ACPI 
issues on some SM boards, I'm quite nervous about committing to any 
particular model or brand.


Thanks,

Charles

___
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: Locking a file backed mdconfig into memory

[Charles Sprickman]

On Tue, 1 Jun 2010, John Baldwin wrote:


On Monday 31 May 2010 2:45:25 pm Jeremy Chadwick wrote:

On Mon, May 31, 2010 at 11:25:51AM -0700, Dave Hayes wrote:

Jeremy Chadwick free...@jdc.parodius.com writes:

Is the mfsroot file compressed (.gz extension)?  Reason I ask is that
the OP states he's using RELENG_7...


Yes it is compressed.


http://jdc.parodius.com/freebsd/pxeboot_serial_install_7.html#step7


Thanks much for this. I did a simple test, I rebuilt a DVD that wasn't
booting to use a lower level of compression (gzip -9 to gzip -6) on
mfsroot without changing anything else. This caused it to boot normally.

I'm not sure it's conclusive evidence, but it certainly looks like a
weak datapoint supporting this kernel bug being the source of my
problem.

Is this problem fixed in 8.0 or by a patch?


With regards to said bug, gzip compression seems to work fine on
RELENG_8, at least in my experiences:

http://jdc.parodius.com/freebsd/pxeboot_serial_install_8.html

I'm not sure the level of compression is what triggers the bug though;
I haven't tested all levels (1 through 9).

CC'ing jhb@ since he last updated PR kern/120127 (which I would say is
still a problem on RELENG_7 :-) ).  John, are you aware of any gzip
decompression / mfsroot changes which might explain the problem on
RELENG_7?  I haven't done a thorough series of tests, but on my
testbed boxes RELENG_8 works fine with a gzip'd mfsroot.


Ok, if you are using a stock mfsroot from a release build, that should work
fine.  If you have built a custom mfsroot that is larger, then you may need to
increase NKPT on i386.  In very recent 7 and later you can do this by setting
it to a new value in your kernel config.  In older versions you can do this by
manually adding a #define to set a new value of NKPT in opt_global.h or
hacking on the source directly.


This is the original post I found confirming all this:

http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2004-02/0241.html

I can also confirm your changes that allow it to be a kernel config option 
works as well. :)


It's nice to essentially have a full livefs as your mfsroot for 
non-sysinstall installs.


Charles


--
John Baldwin
___
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

7.2 filesystem corruption

[Charles Sprickman]

Hello all,

Not sure where to go with this post, I've tried -fs and -scsi previously 
in trying to track down some panics in the softdep stuff.  Perhaps the 
more general audience here can shove me in the right direction.


I have a box (Dell PE 2970) running FreeBSD 7.2/amd-64.  6 GB of ECC RAM, 
and a Dell-branded LSI RAID controller (mpt driver).  It's a mail server 
with the active mail server running in a jail and a test version of same 
running in another jail (qmail/vpopmail/courier on old, 
postfix/pfadmin/dovecot on new).


It passed a few weeks of heavy stress testing where I was putting much 
more load on it using an imap/pop/smtp test suite before going into 
production with only one panic (which happened during a fairly intense 
mstone run) - I figured I was somewhat on the bleeding edge with 7.x 
64-bit at that time, so I was not overly concerned since I've run into 
softdep panics before.  Since then however, there have been a few panics 
in ufsdirhash_lookup.


When this happens, the box reboots, does a background fsck and does not 
complain about anything.  I decided background fsck was probably not a 
good idea, so I disabled it and manually fsck'd on all subsequent panics. 
The pattern is similar to this example:


** /dev/mfid0s1g
** Last Mounted on /spool
** Phase 1 - Check Blocks and Sizes
UNKNOWN FILE TYPE I=147718184
UNEXPECTED SOFT UPDATE INCONSISTENCY
CLEAR? yes

PARTIALLY ALLOCATED INODE I=147718185
UNEXPECTED SOFT UPDATE INCONSISTENCY

And in phase 2, lots of this:

UNALLOCATED I=152688468 OWNER=root MODE=0 SIZE=0 MTIME=Dec 31 19:00 1969 
NAME=/jails/mailbak.blah.net/home/vpopmail/domains/blah.net/A/spec/Maildir/new/1233549930.73014.blah.bway.net


UNEXPECTED SOFT UPDATE INCONSISTENCY
REMOVE? yes

And in Phase 4, lots of this:

** Phase 4 - Check Reference Counts
UNREF FILE I=147623979  OWNER=88 MODE=100600
SIZE=0 MTIME=Feb  7 00:19 2010
CLEAR? yes

In the manual runs, I tend to run through about 3 or 4 times, since even 
though the filesystem gets marked clean, another run finds more errors. 
Once I get two clean runs in a row, I let the box boot.


Regardless of how clean the fs is, I have consistently seen messages 
like this in my serial console log:


g_vfs_done():mfid0s1g[READ(offset=2456998070156636160, length=16384)]error 
= 5
g_vfs_done():mfid0s1g[READ(offset=2456998070156636160, length=16384)]error 
= 5


On the last run, I also turned off soft updates for good measure.

Now I occasinally get these errors:

g_vfs_done():mfid0s1g[READ(offset=533538894859648, length=16384)]error 
= 5
bad block 838May 18 00:29:14 8bigmail kernel: 3pid 24481 (rm), 0uid 0 
inumber 1571657736 on /spoo6l: bad block

76548920427, ino 151657736

In addition, there are some files that now have bizarre flags set, such as 
schg, sappnd, opaque, etc.  Some can be changed, others give a bad 
file descriptor error.


I fear the fs is getting more scrambled.

I started to think that I'm probably dealing with two things - some bug in 
64-bit UFS2, plus a perpetually dirty filesystem that causes the box to 
panic, which causes more corruption, and so on.


I do have the option of trying to schedule a huge maintenance window and 
dumping the fs, newfs'ing it, and then restoring it, but it's a tough sell 
and for various reasons I can't put a ton of time into this (anyone that 
knows me, hit me up offlist for a fun story).  I'm also quite concerned 
that fsck is finding and fixing things, but the fs is still obviously not 
quite right.  In short, how can I ensure this won't happen a week after 
a dump/restore?


So that's the story, here's my questions:

-Is there any interest in tracking down what the nature of the initial 
panic/corruption is?  I know I'm a release behind, but digging through the 
PR database, nothing stuck out as far as softdep, mpt, or dirhash bugs 
that looked similar to what I'm seeing that got fixed in 7.3.


-Where is the most likely place to look for a problem here?  The mpt 
driver?  The megacli utility and the bios utility both claim the array is 
in great shape.  The only fs that ever shows the errors with g_vfs_done 
and the nonsensical offsets is the partition where the jails reside.  Or 
is it ufsdirhash thing?  I saw some interesting bug reports, but nothing 
that quite matched.  UFS2/SU itself?


-If I do dump/restore (or pull from backups), should I stick to 7.2 or go 
to 7.3 while I'm working on the box?  Or gamble on 8.0 (where I've oddly 
enough seen much fewer odd thigns of late)?


For reference, here's a few other queries regarding this issue:

http://marc.info/?l=freebsd-stablem=125901173424554w=2
http://old.nabble.com/7.2-p4:-panic:-ufsdirhash_lookup:-bad-offset-in-hash-array-td27715632.html

I still have some core dumps sitting here as well.

Any input would be appreciated - I do have more info available, but this 
message is already about twice as long as I'd like it to be.  Hit me up 
with any questions.


Thanks,

Charles

Re: 7.2 filesystem corruption

[Charles Sprickman]

On Fri, 21 May 2010, Bob Bishop wrote:


Hi,

On 21 May 2010, at 09:04, Charles Sprickman wrote:


Hello all,

[...]I have a box (Dell PE 2970) running FreeBSD 7.2/amd-64.  6 GB of 
ECC RAM, and a Dell-branded LSI RAID controller (mpt driver). [tale of 
woe elided]


For any case of spooky behaviour involving SCSI, make completely sure 
that the SCSI cabling is above suspicion. If it isn't, your sanity will 
be the first casualty.


FWIW, this is SATA.  I hit up -scsi since I (think) that's where whoever 
deals with mpt(4) lives.  The controller does present the array as a scsi 
device, but thankfully (oh so very thankfully), there's no scsi cabling 
involved.  Say what you will about SATA and SAS, but I'm really happy to 
not have to deal with terminators, jumpers and all that other drek 
anymore.


Thanks,

Charles


--
Bob Bishop
r...@gid.co.uk






___
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: ZFS: separate pools

[Charles Sprickman]

On Sun, 2 May 2010, Wes Morgan wrote:


On Sun, 2 May 2010, Eric Damien wrote:


Hello list.

I am taking my first steps with ZFS. In the past, I used to have two UFS
slices: one dedicated to the o.s. partitions, and the second to data (/home,
etc.). I read on that it was possible to recreate that logic with zfs, using
separate pools.

Considering the example of
   http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot,
any idea how I can adapt that to my needs? I am concerned about all the
different mountpoints.


Well, you need not create all those filesystems if you don't want them.
The pool and FreeBSD will function just fine.

However, as far as storage is concerned, there is no disadvantage to
having additional mount pounts. The only limits each filesystem will have
is a limit you explicitly impose. There are many advantages, though. Some
datasets are inherently compressible or incompressible. Other datasets you
may not want to schedule for snapshots, or allow files to be executed,
suid, checksummed, block sizes, you name it (as the examples in the wiki
demonstrate).

Furthermore, each pool requires its own vdev. If you create slices on a
drive and then make each slice its own pool, I would wonder if zfs's
internal queuing would understand the topology and be able to work as
efficiently. Just a thought, though.


I have two boxes setup where zfs is on top of slices like that.  One has a 
small zpool across 3 disks - the rest of those disks and 3 other disks of 
the same size also make up another zpool.  The hardware is old, so 
performance just is not spectacular (old 8 port 3Ware PATA card).  I can't 
tell if this config is contributing to the somewhat anemic (by today's 
standards) r/w speeds or not.


Another has 4 drives with a gmirror setup on two of the drives for the OS 
(20G out of 1TB).  This box performs extremely well (bonnie++ shows 
123MB/s writes, 142MB/s reads).


Just some random data.  I know when I was reading about ZFS I did come 
across some vague notion that zfs wanted the entire drive to better deal 
with queueing, not sure if that was official Sun docs or some random blog 
though...


Charles


___
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: Results of BIND RFC

[Charles Sprickman]

Can we do sendmail next April 1?

Sent from a device with a tiny keyboard


On Apr 2, 2010, at 1:22 PM, Reko Turja reko.tu...@liukuma.net wrote:

Based on the inspection of the source tree, I want my bikeshed  
mauve. I've not been had by AFD jokes in a while but Doug pulled  
this one off...


-Reko
___
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: Does zfs have it's own nfs server?

[Charles Sprickman]

On Sat, 20 Mar 2010, Willem Jan Withagen wrote:


On 20-3-2010 0:50, Charles Sprickman wrote:

Just wondering, is this using the base nfsd/mountd, or is there some
in-kernel nfs code strictly for zfs? I haven't found much info on the
share* options in the manpage or wiki.


There's also the complete ZFS manual you should read:
http://dlc.sun.com/pdf/819-5461/819-5461.pdf


Anyone know how to tie the version of that document to the current version 
that's in FreeBSD?


Overall, it's a great reference.  Already answered a number of questions.

Here's another Sun doc that I used to get started:

http://hub.opensolaris.org/bin/download/Community+Group+zfs/demos/zfsdemo.pdf

It looks like it's for sales engineers who are going to do a demo of ZFS, 
however it works quite well as a quick-start.  It describes the basic 
concepts well and walks you through creating some pools.  It's hands-down 
my favorite Intro to ZFS doc that I've found so far.


Thanks,

Charles

It's for Solaris, so perhaps not everything works on FreeBSD. But most of it 
will.



Could you give an example of passing options that would say, limit to a
subnet and map root to root using the zfs sharenfs command?


Something like this: (Email might wrap the line)
	zfs set sharenfs='-alldirs -maproot=0 -network 192.168.10.0 -mask 
255.255.255.0' zfsdata/home/wjw


to export /home/wjw which is available as /zfsdata/home/wjw in ZFS.

All the zfs does is add this to the /etc/zfs/exports file.
And then the regular mountd/nfsd combo does the NDS-service.

--WjW





___
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: Does zfs have it's own nfs server?

[Charles Sprickman]

On Fri, 19 Mar 2010, Willem Jan Withagen wrote:


On 17-3-2010 9:27, Matthias Gamsjager wrote:

sharenfs does work in freebsd but iscsi does not. I'm not sure about smb.

about nfs: you should take a look at /etc/zfs/exports



On Wed, Mar 17, 2010 at 9:15 AM, Harald Schmalzbauer
h.schmalzba...@omnilan.de  wrote:

Hello,

I observed some very strange filesystem security problems.
Now I found that if I set sharenfs=yes data/pub I can mount_nfs but it
does't respect any settings in /etc/exports. Also I get very strange uid
numbers when writing.
If I turn sharenfs off, limitations in /etc/exports work as expected.
I thought sharenfs and sharesmb are only working on OpenSolaris. What 
about

shareiscsi?


I do not use /etc/exports for zfs shares
But instead of yes as value, you can use the NFS-options as string and that 
gets it into /etc/zfs/exports.


Just wondering, is this using the base nfsd/mountd, or is there some 
in-kernel nfs code strictly for zfs?  I haven't found much info on the 
share* options in the manpage or wiki.


Could you give an example of passing options that would say, limit to a 
subnet and map root to root using the zfs sharenfs command?


Thanks,

Charles


--WjW
___
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

7.2-p4: panic: ufsdirhash_lookup: bad offset in hash array

[Charles Sprickman]

I have a box that has paniced two nights in a row with this error.  I have 
a corefile from last night, but tonight's failed:


Uptime: 23h55m22s
Physical memory: 6130 MB
Dumping 759 MB: 744 728 712 696 680 664 648
** DUMP FAILED (ERROR 16) **

Here's some info from the core I do have:

#0  doadump () at pcpu.h:195
195 __asm __volatile(movq %%gs:0,%0 : =r (td));
(kgdb) where
#0  doadump () at pcpu.h:195
#1  0x0004 in ?? ()
#2  0x8034c799 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:418
#3  0x8034cba2 in panic (fmt=0x104 Address 0x104 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:574
#4  0x8052545f in ufsdirhash_lookup (ip=0xff0012530398,
name=0xff012788b000 
1266473205.M123372P75411V005BI08EE5F75_0.xena.bway.net,S=43650:2,S, 
namelen=70, offp=0x285f474c,

bpp=0x285f4738, prevoffp=0x0)
at /usr/src/sys/ufs/ufs/ufs_dirhash.c:599
#5  0x805278a0 in ufs_lookup (ap=0x285f4790)
at /usr/src/sys/ufs/ufs/ufs_lookup.c:224
#6  0x803be024 in vfs_cache_lookup (ap=Variable ap is not 
available.) at vnode_if.h:83

#7  0x805a08bf in VOP_LOOKUP_APV (vop=0x807945c0,
a=0x285f4850) at vnode_if.c:99
#8  0x803c4a4f in lookup (ndp=0x285f4960) at vnode_if.h:57
#9  0x803c58ba in namei (ndp=0x285f4960)
at /usr/src/sys/kern/vfs_lookup.c:215
#10 0x803d2c94 in kern_lstat (td=0xff007693aa50, path=Variable 
path is not available.

)   at /usr/src/sys/kern/vfs_syscalls.c:2184
#11 0x803d2f07 in lstat (td=Variable td is not available.
) at /usr/src/sys/kern/vfs_syscalls.c:2167
#12 0x80574e77 in syscall (frame=0x285f4c80)
at /usr/src/sys/amd64/amd64/trap.c:900
#13 0x805598ab in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:330
#14 0x00080071063c in ?? ()
Previous frame inner to this frame (corrupt stack?)

Previous to this, I had one panic while this box was being stress-tested 
before it went into production.  It's a new Dell box with a Dell/LSI RAID 
card (mfi driver).  It's a mail server, and the ufs dirhash sysctl is 
pushed up to vfs.ufs.dirhash_maxmem=33554432.


Previous post on the previous panic back in November is here:
http://marc.info/?l=freebsd-stablem=125901173424554w=2

Before last night's crash, it was up for 93 days.  Nothing has changed in 
the past few days as far as software or overall load.  The crash did 
happen during or shortly after the daily periodic run.


Any interest in this one?  Is it something to file a PR on?

dmesg is below...

Thanks,

Charles
___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
sp...@bway.net - 212.655.9344

Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.2-RELEASE-p4 #2: Mon Nov  2 21:55:12 EST 2009
sp...@bigmail.bway.net:/usr/obj/usr/src/sys/BWAY7-64
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Quad-Core AMD Opteron(tm) Processor 2372 HE (2094.76-MHz K8-class CPU)
  Origin = AuthenticAMD  Id = 0x100f42  Stepping = 2
  
Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT
  Features2=0x802009SSE3,MON,CX16,b23
  AMD 
Features=0xee500800SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!
  AMD 
Features2=0x37ffLAHF,CMP,SVM,ExtAPIC,CR8,b5,b6,b7,Prefetch,b9,b10,b12,b13
  TSC: P-state invariant
  Cores per package: 4
usable memory = 6427951104 (6130 MB)
avail memory  = 6198829056 (5911 MB)
ACPI APIC Table: DELL   PE_SC3  
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
ioapic0: Changing APIC ID to 4
ioapic1: Changing APIC ID to 5
ioapic2: Changing APIC ID to 6
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 Version 1.1 irqs 0-15 on motherboard
ioapic1 Version 1.1 irqs 32-47 on motherboard
ioapic2 Version 1.1 irqs 64-79 on motherboard
kbd0 at kbdmux0
acpi0: DELL PE_SC3 on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
ipmi0: KCS mode found at io 0xca8 on acpi
Timecounter ACPI-safe frequency 3579545 Hz quality 850
acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0
Timecounter HPET frequency 14318180 Hz quality 900
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci8: ACPI PCI bus on pcib1
pcib2: ACPI PCI-PCI bridge at device 13.0 on pci8
pci9: ACPI PCI bus on pcib2
atapci0: ServerWorks HT1000 SATA150 controller port 
0xdcb0-0xdcb7,0xdca0-0xdca3,0xdcb8-0xdcbf,0xdca4-0xdca7,0xdce0-0xdcef mem

netboot issues, 8.0, mfsroot mount failure

[Charles Sprickman]

Howdy,

I'm having some problems getting 8.0 to install over the network.  I've 
got my dhcp, tftp and nfs server working well, and I've tested all three 
services from this host before attempting to boot over the network.


pxeboot seems to work, and I see it get loaded via tftp.  The kernel 
boots, and parses the options in loader.conf that exist in my nfs-exported 
8.0 DVD fileset:


[r...@archive /home/spork/tmp]# cat 
/usr/local/netboot/freebsd8/boot/loader.conf

mfsroot_load=YES
mfsroot_type=mfs_root
mfsroot_name=/boot/mfsroot
boot_multicons=YES
boot_serial=YES
console=comconsole,vidconsole
vfs.root.mountfrom=ufs:/dev/md0c

I see the kernel does find mfsroot and attaches it:

md0: Preloaded image /boot/mfsroot 4423680 bytes at 0xc0f6dfe0

But then when it's ready to mount the root filesystem, I get this:

SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/md0c
ROOT MOUNT ERROR:

If you have invalid mount options, reboot, and first try the following 
from the loader prompt:


 set vfs.root.mountfrom.options=rw

and then remove invalid mount options from /etc/fstab.

It doesn't really state what the error is.  It's hinting that it's 
read-only, but that seems odd.  Even if it couldn't mount r/w, shouldn't 
it just drop to single-user at this point?


Next it tries nfs:

Trying to mount root from nfs:
NFS ROOT: 192.168.1.111:/usr/local/netboot/freebsd8
em0: link state changed to UP

And there it sits.  Remotely I can't do anything.  If I'm local, I can 
ctrl-alt-del a few times and then about a minute later it does an orderly 
restart.


I'm not aware of a good way to snoop on nfs traffic, but tcpdump shows nfs 
traffic between the two hosts, which appears to be the client stat-ing a 
file or directory.  tcpdump also shows some checksum errors, but I recall 
a few threads here mentioning that on Intel cards that generally is not a 
cause for concern.



From another host, I have no issues mounting that nfs filesystem r/w:


r...@h10[/home/spork]# mount_nfs 192.168.1.111:/usr/local/netboot/freebsd8 
/mntr...@h10[/home/spork]# ls /mnt/

.cshrc  HARDWARE.TXTboot.catalogmedia   sbin
.profileREADME.HTM  cdrom.inf   mnt stand
8.0-RELEASE README.TXT  dev packagessys
COPYRIGHT   RELNOTES.HTMdocbook.css proctmp
ERRATA.HTM  RELNOTES.TXTetc rescue  usr
ERRATA.TXT  bin lib rootvar
HARDWARE.HTMbootlibexec rr_moved
r...@h10[/home/spork]# touch /mnt/foo
r...@h10[/home/spork]# rm /mnt/foo
r...@h10[/home/spork]# umount /mnt

Any ideas?  I've got about a dozen remote boxes to upgrade, so I want to 
totally nail down this procedure.  I've been putting off learning this for 
a few years, and now I've got an actual need for it.


Thanks,

Charles
___
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: netboot issues, 8.0, mfsroot mount failure

[Charles Sprickman]

On Tue, 16 Feb 2010, Jeremy Chadwick wrote:


On Tue, Feb 16, 2010 at 08:28:03PM -0500, Charles Sprickman wrote:

Howdy,

I'm having some problems getting 8.0 to install over the network.
I've got my dhcp, tftp and nfs server working well, and I've tested
all three services from this host before attempting to boot over the
network.

pxeboot seems to work, and I see it get loaded via tftp.  The kernel
boots, and parses the options in loader.conf that exist in my
nfs-exported 8.0 DVD fileset:

[r...@archive /home/spork/tmp]# cat
/usr/local/netboot/freebsd8/boot/loader.conf
mfsroot_load=YES
mfsroot_type=mfs_root
mfsroot_name=/boot/mfsroot
boot_multicons=YES
boot_serial=YES
console=comconsole,vidconsole
vfs.root.mountfrom=ufs:/dev/md0c

I see the kernel does find mfsroot and attaches it:

md0: Preloaded image /boot/mfsroot 4423680 bytes at 0xc0f6dfe0

But then when it's ready to mount the root filesystem, I get this:

SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/md0c
ROOT MOUNT ERROR:

If you have invalid mount options, reboot, and first try the
following from the loader prompt:

 set vfs.root.mountfrom.options=rw

and then remove invalid mount options from /etc/fstab.

It doesn't really state what the error is.  It's hinting that it's
read-only, but that seems odd.  Even if it couldn't mount r/w,
shouldn't it just drop to single-user at this point?

Next it tries nfs:

Trying to mount root from nfs:
NFS ROOT: 192.168.1.111:/usr/local/netboot/freebsd8
em0: link state changed to UP

And there it sits.  Remotely I can't do anything.  If I'm local, I
can ctrl-alt-del a few times and then about a minute later it does
an orderly restart.


We've been talking off-list about this (and other things), but at this
point I'm pretty sure the problem is that the local slice naming
convention has changed in RELENG_8 from what it was in RELENG_7.

This is the cause/result of the GEOM overhall (or whatever it is; I
don't know what to call it.  Is it libdisk changes?  GEOM?  Both?  I
really don't know).  Basically, the way the full size of the disk gets
handled differs now from RELENG_7.  (See footnote for fun)  So, try
changing this:

vfs.root.mountfrom=ufs:/dev/md0c

...to this (look closely):

vfs.root.mountfrom=ufs:/dev/md0


I made the change on the server, but the box is stuck until I can get over 
there again.  Serial consoles are nice, but not being able to send 
ctrl-alt-del is a sad limitation. :)



Remember: the mfsroot image is essentially a UFS filesystem that's
mounted as memory disk.  Since you re-created mfsroot (like you're
supposed to :-) ) on a RELENG_8 box, the layout is different.


In this case, I'm still using the stock 8.0 mfsroot.  The only change was 
to un-gzip it.  But this particular issue is probably due to the geom 
change you noted, so we'll see what happens on reboot.



The NFS root mount you see happening later is a result of the root
filesystem not being available.  This is normal if mfsroot fails.


I'm still stumped as to why it hangs there.  I do have something for it to 
mount there via NFS (the 8.0 dvd contents), and it appears to try, but 
then it just sits there.  Not locked up, just waiting...



Please let me (on the list) know if this fixes your problem.


As soon as she boots, I'll report back.


Footnote: This is why I tell folks to zero out the first 8192 bytes of
any disk they've previously installed FreeBSD on (even if the disk has
no filesystems/slices on it).  The way FreeBSD determines the size of
the disk differs in RELENG_8; I believe GEOM figures it out on its own
now, while previous releases relied on the c slice.  The method I've
recommended: do dd if=/dev/zero of=/dev/adX bs=512 count=16.


Is it also advisable to blot out any old glabel stuff at the end of the 
disk?  What's the math to get that?  Get a sector count for the whole 
disk, set bs to 512 and skip to (sector count - 1)?


Thanks,

Charles


--
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| 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


___
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: netboot issues, 8.0, mfsroot mount failure

[Charles Sprickman]

On Tue, 16 Feb 2010, Garrett Cooper wrote:


On Tue, Feb 16, 2010 at 5:28 PM, Charles Sprickman sp...@bway.net wrote:

Howdy,

I'm having some problems getting 8.0 to install over the network.  I've got
my dhcp, tftp and nfs server working well, and I've tested all three
services from this host before attempting to boot over the network.

pxeboot seems to work, and I see it get loaded via tftp.  The kernel boots,
and parses the options in loader.conf that exist in my nfs-exported 8.0 DVD
fileset:

[r...@archive /home/spork/tmp]# cat
/usr/local/netboot/freebsd8/boot/loader.conf
mfsroot_load=YES
mfsroot_type=mfs_root
mfsroot_name=/boot/mfsroot
boot_multicons=YES
boot_serial=YES
console=comconsole,vidconsole
vfs.root.mountfrom=ufs:/dev/md0c

I see the kernel does find mfsroot and attaches it:

md0: Preloaded image /boot/mfsroot 4423680 bytes at 0xc0f6dfe0

But then when it's ready to mount the root filesystem, I get this:

SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/md0c
ROOT MOUNT ERROR:

If you have invalid mount options, reboot, and first try the following from
the loader prompt:

    set vfs.root.mountfrom.options=rw

and then remove invalid mount options from /etc/fstab.

It doesn't really state what the error is.  It's hinting that it's
read-only, but that seems odd.  Even if it couldn't mount r/w, shouldn't it
just drop to single-user at this point?

Next it tries nfs:

Trying to mount root from nfs:
NFS ROOT: 192.168.1.111:/usr/local/netboot/freebsd8
em0: link state changed to UP

And there it sits.  Remotely I can't do anything.  If I'm local, I can
ctrl-alt-del a few times and then about a minute later it does an orderly
restart.

I'm not aware of a good way to snoop on nfs traffic, but tcpdump shows nfs
traffic between the two hosts, which appears to be the client stat-ing a
file or directory.  tcpdump also shows some checksum errors, but I recall a
few threads here mentioning that on Intel cards that generally is not a
cause for concern.


From another host, I have no issues mounting that nfs filesystem r/w:


r...@h10[/home/spork]# mount_nfs 192.168.1.111:/usr/local/netboot/freebsd8
/mntr...@h10[/home/spork]# ls /mnt/
.cshrc          HARDWARE.TXT    boot.catalog    media           sbin
.profile        README.HTM      cdrom.inf       mnt             stand
8.0-RELEASE     README.TXT      dev             packages        sys
COPYRIGHT       RELNOTES.HTM    docbook.css     proc            tmp
ERRATA.HTM      RELNOTES.TXT    etc             rescue          usr
ERRATA.TXT      bin             lib             root            var
HARDWARE.HTM    boot            libexec         rr_moved
r...@h10[/home/spork]# touch /mnt/foo
r...@h10[/home/spork]# rm /mnt/foo
r...@h10[/home/spork]# umount /mnt

Any ideas?  I've got about a dozen remote boxes to upgrade, so I want to
totally nail down this procedure.  I've been putting off learning this for a
few years, and now I've got an actual need for it.


   I'll be in your shoes in a little bit... I ran into some issues
when I last tried with NFSv3 on a Solaris server so we'll see how
things go in the second go-around [with a FreeBSD nfs rootfs server],


In my case the server is FreeBSD (7.2).  It's running with default nfsd 
flags, so I suppose it's offering both tcp and udp.  No idea what version. 
It seems to work enough for the loader to fetch the loader files and 
kernel...



but 7.x netbooted and 8.x didn't when I tried last; the 7.x images
have some secret sauce fixes for PXE booting -- the ones I know of are
as follows (apply to loader.conf as you feel fit):

vfs.root.mountfrom=nfs
boot.nfsroot.path=/absolute/path/to/netboot/dir
boot.nfsroot.server=nfs-server-ip-addr


Is this documented somewhere?


   There were also some code changes made to `fix' netbooting with
pxeloader, but I'm not sure if they're applicable or needed in 8.x,
and I'm not sure what the actual changes are TBH...


Ugh.  With all these variables AND the general nuttiness of PC hardware I 
see many reboot cycles in my future.


Charles



Cheers,
-Garrett
___
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: ZFS on root, serial console install

[Charles Sprickman]

On Mon, 15 Feb 2010, Peter C. Lai wrote:


I did a pxeboot zfs-root install the other day.

If you copy the dvd to an nfs export as the root mount, hack the requisite
files to do serial console then you will drop to a login prompt when it
boots over pxe-tftp. Had no problems setting up zfs root install by
skipping sysinstall and fixit entirely: setup your ZFS root, then set
DESTDIR and use install.sh in the individual package dirs.


In short, did you do what I did somewhat accidentally?  I did a netboot, 
set loader.conf to mount mfsroot as my root fs.  For reasons I'm still 
unclear on, it did not grab mfsroot and proceeded to try and mount root 
over nfs (which happened to be exported RO).  It seems like if my nfs was 
exported rw, I would have been running with all the tools I needed and the 
drives would be available to me...


I'm going to try with rw nfs, currently the machine's locked up as it's 
confused about a ro root...


Thanks,

Charles



http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2


On Fri, Feb 12, 2010 at 7:27 AM, Charles Sprickman sp...@bway.net wrote:

Any hints on that one?

I finally got around to getting dhcp/tftp/nfs setup on an internal
network
to perform normal installs (and with some pxelinux hackery, the ability
to
boot a DOS disk or memtest86 disk images).

Sysinstall in general is kind of an unweildy beast over serial, but one
thing I was not able to accomplish was to get a shell (no extra virtual
consoles on serial) or attempt any mounting of fixit media.  From my
last
install that put ZFS on root, I had to do quite a bit of tapdancing
since I
had no DVD or bootable USB media - lots of switching from the install
disk
to fixit, which brought me to many chicken and egg moments.  I did it
though...

But remotely, I'm not seeing a good way to do this.  If mfsroot were
larger
and had more tools, then I'd be in business.  This is probably the
direction
I need to get shoved in.

I've looked at some other options with pxelinux and perhaps booting the
mini
ISO, but I'm not sure that gets me anywhere.

Any tips?  This isn't a make or break situation, I live 15 minutes from
the
colo...  It's more of a quest. :)



I would installl a small UFS FBSD system of 1 or 2 Gig on say ad0s1.
That gives you more then the equivalent of a fixit CD. You then use
this mini system as base to install the real one on the other
slice(s)

After having finished the install, you use fdisk to change the active
slice to the new install and reboot.
___
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




--
Peter C. Lai
ITS Systems Administrator
Bard College at Simon's Rock
84 Alford Rd.
Great Barrington, MA 01230
(413) 528-7428
peter at simons-rock.edu
___
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: hardware for home use large storage

[Charles Sprickman]

On Sun, 14 Feb 2010, Dan Langille wrote:


Dan Naumov wrote:

On Sun, 14 Feb 2010, Dan Langille wrote:

After creating three different system configurations (Athena,
Supermicro, and HP), my configuration of choice is this Supermicro
setup:

1. Samsung SATA CD/DVD Burner $20 (+ $8 shipping)
2. SuperMicro 5046A $750 (+$43 shipping)
3. LSI SAS 3081E-R $235
4. SATA cables $60
5. Crucial 3×2G ECC DDR3-1333 $191 (+ $6 shipping)
6. Xeon W3520 $310


You do realise how much of a massive overkill this is and how much you
are overspending?



I appreciate the comments and feedback.  I'd also appreciate alternative 
suggestions in addition to what you have contributed so far.  Spec out the 
box you would build.


$1200, and I'll run any benchmarks you'd like to see:

http://secure.newegg.com/WishList/PublicWishDetail.aspx?WishListNumber=8441629

This box is really only for backups, so no fancy CPU.  The sub-$100 
celeron seems to not impact ZFS performance a bit.  It does have ECC 
memory, and a fancy server mainboard.


C


___
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

ZFS on root, serial console install

[Charles Sprickman]

Any hints on that one?

I finally got around to getting dhcp/tftp/nfs setup on an internal network 
to perform normal installs (and with some pxelinux hackery, the ability to 
boot a DOS disk or memtest86 disk images).


Sysinstall in general is kind of an unweildy beast over serial, but one 
thing I was not able to accomplish was to get a shell (no extra virtual 
consoles on serial) or attempt any mounting of fixit media.  From my last 
install that put ZFS on root, I had to do quite a bit of tapdancing since 
I had no DVD or bootable USB media - lots of switching from the install 
disk to fixit, which brought me to many chicken and egg moments.  I did it 
though...


But remotely, I'm not seeing a good way to do this.  If mfsroot were 
larger and had more tools, then I'd be in business.  This is probably the 
direction I need to get shoved in.


I've looked at some other options with pxelinux and perhaps booting the 
mini ISO, but I'm not sure that gets me anywhere.


Any tips?  This isn't a make or break situation, I live 15 minutes from 
the colo...  It's more of a quest. :)


Thanks,

Charles
___
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: hardware for home use large storage

[Charles Sprickman]

On Tue, 9 Feb 2010, Dan Langille wrote:


Charles Sprickman wrote:

On Mon, 8 Feb 2010, Dan Langille wrote:

Also, it seems like
people who use zfs (or gmirror + gstripe) generally end up buying pricey 
hardware raid cards for compatibility reasons.  There seem to be no decent 
add-on SATA cards that play nice with FreeBSD other than that weird 
supermicro card that has to be physically hacked about to fit.


They use software RAID and hardware RAID at the same time?  I'm not sure what 
you mean by this.  Compatibility with FreeBSD?


From what I've seen on this list, people buy a nice Areca or 3Ware card 
and put it in JBOD mode and run ZFS on top of the drives.  The card is 
just being used to get lots of sata ports with a stable driver and known 
good hardware.  I've asked here a few times in the last few years for 
recommendations on a cheap SATA card and it seems like such a thing does 
not exist.  This might be a bit dated at this point, but you're playing it 
safe if you go with a 3ware/Areca/LSI card.


I don't recall all the details, but there were issues with siil, 
highpoint, etc.  IIRC it was not really FBSD's issue, but bugginess in 
those cards.  The intel ICH9 chipset works well, but there are no add-on 
PCIe cards that have an intel chip on them...


I'm sure someone will correct me if my info is now outdated or flat-out 
wrong. :)


Charles

___
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: hardware for home use large storage

[Charles Sprickman]

On Tue, 9 Feb 2010, Jeremy Chadwick wrote:


On Tue, Feb 09, 2010 at 06:53:26AM -0600, Karl Denninger wrote:

Jeremy Chadwick wrote:

On Tue, Feb 09, 2010 at 05:21:32PM +1100, Andrew Snow wrote:


http://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPA.cfm?typ=H

Supermicro just released a new Mini-ITX fanless Atom server board
with 6xSATA ports (based on Intel ICH9) and a PCIe 16x slot.  It
takes up to 4GB of RAM, and there's even a version with KVM-over-LAN
for headless operation and remote management.



Neat hardware.  But with regards to the KVM-over-LAN stuff: it's IPMI,
and Supermicro has a very, *very* long history of having shoddy IPMI
support.  I've been told the latter by too many different individuals in
the industry (some co-workers, some work at Yahoo, some at Rackable,
etc.) for me to rely on it.  If you *have* to go this route, make sure
you get the IPMI module which has its own dedicated LAN port on the
module and ***does not*** piggyback on top of an existing LAN port on
the mainboard.


What's wrong with the Supermicro IPMI implementations?  I have several -
all have a SEPARATE LAN port on the main board for the IPMI KVM
(separate and distinct from the board's primary LAN ports), and I've not
had any trouble with any of them.


http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2008-01/msg01206.html
http://forums.freebsd.org/showthread.php?t=7750
http://www.beowulf.org/archive/2007-November/019925.html
http://bivald.com/lessons-learned/2009/06/supermicro_ipmi_problems_web_i.html
http://lists.freebsd.org/pipermail/freebsd-stable/2008-August/044248.html
http://lists.freebsd.org/pipermail/freebsd-stable/2008-August/044237.html

(Last thread piece does mention that the user was able to get keyboard
working by disabling umass(4) of all things)


I have a box down at Softlayer (one of the few major server rental outfits 
that officially supports FreeBSD), and one of the reasons I went with them 
is that they advertised IP-KVM support.  Turns out they run Supermicro 
boxes with the IPMI card.  It mostly works, but it is very quirky and you 
have to use a very wonky Java client app to get the remote console.  You 
have to build a kernel that omits certain USB devices to make the keyboard 
work over the KVM connection (and their stock FBSD install has it 
disabled).


I can usually get in, but sometimes I have to open a ticket with them and 
a tech does some kind of reset on the card.  I don't know if they a 
hitting a button on the card/chassis or if they have some way to do this 
remotely.  After they do that, I'll see something like this in dmesg:


umass0: Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2 on 
uhub4
ums0: Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2 on 
uhub4

ums0: 3 buttons and Z dir.
ukbd0: Peppercon AG Multidevice, class 0/0, rev 2.00/0.01, addr 2 on 
uhub4

kbd2 at ukbd0

The umass device is to support the virtual media feature that simply 
does not work.  It's supposed to allow you to point the ipmi card at an 
iso or disk image on an SMB server and boot your server off of it.  I had 
no luck with this.


All the IPMI power on/off, reset, and hw monitoring functions do work well 
though.



It gets worse when you use one of the IPMI modules that piggybacks on an
existing Ethernet port -- the NIC driver for the OS, from the ground up,
has to be fully aware of ASF and any quirks/oddities involved.  For
example, on bge(4) and bce(4), you'll find this (bge mentioned below):

 hw.bge.allow_asf
   Allow the ASF feature for cooperating with IPMI.  Can cause sys-
   tem lockup problems on a small number of systems.  Disabled by
   default.

So unless the administrator intentionally sets the loader tunable prior
to booting the OS installation, they'll find all kinds of MAC problems
as a result of the IPMI piggybacking.  Why isn't this enabled by
default?  I believe because there were reports of failures/problems on
people's systems who *did not* have IPMI cards.  Lose-lose situation.


I don't think they have this setup, or if they do, they are using it on 
the internal LAN, so I don't notice any weirdness.



If you really want me to dig up people at Yahoo who have dealt with IPMI
on thousands of Supermicro servers and the insanity involved (due to
bugs, quirks, or implementation differences between the IPMI firmwares
and which revision/model of module used), I can do so.  Most of the
complaints I've heard of stem from serial-over-IPMI.  I don't think
it'd be a very positive/supportive thread, however.  :-)

One similar product that does seem to work well is iLO, available on
HP/Compaq hardware.


I've heard great things about that.  It seems like a much better design - 
it's essentially a small server that is independent from the main host. 
Has it's own LAN and serial ports as well.


Charles


--
| Jeremy Chadwick   j...@parodius.com |
| Parodius Networking   

Re: hardware for home use large storage

[Charles Sprickman]

On Mon, 8 Feb 2010, Dan Langille wrote:


Hi,

I'm looking at creating a large home use storage machine.  Budget is a 
concern, but size and reliability are also a priority.  Noise is also a 
concern, since this will be at home, in the basement.  That, and cost, pretty 
much rules out a commercial case, such as a 3U case.  It would be nice, but 
it greatly inflates the budget.  This pretty much restricts me to a tower 
case.


I recently had to put together something very cheap for a client for 
disk-only backups (rsync + zfs snapshots).  As you noticed, rack 
enclosures that will hold a bunch of drives are insanely expensive.  I put 
my wishlist from NewEgg below.  While the $33 case is a bit flimsy, the 
extra high-cfm fan in the back and the fan that sits in front of the drive 
bays keeps the drives extremely cool.  For $33, I lucked out.


The primary use of this machine will be a backup server[1].  It will do other 
secondary use will include minor tasks such as samba, CIFS, cvsup, etc.


I'm thinking of 8x1TB (or larger) SATA drives.  I've found a case[2] with 
hot-swap bays[3], that seems interesting.  I haven't looked at power 
supplies, but given that number of drives, I expect something beefy with a 
decent reputation is called for.


For home use is the hot-swap option really needed?  Also, it seems like 
people who use zfs (or gmirror + gstripe) generally end up buying pricey 
hardware raid cards for compatibility reasons.  There seem to be no decent 
add-on SATA cards that play nice with FreeBSD other than that weird 
supermicro card that has to be physically hacked about to fit.


I did splurge for a server-class board from Supermicro since I wanted 
bios serial port console redirection, and as many SATA ports on-board that 
I could find.



Whether I use hardware or software RAID is undecided.  I

I think I am leaning towards software RAID, probably ZFS under FreeBSD 8.x 
but I'm open to hardware RAID but I think the cost won't justify it given 
ZFS.


I've had two very different ZFS experiences so far.  On the hardware I 
mention in this message, I had zero problems and excellent performance 
(bonnie++ showing 145MB/s reads, 132MB/s writes on a 4 disk RAIDZ1 array) 
with 8.0/amd64 w/4GB of RAM.  I did no tuning at all - amd64 is the way 
to go for ZFS.


On an old machine at home with 2 old (2003 era) 32-bit xeons, I ran into 
all the issues people see with i386+ZFS - kernel memory exhaustion 
resulting in a panic, screwing around with an old 3Ware RAID card (JBOD 
mode) that cannot properly scan for new drives, just a total mess without 
lots of futzing about.


Given that, what motherboard and RAM configuration would you recommend to 
work with FreeBSD [and probably ZFS].  The lists seems to indicate that more 
RAM is better with ZFS.


Here's the list:

http://secure.newegg.com/WishList/PublicWishDetail.aspx?WishListNumber=8441629

Just over $1K, and I've got 4 nice drives, ECC memory, and a server board. 
Going with the celeron saved a ton of cash with no impact on ZFS that I 
can discern, and again, going with a cheap tower case slashed the cost as 
well.  That whole combo works great.  Now when I use up those 6 SATA 
ports, I don't know how to get more cheaply, but I'll worry about that 
later...


Charles


Thanks.


[1] - FYI running Bacula, but that's out of scope for this question

[2] - http://www.newegg.com/Product/Product.aspx?Item=N82E16811192058

[3] - nice to have, especially for a failure.
___
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

32-bit jails on a 64-bit system?

[Charles Sprickman]

Howdy,

I saw this little tidbit in the 8.0 Release Notes...


The jail(8) subsystem has been updated. Changes include:

Compatibility support which permits 32-bit jail binaries to be used on 
64-bit systems to manage jails has been added.



I know prior to 8.0 with some fancy footwork you could do some interesting 
things (for example, I have a jail running a bunch of 32-bit 4.11 stuff on 
a 7.2 amd64 box), but it was not easy.


Looking at the jail manpage and handbook entries, I'm not seeing anything 
that further explains the changes.  I've been able to get some things 
working in a test setup, but not everything.  Any pointers to what exactly 
that blurb in the release notes actually means?  Google is getting me 
nowhere.


My current scenario is this...  I have a backups server with a ton of 
space.  Nightly backups run to this and get zfs-snapshotted each night.  I 
also have created jails for a number of important hosts so that should I 
lose a host, I can bring up a jail on this box to replace it while I 
repair things.  One host is a 7.2/i386 box.  The backups host is 
8.0/amd64.  Ideally I'd like to copy everything, including the base OS 
into this jail, except for perhaps ps, top and other utilities that 
might have issues.


Any pointers appreciated...

Thanks,

Charles
___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
sp...@bway.net - 212.655.9344

___
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: immense delayed write to file system (ZFS and UFS2), performance issues

[Charles Sprickman]

On Tue, 19 Jan 2010, Gerrit Kühn wrote:


On Tue, 19 Jan 2010 03:24:49 -0800 Jeremy Chadwick
free...@jdc.parodius.com wrote about Re: immense delayed write to file
system (ZFS and UFS2), performance issues:

JC  JC If you want a consumer-edition drive that's better tuned for
JC  JC server work, you should really be looking at the WD Caviar Black
JC  JC series or their RE/RE2 series.

JC  That's exactly what I did. I have WD-RE2 drives here that show
JC  exactly this problem (RE2/GP)! The model number is WD1000FYPS-01ZKB0.

JC I should have been more specific.  WD makes RE-series drives which
JC don't have GP applied to them; those are what I was referring to.

Well, when I bought these drives I was not aware of this issue. Buying a
drive intended for 24/7 use in RAID configurations is basically the right
idea, I think. From what was written about the GP feature back then I
could not anticipate such problems.
I would have liked to buy the 2TB drives without GP lately, but they have
lead times into April here. So I went for the GP model, which now shows
the same problem as the 1TB drive... :-(

JC WD1000FYPS - WD RE2-GP,   1TB, 16MB, variable rpm
JC WD2002FYPS - WD RE4-GP,   2TB, 64MB, variable rpm

JC So which drive models above are experiencing a continual increase in
JC SMART attribute 193 (Load Cycle Count)?  My guess is that some of the
JC WD Caviar Green models, and possibly all of the RE2-GP and RE4-GP
JC models are experiencing this problem.

I can confirm that the two models above show this problem.
Furthermore I can confirm that at least in my setup here this drive
type works fine:

WD5001ABYS

I have some of the RE3 drives sitting around here and will probably try
them later.


I specifically bought RE3 drives recently because of the whole fiasco 
regarding raid compatibility.  I paid about $20 each more for these in 
the interest of things just working, since I saw some debate about 
whether or not the TLER setting can be flipped on the non-RAID drives.


FWIW, 4 1TB RE3's in a zfs raidz (an excerpt from bonnie++, block 
read/write 8G on 4G RAM):


Write   Read
K/sec   K/sec
123207  142749

Both zfs and these drives kind of surprised me, that seems pretty good for 
software raid with parity...


Seagate is currently on my blacklist after we had a large number of them 
fail a year or two in the past year or two.  I've had good luck so far 
with WD RE2 and RE3 drives.  I'll probably give seagate another shot in a 
year or two.


C


Can anyone here report anything about the fixed firmware from
http://support.wdc.com/product/download.asp?groupid=609sid=113lang=en?
Does this remedy the problem for the 1TB RE2 drive?

JC I say some with regards to WD Caviar Green since I have some which do
JC not appear to exhibit the heads/actuator arm moved into the
JC landing/park zone.  I'm at work right now, but when I get home I can
JC verify what models I've used which didn't experience this problem, as
JC well as what the manufacturing date and F/W revisions are.  I should
JC note I don't have said Green drives in use (I use WD1001FALS drives
JC now).

Thanks for sharing this information.


cu
 Gerrit
___
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: Multiple serial consoles via null modem cable

[Charles Sprickman]

On Jan 12, 2010, at 12:04 PM, Boris Samorodov b...@ipt.ru wrote:


On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote:

I'm thinking about the following situation - 1 system acting like a  
host
with a serial port hub, each port of the hub is connected to a  
different

machine on sio0, using null modem cables.


Along with milti-io serial cards we use multi-usb serial
converters, such as SUNIX UTS7009P (7 USB to serial adapter):
http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm



I need to look it up when I'm in front of a real computer, but there  
are a number of reasonably priced multport USB to serial converters  
out there.  We have a 16 port model that's rack mounted and cost  
around $400.  It works better many of the more expensive multiport  
serial cards. Paired with conserver, it's a really nice solution.   
Conserver's logging is great...


I've used old dedicated terminal servers in the past and they can be a  
pain to deal with.  The newer ones are probably nicer, but are also  
lots of money.


C


--
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: Multiple serial consoles via null modem cable

[Charles Sprickman]

On Tue, 12 Jan 2010, Charles Sprickman wrote:



On Jan 12, 2010, at 12:04 PM, Boris Samorodov b...@ipt.ru wrote:


On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote:


I'm thinking about the following situation - 1 system acting like a host
with a serial port hub, each port of the hub is connected to a different
machine on sio0, using null modem cables.


Along with milti-io serial cards we use multi-usb serial
converters, such as SUNIX UTS7009P (7 USB to serial adapter):
http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm



I need to look it up when I'm in front of a real computer, but there are a 
number of reasonably priced multport USB to serial converters out there.


Here we go:

http://www.usbgear.com/USB-Serial.html

Some very cool stuff there.  They also list the chipset used in some of 
those so you have some idea if it will work with FreeBSD.  I think Vixie 
originally pointed me to this model:


http://www.usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RMcats=199catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601

If anyone has the lowdown on which chipsets generally work with FreeBSD 
(especially with all the changes in 8.0), that would be great.


The above model works great on an old 4.11 box.  It's an FTDI chipset - at 
the very bottom of the page they even claim FreeBSD and OpenBSD support.


dmesg:

uhub2: Genesys Logic USB Hub, class 9/0, rev 1.01/0.11, addr 2
uhub2: 7 ports with 7 removable, self powered
ucom0: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 3
[...]
ucom11: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 8
[...]
uhub3: Genesys Logic USB Hub, class 9/0, rev 1.01/0.12, addr 9
uhub3: 4 ports with 4 removable, self powered
ucom12: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 10
[...]
ucom15: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 11

Charles

 We have a 16 port model that's rack mounted and cost around $400.  It 
works better many of the more expensive multiport serial cards. Paired 
with conserver, it's a really nice solution.  Conserver's logging is 
great...


I've used old dedicated terminal servers in the past and they can be a pain 
to deal with.  The newer ones are probably nicer, but are also lots of money.


C


--
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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

___
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: Multiple serial consoles via null modem cable

[Charles Sprickman]

On Tue, 12 Jan 2010, Jeremy Chadwick wrote:


On Tue, Jan 12, 2010 at 02:50:29PM -0500, Charles Sprickman wrote:

On Tue, 12 Jan 2010, Charles Sprickman wrote:


On Jan 12, 2010, at 12:04 PM, Boris Samorodov b...@ipt.ru wrote:


On Tue, 12 Jan 2010 17:14:44 +0200 Marin Atanasov wrote:


I'm thinking about the following situation - 1 system acting like a host
with a serial port hub, each port of the hub is connected to a different
machine on sio0, using null modem cables.


Along with milti-io serial cards we use multi-usb serial
converters, such as SUNIX UTS7009P (7 USB to serial adapter):
http://www.sunix.com.tw/it/en/LinkCraft/UTS4009P_UTS7009P.htm



I need to look it up when I'm in front of a real computer, but
there are a number of reasonably priced multport USB to serial
converters out there.


Here we go:

http://www.usbgear.com/USB-Serial.html

Some very cool stuff there.  They also list the chipset used in some
of those so you have some idea if it will work with FreeBSD.  I
think Vixie originally pointed me to this model:

http://www.usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RMcats=199catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601

If anyone has the lowdown on which chipsets generally work with
FreeBSD (especially with all the changes in 8.0), that would be
great.


The same device appears here:

http://www.serialgear.com/USB-16COM-RM.html
http://www.allserial.com/usb_16com-rm.html


Damn, $130 more than usbgear.com...


Quite inexpensive compared to an actual serial console server!


Very much so!  And if you already have a sort of utility box in a rack, 
this makes a nice add-on.  There are some very cheap 4 and 8 port models 
as well.


I had no idea such a device existed (well, USB-to-serial adapters, sure, 
just not ones which housed 16 adapters or was rack-mountable.  :-) ).


Who knows what's inside, there are two USB hubs in there...  But yeah, 
rack-mount and AC power are nice.


Decently sized FIFO buffers as well (128/384 byte Tx/Rx), at least 
compared to a classic 16650A (14/16 byte Tx/Rx).  Usually larger FIFO == 
can handle higher bps without character loss.


I've 5 questions about this device:

* Does it work with/use hardware flow control (CTS/RTS)?


Yes.  There were a few machines that were giving me issues with the old 
3-wire RocketPort card we had (which only had 8 ports, cost more *used* 
than this USB thing cost new, had buggy drivers, and only had a 3-wire 
interface) and they worked fine when moved to this device.



* Have you tested it for character loss at 115200bps rates?


Nope, never had much luck getting everything (BIOS, loader, getty) all 
talking at the same speed, so I just leave it at 9600.  Zero issues 
though...



* How do you configure each port (speed, flow, etc.)?


I let conserver deal with that - I set the baud, parity and options in 
the default stanza for all ports.  It apparently does the right thing 
when opening the port.  Again, zero issues.



* Does it work under FreeBSD 8.x (given that the entire USB stack
 was re-written)?


No idea, don't even have an 8.x machine at that site.  If you have any 
contacts over at ISC, you might ask there, I got the impression from Vixie 
that this device became part of their standard co-lo build.



* Do you have any idea what the power usage is on this device (in amps)?
 (Our MRV claims 1A max, but drives about 0.25A or so).


No clue, but I imagine it's negligible.  The device generates almost no 
heat, and all of that is in the area around the power supply.



The above model works great on an old 4.11 box.  It's an FTDI
chipset - at the very bottom of the page they even claim FreeBSD and
OpenBSD support.

dmesg:

uhub2: Genesys Logic USB Hub, class 9/0, rev 1.01/0.11, addr 2
uhub2: 7 ports with 7 removable, self powered
ucom0: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 3
[...]
ucom11: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 8
[...]
uhub3: Genesys Logic USB Hub, class 9/0, rev 1.01/0.12, addr 9
uhub3: 4 ports with 4 removable, self powered
ucom12: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 10
[...]
ucom15: FTDI USB FAST SERIAL ADAPTER, rev 2.00/5.00, addr 11


Very nice -- the fact they're using FTDI chips is good (from what I
understand of USB-to-serial adapters).


Yep, this was all plug-and-play.  I also found a source for db9-db9 null 
modem cables at about $3 a pop - much simpler than building rj-xx to db9 
adapters (xyplex, rocketport) or dealing with giant harnesses (cisco, 
xylogics).



We have a 16 port model that's rack mounted and cost around $400.
It works better many of the more expensive multiport serial cards.
Paired with conserver, it's a really nice solution.  Conserver's
logging is great...

I've used old dedicated terminal servers in the past and they can
be a pain to deal with.  The newer ones are probably nicer, but
are also lots of money.


Classic devices (like the Portmaster) are indeed a pain in the butt to
deal with.  I've no experience

7.2 serial console/getty problem

[Charles Sprickman]

Howdy,

I'm having some issues getting a working serial console on a 7.2-amd64 
system (Dell PE 2970).  Everything is running at 9600bps to keep things 
simple (BIOS, loader, getty).  Normal DB-9 null cable to another host. 
/etc/ttys has getty on ttyd0 with the std.9600 gettytab entry and vt100 
terminal type.


The following works fine:

-Console redirection via Dell's BIOS (I can enter setup, navigate BIOS, 
enter RAID config, etc.)

-Boot loader (can enter boot params, select boot options, etc.)
-Boot messages (displays fine)

However once the machine boots and getty has control, things get a bit 
odd.


I've tested this with various hosts using minicom and conserver 
(conserver.com).  No problems with my other hosts running older versions 
of FreeBSD with the same settings (9600, 8N1, hw flow control).


If I just hit enter, I get a response like this:

n~:oommv64(jkoomimnnwwou})(|t}}t9-

It does not vary - always the same string.

However, if I hit CTRL-D, then I get a normal prompt:

FreeBSD/amd64 (bigmail.bway.net) (ttyd0)

login:

If at the login: prompt I just hit enter again without typing a 
username, I get the same garbled output.


CTRL-D again gives me a proper prompt.

Once I'm logged-in, there seem to be no issues.  vi, top and other 
things that rely on the terminal being sane work fine.


Any ideas?

Thanks,

Charles

___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
sp...@bway.net - 212.655.9344

___
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: panic in 7.2 (ffs_alloc.c?)

[Charles Sprickman]

Just a follow-up...  The machine was waiting for a manual fsck - this 
crash seemed to scramble things up pretty good, it hit the jail partition 
hard and seemed to touch others that were quiet at the time.


I'm re-running mstone with an even heavier load to see if I can 
reproduce this again.


Full verbose dmesg:  http://pastie.org/711839

Should I bother with a PR or anything on this?  Doesn't look like a 
hardware issue to me.  It seems like there could be a nasty bug waiting in 
the UFS2 code somewhere, does anyone want to persue this at all?  I have 
the dump available for anyone that wants it.


Thanks,

Charles

On Sun, 22 Nov 2009, Charles Sprickman wrote:


Howdy,

I'm not expert at getting info out of a dump, but I'll do my best to provide 
some information.


This is a Dell PE2970 w/PERC6/i RAID running FreeBSD 7.2/amd64.  Brand new 
box, has been doing very light work for about two weeks.  Last night I 
started a very long mstone run on a jailed mail server and found that quite a 
way into this burn-in, the box paniced.  I was going to put it in service 
Monday (after punishing it all weekend).  Looking for some input on what the 
root cause is and whether going to a -stable snapshot might be worthwhile.


I can tell you there was a good deal of disk activity at the time in the jail 
- mstone was simulating 100 POP and SMTP clients hitting the machine at once. 
This is qmail+courier.  So messages are coming in, hitting the queue, hitting 
a user's maildir, getting read and deleted via the POP client over and over 
again.  I do see lots of ffs_* stuff in the backtrace, which is a little 
scary.


Here's my stab at a kgdb session (also @ pastie for easier reading: 
http://pastie.org/709671):


[r...@bigmail /usr/obj/usr/src/sys/BWAY7-64]# kgdb kernel.debug 
/var/crash/vmcore.0

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd...

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x12d4b9f5c
fault code  = supervisor read data, page not present
instruction pointer = 0x8:0x8050382e
stack pointer   = 0x10:0x281a75b0
frame pointer   = 0x10:0xff000455f800
code segment= base 0x0, limit 0xf, type 0x1b
   = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 6324 (vdelivermail)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 12d0h32m3s
Physical memory: 6130 MB
Dumping 725 MB: 710 694 678 662 646 630 614 598 582 566 550 534 518 502 486 
470 454 438 422 406 390 374 358 342 326 310 294 278 262 246 230 214 198 182 
166 150 134 118 102 86 70 54 38 22 6


Reading symbols from /boot/kernel/nullfs.ko...Reading symbols from 
/boot/kernel/nullfs.ko.symbols...done.

done.
Loaded symbols for /boot/kernel/nullfs.ko
Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from 
/boot/kernel/fdescfs.ko.symbols...done.

done.
Loaded symbols for /boot/kernel/fdescfs.ko
#0  doadump () at pcpu.h:195
195 __asm __volatile(movq %%gs:0,%0 : =r (td));
#3  0x8034cba2 in panic (fmt=0x104 Address 0x104 out of bounds)
   at /usr/src/sys/kern/kern_shutdown.c:574
#4  0x80574823 in trap_fatal (frame=0xff00046c8000, eva=Variable 
eva is not available.

)
   at /usr/src/sys/amd64/amd64/trap.c:757
#5  0x80574bf5 in trap_pfault (frame=0x281a7500, usermode=0)
   at /usr/src/sys/amd64/amd64/trap.c:673
#6  0x80575534 in trap (frame=0x281a7500)
   at /usr/src/sys/amd64/amd64/trap.c:444
#7  0x8055969e in calltrap ()
   at /usr/src/sys/amd64/amd64/exception.S:209
#8  0x8050382e in ffs_realloccg (ip=0xff00267f75c0, lbprev=0,
   bprev=6288224785898156086, bpref=593305256, osize=0, nsize=2048,
   flags=33619968, cred=0xff00927fe800, bpp=0x281a7800)
   at /usr/src/sys/ufs/ffs/ffs_alloc.c:1349
#9  0x80506e8e in ffs_balloc_ufs2 (vp=0xff0027a64dc8, 
startoffset=Variable startoffset is not available.

)
   at /usr/src/sys/ufs/ffs/ffs_balloc.c:692
#10 0x805223e5 in ffs_write (ap=0x281a7a10)
   at /usr/src/sys/ufs/ffs/ffs_vnops.c:724
#11 0x805a0645 in VOP_WRITE_APV (vop=0x80793d20,
   a=0x281a7a10) at vnode_if.c:691
#12 0x803dd731 in vn_write (fp=0xff001027cd00,
   uio=0x281a7b00, active_cred=Variable active_cred is not 
available.

) at vnode_if.h:373
#13 0x80388768 in dofilewrite (td=0xff00046c8000, fd=5,
   fp=0xff001027cd00, auio=dwarf2_read_address: Corrupted

panic in 7.2 (ffs_alloc.c?)

[Charles Sprickman]

Howdy,

I'm not expert at getting info out of a dump, but I'll do my best to 
provide some information.


This is a Dell PE2970 w/PERC6/i RAID running FreeBSD 7.2/amd64.  Brand new 
box, has been doing very light work for about two weeks.  Last night I 
started a very long mstone run on a jailed mail server and found that 
quite a way into this burn-in, the box paniced.  I was going to put it in 
service Monday (after punishing it all weekend).  Looking for some input 
on what the root cause is and whether going to a -stable snapshot might be 
worthwhile.


I can tell you there was a good deal of disk activity at the time in the 
jail - mstone was simulating 100 POP and SMTP clients hitting the machine 
at once.  This is qmail+courier.  So messages are coming in, hitting the 
queue, hitting a user's maildir, getting read and deleted via the POP 
client over and over again.  I do see lots of ffs_* stuff in the 
backtrace, which is a little scary.


Here's my stab at a kgdb session (also @ pastie for easier reading: 
http://pastie.org/709671):


[r...@bigmail /usr/obj/usr/src/sys/BWAY7-64]# kgdb kernel.debug 
/var/crash/vmcore.0

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you 
are
welcome to change it and/or distribute copies of it under certain 
conditions.

Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for 
details.

This GDB was configured as amd64-marcel-freebsd...

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x12d4b9f5c
fault code  = supervisor read data, page not present
instruction pointer = 0x8:0x8050382e
stack pointer   = 0x10:0x281a75b0
frame pointer   = 0x10:0xff000455f800
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 6324 (vdelivermail)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 12d0h32m3s
Physical memory: 6130 MB
Dumping 725 MB: 710 694 678 662 646 630 614 598 582 566 550 534 518 502 
486 470 454 438 422 406 390 374 358 342 326 310 294 278 262 246 230 214 
198 182 166 150 134 118 102 86 70 54 38 22 6


Reading symbols from /boot/kernel/nullfs.ko...Reading symbols from 
/boot/kernel/nullfs.ko.symbols...done.

done.
Loaded symbols for /boot/kernel/nullfs.ko
Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from 
/boot/kernel/fdescfs.ko.symbols...done.

done.
Loaded symbols for /boot/kernel/fdescfs.ko
#0  doadump () at pcpu.h:195
195 __asm __volatile(movq %%gs:0,%0 : =r (td));
#3  0x8034cba2 in panic (fmt=0x104 Address 0x104 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:574
#4  0x80574823 in trap_fatal (frame=0xff00046c8000, 
eva=Variable eva is not available.

)
at /usr/src/sys/amd64/amd64/trap.c:757
#5  0x80574bf5 in trap_pfault (frame=0x281a7500, 
usermode=0)

at /usr/src/sys/amd64/amd64/trap.c:673
#6  0x80575534 in trap (frame=0x281a7500)
at /usr/src/sys/amd64/amd64/trap.c:444
#7  0x8055969e in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:209
#8  0x8050382e in ffs_realloccg (ip=0xff00267f75c0, lbprev=0,
bprev=6288224785898156086, bpref=593305256, osize=0, nsize=2048,
flags=33619968, cred=0xff00927fe800, bpp=0x281a7800)
at /usr/src/sys/ufs/ffs/ffs_alloc.c:1349
#9  0x80506e8e in ffs_balloc_ufs2 (vp=0xff0027a64dc8, 
startoffset=Variable startoffset is not available.

)
at /usr/src/sys/ufs/ffs/ffs_balloc.c:692
#10 0x805223e5 in ffs_write (ap=0x281a7a10)
at /usr/src/sys/ufs/ffs/ffs_vnops.c:724
#11 0x805a0645 in VOP_WRITE_APV (vop=0x80793d20,
a=0x281a7a10) at vnode_if.c:691
#12 0x803dd731 in vn_write (fp=0xff001027cd00,
uio=0x281a7b00, active_cred=Variable active_cred is not 
available.

) at vnode_if.h:373
#13 0x80388768 in dofilewrite (td=0xff00046c8000, fd=5,
fp=0xff001027cd00, auio=dwarf2_read_address: Corrupted DWARF 
expression.

) at file.h:257
#14 0x80388a6e in kern_writev (td=0xff00046c8000, fd=5,
auio=0x281a7b00) at /usr/src/sys/kern/sys_generic.c:402
#15 0x80388aec in write (td=0x800, uap=0x12d4b9f50)
at /usr/src/sys/kern/sys_generic.c:318
#16 0x80596a66 in ia32_syscall (frame=0x281a7c80)
at /usr/src/sys/amd64/ia32/ia32_syscall.c:182
#17 0x80559ad0 in Xint0x80_syscall () at ia32_exception.S:65
#18 0x28167928 in ?? ()
Previous frame inner to this frame (corrupt stack?)

Full dmesg, verbose boot and kernel config at pastie as well.  Actually no 
verbose boot...  I rebooted the 

setting quotas from inside a jail

[Charles Sprickman]

Hello all,

The subject describes my goal.  I'm aware of the usual caveats - if 
there's more than one jail, no UID overlap, this will really only work in 
one jail if all jails are on the same filesystem, etc.


I found a very, very old post that has an... interesting... technique:

http://groups.google.com/group/mpc.lists.freebsd.hackers/msg/2b92fc66ac72efa6?hl=en

It actually works.  It being I suppose the fstab trickery in the jail. 
I need to test this some more, but it does seem possible to edit quotas 
inside the jail, which is my basic goal.  I don't want my provisioning box 
to have to hit the host just to alter quotas in one jail that needs them.


Just looking for any warnings/caveats about the above and what might be 
different 6+ years later...


Thanks,

Charles

___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
sp...@bway.net - 212.655.9344

___
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: LSI Logic raid status

[Charles Sprickman]

On Mar 24, 2009, at 9:20 AM, Peter Ankerstål wrote:



On Mar 24, 2009, at 2:08 PM, Ruben van Staveren wrote:



On 24 Mar 2009, at 13:40, Peter Ankerstål wrote:


Hi,

I have a LSI Logic sata/sas raid running, is there a way to see  
the state of

the volume, like optimal, degraded or resyncing?


There is sysutils/linux-megacli


Sorry about that. This is not megaraid its the mpt driver.
LSI SAS3041E-R PCI-e

mpt0: LSILogic SAS/SATA Adapter port 0x2000-0x20ff mem  
0xd021-0xd0213fff,0xd020-0xd020 irq 16 at device 0.0 on  
pci3

mpt0: [ITHREAD]
mpt0: MPI Version=1.5.19.0
mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 )
mpt0: 1 Active Volume (2 Max)
mpt0: 2 Hidden Drive Members (14 Max)


While I haven't found a way to actually configure the thing in  
FreeBSD, the mpt

driver does make some information available via sysctl:

[sp...@uniweb ~]$ sysctl -a|grep dev.mpt
dev.mpt.0.%desc: LSILogic SAS/SATA Adapter
dev.mpt.0.%driver: mpt
dev.mpt.0.%location: slot=8 function=0
dev.mpt.0.%pnpinfo: vendor=0x1000 device=0x0054 subvendor=0x1028  
subdevice=0x1f09 class=0x01

dev.mpt.0.%parent: pci2
dev.mpt.0.debug: 3
dev.mpt.0.role: 1
dev.mpt.0.vol_member_wce: NC
dev.mpt.0.vol_queue_depth: 128
dev.mpt.0.vol_resync_rate: 0
dev.mpt.0.nonoptimal_volumes: 0

Don't test whether the nonoptimal_volumes parameter works, it does -
but if you pull a drive, FreeBSD likes to panic both on the loss of a  
disk

and then again when the drive is reconnected and the rebuild completes.
This is apparently some problem in the CAM layer, not the mpt driver,  
but

it's something to be aware of.  Scott Long has noted that this is being
worked on in 8.x.

Charles





--
Peter Ankerstål
pe...@pean.org
http://www.pean.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 



Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet www.bway.net
sp...@bway.net - 212.655.9344



___
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: LSI Logic raid status

[Charles Sprickman]

On Tue, 24 Mar 2009, Marat N.Afanasyev wrote:


Peter Ankerst?l wrote:


On Mar 24, 2009, at 8:20 PM, Scott Long wrote:


Peter Ankerst?l wrote:

On Mar 24, 2009, at 8:00 PM, Charles Sprickman wrote:



dev.mpt.0.nonoptimal_volumes: 0

Don't test whether the nonoptimal_volumes parameter works, it does -
but if you pull a drive, FreeBSD likes to panic both on the loss of a 
disk

and then again when the drive is reconnected and the rebuild completes.
This is apparently some problem in the CAM layer, not the mpt driver, 
but

it's something to be aware of.  Scott Long has noted that this is being
worked on in 8.x.
Yes, I tried to remove a drive today. Of course I need to see if it works 
properly
before using it for real. It did, but just as you say it paniced when I 
pulled the
drive and when is was resynced. But it sound great if someone is working 
on

this problem!


The instability during a rebuild should be fixed in 7.2 (and 7-stable as
of about the last month).  If you can, please update your sources and
let me know if it helps.

As for actually monitoring and configuring arrays, that work is in
progress.

Scott


Im running RELENG_7 cvsuped and built like 15 hours ago. I still have this 
problem.
Please come back to me if you want some additional information about the 
setup.


--
Peter Ankerst?l
pe...@pean.org
http://www.pean.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

I'd rather prefer using a gmirror/gstripe instead of mpt semihardware raid 
then ;)


The LSI card is not semi-hardware RAID, it's an actual RAID controller. 
It's also in a ton of Dell products as well.  It's a decent enough 
controller and not terribly pricey.


Charles


--
SY, Marat
___
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: setting quotas from inside a jail

[Charles Sprickman]

On Tue, 24 Mar 2009, Michael R. Wayne wrote:


On Tue, Mar 24, 2009 at 03:05:05AM -0400, Charles Sprickman wrote:


The subject describes my goal.  I'm aware of the usual caveats - if
there's more than one jail, no UID overlap, this will really only work in
one jail if all jails are on the same filesystem, etc.

I found a very, very old post that has an... interesting... technique:

http://groups.google.com/group/mpc.lists.freebsd.hackers/msg/2b92fc66ac72efa6?hl=en

It actually works.  It being I suppose the fstab trickery in the jail.
I need to test this some more, but it does seem possible to edit quotas
inside the jail, which is my basic goal.  I don't want my provisioning box
to have to hit the host just to alter quotas in one jail that needs them.

Just looking for any warnings/caveats about the above and what might be
different 6+ years later...


That's my post.  Yes, we still do this.  It still works.  Over time,
sometimes things get out of sync.  If that happens, go to S, shut
off quotas, do a quotacheck, turn them back on.


I seemed to knock it out of whack on my first reboot after getting it 
working.  Does checking quotas on boot break it?


Thanks,

C


/\/\ \/\/
___
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: Various route locking fixes merged to stable/7 (was: Re: Big problems with 7.1 locking up :-()

[Charles Sprickman]

On Wed, 25 Feb 2009, Robert Watson wrote:

Just a minor heads up: I've merged both Kip Macy's lock order fixes to the 
kernel routing code, and the route locking and reference counting fixes from 
kern/130652 to stable/7.  These fixes should correct a number of reported 
network-related hangs.  We might want to release a subset of these as an 
errata patch to 7.1 if they shake out well in 7-stable.


+1

Charles



Robert N M Watson
Computer Laboratory
University of Cambridge

On Wed, 25 Feb 2009, Robert Watson wrote:


On Wed, 25 Feb 2009, Pete French wrote:

FYI, I'm currently awaiting testing results from Pete on the MFC of a 
number of routing table locking fixes, and once that's merged (hopefully 
tomorrow?) I'll start on the patches in the above PR.  I've taken a 
crash-course in routing table locking in the last few days... :-)


Just to let you know that I have had zero crashes since I out the patch 
live on sunday. Of course thats only three days, but it does look very 
much like it has fixed it. I am also running with the other routing table 
patch too..


At this point no news is good news, as it is just sitting there ticking 
away nicely to itself. I will roll it out to a few more machines over the 
next few days.


But looking good so far, I would encourage other people to try the ptches 
if they are having problems...


Thanks -- I've gone ahead and merged the patch to 7.x (r189026) so that I 
can look at the PR and get that in-progress.  Since the code affected by 
the PR is no longer in 8.x, I'll merge directly to 7.x, and probably fairly 
quickly since you've had it in production for a while.


Robert N M Watson
Computer Laboratory
University of Cambridge
___
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


___
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

7.1 Panic on degraded disk w/mpt

[Charles Sprickman]

Howdy,

I dug around and can't find a PR on this, and the only other report I saw 
was in this mailing list post that has no replies:


http://www.nabble.com/7.1-BETA2-panic-on-mpt-degrade-td20183173.html

The hardware is a Dell PowerEdge 860 with the Dell/LSI SAS5 controller:
mpt0: LSILogic SAS/SATA Adapter port 0xec00-0xecff mem 
0xfe9fc000-0xfe9f,0xfe9e-0xfe9e irq 16 at device 8.0 on pci2

mpt0: MPI Version=1.5.13.0

The panic is repeatable by forcing the array into a degraded state.

Here's my best shot at getting info out of kgdb:

[r...@uniweb /home/spork]# cd /usr/obj/usr/src/sys/BWAY7/
[r...@uniweb /usr/obj/usr/src/sys/BWAY7]# kgdb kernel.debug 
/var/crash/vmcore.0 GNU gdb 6.1.1 [FreeBSD]

Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you 
are welcome to change it and/or distribute copies of it under certain 
conditions.

Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for 
details.

This GDB was configured as i386-marcel-freebsd...

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x14
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc044b09b
stack pointer   = 0x28:0xe6ee5b80
frame pointer   = 0x28:0xe6ee5b9c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 17 (swi2: cambio)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 3m7s
Physical memory: 3575 MB
Dumping 94 MB: 79 63 47 31 15

Reading symbols from /boot/kernel/acpi.ko...Reading symbols from 
/boot/kernel/acpi.ko.symbols...done.

done.
Loaded symbols for /boot/kernel/acpi.ko
#0  doadump () at pcpu.h:196
196 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) list *0xc044b09b
0xc044b09b is in xpt_done (/usr/src/sys/cam/cam_xpt.c:4832).
4827if ((done_ccb-ccb_h.func_code  XPT_FC_QUEUED) != 0) {
4828/*
4829 * Queue up the request for handling by our SWI handler
4830 * any of the non-immediate type of ccbs.
4831 */
4832sim = done_ccb-ccb_h.path-bus-sim;
4833switch (done_ccb-ccb_h.path-periph-type) {
4834case CAM_PERIPH_BIO:
4835TAILQ_INSERT_TAIL(sim-sim_doneq, 
done_ccb-ccb_h,
4836  sim_links.tqe);

(kgdb) backtrace
#0  doadump () at pcpu.h:196
#1  0xc061d0f7 in boot (howto=260) at 
/usr/src/sys/kern/kern_shutdown.c:418

#2  0xc061d3c9 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3  0xc0865fcc in trap_fatal (frame=0xe6ee5b40, eva=20)
at /usr/src/sys/i386/i386/trap.c:939
#4  0xc0866230 in trap_pfault (frame=0xe6ee5b40, usermode=0, eva=20)
at /usr/src/sys/i386/i386/trap.c:852
#5  0xc0866bc2 in trap (frame=0xe6ee5b40) at 
/usr/src/sys/i386/i386/trap.c:530

#6  0xc084d45b in calltrap () at /usr/src/sys/i386/i386/exception.s:159
#7  0xc044b09b in xpt_done (done_ccb=0xc6bf5000)
at /usr/src/sys/cam/cam_xpt.c:4832
#8  0xc044eee9 in xpt_scan_bus (periph=0xc6984b00, request_ccb=0xc6bf5000)
at /usr/src/sys/cam/cam_xpt.c:5395
#9  0xc044d241 in camisr_runqueue (V_queue=Variable V_queue is not 
available.

) at /usr/src/sys/cam/cam_xpt.c:7316
#10 0xc044d39e in camisr (dummy=0x0) at /usr/src/sys/cam/cam_xpt.c:7216
#11 0xc05fb41b in ithread_loop (arg=0xc699d770)
at /usr/src/sys/kern/kern_intr.c:1088
#12 0xc05f7f69 in fork_exit (callout=0xc05fb260 ithread_loop,
arg=0xc699d770, frame=0xe6ee5d38) at /usr/src/sys/kern/kern_fork.c:810
#13 0xc084d4d0 in fork_trampoline () at 
/usr/src/sys/i386/i386/exception.s:264


I can supply dmesg, more info, make it crash more, etc.  I suspect it will 
panic again when the rebuild completes, I'll capture that one as well.


Please let me know how to proceed - I can open a PR if this is truly a 
bug, or bring it over to freebsd-scsi if more appropriate.


Thanks,

Charles

___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
sp...@bway.net - 212.655.9344

___
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: 7.1, mpt and slow writes

[Charles Sprickman]

On Sat, 31 Jan 2009, Gary Palmer wrote:


On Sat, Jan 31, 2009 at 01:48:46AM -0500, Charles Sprickman wrote:

On Fri, 30 Jan 2009, Gary Palmer wrote:


On Thu, Jan 29, 2009 at 11:43:11PM -0500, Charles Sprickman wrote:

[ snip ]


Any idea what happened to the sysctl?  Is there some other method to
verify the loader tunable took (other than testing the throughput)?


Boot with -v.  If the loader tunable took effect, you should see
Enabling SATA WC on phy  instead of Disabling SATA ...


Cool, it works then.  Why was the info removed from the sysctl mib?

mpt0: Enabling SATA WC on phy 0
mpt0: Enabling SATA WC on phy 1

Bonnie++ is showing me about 24MB/s writes and 70MB/s reads.

Is any of this verbose stuff problematic?

mpt0: No Handlers For Any Event Notify Frames. Event 0xa (ACK not required).
mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not
required).
mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not
required).
mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not
required).
mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not
required).
mpt0: No Handlers For Any Event Notify Frames. Event 0xb (ACK not required).

And is any of this info found at boot-time accessible while the system is
running?


Hi,

Sorry, I can't answer your questions - all I did to find the
boot -v information was to look in the kernel source code.  Grepping
through the CVS history I don't actually see a point in CVS history
where there was a sysctl MIB value for the SATA WC status, although I
might be mistaken.  Perhaps you are remembering using kenv to get
at hw.mpt.enable_sata_wc instead of sysctl?


That, my friend, is precisely the problem.  kenv didn't stick in my head 
because most of the FreeBSD-isms in my head still date back to 4.x.  I am 
behind the times...


Thanks for solving the mystery for me.

Charles


Regards,

Gary


mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares High-Priority-ReSync )
mpt0:vol0(mpt0:0:0): Using Spare Pool: 0
mpt0:vol0(mpt0:0:0): 2 Members:
  (mpt0:1:32:0): Primary Online
  (mpt0:1:1:0): Secondary Online
mpt0:vol0(mpt0:0:0): RAID-1 - Optimal
mpt0:vol0(mpt0:0:0): Status ( Enabled )
(mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:0:0)
(mpt0:vol0:1): Online
(mpt0:vol0:0): Physical (mpt0:0:32:0), Pass-thru (mpt0:1:1:0)
(mpt0:vol0:0): Online

Thanks,

Charles

ps - would it kill Dell to make a damn ISO of a bootable media for RAID
controller firmware upgrades???  I don't even own anything with a floppy
drive anymore.


Regards,

Gary

___
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: 7.1, mpt and slow writes

[Charles Sprickman]

On Fri, 30 Jan 2009, Gary Palmer wrote:


On Thu, Jan 29, 2009 at 11:43:11PM -0500, Charles Sprickman wrote:

[ snip ]


Any idea what happened to the sysctl?  Is there some other method to
verify the loader tunable took (other than testing the throughput)?


Boot with -v.  If the loader tunable took effect, you should see
Enabling SATA WC on phy  instead of Disabling SATA ...


Cool, it works then.  Why was the info removed from the sysctl mib?

mpt0: Enabling SATA WC on phy 0
mpt0: Enabling SATA WC on phy 1

Bonnie++ is showing me about 24MB/s writes and 70MB/s reads.

Is any of this verbose stuff problematic?

mpt0: No Handlers For Any Event Notify Frames. Event 0xa (ACK not required).
mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not required).
mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not required).
mpt0: No Handlers For Any Event Notify Frames. Event 0x12 (ACK not required).
mpt0: No Handlers For Any Event Notify Frames. Event 0x16 (ACK not required).
mpt0: No Handlers For Any Event Notify Frames. Event 0xb (ACK not required).

And is any of this info found at boot-time accessible while the system is 
running?


mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares High-Priority-ReSync )
mpt0:vol0(mpt0:0:0): Using Spare Pool: 0
mpt0:vol0(mpt0:0:0): 2 Members:
  (mpt0:1:32:0): Primary Online
  (mpt0:1:1:0): Secondary Online
mpt0:vol0(mpt0:0:0): RAID-1 - Optimal
mpt0:vol0(mpt0:0:0): Status ( Enabled )
(mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:0:0)
(mpt0:vol0:1): Online
(mpt0:vol0:0): Physical (mpt0:0:32:0), Pass-thru (mpt0:1:1:0)
(mpt0:vol0:0): Online

Thanks,

Charles

ps - would it kill Dell to make a damn ISO of a bootable media for RAID 
controller firmware upgrades???  I don't even own anything with a floppy 
drive anymore.



Regards,

Gary

___
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

7.1, mpt and slow writes

[Charles Sprickman]

Hello,

I think this needs a few more eyes:

http://lists.freebsd.org/pipermail/freebsd-scsi/2009-January/003782.html

In short, writes are slow, likely do to the write-cache being enabled on 
the controller.  The sysctl used in 6.x to turn the cache off don't seem 
to be in 7.x.


Thanks,

Charles

___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
sp...@bway.net - 212.655.9344

___
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: 7.1, mpt and slow writes

[Charles Sprickman]

On Thu, 29 Jan 2009, Richard Tector wrote:


Charles Sprickman wrote:

Hello,

I think this needs a few more eyes:

http://lists.freebsd.org/pipermail/freebsd-scsi/2009-January/003782.html

In short, writes are slow, likely do to the write-cache being enabled on 
the controller.  The sysctl used in 6.x to turn the cache off don't seem to 
be in 7.x.


I have two Dell 860's here also running 7.1-REL.
A simple dd on one shows roughly 60MB/s writes to a mirror of 2 320GB disks 
on what I'm assuming is the same LSI controller card (SAS5)


rich...@moses:~# cat /boot/loader.conf
hw.mpt.enable_sata_wc=1

Seems to work just fine for me.


Well, now I'm puzzled.  A sysctl -a shows no hw.mpt. tree at all:

# sysctl -a|grep hw.mpt
#

It's a poor test, but:

# dd if=/dev/zero of=/jails/foo count=1M
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 144.830977 secs (3706879 bytes/sec)

# dd if=/jails/foo of=/dev/null
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 4.136582 secs (129786112 bytes/sec)

I added the tunable to loader.conf:

$ cat /boot/loader.conf
hw.mpt.enable_sata_wc=1

And still nothing in the sysctl output (there was on 6.4 on this same 
hardware, FWIW):


$ sysctl -a |grep hw.mpt
$

However, performance did improve:

# dd if=/dev/zero of=/jails/foo count=16M
16777216+0 records in
16777216+0 records out
8589934592 bytes transferred in 276.332753 secs (31085474 bytes/sec)

Any idea what happened to the sysctl?  Is there some other method to 
verify the loader tunable took (other than testing the throughput)?


I assume there's still no management tools for these controllers, right?

Thanks,

Charles


Regards,

Richard


___
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: 7.x and multiple IPs in jails

[Charles Sprickman]

On Wed, 29 Oct 2008, Robert Watson wrote:


On Tue, 28 Oct 2008, Chris St Denis wrote:


Serious question here (not trolling).

These patches have been around for years, why have they never been 
committed to trunk/stable?

...
The current patches Bjoern is preparing address most of these concerns, 
and they've been undergoing review and testing for a few months now. 
I'd like to think they will be in 8.x relatively shortly (next week or 
two), and in 7.x before 7.2.


That is great news!  I have always avoided running patches like this on 
anything that I expect to be maintaining over a long period of time, since 
you can't know for sure whether new patches will be developed going 
forward.  Having this very useful feature become part of the base really 
helps me and anyone else doing VPS-type stuff.


I did find the vimage work eventually, but it's more than I need and I was 
not too certain about how stable it is at this point.


Thanks,

Charles


Robert N M Watson
Computer Laboratory
University of Cambridge


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

7.x and multiple IPs in jails

[Charles Sprickman]

Hello all,

I've been searching around and have come up with no current discussions on 
this issue.  I'll keep it brief:


In 7.0 or 7.1 is there any provision to have multiple IP addresses in a 
jail?


I'm stumped on this, as I just started a new hosting project that needs a 
few jails.  At least one of those requires multiple IPs, which is 
something I never really even realized was not supported.  What puzzles me 
more is that before I decided to host this stuff myself, I was shopping 
for FreeBSD VPS providers, and I noticed that Verio is actually offering 
what looks like jails as VPSs, and they are offering multiple IPs.  Is 
this something they hacked up and did not contribute back?


Is there any firewall hackery to be had that can at least let me do IP 
based virtual hosts for web hosting?


Thanks,

Charles
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Recent Problems with RELENG_7 i386

[Charles Sprickman]

On Thu, 9 Oct 2008, Jeremy Chadwick wrote:


On Fri, Oct 10, 2008 at 03:51:02AM +1100, Ian Smith wrote:

 Well, I believe HZ was increased from 100 to 1000 long ago (RELENG_6?)
 as a default.  I'm really not sure of the implications of decreasing it,
 besides having less granularity for some things (the only things I know
 of would be something pertaining to firewalls, I just can't remember
 what.  My brain is full.  :-) )

You need a day off :)  But yes, RELENG_5 still had HZ=100 default, long
after the 'average' CPU clock frequency was 10 or more times faster than
the 166MHz Pentiums and such (mostly then on only 100Mbps ethernet) that
were comfortable at 100Hz slicing.  1000Hz was a big shift to catch up.

In a day or so playing around with it years ago, I found 200-250Hz good
for 300MHz, 500Hz a bit much, 1000Hz way too busy, and find my 1133MHz
P3-M happy enough at 1000Hz, though I've done no specific tests on it.

Some people had perhaps similar clock issues when their fast processors
were throttling/stepping down to very low speeds (100, even 75MHz) while
still slicing at 1000Hz, which I didn't find too surprising.  Limiting
minimum CPU freq to 300Mz or more seemed to solve many such issues, but
I haven't your perseverance for digging up the relevant threads ..

Even in 5.5-S (/sys/conf/NOTES and /sys/i386/conf/NOTES) HZ=1000 or 2000
was suggested for DEVICE_POLLING (which bf included in config, though
maybe it's not enabled?) and HZ=1000 or more was recommended when using
DUMMYNET with ipfw - to provide smoother queue dispatching, I gather.

Bottom line, IMHO, bf should probably run the default 1000Hz, 500 at
least, on an Athlon 900.  With powerd, maybe set min. freq = 150MHz?


Wow, this is fantastic information.  You've just educated me a great bit
about the history and use of HZ.  I've always had a general idea of
its importance and key role, but I was never fully aware of the history.


Not to pull this too much further OT, but in the original message there 
was a comment about HZ and context switching.  I care for a number of FBSD 
boxes that are stuffed full of qmail processes.  Context switches are 
always through the roof when the boxes are busy.  My layman's 
understanding of context switching is very vague - in short I assume 
it's some type of overhead from the kernel having to move between 
servicing different processes.  Altering HZ to tune this is very 
intriguing to me, so if anyone would like to explain, I'm all ears.



P.S. -- I need more like 6 months off.  I've never taken an official
(read: real) vacation my entire life.  Maybe some day I'll get to travel
to Seoul and visit Pyun Yong-Hyeon and drink lots of soju.  :-)


Join the f***ing club.  I'm still waiting for my honeymoon after two years 
of being married. :)


Charles


--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| 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 [EMAIL PROTECTED]


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

Recommendations for servers running SATA drives

[Charles Sprickman]

I'm forking the thread on fsck/soft-updates in hopes of getting some 
practical advice based on the discussion here of background fsck, 
softupdates and write-caching on SATA drives.


On Fri, 26 Sep 2008, Jeremy Chadwick wrote:


Let's be realistic.  We're talking about ATA and SATA hard disks, hooked
up to on-board controllers -- these are the majority of users.  Those
with ATA/SATA RAID controllers (not on-board RAID either; most/all of
those do not let you disable drive write caching) *might* have a RAID
BIOS menu item for disabling said feature.


While I would love to deploy every server with SAS, that's not practical 
in many cases, especially for light-duty servers that are not being pushed 
very hard.  I am taking my chances with multiple affordable drives and 
gmirror where I cannot throw in a 3Ware card.  I imagine that many 
non-desktop FreeBSD users are doing the same considering you can fetch a 
decent 1U box with plenty of storage for not much more than $1K.  I assume 
many here are in agreement on this point -- just making it clear that the 
bargain crowd is not some weird edge case in the userbase...



Regardless of all of this, end-users should, in no way shape or form,
be expected to go to great lengths to disable their disk's write cache.
They will not, I can assure you.  Thus, we must assume: write caching
on a disk will be enabled, period.  If a filesystem is engineered with
that fact ignored, then the filesystem is either 1) worthless, or 2)
serves a very niche purpose and should not be the default filesystem.


Arguments about defaults aside, this is my first questions.  If I've got a 
server with multiple SATA drives mirrored with gmirror, is turning on 
write-caching a good idea?  What kind of performance impact should I 
expect?  What is the relationship between caching, soft-updates, and 
either NCQ or TCQ?


Here's an example of a Seagate, trimmed for brevity:

Protocol  Serial ATA v1.0
device model  ST3160811AS

Feature  Support  EnableValue   Vendor
write cacheyes  yes
read ahead yes  yes
Native Command Queuing (NCQ)   yes   -  31/0x1F
Tagged Command Queuing (TCQ)   no   no  31/0x1F

TCQ is clearly not supported, NCQ seems to be supported, but I don't know 
how to tell if it's actually enabled or not.  Write-caching is currently 
on.


The tradeoff is apparently performance vs. more reliable recovery should 
the machine lose power, smoke itself, etc., but all I've seen is anecdotal 
evidence of how bad performance gets.


FWIW, this machine in particular had it's mainboard go up in smoke last 
week.  One drive was too far gone for gmirror to rebuild it without doing 
a forget and insert.  The remaining drive was too screwy for 
background fsck, but a manual check in single-user left me with no real 
suprises or problems.



The system is already up and the filesystems mounted.  If the error in
question is of such severity that it would impact a user's ability to
reliably use the filesystem, how do you expect constant screaming on
the console will help?  A user won't know what it means; there is
already evidence of this happening (re: mysterious ATA DMA errors which
still cannot be figured out[6]).

IMHO, a dirty filesystem should not be mounted until it's been fully
analysed/scanned by fsck.  So again, people are putting faith into
UFS2+SU despite actual evidence proving that it doesn't handle all
scenarios.


I'll ask, but it seems like the consensus here is that background fsck, 
while the default, is best left disabled.  The cases where it might make 
sense are:


-desktop systems
-servers that have incredibly huge filesystems (and even there being able 
to selectively background fsck filesystems might be helpful)


The first example is obvious, people want a fast-booting desktop.  The 
second is trading long fsck times in single-user for some uncertainty.



The problem here is that when it was created, it was sort of an
experiment.  Now, when someone installs FreeBSD, UFS2 is the default
filesystem used, and SU are enabled on every filesystem except the root
fs.  Thus, we have now put ourselves into a situation where said
feature ***must*** be reliable in all cases.

You're also forgetting a huge focus of SU -- snapshots[1].  However, there
are more than enough facts on the table at this point concluding that
snapshots are causing more problems[7] than previously expected.  And
there's further evidence filesystem snapshots shouldn't even be used in
this way[8].


...


Filesystems have to be reliable; data integrity is focus #1, and cannot
be sacrificed.  Users and administrators *expect* a filesystem to be
reliable.  No one is going to keep using a filesystem if it has
disadvantages which can result in data loss or waste of administrative
time (which I believe is what's occurring here).


The softupdates question seems tied quite closely to the 

Re: FreeBSD 7.1 and BIND exploit

[Charles Sprickman]

On Mon, 21 Jul 2008, Kevin Oberman wrote:


From: Max Laier [EMAIL PROTECTED]
Date: Mon, 21 Jul 2008 21:38:46 +0200
Sender: [EMAIL PROTECTED]

On Monday 21 July 2008 21:14:22 Doug Barton wrote:

Brett Glass wrote:
| Everyone:
|
| Will FreeBSD 7.1 be released in time to use it as an upgrade to
| close the BIND cache poisoning hole?

Brett, et al,

I'll make this simple for you. If you have a server that is running
BIND, update BIND now. If you need to use the ports, that's fine, just
do it now. Make sure that you are not specifying a port via any
query-source* options in named.conf, and that any firewall between
your named process and the outside world does keep-state on outgoing
UDP packets.


... and that any NAT device employs at least a somewhat random port
allocation mechanism - pf provides this.


And, if you are not sure how good a job it does (and I am not), you
should use the OARC test to check how well it works:
dig +short porttest.dns-oarc.net TXT

If the result is not GOOD, it's not good enough.


I was playing around with this a bit.  It seems like a patched server will 
give a standard deviation of more than 18,000.  If I make some queries 
behind a one-to-many NAT using pf, it falls to somewhere around 6,000 
(with a patched BIND - unpatched is pitiful).


PF is not *adding* any randomness to unpatched servers.  Since it has a 
(non-configurable?) range of ports it will grab when doing outbound NAT, 
the results are not as good as with no NAT intervention, but passable I 
suppose.


Of course in a 1:1 NAT setup it is transparent.

Charles


You can test a remote server by adding @remote-server to the dig
command. The server may be specified by name or IP address.

Don't forget that ANY server that caches data, including an end system
running a caching only server is vulnerable.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751


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

Re: named.conf: query-source address

[Charles Sprickman]

On Wed, 16 Jul 2008, Jeremy Chadwick wrote:


On Thu, Jul 17, 2008 at 12:20:42AM +0800, Eugene Grosbein wrote:

I fully understand and second efforts on educating people
how to configure BIND to be stong to attacks and keep them from using
query-source address with port option but how about
binding named to particular IP address when host has many of them?


We do such on our authoritative nameservers.  The options we use:


Same here...


   listen-on   { 127.0.0.1; 72.20.106.4; };
query-source address 72.20.106.4;
transfer-source 72.20.106.4;
notify-source 72.20.106.4;


But just that portion.  It works, and it passes the test with a std. dev 
of 19K or so on the port randomness.


Charles


   interface-interval 0;
   use-alt-transfer-source no;

--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| 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 [EMAIL PROTECTED]


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

Re: named.conf: query-source address

[Charles Sprickman]

On Wed, 16 Jul 2008, Chuck Swiger wrote:


On Jul 16, 2008, at 8:51 PM, Eugene Grosbein wrote:

On Wed, Jul 16, 2008 at 06:34:38PM +0100, Matthew Seaman wrote:

The 'query-source' options don't have to be specified: the system
will just choose some appropriate address according to the state of
the routing table.  'query-source' to set the source /IP/ is really
only useful in some specific server configurations with several alias
addresses any of which could be used.  That's pretty rare really.


Isn't this common to have multiple aliases at an interface?
Sometimes only one of them should be used for all DNS traffic.


About the only common reason to set up multiple aliases on an interface is 
when you're doing something like hosting multiple SSL webservers on a single 
box which actually need to have distinct IPs as a consequence.  Other than 
that, using public IPs for aliases is usually wasteful of IP address space.


I think another common reason is portability of services.  When I setup a 
box, it gets an IP that sticks with that piece of hardware.  Each distinct 
service that I pile onto it then gets it's own IP.  This has at least two 
major advantages that I've found:


-If the box dies, it's easy to move any of the services to another box 
without waiting for DNS changes to propogate.


-If one of the services outgrows the box, it's a simple matter to move 
that service elsewhere, again without playing with DNS.


I also will sometimes move services away for a major upgrade of the box. 
All of this becomes simple when you just bring an alias down on one box 
and up on another.


Next step, putting each service in a jail and moving the jail when needed.


YMMV...


On the internets, it always does. :)

Charles


Regards,
--
-Chuck

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

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

Re: possible zfs bug? lost all pools

[Charles Sprickman]

On Sun, 18 May 2008, Torfinn Ingolfsen wrote:


On Sun, 18 May 2008 09:56:17 -0300
JoaoBR [EMAIL PROTECTED] wrote:


after trying to mount my zfs pools in single user mode I got the
following message for each:

May 18 09:09:36 gw kernel: ZFS: WARNING: pool 'cache1' could not be
loaded as it was last accessed by another system (host:
gw.bb1.matik.com.br hostid: 0xbefb4a0f).  See:
http://www.sun.com/msg/ZFS-8000-EY


Did you run '/etc/rc.d.hostid start' first?
IIRC, it is needed before zfs will mount in single-user mode.


Just curious, as I've been wanting to fiddle around with ZFS in my spare 
time...  what is the solution here if you have failed hardware and you 
want to move your ZFS disks to another system (with a different host id)?


Thanks,

Charles


HTH
--
Regards,
Torfinn Ingolfsen

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


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

Re: list spam

[Charles Sprickman]

On Sun, 9 Mar 2008, Mike Lempriere wrote:

I've had it with the list spam -- is the any possibility of moderating this 
list, or changing it to must-be-subscriber-to-post?


I have a humble suggestion that perhaps the FreeBSD Foundation could 
handle...  Seeing as Cisco recently bought a company that builds an 
anti-spam appliance that runs FreeBSD, perhaps it would be worthwhile to 
ping someone at cisco about a donation of one of these boxes.


If it's as nice as the Barracuda, it would give the mailing list 
maintainers time to focus on everything else beyond the spam.


Some links:

http://lists.freebsd.org/pipermail/freebsd-jobs/2007-December/000548.html
http://www.ironport.com/products/

Just a random thought...

Charles


--
Mike Lempriere- Home: [EMAIL PROTECTED]  Phone: 206-780-2146
Cellphone: 206-200-5902;  text pager: [EMAIL PROTECTED]


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


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

Re: /usr/lib/compat and updates

[Charles Sprickman]

Just following-up to myself, please correct me if I got anything wrong...

On Tue, 15 Jan 2008, Charles Sprickman wrote:


Hi all,

I've been doing a number of 4.11 - 5.5 - 6.2 upgrades.  All of them I've 
done have gone very well.  One that was handled by someone else following my 
step-by-step directions ended up missing some items from /usr/lib/compat and 
all the timestamps on the files in that directory are quite old (2002 and 
2005).


From what I can tell, the admin missed the installworld step when he 

landed at 5.5 (probably got distracted and resumed later).

As best I can tell COMPAT4X was set in /etc/make.conf on the machine in 
question.


It was...

Can anyone help me understand where in the update process the compat libs are 
updated and which files correspond to which release?


From what I can see, in 5.x there is a /usr/src/lib/compat/4x-arch 
directory.  If COMPAT4X is set in make.conf, buildworld/installworld 
will descend into that directory and build/install the compat libs.


After digging around the 6.x and newer source trees, it appears that the 
ability to build the old libraries is gone.  If it's not gone, it has 
moved to a location I can't find. :)  If you go directly from 4.x to 6.x, 
the compat4x port in misc is how you get your libs.


Correct?

Thanks,

Charles


Thanks,

Charles

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


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

/usr/lib/compat and updates

[Charles Sprickman]

Hi all,

I've been doing a number of 4.11 - 5.5 - 6.2 upgrades.  All of them I've 
done have gone very well.  One that was handled by someone else following 
my step-by-step directions ended up missing some items from 
/usr/lib/compat and all the timestamps on the files in that directory are 
quite old (2002 and 2005).


As best I can tell COMPAT4X was set in /etc/make.conf on the machine in 
question.


Can anyone help me understand where in the update process the compat libs 
are updated and which files correspond to which release?


Thanks,

Charles

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

Re: Why does firefox keep locking up on me?

[Charles Sprickman]

Hey all,

On Tue, 15 Jan 2008, Christian Walther wrote:


Hello Bob,

On 15/01/2008, Bob Vaughan [EMAIL PROTECTED] wrote:

I've been having a problem on one particular machine with Firefox locking up
on me, requiring a hard kill to get rid of it.

The problem is thus: Firefox starts normally, but as soon as I go to a
site that requires authentication, or any other form of user input,
It will freeze as soon as I start entering my userid.

[...]


Any ideas where to start looking?


Since you've done nearly everything that could affect a binary working
properly, I think we can rule out a problem with the base system, X or
the browser itself.
I guess the problem might be related to your ~/.mozilla directory. I
noticed that a large variety of problems might be related to something
been broken inside it.
This might be an extension that might be incompatible and that isn't
installed on any of the other machines.
I'd recommend you to shut down firefox, open a terminal window and
rename the directory to something different. Please note that it
contains all settings you've made in *any* mozilla product (sunbird,
thunderbird).
Start firefox again and give it a try.


Another neat trick that I oddly enough learned using OS-X is to just setup 
a new user on the box and reserve it for checking out odd problems that 
might be caused by any user-specific settings.  This has really helped me 
out a number of times.  Very different OSes, but both end up with a ton of 
user-specific stuff in $HOME...


Charles


HTH
Christian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


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

Re: Freebsd.org is down

[Charles Sprickman]

On Fri, 14 Sep 2007, Gary Palmer wrote:


On Fri, Sep 14, 2007 at 01:26:33PM -0700, Jon wrote:

Check the freebsd-questions list for more info


For those, like me, who are not subscribed to freebsd-questions,
the list archives can be accessed at:

http://lists.freebsd.org/pipermail/freebsd-questions/2007-September/thread.html#158022


I'll save you all some trouble...  The thread basically consists of people 
noting that it does not work.  That's pretty much it.  There's no post yet 
stating what the trouble is or what the ETR is.


Of note is that portaudit relies on www.freebsd.org being up to fetch it's 
info.


Charles


That URL appears to still be answering presently.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


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

Re: BIND 9.3.1 - How to get rid of AAAA querys?

[Charles Sprickman]

On Thu, 13 Sep 2007, Darren Pilgrim wrote:


Andreas Pettersson wrote:

Mark Andrews wrote:

Why don't you go the other way and get yourself IPv6
connectivity.  You do realise that you will require it to
reach many sites in about 3 years time as they will be IPv6
only


For almost 10 years I've heard discussions about the successor to IPv4, but 
from my point of view (may differ from others..) not much has happened. Of 
course, I can imagine that when the wheel starts rolling for real things 
might change quickly. 3 years may prove to be correct, but are there any 
clear signs pointing in this direction?


The proponents of IPv6 have claimed growing real-world deployment for the 
last several years.  There is yet no significant commercial deployment--the 
real world still runs on IPv4.


Just adding another real world datapoint...  I'd love to get my hands 
dirty with IPv6.  I contacted both of our upstreams, Level3 and HE.net.


Level3 never responded, if anyone has details on what their deal is, 
please share (offlist).


HE.net wanted both more money and for us to order another port with them.

For the 0.0001% of our users that have expressed interest in v6 
connectivity, we're not going to pay for another FE port just to 
experiment.  I'm sure most other Tier-2 local/regional ISPs feel the same 
way.


If there were a free and best effort service offered by any of our 
upstreams though, I'd jump at it.


My buddy Ike over at NYCBUG does have a bunch of pictures of cheap 
consumer IPv6 home routers from his trip to Japan.  Apparently it's quite 
widespread there.


Charles


--
Darren Pilgrim
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


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

6.2, USB wedged

[Charles Sprickman]

Hi all,

I'm not too familiar with USB in 5.x or 6.x.  After some great one-on-one 
work with one of the NUT UPS tools devs, he got many linuxisms out of the 
tripplite_usb code so I can monitor a UPS here.


The code is likely not perfect, and sometimes the NUT daemon needs to be 
restarted to get fresh data.


Today it did this and I accidentally started two instances of the daemon. 
This seems to have completely wedged up the USB stack.  The tripplite_usb 
process is unkillable, and is in disk wait state, which seems odd:


nut   59693  0.0  0.1  1480  1028  p1  D 1:34PM   0:00.00 
/usr/local/libexec/nut/tripplite_usb -a colo1


All the kill -9's in the world won't stop it.

I ran usbdevs to see if it was able to probe any devices and that too 
hung and is now unkillable:


[EMAIL PROTECTED] /home/spork]# usbdevs
addr 1: UHCI root hub, VIA
^C^C^C

root  31627  0.0  0.1  1264   580  p1  D+5:33PM   0:00.00 usbdevs

Also in disk wait...

Any ideas, short of a reboot to kick things back into shape?

Here's the other processes, they all seem to be in disk wait and waiting 
to acquire a lock (DL):


root 25  0.0  0.0 0 8  ??  DL   14Mar07   0:00.97 [usb0]
root 26  0.0  0.0 0 8  ??  DL   14Mar07   0:00.00 
[usbtask]

root 28  0.0  0.0 0 8  ??  DL   14Mar07   0:00.98 [usb1]
root 29  0.0  0.0 0 8  ??  DL   14Mar07   0:00.73 [usb2]
root 31  0.0  0.0 0 8  ??  DL   14Mar07   0:00.72 [usb3]
root  34496  0.0  0.1  1288   712  ??  Is5:42PM   0:00.00 
/usr/sbin/usbd

root  31627  0.0  0.1  1264   580  p1  D+5:33PM   0:00.00 usbdevs
nut   59693  0.0  0.1  1480  1028  p1  D 1:34PM   0:00.00 
/usr/local/libexec/nut/tripplite_usb -a colo1


Also any pointers to more info on USB for users would be appreciated.

Thanks,

Charles

___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
[EMAIL PROTECTED] - 212.655.9344

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