Re: how to update ports while using pkgng?
On 16/09/2012 22:24, Andreas Nilsson wrote: Since no one asked: Why would you want to do it this way? If you are using pkgng updating is as easy as: pkg upgrade. Actually, we (the pkgng developers) think this is a perfectly valid use case, and we'd like to have it as a standard choice available to users. If you have some programs installed not available from official pkgng repositories you are on thin ice and should consider using something like ports-mgmt/poudriere to build pkgng packages of those ports and host your own repo from which you can then install them. While poudriere is an excellent piece of software, using it does involve some significant overheads. It is also tied to using ZFS as the underlying filesystem, which may not suit everyone. If you've got a whole bunch of machines to maintain, then poudriere is a no-brainer. If you've only got your own desktop, then it's not so clear cut. portmaster+pkgng patches works well for me in that scenario. Also, the official pkgng repositories aren't really in action yet: pkg.freebsd.org is a SRV record that at the moment resolves to the same beta-test repository that's been used for the last year or more. It has nothing like complete coverage of the ports tree. Plans are afoot to start using the package build clusters to generate a comprehensive set of pkgng packages and keep them regularly updated, but these will be introduced only after a great deal of testing and debugging, and initially will probably be just for 10-CURRENT. So, in the mean time, building your own packages is a good idea. We want to make it so that you can mix locally compiled (and customized) pkgs with the standard ones from the official repos, and work is currently under way to put in place a large chunk of the functionality necessary for that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: bsnmpd always died on HDD detach
On Sun, Sep 16, 2012 at 07:07:20PM +0200, Miroslav Lachman wrote: I am glad to read that you found the bug! The fix (patch) seems trivial - will it be commited / MFCed? :) Andrey told me that he was not sure when he would be able to commit his work, so I have just committed my fix. I am going to MFC it. -- Mikolaj Golub ___ 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
Multipathing issue under FreeBSD
Hi, We carried few tests under FreeBSD using our LSI HBA after enabling multipathing. During the test of verifying the fail over, inconsistently we are observing data corruption while removing the active path. The way we enabled multipathing and steps that we had followed for the test are as below Procedure to Enable the Multipath: 1. Load the Multipath using the following cmd - gmultipah load 2. Make the following entry in the /boot/loder.conf - geom_multipath_load=YES 3. Assign the label for the drives using the following cmd - gmultipah label -v mpta /dev/da1 /dev/da2 4. Create the file system using the following cmd - newfs /dev/multipath/mpta 5. Mount the file system to the /mnt/ location 6. Run the IO's on the mounted file system Observation details: 1. Connect the Enclosure with 2 to 3 SAS drives to system which has multipath enabled. 2. Create the file system and run the IO's using the above procedure. 3. Unplug the Active path from the enclosure. 4. Sometimes the fail over on the passive path happens. But at times Data corruption is seen on any one of drive while pulling out the active path from the enclosure. On Other drives the IO still continue to run. 5. After removing the active path the multipath status will be shown up as degraded. Again on inserting the multipath the status will come up as optimal. The IOs are still running but the drive on which data corruption occurs the IOs never continue on that drive. The testing was done on two different enclosure and details are as follows. Server Enclosure Observation IBM x3650 M4 Camden 1 out 5 iterations Data corruption on any one of the drive. IBM x3650 M4 DELL Power Vault MD1220 1 out 5 iterations Data corruption on any one of the drive. Kindly let us know if there any issues similar to this has been reported to the community. Or does it look like a fresh and does it really seem to be potential defect? Best Regards Subramani ___ 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: how to update ports while using pkgng?
Will it be updated after ports? So then, I can just use pkgng :-) On 2012/09/17 14:07, Matthew Seaman wrote: Also, the official pkgng repositories aren't really in action yet ___ 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: Multipathing issue under FreeBSD
On Mon, 17 Sep 2012 04:14:14 -0500, Pasupathy, Subramani subramani.pasupa...@lsi.com wrote: Kindly let us know if there any issues similar to this has been reported to the community. Or does it look like a fresh and does it really seem to be potential defect? I did extensive testing of the new(er) multipath code earlier (January-March) this year before putting our ZFS SANs into production. I was never able to produce corruption by breaking the multipath during my tests. There would be errors, but it always seemed to recover. I also would have expected ZFS to notice write errors or something during scrubbing. Hopefully this info is useful to someone out there... ___ 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: how to update ports while using pkgng?
On 9/14/2012 11:41 PM, Mike Manilone wrote: Hi, I'm using ports with pkgng enabled. But I found that portmaster won't work. Is there any way to update ports? Thanks! Sincerely, Mike Manilone ports-mgmt/portupgrade-devel will work with PKGNG out of the box. 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
[PATCH] Locking for adv(4), adw(4), aha(4), ahb(4), aic(4), and bt(4)
I have patches to add locking to the adv(4), adw(4), aha(4), ahb(4), aic(4), and bt(4) drivers so that they no longer use Giant. I would appreciate any testing folks are able to do. The patches are against HEAD but should apply to 8 or 9. Make sure you have INVARIANTS and INVARIANT_SUPPORT enabled for any initial testing that you do. Thanks! http://www.FreeBSD.org/~jhb/patches/adv_locking.patch http://www.FreeBSD.org/~jhb/patches/adw_locking.patch http://www.FreeBSD.org/~jhb/patches/aha_locking.patch http://www.FreeBSD.org/~jhb/patches/ahb_locking.patch http://www.FreeBSD.org/~jhb/patches/aic_locking.patch http://www.FreeBSD.org/~jhb/patches/bt_locking.patch -- 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
Re: Clang as default compiler
On Wed, Sep 12, 2012 at 01:04:20AM -0500, Mark Linimon wrote: On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote: Is there a specif PR to use for ports that fails with clang and does not specify to use gcc ( devel/cdecl and deskutils/calibre so were the culprits so far) There is no specific PR. We have not yet placed the requirement on our ports maintainers to deal with clang. For most of the failures, we are already aware of them, as a result of our periodic runs. So, just filing a PR to say broken on clang doesn't really help us all that much. Those are build failures. What about crashes? E.g. I've recently had crashes with x11-wm/i3 and x11/rxvt-unicode. Both problems disappeared after recompiling them with gcc46. Roland -- R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpI9WK6wuK68.pgp Description: PGP signature
[releng_9_1 tinderbox] failure on arm/arm
TB --- 2012-09-17 19:40:00 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-09-17 19:40:00 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-09-17 19:40:00 - starting RELENG_9_1 tinderbox run for arm/arm TB --- 2012-09-17 19:40:00 - cleaning the object tree TB --- 2012-09-17 19:40:00 - checking out /src from svn://svn.freebsd.org/base/releng/9.1 TB --- 2012-09-17 19:40:00 - cd /tinderbox/RELENG_9_1/arm/arm TB --- 2012-09-17 19:40:00 - /usr/local/bin/svn cleanup /src TB --- 2012-09-17 19:41:33 - /usr/local/bin/svn update /src TB --- 2012-09-17 19:46:06 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-09-17 19:46:06 - ERROR: unable to check out the source tree TB --- 2012-09-17 19:46:06 - 3.32 user 3.69 system 365.86 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-arm-arm.full ___ 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: Userland dtrace broken?
On 09/13/12 18:04, Chris Nehren wrote: Relevant to my interests, too. I've followed the instructions on the wiki / in the handbook (on 9.0/9.1-PRE) and only receive error messages. Is DTrace supposed to be working properly on 9.x, or is it still experimental? From my experience, as long as you avoid using the pid provider, and don't bother trying to get fbt:::return arguments, then it works reliably. I haven't tried userland static probes though. Tracing userland works *occasionally* (I find maybe ~20% of the time when it's the first command run on a machine with 1m uptime), but you're more likely to get strange results, or just a panic. -- The information contained in this message is confidential and intended for the addressee only. If you have received this message in error, or there are any problems with its content, please contact the sender. iCritical is a trading name of Critical Software Ltd. Registered in England: 04909220. Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH. This message has been scanned for security threats by iCritical. www.icritical.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
Re: Clang as default compiler
On 2012-09-17 21:43, Roland Smith wrote: On Wed, Sep 12, 2012 at 01:04:20AM -0500, Mark Linimon wrote: ... For most of the failures, we are already aware of them, as a result of our periodic runs. So, just filing a PR to say broken on clang doesn't really help us all that much. Those are build failures. What about crashes? E.g. I've recently had crashes with x11-wm/i3 and x11/rxvt-unicode. Both problems disappeared after recompiling them with gcc46. We can't figure them all out without *your* help. :-) Please attempt to run the program in a debugger, gather core dumps, etc. Or at least, try to make it into a reproducible case, so somebody else can attempt to diagnose it. And please specify the exact version of clang you used. Now, most of the time this is because programs contain bugs, or undefined behavior, which happens to go unnoticed with gcc, for example because it optimized by accident in such a way to mask the bug. In a few other cases, real clang bugs are found, and most of the time, those can be fixed quickly. That said, in these cases specifically, how do the applications crash? Right at startup, or after specific inputs or user actions? ___ 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
