9.1 USB flash drive: Medium not present
I csup'd to RELENG_9_1, and ran into a new regression (relative to 9.0p3). When I connect my PNY flash drive, I get this: ugen0.3: at usbus0 umass2: on usbus0 umass2: SCSI over Bulk-Only; quirks = 0x4100 umass2:5:2:-1: Attached to scbus5 da2 at umass-sim2 bus 2 scbus5 target 0 lun 0 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: UNIT ATTENTION, Medium not present My full dmesg is as follows: Copyright (c) 1992-2012 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 9.1-PRERELEASE #22: Sat Aug 11 17:50:08 CDT 2012 r...@desktop.resnet.tntech.edu:/usr/obj/usr/src/sys/CUSTOM amd64 CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (3399.70-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbff Features2=0x1f9ae3bf AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8208252928 (7828 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110527/psargs-392) ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110527/nsinit-380) acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xe000-0xe07f mem 0xf800-0xf9ff,0xe800-0xefff,0xf000-0xf3ff irq 16 at device 0.0 on pci1 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_io vgapci0: child nvidia0 requested pci_enable_io hdac0: mem 0xfa08-0xfa083fff irq 17 at device 0.1 on pci1 pci0: at device 22.0 (no driver attached) ehci0: mem 0xfa307000-0xfa3073ff irq 23 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 hdac1: mem 0xfa30-0xfa303fff irq 22 at device 27.0 on pci0 pcib2: irq 17 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 18 at device 28.2 on pci0 pci3: on pcib3 pcib4: irq 19 at device 28.3 on pci0 pci4: on pcib4 pcib5: irq 17 at device 28.4 on pci0 pci5: on pcib5 pcib6: irq 16 at device 28.5 on pci0 pci6: on pcib6 xhci0: mem 0xfa20-0xfa207fff irq 17 at device 0.0 on pci6 xhci0: 32 byte context size. usbus1 on xhci0 pcib7: irq 18 at device 28.6 on pci0 pci7: on pcib7 re0: port 0xd000-0xd0ff mem 0xf4104000-0xf4104fff,0xf410-0xf4103fff irq 18 at device 0.0 on pci7 re0: Using 1 MSI-X message re0: Chip rev. 0x2c80 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 14:da:e9:f4:8c:58 pcib8: irq 19 at device 28.7 on pci0 pci8: on pcib8 pcib9: irq 17 at device 0.0 on pci8 pci9: on pcib9 ath0: mem 0xfa10-0xfa10 irq 17 at device 2.0 on pci9 ath0: AR2413 mac 7.8 RF2413 phy 4.5 ehci1: mem 0xfa306000-0xfa3063ff irq 23 at device 29.0 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xfa305000-0xfa3057ff irq 20 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich2: at channel 2 on ahci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 orm0: at iomem 0xc-0xc
Re: FreeBSD 9.1-RC1 Available...
On 23 Aug 2012, at 22:52, "Simon L. B. Nielsen" wrote:
>
> On 23 Aug 2012, at 20:41, Peter Wemm wrote:
On Thu, 23 Aug 2012 00:50:46 -0400, Ken Smith wrote:
> With both the doc and ports repositories now moved to SVN it has been
> decided to not export the 9.1 release branch activity to CVS. So
> csup/cvsup update mechanisms are not available for updating to 9.1-RC1.
> If you would like to use SVN the branch to use is releng/9.1.
>> * RIght now you can mirror
>> svn://svn.freebsd.org/base/{stable/9,release/9.1*,etc} to your laptop,
>> and Simon is setting up a US-east coast and US-west coast mirror. You
>> can easily switch your mirrors on the fly if there's a closer/faster
>> one.
>
> Real world got in the way, but they should be ready by Friday or Saturday,
> and will be documented in the Handbook.
Mirrors are now running and documented:
http://www.freebsd.org/doc/en/books/handbook/mirrors-svn.html
I'm still doing some final tweaks so there might be some shorter outages over
the weekend, but it should be < 1m issues.
PS. also, if anyone are access http://svn.FreeBSD.org/ you are in fact now
using svn0.us-west.FreeBSD.org, to avoid having to run apache on the main svn
server, so - you might as well use the mirror directly and avoid going through
netcat...
--
Simon L. B. Nielsen
Hat: FreeBSD.org admins team
___
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 9.1-RC1 Available...
On Sat, Aug 25, 2012 at 04:04:07PM +0200, Alexandre wrote: > > No. freebsd-update(8) is a binary system updater. It does not touch > > your source tree. > > > > Freebsd-update tool installs binary updates for -RELEASE branch only (base > system + GENERIC kernel). By default, /usr/src is synced. So you can > upgrade your system and GENERIC kernel, then rebuild manually your custom > kernel if you got one. This is described in the Handbook at the page > "FreeBSD update". > You do not have to SVN or CSUP your /usr/src sources tree after used > freebsd-update tool. > You're right, my mistake. I meant to remove that last sentence after realizing this. Sorry for the confusion. Glen pgpQHzHIOKP3w.pgp Description: PGP signature
AUTO: Steve Coles is out of the office (returning 03/09/2012)
I am out of the office until 03/09/2012. Note: This is an automated response to your message "freebsd-stable Digest, Vol 475, Issue 7" sent on 25/08/2012 13:00:57. This is the only notification you will receive while this person is away. UK Businesses use 2 million tonnes of paper each year. THINK before you PRINT this e-mail. This email and all information contained within it, is confidential and intended solely for the use of the individual, or entity, to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any use, copying, dissemination or disclosure of this information is strictly prohibited. If you have received this email in error then please notify us (postmas...@mearsgroup.co.uk) so that our records can be amended and please delete the original from your system. Attachments to this email may contain software viruses, Mears Group PLC has taken every reasonable precaution to minimise this risk but we advise that any attachments should be virus checked before they are opened. Any view or opinions within this email are solely those of the author and do not necessarily represent those of Mears Group PLC and its subsidiaries. Mears Group PLC. Registered office: 1390 Montpellier Court, Gloucester Business Park, Brockworth, Gloucester GL3 4AH Registered number: 3232863. Country of registration: England and Wales ___ 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 9.1 RC1 and CAM issues with old SCSI drive
Hi, I booted FreeBSD 9.1-RC1 on one of my older scratch i386 PCs and noticed this regression -- the SCSI disk is unusable: FreeBSD 9.1-RC1 #0: Tue Aug 14 03:56:40 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 ahc0: port 0x6400-0x64ff mem 0xd300-0xd3000fff irq 3 at device 13.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs (probe0:ahc0:0:0:0): INQUIRY. CDB: 12 0 0 1 0 0 (probe0:ahc0:0:0:0): CAM status: SCSI Status Error (probe0:ahc0:0:0:0): SCSI status: Check Condition (probe0:ahc0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid field in CDB) (probe0:ahc0:0:0:0): Command Specific Info: 0x (probe0:ahc0:0:0:0): Command byte 3 is invalid (probe0:ahc0:0:0:0): Error 22, Unretryable error [da0 never appears] This drive will be found with 9.0: FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 ahc0: port 0x6400-0x64ff mem 0xd300-0xd3000fff irq 3 at device 13.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs (probe0:ahc0:0:0:0): inquiry data fails comparison at DV1 step (probe0:ahc0:0:0:0): inquiry data fails comparison at DV1 step (probe0:ahc0:0:0:0): inquiry data fails comparison at DV1 step da0 at ahc0 bus 0 scbus2 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 6.600MB/s transfers (16bit) da0: Command Queueing enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) That this drive is downgraded to 6.600MB/s appears to be known issue -- http://www.freebsd.org/cgi/query-pr.cgi?pr=128245 This appeared to work better with 6.1 FreeBSD 6.1-RELEASE #0: Mon May 29 19:39:51 EDT 2006 ahc1: port 0x9800-0x98ff mem 0xe380-0xe3800fff irq 11 at device 11.0 on pci0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) -- Kirk Russell http://www.ba23.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 9.1-RC1 Available...
On Sat, 2012-08-25 at 04:42 -0700, David Wolfskill wrote: > On Fri, Aug 24, 2012 at 10:19:36PM -0700, Dennis Glatting wrote: > > ... > > There are two things that I am confused about "base." > > > > 1) What, exactly, is base? When I do a co, what tree branch is that? > > Using CVS, failure to specify a tag would get you HEAD. > > Using SVN, failure to specify a branch will get you head. > > This may help. As noted previously, I have a local private mirror of > the FreeBSD SVN src repository located in /svn/freebsd/src/base; so: > > g1-227(9.1-P)[1] svn ls file:///svn/freebsd/src/base > ROADMAP.txt > cvs2svn/ > head/ > projects/ > release/ > releng/ > stable/ > svnadmin/ > user/ > vendor/ > vendor-crypto/ > vendor-sys/ > g1-227(9.1-P)[2] svn ls file:///svn/freebsd/src/base/releng > 2.0.5/ > 4.10/ > 4.11/ > 4.3/ > 4.4/ > 4.5/ > 4.6/ > 4.7/ > 4.8/ > 4.9/ > 5.0/ > 5.1/ > 5.2/ > 5.3/ > 5.4/ > 5.5/ > 6.0/ > 6.1/ > 6.2/ > 6.3/ > 6.4/ > 7.0/ > 7.1/ > 7.2/ > 7.3/ > 7.4/ > 8.0/ > 8.1/ > 8.2/ > 8.3/ > 9.0/ > 9.1/ > ALPHA_2_0/ > BETA_2_0/ > g1-227(9.1-P)[3] svn ls file:///svn/freebsd/src/base/stable > 2.0.5/ > 2.1/ > 2.2/ > 3/ > 4/ > 5/ > 6/ > 7/ > 8/ > 9/ > g1-227(9.1-P)[4] svn ls file:///svn/freebsd/src/base/head > COPYRIGHT > LOCKS > MAINTAINERS > Makefile > Makefile.inc1 > ObsoleteFiles.inc > README > UPDATING > bin/ > cddl/ > contrib/ > crypto/ > etc/ > games/ > gnu/ > include/ > kerberos5/ > lib/ > libexec/ > release/ > rescue/ > sbin/ > secure/ > share/ > sys/ > tools/ > usr.bin/ > usr.sbin/ > g1-227(9.1-P)[5] > > > Does that help? > > > 2) Base /appears/ not to contain releng/9.1 or stable/8. How do I mirror > > those? > > As shown above, they are there. > Thanks for the clue. > Peace, > david ___ 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 9.1-RC1 Available...
On Saturday, August 25, 2012, Glen Barber wrote: > On Sat, Aug 25, 2012 at 04:55:48AM +0100, Ben Morrow wrote: > > Quoth Ken Smith >: > > > > > > The latter. If you are not using FreeBSD-Update to handle the updates > > > of a machine you'll need to update your source tree using SVN for > > > release branches (releng/*) from now on. Updates of the CVS repository > > > will continue for the existing stable/* and head for now. I don't > think > > > anything has been decided on when that will stop. > > > > Two questions: > > > > 1. Is is sensible|supported to use freebsd-update to update just the src > > component, followed by a normal buildworld/buildkernel to update the > > rest of the system? I would much prefer to avoid having to use svn, > > especially given that it isn't in the base system. > > > > No. freebsd-update(8) is a binary system updater. It does not touch > your source tree. > > Glen > > Hi Glen, Freebsd-update tool installs binary updates for -RELEASE branch only (base system + GENERIC kernel). By default, /usr/src is synced. So you can upgrade your system and GENERIC kernel, then rebuild manually your custom kernel if you got one. This is described in the Handbook at the page "FreeBSD update". You do not have to SVN or CSUP your /usr/src sources tree after used freebsd-update tool. Regards, Alexandre ___ 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 9.1-RC1 Available...
On Fri, Aug 24, 2012 at 10:19:36PM -0700, Dennis Glatting wrote: > ... > There are two things that I am confused about "base." > > 1) What, exactly, is base? When I do a co, what tree branch is that? Using CVS, failure to specify a tag would get you HEAD. Using SVN, failure to specify a branch will get you head. This may help. As noted previously, I have a local private mirror of the FreeBSD SVN src repository located in /svn/freebsd/src/base; so: g1-227(9.1-P)[1] svn ls file:///svn/freebsd/src/base ROADMAP.txt cvs2svn/ head/ projects/ release/ releng/ stable/ svnadmin/ user/ vendor/ vendor-crypto/ vendor-sys/ g1-227(9.1-P)[2] svn ls file:///svn/freebsd/src/base/releng 2.0.5/ 4.10/ 4.11/ 4.3/ 4.4/ 4.5/ 4.6/ 4.7/ 4.8/ 4.9/ 5.0/ 5.1/ 5.2/ 5.3/ 5.4/ 5.5/ 6.0/ 6.1/ 6.2/ 6.3/ 6.4/ 7.0/ 7.1/ 7.2/ 7.3/ 7.4/ 8.0/ 8.1/ 8.2/ 8.3/ 9.0/ 9.1/ ALPHA_2_0/ BETA_2_0/ g1-227(9.1-P)[3] svn ls file:///svn/freebsd/src/base/stable 2.0.5/ 2.1/ 2.2/ 3/ 4/ 5/ 6/ 7/ 8/ 9/ g1-227(9.1-P)[4] svn ls file:///svn/freebsd/src/base/head COPYRIGHT LOCKS MAINTAINERS Makefile Makefile.inc1 ObsoleteFiles.inc README UPDATING bin/ cddl/ contrib/ crypto/ etc/ games/ gnu/ include/ kerberos5/ lib/ libexec/ release/ rescue/ sbin/ secure/ share/ sys/ tools/ usr.bin/ usr.sbin/ g1-227(9.1-P)[5] Does that help? > 2) Base /appears/ not to contain releng/9.1 or stable/8. How do I mirror > those? As shown above, they are there. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpso5GP1dxdt.pgp Description: PGP signature
Re: Problem with link aggregation + sshd
In the meantime kindly post: Ifconfig for your igb0 Netstat -rn Netstat -aln | grep 22 On 25 Aug 2012, at 13:18, Damien Fleuriot wrote: > I'll get back to you regarding link aggregation when I'm done with groceries. > > We use it here in production and it works flawlessly. > > > > On 25 Aug 2012, at 09:54, Giulio Ferro wrote: > >> No answer, so it seems that link aggregation doesn't really work in freebsd, >> this may help others with the same problem... >> >> I reverted back to one link for management and one for service, and ssh >> works as it should... >> >> >> On 08/21/2012 11:18 PM, Giulio Ferro wrote: >>> Scenario : freebsd 9 stable (yesterday) amd64 on HP server with 4 nic (igb) >>> >>> 1 nic is connected standalone to the management switch, the 3 other nics >>> are connected to a switch configured for aggregation. >>> >>> If I configure the first nic (igb0) there is no problem, I can operate >>> as I normally do and sshd functions normally. >>> >>> The problems start when I configure the 3 other nics for aggregation: >>> >>> in /etc/rc.conf >>> ... >>> ifconfig_igb1="up" >>> ifconfig_igb2="up" >>> ifconfig_igb3="up" >>> >>> cloned_interfaces=lagg0 >>> ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 >>> 192.168.12.7/24" >>> ... >>> >>> I restart the server and the aggregation seems to work correctly, in >>> fact ifconfig returns the correct lagg0 interface with the aggregated >>> links, the correct protocol (lacp) and the correct ip address and the >>> status is active. I can ping other IPs on the aggregated link. >>> >>> Also the other (standalone) link seems to work correctly. I can ping >>> that address from other machines, and I can ping other IPs from that >>> server. >>> >>> DNS lookups work ok too I can also use telnet to connect to pop3 >>> servers so there seems to be no problem on the network stack. >>> >>> But if I try to connect to the sshd service on that server, it hangs >>> indefinitely. On the server I find two sshd processes: >>> /usr/sbin/sshd >>> /usr/sbin/sshd -R >>> >>> There is no message in the logs. >>> >>> If I try to kill sshd (/etc/rc.d/sshd stop) I can't. it just stays there >>> forever waiting for the pid to die (it never does) >>> >>> Even ssh client doesn't seem to work. In fact, if I try to connect to >>> another server, the ssh client may start to work correctly, then soon >>> or later it just hangs there forever, and I can't kill it with ctrl-c. >>> >>> No firewall is configured, there is nothing else working on this server. >>> >>> Thanks for any suggestions... >>> ___ >>> 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: Problem with link aggregation + sshd
I'll get back to you regarding link aggregation when I'm done with groceries. We use it here in production and it works flawlessly. On 25 Aug 2012, at 09:54, Giulio Ferro wrote: > No answer, so it seems that link aggregation doesn't really work in freebsd, > this may help others with the same problem... > > I reverted back to one link for management and one for service, and ssh > works as it should... > > > On 08/21/2012 11:18 PM, Giulio Ferro wrote: >> Scenario : freebsd 9 stable (yesterday) amd64 on HP server with 4 nic (igb) >> >> 1 nic is connected standalone to the management switch, the 3 other nics >> are connected to a switch configured for aggregation. >> >> If I configure the first nic (igb0) there is no problem, I can operate >> as I normally do and sshd functions normally. >> >> The problems start when I configure the 3 other nics for aggregation: >> >> in /etc/rc.conf >> ... >> ifconfig_igb1="up" >> ifconfig_igb2="up" >> ifconfig_igb3="up" >> >> cloned_interfaces=lagg0 >> ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 >> 192.168.12.7/24" >> ... >> >> I restart the server and the aggregation seems to work correctly, in >> fact ifconfig returns the correct lagg0 interface with the aggregated >> links, the correct protocol (lacp) and the correct ip address and the >> status is active. I can ping other IPs on the aggregated link. >> >> Also the other (standalone) link seems to work correctly. I can ping >> that address from other machines, and I can ping other IPs from that >> server. >> >> DNS lookups work ok too I can also use telnet to connect to pop3 >> servers so there seems to be no problem on the network stack. >> >> But if I try to connect to the sshd service on that server, it hangs >> indefinitely. On the server I find two sshd processes: >> /usr/sbin/sshd >> /usr/sbin/sshd -R >> >> There is no message in the logs. >> >> If I try to kill sshd (/etc/rc.d/sshd stop) I can't. it just stays there >> forever waiting for the pid to die (it never does) >> >> Even ssh client doesn't seem to work. In fact, if I try to connect to >> another server, the ssh client may start to work correctly, then soon >> or later it just hangs there forever, and I can't kill it with ctrl-c. >> >> No firewall is configured, there is nothing else working on this server. >> >> Thanks for any suggestions... >> ___ >> 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: FreeBSD 9.1-RC1 Available...
[Removing re@] On 25 Aug 2012, at 10:33, Harald Schmalzbauer wrote: > schrieb Peter Wemm am 24.08.2012 00:14 (localtime): >> ... >> You'll also find out very quickly how much fsync(2) hurts on a softdep >> or su+j system. The svn fsfs backend does a fsync multiple times per >> revision to guarantee its transaction boundaries. > > Not only on softdep ufs, also with zfs I'm seeing big performance > regressions (checkout ports from one zfs holding svnsynced repo to > another on the same pool takes hours with svn, while completed in less > than half an hour with csup) > But my real problem is that svn is not in the base system. And for > example installing subversion package on my cvsup mirror failed because > pkg-config-0-25_1 was installed and sqlite, a dependency of subversion, > wants to install pkgconf-0.8.5. So I'm hit by the henn-egg problem. I > hope I can build subversion (sqlite) with pkg-config-0 dependency, but > right now I still have to wait for this awful slow svn checkout (svn co > file:///svn/repos/mirror/ports/head /usr/ports/) > > Can someone share any sensible tuning for svn and zfs? > > Is it possible to build any svn compatible (checkout-only-capable) > binary without that much dependencies? If so, I hope this will be in the > base very soon. If you are going to do checkouts from svn:// only you can disable Neon which should reduce the dependency chain some. I haven't found svn checkouts to be too slow most of the time, but of course I'm generally using systems with hardware RAID controller which likely helps some. PS. I don't think you should expect svn in base - it has too many dependencies, options, and is too fast moving to sanely be in the base system. -- Simon L. B. Nielsen ___ 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 9.1-RC1 Available...
schrieb Peter Wemm am 24.08.2012 00:14 (localtime): > ... > You'll also find out very quickly how much fsync(2) hurts on a softdep > or su+j system. The svn fsfs backend does a fsync multiple times per > revision to guarantee its transaction boundaries. Not only on softdep ufs, also with zfs I'm seeing big performance regressions (checkout ports from one zfs holding svnsynced repo to another on the same pool takes hours with svn, while completed in less than half an hour with csup) But my real problem is that svn is not in the base system. And for example installing subversion package on my cvsup mirror failed because pkg-config-0-25_1 was installed and sqlite, a dependency of subversion, wants to install pkgconf-0.8.5. So I'm hit by the henn-egg problem. I hope I can build subversion (sqlite) with pkg-config-0 dependency, but right now I still have to wait for this awful slow svn checkout (svn co file:///svn/repos/mirror/ports/head /usr/ports/) Can someone share any sensible tuning for svn and zfs? Is it possible to build any svn compatible (checkout-only-capable) binary without that much dependencies? If so, I hope this will be in the base very soon. Thanks, -Harry signature.asc Description: OpenPGP digital signature
Re: Problem with link aggregation + sshd
No answer, so it seems that link aggregation doesn't really work in freebsd, this may help others with the same problem... I reverted back to one link for management and one for service, and ssh works as it should... On 08/21/2012 11:18 PM, Giulio Ferro wrote: Scenario : freebsd 9 stable (yesterday) amd64 on HP server with 4 nic (igb) 1 nic is connected standalone to the management switch, the 3 other nics are connected to a switch configured for aggregation. If I configure the first nic (igb0) there is no problem, I can operate as I normally do and sshd functions normally. The problems start when I configure the 3 other nics for aggregation: in /etc/rc.conf ... ifconfig_igb1="up" ifconfig_igb2="up" ifconfig_igb3="up" cloned_interfaces=lagg0 ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.12.7/24" ... I restart the server and the aggregation seems to work correctly, in fact ifconfig returns the correct lagg0 interface with the aggregated links, the correct protocol (lacp) and the correct ip address and the status is active. I can ping other IPs on the aggregated link. Also the other (standalone) link seems to work correctly. I can ping that address from other machines, and I can ping other IPs from that server. DNS lookups work ok too I can also use telnet to connect to pop3 servers so there seems to be no problem on the network stack. But if I try to connect to the sshd service on that server, it hangs indefinitely. On the server I find two sshd processes: /usr/sbin/sshd /usr/sbin/sshd -R There is no message in the logs. If I try to kill sshd (/etc/rc.d/sshd stop) I can't. it just stays there forever waiting for the pid to die (it never does) Even ssh client doesn't seem to work. In fact, if I try to connect to another server, the ssh client may start to work correctly, then soon or later it just hangs there forever, and I can't kill it with ctrl-c. No firewall is configured, there is nothing else working on this server. Thanks for any suggestions... ___ 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: FreeBSD 9.1-RC1 Available...
[ Jim Pingle wrote on Fri 24.Aug'12 at 23:07:30 -0400 ] > On 8/23/2012 11:43 AM, Ian Lepore wrote: > > On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote: > >> > >> I found two good primers: > >> http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html > >> http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER > >> > >> The second primer in the committer handbook seems to indicate that it > >> is difficult to run an SVN mirror. This appears to me to be the > >> biggest drawback. I have been using CVS and perforce for years, but > >> subversion is new to me. > > > > It may be difficult to run an svn mirror that allows you to commit > > locally and get those changes back to the project, but running a > > read-only mirror is trivial. The script I run nightly from cron to sync > > my local mirror is: > > > > #!/bin/sh > > # > > # svnsync to pull in changes from FreeBSD to my local mirror. > > # > > svnsync sync file:///local/vc/svn/base > > > > I can't remember how I initially created and populated the mirror, but > > it's likely I grabbed a snapshot of the mirror at work and brought it > > home on a thumb drive (just to avoid initial network DL time). > > I spent a little time today setting up an SVN mirror after reading this > thread and wrote up a how-to for those looking to do the same. > > http://www.pingle.org/2012/08/24/freebsd-svn-mirror > > Comments/Flames/Corrections welcome... That's cool Jim. Certainly provides a clear explanation and simple steps. ___ 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 9240-4i 4K alignment
On 8 Aug, George Kontostanos wrote: > The problem: > > When trying to create a RaidZ pool using gpart and perform a 4K > alignment using gnop, we get the follwoing error immediately after > exporting the pool and destroying the .nop devices: > > id: 8043746387654554958 > state: FAULTED > status: One or more devices contains corrupted data. > action: The pool cannot be imported due to damaged devices or data. > The pool may be active on another system, but can be imported using > the '-f' flag. >see: http://illumos.org/msg/ZFS-8000-5E > config: > > Pool FAULTED corrupted data > raidz1-0ONLINE > 13283347160590042564 UNAVAIL corrupted data > 16981727992215676534 UNAVAIL corrupted data > 6607570030658834339 UNAVAIL corrupted data > 3435463242860701988 UNAVAIL corrupted data > > When we use glabel for the same purpose with the combination of gnop, > the pool imports fine. Might kern/170945 have something to do with this? ___ 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"
