Unresponsive keyboard after a few boots
Hi, I am using a very recent Freebsd 8.0 STABLE on a Macbook. I updated my sources and rebuilt a kernel about 3 days ago. I was able to use the machine fine once or twice after that. But now the keyboard has stopped working. The boot program is able to use the keyboard, but the kernel isn't, and I am unable to do anything useful with the machine from the login screen. I had rebuilt the kernel twice with slightly varying settings, so I don't have a copy of the previously working kernel in /boot/kernel.old. It may not be easy for me to download a ISO image. Can someone please help? Thanks. ___ 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 probe order issues
Hi Andriy, On 2010-Feb-05 00:40:24 +0200, Andriy Gapon a...@icyb.net.ua wrote: Unfortunately, I don't see any explanation for what you are experiencing. I came up with some things with which you can try to experiment: 1. Boot with hw.pci.usb_early_takeover=0 in loader.conf. 2. Comment out the following line in sys/dev/usb/controller/uhci_pci.c: pci_write_config(self, PCI_LEGSUP, PCI_LEGSUP_USBPIRQDEN, 2); hps@ suggested a ukbd patch as well. Unfortunately, something has come up and I won't be able to check either suggestion until late March. -- Peter Jeremy pgp54yCHzO6zK.pgp Description: PGP signature
Re: hardware for home use large storage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08.02.2010 06:01, Dan Langille wrote: Hi, I'm looking at creating a large home use storage machine. Budget is a concern, but size and reliability are also a priority. Noise is also a concern, since this will be at home, in the basement. That, and cost, pretty much rules out a commercial case, such as a 3U case. It would be nice, but it greatly inflates the budget. This pretty much restricts me to a tower case. The primary use of this machine will be a backup server[1]. It will do other secondary use will include minor tasks such as samba, CIFS, cvsup, etc. I'm thinking of 8x1TB (or larger) SATA drives. I've found a case[2] with hot-swap bays[3], that seems interesting. I haven't looked at power supplies, but given that number of drives, I expect something beefy with a decent reputation is called for. Whether I use hardware or software RAID is undecided. I I think I am leaning towards software RAID, probably ZFS under FreeBSD 8.x but I'm open to hardware RAID but I think the cost won't justify it given ZFS. Given that, what motherboard and RAM configuration would you recommend to work with FreeBSD [and probably ZFS]. The lists seems to indicate that more RAM is better with ZFS. Just before christmas, I rebuilt my own storage backend server for my home, so I've had a recent look at what's there. Some hardware I had from the old solution, and some were new. Some of it is a tad more expensive that what you gave as the idea here, but the logic is (mostly) the same. I'll also include what replacements for some of the old parts I'm looking at. Heirlooms of the old server: - -Disks (four Samsung HD501LJ, Four Seagate ST31500341AS) - -Disk Controller AMI/Lsilogic Megaraid SAS 8308ELP (8chan MFI) The new hardware around this: - -Chieftec UNB-410F-B - -Two Chieftec SST3141SAS - -Chieftec APS-850C (850watt modular power) - -Intel E7500 CPU using the bundled stock cooler, and arcticsilver paste - -4 2GB Corasair Valueram DDR2 1066 sticks - -Asus P5Q Premium mainboard - -LSI SAS3801E (for the tape autoloader) - -Some old graphics board (unless you need a lot of fancy 3D stuff, use what you have around that's not ESD-damaged here). Should I have started from scratch, I'd have used Seagate 2TB Green disks, due to the lower temperatures and powerconsumption of these. And that's about the only thing I'd do differently. The MFI controller (Megaraid) would stay, simply because it has built in logic to periodically do patrolreading and consistency checks, and I've had previous experiences with the raid-controllers checks discovering bad disks before they go critical. But this breed of controllers is a little costly (Customers are willing to pay for the features, so the manufacturer milks them for all they can). I recommend you go for a modular power, that is rated for quite a bit more that what you expect to draw from it. The reason is that as current increases, the efficiency of the conversion drops, so a power running at half its rated max, is more efficient than one pushed to the limits. Go for modular so you don't have to have the extra cables tied into coils inside your machine distruption airflow (and creating EMF noise). Make sure you get yourself a proper ESD wriststrap (or anklestrap) before handling any of these components, and make sure you use correct torque for all the screws handling the components (and disks). This machine will probably have a lot of uptime, and disks (and fans) create vibrations. If in doubt, use some fancy-colored nailpolish (or locktite) on the screws to make sure they don't unscrew from vibrations over time. (a loose screw has a will of it own, and WILL short-circuit the most expensive component in your computer). Also make sure you use cableties to get the cables out of the airflow, so you get sufficient cooling. Speaking of cooling, make sure your air-inputs have some sort of filtering, or you'll learn where Illiad (userfriendly.org) got the idea for Dustpuppy. No matter how pedantic you are about cleaning your house, a computer is basically a large, expensive, vacuum-cleaner and WILL suck in dust from the air. These are some of the pointers I'd like to share on the subject. :) //Svein - -- - +---+--- /\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE -
NFSv4: mount -t nsf4 not the same as mount_newnfs?
Hello. I set up a NFSv4 server located on a FreeBSD 8.0/amd64 box (most recent world). It seems I successfully set up the NFSv4 service and this results in a successful mount of a file system by another FreeBSD 8.0 box. But their is a weirdnes I do not understand. Mounting the filessystem via mount_newnfs host:/path /path works fine, but not mount -t nfs4 host:/path /path. When doing the latter, I always get the error : Operation not supported by device What I'm doing wrong? Regards, Oliver P.S. Kernel has both NFSSERVER and NFSD, NFSCL and NFSCLIENT, /etc/rc.conf has nfsv4_server_enable=YES nfsuserd_enable=YES rpcbind_enable=YES on serverside, on clientside, it's nfsuserd_enable=YES nfscbd_enable=YES ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: hardware for home use large storage
Dan Langille wrote: Hi, I'm looking at creating a large home use storage machine. Budget is a concern, but size and reliability are also a priority. Noise is also a concern, since this will be at home, in the basement. That, and cost, pretty much rules out a commercial case, such as a 3U case. It would be nice, but it greatly inflates the budget. This pretty much restricts me to a tower case. The primary use of this machine will be a backup server[1]. It will do other secondary use will include minor tasks such as samba, CIFS, cvsup, etc. It depends on your needs (storage capacity [number of drives], performance etc.) One year ago I purchased HP ProLiant ML110G5 / P2160 / 1GB / 250GB SATA / DVDRW / Tower / (with 3 years Next Business Day support!). It is sold for about 9000,- CZK ($500), I added next 4GB of RAM, 4x 1TB Samsung F1 instead of original 250GB Seagate. System is booted from 2GB internal USB flash drive and all drives are in RAIDZ pool. The machine is really quiet. All in all cost is about $1000 with 3 years NBD. You can put in 2TB drives instead of 1TB drives. It is really low end machine, but runs without problems for more than a year. 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: hardware for home use large storage
On Mon, Feb 8, 2010 at 11:59 AM, Miroslav Lachman 000.f...@quip.cz wrote: System is booted from 2GB internal USB flash Be aware that not all USB sticks work as a root device on 8.0-RELEASE. I've tried a couple of different sticks that is probed *after* the kernel tries to mount /. It seems to be a problem that emerged with 8.0, as 7.x worked like a charm on the same USB stick. http://www.freebsd.org/cgi/query-pr.cgi?pr=138798 -- chs, ___ 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: Unresponsive keyboard after a few boots
On Mon, Feb 08, 2010 at 02:19:06PM +0530, Rohit Grover wrote: I am using a very recent Freebsd 8.0 STABLE on a Macbook. I updated my sources and rebuilt a kernel about 3 days ago. I was able to use the machine fine once or twice after that. But now the keyboard has stopped working. The boot program is able to use the keyboard, but the kernel isn't, and I am unable to do anything useful with the machine from the login screen. I had rebuilt the kernel twice with slightly varying settings, so I don't have a copy of the previously working kernel in /boot/kernel.old. It may not be easy for me to download a ISO image. Can someone please help? Is the keyboard USB? -- | 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
www/firefox: Firefox 3.6 crashes, Firefox 3.5.7 not
Today, I upgraded Firefox 3.5.7 (built yesterday) to Firefox 3.6. After deleting ~/.mozilla (after I did a buckup, of course), I tried a fresh start of 'firefox3'. After firefox showed up, I realized that no option-field (File, Extras etc) can be used, they are dead and after a few seconds I clicked them, firefox3 is crashing. Since I recompiled firefox 3.5.7 yesterday I was wondering if this is due to some 'false' lib or dependency. Since I figured that I have similar trouble with Thunderbird 3.0.1 after I installed it, I suspect a faulty library causing this behaviour. With Thunderbird 3, I never solved the problem although I tried to rebuild everything with thunderbird via 'portmaster -f'. I'll did this with firefox 3.6 also, but with no success. The crashing is observed on two nearly identical SMP FreeBSD 8.0/amd64 STABLE boxes (make world of today), up-to-date ports. The crash is NOT observed on my private oldish UP box, nearly the same setup, OS at the same revision and ports up to date as of yesterday. Maybe this could be a hint. Any hints or suggestions? Regards, Oliver ___ 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: one more load-cycle-count problem
Any further ideas how to get rid of this feature? You have several options. 1) The most clean solution is probably using the WDIDLE3 utility on your drives to disable automatic parking or in cases where its not possible to complete disable it, you can adjust it to 5 minutes, which essentially solves the problem. Note that going this route will probably involve rebuilding your entire array from scratch, because applying WDIDLE3 to the disk is likely to very slightly affect disk geometry, but just enough for hardware raid or ZFS or whatever to bark at you and refuse to continue using the drive in an existing pool (the affected disk can become very slightly smaller in capacity). Backup data, apply WDIDLE3 to all disks. Recreate the pool, restore backups. This will also void your warranty if used on the new WD drives, although it will still work just fine. 2) A less clean solution would be to setup a script that polls the SMART data of all disks affected by the problem every 8-9 seconds and have this script launch on boot. This will keep the affected drives just busy enough to not park their heads. - Sincerely, Dan Naumov ___ 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: one more load-cycle-count problem
On Mon, 8 Feb 2010 15:43:46 +0200 Dan Naumov dan.nau...@gmail.com wrote about RE: one more load-cycle-count problem: DN Any further ideas how to get rid of this feature? DN 1) The most clean solution is probably using the WDIDLE3 utility on DN your drives to disable automatic parking or in cases where its not DN possible to complete disable it, you can adjust it to 5 minutes, which DN essentially solves the problem. Note that going this route will DN probably involve rebuilding your entire array from scratch, because DN applying WDIDLE3 to the disk is likely to very slightly affect disk DN geometry, but just enough for hardware raid or ZFS or whatever to bark DN at you and refuse to continue using the drive in an existing pool (the DN affected disk can become very slightly smaller in capacity). Backup DN data, apply WDIDLE3 to all disks. Recreate the pool, restore backups. DN This will also void your warranty if used on the new WD drives, DN although it will still work just fine. Thanks for the warning. How on earth can a tool to set the idle time affect the disk geometry?! DN 2) A less clean solution would be to setup a script that polls the DN SMART data of all disks affected by the problem every 8-9 seconds and DN have this script launch on boot. This will keep the affected drives DN just busy enough to not park their heads. That's what I'm doing since yesterday when I first noted the problem on this particular system. Not a pretty solution either. I'm close of buying Hitachi drives instead (HTE545050B9A300). Does anyone here know these drives and can confirm that they do not have this kind of problem (I would expect it because of the 24/7 certification)? cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: one more load-cycle-count problem
2010/2/8 Gerrit Kühn ger...@pmp.uni-hannover.de: On Mon, 8 Feb 2010 15:43:46 +0200 Dan Naumov dan.nau...@gmail.com wrote about RE: one more load-cycle-count problem: DN Any further ideas how to get rid of this feature? DN 1) The most clean solution is probably using the WDIDLE3 utility on DN your drives to disable automatic parking or in cases where its not DN possible to complete disable it, you can adjust it to 5 minutes, which DN essentially solves the problem. Note that going this route will DN probably involve rebuilding your entire array from scratch, because DN applying WDIDLE3 to the disk is likely to very slightly affect disk DN geometry, but just enough for hardware raid or ZFS or whatever to bark DN at you and refuse to continue using the drive in an existing pool (the DN affected disk can become very slightly smaller in capacity). Backup DN data, apply WDIDLE3 to all disks. Recreate the pool, restore backups. DN This will also void your warranty if used on the new WD drives, DN although it will still work just fine. Thanks for the warning. How on earth can a tool to set the idle time affect the disk geometry?! WDIDLE3 changes the drive firmware. This is also how WD can detect you've used it on your disk and void your warranty accordingly :) - Sincerely, Dan Naumov ___ 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: one more load-cycle-count problem
On Mon, Feb 08, 2010 at 03:56:35PM +0200, Dan Naumov wrote: 2010/2/8 Gerrit Kühn ger...@pmp.uni-hannover.de: On Mon, 8 Feb 2010 15:43:46 +0200 Dan Naumov dan.nau...@gmail.com wrote about RE: one more load-cycle-count problem: DN Any further ideas how to get rid of this feature? DN 1) The most clean solution is probably using the WDIDLE3 utility on DN your drives to disable automatic parking or in cases where its not DN possible to complete disable it, you can adjust it to 5 minutes, which DN essentially solves the problem. Note that going this route will DN probably involve rebuilding your entire array from scratch, because DN applying WDIDLE3 to the disk is likely to very slightly affect disk DN geometry, but just enough for hardware raid or ZFS or whatever to bark DN at you and refuse to continue using the drive in an existing pool (the DN affected disk can become very slightly smaller in capacity). Backup DN data, apply WDIDLE3 to all disks. Recreate the pool, restore backups. DN This will also void your warranty if used on the new WD drives, DN although it will still work just fine. Thanks for the warning. How on earth can a tool to set the idle time affect the disk geometry?! WDIDLE3 changes the drive firmware. This is also how WD can detect you've used it on your disk and void your warranty accordingly :) I have to assume WDIDLE3 is identical in implementation/style as WDTLER is -- the firmware itself does not change but rather some tuning settings in an EEPROM on the drive PCB (which may be embedded in the on-PCB I/O controller -- yes this is possible, PIC chips offer this). Last I remember, there *is not* a way to determine if someone has ever adjusted these settings. As long as you set them back to their factory defaults (whatever those values are; the EXEs tell you what they were before they change them), there's no accurate way to determine whether or not the settings had been adjusted since the disk was shipped. The DOS utilities submit custom ATA CMDs or data to all WD disks to toggle or adjust these features. If someone could figure out what the command(s) were, the feature(s) could be implemented into atacontrol(8). Of course, that would require reverse-engineering of the EXEs, which would probably induce DMCA-related lawsuits (in the US). Sad too, since documentation of said feature(s) would improve customer satisfaction. But hey, I'm just an engineer, what do I know. -- | 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
ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
Hi! I'm seeing this problem on my machine at work. It's an HP DC 7800, mounts an ich9 chipset(not ahci capable). I'm attaching the dmesg. I noticed this in the past, but it got evident(and very annoying) while recompiling many ports today after the jpeg-8 update. It looks like it freezes the system for the second or two it takes to flush buffers to disk when there are big outputs. This happens when decompressiong big distfiles, mainly. The openoffice port triggers this almost continuosly every few seconds during compilation. I've also seen this when working with big files(for example graphic images in uncompressed formats). It gets very annoying and I don't remember this happening before activating the ATA_CAM flag. There was some slowdown with big disk access, but not a total freeze. The input I give during the freeze is not lost though, but replayed in a bunch as soon as the system becomes responsive again. BTW there's another thing that shows up on this machine. Lately, this too after putting the option ATA_CAM in the kernel, during boot there is a long pause(exactly one minute, as the message below states) in this point of the dmesg: uhub6: Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus6 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered uhub5: 2 ports with 2 removable, self powered uhub6: 4 ports with 4 removable, self powered uhub3: 6 ports with 6 removable, self powered ugen2.2: Logitech at usbus2 ums0: Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2 on usbus2 ums0: 16 buttons and [XYZ] coordinates ID=0 uhid0: Logitech USB Gaming Mouse, class 0/0, rev 2.00/52.00, addr 2 on usbus2 ugen1.2: vendor 0x0df6 at usbus1 ubt0: vendor 0x0df6 Sitecom USB bluetooth2.0 class 2 dongle CN-512, class 224/1 , rev 2.00/19.58, addr 2 on usbus1 -- 60 seconds pause happens here run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config ada0 at ata0 bus 0 scbus2 target 0 lun 0 ada0: ST3160815AS 3.CHF ATA-7 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO size 8192bytes)cd0 at ata1 bus 0 scbus3 target 0 lun 0 This is not a big problem but quite annoying too. Maybe they're related, maybe not. I don't relly know. Hope these indications help. If needed I could provide more information and test patches. Thanks to the developers for they're great work on FreeBSD. Hope this email helps make it even better! Thanks in advance for any attention to this problem! -- Guido Falsi m...@madpilot.net Copyright (c) 1992-2010 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 8.0-STABLE #38: Mon Feb 8 10:27:55 CET 2010 r...@vwg82.xxx.it:/usr/obj/usr/src/sys/VWG82 amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2327.51-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fb Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 4299161600 (4100 MB) avail memory = 4037332992 (3850 MB) ACPI APIC Table: COMPAQ BEARLAKE FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard netsmb_dev: loaded iscsi: version 2.1.0 kbd1 at kbdmux0 acpi0: HPQOEM SLIC-BPC on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, dff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xf808-0xf80b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0x1230-0x1237 mem 0xf010-0xf017,0xe000-0xefff,0xf000-0xf00f irq 16 at device 2.0 on pci0 agp0: Intel Q35 SVGA controller on vgapci0 agp0: detected 6140k stolen memory agp0: aperture size is 256M drm0: Intel Q35 on vgapci0 info: [drm] MSI enabled 1 message(s) vgapci0: child drm0 requested pci_enable_busmaster info: [drm] AGP at 0xe000 256MB info: [drm] Initialized i915 1.6.0 20080730 pci0: simple comms at device 3.0 (no driver attached) atapci0: Intel ATA controller port 0x1238-0x123f,0x1270-0x1273,0x1240-0x1247,0x1274-0x1277,0x11e0-0x11ef irq 18
Re: one more load-cycle-count problem
On Mon, 8 Feb 2010 15:56:35 +0200 Dan Naumov wrote: WDIDLE3 changes the drive firmware. This is also how WD can detect you've used it on your disk and void your warranty accordingly :) I've upgraded the firmware at five WD1000FYPS disks. One of them still kept on running load cycles. Then I used wdidle3 to disable this feature at this particular disk. Finally that helped. But I don't see any changes at the disk geomentry. It's just the same as before (and other four disks as well). May be not all disks are affected by a geometry change. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
On 02/08/10 15:33, Guido Falsi wrote: It looks like it freezes the system for the second or two it takes to flush buffers to disk when there are big outputs. This happens when decompressiong big distfiles, mainly. The openoffice port triggers this almost continuosly every few seconds during compilation. I've also seen this when working with big files(for example graphic images in uncompressed formats). It gets very annoying and I don't remember this happening before activating the ATA_CAM flag. There was some slowdown with big disk access, but not a total freeze. I think ZFS does this all the time, i.e. regardless of underlying device drivers. Can you test your theory by going to an older kernel and keeping *everything* else the same? ___ 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: NFSv4: mount -t nsf4 not the same as mount_newnfs?
On Mon, 8 Feb 2010, O. Hartmann wrote: Mounting the filessystem via mount_newnfs host:/path /path works fine, but not mount -t nfs4 host:/path /path. The mount command can be either: mount -t nfs -o nfsv4 host:/path /path or mount -t newnfs -o nfsv4 host:/path /path (The above was what the old now removed nfs4 used.) Have fun with it, rick ___ 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.0-RELEASE - -STABLE and size of /
On Friday 05 February 2010 9:00:51 am Oliver Fromme wrote: Randi Harper wrote: Marian Hettwer wrote: +1 vote for making / bigger. At least a size where a make installkernel runs through. This is going to happen. It's been on my to-do list for a while, as I find it increasingly annoying. The default sizes of all mount points need to be tweaked a bit. Be patient, there will be some new changes going into sysinstall very soon. Revisiting sysinstall's default partition sizes is certainly a good idea. However, I think it makes a lot of sense to *not* install symbol files in /boot/kernel by default. I can't think of a good reason why they need to be there by default, and they're what causes the space problems for the root FS in the first place. Please change the default. It makes debugging kernel crashes for simpler and easier. For example, with the kernel symbols installed, the crashinfo(8) script can generate useful information after a crash on an out-of-the-box system. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Recent MFC to 7 causes crash on VMware ESXi
On Saturday 06 February 2010 4:47:16 pm Tom McLaughlin wrote: John Baldwin wrote, On 02/05/2010 08:27 AM: On Thursday 04 February 2010 10:00:55 pm Tom McLaughlin wrote: Hi all, a recent MFC to 7-STABLE has started to cause issues for my VMs on VMware ESXi 3.5u4. After loading the mpt driver for the LSI disk controller the VM just shuts off. The workaround is to change the disk controller to the BusLogic type. Still, it used to work up until last week. The change was made around January 26th and based on the commits that day I'm guessing it's either r203047 or r203073 I have the same issue with both amd64 and i386 VMs. This affects HEAD and 8-STABLE as well and first affected HEAD over the summer. (I just worked around it and went about my business at the time. :-/) I've attached a dmesg from a kernel before the problem and one from after it started. What if you set 'hw.clfush_disable=1' from the loader? Yes, that corrected it on all my VMs. I've talked to people on ESXi 4 and they do not see the problem. I have yet to try 3.5u5 to see if this is a non-issue. 3.5 will be supported for awhile longer from VMware. I'm going to try upgrading the box during the week. I believe folks had to do this on HEAD/8.x as well. Perhaps we can automatically disable clflush if we are executing under VMware or Xen: Index: amd64/amd64/initcpu.c === --- amd64/amd64/initcpu.c (revision 203430) +++ amd64/amd64/initcpu.c (working copy) @@ -177,17 +177,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* -* XXXKIB: (temporary) hack to work around traps generated when -* CLFLUSHing APIC registers window. +* XXXKIB: (temporary) hack to work around traps generated +* when CLFLUSHing APIC registers window under virtualization +* environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by -* hw.clflush_disable tunable. This may help Xen guest on some AMD -* CPUs. +* hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; Index: i386/i386/initcpu.c === --- i386/i386/initcpu.c (revision 203430) +++ i386/i386/initcpu.c (working copy) @@ -724,17 +724,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* -* XXXKIB: (temporary) hack to work around traps generated when -* CLFLUSHing APIC registers window. +* XXXKIB: (temporary) hack to work around traps generated +* when CLFLUSHing APIC registers window under virtualization +* environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by -* hw.clflush_disable tunable. This may help Xen guest on some AMD -* CPUs. +* hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
On Mon, Feb 08, 2010 at 03:33:29PM +0100, Guido Falsi wrote: Hi! I'm seeing this problem on my machine at work. It's an HP DC 7800, mounts an ich9 chipset(not ahci capable). I'm attaching the dmesg. I noticed this in the past, but it got evident(and very annoying) while recompiling many ports today after the jpeg-8 update. It looks like it freezes the system for the second or two it takes to flush buffers to disk when there are big outputs. This happens when decompressiong big distfiles, mainly. The openoffice port triggers this almost continuosly every few seconds during compilation. I've also seen this when working with big files(for example graphic images in uncompressed formats). It gets very annoying and I don't remember this happening before activating the ATA_CAM flag. There was some slowdown with big disk access, but not a total freeze. This happens without ATA_CAM (e.g. using ataahci(4) or any other controller driver). The behaviour you're describing (bursty heavy disk I/O that stalls the subsystem) is pretty much the norm on all FreeBSD systems I've seen with ZFS. When it starts happening, it's easy to notice/follow using zpool iostat 1 or gstat -I500ms. Lots of I/O will happen (read or write) and the ARC is essentially being thrashed -- said utilities won't show any I/O counters incrementing until some threshold is reached, where you'll see a massive amount of I/O reported, during which time the system is sluggish (beyond acceptable levels, IMHO). A few seconds later, the I/O counters start reporting 0 as the ARC gets used, then a few seconds massive I/O, rinse lather repeat. I've seen Solaris 10 systems which behave the same way, and others which don't. I don't know what causes things to start behaving this way. BTW there's another thing that shows up on this machine. Lately, this too after putting the option ATA_CAM in the kernel, during boot there is a long pause(exactly one minute, as the message below states) in this point of the dmesg: This should probably be discussed in a different thread. -- | 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: Recent MFC to 7 causes crash on VMware ESXi
On Mon, Feb 08, 2010 at 09:49:00AM -0500, John Baldwin wrote: On Saturday 06 February 2010 4:47:16 pm Tom McLaughlin wrote: John Baldwin wrote, On 02/05/2010 08:27 AM: On Thursday 04 February 2010 10:00:55 pm Tom McLaughlin wrote: Hi all, a recent MFC to 7-STABLE has started to cause issues for my VMs on VMware ESXi 3.5u4. After loading the mpt driver for the LSI disk controller the VM just shuts off. The workaround is to change the disk controller to the BusLogic type. Still, it used to work up until last week. The change was made around January 26th and based on the commits that day I'm guessing it's either r203047 or r203073 I have the same issue with both amd64 and i386 VMs. This affects HEAD and 8-STABLE as well and first affected HEAD over the summer. (I just worked around it and went about my business at the time. :-/) I've attached a dmesg from a kernel before the problem and one from after it started. What if you set 'hw.clfush_disable=1' from the loader? Yes, that corrected it on all my VMs. I've talked to people on ESXi 4 and they do not see the problem. I have yet to try 3.5u5 to see if this is a non-issue. 3.5 will be supported for awhile longer from VMware. I'm going to try upgrading the box during the week. I believe folks had to do this on HEAD/8.x as well. Perhaps we can automatically disable clflush if we are executing under VMware or Xen: Index: amd64/amd64/initcpu.c === --- amd64/amd64/initcpu.c (revision 203430) +++ amd64/amd64/initcpu.c (working copy) @@ -177,17 +177,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* - * XXXKIB: (temporary) hack to work around traps generated when - * CLFLUSHing APIC registers window. + * XXXKIB: (temporary) hack to work around traps generated + * when CLFLUSHing APIC registers window under virtualization + * environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by - * hw.clflush_disable tunable. This may help Xen guest on some AMD - * CPUs. + * hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; Index: i386/i386/initcpu.c === --- i386/i386/initcpu.c (revision 203430) +++ i386/i386/initcpu.c (working copy) @@ -724,17 +724,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* - * XXXKIB: (temporary) hack to work around traps generated when - * CLFLUSHing APIC registers window. + * XXXKIB: (temporary) hack to work around traps generated + * when CLFLUSHing APIC registers window under virtualization + * environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by - * hw.clflush_disable tunable. This may help Xen guest on some AMD - * CPUs. + * hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; It might be better to or old condition, i.e. Intel without SS, and new one, vm_guest != 0, instead of replacing the old ? pgpMEtc2k6I8b.pgp Description: PGP signature
Re: NFSv4: mount -t nsf4 not the same as mount_newnfs?
On Mon, 8 Feb 2010, O. Hartmann wrote: Mounting the filessystem via mount_newnfs host:/path /path Oh, and you should set: sysctl vfs.newnfs.locallocks_enable=0 in the server, since I haven't fixed the local locking yet. (This implies that apps/daemons running locally on the server won't see byte range locks performed by NFSv4 clients.) However, byte range locking between NFSv4 clients should work ok. rick ___ 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: one more load-cycle-count problem
On Mon, 8 Feb 2010 06:22:59 -0800 Jeremy Chadwick free...@jdc.parodius.com wrote about Re: one more load-cycle-count problem: JC The DOS utilities submit custom ATA CMDs or data to all WD disks to JC toggle or adjust these features. If someone could figure out what the JC command(s) were, the feature(s) could be implemented into atacontrol JC (8). Of course, that would require reverse-engineering of the EXEs, JC which would probably induce DMCA-related lawsuits (in the US). Sad JC too, since documentation of said feature(s) would improve customer JC satisfaction. But hey, I'm just an engineer, what do I know. :-))) I would really prefer to be able to set this stuff via camcontrol or atacontrol. Alone having to boot DOS with this machine (no floppy, no cdrom) will be a real pain. And most probably the DOS tool will not be able to see the disks sitting behind my lsi-driven controller anyway, so I have to plug them elsewhere, too. Great job, WD. :-( cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Recent MFC to 7 causes crash on VMware ESXi
On Monday 08 February 2010 9:56:36 am Kostik Belousov wrote: On Mon, Feb 08, 2010 at 09:49:00AM -0500, John Baldwin wrote: On Saturday 06 February 2010 4:47:16 pm Tom McLaughlin wrote: John Baldwin wrote, On 02/05/2010 08:27 AM: On Thursday 04 February 2010 10:00:55 pm Tom McLaughlin wrote: Hi all, a recent MFC to 7-STABLE has started to cause issues for my VMs on VMware ESXi 3.5u4. After loading the mpt driver for the LSI disk controller the VM just shuts off. The workaround is to change the disk controller to the BusLogic type. Still, it used to work up until last week. The change was made around January 26th and based on the commits that day I'm guessing it's either r203047 or r203073 I have the same issue with both amd64 and i386 VMs. This affects HEAD and 8-STABLE as well and first affected HEAD over the summer. (I just worked around it and went about my business at the time. :-/) I've attached a dmesg from a kernel before the problem and one from after it started. What if you set 'hw.clfush_disable=1' from the loader? Yes, that corrected it on all my VMs. I've talked to people on ESXi 4 and they do not see the problem. I have yet to try 3.5u5 to see if this is a non-issue. 3.5 will be supported for awhile longer from VMware. I'm going to try upgrading the box during the week. I believe folks had to do this on HEAD/8.x as well. Perhaps we can automatically disable clflush if we are executing under VMware or Xen: Index: amd64/amd64/initcpu.c === --- amd64/amd64/initcpu.c (revision 203430) +++ amd64/amd64/initcpu.c (working copy) @@ -177,17 +177,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* -* XXXKIB: (temporary) hack to work around traps generated when -* CLFLUSHing APIC registers window. +* XXXKIB: (temporary) hack to work around traps generated +* when CLFLUSHing APIC registers window under virtualization +* environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by -* hw.clflush_disable tunable. This may help Xen guest on some AMD -* CPUs. +* hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; Index: i386/i386/initcpu.c === --- i386/i386/initcpu.c (revision 203430) +++ i386/i386/initcpu.c (working copy) @@ -724,17 +724,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* -* XXXKIB: (temporary) hack to work around traps generated when -* CLFLUSHing APIC registers window. +* XXXKIB: (temporary) hack to work around traps generated +* when CLFLUSHing APIC registers window under virtualization +* environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by -* hw.clflush_disable tunable. This may help Xen guest on some AMD -* CPUs. +* hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; It might be better to or old condition, i.e. Intel without SS, and new one, vm_guest != 0, instead of replacing the old ? I thought the old condition only happened under VMware? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Recent MFC to 7 causes crash on VMware ESXi
On Mon, Feb 08, 2010 at 10:32:37AM -0500, John Baldwin wrote: On Monday 08 February 2010 9:56:36 am Kostik Belousov wrote: On Mon, Feb 08, 2010 at 09:49:00AM -0500, John Baldwin wrote: On Saturday 06 February 2010 4:47:16 pm Tom McLaughlin wrote: John Baldwin wrote, On 02/05/2010 08:27 AM: On Thursday 04 February 2010 10:00:55 pm Tom McLaughlin wrote: Hi all, a recent MFC to 7-STABLE has started to cause issues for my VMs on VMware ESXi 3.5u4. After loading the mpt driver for the LSI disk controller the VM just shuts off. The workaround is to change the disk controller to the BusLogic type. Still, it used to work up until last week. The change was made around January 26th and based on the commits that day I'm guessing it's either r203047 or r203073 I have the same issue with both amd64 and i386 VMs. This affects HEAD and 8-STABLE as well and first affected HEAD over the summer. (I just worked around it and went about my business at the time. :-/) I've attached a dmesg from a kernel before the problem and one from after it started. What if you set 'hw.clfush_disable=1' from the loader? Yes, that corrected it on all my VMs. I've talked to people on ESXi 4 and they do not see the problem. I have yet to try 3.5u5 to see if this is a non-issue. 3.5 will be supported for awhile longer from VMware. I'm going to try upgrading the box during the week. I believe folks had to do this on HEAD/8.x as well. Perhaps we can automatically disable clflush if we are executing under VMware or Xen: Index: amd64/amd64/initcpu.c === --- amd64/amd64/initcpu.c (revision 203430) +++ amd64/amd64/initcpu.c (working copy) @@ -177,17 +177,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* - * XXXKIB: (temporary) hack to work around traps generated when - * CLFLUSHing APIC registers window. + * XXXKIB: (temporary) hack to work around traps generated + * when CLFLUSHing APIC registers window under virtualization + * environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by - * hw.clflush_disable tunable. This may help Xen guest on some AMD - * CPUs. + * hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; Index: i386/i386/initcpu.c === --- i386/i386/initcpu.c (revision 203430) +++ i386/i386/initcpu.c (working copy) @@ -724,17 +724,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* - * XXXKIB: (temporary) hack to work around traps generated when - * CLFLUSHing APIC registers window. + * XXXKIB: (temporary) hack to work around traps generated + * when CLFLUSHing APIC registers window under virtualization + * environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by - * hw.clflush_disable tunable. This may help Xen guest on some AMD - * CPUs. + * hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; It might be better to or old condition, i.e. Intel without SS, and new one, vm_guest != 0, instead of replacing the old ? I thought the old condition only happened under VMware? Reports I got where from XEN. pgp30aW6Aap4E.pgp Description: PGP signature
Re: ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
On Mon, Feb 08, 2010 at 03:41:14PM +0100, Ivan Voras wrote: On 02/08/10 15:33, Guido Falsi wrote: It looks like it freezes the system for the second or two it takes to flush buffers to disk when there are big outputs. This happens when decompressiong big distfiles, mainly. The openoffice port triggers this almost continuosly every few seconds during compilation. I've also seen this when working with big files(for example graphic images in uncompressed formats). It gets very annoying and I don't remember this happening before activating the ATA_CAM flag. There was some slowdown with big disk access, but not a total freeze. I think ZFS does this all the time, i.e. regardless of underlying device drivers. Can you test your theory by going to an older kernel and keeping *everything* else the same? I have made the test and in fact I see the same freezes without ATA_CAM and the legacy ata system. Maybe my idea was due to selective memory :) The other problem at boot still exists with ATA_CAM and does not without it. I'll create a new thread about this as suggested by Jeremy Chadwick. -- Guido Falsi m...@madpilot.net ___ 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: ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
On Mon, Feb 08, 2010 at 06:51:47AM -0800, Jeremy Chadwick wrote: On Mon, Feb 08, 2010 at 03:33:29PM +0100, Guido Falsi wrote: It gets very annoying and I don't remember this happening before activating the ATA_CAM flag. There was some slowdown with big disk access, but not a total freeze. This happens without ATA_CAM (e.g. using ataahci(4) or any other controller driver). The behaviour you're describing (bursty heavy disk I/O that stalls the subsystem) is pretty much the norm on all FreeBSD systems I've seen with ZFS. When it starts happening, it's easy to notice/follow using zpool iostat 1 or gstat -I500ms. Lots of I/O will happen (read or write) and the ARC is essentially being thrashed -- said utilities won't show any I/O counters incrementing until some threshold is reached, where you'll see a massive amount of I/O reported, during which time the system is sluggish (beyond acceptable levels, IMHO). A few seconds later, the I/O counters start reporting 0 as the ARC gets used, then a few seconds massive I/O, rinse lather repeat. I've seen Solaris 10 systems which behave the same way, and others which don't. I don't know what causes things to start behaving this way. Thank you for the explanation. I in fact see the same problem with the legacy ata driver. I see this is something not trivial to fix, so I don't want to put too much burden on the pople who brought us zfs, which is anyway a great thing! Anyway the sluggish responsiveness of the system during these bursts is a problem for desktop use. I see that ZFS is mainly a server oriented FS, but this should be addressed sometime in the future I think. BTW there's another thing that shows up on this machine. Lately, this too after putting the option ATA_CAM in the kernel, during boot there is a long pause(exactly one minute, as the message below states) in this point of the dmesg: This should probably be discussed in a different thread. I'll follow your suggestion and post a new thread about this. Thank you again! -- Guido Falsi m...@madpilot.net ___ 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: www/firefox: Firefox 3.6 crashes, Firefox 3.5.7 not
On Mon, 08 Feb 2010 13:32:25 + O. Hartmann ohart...@zedat.fu-berlin.de wrote: Today, I upgraded Firefox 3.5.7 (built yesterday) to Firefox 3.6. After deleting ~/.mozilla (after I did a buckup, of course), I tried a fresh start of 'firefox3'. After firefox showed up, I realized that no option-field (File, Extras etc) can be used, they are dead and after a few seconds I clicked them, firefox3 is crashing. Since I recompiled firefox 3.5.7 yesterday I was wondering if this is due to some 'false' lib or dependency. Since I figured that I have similar trouble with Thunderbird 3.0.1 after I installed it, I suspect a faulty library causing this behaviour. With Thunderbird 3, I never solved the problem although I tried to rebuild everything with thunderbird via 'portmaster -f'. I'll did this with firefox 3.6 also, but with no success. The crashing is observed on two nearly identical SMP FreeBSD 8.0/amd64 STABLE boxes (make world of today), up-to-date ports. The crash is NOT observed on my private oldish UP box, nearly the same setup, OS at the same revision and ports up to date as of yesterday. Maybe this could be a hint. Any hints or suggestions? Try doing ldd /usr/local/lib/firefox3/firefox-bin and see if anything looks weird. You can porbably ignore /usr/local/lib/firefox3/firefox-bin: libxul.so = not found (0x0) libmozjs.so = not found (0x0) libxpcom.so = not found (0x0) because run-mozilla.sh sets LD_LIBRARY_PATH to include /usr/local/lib/firefox3 where these libraries are installed. I merely deleted my old firefox 3.6 and reinstalled from the port (on 9-CURRENT AMD64) and haven't seen any problems. But of course, I've been running various incarnations of 3.6 for a while and may have gotten all the dependencies already correctly installed. --- Gary Jennejohn ___ 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: ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
Jeremy Chadwick free...@jdc.parodius.com wrote: On Mon, Feb 08, 2010 at 03:33:29PM +0100, Guido Falsi wrote: I'm seeing this problem on my machine at work. It's an HP DC 7800, mounts an ich9 chipset(not ahci capable). I'm attaching the dmesg. I noticed this in the past, but it got evident(and very annoying) while recompiling many ports today after the jpeg-8 update. It looks like it freezes the system for the second or two it takes to flush buffers to disk when there are big outputs. This happens when decompressiong big distfiles, mainly. The openoffice port triggers this almost continuosly every few seconds during compilation. I've also seen this when working with big files(for example graphic images in uncompressed formats). It gets very annoying and I don't remember this happening before activating the ATA_CAM flag. There was some slowdown with big disk access, but not a total freeze. This happens without ATA_CAM (e.g. using ataahci(4) or any other controller driver). Indeed. The behaviour you're describing (bursty heavy disk I/O that stalls the subsystem) is pretty much the norm on all FreeBSD systems I've seen with ZFS. When it starts happening, it's easy to notice/follow using zpool iostat 1 or gstat -I500ms. Lots of I/O will happen (read or write) and the ARC is essentially being thrashed -- said utilities won't show any I/O counters incrementing until some threshold is reached, where you'll see a massive amount of I/O reported, during which time the system is sluggish (beyond acceptable levels, IMHO). A few seconds later, the I/O counters start reporting 0 as the ARC gets used, then a few seconds massive I/O, rinse lather repeat. I experienced what I think is the same problem. ZFS's bulk disk flushes caused vlc to occasionally stutter when viewing a DVD rip from disk while ripping a DVD at the same time. My workaround is to put vfs.zfs.txg.timeout=3 in /boot/loader.conf. I think I read about this on zfs-disc...@. I assume on faster systems one can use a higher value. I'm currently updating the jpeg dependencies, too: f...@r500 ~ $zpool iostat 1 capacity operationsbandwidth pool used avail read write read write -- - - - - - - tank 176G 52.1G 22 40 1.40M 1.85M tank 176G 52.1G 73 0 9.24M 0 tank 176G 52.1G 73 0 9.05M 0 tank 176G 52.1G 42176 5.12M 11.3M tank 176G 52.1G 68 0 8.62M 0 tank 176G 52.1G 67 0 8.43M 0 tank 176G 52.1G 57106 7.11M 9.54M tank 176G 52.1G 75 0 9.50M 0 tank 176G 52.1G 76 0 9.62M 0 tank 176G 52.1G 46167 5.74M 11.7M tank 176G 52.1G 79 0 9.99M 0 tank 176G 52.1G 81 0 10.2M 0 tank 176G 52.1G 43164 5.43M 11.7M tank 176G 52.1G 71 0 9.00M 0 tank 176G 52.1G 61 39 7.74M 5.00M tank 176G 52.1G 46111 5.74M 9.17M tank 176G 52.1G 71 0 8.99M 0 tank 176G 52.1G 80 0 10.1M 0 tank 176G 52.1G 47113 5.87M 9.68M tank 176G 52.1G 70 0 8.87M 0 tank 176G 52.1G 78 0 9.80M 0 tank 176G 52.1G 42164 5.24M 11.3M tank 176G 52.1G 76 0 9.62M 0 tank 176G 52.1G 79 0 9.99M 0 tank 176G 52.1G 49153 6.11M 10.8M tank 176G 52.1G 72 0 9.12M 0 Fabian signature.asc Description: PGP signature
ATA_CAM run_interrupt_driven_hooks waiting for xpt_config
Hi, I'm opening this new thread about this strange problem on boot that I have. I'm attaching 2 dmesg. One without ATA_CAM and one with. Botting with ATA__CAM on this machine creates a 60 second pause in the kernel boot just after the line: ubt0: vendor 0x0df6 Sitecom USB bluetooth2.0 class 2 dongle CN-512, class 224/1, rev 2.00/19.58, addr 2 on usbus1 After sixty seconds the following message appears: run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config a few moments later the boot process goes on as usual. The machine is an HP DC7800 PC, with an ich7 southbridge not ahci capable. I've also seen this same problem on an HP Proliant 150G6 desktop server. I am available to provide any further details if needed. Thanks for any answer and time spent on this problem! -- Guido Falsi m...@madpilot.net Copyright (c) 1992-2010 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 8.0-STABLE #39: Mon Feb 8 15:59:14 CET 2010 r...@vwg82.xxx.it:/usr/obj/usr/src/sys/VWG82 amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2327.51-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fb Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 4299161600 (4100 MB) avail memory = 4037160960 (3850 MB) ACPI APIC Table: COMPAQ BEARLAKE FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard netsmb_dev: loaded iscsi: version 2.1.0 kbd1 at kbdmux0 acpi0: HPQOEM SLIC-BPC on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, dff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xf808-0xf80b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0x1230-0x1237 mem 0xf010-0xf017,0xe000-0xefff,0xf000-0xf00f irq 16 at device 2.0 on pci0 agp0: Intel Q35 SVGA controller on vgapci0 agp0: detected 6140k stolen memory agp0: aperture size is 256M drm0: Intel Q35 on vgapci0 info: [drm] MSI enabled 1 message(s) vgapci0: child drm0 requested pci_enable_busmaster info: [drm] AGP at 0xe000 256MB info: [drm] Initialized i915 1.6.0 20080730 pci0: simple comms at device 3.0 (no driver attached) atapci0: Intel ATA controller port 0x1238-0x123f,0x1270-0x1273,0x1240-0x1247,0x1274-0x1277,0x11e0-0x11ef irq 18 at device 3.2 on pci0 atapci0: [ITHREAD] ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] pci0: simple comms, UART at device 3.3 (no driver attached) em0: Intel(R) PRO/1000 Network Connection 6.9.14 port 0x1100-0x111f mem 0xf018-0xf019,0xf01a5000-0xf01a5fff irq 19 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1e:0b:ab:e6:a7 uhci0: Intel 82801I (ICH9) USB controller port 0x1120-0x113f irq 20 at device 26.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801I (ICH9) USB controller on uhci0 uhci1: Intel 82801I (ICH9) USB controller port 0x1140-0x115f irq 21 at device 26.1 on pci0 uhci1: [ITHREAD] usbus1: Intel 82801I (ICH9) USB controller on uhci1 uhci2: Intel 82801I (ICH9) USB controller port 0x1160-0x117f irq 22 at device 26.2 on pci0 uhci2: [ITHREAD] usbus2: Intel 82801I (ICH9) USB controller on uhci2 ehci0: Intel 82801I (ICH9) USB 2.0 controller mem 0xf01a6000-0xf01a63ff irq 22 at device 26.7 on pci0 ehci0: [ITHREAD] usbus3: EHCI version 1.0 usbus3: Intel 82801I (ICH9) USB 2.0 controller on ehci0 hdac0: Intel 82801I High Definition Audio Controller mem 0xf01a-0xf01a3fff irq 21 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20100122_0141 hdac0: [ITHREAD] pcib1: ACPI PCI-PCI bridge at device 28.0 on pci0 pci32: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 21 at device 28.1 on pci0 pci48: ACPI PCI bus on pcib2 uhci3: Intel 82801I (ICH9) USB controller port 0x1180-0x119f irq 20 at device 29.0 on pci0 uhci3: [ITHREAD] usbus4: Intel 82801I (ICH9) USB controller on uhci3 uhci4: Intel 82801I (ICH9) USB controller port 0x11a0-0x11bf irq 21 at device 29.1 on pci0 uhci4: [ITHREAD] usbus5: Intel 82801I (ICH9) USB controller on uhci4 ehci1: Intel 82801I (ICH9) USB 2.0
Re: ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
On Mon, Feb 08, 2010 at 05:18:22PM +0100, Fabian Keil wrote: I experienced what I think is the same problem. ZFS's bulk disk flushes caused vlc to occasionally stutter when viewing a DVD rip from disk while ripping a DVD at the same time. My workaround is to put vfs.zfs.txg.timeout=3 in /boot/loader.conf. I think I read about this on zfs-disc...@. I assume on faster systems one can use a higher value. This was a very good idea. I'm trying this and the system freezes much less if at all. Are there any drawbacks I should be aware of? I can imagine that forcing more disk writes somewhat slows down normal disk activity, but I can bear that on a desktop system. -- Guido Falsi m...@madpilot.net ___ 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: NFSv4: mount -t nsf4 not the same as mount_newnfs?
On 02/08/10 15:08, Rick Macklem wrote: On Mon, 8 Feb 2010, O. Hartmann wrote: Mounting the filessystem via mount_newnfs host:/path /path Oh, and you should set: sysctl vfs.newnfs.locallocks_enable=0 in the server, since I haven't fixed the local locking yet. (This implies that apps/daemons running locally on the server won't see byte range locks performed by NFSv4 clients.) However, byte range locking between NFSv4 clients should work ok. rick ___ 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 Interesting, I see a lot of vfs.newfs-stuff on server-side, but not this specific OID. Do I miss something here? Regards, Oliver ___ 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: NFSv4: mount -t nsf4 not the same as mount_newnfs?
On 02/08/10 15:01, Rick Macklem wrote: On Mon, 8 Feb 2010, O. Hartmann wrote: Mounting the filessystem via mount_newnfs host:/path /path works fine, but not mount -t nfs4 host:/path /path. The mount command can be either: mount -t nfs -o nfsv4 host:/path /path or mount -t newnfs -o nfsv4 host:/path /path (The above was what the old now removed nfs4 used.) Have fun with it, rick So I guess the above one is the more 'transparent' one with respect to the future, when NFSv4 gets mature and its way as matured into the kernel? I tried the above and it works. But it seems, that only UFS2 filesystems can be mounted by the client. When trying mounting a filesystem residing on ZFS, it fails. Mounting works, but when try to access or doing a simple 'ls', I get ls: /backup: Permission denied On server side, /etc/exports looks like -- V4: / -sec=sys:krb5 #IPv4# /backup #IPv4# -- Is there still an issue with ZFS? Regards, Oliver ___ 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: Kerberized NFSv3 incorrect behavior
On 08/02/2010 00:34, Rick Macklem wrote: On Sat, 6 Feb 2010, George Mamalakis wrote: thank you for all your answers. I am planning on setting up the computer labs of my department using kerberized nfsv3 (since v4 seems to be more experimental) with a FreeBSD nfs server and Linux nfs clients. I was wondering how stable such an implementation would be; meaning that I wouldn't want to end up with an unstsable setup when receiving requests from 50-60 simultaneous clients, because that would be my everyday scenario. I believe that the above should be stable, but your mileage may vary, as they say. The main issue will be what your TGT lifetime will be, since client access to the server will normally stop when the TGT expires. Some systems (Mac OS X) will automagically renew the TGT before it expires, if your KDC allows that. I don't think most/all Linux systems do this by default, but there are some utilities out there (try a search for krenew) that will do so. I think that this I can be overcome with a default timeout option in my shell variables (at least for the 'pilot phase'). Basically, I think you'll want to avoid TGTs expiring before the user logs out. You also need a unique uid-user principal mapping for all users logging in. I am planning on using LDAP as my backend with kerberos attributes (I have already setup my ldap like that). To be honest, I have done something funny. My heimdal's backend is openldap; this LDAP is only for heimdal access (inside a jail). Then, I have another jail which serves its openldap instance to all my clients. This ldap (which stores a totally different DIT then heimdal's LDAP) is kerberized (it uses gssapi authentication via cyrus-sasl), using the heimdal jail. It's a bit dramatic, but it seems to work fine-until now-, it seems quite secure, and allows me to synchronize the heimdal backend easily through openldap replication. Moreover, keeping the user credentials in ldap helps for having a generic user/password store for other services I use (like samba, (for my windows hosts)). So, I use a different ldap attribute for samba-semantics and another ldap attribute for kerberos. Lastly, openldap caters for storing uids,gids,home_folder_locations,etc for my users, where my clients have access to this information via their respective nsswitch.conf files. I think that this answers your question regarding uid-user principal mapping, unless I misunderstood something. You definitely want to do some testing with whatever Linux system you are using for the client. Good luck with it, rick ps: Choosing nfsv3 vs nfsv4 is basically independent of using RPCSEC_GSS except for the host based initiator credential needed by some clients (Linux and Solaris10 are among those) for NFSv4. To tell you the truth, when I recompiled my kernel with: options NFSD options KGSSAPI device crypto to setup an nvsv4 server, nfsd refused to start because mountd was segfaulting. I didn't play much with this setup, because I was in a hurry, so I commented out NFSD and put back NFSSERVER, to be able to test my server. Now a last question: Does gssapi/nfs setup work with the automounter (bsd/linux nfs-client)? Thanx again for your answer. -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 ___ 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: Recent MFC to 7 causes crash on VMware ESXi
On Monday 08 February 2010 11:06:00 am Kostik Belousov wrote: On Mon, Feb 08, 2010 at 10:32:37AM -0500, John Baldwin wrote: On Monday 08 February 2010 9:56:36 am Kostik Belousov wrote: On Mon, Feb 08, 2010 at 09:49:00AM -0500, John Baldwin wrote: On Saturday 06 February 2010 4:47:16 pm Tom McLaughlin wrote: John Baldwin wrote, On 02/05/2010 08:27 AM: On Thursday 04 February 2010 10:00:55 pm Tom McLaughlin wrote: Hi all, a recent MFC to 7-STABLE has started to cause issues for my VMs on VMware ESXi 3.5u4. After loading the mpt driver for the LSI disk controller the VM just shuts off. The workaround is to change the disk controller to the BusLogic type. Still, it used to work up until last week. The change was made around January 26th and based on the commits that day I'm guessing it's either r203047 or r203073 I have the same issue with both amd64 and i386 VMs. This affects HEAD and 8-STABLE as well and first affected HEAD over the summer. (I just worked around it and went about my business at the time. :-/) I've attached a dmesg from a kernel before the problem and one from after it started. What if you set 'hw.clfush_disable=1' from the loader? Yes, that corrected it on all my VMs. I've talked to people on ESXi 4 and they do not see the problem. I have yet to try 3.5u5 to see if this is a non-issue. 3.5 will be supported for awhile longer from VMware. I'm going to try upgrading the box during the week. I believe folks had to do this on HEAD/8.x as well. Perhaps we can automatically disable clflush if we are executing under VMware or Xen: Index: amd64/amd64/initcpu.c === --- amd64/amd64/initcpu.c (revision 203430) +++ amd64/amd64/initcpu.c (working copy) @@ -177,17 +177,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* -* XXXKIB: (temporary) hack to work around traps generated when -* CLFLUSHing APIC registers window. +* XXXKIB: (temporary) hack to work around traps generated +* when CLFLUSHing APIC registers window under virtualization +* environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by -* hw.clflush_disable tunable. This may help Xen guest on some AMD -* CPUs. +* hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; Index: i386/i386/initcpu.c === --- i386/i386/initcpu.c (revision 203430) +++ i386/i386/initcpu.c (working copy) @@ -724,17 +724,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* -* XXXKIB: (temporary) hack to work around traps generated when -* CLFLUSHing APIC registers window. +* XXXKIB: (temporary) hack to work around traps generated +* when CLFLUSHing APIC registers window under virtualization +* environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by -* hw.clflush_disable tunable. This may help Xen guest on some AMD -* CPUs. +* hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; It might be better to or old condition, i.e. Intel without SS, and new one, vm_guest != 0, instead of replacing the old ? I thought the old condition only happened under VMware? Reports I got where from XEN. Ok. Those would also be covered under the vm_guest test as it is non-zero for Xen, VMware, Parallels, etc. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Recent MFC to 7 causes crash on VMware ESXi
On Mon, Feb 08, 2010 at 01:15:06PM -0500, John Baldwin wrote: On Monday 08 February 2010 11:06:00 am Kostik Belousov wrote: On Mon, Feb 08, 2010 at 10:32:37AM -0500, John Baldwin wrote: On Monday 08 February 2010 9:56:36 am Kostik Belousov wrote: On Mon, Feb 08, 2010 at 09:49:00AM -0500, John Baldwin wrote: On Saturday 06 February 2010 4:47:16 pm Tom McLaughlin wrote: John Baldwin wrote, On 02/05/2010 08:27 AM: On Thursday 04 February 2010 10:00:55 pm Tom McLaughlin wrote: Hi all, a recent MFC to 7-STABLE has started to cause issues for my VMs on VMware ESXi 3.5u4. After loading the mpt driver for the LSI disk controller the VM just shuts off. The workaround is to change the disk controller to the BusLogic type. Still, it used to work up until last week. The change was made around January 26th and based on the commits that day I'm guessing it's either r203047 or r203073 I have the same issue with both amd64 and i386 VMs. This affects HEAD and 8-STABLE as well and first affected HEAD over the summer. (I just worked around it and went about my business at the time. :-/) I've attached a dmesg from a kernel before the problem and one from after it started. What if you set 'hw.clfush_disable=1' from the loader? Yes, that corrected it on all my VMs. I've talked to people on ESXi 4 and they do not see the problem. I have yet to try 3.5u5 to see if this is a non-issue. 3.5 will be supported for awhile longer from VMware. I'm going to try upgrading the box during the week. I believe folks had to do this on HEAD/8.x as well. Perhaps we can automatically disable clflush if we are executing under VMware or Xen: Index: amd64/amd64/initcpu.c === --- amd64/amd64/initcpu.c (revision 203430) +++ amd64/amd64/initcpu.c (working copy) @@ -177,17 +177,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* - * XXXKIB: (temporary) hack to work around traps generated when - * CLFLUSHing APIC registers window. + * XXXKIB: (temporary) hack to work around traps generated + * when CLFLUSHing APIC registers window under virtualization + * environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by - * hw.clflush_disable tunable. This may help Xen guest on some AMD - * CPUs. + * hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; Index: i386/i386/initcpu.c === --- i386/i386/initcpu.c (revision 203430) +++ i386/i386/initcpu.c (working copy) @@ -724,17 +724,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* - * XXXKIB: (temporary) hack to work around traps generated when - * CLFLUSHing APIC registers window. + * XXXKIB: (temporary) hack to work around traps generated + * when CLFLUSHing APIC registers window under virtualization + * environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by - * hw.clflush_disable tunable. This may help Xen guest on some AMD - * CPUs. + * hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; It might be better to or old condition, i.e. Intel without SS, and new one, vm_guest != 0, instead of replacing the old ? I thought the old condition only happened under VMware? Reports I got where from XEN. Ok. Those would also be covered under the vm_guest test as it is non-zero for Xen, VMware, Parallels, etc. What I said was suggestion and not objection. Ignore me. pgpA8H8gTuFSM.pgp Description: PGP signature
Re: www/firefox: Firefox 3.6 crashes, Firefox 3.5.7 not
On 02/08/10 16:20, Gary Jennejohn wrote: On Mon, 08 Feb 2010 13:32:25 + O. Hartmannohart...@zedat.fu-berlin.de wrote: Today, I upgraded Firefox 3.5.7 (built yesterday) to Firefox 3.6. After deleting ~/.mozilla (after I did a buckup, of course), I tried a fresh start of 'firefox3'. After firefox showed up, I realized that no option-field (File, Extras etc) can be used, they are dead and after a few seconds I clicked them, firefox3 is crashing. Since I recompiled firefox 3.5.7 yesterday I was wondering if this is due to some 'false' lib or dependency. Since I figured that I have similar trouble with Thunderbird 3.0.1 after I installed it, I suspect a faulty library causing this behaviour. With Thunderbird 3, I never solved the problem although I tried to rebuild everything with thunderbird via 'portmaster -f'. I'll did this with firefox 3.6 also, but with no success. The crashing is observed on two nearly identical SMP FreeBSD 8.0/amd64 STABLE boxes (make world of today), up-to-date ports. The crash is NOT observed on my private oldish UP box, nearly the same setup, OS at the same revision and ports up to date as of yesterday. Maybe this could be a hint. Any hints or suggestions? Try doing ldd /usr/local/lib/firefox3/firefox-bin and see if anything looks weird. I did - and there is nothing weird. I checked the installed libraries and they are all rebuild when rebuilding necessary dependencies for firefox3. You can porbably ignore /usr/local/lib/firefox3/firefox-bin: libxul.so = not found (0x0) libmozjs.so = not found (0x0) libxpcom.so = not found (0x0) because run-mozilla.sh sets LD_LIBRARY_PATH to include /usr/local/lib/firefox3 where these libraries are installed. I merely deleted my old firefox 3.6 and reinstalled from the port (on 9-CURRENT AMD64) and haven't seen any problems. But of course, I've been running various incarnations of 3.6 for a while and may have gotten all the dependencies already correctly installed. --- Gary Jennejohn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I tried again, left the 'make config'-options as they were set by default, delete/backuped .mozilla in my home and they restartet firefox3. Nothing better than previously seen. Try hitting Button 'Tools' at the top menu bar gives a menu after several seconds, then firefox crashes/core dumps. Oliver ___ 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: Recent MFC to 7 causes crash on VMware ESXi
On Monday 08 February 2010 1:51:46 pm Kostik Belousov wrote: On Mon, Feb 08, 2010 at 01:15:06PM -0500, John Baldwin wrote: On Monday 08 February 2010 11:06:00 am Kostik Belousov wrote: On Mon, Feb 08, 2010 at 10:32:37AM -0500, John Baldwin wrote: On Monday 08 February 2010 9:56:36 am Kostik Belousov wrote: On Mon, Feb 08, 2010 at 09:49:00AM -0500, John Baldwin wrote: On Saturday 06 February 2010 4:47:16 pm Tom McLaughlin wrote: John Baldwin wrote, On 02/05/2010 08:27 AM: On Thursday 04 February 2010 10:00:55 pm Tom McLaughlin wrote: Hi all, a recent MFC to 7-STABLE has started to cause issues for my VMs on VMware ESXi 3.5u4. After loading the mpt driver for the LSI disk controller the VM just shuts off. The workaround is to change the disk controller to the BusLogic type. Still, it used to work up until last week. The change was made around January 26th and based on the commits that day I'm guessing it's either r203047 or r203073 I have the same issue with both amd64 and i386 VMs. This affects HEAD and 8-STABLE as well and first affected HEAD over the summer. (I just worked around it and went about my business at the time. :-/) I've attached a dmesg from a kernel before the problem and one from after it started. What if you set 'hw.clfush_disable=1' from the loader? Yes, that corrected it on all my VMs. I've talked to people on ESXi 4 and they do not see the problem. I have yet to try 3.5u5 to see if this is a non-issue. 3.5 will be supported for awhile longer from VMware. I'm going to try upgrading the box during the week. I believe folks had to do this on HEAD/8.x as well. Perhaps we can automatically disable clflush if we are executing under VMware or Xen: Index: amd64/amd64/initcpu.c === --- amd64/amd64/initcpu.c (revision 203430) +++ amd64/amd64/initcpu.c (working copy) @@ -177,17 +177,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* -* XXXKIB: (temporary) hack to work around traps generated when -* CLFLUSHing APIC registers window. +* XXXKIB: (temporary) hack to work around traps generated +* when CLFLUSHing APIC registers window under virtualization +* environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by -* hw.clflush_disable tunable. This may help Xen guest on some AMD -* CPUs. +* hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; Index: i386/i386/initcpu.c === --- i386/i386/initcpu.c (revision 203430) +++ i386/i386/initcpu.c (working copy) @@ -724,17 +724,16 @@ if ((cpu_feature CPUID_CLFSH) != 0) cpu_clflush_line_size = ((cpu_procinfo 8) 0xff) * 8; /* -* XXXKIB: (temporary) hack to work around traps generated when -* CLFLUSHing APIC registers window. +* XXXKIB: (temporary) hack to work around traps generated +* when CLFLUSHing APIC registers window under virtualization +* environments. */ TUNABLE_INT_FETCH(hw.clflush_disable, hw_clflush_disable); - if (cpu_vendor_id == CPU_VENDOR_INTEL !(cpu_feature CPUID_SS) - hw_clflush_disable == -1) + if (vm_guest != 0 /* VM_GUEST_NO */ hw_clflush_disable == -1) cpu_feature = ~CPUID_CLFSH; /* * Allow to disable CLFLUSH feature manually by -* hw.clflush_disable tunable. This may help Xen guest on some AMD -* CPUs. +* hw.clflush_disable tunable. */ if (hw_clflush_disable == 1) cpu_feature = ~CPUID_CLFSH; It might be better to or old condition, i.e. Intel without SS, and new one, vm_guest != 0, instead of replacing the old ? I thought the old condition only happened under VMware? Reports I got where from XEN. Ok. Those would also be covered under the vm_guest test as it is non-zero for Xen, VMware, Parallels, etc. What I said was suggestion and not objection. Ignore me. Were there any
Re: Recent MFC to 7 causes crash on VMware ESXi
On Mon, Feb 08, 2010 at 02:42:33PM -0500, John Baldwin wrote: On Monday 08 February 2010 1:51:46 pm Kostik Belousov wrote: On Mon, Feb 08, 2010 at 01:15:06PM -0500, John Baldwin wrote: I thought the old condition only happened under VMware? Reports I got where from XEN. Ok. Those would also be covered under the vm_guest test as it is non-zero for Xen, VMware, Parallels, etc. What I said was suggestion and not objection. Ignore me. Were there any reports of problems with Intel CPUs that weren't under a virtualization system? If so, we should keep the test, but my understanding was that the test was only true under specific virtualization environments. Forcing Intel CPU to use CLFLUSH, by clearing SS bit, caused reserved trap on Pentium M at least. My concern is that if Intel makes some stripped-down CPU with CLFLUSH but without SS logic, we would be affected. pgp8Dyl6vEiKT.pgp Description: PGP signature
Re: PF Traffic Redirection issues
Thanks for the info Nick, I had the reflection working with PF + Inetd + NC. *in the inetd.conf I have the following:* #INTERNAL NC CONFIGURATION http stream tcp nowait root /usr/bin/nc nc -w 20 192.168.128.102 80 *in rc.conf in had to add the following to limit the proxy listening on the localhost Only:* inetd_flags=-wW -a 127.0.0.1 *the PF configuration is as follows:* TRANSLATION RULES: rdr pass on em0 inet proto tcp from any to 192.168.128.170 port = http - 127.0.0.1 port 80 FILTER RULES: block drop log all pass in on lo0 inet6 proto tcp from any to fe80::1 port = http flags S/SA keep state pass in on lo0 inet6 proto tcp from any to ::1 port = http flags S/SA keep state pass in on lo0 inet proto tcp from any to 127.0.0.1 port = http flags S/SA keep state pass in on em0 inet proto tcp from any to 192.168.128.170 port = ssh flags S/SA keep state pass out all flags S/SA keep state Thanks for the heads up. Hope this works for someone. KR, Spas On Fri, Feb 5, 2010 at 8:39 PM, Nick Rogers ncrog...@gmail.com wrote: On Fri, Feb 5, 2010 at 9:41 AM, Spas Karabelov st...@sofiahouse.netwrote: Hello, I am trying to perform traffic redirection with PF on 7.2-RELEASE. The traffic is in the same subnet and I try doing that by using just one interface em0. PF cannot redirect packets back out the interface they originated on. From pf.conf(5)... Redirections cannot reflect packets back through the interface they arrive on, they can only be redirected to hosts connected to different interfaces or to the firewall itself. ___ 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: ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
On Mon, Feb 08, 2010 at 05:58:53PM +0100, Guido Falsi wrote: On Mon, Feb 08, 2010 at 05:18:22PM +0100, Fabian Keil wrote: I experienced what I think is the same problem. ZFS's bulk disk flushes caused vlc to occasionally stutter when viewing a DVD rip from disk while ripping a DVD at the same time. My workaround is to put vfs.zfs.txg.timeout=3 in /boot/loader.conf. I think I read about this on zfs-disc...@. I assume on faster systems one can use a higher value. This was a very good idea. I'm trying this and the system freezes much less if at all. Are there any drawbacks I should be aware of? I can imagine that forcing more disk writes somewhat slows down normal disk activity, but I can bear that on a desktop system. I'd like a technical explanation of exactly what this loader.conf tunable does. The sysctl -d explanation is useful if one has insight to what purpose it serves. I can find mention on Solaris lists about txg timeout, but the context is over my head (intended for those very familiar with the inner workings of ZFS). I'd also like to know what vfs.zfs.txg.synctime does. I've been playing with vfs.zfs.txg.timeout (decreasing it from 30 to 5) and testing on a 3-disk raidz1 pool on a test machine I have, but I haven't finished my testing yet. A person said that decreasing the value increased throughput[1] for them, but in my brief test (using dd) it doesn't appear to improve I/O speed at all. Anyone know of a good (non-X-related) repro test case which can induce the ZFS bursty sluggishness problem so I can try it with different loader.conf tunables? Thanks. -- | 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: Recent MFC to 7 causes crash on VMware ESXi
On Monday 08 February 2010 2:46:51 pm Kostik Belousov wrote: On Mon, Feb 08, 2010 at 02:42:33PM -0500, John Baldwin wrote: On Monday 08 February 2010 1:51:46 pm Kostik Belousov wrote: On Mon, Feb 08, 2010 at 01:15:06PM -0500, John Baldwin wrote: I thought the old condition only happened under VMware? Reports I got where from XEN. Ok. Those would also be covered under the vm_guest test as it is non-zero for Xen, VMware, Parallels, etc. What I said was suggestion and not objection. Ignore me. Were there any reports of problems with Intel CPUs that weren't under a virtualization system? If so, we should keep the test, but my understanding was that the test was only true under specific virtualization environments. Forcing Intel CPU to use CLFLUSH, by clearing SS bit, caused reserved trap on Pentium M at least. My concern is that if Intel makes some stripped-down CPU with CLFLUSH but without SS logic, we would be affected. Hmm, I am content to just workaround things that we know are broken for enough. There are an infinite number of possibilities as far as if future products may be broken. I think for that case we should wait and add a workaround to disable it as new parts that are broken become available. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: www/firefox: Firefox 3.6 crashes, Firefox 3.5.7 not
I have no idea if this is related but from pkg-message Firefox 3.6 and HTML5 Certain functions used to display HTML5 elements need the sem module. If your Firefox crashes with the following message while viewing a HTML5 page: Bad system call (core dumped) you need to load the sem module (kldload sem). To load sem on every boot put the following into your /boot/loader.conf: sem_load=YES On Mon, Feb 8, 2010 at 9:04 PM, O. Hartmann ohart...@zedat.fu-berlin.dewrote: On 02/08/10 16:20, Gary Jennejohn wrote: On Mon, 08 Feb 2010 13:32:25 + O. Hartmannohart...@zedat.fu-berlin.de wrote: Today, I upgraded Firefox 3.5.7 (built yesterday) to Firefox 3.6. After deleting ~/.mozilla (after I did a buckup, of course), I tried a fresh start of 'firefox3'. After firefox showed up, I realized that no option-field (File, Extras etc) can be used, they are dead and after a few seconds I clicked them, firefox3 is crashing. Since I recompiled firefox 3.5.7 yesterday I was wondering if this is due to some 'false' lib or dependency. Since I figured that I have similar trouble with Thunderbird 3.0.1 after I installed it, I suspect a faulty library causing this behaviour. With Thunderbird 3, I never solved the problem although I tried to rebuild everything with thunderbird via 'portmaster -f'. I'll did this with firefox 3.6 also, but with no success. The crashing is observed on two nearly identical SMP FreeBSD 8.0/amd64 STABLE boxes (make world of today), up-to-date ports. The crash is NOT observed on my private oldish UP box, nearly the same setup, OS at the same revision and ports up to date as of yesterday. Maybe this could be a hint. Any hints or suggestions? Try doing ldd /usr/local/lib/firefox3/firefox-bin and see if anything looks weird. I did - and there is nothing weird. I checked the installed libraries and they are all rebuild when rebuilding necessary dependencies for firefox3. You can porbably ignore /usr/local/lib/firefox3/firefox-bin: libxul.so = not found (0x0) libmozjs.so = not found (0x0) libxpcom.so = not found (0x0) because run-mozilla.sh sets LD_LIBRARY_PATH to include /usr/local/lib/firefox3 where these libraries are installed. I merely deleted my old firefox 3.6 and reinstalled from the port (on 9-CURRENT AMD64) and haven't seen any problems. But of course, I've been running various incarnations of 3.6 for a while and may have gotten all the dependencies already correctly installed. --- Gary Jennejohn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I tried again, left the 'make config'-options as they were set by default, delete/backuped .mozilla in my home and they restartet firefox3. Nothing better than previously seen. Try hitting Button 'Tools' at the top menu bar gives a menu after several seconds, then firefox crashes/core dumps. Oliver ___ freebsd-po...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-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: NFSv4: mount -t nsf4 not the same as mount_newnfs?
On Mon, 8 Feb 2010, O. Hartmann wrote: Oh, and you should set: sysctl vfs.newnfs.locallocks_enable=0 in the server, since I haven't fixed the local locking yet. (This implies that apps/daemons running locally on the server won't see byte range locks performed by NFSv4 clients.) However, byte range locking between NFSv4 clients should work ok. Interesting, I see a lot of vfs.newfs-stuff on server-side, but not this specific OID. Do I miss something here? Oops, make that vfs.newnfs.enable_locallocks=0 rick ___ 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: NFSv4: mount -t nsf4 not the same as mount_newnfs?
On Mon, 8 Feb 2010, O. Hartmann wrote: So I guess the above one is the more 'transparent' one with respect to the future, when NFSv4 gets mature and its way as matured into the kernel? Yea, I'd only use mount -t newnfs if for some reason you want to test/use the experimental client for nfsv2,3 instead of the regular one. I tried the above and it works. But it seems, that only UFS2 filesystems can be mounted by the client. When trying mounting a filesystem residing on ZFS, it fails. Mounting works, but when try to access or doing a simple 'ls', I get ls: /backup: Permission denied On server side, /etc/exports looks like -- V4: / -sec=sys:krb5 #IPv4# /backup #IPv4# -- Is there still an issue with ZFS? For ZFS, everything from the root specified by the V4: line must be exported at this time. So, if / isn't exported, the above won't work for ZFS. You can either export / or move the NFSv4 root down to backup. For example, you could try: V4: /backup -sec=sys:krb5 /backup (assuming /backup is the ZFS volume) and then a mount like: mount -t nfs -o nfsv4 server:/ /mnt will mount /backup on /mnt rick ps: ZFS also has its own export stuff, but it is my understanding that putting a line in /etc/exports is sufficient. I've never used ZFS, so others will know more than I. ___ 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: NFSv4: mount -t nsf4 not the same as mount_newnfs?
On Mon, Feb 8, 2010 at 2:37 PM, Rick Macklem rmack...@uoguelph.ca wrote: ps: ZFS also has its own export stuff, but it is my understanding that putting a line in /etc/exports is sufficient. I've never used ZFS, so others will know more than I. My understanding (from having used NFS and ZFS, haven't looked at the code) is that: The sharenfs property for a ZFS dataset gets written out to /etc/zfs/exports, which gets appended to the mountd command-line by default. Thus, you can use /etc/exports or sharenfs property, whichever is easier. # zfs get sharenfs storage/backup NAMEPROPERTY VALUE SOURCE storage/backup sharenfs -maproot=root 192.168.0.12 local # cat /etc/exports # cat /etc/zfs/exports # !!! DO NOT EDIT THIS FILE MANUALLY !!! /storage/backup -maproot=root 192.168.0.12 # pgrep -lf exports 1381 /usr/sbin/mountd -r -p 32000 /etc/exports /etc/zfs/exports -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kerberized NFSv3 incorrect behavior
On Mon, 8 Feb 2010, George Mamalakis wrote: To tell you the truth, when I recompiled my kernel with: options NFSD options KGSSAPI device crypto to setup an nvsv4 server, nfsd refused to start because mountd was segfaulting. I didn't play much with this setup, because I was in a hurry, so I commented out NFSD and put back NFSSERVER, to be able to test my server. Ok, I'll test the above case. It definitely should be fixed. Now a last question: Does gssapi/nfs setup work with the automounter (bsd/linux nfs-client)? No idea. The Mac OS X client works ok with the automounter. The main issue I'm aware of is that, if you are automounting home directories, then the kinit has to happen before any access attempt to the home dir. occurs during the login sequence. (I've never tried to automount on either FreeBSD nor Linux.) Have fun, rick ps: The nf...@linux-nfs.org mailing list is a good place to ask, if you run into Linux client issues. ___ 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: ATA_CAM + ZFS gives short 1-2 seconds system freeze on disk load
I'd like a technical explanation of exactly what this loader.conf tunable does. The sysctl -d explanation is useful if one has insight to what purpose it serves. I can find mention on Solaris lists about txg timeout, but the context is over my head (intended for those very familiar with the inner workings of ZFS). Ben Rockwood's blog has pretty decent explanation of how transaction groups in ZFS work: http://www.cuddletech.com/blog/pivot/entry.php?id=1015 --Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
suspend to disk
Hello everyone today I tried whether my samsung q35 laptop would suspend using acpiconf on RELENG_8. I was amazed that acpiconf -s3 works out of the box. However acpiconf -s4 does not work which would be the useful side of hibernation for me. From the manpage of acpiconf I understand that acpiconf -s4 should store the non-cache-parts from ram somewhere on disk. If called the system shuts down without writing much on the disk so something is odd there. I have 2,5 gb of ram and only 800MB of swap space which is labeled correctly. What do I have to do in order to make suspend to disk work? Is it possible to compress the contents of the ram like some programs from the linuxworld do it (tuxonice)? Or did I entirely miss some configuration here? Please cc me while replying to this email as I am not on the freebsd-acpi list. I do track -stable though. kind regards Christof -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: This is a digitally signed message part.
Re: suspend to disk
On Tue, Feb 9, 2010 at 12:13 AM, Christof Schulze christof.schu...@gmx.com wrote: Hello everyone today I tried whether my samsung q35 laptop would suspend using acpiconf on RELENG_8. I was amazed that acpiconf -s3 works out of the box. However acpiconf -s4 does not work which would be the useful side of hibernation for me. http://www.freebsd.org/projects/acpi/ Excerpt: suspend to disk -- Implement a suspend/resume from disk mechanism. Possibly use the dump functions to dump pages to disk, then use ACPI to put the system in S4 or power-off. Resume would require changes to the loader to load the memory image directly and then begin executing again. -- Not done. Did anything change in recent years? m. ___ 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
xorg big slowdown after upgrade (intel driver)
Hello, yesterday I upgraded my 8.0-STABLE installation and noticed that xorg become a lot slower then it used to be. The previous upgrade dates back to about one month ago. I'm running freebsd on an amd64 and the graphic card is an integrated Intel Q45/Q43. Here is the relevant line from lspci: 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) The kernel is an almost unmodified GENERIC. Has anybody noticed this problem too? Any idea? Thank you, Paride Legovini ___ 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: one more load-cycle-count problem
On Tue, 9 Feb 2010, Dan Naumov wrote: which essentially solves the problem. Note that going this route will probably involve rebuilding your entire array from scratch, because applying WDIDLE3 to the disk is likely to very slightly affect disk geometry, but just enough for hardware raid or ZFS or whatever to bark at you and refuse to continue using the drive in an existing pool (the affected disk can become very slightly smaller in capacity). Backup data, apply WDIDLE3 to all disks. Recreate the pool, restore backups. This will also void your warranty if used on the new WD drives, although it will still work just fine. Errm.. Why would it change the geometry? I have used this tool to change the settings on all my disks and it did not in any way cause a problem booting later. My disks are WDC WD10EADS-00L5B1/01.01A01 (1Tb green disks) AFAIK it just tunes EEPROM settings, it doesn't reflash the firmware. That said I have heard reports of it bricking a drive so I would test it on one drive first (not that I did, I heard the bricking reports later..) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: one more load-cycle-count problem
On Tue, 9 Feb 2010, Gerrit Kühn wrote: :-))) I would really prefer to be able to set this stuff via camcontrol or atacontrol. Alone having to boot DOS with this machine (no floppy, no cdrom) will be a real pain. And most probably the DOS tool will not be able to see the disks sitting behind my lsi-driven controller anyway, so I have to plug them elsewhere, too. Great job, WD. :-( It does boggle the mind that they don't publish the spec for this :( I booted off a USB stick (syslinux booting freedos), although the BIOS sees my disks.. (Although not all, I had to flash 4, then swap 2 and flash the last one.. very stupid) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: one more load-cycle-count problem
On Mon, Feb 8, 2010 at 4:29 PM, Daniel O'Connor docon...@gsoft.com.auwrote: On Tue, 9 Feb 2010, Dan Naumov wrote: which essentially solves the problem. Note that going this route will probably involve rebuilding your entire array from scratch, because applying WDIDLE3 to the disk is likely to very slightly affect disk geometry, but just enough for hardware raid or ZFS or whatever to bark at you and refuse to continue using the drive in an existing pool (the affected disk can become very slightly smaller in capacity). Backup data, apply WDIDLE3 to all disks. Recreate the pool, restore backups. This will also void your warranty if used on the new WD drives, although it will still work just fine. Errm.. Why would it change the geometry? I have used this tool to change the settings on all my disks and it did not in any way cause a problem booting later. My disks are WDC WD10EADS-00L5B1/01.01A01 (1Tb green disks) I just did this to 8 of the 1.5 TB Caviar Green disks, without ZFS complaining in any way. I did test it on a spare drive before doing it to the 7 live drives. And I did replace them while the server was turned off, just to be safe (and to prevent a resilver from occuring). wdidle3 doesn't actually disable the idle timeout on these drives. Using /d just sets the timeout to 62 minutes. Effectively the same, but don't be surprised when it continues to say idel 3 available and enabled. :) So far, things are running much smoother. Load_Cycle_Count has stopped increasing (50,000 in 8 weeks on 1 drive). Re-silver throughput for these drives has jumped from 7 MBps to over 40 MBps (90% full pool, so it's slower than normal right now, which is why we're swapping these drive into the pool). -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: one more load-cycle-count problem
On Tue, 9 Feb 2010, Freddie Cash wrote: I just did this to 8 of the 1.5 TB Caviar Green disks, without ZFS complaining in any way. I did test it on a spare drive before doing it to the 7 live drives. And I did replace them while the server was turned off, just to be safe (and to prevent a resilver from occuring). wdidle3 doesn't actually disable the idle timeout on these drives. Using /d just sets the timeout to 62 minutes. Effectively the same, but don't be surprised when it continues to say idel 3 available and enabled. :) /d sets it (for me) to 6300 milliseconds (6.3 seconds). I took this as a special value that disabled it entirely (no idea why they didn't use 0 or 255..) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
FreeBSD 8.0 i386 unable to boot...
Hi, I have a hard time booting FreeBSD 8.0 on one of my machines. It is an older Pentium with HyperThreading. It was running fine with 7.2 but the kernel crashed after a buildworld/buildkernel/installkernel/reboot of 8.0. I had not updated FreeBSD on that machine for a while so I decided to burn a CD of 8.0 i386 (disc1) and boot the machine with it. This does not work either however as the kernel wants to automatically reboot the machine right after the Probing Device stage. Here is the error message I get: Going nowhere without my init cpuid = 1 Does anyone know what can be causing this and how to solve it? Thanks! ___ 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.0 i386 unable to boot...
Well try turning off ACPI, HyperThreading, etc.? On 2010-02-08 09:01:28PM -0500, Pierre-Luc Drouin wrote: Hi, I have a hard time booting FreeBSD 8.0 on one of my machines. It is an older Pentium with HyperThreading. It was running fine with 7.2 but the kernel crashed after a buildworld/buildkernel/installkernel/reboot of 8.0. I had not updated FreeBSD on that machine for a while so I decided to burn a CD of 8.0 i386 (disc1) and boot the machine with it. This does not work either however as the kernel wants to automatically reboot the machine right after the Probing Device stage. Here is the error message I get: Going nowhere without my init cpuid = 1 Does anyone know what can be causing this and how to solve it? Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- === Peter C. Lai | Bard College at Simon's Rock Systems Administrator| 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 === ___ 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
hardware for home use large storage
While I'm not a heavy FreeBSD user I can offer you some advice on hardware at least based on my own experience. If you want things to work as good as possible go with Intel chipset and LAN. AMD chipsets works (mostly) but you'll have worse performance and you wont get an Intel NIC which performs much better than Realtek or Attansic. which you usually find on AMD motherboards. A general tip is to go for business chipsets as Intel like to call them, Q35 (I have a few of those and they work very good), Q45 and Q57. By doing so you can be sure to get Intel NIC and they aren't much more expensive than your average motherboard and also usually carries some kind of remote management. Having in mind that FreeBSD may/may not support the newest hardware around I'd guess that Q57 needs -CURRENT for now but I would highly recommend it as Socket 775 is slowly dying. ASUS P7Q57-M DO looks like a very nice board if you want bleeding edge have in mind though as time of writing support for NIC doesn't seem to be in FreeBSD but I guess its a short matter of time (82578DM). Pair it with the slowest Core i3 CPU you can find and you have a very nice solution. If you step up to i5 you get hardware encryption =) If you want legacy Intel DQ45CB should be a pretty nice choice with supported LAN out of the box. Intel Pentium E6300 should be more than enough for storage. Both MSI and Gigabyte also makes Q-chipsets motherboards but they don't seem to widely available in the US and their boards should be fine too. Since you want to have more than 5 HDDs you need a controller card of some sort, in that case I would recommend you to have a look at the Supermicro ones mentioned in the post. http://forums.freebsd.org/showpost.php?p=59735postcount=5 UIO is just a backwards PCIe slot so turning it around till make it fit although you mean need to secure it somehow. They may be a bit hard to find but you can find a few sellers on eBay too. What I don't know is how the motherboards will react if you pop one in which you need to do some research on. As for memory you'll need at least 2Gb but 4Gb is highly recommended if you're going to use ZFS. Just make sure the sticks follows JEDEC standards and you'll be fine (Corsair Value Select series or stock Crucial are fine). //Daniel ___ 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.0 i386 unable to boot...
After doing some more research, it seems that I am having the same problem than described by this person: http://forums.freebsd.org/showthread.php?t=4502 however I really don't understand why I would need to move partitions around to allow the installer to even start? This machine has 2GB of RAM which I guess should be plenty enough to start the installer without swapping... The hard drive is a 80GB WD IDE drive. The machine is not configured to use any RAID. Thanks! Peter C. Lai wrote: Well try turning off ACPI, HyperThreading, etc.? On 2010-02-08 09:01:28PM -0500, Pierre-Luc Drouin wrote: Hi, I have a hard time booting FreeBSD 8.0 on one of my machines. It is an older Pentium with HyperThreading. It was running fine with 7.2 but the kernel crashed after a buildworld/buildkernel/installkernel/reboot of 8.0. I had not updated FreeBSD on that machine for a while so I decided to burn a CD of 8.0 i386 (disc1) and boot the machine with it. This does not work either however as the kernel wants to automatically reboot the machine right after the Probing Device stage. Here is the error message I get: Going nowhere without my init cpuid = 1 Does anyone know what can be causing this and how to solve it? Thanks! ___ 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: ionice in FreeBSD?
On 3/02/2010 10:52 PM, Jordi Espasa Clofent wrote: On 02/03/2010 12:12 PM, Bruce Simpson wrote: On 02/02/2010 17:19, Jordi Espasa Clofent wrote: In FreeBSD we've nice(1), renice(8) and even rtprio, idprio(1) but if I'm understanding correctly, they're related to CPU priorty only, not to I/O. That's not entirely true. A thread's CPU priority is still going to affect its ability to be scheduled on the CPU, and if it's waiting in the read() or write() syscalls, then this will make a difference to how quickly it can complete the next call. Yes. I've already supposed it. However, it doesn't explicitly affect relative I/O prioritization. This is another story entirely. I suspect in a lot of cases adding a weight to per thread I/O, isn't going to make much difference for disk I/Os which are being sorted for the geometry (e.g. AHCI NCQ). So I guess my question is, 'why do you need I/O scheduling, and what aspect of system performance are you trying to solve with it' ? Some shell-scripts based on dd or rsync, for example. Even a daily antivirus (ClamAV) scanner means an extensive I/O. Programs like Rsync do provide --bwlimit= which work great in slowing it down to a desired level. I can't help but think every program that can use too much IO should have it's own IO/speed switch of some sort. I can only hope that in general nix evolution that all programs that can over use IO will offer a switch to slow it down like Rsync does. Using a while ionice can be a useful feature it can also be said that there are too many instances where it's being used as a hack to deal with a program that isn't offering all the functionality that it should. Cheers, Mike ___ 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.0 i386 unable to boot...
On Tue, 9 Feb 2010, Pierre-Luc Drouin wrote: After doing some more research, it seems that I am having the same problem than described by this person: http://forums.freebsd.org/showthread.php?t=4502 So you get the same file system full message and then a panic about init? however I really don't understand why I would need to move partitions around to allow the installer to even start? This machine has 2GB of RAM which I guess should be plenty enough to start the installer without swapping... The hard drive is a 80GB WD IDE drive. The machine is not configured to use any RAID. It is pretty odd, I've installed FreeBSD on a laptop with 60Gb partitions and FreeBSD was last yet it worked fine.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: ionice in FreeBSD?
On Mon, 8 Feb 2010 23:37, mv@ wrote: On 3/02/2010 10:52 PM, Jordi Espasa Clofent wrote: On 02/03/2010 12:12 PM, Bruce Simpson wrote: On 02/02/2010 17:19, Jordi Espasa Clofent wrote: In FreeBSD we've nice(1), renice(8) and even rtprio, idprio(1) but if I'm understanding correctly, they're related to CPU priorty only, not to I/O. That's not entirely true. A thread's CPU priority is still going to affect its ability to be scheduled on the CPU, and if it's waiting in the read() or write() syscalls, then this will make a difference to how quickly it can complete the next call. Yes. I've already supposed it. However, it doesn't explicitly affect relative I/O prioritization. This is another story entirely. I suspect in a lot of cases adding a weight to per thread I/O, isn't going to make much difference for disk I/Os which are being sorted for the geometry (e.g. AHCI NCQ). So I guess my question is, 'why do you need I/O scheduling, and what aspect of system performance are you trying to solve with it' ? Some shell-scripts based on dd or rsync, for example. Even a daily antivirus (ClamAV) scanner means an extensive I/O. Programs like Rsync do provide --bwlimit= which work great in slowing it down to a desired level. I can't help but think every program that can use too much IO should have it's own IO/speed switch of some sort. I can only hope that in general nix evolution that all programs that can over use IO will offer a switch to slow it down like Rsync does. Using a while ionice can be a useful feature it can also be said that there are too many instances where it's being used as a hack to deal with a program that isn't offering all the functionality that it should. Cheers, Mike In this thread with due respect to the OP the following might be considered a fruitless hack but it works!. Piping a processes output to dd(1) if you have a choice is a pretty fair temporary solution if a program does not offer that capability. For instance, I don't know if you are familiar with dump(8) at all, but I use a -P or pipe from that process to dd(8) to slow down the traffic that it tries to write over the network for backup purposes and then also give dump(8) a different nice level so it plays along. So even if you can cat your output and then read it in from fd(4) using dd(8) you still have a chance at slowing things down a little or writing at smaller increments that wont impact your environment as hard. ;) -- jhell ___ 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.0 i386 unable to boot...
Hi-- On Feb 8, 2010, at 6:01 PM, Pierre-Luc Drouin wrote: Going nowhere without my init cpuid = 1 Does anyone know what can be causing this and how to solve it? I don't suppose you built a custom kernel without the COMPAT_FREEBSD7 option? You need it until you get a new R8 userland and all ports recompiled... -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: hardware for home use large storage
On Mon, Feb 08, 2010 at 03:56:46PM +1030 I heard the voice of Daniel O'Connor, and lo! it spake thus: I have something similar (5x1Tb) - I have a Gigabyte GA-MA785GM-US2H with an Athlon X2 and 4Gb of RAM (only half filled - 2x2Gb) [...] Note that it doesn't support ECC, I don't know if that is a problem. How's that? Is the BIOS just stupid, or is the board physically missing traces? -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: hardware for home use large storage
On Tue, 9 Feb 2010, Matthew D. Fuller wrote: On Mon, Feb 08, 2010 at 03:56:46PM +1030 I heard the voice of Daniel O'Connor, and lo! it spake thus: I have something similar (5x1Tb) - I have a Gigabyte GA-MA785GM-US2H with an Athlon X2 and 4Gb of RAM (only half filled - 2x2Gb) [...] Note that it doesn't support ECC, I don't know if that is a problem. How's that? Is the BIOS just stupid, or is the board physically missing traces? I don't know.. Some consumer Gigabyte motherboards seem to support it (eg GA-MA770T-UD3P). Probably the result of idiotic penny pinching though :-/ -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: hardware for home use large storage
On Mon, 8 Feb 2010, Dan Langille wrote: Hi, I'm looking at creating a large home use storage machine. Budget is a concern, but size and reliability are also a priority. Noise is also a concern, since this will be at home, in the basement. That, and cost, pretty much rules out a commercial case, such as a 3U case. It would be nice, but it greatly inflates the budget. This pretty much restricts me to a tower case. I recently had to put together something very cheap for a client for disk-only backups (rsync + zfs snapshots). As you noticed, rack enclosures that will hold a bunch of drives are insanely expensive. I put my wishlist from NewEgg below. While the $33 case is a bit flimsy, the extra high-cfm fan in the back and the fan that sits in front of the drive bays keeps the drives extremely cool. For $33, I lucked out. The primary use of this machine will be a backup server[1]. It will do other secondary use will include minor tasks such as samba, CIFS, cvsup, etc. I'm thinking of 8x1TB (or larger) SATA drives. I've found a case[2] with hot-swap bays[3], that seems interesting. I haven't looked at power supplies, but given that number of drives, I expect something beefy with a decent reputation is called for. For home use is the hot-swap option really needed? Also, it seems like people who use zfs (or gmirror + gstripe) generally end up buying pricey hardware raid cards for compatibility reasons. There seem to be no decent add-on SATA cards that play nice with FreeBSD other than that weird supermicro card that has to be physically hacked about to fit. I did splurge for a server-class board from Supermicro since I wanted bios serial port console redirection, and as many SATA ports on-board that I could find. Whether I use hardware or software RAID is undecided. I I think I am leaning towards software RAID, probably ZFS under FreeBSD 8.x but I'm open to hardware RAID but I think the cost won't justify it given ZFS. I've had two very different ZFS experiences so far. On the hardware I mention in this message, I had zero problems and excellent performance (bonnie++ showing 145MB/s reads, 132MB/s writes on a 4 disk RAIDZ1 array) with 8.0/amd64 w/4GB of RAM. I did no tuning at all - amd64 is the way to go for ZFS. On an old machine at home with 2 old (2003 era) 32-bit xeons, I ran into all the issues people see with i386+ZFS - kernel memory exhaustion resulting in a panic, screwing around with an old 3Ware RAID card (JBOD mode) that cannot properly scan for new drives, just a total mess without lots of futzing about. Given that, what motherboard and RAM configuration would you recommend to work with FreeBSD [and probably ZFS]. The lists seems to indicate that more RAM is better with ZFS. Here's the list: http://secure.newegg.com/WishList/PublicWishDetail.aspx?WishListNumber=8441629 Just over $1K, and I've got 4 nice drives, ECC memory, and a server board. Going with the celeron saved a ton of cash with no impact on ZFS that I can discern, and again, going with a cheap tower case slashed the cost as well. That whole combo works great. Now when I use up those 6 SATA ports, I don't know how to get more cheaply, but I'll worry about that later... Charles Thanks. [1] - FYI running Bacula, but that's out of scope for this question [2] - http://www.newegg.com/Product/Product.aspx?Item=N82E16811192058 [3] - nice to have, especially for a failure. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: hardware for home use large storage
http://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPA.cfm?typ=H Supermicro just released a new Mini-ITX fanless Atom server board with 6xSATA ports (based on Intel ICH9) and a PCIe 16x slot. It takes up to 4GB of RAM, and there's even a version with KVM-over-LAN for headless operation and remote management. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: hardware for home use large storage
On Tue, Feb 09, 2010 at 05:21:32PM +1100, Andrew Snow wrote: http://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPA.cfm?typ=H Supermicro just released a new Mini-ITX fanless Atom server board with 6xSATA ports (based on Intel ICH9) and a PCIe 16x slot. It takes up to 4GB of RAM, and there's even a version with KVM-over-LAN for headless operation and remote management. Neat hardware. But with regards to the KVM-over-LAN stuff: it's IPMI, and Supermicro has a very, *very* long history of having shoddy IPMI support. I've been told the latter by too many different individuals in the industry (some co-workers, some work at Yahoo, some at Rackable, etc.) for me to rely on it. If you *have* to go this route, make sure you get the IPMI module which has its own dedicated LAN port on the module and ***does not*** piggyback on top of an existing LAN port on the mainboard. -- | 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: hardware for home use large storage
On Tue, 9 Feb 2010, Charles Sprickman wrote: For home use is the hot-swap option really needed? Also, it seems like people who use zfs (or gmirror + gstripe) generally end up buying pricey hardware raid cards for compatibility reasons. There seem to be no decent add-on SATA cards that play nice with FreeBSD other than that weird supermicro card that has to be physically hacked about to fit. A friend of mine is building one and I couldn't get the Supermicro card to work (the older version). It being a black box driver I couldn't see what the problem was. I had good success with the onboard SATA ports (AHCI compliant), however there are only 6 ports on the board I picked. Hopefully port multipliers will be fully working when I need some more disks ;) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
