Re: Crashing repeatedly: 6.2-RELEASE-p5 and MySQL 5.0.41
Yes i agree with everything. Definetly mysql need to be tuned for InnoDB and in general . As stated in the previous post my a collegue of mine i had to install a new kernel to have a consistent crash coredump. Anyway still in my mind is that even if not tuned mysql should not cause my kernel to panic, i could expect a mysql crash or very very poor performance ... but the kernel panic leave me confused. I will post on this thread my coredump as soon as the server crash again (and it will) ... surely i will tune mysql then and see if and how much this helps. thanks On Feb 5, 2008 7:37 PM, Tom Samplonius [EMAIL PROTECTED] wrote: - Primeroz lists [EMAIL PROTECTED] wrote: Hi all, we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2). FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram. MySQL Version is 5.0.41 with following configuration settings: set-variable= key_buffer=768M set-variable= table_cache=800 set-variable= sort_buffer=24M set-variable= myisam_sort_buffer_size=256M set-variable= record_buffer=16M set-variable= max_allowed_packet=10M set-variable= thread_stack=128K set-variable= join_buffer=512M set-variable= max_heap_table_size=256M set-variable= max_connections=300 set-variable= tmp_table_size=384M set-variable= query_cache_size=402653184 set-variable= query_cache_limit=134217728 set-variable= read_rnd_buffer_size=10M set-variable= ft_min_word_len=1 pid-file= /var/db/mysqld.pid tmpdir = /var/tmp ft_stopword_file = '' set-variable= thread_cache_size=80 set-variable= myisam_stats_method=nulls_equal Also, myslq is not really well tuned. The query cache is a kludge. It is helpful, if you have stupid application that issues the same query over and over again, even though the database has not changed. If you don't have this problem, it just adds overhead. And quite a lot, if it is big. Generally, the query cache should be 20 to 100M at most, if not disabled. If you have a smart web application (anything using memcached), the query cache should just be turned off. It will actually be faster. You should give us much storage as possible to the database engine, for it cache actual data, not query results. It is weird that you are apparently are heavily using Innodb, but you have just set various myiasam values? Here is something useful: http://www.joyeur.com/2007/09/25/quick-wins-with-mysql Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
finstall alpha3
Hi, As some of you may already know, I'm working on a graphical installer for FreeBSD 7, which was started as a Google SoC 2007 project but still continues. Usually I'd announce a new build on blogs.freebsdish.org but it's currently down and anyway maybe it's time for a wider exposure. The latest build can be found at http://ivoras.sharanet.org/stuff/freebsd7-finstall-alpha3.iso.bz2 with MD5 fingerprint of 4a11b172ed1c3030f530028a56f88ece. This is a i386 build as I don't have an amd64 development machine. Caveat! This is to be considered alpha-quality software. In particular, it still can't do any of the following things: - install on an already partitioned drive (so it's practically only usable for experimentation in VMWare and similar tools) - configure any of the more advanced features like RAID, X11 and sound - configure system locale similar features On the other hand, here's what it *can* do currently: - it's a live CD environment, completely like an already installed FreeBSD system, only running from a read-only media (e.g. it's usable as a FixIt system) - it installs both the base system (7.0-RC1) and a pre-selected set of packages which includes X.Org 7.3, XFce desktop 4.4, Firefox and Thunderbird - supports UFS, UFS+gjournal, ZFS and Ext2 (only UFS has been well tested). - configure simple services like ssh, ntpdate, bsdstats For those who tried earlier versions, the major changes are: - several subtle bugs are fixed - implemented ZFS support with proper tuning in loader.conf - added bsdstats package in the default set I'd like to hear impressions and suggestions of potential users. Some of the obvious features (like install on a already partitioned drive) will be done in time for, or slightly after, 7.0 gets released (a rudimentary support for remote installs will also be present), some features (RAID) will almost certainly get done later. Anything other will require time and probably sponsorship. I'm also interested in possible contributions to the project. In particular, it needs many UI strings to be filled in (many of the text labels and help texts are only placeholders). Interested people should know how to use Subversion. The project is hosted on SourceForge at http://sourceforge.net/projects/finstall - Perforce was avoided to allow access to people without FreeBSD developer accounts. I'd like to thank Google for the SoC project funding, Murray Stokely who was the mentor during the SoC and many other people who have helped. signature.asc Description: OpenPGP digital signature
Re: Did something change with DHCP?
On Tue, 5 Feb 2008 20:28:02 +0100 Christian Baer wrote: Greetings, people! Never mind about this thing. Problem was solved. I must have had a mental blackout today. Resetting the dhcp-leases did the trick. Regards Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finstall alpha3
Ivan Voras wrote: As some of you may already know, I'm working on a graphical installer for FreeBSD 7, which was started as a Google SoC 2007 project but still continues. 10+ years back when Jordan did first pre= X, 24x80 graphical installer, soon afer he'd finished a blind chap posted ~So how do I install ?~ Answer then: ~Get a friend do it for you, or abandon FreeBSD use NetBSD~ NetBSD still have Ascii installer, so more attractive to some. Idea for another SOC project : An automated tool that could descramble all the glitz of [arbitrary ?] graphics tools back to something sensible / Ascii, a bit like what OCR does for printed paper. No doubt a bew grraphical installer might be nice (if X is reliable which it often is Not, don't rely on VESA either on old hardware), but just so's we don't forget blind too, amazingly they use computers (with expensive interfaces). Also visually impaired do too, the later simply with simple text xterms with Monster fonts, rather than graphics I presume. -- Julian Stacey. BSD Unix Linux Net Consultant, Munich. http://berklix.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finstall alpha3
Julian H. Stacey wrote: Ivan Voras wrote: As some of you may already know, I'm working on a graphical installer for FreeBSD 7, which was started as a Google SoC 2007 project but still continues. 10+ years back when Jordan did first pre= X, 24x80 graphical installer, soon afer he'd finished a blind chap posted ~So how do I install ?~ Answer then: ~Get a friend do it for you, or abandon FreeBSD use NetBSD~ Good advice, in a BOFH kind of way :) The installer is actually separated into a front-end (GUI) and the back-end, with the idea that both be interchangeable. In the long term, someone may write a text-based front-end, if it is needed. The actual usability of finstall will come with the more advanced features, like configuring GEOM RAID, etc. Even now it can set up UFS+gjournal or ZFS file systems for users who want it. It will not replace sysinstall immediately, but it might, given time. I hope to preach about it on BSDCan :) signature.asc Description: OpenPGP digital signature
[releng_7_0 tinderbox] failure on i386/i386
TB --- 2008-02-06 10:50:01 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-06 10:50:01 - starting RELENG_7_0 tinderbox run for i386/i386 TB --- 2008-02-06 10:50:01 - cleaning the object tree TB --- 2008-02-06 10:50:30 - cvsupping the source tree TB --- 2008-02-06 10:50:30 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_0/i386/i386/supfile TB --- 2008-02-06 10:50:40 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-06 10:50:40 - cd /src TB --- 2008-02-06 10:50:40 - /usr/bin/make -B buildworld World build started on Wed Feb 6 10:50:41 UTC 2008 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Wed Feb 6 11:53:41 UTC 2008 TB --- 2008-02-06 11:53:41 - generating LINT kernel config TB --- 2008-02-06 11:53:41 - cd /src/sys/i386/conf TB --- 2008-02-06 11:53:41 - /usr/bin/make -B LINT TB --- 2008-02-06 11:53:42 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-02-06 11:53:42 - cd /src TB --- 2008-02-06 11:53:42 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Feb 6 11:53:42 UTC 2008 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] : hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue vers.c linking kernel hptrr_os_bsd.o(.data+0x0): multiple definition of `hpt_dbg_level' entry.o(.bss+0x0): first defined here *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-06 12:08:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-06 12:08:30 - ERROR: failed to build lint kernel TB --- 2008-02-06 12:08:30 - tinderbox aborted TB --- 3976.78 user 392.48 system 4709.47 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_0-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7_0 tinderbox] failure on amd64/amd64
TB --- 2008-02-06 10:50:01 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-02-06 10:50:01 - starting RELENG_7_0 tinderbox run for amd64/amd64 TB --- 2008-02-06 10:50:01 - cleaning the object tree TB --- 2008-02-06 10:50:34 - cvsupping the source tree TB --- 2008-02-06 10:50:34 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7_0/amd64/amd64/supfile TB --- 2008-02-06 10:50:42 - building world (CFLAGS=-O2 -pipe) TB --- 2008-02-06 10:50:42 - cd /src TB --- 2008-02-06 10:50:42 - /usr/bin/make -B buildworld World build started on Wed Feb 6 10:50:43 UTC 2008 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything stage 5.1: building 32 bit shim libraries World build completed on Wed Feb 6 12:18:04 UTC 2008 TB --- 2008-02-06 12:18:04 - generating LINT kernel config TB --- 2008-02-06 12:18:04 - cd /src/sys/amd64/conf TB --- 2008-02-06 12:18:04 - /usr/bin/make -B LINT TB --- 2008-02-06 12:18:04 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-02-06 12:18:04 - cd /src TB --- 2008-02-06 12:18:04 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Feb 6 12:18:04 UTC 2008 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] : hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue vers.c linking kernel hptrr_os_bsd.o(.data+0x0): multiple definition of `hpt_dbg_level' entry.o(.bss+0x0): first defined here *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-02-06 12:31:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-02-06 12:31:07 - ERROR: failed to build lint kernel TB --- 2008-02-06 12:31:07 - tinderbox aborted TB --- 5117.09 user 551.29 system 6066.05 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7_0-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finstall alpha3
Julian H. Stacey wrote: Ivan Voras wrote: As some of you may already know, I'm working on a graphical installer for FreeBSD 7, which was started as a Google SoC 2007 project but still continues. 10+ years back when Jordan did first pre= X, 24x80 graphical installer, soon afer he'd finished a blind chap posted ~So how do I install ?~ Answer then: ~Get a friend do it for you, or abandon FreeBSD use NetBSD~ NetBSD still have Ascii installer, so more attractive to some. Idea for another SOC project : An automated tool that could descramble all the glitz of [arbitrary ?] graphics tools back to something sensible / Ascii, a bit like what OCR does for printed paper. No doubt a bew grraphical installer might be nice (if X is reliable which it often is Not, don't rely on VESA either on old hardware), but just so's we don't forget blind too, amazingly they use computers (with expensive interfaces). Also visually impaired do too, the later simply with simple text xterms with Monster fonts, rather than graphics I presume. Just my opinion: Maybe you are great BUT YOU ARE TO DEROGATORY about a work witch may be usefull to some new users Henri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dmesg : no output on 1 of 2 7-stable boxes
Hello Julian, I'm sorry this is a late reply, but I noticed your post on the freebsd-stable list just now. Julian H. Stacey wrote: One of 2 laptops running 7-stable shows nothing with dmesg, (other is OK). Did you try dmesg -a? The dmesg buffer is a circular buffer containing both kernel output and console output. However, dmesg displays only the kernel output. If there was lots of console output, it filled all of the dmesg buffer, so dmesg displays nothing (all of the kernel output was overwritten by console output). dmesg -a will display everything, i.e. kernel + console output. If dmesg -a doesn't print anything either, I'm afraid I have no idea what might be wrong. Well, you could try sysctl -b kern.msgbuf which will retrieve the raw contents of the dmesg buffer. - I tried loader.confkern.msgbuf=64000 I think it must be a multiple of the pages size, i,e, 4K = 4096 on FreeBSD/i386. I usually set it to 65536 or 131072. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Python tricks is a tough one, cuz the language is so clean. E.g., C makes an art of confusing pointers with arrays and strings, which leads to lotsa neat pointer tricks; APL mistakes everything for an array, leading to neat one-liners; and Perl confuses everything period, making each line a joyous adventure wink. -- Tim Peters ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finstall alpha3
Henri Hennebert wrote 2 emails with same common text To: Julian H. Stacey [EMAIL PROTECTED] Date: Wed, 06 Feb 2008 15:20:38 +0100 Message-ID: [EMAIL PROTECTED] The first private shouting got answered. Then came To: freebsd-stable@freebsd.org Date: Wed, 06 Feb 2008 15:25:57 +0100 Message-id: [EMAIL PROTECTED] Assume Henri is too young to remember first graphical installer. Though a new graphical installer may be very nice as an option, let it not ever be the only way: Remember blind installers, non VESA supported consoles, non X recognised chips, serial line controlled installs, non intel/AMD platforms with broken graphics terminal support. (Sparc maybe ? more later ?) -- Julian Stacey. BSD Unix Linux Net Consultant, Munich. http://berklix.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG_7: interrupt eating whole cpu core
While ripping DVDs the irq14: ata0 eats ~95% of one of my cores. The channel is exclusive to the drive. # atacontrol list 64 /root ATA channel 0: Master: acd0 Optiarc DVD RW AD-7560A/DH10 ATA/ATAPI revision 7 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: ad4 ST9160821AS/3.BHE Serial ATA v1.0 Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: no device present Slave: no device present The number of interrupts looks reasonable to me. # vmstat -i 0 /root interrupt total rate irq1: atkbd0 35171 1 irq9: acpi015729 0 irq12: psm010004 0 irq14: ata0 5148195272 irq16: pcm0 uhci0 40783 2 irq17: uhci1+1446238 76 irq18: bge0 ehci0+ 38588 2 irq20: uhci2 ehci1125447 6 irq21: uhci3 156783 8 cpu0: timer 37792079 1999 cpu1: timer 37784062 1999 Total 82593079 4370 I'm currently rebuilding world+kernel. I will report weather the behaviour has changed. This is an HP 6510b GR695EA#ABD, if anyone thinks it might be helpful, I can supply you with a dmesg and the output of pciconf -lv. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_7: interrupt eating whole cpu core
Dominic Fandrey wrote: While ripping DVDs the irq14: ata0 eats ~95% of one of my cores. The channel is exclusive to the drive. ... behaviour has changed. This is an HP 6510b GR695EA#ABD, if anyone thinks it might be helpful, I can supply you with a dmesg and the output of pciconf -lv. The problem remains with fresh sources: PID USERNAME THR PRI NICE SIZERES STATE C TIMECPU COMMAND 12 root 1 171 ki31 0K16K RUN0 22:04 97.85% idle: cpu0 37 root 1 -64- 0K16K CPU1 1 2:35 96.00% irq14: ata0 11 root 1 171 ki31 0K16K RUN1 19:32 6.40% idle: cpu1 The rip is done by k3b, so the drive is accessed through the cam interface. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_7: interrupt eating whole cpu core
Hi, Dominic-- On Feb 6, 2008, at 11:12 AM, Dominic Fandrey wrote: behaviour has changed. This is an HP 6510b GR695EA#ABD, if anyone thinks it might be helpful, I can supply you with a dmesg and the output of pciconf -lv. The problem remains with fresh sources: PID USERNAME THR PRI NICE SIZERES STATE C TIMECPU COMMAND 12 root 1 171 ki31 0K16K RUN0 22:04 97.85% idle: cpu0 37 root 1 -64- 0K16K CPU1 1 2:35 96.00% irq14: ata0 11 root 1 171 ki31 0K16K RUN1 19:32 6.40% idle: cpu1 The rip is done by k3b, so the drive is accessed through the cam interface. What are the values being reported by sysctl hw.ata? If you're going to be burning CD/DVDs, you really want to make sure hw.ata.atapi_dma is on. Regards, -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_7: interrupt eating whole cpu core
Chuck Swiger wrote: Hi, Dominic-- On Feb 6, 2008, at 11:12 AM, Dominic Fandrey wrote: behaviour has changed. This is an HP 6510b GR695EA#ABD, if anyone thinks it might be helpful, I can supply you with a dmesg and the output of pciconf -lv. The problem remains with fresh sources: PID USERNAME THR PRI NICE SIZERES STATE C TIMECPU COMMAND 12 root 1 171 ki31 0K16K RUN0 22:04 97.85% idle: cpu0 37 root 1 -64- 0K16K CPU1 1 2:35 96.00% irq14: ata0 11 root 1 171 ki31 0K16K RUN1 19:32 6.40% idle: cpu1 The rip is done by k3b, so the drive is accessed through the cam interface. What are the values being reported by sysctl hw.ata? If you're going to be burning CD/DVDs, you really want to make sure hw.ata.atapi_dma is on. I cannot believe it was so trivial. The sysctl looks all right. # sysctl hw.ata 0 /root hw.ata.wc: 1 hw.ata.atapi_dma: 1 hw.ata.ata_dma: 1 But further research revealed: # atacontrol mode acd0 0 /root current mode = PIO4 # atacontrol mode acd0 udma330 /root changed the load dramatically: PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 12 root 1 171 ki31 0K16K RUN0 52:54 100.00% idle: cpu0 11 root 1 171 ki31 0K16K CPU1 1 23:36 94.29% idle: cpu1 1087 kamikaze 3 -80 133M 36168K physrd 1 1:09 3.17% k3b 37 root 1 -64- 0K16K WAIT 1 30:10 0.00% irq14: ata0 Thank you very much! I used to think that UDMA33 was the default for CD-/DVD-Rom drives. I suppose I should review the BIOS settings or change something in the hints file. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finstall alpha3
Julian Stacey wrote: Henri Hennebert wrote 2 emails with same common text To: Julian H. Stacey [EMAIL PROTECTED] Date: Wed, 06 Feb 2008 15:20:38 +0100 Message-ID: [EMAIL PROTECTED] The first private shouting got answered. Then came To: freebsd-stable@freebsd.org Date: Wed, 06 Feb 2008 15:25:57 +0100 Message-id: [EMAIL PROTECTED] Assume Henri is too young to remember first graphical installer. Thank you! I'm 60 this year :-) and using FreeBSD since 2.1. Xenix since 88 IIRC. My point is that a graphical installer may be usefull, that's all. Though a new graphical installer may be very nice as an option, let it not ever be the only way: Remember blind installers, non VESA supported consoles, non X recognised chips, serial line controlled installs, non intel/AMD platforms with broken graphics terminal support. (Sparc maybe ? more later ?) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Reconstruct disklabel for UFS and GELI volumes
Hi, Somehow[TM] an installation of 4.11 to ad0s3 managed to wipe out my existing disklabel for 7.0 on ad0s4. I now need to recover the disklabel to get my system to boot! There were three labels - ad0s4a: UFS, exact size unknown. Is it possible to infer this from the UFS partition size? I can mount this already, as I simply wrote an 'a' label of maximum size to the disklabel - ad0s4b: GELI encrypted swap - ad0s4d: GELI encrypted ZVOL I only need to find out the start of ad0s4d. Is the consumer size of an GELI device stored in the last 512 bytes metadata? Or are there some magic bytes in this 512 bytes so I could find out the exact end of ad0s4b and thus the start of ad0s4d? Any help or advice would be highly appreciated! Thanks, Uli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: finstall alpha3
Henri Hennebert wrote: Julian Stacey wrote: Henri Hennebert wrote 2 emails with same common text To: Julian H. Stacey [EMAIL PROTECTED] Date: Wed, 06 Feb 2008 15:20:38 +0100 Message-ID: [EMAIL PROTECTED] The first private shouting got answered. Then came To: freebsd-stable@freebsd.org Date: Wed, 06 Feb 2008 15:25:57 +0100 Message-id: [EMAIL PROTECTED] Assume Henri is too young to remember first graphical installer. Thank you! I'm 60 this year :-) and using FreeBSD since 2.1. Xenix since 88 IIRC. My point is that a graphical installer may be usefull, that's all. Chuckle :-) Looks like we reach agreement :-)) -- Julian Stacey. BSD Unix Linux Net Consultant, Munich. http://berklix.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
synaptics problem
Hi, I've recently installed FreeBSD 6.3, and I've got a problem with synaptics. I've installed it, followed the pkg-message : hw.psm.synaptics_support=1 It works, dmesg gives : psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 moused_enable=NO ps shows me that moused doesn't run. xorg.conf : InputDevice Synaptics_TouchpadCorePointer ... Section InputDevice Identifier Synaptics_Touchpad Driver synaptics Option Device/dev/psm0 Option Protocol psm ... And here is a part of Xorg.log : (WW) default pointer: No Device specified, looking for one... (II) default pointer: Setting Device option to /dev/psm0 (--) default pointer: Device: /dev/psm0 (==) default pointer: Protocol: Auto ... Synaptics DeviceInit called SynapticsCtrl called. (II) default pointer: SetupAuto: hw.iftype is 3, hw.model is 13 (II) default pointer: SetupAuto: protocol is SysMouse (WW) fcntl(15, O_ASYNC): Inappropriate ioctl for device Synaptics DeviceOn called (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (WW) Synaptics_Touchpad: cannot open input device couldn't enable device 3 Protocol isn't psm, why ? Can I force it ? /dev/psm0 isn't used or it is used by Xorg (I saw it with fstat) any idea ? I didn't had this problem with 6.2 but may be I wasn't up to date with xorg. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount -p and NFS options
On Tue, 5 Feb 2008, Dan Nelson wrote: In the last episode (Feb 04), Mike Andrews said: Is there anything like mount -p that will print the current NFS options in use? TCP vs UDP, v2 vs v3, read/write sizes etc. It doesn't have to be in fstab format; I just need to be able to see what the flags are for an active mount. This would be useful in tracking down an irritating NFS problem I've been experiencing with diskless systems in every 6.x release and 7.0-RC1, namely libc.so.6 appears to be truncated or corrupt to the client at somewhat random times... I think it may be related to mount options, hence the question. Theoretically, any filesystem that uses nmount(2) should have its options recored in an easy-to-extract format, since one of the arguments to nmount is an array of options. I patched my kernel and /sbin/mount binary to do this (borrowing the f_charspare field in struct statfs), and it mostly works. The stuff below in brackets are from the options array. You can see that cd9660 was mounted with the option ssector=0: [snip] Unfortunately, mount_nfs simply calls nmount with a single nfs_args option whose value is the same binary struct nfs_args it used to call mount(2) with :( The fix would be to make nfs_vfsops.c and mount_nfs.c use the options array instead of a custom struct, but nfs_vfsops.c:nfs_decode_args scares me off every time I look at it. Hm. Well, that's a bummer. But it at least told me where to hack in some temporary printf() calls, and that helped me narrow my immediate problem down to the rsize/wsize parameters. My problem was, on a diskless 7.0-RC1 system, trying to compile anything resulted in ld SIGSEGV'ing. With diskless 6.3 ld said that libc.so.6 was truncated. ktrace hinted that 7.0's ld crash was right after reading libc.so.7 so it's probably the same issue -- problems reading libc. The problem goes away if I change rsize/wsize from 32K down to 16K or the default 8K, at least with TCP mounts. So for now in /boot/loader.conf I'm using boot.nfsroot.options=nfsv3 tcp rsize=8192 wsize=8192. (NFS options for the root filesystem in fstab seem to be ignored.) I don't know why it was libc consistently getting misread and why other files seem to always work, or why mounting other NFS filesystems with a 32K blocksize work fine... unless I'm hitting some edge case that's specific to NFS root vs NFS anything-else. Anyway, I've got a workaround for now. (FWIW, this happened with two different machines, one with an msk NIC and one with an em NIC, neither of which have jumbo frames enabled.) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reconstruct disklabel for UFS and GELI volumes
On Wed, 06 Feb 2008 21:04:23 +0100 Ulrich Spoerlein [EMAIL PROTECTED] wrote: There were three labels Actually, it is one label per slice, unless you are doing something unusual? - ad0s4a: UFS, exact size unknown. Is it possible to infer this from the UFS partition size? I can mount this already, as I simply wrote an 'a' label of maximum size to the disklabel - ad0s4b: GELI encrypted swap - ad0s4d: GELI encrypted ZVOL These are partitions in BSD-speak. Any help or advice would be highly appreciated! FWIW, I have had success with scan_ffs[1] as documented in this short article[2]. It will recover lost labels, or at least try to. If you are downloading binary packages from somewhere, be sure to double check that you get the one that fits your platform (i386 / amd64 or whatever) and version. Take it slowly, and double check all steps before comitting anything. Good luck! References: 1) http://www.freshports.org/sysutils/scan_ffs/ 2) http://geekinfo.net/article.php?story=20071224175132586 -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reconstruct disklabel for UFS and GELI volumes
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Wed, 6 Feb 2008 21:04:23 +0100 Ulrich Spoerlein [EMAIL PROTECTED] wrote: Hi, Somehow[TM] an installation of 4.11 to ad0s3 managed to wipe out my existing disklabel for 7.0 on ad0s4. I now need to recover the disklabel to get my system to boot! There were three labels - ad0s4a: UFS, exact size unknown. Is it possible to infer this from the UFS partition size? I can mount this already, as I simply wrote an 'a' label of maximum size to the disklabel - ad0s4b: GELI encrypted swap - ad0s4d: GELI encrypted ZVOL I only need to find out the start of ad0s4d. Is the consumer size of an GELI device stored in the last 512 bytes metadata? Or are there some magic bytes in this 512 bytes so I could find out the exact end of ad0s4b and thus the start of ad0s4d? Hi Ulrich, Try to scan that disk with sysutils/testdisk: http://www.cgsecurity.org/wiki/TestDisk Best regards. - -- Nikola Lečić = Никола Лечић fingerprint : FEF3 66AF C90E EDC3 D878 7CDC 956D F4AB A377 1C9B -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iQCVAwUBR6pJVfzDP9K2CKGYAQMrxAP9Fxng2ZaHmgB5ID6ZTVfOwNTTDrzPNlMX FRlOIKnksldTzhUdk0UfsJP9kgYpEInz6gQ3unSlUSBDTgN9jSW6yQGM0fW4hZ3H 27Ge5frdzETXg91TRsx1aP24i3SezNHO0AYLQw9cbD7ftDVHH1yzkmZrxSP7kYJ/ YPge/g7YRKI= =h/6V -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: synaptics problem
Matthieu Bollot wrote: Hi, I've recently installed FreeBSD 6.3, and I've got a problem with synaptics. I've installed it, followed the pkg-message : hw.psm.synaptics_support=1 It works, dmesg gives : psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 moused_enable=NO ps shows me that moused doesn't run. xorg.conf : InputDevice Synaptics_TouchpadCorePointer ... Section InputDevice Identifier Synaptics_Touchpad Driver synaptics Option Device/dev/psm0 Option Protocol psm ... And here is a part of Xorg.log : (WW) default pointer: No Device specified, looking for one... (II) default pointer: Setting Device option to /dev/psm0 (--) default pointer: Device: /dev/psm0 (==) default pointer: Protocol: Auto ... Synaptics DeviceInit called SynapticsCtrl called. (II) default pointer: SetupAuto: hw.iftype is 3, hw.model is 13 (II) default pointer: SetupAuto: protocol is SysMouse (WW) fcntl(15, O_ASYNC): Inappropriate ioctl for device Synaptics DeviceOn called (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (WW) Synaptics_Touchpad: cannot open input device couldn't enable device 3 Protocol isn't psm, why ? Can I force it ? /dev/psm0 isn't used or it is used by Xorg (I saw it with fstat) any idea ? I didn't had this problem with 6.2 but may be I wasn't up to date with xorg. I think protocol has to stay auto. Is it possible that your Xorg.conf has more device sections? One of which already uses /dev/psm0? PS: On my new system the touchpad is recognized as an Intellimouse Explorer, no matter weather I set hw.psm.synaptics_support=1 or not. The Xorg synaptics driver rejects it, however, vertical scrolling works out of the box, even using moused. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
