Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
On 04/16/2012 09:08 AM, Craig Rodrigues wrote: So my CPU support 64-bit mode, but does not support hardware-assisted virtualization. Intel doesn't support 64 bit software-only virtualization. You really need VTX for this to work. See also: http://en.wikipedia.org/wiki/X86_virtualization#64-bit Regards, Thomas ___ 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: Crashes with Promise controller
On 7/7/11 2:09 PM, Christian Baer wrote: Do you have an alternative controller in mind? Preferably I mean one that doesn't cost ten times as much. :-) I suggest an LSI 1068 based SAS controller. With the SAS-SATA cables included it will cost at most five times as much :) Regards, Thomas ___ 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: Crashes with Promise controller
On 6/30/11 7:31 PM, Christian Baer wrote: As far as I can tell so far there isn't any realy kernel panik. But the machine resets alright. All I can find in /var/log/messages is what I have already written. :-( A serial console is easy enough to set up on a Sun for example, but in this case, I am running a simple AthlonXP, which has nothing for that sort of help. I would need a special card for that and those cose quite a bit. :-( You can use a USB to serial converter. They cost around $20. I don't know which one to choose; I've never used one on FreeBSD so hopefully someone else can fill me in here. Regards, Thomas ___ 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: Crashes with Promise controller
On 6/30/11 8:08 PM, Christian Baer wrote: Please keep in mind though that I am not the only person out there with the same error using the same controller (type). I somehow doubt that all those hits by Google are all caused by power difficulties and the common controller is pure coincidence. Just a little 'me too'. I used to have a system with an Athlon XP 3200+, an ASUS A7V880 mainboard (iirc) and a Promise SATA150TX4 and a Promise SATA300something, both PCI (no PCI-e) cards with 4 SATA ports. I didn't encounter system resets, but hard lockups with FreeBSD 7 and 8. No kernel messages on the console, everything just hang until I pressed the hard reset button. After about 3 months of testing and frustration I gave up and bought another controller. Regards, Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS vs OSX Time Machine
Hi, On 4/28/11 4:03 PM, Daniel O'Connor wrote: Does anyone else use ZFS to store TM backups? I find that whenever my laptop (over wifi!) starts a TM the ZFS machine it's backing up to grinds to a halt.. Other systems streaming stuff over NFS from it also tend to stall.. Are you using zfs compression? If so, try turning that off. I have a pool with a couple of filesystems with gzip-9 compression enabled. Whenever I write (using zfs receive, it is a backup server) to one of those volumes the whole pool stalls with lots of disk activity. Even creating a snapshot on another filesystem within the same pool lasts a couple of minutes. Does anyone know how to make this perform a little better? It's only writing small amounts (70-100 ops/s, 1 MB/s) on an otherwise idle pool. Still the drive leds blink like crazy. One of my two CPU cores is maxed out, the other is idle. I suppose it won't get any faster (it's CPU bound because of the heavy gzip compression), but why is the pool so slow? Is zfs receive using synchonous writes? Sorry for maybe being offtopic :-) Regards, Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS backups: retrieving a few files?
On 11/23/10 1:45 PM, Andrew Reilly wrote: No, I don't like tar, rsync and friends for backups: they don't deal well with hard links, special files or sparse files. rsync -avHxS --delete --numeric-ids /src/. /dst/. Handles sparse files (S) and hard links (H). Never had any trouble with special files. What sort of special files are not handled correctly by rsync? I'd like to know because I'm relying on rsync for backups for years on my home network. Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS backups: retrieving a few files?
On 11/23/10 4:45 PM, Freddie Cash wrote: On Tue, Nov 23, 2010 at 4:56 AM, Thomas Ronnertho...@ronner.org wrote: rsync -avHxS --delete --numeric-ids /src/. /dst/. One problem with using rsync when dealing with hard-linked files: it doesn't like it when the source switches from hard-linked to non-hard-linked files. You end up with a mix of hard-linked and non-hard-linked files in the destination, with the contents of the non-hard-linked files all mixed around. We just discovered this when we upgraded our Debian 4.0 (Etch) boxes to Debian 5.0 (Lenny). On Etch, all the gzip tools are hard-links (zcat, zless, gzip, gunzip, etc). On Lenny, they are all separate files, and most are just shell scripts that use gzip. Doing an rsync of a Lenny box onto a directory from an Etch box, you end up with some hard-linked files, some regular files, and the contents of all the files are mixed-up based on which source file (script or binary) was read first. We've had to resort to clearing out the backups directory when doing a Debian upgrade, in order to guarantee that we get a clean backup via rsync. Thanks for this info! I'm going to try to reproduce this. Thomas. ___ 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: Can't build 8.1 GENERIC kernel
Hi Olaf, On 09/09/2010 16:17, Olaf Seibert wrote: I'm trying to build a custom kernel, and I got an error. So I tried GENERIC, in the perhaps old-fashioned way of # config GENERIC # cd ../compile/GENERIC # make depend # make I don't know about the old-fashioned way, but the new way is: # cd /usr/src # make buildkernel KERNCONF=GENERIC # make installkernel KERNCONF=GENERIC The KERNCONF=GENERIC is redundant, because the GENERIC config is default. Thomas ___ 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: Sysinstall does not define SATA
Hello, On 26 Feb 2010, at 15:21, oleg wrote: Got some trouble. The Sysinstall program of FreeBSD 8.0 release does not define SATA hard drives. Can`t create slices. But that machine works correctly by Windows. See attached dmesg file. The dmesg you attached is from FreeBSD 6.1, not 8.0. It probably lacks the driver for your SATA chipset. Regards, Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On 18 Nov 2009, at 10:17, Gerrit Kühn wrote: Supermicro AOC-USASLP-L8i card All my childhood traumas magically went away when I bought this card. Recommended! Thomas___ 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 Install Failure
On 15 Sep 2009, at 10:52, Doug Hardie wrote: Installing 8.0 Beta 4 on an i386 machine from disc 1. IN the Extracting ports: Panic: initiate_write_inodeblock_ufs2: already started cpuid=0 KDB: enter: panic [thread pid 19 tid 100045 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why I did a where but its way too much to type accurately by hand. This is an older system, but it does boot disc 1 where some of the previous releases it would not boot disk 1 but had to use the live file system. The same thing happened to me under VMWare Workstation, when I installed FreeBSD 8.0-BETA4 on a (virtual) disk connected to a (virtual) LSI SAS adaptor. Installing on a IDE disk worked around the problem. It happened with the i386 as well as the amd64 version. Thomas ___ 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: Detecting CPU throttling on over temperature
Hi, On 10 Sep 2009, at 14:43, Daniel O'Connor wrote: I thought coretemp had be modified in HEAD to support Phenoms but I can't find any evidence of that in SVN so I am not sure what I am thinking.. How about 'k8temp'? # make search name=k8temp Port: k8temp-0.4.0 Path: /usr/ports/sysutils/k8temp Info: Athlon 64 and Opteron on-die temperature reader Maint: t...@hur.st B-deps: R-deps: WWW:http://hur.st/k8temp/ # k8temp CPU 0 Core 0 Sensor 0: 35c CPU 0 Core 1 Sensor 0: 36c This is on the amd64 version of FreeBSD 8.0 using an Athlon64 X2 4200+. Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS: zpool scrub lockup
On Fri, 2009-07-10 at 15:09 +0300, Andriy Gapon wrote: on 09/07/2009 21:25 Thomas Ronner said the following: Is this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-gdb.html (10.6 On-Line Kernel Debugging Using Remote GDB) the debugging via serial console you're referring to? Yes. Thanks. I'll try that in a couple of weeks when I return from vacation. Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS: zpool scrub lockup
Hi Andriy, Andriy Gapon wrote: on 08/07/2009 23:30 Thomas Ronner said the following: Hello, I don't know whether this is the right list; maybe freebsd-fs is more appropriate. So please redirect me there if this isn't the right place. My system (i386, Athlon XP) locks hard when scrubbing a certain pool. It has been doing this for at least a couple of months now. For this reason I upgraded to 7.2-STABLE recently as this had the latest ZFS bits, but this doesn't help. It even makes the problem worse: in previous versions I just hit the reset button and forgot about it, but now it remembers that it was scrubbing (I presume) and tries to resume at the exact same place, locking up again. This means I haven't been able to mount these ZFS volumes successfully: the moment I do a /etc/rc.d/zfs start from single user mode (I have my /, /var and /usr on UFS) it locks up in a couple of seconds. And by locks up I really mean locks up. No panic, nothing. Pressing the reset button on the chassis is the only way to reboot. You can try adding SW_WATCHDOG option to your kernel which might help catching the lockup. Things like INVARIANTS and WITNESS might help th debugging too. Serial console for remote debugging would be very useful too. I'll definitely try those and report back on this list. Thanks for your answer! Regards, Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS: zpool scrub lockup
Thomas Ronner wrote: Hi Andriy, Andriy Gapon wrote: on 08/07/2009 23:30 Thomas Ronner said the following: Hello, I don't know whether this is the right list; maybe freebsd-fs is more appropriate. So please redirect me there if this isn't the right place. My system (i386, Athlon XP) locks hard when scrubbing a certain pool. It has been doing this for at least a couple of months now. For this reason I upgraded to 7.2-STABLE recently as this had the latest ZFS bits, but this doesn't help. It even makes the problem worse: in previous versions I just hit the reset button and forgot about it, but now it remembers that it was scrubbing (I presume) and tries to resume at the exact same place, locking up again. This means I haven't been able to mount these ZFS volumes successfully: the moment I do a /etc/rc.d/zfs start from single user mode (I have my /, /var and /usr on UFS) it locks up in a couple of seconds. And by locks up I really mean locks up. No panic, nothing. Pressing the reset button on the chassis is the only way to reboot. You can try adding SW_WATCHDOG option to your kernel which might help catching the lockup. Things like INVARIANTS and WITNESS might help th debugging too. Serial console for remote debugging would be very useful too. I'll definitely try those and report back on this list. Thanks for your answer! I put the following in my kernel config: # debugging options KDB options DDB options GDB options BREAK_TO_DEBUGGER options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_KDB options DEBUG_VFS_LOCKS options DIAGNOSTIC options SW_WATCHDOG When I send a BREAK from my serial console it enters the debugger, so that works. But when I start ZFS (/etc/rc.d/zfs start) it freezes again and BREAK doesn't enter the debugger. I'll try playing with the watchdog now, but I doubt this will help. Any clues? Thanks, Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS: zpool scrub lockup
Andriy Gapon wrote: For watchdog to fire it first needs to be enabled, e.g. by starting watchdogd. Try to run /etc/rd.d/watchdogd onestart before zfs start and then wait for about 16 seconds (default timeout). I tried this. When only running 'watchdog' (without starting the daemon) it enters the debugger in 16 seconds. The only way to continue is issuing the 'watchdog' debugger command (I presume this disables the watchdog?), followed by 'c'. But when re-enabling the watchdog by running /etc/rc.d/watchdogd start (I already added watchdogd to rc.conf) If that doesn't help, then it seems that the only option would be debugging via serial console. Or manually generating NMI, if your system has an NMI button/switch/jumper. No, I don't have a manual NMI thingy. Is this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-gdb.html (10.6 On-Line Kernel Debugging Using Remote GDB) the debugging via serial console you're referring to? Thanks, Thomas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ZFS: zpool scrub lockup
Hello, I don't know whether this is the right list; maybe freebsd-fs is more appropriate. So please redirect me there if this isn't the right place. My system (i386, Athlon XP) locks hard when scrubbing a certain pool. It has been doing this for at least a couple of months now. For this reason I upgraded to 7.2-STABLE recently as this had the latest ZFS bits, but this doesn't help. It even makes the problem worse: in previous versions I just hit the reset button and forgot about it, but now it remembers that it was scrubbing (I presume) and tries to resume at the exact same place, locking up again. This means I haven't been able to mount these ZFS volumes successfully: the moment I do a /etc/rc.d/zfs start from single user mode (I have my /, /var and /usr on UFS) it locks up in a couple of seconds. And by locks up I really mean locks up. No panic, nothing. Pressing the reset button on the chassis is the only way to reboot. Details about my system: Athlon XP 2400+ Asus K7V-880 (VIA chipset; 2 IDE, 2 SATA ports) 2 GB RAM Promise Ultra133-TX2 (2 port IDE controller) Promise SATA150 4 port SATA controller Promise SATA300 4 port SATA controller 4 Maxtor 300 GB IDE disks 1 Maxtor 300 GB SATA disk 1 WD 320 GB SATA disk 6 Samsung 1 TB SATA disks The Samsung disks form the pool I'm having trouble with. They are connected to the Promise controllers. Does anyone know how I can debug this? I'm not even sure whether it is a software or a hardware problem. Any help is greatly appreciated! Regards, Thomas ___ 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
