Re: qbittorrent 2.2.9 8.0-STABLE Amd64
On 06/18/10 10:26, Andriy Gapon wrote: on 18/06/2010 18:51 Жиндарев Алексей said the following: Jun 18 19:33:54 last message repeated 371 times Jun 18 19:41:31 last message repeated 1359 times Jun 18 19:43:29 kernel: WARNING pid 31369 (qbittorrent): ioctl sign-extension ioctl 8004667e Jun 18 19:44:00 last message repeated 545 times Jun 18 19:45:45 last message repeated 1751 times Jun 18 19:45:46 kernel: WARNING pid 31369 (qbittorrent): ioctl sign-extension ioctl 8004667e Jun 18 19:46:17 last message repeated 481 times Manifested after the new port, possibly after updating QT This is FIONBIO ioctl. Look through the code where this is passed via a variable of incorrect type. Correct type for ioctl request should be unsigned long. I can't find any references to FIONBIO at all, or even the word ioctl. The software in question is a bittorrent client, I can't see any reason it would even use ioctl's directly. I also checked the libtorrent-rasterbar sources (which qbittorrent uses) and there is no FIONBIO there either. Thanks for your help Andriy, but I'm more confused than ever. :) Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!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"
Re: kernel panic on 8.1-rc1 amd64
On Fri, 18 Jun 2010 15:10:34 -0500 (CDT) "Sean C. Farley" wrote: > On Fri, 18 Jun 2010, Nenhum_de_Nos wrote: > > > On Thu, June 17, 2010 23:49, Alexandre \"Sunny\" Kovalenko wrote: > >> Not much -- this is just panic I had in the same timeframe and solved > >> it by disabling and, consequently rebuilding, Virtual Box kernel > >> modules. I assume you either not loading or did disable the remaining > >> two: vboxnetflt.ko and vboxnetadp.ko. > >> > >> I guess any third-party modules (webcam, qemu, etc.) would be good > >> candidates for being disabled -- it seams like there were changes in > >> the kernel which required rebuild of them. > >> > >> Outside of that -- sorry, out of ideas. > > > > thanks for the tip, for the record it was a module (or two), as I > > tried disabling both nvidia and vboxdrv. > > > > I'll try to update both now, > > For the record, it has been reported on emulation@ that the nvidia and > vbox drivers do not get along with each other. I occasionally get > lockups while there is network traffic between my host and > (console-only) guest both running FreeBSD 8 amd64. > > Unfortunately, I do not know which module is at fault, and I have been > too busy to try harder to find the culprit. I read about that also, but they were ok to that moment. I'll rebuild the nvidia driver and try again. thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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.1 speed issues
On 06/18/10 14:48, William D. Colburn (Schlake) wrote: So I've just upgraded from whatever was stable in 2004 to 8.1 (it's a private file server in my house, I pay no attention to it until it crashes), and uh, the speed difference is very noticeable. In short, it's like I bought a brand new machine that eleven times as fast when all I did was upgrade the OS. How on earth did you guys make such a dramatic improvement? Only 11? We must be slipping ... Doug (Thanks for the kind words, they really are appreciated) -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!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"
Re: FreeBSD 8.1-RC1 Available...
On 06/18/10 15:27, Chip Camden wrote: Thanks for the clarification. I want to stay stable (though my wife would contest that I've ever been). There's only so much an operating system, ANY operating system can do ... Doug (you're welcome) :) -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!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"
Re: 8.1 speed issues
On Fri, 18 Jun 2010, William D. Colburn (Schlake) wrote: So I've just upgraded from whatever was stable in 2004 to 8.1 (it's a private file server in my house, I pay no attention to it until it crashes), and uh, the speed difference is very noticeable. In short, it's like I bought a brand new machine that eleven times as fast when all I did was upgrade the OS. How on earth did you guys make such a dramatic improvement? Well, I guess the good news is that we did a lot in six years. The bad news is that figuring out which changes helped your specific configuration and workload would be quite tricky. Certainly, our work on SMP optimization for scheduling, network stack, threading, storage, etc, has been a big deal. Thre are also countless protocol improvements in TCP/IP, significant changes in file system code, ... that could well be involved. Needless to say, it's satisfying to hear that it worked out -- I'd like to think we have even further good stuff coming in 9! Robert ___ 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.1 speed issues
On Fri, Jun 18, 2010 at 4:48 PM, William D. Colburn (Schlake) wrote: > So I've just upgraded from whatever was stable in 2004 to 8.1 (it's a > private file server in my house, I pay no attention to it until it > crashes), and uh, the speed difference is very noticeable. In short, > it's like I bought a brand new machine that eleven times as fast when > all I did was upgrade the OS. How on earth did you guys make such a > dramatic improvement? > BSD = Blazing Speed, Dude! Oh, and it's Free. Seriously though, if you're curious, the source code commit logs are always enlightening ;) -Brandon ___ 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 8.1-RC1 Available...
On Jun 18 2010 12:47, Doug Barton wrote: > On 06/18/10 10:01, Chip Camden wrote: > >On Jun 17 2010 23:06, Ken Smith wrote: > >> > >[snip] > >> > >>If you are updating an already running machine the CVS branch > >>tag is RELENG_8_1, or if you prefer SVN use "releng/8.1". > >> > >[snap] > > > >Forgive me if the answer to this question should be obvious. I'm on > >stable/8, so if I understand correctly all I should need to do is change > >my supfile CVS tag to RELENG_8_1, csup, and rebuild? > > If you're already on -stable you don't have to do anything, unless you > want to stay at what will eventually become 8.1-RELEASE. > > > hth, > > Doug > > -- > > ... and that's just a little bit of history repeating. > -- Propellerheads > > Improve the effectiveness of your Internet presence with > a domain name makeover!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" Thanks for the clarification. I want to stay stable (though my wife would contest that I've ever been). -- Sterling (Chip) Camden http://camdensoftware.com | http://chipstips.com | http://chipsquips.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"
8.1 speed issues
So I've just upgraded from whatever was stable in 2004 to 8.1 (it's a private file server in my house, I pay no attention to it until it crashes), and uh, the speed difference is very noticeable. In short, it's like I bought a brand new machine that eleven times as fast when all I did was upgrade the OS. How on earth did you guys make such a dramatic improvement? -- -- Schlake ___ 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"
make installworld breaks at share/syscons/scrnmaps
8-STABLE system csup today
FreeBSD xxx.local 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Fri Jun 18 18:28:03
CEST 2010 r...@xxx.local:/usr/obj/usr/src/sys/XXX amd64
make installworld
breaks at
===> share/syscons/scrnmaps (install)
./armscii8-2haik8.mk armscii8-2haik8.tmp
uuencode armscii8-2haik8.tmp armscii8-2haik8 > armscii8-2haik8.scm
uuencode: Command not found.
*** Error code 127
Stop in /usr/src/share/syscons/scrnmaps.
*** Error code 1
...
I fixed it on that machine by this patch,
--- share/syscons/scrnmaps/Makefile.orig2010-06-18 22:48:35.0
+0200
+++ share/syscons/scrnmaps/Makefile 2010-06-18 22:48:47.0 +0200
@@ -16,7 +16,7 @@
${SCRMAPS}: ${.TARGET:R}.mk
./${.TARGET:R}.mk ${.TARGET:R}.tmp
- uuencode ${.TARGET:R}.tmp ${.TARGET:R} > ${.TARGET}
+ /usr/bin/uuencode ${.TARGET:R}.tmp ${.TARGET:R} > ${.TARGET}
rm -f ${.TARGET:R}.tmp
${SCRMAPS_MK}: ${.TARGET:R} mkscrfil.c
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
...but where the /usr/bin-PATH disappeared?
-- Damian
___
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 panic on 8.1-rc1 amd64
On Fri, 18 Jun 2010, Nenhum_de_Nos wrote: On Thu, June 17, 2010 23:49, Alexandre \"Sunny\" Kovalenko wrote: Not much -- this is just panic I had in the same timeframe and solved it by disabling and, consequently rebuilding, Virtual Box kernel modules. I assume you either not loading or did disable the remaining two: vboxnetflt.ko and vboxnetadp.ko. I guess any third-party modules (webcam, qemu, etc.) would be good candidates for being disabled -- it seams like there were changes in the kernel which required rebuild of them. Outside of that -- sorry, out of ideas. thanks for the tip, for the record it was a module (or two), as I tried disabling both nvidia and vboxdrv. I'll try to update both now, For the record, it has been reported on emulation@ that the nvidia and vbox drivers do not get along with each other. I occasionally get lockups while there is network traffic between my host and (console-only) guest both running FreeBSD 8 amd64. Unfortunately, I do not know which module is at fault, and I have been too busy to try harder to find the culprit. Sean -- s...@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"
Fwd: Sysinstall crashes in 8.1-BETA1
Verified to exist in 8.1-RC1. Submitted as PR 147980. -- Forwarded message -- From: Nicholas Mills Date: Sat, Jun 5, 2010 at 9:01 PM Subject: Sysinstall crashes in 8.1-BETA1 To: ra...@freebsd.org Hello, I found and patched a bug in sysinstall(8). My system is running GENERIC 8.1-BETA1 on i386. Initial install went well, but after the system booted I wanted to add some other distributions. However, every time I attempted to connect to an ftp server sysinstall would crash and dump core. I traced the problem down to some uninitialized variables in tcpip.c:tcpDeviceSelect. Attached is my patch. Thanks, Nick Mills nlmi...@g.clemson.edu tcpip.patch Description: Binary data ___ 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 8.1-RC1 Available...
On 06/18/10 10:01, Chip Camden wrote: On Jun 17 2010 23:06, Ken Smith wrote: [snip] If you are updating an already running machine the CVS branch tag is RELENG_8_1, or if you prefer SVN use "releng/8.1". [snap] Forgive me if the answer to this question should be obvious. I'm on stable/8, so if I understand correctly all I should need to do is change my supfile CVS tag to RELENG_8_1, csup, and rebuild? If you're already on -stable you don't have to do anything, unless you want to stay at what will eventually become 8.1-RELEASE. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!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"
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
On Fri, 2010-06-18 at 10:42 -0700, Jeremy Chadwick wrote:
> On Fri, Jun 18, 2010 at 04:47:11PM +0100, Matthew Lear wrote:
> > Hello Jeremy,
> > Thanks very much for the feedback.
> >
> > [snip]
> > > Could you please provide the full output from "smartctl -a /dev/ad0"
> > > here? Your drive may be completely fine and you may not have to swap it
> > > at all; hard to say.
> >
> > Sure. See below:
> > {snip}
>
> Your SMART statistics look completely OK. There's nothing there that
> indicates there were any write failures or otherwise. I'll explain near
> the end of the Email how to test a range of LBAs "just in case".
Good. That's what I thought too :-)
> I'll take a moment to point out that the error previously seen was a
> timeout during a write transaction (WRITE_DMA48). Recap:
>
> > > > ad0: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=395032335
> > > > ad0: FAILURE - WRITE_DMA48 status=51
> > > > error=10 LBA=395032335
> > > > ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode
>
> The status codes shown (status=51 and error=10) are hexadecimal. I'm
> pointing this out because they aren't preceded by '0x' or '$' and it
> clarifies my next point:
>
> NID_NOT_FOUND (bit 4 set in the ATA error field) is referred to as IDNF
> per ATA6-ACS specification and onward, so I'll refer to it as that.
> (I've always wondered why FreeBSD calls this NID_NOT_FOUND; IDFN stands
> for ID Not Found, so what's with the extra "N"? I've always felt this
> is a typo...)
>
> Using the ATA8-ACS specification working draft (2007/05/21), since it's
> more recent, we see the following:
>
> Section 6.2 - Error field
> Section 6.2.4 - ID Not Found (IDNF) bit
>
> Error bit 4. The IDNF bit shall be set to one if a user-accessible
> address was not found. The IDNF bit shall be set to one if an
> address outside of the range of user-accessible addresses is
> requested when command aborted is not returned (see 4.11.3 and
> 6.2.1).
>
> Section 4.11 - Host Protected Area (HPA) feature set
> Section 4.11.3 - 28-bit and 48-bit HPA commands
>
> Any read or write command to an address above the maximum address
> specified by the SET MAX ADDRESS or SET MAX ADDRESS EXT command shall
> cause command completion with the IDNF bit set to one and ERR set to
> one, or command aborted.
>
> There's no definition of what "address" means in 6.2.4, but the most
> logical (pun intended) guess is an LBA. This error is returned by the
> disk (e.g. not a controller-induced error). I've mentioned this problem
> in the past:
>
> http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting
>
> I've always read IDNF to mean "OS requested access (read or write) to an
> LBA which is out of bounds", where "out of bounds" means "not between 0
> and ". How exactly is that possible? Alexander, do you have
> any familiarity with this error code per ATA spec?
>
> Matthew, can you provide output from "atacontrol cap ad0"? Thanks.
Sure thing. See below.
[r...@meshuga /home/matt]# atacontrol cap ad0
Protocol SATA revision 2.x
device model WDC WD3200AAKS-00VYA0
serial number WD-WCARW0164427
firmware revision 12.01B02
cylinders 16383
heads 16
sectors/track 63
lba supported 268435455 sectors
lba48 supported 625142448 sectors
dma supported
overlap not supported
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
SMART yes yes
microcode download yes yes
security yes no
power management yes yes
advanced power management no no 0/0x00
automatic acoustic management yes no 254/0xFE128/0x80
[r...@meshuga /home/matt]#
>
> Now regarding the LBA tests -- "smartctl -t select,start-end" will do
> the trick. start should be a starting LBA, end should be an ending LBA.
> The OS claims that LBA 395032335 is what was requested to be accessed
> when the failure happened, so I would recommend picking start/end ranges
> around that area. Remember that a single sector encapsulates a very
> large number of blocks (especially given sizes of disks today), so it's
> wise to pick a very large range of LBAs. I would recommend this in your
> case:
>
> smartctl -t select,39000,41000 /dev/ad0
[r...@meshuga /home/matt]# smartctl -t
select,39000-41000 /dev/ad0
smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 7.2-RELEASE-p4 i386] (local
build)
Copyright (C) 2002-10 by Bruce Allen,
http://smartmontools.sourceforge.net
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Selective self-test routine immediately
in off-line mode".
SPAN STARTIN
Re: kernel panic on 8.1-rc1 amd64
On Thu, June 17, 2010 23:49, Alexandre \"Sunny\" Kovalenko wrote: > Not much -- this is just panic I had in the same timeframe and solved it > by disabling and, consequently rebuilding, Virtual Box kernel modules. I > assume you either not loading or did disable the remaining two: > vboxnetflt.ko and vboxnetadp.ko. > > I guess any third-party modules (webcam, qemu, etc.) would be good > candidates for being disabled -- it seams like there were changes in the > kernel which required rebuild of them. > > Outside of that -- sorry, out of ideas. thanks for the tip, for the record it was a module (or two), as I tried disabling both nvidia and vboxdrv. I'll try to update both now, thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ 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 8.1-RC1 Available...
On Jun 17 2010 23:06, Ken Smith wrote: > [snip] > > If you are updating an already running machine the CVS branch > tag is RELENG_8_1, or if you prefer SVN use "releng/8.1". > [snap] Forgive me if the answer to this question should be obvious. I'm on stable/8, so if I understand correctly all I should need to do is change my supfile CVS tag to RELENG_8_1, csup, and rebuild? -- Sterling (Chip) Camden http://camdensoftware.com | http://chipstips.com | http://chipsquips.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: [Stable 7] CPIO breakage/
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010/06/18 10:51, Sean Bruno wrote: > On Thu, 2010-06-17 at 15:13 -0700, Xin LI wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 2010/06/17 13:53, Peter Jeremy wrote: >>> On 2010-Jun-15 17:22:50 -0700, Xin LI wrote: On 2010/06/15 17:05, Sean Bruno wrote: > A little more background. It looks like symlinks are getting stripped > of their '/' which sucks. Ideas? >>> ... > e.g. /home/foo/bar -> /opt/baz/blob > > becomes > > home/foo/bar -> opt/baz/blob > > Yuck. This is a security measurement I think. >>> >>> Can someone please explain how stripping a leading '/' off the >>> destination of a symlink enhances security? The destination is >>> not being written to. >>> --absolute-filenames disables this behavior. >>> >>> This definitely reduces security and would seem to be far more >>> dangerous than being able to create symlinks to absolute pathnames. >> >> Sorry I have misunderstood the original issue. It's the link target >> being mangled and doesn't seem right to me. I'll ask the author about this. >> >> The attached patch should restore the old behavior. >> >> Cheers, >> - -- >> Xin LI http://www.delphij.net/ >> FreeBSD - The Power to Serve! Live free or die > > Yep, *this* patches seems to make things much happier. I'll integrate > cpio 2.8 back into the Yahoo tree when this is merged in. Thanks for testing, I have committed the patch as r209311 and sorry for the breakage. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBCAAGBQJMG7lxAAoJEATO+BI/yjfBBhEIAJRbR1ZniY+JQ4Ak+He+FWKw jRXb/lTC1PfCDIi5Vm+j0NGAZP2hNBzt9k7uouDyguXcHKvPNXKFhjvaJtdDK40Y e2Pr2PNeXzwBGaL27eDPdjt2gxZ16GbzQe47d2jyT3nQRUYBGehJcLzJl7chrLZn 0PJmztmZt8Uc6oeQo427PzhgqcCFG5Edrc7dtiFZ1rvdaXGXd64mu30oArLV3MCA c//wgx+qK2wQ1AGeylZGOqbJmtgdxY3+g961a/G9c0Y/Bt+muWBY5xDK1LpA7IcN /s8l39g6TMzjp4YYlRUG5flhv3xtFACZxxAnkDYA+02cR2euNpt1irjdxj7jwvI= =V3yO -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: em(4) duplex problems with 82541EI on RELENG_8, -CURRENT on PowerEdge 1850
Yes, the commits today are slated to get into 8.1, at least that's my understanding. Jack On Fri, Jun 18, 2010 at 10:46 AM, Brandon Gooch wrote: > On Tue, Jun 1, 2010 at 2:37 PM, Jeremy Chadwick > wrote: > > On Tue, Jun 01, 2010 at 03:18:39PM -0400, Brian A. Seklecki wrote: > >> = Re-posted from freebsd-hardware@, since this is more of a bug > >> report than a hardware comparability inquiry / buying strategy > >> discussion. == > >> > >> All: > >> > >> Has anyone upgraded their PowerEdge 1850s to 8.0-PL or > >> RELENG_8 -stable? We're seeing problems where 7.2-PL and > >> 6.3-PL were not affected on the same hardware. > >> > >> The problem is that forcing the duplex 100/full on both > >> sides no longer functions. > >> > >> Configuration: > >> > >>- A variety of Cisco L2/L3 switches over the last decade: > >>-- 2848G-L3 > >>-- 2950 > >>-- 2960s > >>-- 3550-12Ts > >>-- 3550XLs > >>-- Duplex forced 100/full on Cisco side > >>- FreeBSD/amd64 RELENG_8 or 9-CURRENT with duplex > >> forced '100baseTX mediaopt full-duplex', > >>- This configuration has worked since FreeBSD 5.4 > >> > >> When connected to PowerEdge 1850r1/r2, with the onboard Intel > >> 82541EI, the parenthesis show an actual media speed/duplex of: > >> > >> media: Ethernet 100baseTX (100baseTX ) > >> > >> The same configuration using a Dell-sold Intel dual port > >> 82546EB, in the same system, on the same switch, works fine. > >> > >> > >> - > >> ifconfig(8): > >> - > >> em3: flags=8843 >> MULTICAST> metric 0 mtu 1500 > >> options=9b > >> ether 00:13:72:4f:70:81 > >> inet 192.168.97.20 netmask 0xff80 broadcast 192.168.97.127 > >> media: Ethernet 100baseTX (100baseTX ) > >> status: active > >> - > >> em0: flags=8843 >> MULTICAST> metric 0 mtu 1500> > >> options=9b > >> ether 00:04:23:c8:fe:ac > >> media: Ethernet 100baseTX > >> status: active > >> - > >> - > >> pciconf(8): > >> - > >> e...@pci0:7:8:0: class=0x02 card=0x016d1028 chip=0x10768086 > >> rev=0x05 hdr=0x00 > >> vendor = 'Intel Corporation' > >> device = 'Gigabit Ethernet Controller (82541EI)' > >> class = network > >> subclass = ethernet > >> e...@pci0:3:11:0: class=0x02 card=0x10128086 chip=0x10108086 > rev=0x01 > >> hdr=0x00 > >>vendor = 'Intel Corporation' > >>device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' > >>class = network > >>subclass = ethernet > >> > >> - > >> > >> rc.conf(5) for shits & giggles: > >> > >> ifconfig_em0="inet X netmask Y media 100baseTX mediaopt full-duplex" > >> ifconfig_em3="inet Z netmask F media 100baseTX mediaopt full-duplex" > >> > >> > >> > >> Example IOS switch config: > >> interface FastEthernet0/39 > >> description I hate Dell > >> switchport access vlan 100 > >> switchport mode access > >> speed 100 > >> duplex full > >> spanning-tree portfast > >> end > >> > >> > >> I've been clearing interface counters on the switch side, but I'll send > >> 'netstat -i', 'show interface counters', and 'sudo sysctl -w > >> dev.em.3.stats=1' ASAP to illustrate connectivity errors soon. > >> > >> Are we being punished for patronizing Dell? > >> > >> Is it possible that ifconfig(8) output has simply changed? Are the > >> values in the parenthesis on the right the Ethernet auto-sense desired > >> values where as outside the parenthesis the current active values? > >> > >> In 6.3/7.2, once you forced a speed/duplex, the values in parenthesis > >> went away entirely. > >> > >> The only way I've been able to make that happen is to #define in > >> src/sys/dev/e1000/if_em.h: > >> > >> #define DO_AUTO_NEG 0 > >> /* > >>* This parameter control whether or not the driver will wait for > >>* autonegotiation to complete. > >>* 1 - Wait for autonegotiation to complete > >>* 0 - Don't wait for autonegotiation to complete > >> */ > >> > >> Also seems odd that some ICs are affected but not others. > >> > >> Its also possible that my problems are pf(4) + setfib(8) related and I > >> that this is a separate issue. > >> > >> Two new notes since the original post: > >> > >> - I have confirmed this problem on two revisions of the Dell > >>8th gen hardware in two different datacenters > >> - The problem persists on -CURRENT from 05/2010 > >> - RELENG_7 does not seem to be impacted > >> - More stats below. > >> > >> > >> Thanks, > >> ~BAS > >> > >> --- > >> > >> > >> > >> em1: link state changed to DOWN > >> em1: link state changed to UP > >> em1: link state changed to DOWN > >> em1: link state changed to UP > >> em1: link state changed to DOWN > >> em1: link state changed to UP > >> em1: link state changed to DOWN > >> em1: link state changed to UP > >> em1: link state changed t
Re: [Stable 7] CPIO breakage/
On Thu, 2010-06-17 at 15:13 -0700, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 2010/06/17 13:53, Peter Jeremy wrote: > > On 2010-Jun-15 17:22:50 -0700, Xin LI wrote: > >> On 2010/06/15 17:05, Sean Bruno wrote: > >>> A little more background. It looks like symlinks are getting stripped > >>> of their '/' which sucks. Ideas? > > ... > >>> e.g. /home/foo/bar -> /opt/baz/blob > >>> > >>> becomes > >>> > >>> home/foo/bar -> opt/baz/blob > >>> > >>> Yuck. > >> > >> This is a security measurement I think. > > > > Can someone please explain how stripping a leading '/' off the > > destination of a symlink enhances security? The destination is > > not being written to. > > > >> --absolute-filenames disables this behavior. > > > > This definitely reduces security and would seem to be far more > > dangerous than being able to create symlinks to absolute pathnames. > > Sorry I have misunderstood the original issue. It's the link target > being mangled and doesn't seem right to me. I'll ask the author about this. > > The attached patch should restore the old behavior. > > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve!Live free or die Yep, *this* patches seems to make things much happier. I'll integrate cpio 2.8 back into the Yahoo tree when this is merged in. Thanks for your patience and work on -stable. Sean ___ 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: em(4) duplex problems with 82541EI on RELENG_8, -CURRENT on PowerEdge 1850
On Tue, Jun 1, 2010 at 2:37 PM, Jeremy Chadwick wrote: > On Tue, Jun 01, 2010 at 03:18:39PM -0400, Brian A. Seklecki wrote: >> = Re-posted from freebsd-hardware@, since this is more of a bug >> report than a hardware comparability inquiry / buying strategy >> discussion. == >> >> All: >> >> Has anyone upgraded their PowerEdge 1850s to 8.0-PL or >> RELENG_8 -stable? We're seeing problems where 7.2-PL and >> 6.3-PL were not affected on the same hardware. >> >> The problem is that forcing the duplex 100/full on both >> sides no longer functions. >> >> Configuration: >> >> - A variety of Cisco L2/L3 switches over the last decade: >> -- 2848G-L3 >> -- 2950 >> -- 2960s >> -- 3550-12Ts >> -- 3550XLs >> -- Duplex forced 100/full on Cisco side >> - FreeBSD/amd64 RELENG_8 or 9-CURRENT with duplex >> forced '100baseTX mediaopt full-duplex', >> - This configuration has worked since FreeBSD 5.4 >> >> When connected to PowerEdge 1850r1/r2, with the onboard Intel >> 82541EI, the parenthesis show an actual media speed/duplex of: >> >> media: Ethernet 100baseTX (100baseTX ) >> >> The same configuration using a Dell-sold Intel dual port >> 82546EB, in the same system, on the same switch, works fine. >> >> >> - >> ifconfig(8): >> - >> em3: flags=8843> MULTICAST> metric 0 mtu 1500 >> options=9b >> ether 00:13:72:4f:70:81 >> inet 192.168.97.20 netmask 0xff80 broadcast 192.168.97.127 >> media: Ethernet 100baseTX (100baseTX ) >> status: active >> - >> em0: flags=8843> MULTICAST> metric 0 mtu 1500> >> options=9b >> ether 00:04:23:c8:fe:ac >> media: Ethernet 100baseTX >> status: active >> - >> - >> pciconf(8): >> - >> e...@pci0:7:8:0: class=0x02 card=0x016d1028 chip=0x10768086 >> rev=0x05 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Gigabit Ethernet Controller (82541EI)' >> class = network >> subclass = ethernet >> e...@pci0:3:11:0: class=0x02 card=0x10128086 chip=0x10108086 >> rev=0x01 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Dual Port Gigabit Ethernet Controller (Copper) (82546EB)' >> class = network >> subclass = ethernet >> >> - >> >> rc.conf(5) for shits & giggles: >> >> ifconfig_em0="inet X netmask Y media 100baseTX mediaopt full-duplex" >> ifconfig_em3="inet Z netmask F media 100baseTX mediaopt full-duplex" >> >> >> >> Example IOS switch config: >> interface FastEthernet0/39 >> description I hate Dell >> switchport access vlan 100 >> switchport mode access >> speed 100 >> duplex full >> spanning-tree portfast >> end >> >> >> I've been clearing interface counters on the switch side, but I'll send >> 'netstat -i', 'show interface counters', and 'sudo sysctl -w >> dev.em.3.stats=1' ASAP to illustrate connectivity errors soon. >> >> Are we being punished for patronizing Dell? >> >> Is it possible that ifconfig(8) output has simply changed? Are the >> values in the parenthesis on the right the Ethernet auto-sense desired >> values where as outside the parenthesis the current active values? >> >> In 6.3/7.2, once you forced a speed/duplex, the values in parenthesis >> went away entirely. >> >> The only way I've been able to make that happen is to #define in >> src/sys/dev/e1000/if_em.h: >> >> #define DO_AUTO_NEG 0 >> /* >> * This parameter control whether or not the driver will wait for >> * autonegotiation to complete. >> * 1 - Wait for autonegotiation to complete >> * 0 - Don't wait for autonegotiation to complete >> */ >> >> Also seems odd that some ICs are affected but not others. >> >> Its also possible that my problems are pf(4) + setfib(8) related and I >> that this is a separate issue. >> >> Two new notes since the original post: >> >> - I have confirmed this problem on two revisions of the Dell >> 8th gen hardware in two different datacenters >> - The problem persists on -CURRENT from 05/2010 >> - RELENG_7 does not seem to be impacted >> - More stats below. >> >> >> Thanks, >> ~BAS >> >> --- >> >> >> >> em1: link state changed to DOWN >> em1: link state changed to UP >> em1: link state changed to DOWN >> em1: link state changed to UP >> em1: link state changed to DOWN >> em1: link state changed to UP >> em1: link state changed to DOWN >> em1: link state changed to UP >> em1: link state changed to DOWN >> em1: link state changed to UP >> em1: link state changed to DOWN >> >> em0: Excessive collisions = 0 >> em0: Sequence errors = 0 >> em0: Defer count = 0 >> em0: Missed Packets = 0 >> em0: Receive No Buffers = 0 >> em0: Receive Length Errors = 0 >> em0: Receive errors = 0 >> em0: Crc errors = 0 >> em0: Alignment errors = 0 >> em0: Collision/Carrier extension errors = 0 >> em0: RX overruns = 0 >> em0: watchdog timeouts = 0 >> em
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
On Fri, Jun 18, 2010 at 04:47:11PM +0100, Matthew Lear wrote:
> Hello Jeremy,
> Thanks very much for the feedback.
>
> [snip]
> > Could you please provide the full output from "smartctl -a /dev/ad0"
> > here? Your drive may be completely fine and you may not have to swap it
> > at all; hard to say.
>
> Sure. See below:
> {snip}
Your SMART statistics look completely OK. There's nothing there that
indicates there were any write failures or otherwise. I'll explain near
the end of the Email how to test a range of LBAs "just in case".
I'll take a moment to point out that the error previously seen was a
timeout during a write transaction (WRITE_DMA48). Recap:
> > > ad0: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=395032335
> > > ad0: FAILURE - WRITE_DMA48 status=51
> > > error=10 LBA=395032335
> > > ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode
The status codes shown (status=51 and error=10) are hexadecimal. I'm
pointing this out because they aren't preceded by '0x' or '$' and it
clarifies my next point:
NID_NOT_FOUND (bit 4 set in the ATA error field) is referred to as IDNF
per ATA6-ACS specification and onward, so I'll refer to it as that.
(I've always wondered why FreeBSD calls this NID_NOT_FOUND; IDFN stands
for ID Not Found, so what's with the extra "N"? I've always felt this
is a typo...)
Using the ATA8-ACS specification working draft (2007/05/21), since it's
more recent, we see the following:
Section 6.2 - Error field
Section 6.2.4 - ID Not Found (IDNF) bit
Error bit 4. The IDNF bit shall be set to one if a user-accessible
address was not found. The IDNF bit shall be set to one if an
address outside of the range of user-accessible addresses is
requested when command aborted is not returned (see 4.11.3 and
6.2.1).
Section 4.11 - Host Protected Area (HPA) feature set
Section 4.11.3 - 28-bit and 48-bit HPA commands
Any read or write command to an address above the maximum address
specified by the SET MAX ADDRESS or SET MAX ADDRESS EXT command shall
cause command completion with the IDNF bit set to one and ERR set to
one, or command aborted.
There's no definition of what "address" means in 6.2.4, but the most
logical (pun intended) guess is an LBA. This error is returned by the
disk (e.g. not a controller-induced error). I've mentioned this problem
in the past:
http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting
I've always read IDNF to mean "OS requested access (read or write) to an
LBA which is out of bounds", where "out of bounds" means "not between 0
and ". How exactly is that possible? Alexander, do you have
any familiarity with this error code per ATA spec?
Matthew, can you provide output from "atacontrol cap ad0"? Thanks.
Now regarding the LBA tests -- "smartctl -t select,start-end" will do
the trick. start should be a starting LBA, end should be an ending LBA.
The OS claims that LBA 395032335 is what was requested to be accessed
when the failure happened, so I would recommend picking start/end ranges
around that area. Remember that a single sector encapsulates a very
large number of blocks (especially given sizes of disks today), so it's
wise to pick a very large range of LBAs. I would recommend this in your
case:
smartctl -t select,39000,41000 /dev/ad0
I would highly recommend doing this with the disk not doing any I/O,
though it won't hurt it (it'll just delay the scan). "smartctl -a" will
show the state of things in the "SMART Selective self-test log" at the
bottom, or somewhere else within the output (depends on the drive).
This should, in my opinion, rule out whether or not there's a bad block
or something along those lines within said range. Given what I believe
IDNF represents, I would say your scan will probably come back clean.
Also remember that the scan performed here is a *disk-level scan*; the
disk firmware itself is doing it (the OS isn't involved). This helps
rule out any sort of "weird" issues that the OS may be reporting ("hey
man, LBA 8943943983492893428932489324 is bad!" "Yeah sure it is").
> The two devices in the array are on channels 0 and 1. There is indeed a
> second drive on channel 0 (160G). As I said above, I use that as an
> additional back up device but it's not part of the array.
Okay, so executing "atacontrol detach ata0" will cause you to lose both
ad0 and ad1. If you can live with that, then cool.
> > What motherboard is this? Can you change the setting to either
> > "Native", "Enhanced", or (even better) "AHCI"? I've seen some systems
> > where the Serial ATA option in the BIOS has an "Auto" option, which does
> > totally bizarre things at times.
>
> I think this has been covered in subsequent postings. I could try it but
> as you say below, I'd like to resolve the disk issue first.
> ...
> > The atacontrol man page covers your situation:
> > ...
> I don't think this is the case for me since ad0 and ad2 are on seperate
> ata channels.
> ...
>
Re: qbittorrent 2.2.9 8.0-STABLE Amd64
on 18/06/2010 18:51 Жиндарев Алексей said the following: > Jun 18 19:33:54 last message repeated 371 times > Jun 18 19:41:31 last message repeated 1359 times > Jun 18 19:43:29 kernel: WARNING pid 31369 (qbittorrent): ioctl > sign-extension ioctl 8004667e > Jun 18 19:44:00 last message repeated 545 times > Jun 18 19:45:45 last message repeated 1751 times > Jun 18 19:45:46 kernel: WARNING pid 31369 (qbittorrent): ioctl > sign-extension ioctl 8004667e > Jun 18 19:46:17 last message repeated 481 times > > Manifested after the new port, possibly after updating QT This is FIONBIO ioctl. Look through the code where this is passed via a variable of incorrect type. Correct type for ioctl request should be unsigned long. -- 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"
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
Hello Jeremy, Thanks very much for the feedback. [snip] > Could you please provide the full output from "smartctl -a /dev/ad0" > here? Your drive may be completely fine and you may not have to swap it > at all; hard to say. Sure. See below: smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 7.2-RELEASE-p4 i386] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Blue Serial ATA family Device Model: WDC WD3200AAKS-00VYA0 Serial Number:WD-WCARW0164427 Firmware Version: 12.01B02 User Capacity:320,072,933,376 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is:Fri Jun 18 16:27:54 2010 BST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (8400) seconds. Offline data collection capabilities:(0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 100) minutes. Conveyance self-test routine recommended polling time:( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051Pre-fail Always - 0 3 Spin_Up_Time0x0003 218 150 021Pre-fail Always - 2100 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 118 5 Reallocated_Sector_Ct 0x0033 200 200 140Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051Old_age Always - 0 9 Power_On_Hours 0x0032 088 088 000Old_age Always - 9316 10 Spin_Retry_Count0x0012 100 100 051Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 100 051Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 116 192 Power-Off_Retract_Count 0x0032 200 200 000Old_age Always - 115 193 Load_Cycle_Count0x0032 200 200 000Old_age Always - 118 194 Temperature_Celsius 0x0022 109 103 000Old_age Always - 38 196 Reallocated_Event_Count 0x0032 200 200 000Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x003e 200 200 000Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 051Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted without error 00% 9299 - # 2 Short offline Completed without error 00% 9298 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1
qbittorrent 2.2.9 8.0-STABLE Amd64
Jun 18 19:33:54 last message repeated 371 times Jun 18 19:41:31 last message repeated 1359 times Jun 18 19:43:29 kernel: WARNING pid 31369 (qbittorrent): ioctl sign-extension ioctl 8004667e Jun 18 19:44:00 last message repeated 545 times Jun 18 19:45:45 last message repeated 1751 times Jun 18 19:45:46 kernel: WARNING pid 31369 (qbittorrent): ioctl sign-extension ioctl 8004667e Jun 18 19:46:17 last message repeated 481 times Manifested after the new port, possibly after updating QT -- С Уважением,Алексей Жиндарев. ___ 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: [HEADSUP]: Ports feature freeze for 8.1 now in effect
On Fri, 18 Jun 2010 14:10:28 +0200 Erwin Lansing wrote: > In preparation for 8.1-RELEASE, the ports tree is now in feature > freeze. > > Normal upgrade, new ports, and changes that only affect other branches > are allowed without prior approval but with the extra Feature safe: > yes tag in the commit message. Any commit that is sweeping, i.e. > touches a large number of ports, infrastructural changes, commits to > ports with unusually high number of dependent ports, and any other > commit that requires the rebuilding of many packages is not allowed > without prior explicit approval from portmgr after that date. > > When in doubt, please do not hesitate to contact portmgr. "any commit that requires the rebuilding of many packages" And this time we will ask for instant back-out of everything that should had not been committed in the first place. If you have time, you can always help with unmaintained ports: http://qat.tecnik93.com/index.php?action=failed_buildports&maintainer=ports%40freebsd.org&; or even maintained ones: http://qat.tecnik93.com/index.php?action=failed_buildports Help us getting a good, stable package set for the release please, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
Jeremy Chadwick wrote: > On Fri, Jun 18, 2010 at 01:36:53PM +0200, Miroslav Lachman wrote: >> Jeremy Chadwick wrote: >>> On Fri, Jun 18, 2010 at 08:08:24AM +0100, Matthew Lear wrote: >> [...] >> The drives in the RAID exist on two seperate ATA channels: [r...@meshuga /home/matt]# atacontrol list ATA channel 0: Master: ad0 SATA revision 2.x Slave: ad1 SATA revision 1.x ATA channel 1: Master: ad2 SATA revision 2.x Slave: no device present ATA channel 2: Master: acd0 SATA revision 1.x Slave: no device present ATA channel 3: Master: no device present Slave: no device present ad1 is a third 160G drive that I periodically back up to using cron. >>> So your RAID-1 array consists of ad0 and ad2? You didn't provide >>> "atacontrol status" output so I'm going to assume that's the case. >>> >>> What's odd to me is that you somehow have two disks on a single ATA >>> channel -- look closely at channel 0. SATA has a 1:1 device-to-channel >>> mapping, so I'm a little surprised to see there's two devices on channel >>> 0. To me, this indicates your system BIOS is configured to run in >>> "Emulation" mode -- where the ATA controller pretends to be a PATA/IDE >>> controller, thus SATA-0 and SATA-1 devices appear as primary master and >>> primary slave, respectively. >>> >>> What motherboard is this? Can you change the setting to either >>> "Native", "Enhanced", or (even better) "AHCI"? I've seen some systems >>> where the Serial ATA option in the BIOS has an "Auto" option, which does >>> totally bizarre things at times. >>> >>> But before changing the setting, I would recommend dealing with the disk >>> problem first. Changing the SATA controller operation mode will almost >>> certainly change all of your device names (you'll have to go into >>> single-user mode, mount filesystems by hand, fix /etc/fstab, etc.). >> [...] >> >> It is "normal" on HP G5 series. I have ProLiant ML 110 G5. I tried >> all type of settings in BIOS, but all of them shows two disks on one >> ATA channel: >> >> HP ProLiant ML 110 G5 >> >> FreeBSD 7.2-RELEASE-p4 amd64 GENERIC >> >> r...@kiwi ~/# atacontrol list >> ATA channel 0: >> Master: ad0 SATA revision 2.x >> Slave: ad1 SATA revision 2.x >> ATA channel 1: >> Master: ad2 SATA revision 2.x >> Slave: ad3 SATA revision 2.x >> ATA channel 2: >> Master: acd0 SATA revision 1.x >> Slave: no device present >> ATA channel 3: >> Master: no device present >> Slave: no device present >> >> >> >> atapci0: port >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c10-0x1c1f,0x1c00-0x1c0f at >> device 31.2 on pci0 >> ata0: on atapci0 >> ata0: [ITHREAD] >> ata1: on atapci0 >> ata1: [ITHREAD] >> pci0: at device 31.3 (no driver attached) >> atapci1: port >> 0x1c68-0x1c6f,0x1c5c-0x1c5f,0x1c60-0x1c67,0x1c58-0x1c5b,0x1c30-0x1c3f,0x1c20-0x1c2f >> irq 18 at device 31.5 on pci0 >> atapci1: [ITHREAD] >> ata2: on atapci1 >> ata2: [ITHREAD] >> ata3: on atapci1 >> ata3: [ITHREAD] >> >> >> pciconf -lv >> atap...@pci0:0:31:2:class=0x01018a card=0x31f4103c >> chip=0x29208086 rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82801IB/IR/IH (ICH9 Family) 4 port Serial ATA >> Storage Controller 1' >> class = mass storage >> subclass = ATA >> >> atap...@pci0:0:31:5:class=0x010185 card=0x31f4103c >> chip=0x29268086 rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82801IB/IR/IH (ICH9 Family) 2 port Serial ATA >> Storage Controller 2' >> class = mass storage >> subclass = ATA >> >> >> >> ad0: 953869MB at ata0-master SATA300 >> ad1: 953869MB at ata0-slave SATA300 >> ad2: 953869MB at ata1-master SATA300 >> ad3: 953869MB at ata1-slave SATA300 >> da0 at umass-sim0 bus 0 target 0 lun 0 >> da0: Removable Direct Access SCSI-2 device >> da0: 40.000MB/s transfers >> da0: 1928MB (3948544 512 byte sectors: 255H 63S/T 245C) >> acd0: DVDR at ata2-master SATA150 >> >> >> I am using this machine as storage for backups with ZFS RAIDZ >> without any timeouts so I think that two disks on one channel is not >> causing the timeouts (only little slowdown) > > Wow, that's really... interesting. :-) What this indicates is that the > controller is running in Native/Enhanced mode yet devices attached to > SATA ports #0/#1 are master/slave on channel 0, and ports #2/#3 are > master/slave on channel 1. Except AHCI, all other modes are just variations of PATA emulation. "subclass = ATA" means that there is no AHCI enabled. PATA emulation itself should not be a problem, but it is definitely not good from performance and hot-swap points. As already told, ata(4) has very strict timeout values. It may happen, that due to medium errors drive needs too much time co complete I/O. It is theoretically possible that SMART may complete the test due to higher timeo
Re: /usr/src fails to compile in 8.0 after cvsup to RELENG_8
On Thu, Jun 17, 2010 at 7:09 AM, Matthew Seaman wrote: > Uh -- you don't need to compile emacs again. You can package up what > you already have installed under 8.0: e.g. I just reinstalled from the new CD without saving the package. Emacs is compiling, 8.1 is running, and I went ahead and ordered 8T more of disk to add to the machine to celebrate my success. -- -- Schlake ___ 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"
[HEADSUP]: Ports feature freeze for 8.1 now in effect
In preparation for 8.1-RELEASE, the ports tree is now in feature freeze. Normal upgrade, new ports, and changes that only affect other branches are allowed without prior approval but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commits to ports with unusually high number of dependent ports, and any other commit that requires the rebuilding of many packages is not allowed without prior explicit approval from portmgr after that date. When in doubt, please do not hesitate to contact portmgr. -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpjUJDoWTfnI.pgp Description: PGP signature
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
On Fri, Jun 18, 2010 at 01:36:53PM +0200, Miroslav Lachman wrote: > Jeremy Chadwick wrote: > >On Fri, Jun 18, 2010 at 08:08:24AM +0100, Matthew Lear wrote: > > [...] > > >>The drives in the RAID exist on two seperate ATA channels: > >>[r...@meshuga /home/matt]# atacontrol list > >>ATA channel 0: > >> Master: ad0 SATA revision 2.x > >> Slave: ad1 SATA revision 1.x > >>ATA channel 1: > >> Master: ad2 SATA revision 2.x > >> Slave: no device present > >>ATA channel 2: > >> Master: acd0 SATA revision 1.x > >> Slave: no device present > >>ATA channel 3: > >> Master: no device present > >> Slave: no device present > >> > >>ad1 is a third 160G drive that I periodically back up to using cron. > > > >So your RAID-1 array consists of ad0 and ad2? You didn't provide > >"atacontrol status" output so I'm going to assume that's the case. > > > >What's odd to me is that you somehow have two disks on a single ATA > >channel -- look closely at channel 0. SATA has a 1:1 device-to-channel > >mapping, so I'm a little surprised to see there's two devices on channel > >0. To me, this indicates your system BIOS is configured to run in > >"Emulation" mode -- where the ATA controller pretends to be a PATA/IDE > >controller, thus SATA-0 and SATA-1 devices appear as primary master and > >primary slave, respectively. > > > >What motherboard is this? Can you change the setting to either > >"Native", "Enhanced", or (even better) "AHCI"? I've seen some systems > >where the Serial ATA option in the BIOS has an "Auto" option, which does > >totally bizarre things at times. > > > >But before changing the setting, I would recommend dealing with the disk > >problem first. Changing the SATA controller operation mode will almost > >certainly change all of your device names (you'll have to go into > >single-user mode, mount filesystems by hand, fix /etc/fstab, etc.). > > [...] > > It is "normal" on HP G5 series. I have ProLiant ML 110 G5. I tried > all type of settings in BIOS, but all of them shows two disks on one > ATA channel: > > HP ProLiant ML 110 G5 > > FreeBSD 7.2-RELEASE-p4 amd64 GENERIC > > r...@kiwi ~/# atacontrol list > ATA channel 0: > Master: ad0 SATA revision 2.x > Slave: ad1 SATA revision 2.x > ATA channel 1: > Master: ad2 SATA revision 2.x > Slave: ad3 SATA revision 2.x > ATA channel 2: > Master: acd0 SATA revision 1.x > Slave: no device present > ATA channel 3: > Master: no device present > Slave: no device present > > > > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c10-0x1c1f,0x1c00-0x1c0f at > device 31.2 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > ata1: on atapci0 > ata1: [ITHREAD] > pci0: at device 31.3 (no driver attached) > atapci1: port > 0x1c68-0x1c6f,0x1c5c-0x1c5f,0x1c60-0x1c67,0x1c58-0x1c5b,0x1c30-0x1c3f,0x1c20-0x1c2f > irq 18 at device 31.5 on pci0 > atapci1: [ITHREAD] > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > > > pciconf -lv > atap...@pci0:0:31:2:class=0x01018a card=0x31f4103c > chip=0x29208086 rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801IB/IR/IH (ICH9 Family) 4 port Serial ATA > Storage Controller 1' > class = mass storage > subclass = ATA > > atap...@pci0:0:31:5:class=0x010185 card=0x31f4103c > chip=0x29268086 rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801IB/IR/IH (ICH9 Family) 2 port Serial ATA > Storage Controller 2' > class = mass storage > subclass = ATA > > > > ad0: 953869MB at ata0-master SATA300 > ad1: 953869MB at ata0-slave SATA300 > ad2: 953869MB at ata1-master SATA300 > ad3: 953869MB at ata1-slave SATA300 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 40.000MB/s transfers > da0: 1928MB (3948544 512 byte sectors: 255H 63S/T 245C) > acd0: DVDR at ata2-master SATA150 > > > I am using this machine as storage for backups with ZFS RAIDZ > without any timeouts so I think that two disks on one channel is not > causing the timeouts (only little slowdown) Wow, that's really... interesting. :-) What this indicates is that the controller is running in Native/Enhanced mode yet devices attached to SATA ports #0/#1 are master/slave on channel 0, and ports #2/#3 are master/slave on channel 1. I don't have an HP box to tinker with, but when I get home in a few hours I'll tinker around with BIOS settings on my Supermicro ICH7-based test box and see if I can reproduce it. I'm curious: does the same behaviour (see first paragraph) happen on RELENG_8 as well? Adding mav@ for some insights -- you ever seen this, Alexander? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
Jeremy Chadwick wrote: On Fri, Jun 18, 2010 at 08:08:24AM +0100, Matthew Lear wrote: [...] The drives in the RAID exist on two seperate ATA channels: [r...@meshuga /home/matt]# atacontrol list ATA channel 0: Master: ad0 SATA revision 2.x Slave: ad1 SATA revision 1.x ATA channel 1: Master: ad2 SATA revision 2.x Slave: no device present ATA channel 2: Master: acd0 SATA revision 1.x Slave: no device present ATA channel 3: Master: no device present Slave: no device present ad1 is a third 160G drive that I periodically back up to using cron. So your RAID-1 array consists of ad0 and ad2? You didn't provide "atacontrol status" output so I'm going to assume that's the case. What's odd to me is that you somehow have two disks on a single ATA channel -- look closely at channel 0. SATA has a 1:1 device-to-channel mapping, so I'm a little surprised to see there's two devices on channel 0. To me, this indicates your system BIOS is configured to run in "Emulation" mode -- where the ATA controller pretends to be a PATA/IDE controller, thus SATA-0 and SATA-1 devices appear as primary master and primary slave, respectively. What motherboard is this? Can you change the setting to either "Native", "Enhanced", or (even better) "AHCI"? I've seen some systems where the Serial ATA option in the BIOS has an "Auto" option, which does totally bizarre things at times. But before changing the setting, I would recommend dealing with the disk problem first. Changing the SATA controller operation mode will almost certainly change all of your device names (you'll have to go into single-user mode, mount filesystems by hand, fix /etc/fstab, etc.). [...] It is "normal" on HP G5 series. I have ProLiant ML 110 G5. I tried all type of settings in BIOS, but all of them shows two disks on one ATA channel: HP ProLiant ML 110 G5 FreeBSD 7.2-RELEASE-p4 amd64 GENERIC r...@kiwi ~/# atacontrol list ATA channel 0: Master: ad0 SATA revision 2.x Slave: ad1 SATA revision 2.x ATA channel 1: Master: ad2 SATA revision 2.x Slave: ad3 SATA revision 2.x ATA channel 2: Master: acd0 SATA revision 1.x Slave: no device present ATA channel 3: Master: no device present Slave: no device present atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c10-0x1c1f,0x1c00-0x1c0f at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) atapci1: port 0x1c68-0x1c6f,0x1c5c-0x1c5f,0x1c60-0x1c67,0x1c58-0x1c5b,0x1c30-0x1c3f,0x1c20-0x1c2f irq 18 at device 31.5 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] pciconf -lv atap...@pci0:0:31:2:class=0x01018a card=0x31f4103c chip=0x29208086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) 4 port Serial ATA Storage Controller 1' class = mass storage subclass = ATA atap...@pci0:0:31:5:class=0x010185 card=0x31f4103c chip=0x29268086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801IB/IR/IH (ICH9 Family) 2 port Serial ATA Storage Controller 2' class = mass storage subclass = ATA ad0: 953869MB at ata0-master SATA300 ad1: 953869MB at ata0-slave SATA300 ad2: 953869MB at ata1-master SATA300 ad3: 953869MB at ata1-slave SATA300 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 1928MB (3948544 512 byte sectors: 255H 63S/T 245C) acd0: DVDR at ata2-master SATA150 I am using this machine as storage for backups with ZFS RAIDZ without any timeouts so I think that two disks on one channel is not causing the timeouts (only little slowdown) 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"
Re: network deamons starting before network!
Mark Stapper schrieb: > Hello, > > Since updating to 8.X I noticed that network services were started > before the network was up! > I use lagg failover configuration on both my FreeBSD boxes. > First, boot fails on mounting my nfs-shares. > After entering and exiting the "rescue" shell, the system boots as normal. > > uname -a > FreeBSD mario 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #4: Fri Jun 18 > 07:46:01 CEST 2010 *...@mario:/usr/obj/usr/src/sys/mario amd64 > What could I do to fix this? > > Here's an exerpt from /var/log/messages: > > Jun 18 09:10:25 ntpd[1376]: ntpd 4.2.4p5-a (1) > Jun 18 09:10:25 kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 > Jun 18 09:10:27 ntpd_initres[1412]: host name not found: yoshi > Jun 18 09:10:27 kernel: nfe0: link state changed to UP > Jun 18 09:10:27 kernel: lagg0: link state changed to UP > Jun 18 09:10:27 kernel: nfe1: link state changed to UP > Jun 18 09:10:27 ntpd_initres[1412]: couldn't resolve `yoshi', giving up > on it > Jun 18 09:10:28 dhclient: New Hostname (lagg0): mario > Jun 18 09:10:28 dhclient: New IP Address (lagg0): 10.58.235.6 > Jun 18 09:10:28 dhclient: New Subnet Mask (lagg0): 255.255.255.0 > Jun 18 09:10:28 dhclient: New Broadcast Address (lagg0): 10.58.235.255 > Jun 18 09:10:28 dhclient: New Routers (lagg0): 10.58.235.1 > > Hello, adding: synchronous_dhclient="YES" to /etc/rc.conf solved some similar issues for me. The default behaviour of getting an IP via dhcp has changed. -- Alfred Bartsch mailto:bart...@dssgmbh.de ___ 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: network deamons starting before network!
On Fri, Jun 18, 2010 at 10:47:34AM +0200, Mark Stapper wrote:
> On 18/06/2010 10:26, Jeremy Chadwick wrote:
> > On Fri, Jun 18, 2010 at 09:34:24AM +0200, Mark Stapper wrote:
> >
> >> Hello,
> >>
> >> Since updating to 8.X I noticed that network services were started
> >> before the network was up!
> >>
> > This is common/normal. I wrote a script (still working on getting it
> > added to the base system) to deal with this issue. Please see:
> >
> > http://jdc.parodius.com/freebsd/netwait
> >
> > Drop this into /usr/local/etc/rc.d, chmod it 755, and read the
> > descriptions of the variables and add the appropriate settings to
> > rc.conf.
> >
> > Please be aware netwait_if only takes a single interface; you're using
> > lagg, so I hope that when your system boots whichever interface you pick
> > in netwait_if the one which you default to using.
> >
> >
> couldn't I use lagg0 on this parameter?
You could, but it won't necessarily work in the way you think it will.
netwait explicitly looks for link interface state ("status: no carrier")
in ifconfig output. This methodology is used in other base system
scripts.
If lagg devices offer that line in ifconfig, then the script will work
but won't necessarily do what you expect. It's very common on FreeBSD
for drivers of this sort to ""lie"" (please note the quotes) about the
state of link. Meaning, lagg0 might show link, but maybe that means
"Yeah! I'm configured!" -- but that doesn't mean the *physical network
interfaces lagg0 is associated with* are actually functional.
See where I'm going with this?
In your situation, assuming lagg0 provides a status line in ifconfig,
then yes you can use that -- but *ultimately* you're going to be reliant
entirely upon the netwait_ip ping tests to verify network connections
are working. That's just the nature of the beast.
The bottom line is that the netwait script *cannot* be reliably used in
"complex network situations" (and this may be one of those). Below is
my original mail to -stable about the script (then called
"waitnetwork"); see "CAVEATS / POINTS OF INTEREST". There is truly no
universal way that covers everyone's configuration/setup.
http://www.mail-archive.com/freebsd-stable@freebsd.org/msg109853.html
--
| 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"
Re: network deamons starting before network!
On 18/06/2010 10:26, Jeremy Chadwick wrote: > On Fri, Jun 18, 2010 at 09:34:24AM +0200, Mark Stapper wrote: > >> Hello, >> >> Since updating to 8.X I noticed that network services were started >> before the network was up! >> > This is common/normal. I wrote a script (still working on getting it > added to the base system) to deal with this issue. Please see: > > http://jdc.parodius.com/freebsd/netwait > > Drop this into /usr/local/etc/rc.d, chmod it 755, and read the > descriptions of the variables and add the appropriate settings to > rc.conf. > > Please be aware netwait_if only takes a single interface; you're using > lagg, so I hope that when your system boots whichever interface you pick > in netwait_if the one which you default to using. > > couldn't I use lagg0 on this parameter? thx btw :-) Regards, Mark signature.asc Description: OpenPGP digital signature
Re: network deamons starting before network!
On Fri, Jun 18, 2010 at 09:34:24AM +0200, Mark Stapper wrote: > Hello, > > Since updating to 8.X I noticed that network services were started > before the network was up! This is common/normal. I wrote a script (still working on getting it added to the base system) to deal with this issue. Please see: http://jdc.parodius.com/freebsd/netwait Drop this into /usr/local/etc/rc.d, chmod it 755, and read the descriptions of the variables and add the appropriate settings to rc.conf. Please be aware netwait_if only takes a single interface; you're using lagg, so I hope that when your system boots whichever interface you pick in netwait_if the one which you default to using. -- | 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"
Re: 7.3-STABLE acpi and mpt problems?
on 18/06/2010 10:06 Lystopad Olexandr said the following: > Hello, John Baldwin! > > On Wed, Jun 16, 2010 at 07:55:27AM -0400 > j...@freebsd.org wrote about "Re: 7.3-STABLE acpi and mpt problems?": >> On Wednesday 16 June 2010 7:14:09 am Lystopad Olexandr wrote: >>> Hi! >>> >>> I have FreeBSD 7.3-STABLE on Biostar 945GC-M4 motherboard. >>> When I boot with custom kernel it fail to boot on ACPI. FreeBSD box >>> do not respond to any key. But it successfully boots with button 2 >>> from boot menu (without acpi). >>> >>> Then I try to boot with GENERIC. Success! Ok, I try comment >>> out one-by-one devices in GENERIC, rebuild and install kernel, >>> and try to boot. My custom kernel boot fine until I comment >>> out mpt device in kernel, but it successfully boots without >>> acpi (button 2 on boot menu). I have no mpt devices in >>> this box. When I insert "device mpt" back to the kernel it boots >>> successfully. >>> >>> Why acpi depends on device mpt? Why this server do not boot without >>> this device? >> How does it fail to boot in the non-mpt case? Does it hang, does it panic? >> If it hangs, can you break into DDB and capture the output of 'ps' and a >> stack >> trace? (A serial console is probably useful for this.) > > John, thank you very much for your answer. > Sorry for delay. > > My freebsd box fails to boot after detecting CPU and memory. It > simply hang. I think this is too early to run ddb or somethig else. > > Also, similar problem with this device I detect on two remote bsd > servers in production. After insert mpt device into kernel, that > servers begin boots fine. Can you please produce _verbose_ dmesg for booting with acpi+mpt and no acpi, no mpt? And also, _verbose_ dmesg of acpi and !mpt. You can capture the latter with serial console. If you don't have it, try to get screenshots. -- 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"
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
On Fri, Jun 18, 2010 at 08:08:24AM +0100, Matthew Lear wrote:
> Hi there,
>
> I'm running 7.2-RELEASE-p4 on an i386 HP server (ML G5) in RAID1
> configuration. Very recently, I've seen IO errors such as:
>
> ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=20472527
>
> reported and the RAID mirror is now offline.
>
> ad0: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=395032335
> ad0: FAILURE - WRITE_DMA48 status=51
> error=10 LBA=395032335
> ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode
>
> Strangely, I've ran some SMART tests on the device and no error has been
> recorded. Health checks pass. Running a long test on the device doesn't
> show any problem. While SMART can be manufacturer specific I at least
> expected to see something which looked to be suspicious.
Could you please provide the full output from "smartctl -a /dev/ad0"
here? Your drive may be completely fine and you may not have to swap it
at all; hard to say.
> The drives in the RAID exist on two seperate ATA channels:
> [r...@meshuga /home/matt]# atacontrol list
> ATA channel 0:
> Master: ad0 SATA revision 2.x
> Slave: ad1 SATA revision 1.x
> ATA channel 1:
> Master: ad2 SATA revision 2.x
> Slave: no device present
> ATA channel 2:
> Master: acd0 SATA revision 1.x
> Slave: no device present
> ATA channel 3:
> Master: no device present
> Slave: no device present
>
> ad1 is a third 160G drive that I periodically back up to using cron.
So your RAID-1 array consists of ad0 and ad2? You didn't provide
"atacontrol status" output so I'm going to assume that's the case.
What's odd to me is that you somehow have two disks on a single ATA
channel -- look closely at channel 0. SATA has a 1:1 device-to-channel
mapping, so I'm a little surprised to see there's two devices on channel
0. To me, this indicates your system BIOS is configured to run in
"Emulation" mode -- where the ATA controller pretends to be a PATA/IDE
controller, thus SATA-0 and SATA-1 devices appear as primary master and
primary slave, respectively.
What motherboard is this? Can you change the setting to either
"Native", "Enhanced", or (even better) "AHCI"? I've seen some systems
where the Serial ATA option in the BIOS has an "Auto" option, which does
totally bizarre things at times.
But before changing the setting, I would recommend dealing with the disk
problem first. Changing the SATA controller operation mode will almost
certainly change all of your device names (you'll have to go into
single-user mode, mount filesystems by hand, fix /etc/fstab, etc.).
Also, can you please provide output from "dmesg | grep -i ata"?
> I've seen the thread below but I'm not using ZFS. This seems similar to
> what I'm experiencing.
> http://freebsd.monkey.org/freebsd-stable/200801/msg00617.html
>
> I'm using software RAID with atacontrol but the drives are not hot-swap.
When you say "software RAID", I'm assuming you're referring to ata(4)'s
native OS-level RAID (as in "atacontrol create RAID1 ad0 ad1"). Or are
you using something like Intel MatrixRAID?
> Therefore I expect that I need to detach ad0 from the RAID, power down
> the unit, replace the drive, power on the unit and rebuild the array in
> order to fix things. Trouble is, I'm struggling to find out if this can
> be done safely with atacontrol and the hw configuration I have, and if
> so, how best to do it?
The atacontrol man page covers your situation:
It is NOT recommended to create such arrays on a primary/secondary pair
on a SINGLE channel since the throughput of the mirror would be severely
compromised, the ability to rebuild the array in the event of a disk
failure would be greatly complicated, and if a disk controller
electronics failed it could wedge the channel and take both disks in the
mirror offline. (which would defeat the purpose of having a mirror in
the first place)
I realise ad0 is on channel 0 and ad2 is on channel 1, but you have a
"mystery device" as a Slave on channel 0, which is going to be impacted.
You really need AHCI to be able to hot-swap effectively. The procedure
I've followed for years -- without ZFS in the picture (that should just
add a few extra commands to the picture) -- relies on AHCI and a proper
hot-swap bay/backplane. Hot-swapping disks without such a backplane,
in my experience, results in the system powering off suddenly. Anyway,
this is the procedure:
- atacontrol detach ataX (where ataX = channel disk is attached to)
- Physically remove the bad disk
- Physically insert a new disk
- Wait 15 seconds for drive to settle
- atacontrol attach ataX
The new disk should appear automatically, and should appear as the same
device name (adX) that it did before. At least that's my experience
when using AHCI with ataahci.ko (I haven't tried when using ahci.ko,
which uses CAM). We can discuss the details/differences later.
If the disk doesn't reappear ("atacontrol list" shows
Re: 7.2-RELEASE-p4, IO errors & RAID1 failure
Hi Matthew, I'm running 7.2-RELEASE-p4 on an i386 HP server (ML G5) in RAID1 configuration. Very recently, I've seen IO errors such as: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=20472527 reported and the RAID mirror is now offline. ad0: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=395032335 ad0: FAILURE - WRITE_DMA48 status=51 error=10 LBA=395032335 ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode I had more or less the same timeout issues on my 8.0-RELEASE box on a Dell R300 with SATA disks. What I did was raise the ata timeout from 5 seconds to 20. I did this by patching the kernel code while running, but I'm not sure you'd like that approach ;) In http://www.freebsd.org/cgi/query-pr.cgi?pr=111023 a patch is presented that raises the timeouts by patching a few ATA kernel source files. This has been committed to RELENG_7 as well, so by upgrading your 7.2-install to the latest RELENG_7 (or RELENG_8), you'll have that timeout fix. Why ATA commands can take longer than 5 seconds although the disks appear to be fine.. wouldn't know .. -- Pieter ___ 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-RELEASE-p4, IO errors & RAID1 failure
Hi there, I'm running 7.2-RELEASE-p4 on an i386 HP server (ML G5) in RAID1 configuration. Very recently, I've seen IO errors such as: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=20472527 reported and the RAID mirror is now offline. ad0: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=395032335 ad0: FAILURE - WRITE_DMA48 status=51 error=10 LBA=395032335 ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode Strangely, I've ran some SMART tests on the device and no error has been recorded. Health checks pass. Running a long test on the device doesn't show any problem. While SMART can be manufacturer specific I at least expected to see something which looked to be suspicious. The drives in the RAID exist on two seperate ATA channels: [r...@meshuga /home/matt]# atacontrol list ATA channel 0: Master: ad0 SATA revision 2.x Slave: ad1 SATA revision 1.x ATA channel 1: Master: ad2 SATA revision 2.x Slave: no device present ATA channel 2: Master: acd0 SATA revision 1.x Slave: no device present ATA channel 3: Master: no device present Slave: no device present ad1 is a third 160G drive that I periodically back up to using cron. I've seen the thread below but I'm not using ZFS. This seems similar to what I'm experiencing. http://freebsd.monkey.org/freebsd-stable/200801/msg00617.html I'm using software RAID with atacontrol but the drives are not hot-swap. Therefore I expect that I need to detach ad0 from the RAID, power down the unit, replace the drive, power on the unit and rebuild the array in order to fix things. Trouble is, I'm struggling to find out if this can be done safely with atacontrol and the hw configuration I have, and if so, how best to do it? It may well be a case of RTFM (again) but I just wanted to run this by the community to get some feedback. Loosing data is not an option here so hopefully I can get the machine back up on its feet soon. Any help or feedback much appreciated. Thanks, -- Matt ___ 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"
network deamons starting before network!
Hello, Since updating to 8.X I noticed that network services were started before the network was up! I use lagg failover configuration on both my FreeBSD boxes. First, boot fails on mounting my nfs-shares. After entering and exiting the "rescue" shell, the system boots as normal. uname -a FreeBSD mario 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #4: Fri Jun 18 07:46:01 CEST 2010 *...@mario:/usr/obj/usr/src/sys/mario amd64 What could I do to fix this? Here's an exerpt from /var/log/messages: Jun 18 09:10:25 ntpd[1376]: ntpd 4.2.4p5-a (1) Jun 18 09:10:25 kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Jun 18 09:10:27 ntpd_initres[1412]: host name not found: yoshi Jun 18 09:10:27 kernel: nfe0: link state changed to UP Jun 18 09:10:27 kernel: lagg0: link state changed to UP Jun 18 09:10:27 kernel: nfe1: link state changed to UP Jun 18 09:10:27 ntpd_initres[1412]: couldn't resolve `yoshi', giving up on it Jun 18 09:10:28 dhclient: New Hostname (lagg0): mario Jun 18 09:10:28 dhclient: New IP Address (lagg0): 10.58.235.6 Jun 18 09:10:28 dhclient: New Subnet Mask (lagg0): 255.255.255.0 Jun 18 09:10:28 dhclient: New Broadcast Address (lagg0): 10.58.235.255 Jun 18 09:10:28 dhclient: New Routers (lagg0): 10.58.235.1 signature.asc Description: OpenPGP digital signature
Re: 7.3-STABLE acpi and mpt problems?
Hello, John Baldwin! On Wed, Jun 16, 2010 at 07:55:27AM -0400 j...@freebsd.org wrote about "Re: 7.3-STABLE acpi and mpt problems?": > On Wednesday 16 June 2010 7:14:09 am Lystopad Olexandr wrote: > > > > Hi! > > > > I have FreeBSD 7.3-STABLE on Biostar 945GC-M4 motherboard. > > When I boot with custom kernel it fail to boot on ACPI. FreeBSD box > > do not respond to any key. But it successfully boots with button 2 > > from boot menu (without acpi). > > > > Then I try to boot with GENERIC. Success! Ok, I try comment > > out one-by-one devices in GENERIC, rebuild and install kernel, > > and try to boot. My custom kernel boot fine until I comment > > out mpt device in kernel, but it successfully boots without > > acpi (button 2 on boot menu). I have no mpt devices in > > this box. When I insert "device mpt" back to the kernel it boots > > successfully. > > > > Why acpi depends on device mpt? Why this server do not boot without > > this device? > > How does it fail to boot in the non-mpt case? Does it hang, does it panic? > If it hangs, can you break into DDB and capture the output of 'ps' and a > stack > trace? (A serial console is probably useful for this.) John, thank you very much for your answer. Sorry for delay. My freebsd box fails to boot after detecting CPU and memory. It simply hang. I think this is too early to run ddb or somethig else. Also, similar problem with this device I detect on two remote bsd servers in production. After insert mpt device into kernel, that servers begin boots fine. -- Olexandr Lystopad ___ 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"
