Re: Looking for ipfw info.
Hi there, On Thu, Feb 26, 2004 at 01:13:08PM -0500, Shaun T. Erickson wrote: Thanks for the resources. A couple of questions (because I'm new to FreeBSD): The ipfw man page in 5.2.1-RELEASE says that ipfw in CURRENT is ipfw2 and that ipfw in STABLE is ipfw1. I still don't understand the releationship between RELEASE and the other two, so I am not sure which ipfw I have in 5.2.1-RELEASE. If you are using ipfw on 5.2.1 you have ipfw2. Brief summary: -STABLE is at the moment based on FreeBSD 4. -CURRENT is based on FreeBSD 5. A -RELEASE is a snapshot of the state of the code at a particular point in time. 5.2.1-RELEASE is based on FreeBSD 5. Perhaps this page can help explain: http://www.freebsd.org/releng/index.html There's also more detail on the various tags at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html To get ipfw2 on 4.9 you need to recompile with the ipfw2 option in the kernel config - the ipfw man page has a section on this aspect. On a version note, while I personally have not experienced any problems running 5.2.1 it is a bit more bleeding edge than 4.9 for example. 4.9 is recommended if you want maximum stability for the moment. I have read the following 5 excellent articles on ipfw, by Dru Lavigne. Even though they were written in 2001, and thus pre-date ipfw2, I found them to be a great crash course in ipfw, and the ipfw manpage in 5.2.1-RELEASE just adds to it. In Dru's first article, she(?) discusses how the kernel must be modified to support a firewall. She looks into /usr/src/sys/i386/conf/LINT to find the relevant information that needs to be added to my kernel conf file. I cannot find a LINT file on my 5.2.1-RELEASE system. Where can I find complete information on what I need to do to my kernel? 4.9 and older used LINT to list all options for kernel config, 5 and onwards use a file called NOTES. There's one of these under /usr/src/sys/conf (for machine independant bits) and another under /usr/src/sys/i386/conf for i386 related (also other arch have their own) Refer to the following pages for more info: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/kernelconfig.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html /etc/rc.firewall is the best place to start for some sample rules and the ipfw man page is really quite good. With 5.2.1 you should not need to recompile a kernel to use ipfw or any of the other supported firewalls (ipfilter and pf). Which firewall you choose to go with is your choice. If you intend to use ipfw divert rule and natd you will probably need to compile a new kernel with the divert option added to the kernel config, ie: options IPDIVERT If you have firewall_enable=YES in your /etc/rc.conf the kld should be loaded at boot time and the config will be pulled in from /etc/rc.firewall so you can start with firewall_type=SIMPLE or whatever to get you going. Basically start with the man pages they cover just about everything. There is also the faq: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/networking.html For natd specifically: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-natd.html There is a lot of good information on the FreeBSD website so start there. For ipfw specifically you can also search browse the freebsd-ipfw mailing list. For other firewalls you can find specific lists or try freebsd-net for some questions. In general search the archives first to see if your question isn't already answered. http://www.freebsd.org/search/search.html#mailinglists Hope it helps, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Growing RAID5 (using RAID0).
Hi there, On Thu, Feb 26, 2004 at 02:15:14PM +, Lewis Thompson wrote: I've been thinking about this and I'm wondering if it is possible to do something like the following: I have an existing RAID5 volume, comprised of just 3 120GB disks. However, I've just bought three more 250GB disks that I also want to RAID5. I would still like a single volume, comprising the size of the two RAID5 volumes. Could this be possible through the use of RAID0? In theory, yes. i.e. can I create a RAID0 volume from two RAID5 volumes? Depends on the raid implementation. I understand this might sound a little odd but if it works it would be the ideal solution for me. I would also be interested in hearing how other people might have overcome this problem of growing a large RAID5 volume. As you didnt post anything about your implementation I can only guess. If you are using hardware raid5 for each disk set and it cannot do raid0 on top you could look at using software raid0 to join the two hardware sets. Eg vinum can do raid0 in software over raid5 in hardware. If you are doing this purely in software it will depend on what software you use. If using vinum I believe you can only mirror across two (or more) raid5 plexes, so probably not what you want to do. If you want more specific solutions you will need to advise your hardware and software details including FreeBSD version. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum crashed
Hi there, On Thu, Feb 26, 2004 at 09:14:06AM +0100, Axel S. Gruner wrote: I setup a disk stripping with two disks and vinum. I was impressed about the quick and easy setup. The configuration is, that i installed FreeBSD 5.2.1-RC2 on /, a little bit of swap, and the gave the rest for vinum. So the two disks have both a bootable / and /usr and /var is on vinum. All went fine and was working. Yes, was... A colleague of mine went to the server, took the first HD out, and tried to boot. Crash. Single user mode. Thats it. (strange guy...). Ok, i put the second HD in, rebooted the server, and still found myself in single user. fsck on vinum does not work (but the filesystem wants to do a fsck). So i looked at vinum ls output an saw that vinum is marked as crashed. After a #vinum vinum -- start the stripping was up again. Happy happy joy joy i thought and i booted into multiuser mode. To test it out, i rebooted the machine, and, no more happy happy und no more joy joy, the system boots in single user mode, wants to fsck vinum, can not do that Yes, i know, it would be fine to post some error messages, but right now i dont have any access to that machine. So, what could be the problem, and how to solve it. I appreciate any hints. Do you include start_vinum=YES in your /etc/rc.conf ? It is likely given information about past working, but maybe it was lost/changed? After a subdisk has crashed the data is still valid so a 'vinum start' should bring the plex back online. This will then give you full access to your filesystems. At that point you should run fsck on the vinum volumes to ensure no errors. Anytime you start in single user mode you will need to begin with a 'vinum start' command at least to get vinum going unless you load vinum in /etc/loader.conf or something. To help any further we would need some specific error details. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RAID (ccd/vinum) with 2 harddisks
Hi, On Mon, Feb 23, 2004 at 08:32:40AM +0100, Axel S. Gruner wrote: Hi. Greg 'groggy' Lehey wrote: On Monday, 23 February 2004 at 8:27:33 +0100, Axel S. Gruner wrote: Hi. I want to use RAID on a IBM xSeries 345 with two harddisks. So the problem is, i can not setup a RAID System via Installation of FreeBSD (it will be 4.9 or maybe 5.2) and i do not have a System harddisk so that i can use the other ones as a RAID System. Is there a way to setup RAID (CCD otr Vinum) on a System with 2 harddisks (mirroring or stripping)? Yes. It's described in the man pages. Oh boy, i need a real large cup of coffee, or some glasses. In addition to the man pages I found these resources of particular use: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html and http://www.vinumvm.org/cfbsd/vinum.pdf From my own experience it can be done without much trouble. I burnt myself a few times in the process but that was mostly user fault. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clarification needed on Handbook: Tracking for Multiple Machines
Hi, On Mon, Feb 23, 2004 at 10:46:07AM -0600, D J Hawkey Jr wrote: On Feb 23, at 09:12 AM, M. Warner Losh wrote: In message: [EMAIL PROTECTED] D J Hawkey Jr [EMAIL PROTECTED] writes: : True or False: Setting CPUTYPE to the lowest target CPU (p2) in : a build machine's make.conf will cripple the performance of target : machines with higher CPUs (p3, p4, i586, i686, etc.). False. It might have a minor impact on performance, but not a major one. At least in my experience. Minor here means 10% for something like the world stone. Cripple to me implies 25%. OK, thanks. Just to satisfy my anal-retentive side, would that ~10% degradation be a higher level of performance on a PIII (or higher) with no CPUTYPE specified at all, given the same *FLAGS? Perhaps the easiest option is to actually try it and see what the results are? : If True, for optimized code across all machines, the code should : just be built on each machine, right? That would give slightly better performance. However, it can be more pain than it is worth if the number of machine types is high. Consuming considerably more time and disk space, a shell script to alter make.conf and rename /usr/obj between the build for each machine is doable, though pro'lly not worth it. The install at each each box would just have to mount it's corresponding /usr/obj tree. Just need to set __MAKE_CONF and MAKEOBJDIRPREFIX before running the build. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clarification needed on Handbook: Tracking for Multiple Machines
Hi, On Sat, Feb 21, 2004 at 11:23:28AM -0600, D J Hawkey Jr wrote: On Feb 21, at 05:56 PM, Gabriel Ambuehl wrote: DJHJ Second, two machines are of the same architecture, but they have different DJHJ CPUs: One is an Intel PIII, but the other is a PII. Will the world built DJHJ on a PIII be correct for a PII? Similarly, will the kernel for the PII DJHJ built on a PIII be correct for the PII, given the different variables and DJHJ settings in the two kernel configuration files? Just make sure you build for 686. If that doesn't work, make it 586 (I think the PI qualifies as 686 but I'm not entirely sure). I think the extensions such as SSE etc are detected dynamically and shouldn't cause any problem. In all my years of messing with builds, I never run into this problem, so I guess it's pretty safe. Yes, both [my] machines define I686_CPU. Dynamically, as in at runtime? I think you're right, but I don't know for certain, either. This is exactly what I'm wondering about; the PII has only MMX, for instance, while the PIII has SSE and MMX2. I assume the world's codebase is CPU-agnostic within an architecture, but I really don't want to assume this; I'd rather know this. I have PII, Celeron, PIII and P4 in my environment. All these use I686_CPU in my kernel configs (I got rid of the other I[345]_CPU types. In /etc/make.conf I include CPUTYPE=p2 as the lowest common denominator if including a CPUTYPE flag. The resulting world kernel run fine on all the systems. The higher flags p3 and p4 still just use -march=pentiumpro, however for SSE you will need p3 or p4 as MACHINE_CPU does not include SSE for p2 level. Check out /usr/share/mk/bsd.cpu.mk for specifics. DJHJ /etc/defaults/make.conf doesn't mention KERNCONF; /usr/src/Makefile.inc1 DJHJ does. Since /usr/share/mk/sys.mk sucks in /etc/make.conf, that should DJHJ propogate KERNCONF to /usr/src/Makefile, right? You can also just supply it on the command line when doing your make runs. Yes, but this means individual commands for each machine's kernel, as opposed to one command for all machines (think issue command and go to bed, or even an `at` command). Are you stating definitively that what I saw in the makefile chain isn't what is really there? To your original question, yes. Just add a KERNCONF= line to /etc/make.conf. First entry should be the local machine kernel (to install) and any subsequent entries will also be built during 'make buildkernel' eg: KERNCONF= MARVIN RAIDER RAIDERI GENERIC make buildkernel builds all four. make installkernel installs MARVIN. Good luck, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahc + vinum raid5 deadlocks?
Hi, Cross posting to -scsi as it seems maybe related to my scsi setup. At least, the problems currently only appear when the scsi parts are in use. On Sat, Feb 21, 2004 at 02:47:49PM +1100, Tony Frank wrote: Refer earlier thread on -stable for more background. 4.9-STABLE (cvsup 20th Feb) Kernel was compiled with DDB, INVARIANTS, DIAGNOSTICS. All options removed from /etc/make.conf except 'NOPROFILE=TRUE' I get the following on the console before system freezes: ahc0: WARNING no command for scb 14 (cmdcmplt) QOUTPOS = 44 This occured while doing majority of i/o to vinum raid5 volume. Since that time I have removed the vinum raid5 configuration and am using the disks directly - ufs mounted on /dev/da0s1h. When performing the same load benchmark I have received two separate panic's: First panic occurs due to KASSERT in ffs_read, refer: http://fxr.watson.org/fxr/source//ufs/ufs/ufs_readwrite.c?v=RELENG4#L316 (da0:ahc0:0:0:0): tagged openings now 40 (da1:ahc0:0:1:0): tagged openings now 40 (da2:ahc0:0:2:0): tagged openings now 40 (da3:ahc0:0:3:0): tagged openings now 40 Feb 21 15:48:16 raider su: tony to root on /dev/ttypc panic: bp-b_resid != 0 syncing disks... Stopped at siointr1+0x102: movl$0,brk_state2.757 db trace siointr1(c0f98000,ccdc6c64,c027d546,c0f98000,10) at siointr1+0x102 siointr(c0f98000,10,0,0,0) at siointr+0xb Xfastintr4(c1090800,140,600,20002,ccd54300) at Xfastintr4+0x16 lockmgr(c1090800,1030002,ccd5436c,c032c7a0,ccdc6cac) at lockmgr+0x1fc vop_stdlock(ccdc6cc4,ccdc6cd4,c01bb269,ccdc6cc4,0) at vop_stdlock+0x20 ufs_vnoperatespec(ccdc6cc4) at ufs_vnoperatespec+0x15 vn_lock(ccd54300,20002,c032c7a0,c1129000,0) at vn_lock+0x71 ffs_sync(c1129000,2,c0b2d600,c032c7a0,c1129000) at ffs_sync+0x17f sync(c032c7a0,0,c02b9660,c02d6048,100) at sync+0x63 boot(100,0,0,ccdc6de0,c02482a2) at boot+0x8a panic(c02d6048,ccf5cbc0,5b,ccd8f000,400) at panic+0x79 ffs_read(ccdc6df4,0,ccdc6ea8,c02ec1e0,ccf5cbc0) at ffs_read+0x37a ufs_readlink(ccdc6e38,ccdc6e68,c01b1c8a,ccdc6e38,c7f7bee0) at ufs_readlink+0x6b ufs_vnoperate(ccdc6e38,c7f7bee0,c7f7bee0,ccdc6f80,c7f7bee0) at ufs_vnoperate+0x15 namei(ccdc6e80,c7f7bee0,2,ccdc6f80,8137400) at namei+0x302 stat(c7f7bee0,ccdc6f80,bfbe7810,bfbe8298,bfbea49c) at stat+0x41 syscall2(c027002f,2f,2f,bfbea49c,bfbe8298) at syscall2+0x209 Xint0x80_syscall() at Xint0x80_syscall+0x25 db I have a core from this panic saved. 'trace' is about the extent of my ddb skills at the moment though. Checking the archives a similar problem was seen ~6months ago with particular SCSI disk and having too high tags value. Refer: http://docs.freebsd.org/cgi/mid.cgi?FE045D4D9F7AED4CBFF1B3B813C8533702741FEA From what I can see, the ahc driver is forcing a max of 40 tags. The SCSI hardware is fairly old but was working without problems in the old system (Win based) Second panic occurs in ffs_softdep, refer: http://fxr.watson.org/fxr/source//ufs/ffs/ffs_softdep.c?v=RELENG4#L3590 Feb 21 17:16:30 raider su: tony to root on /dev/ttyp8 (da1:ahc0:0:1:0): tagged openings now 40 Feb 21 17:21:29 raider su: tony to root on /dev/ttyp3 (da3:ahc0:0:3:0): tagged openings now 40 (da2:ahc0:0:2:0): tagged openings now 40 panic: handle_written_inodeblock: live inodedep syncing disks... Stopped at siointr1+0x102: movl$0,brk_state2.757 db trace siointr1(c0f98000,ccf6bba0,c027d546,c0f98000,10) at siointr1+0x102 siointr(c0f98000,10,0,8,68c040) at siointr+0xb Xfastintr4(c389c20c,10,c02be0a4,0) at Xfastintr4+0x16 biowait(c389c20c,c106b800,c11d1900,2,c02ec760) at biowait+0x37 bread(ccaaba00,18c040,2000,0,ccf6bc14) at bread+0xb2 ffs_update(ccd51c00,0,68c040,ccd51c00,ccf33580) at ffs_update+0xba ffs_fsync(ccf6bc78) at ffs_fsync+0x358 ffs_sync(c1069c00,2,c0b2d600,c032c7a0,c1069c00) at ffs_sync+0xdb sync(c032c7a0,0,c02b9660,c02d56e0,100) at sync+0x63 boot(100,0,c127bb00,ccf6bd18,c024416a) at boot+0x8a panic(c02d56e0,1,c11a5c80,c38d6178,0) at panic+0x79 handle_written_inodeblock(c11a5c80,c38d6150) at handle_written_inodeblock+0x30e softdep_disk_write_complete(c38d6150) at softdep_disk_write_complete+0x6a biodone(c38d6150,1,68c040,c10efa48,c38d6150) at biodone+0x121 complete_rqe(c10efa20,0,c1028c00,f76,c1028d3c) at complete_rqe+0x651 biodone(c10efa20,c1028cb8,c10efa20,c0146d58,c16caac0) at biodone+0xf5 ad_interrupt(c16caac0,c032b7d4,ccf6be38,c0182482,c0fa7900) at ad_interrupt+0x3e7 ata_intr(c0fa7900,c16ccdc0,ccf6be8c,c027e4c2,c032b7d4) at ata_intr+0xd8 add_interrupt_randomness(c032b7d4,0,10,c3870010,c01a0010) at add_interrupt_rando mness+0xe Xresume15() at Xresume15+0x2b --- interrupt, eip = 0xc01ab6e5, esp = 0xccf6be80, ebp = 0xccf6be8c --- bwillwrite(c16ccdc0,ccf6bf80,cce7b2a0,0,0) at bwillwrite+0x75 dofilewrite(cce7b2a0,c16ccdc0,a,824a00c,f76) at dofilewrite+0xa2 write(cce7b2a0,ccf6bf80,824a00c,bfbff7e0,bfbff800) at write+0x36 syscall2(bfbf002f,bfbf002f,822002f,bfbff800,bfbff7e0) at syscall2+0x209 Xint0x80_syscall() at Xint0x80_syscall+0x25 db My searches show a few hits
Re: dialup question ?
Hi, On Fri, Feb 20, 2004 at 07:37:49PM -0300, Roberto Pereyra wrote: A question: I want to configure a simple dial-up server and have this ppp.conf -- default: pap: set debug phase lcp chat set timeout 0 set debug phase lcp chat enable pap set ifaddr 192.168.0.1 192.168.0.101-192.168.0.104 255.255.255.0 enable proxy accept dns set dns 192.168.0.1 load server set radius /etc/radius.conf My dial-up server (192.168.0.170) is not the internet gateway (192.168.0.1) The line: set ifaddr 192.168.0.1 192.168.0.101-192.168.0.104 255.255.255.0 is right ? the first ip must be the system gateway or must be the dial-up server ip ? I think it should be the gateway as you are going to be proxying the dialup users onto your local LAN. The dialup box will proxy-arp the dialup users to the LAN and will forward their packets to the gateway. I have a similar setup to what you describe. In my case the dialup is also the gateway which makes it simpler. My config is: server: set timeout 0 set enddisc mac enable chap chap81 pap passwdauth enable proxy set ifaddr 192.168.3.2 192.168.3.80-192.168.3.100 255.255.255.255 set server /var/run/ppp/ppp-server-%d 0177 set dns 192.168.3.2 set nbns 192.168.3.2 accept dns Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Custom startup+shutdown scripts
Hi there, On Fri, Feb 20, 2004 at 01:38:39PM -, Dominic Bishop wrote: I am shortly going to try and install a Belkin universal UPS on one of my FreeBSD machines running 5.2 using the nut utility. Something I've been thinking of doing for many months now. Due to a failing in the Belkin protocol it requires some custom startup/shutdown scripting to make it work in an unsupervised recovery, [ snip ] The startup script needs to be run before disks are mounted in read/write and before filesystem checks for similar reasons. I've looked through some of the rc scripts, namely rc.shutdown and a few others but really aren't sure as to where I should make these changes so they execute at the correct time in the boot/shutdown process. Could anyone tell me where I should be making these additions? I'm in a 4.9-STABLE world and there I think it would be fairly straightforward: Based on my understanding - init(8) is a good place to start - init will run /etc/rc.shutdown before it finally powers off/reboots during a shutdown. It currently does not unmount local filesystems, but you could add to the rc.shutdown script at the end to unmount the local filesystems and then perform your extra actions. At startup you have a standard hook that will call /etc/rc.early if it exists. You should be able to add whatever extra functions you need in here. Note that this will be before filesystem checks are done etc. Root will be mounted ro at this point. I understand the rc system has changed a lot with 5.2 so I dont know how much this will help you. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP access
Hi, On Fri, Feb 20, 2004 at 04:05:54PM -0800, Jim Pazarena wrote: I have a wireless home network with an 802.11B router which assigns IPs via DHCP. what method is appropriate to access one fbsd box from another when I don't actually know the IP which has been assigned to any given box. May sound rookie, but presently I go to each box and determine it's IP directly and then I know the IP (at least for this session). There has gotta be a better way. suggestions please. Does you router/dhcp support static assignment? Basically you program fbsd 1 MAC address to always be assigned IP 1 and so forth. Otherwise you might consider using static address on your fbsd system? Ie if router is doing dhcp from 192.168.0.100-192.168.0.150 you should be able to static configure fbsd 1 as 192.168.0.1 for example. Just dont use the address of the router/gateway. Another option is dynamic dns updates - if your router/dhcp also provides dns you can either configure dhcp server or client to update dns with new address. Finally another idea is to use something like dyndns.org with each fbsd box. ddclient from ports will hook into DHCP and submit whatever address you get to dyndns.org. Works great for the public address, not sure if it will do private addresses but worth a shot. Then you'd give each box a name and register it on dyndns (or one of the many other equivalent sites) To talk to the other box you then just need to use the name which is updated. Hope there's something there for you, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB modem support?
Hi, On Sat, Feb 21, 2004 at 02:26:24AM +, Daniela wrote: I'm having problems with an USB ADSL modem (Alcatel Speed Touch). It is recognized at boot time, but when I try to connect, it tells me that the modem is busy. I symlinked /dev/cuaa3 to /dev/ugen1 (that's the device that showed up in the boot messages) and directed the kppp utility to use /dev/cuaa3. I entered all the information it asked me for, and then I got the error message: Modem is busy. My ISP told me to f*** off and get Windoze. Anything else is unsupported. Is it a hardware problem or a classical case of a dumb user? I'm not unexperienced with Ethernet connections, and I have a great knowledge of the TCP/IP standard, but I have never done anything with modems, so I can't even imagine how this stuff works. Have you tried: FreeBSD Handbook: http://marvin.home.local/doc/en_US.ISO8859-1/books/handbook/pppoa.html Or ports collection: http://www.freebsd.org/cgi/ports.cgi?query=speedtouchstype=all Port: pppoa-1.2b3,1 Path: /usr/ports/net/pppoa Info: Run PPP over Alcatel's USB Speedtouch device Maint: [EMAIL PROTECTED] Index: net B-deps: R-deps: Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS and different exports to the same host
Hi there, On Fri, Feb 20, 2004 at 09:17:37PM -0600, dap wrote: Per the FreeBSD handbook, I have to follow the rule that for a specific host I have to export everything the same for a particular filesystem. So let's say I have one filesystem, /. So I can't have: /export1-roserver1 server2 /export2 server1 Instead, I need: /export1 \ /export2 \ server1 Is there a way around this? Each filesystem can only be exported with one set of attributes to a particular host. If both /export1 and /export2 are directories of / then you would do: /export1 /export2 -ro server1 /export1 -ro server2 But note that the same attributes apply - ie both ro or both rw. If you need to give ro on one and rw to the other then you need to make them separate filesystems. See below for a way to do this. From the handbook: In /etc/exports, each line represents the export information for one filesystem to one host. A remote host can only be specified once per filesystem, and may only have one default entry. For example, assume that /usr is a single filesystem. The following /etc/exports would be invalid: /usr/src client /usr/ports client One filesystem, /usr, has two lines specifying exports to the same host, client. The correct format for this situation is: /usr/src /usr/ports client The properties of one filesystem exported to a given host must all occur on one line. Lines without a client specified are treated as a single host. This limits how you can export filesystems, but for most people this is not an issue. eg I have in my /etc/exports file: /data/ad2 -alldirs -maproot=root -network 192.168.0.0 -mask 255.255.0.0 /data/ad3 -alldirs -maproot=root -network 192.168.0.0 -mask 255.255.0.0 /usr -alldirs -ro -network 192.168.0.0 -mask 255.255.0.0 /usr /usr/local -maproot=0:10 group1 /usr -ro -mapall=nobody /tmp -maproot=root group1 /tmp group2 /cdrom -alldirs,quiet,ro -network 192.168.3.0 -mask 255.255.255.0 So you can export the one filesystem (/usr or /tmp here) to different places with different attributes. You cannot have different attributes for same filesystem + same host. So if I had a host in both group1 and group2 in this example it would break. I have found that it works best for us to have a /exports, where we dump things like /exports/www, /exports/mail, and so on, rather than having filesystems for each of those. This is important since FreeBSD has a limitation on the number of possible slices, and we are running with one big RAID-1 storage system. If you want to break up a single disk into many pieces you might want to look at using vinum for this. If you are using hardware raid already you can make the virtual disk a vinum drive and then break it up into as many subdisks as you like. Eg a config like: drive hwraid1 device /dev/da0s1h volume www plex org concat sd drive hwraid1 len 2G volume mail plex org concat sd drive hwraid1 len 2G While it adds an extra layer it should not be too much of an overhead. You can also then add as many filesystems as you like, but they cannot share the same total disk. You could however add extra subdisks if more space is needed and run growfs to increase room if it is needed. Also, I found that this generates errors (by mountd -r): /export1 -maproot=nobody \ /export2 -maproot=root \ server1 While this works: /export1 \ /export2 \ -maproot=root \ server1 That's no good. Is there a solution to this problem? Each line should be made of 3 parts: 1 - directory/filesystems to export 2 - attributes 3 - hosts First one does not follow this layout. You can make each directory it's own filesystem using the vinum idea. By the way, I have found that FreeBSD is a solid NFS server. Other than this limitation NFS has worked great. Handbook on NFS: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-nfs.html Hope that helps, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Copy old drive to new drive - is it possible?
Hi there, On Sat, Feb 21, 2004 at 09:38:41PM +1100, Tig wrote: Hi, I have a hard drive which is on its last legs. I also have new hard drive to replace the old one. I was wondering if it is possible to simply copy everything from the old drive to the new (after formating the new drive) and have my system back up and running, or do I need to reinstall the OS and everything else? Yes this is quite possible happens regularly. Check out the handbook chapter 12: http://marvin.home.local/doc/en_US.ISO8859-1/books/handbook/disks-adding.html This example is for a new disk alongside existing system. If you plan to replace the original disk altogether you can do: 0. Backup all important data, settings, configuration hard to replace items. 1. Physically install new disk together with old disk 2. Install boot blocks if necessary 3. layout filesystems on the new disk (can use fdisk disklabel) 4. Create new filesystems (newfs) 5. mount new filesystem in temporary location 6. copy data across. Many ways exist: tar cpio dump / restore 7. shutdown system 8. Remove old drive, install new drive in old position. Ie if IDE primary master is your old disk, put the new into the same position. If it all goes to pieces reinstall on the new drives and restore your backups. You can use /stand/sysinstall to do steps 2,3,4 - the handbook covers this part quite well. Tips, URL's or a simple 'from personal experience, best to reinstall' comments more than welcome. It depends on how comfortable you are in a procedure like the above. It may be reinstall is easiest / best option for you. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to convert GNU make files to FreeBSD make?
Hi, On Fri, Feb 20, 2004 at 11:02:43AM +0300, Igor B. Bykhalo wrote: How can this GNU make constuct converted to FreeBSD: SRCDIRS = convert/c misc/c string/c memory/c handleio/c startup/c environ/c vpath %.c $(SRCDIRS) ? Is there some guide on the topic? I am new to this... While I cannot help much in make file contents conversion, you can install GNU make on FreeBSD through the ports/packages. See /usr/ports/devel/gmake Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: endless sysquery: no addrs found for root
Hi, On Fri, Feb 20, 2004 at 07:46:34AM -0600, John wrote: On Fri, Feb 20, 2004 at 06:35:51PM +1100, Tony Frank wrote: On Thu, Feb 19, 2004 at 10:25:04PM -0600, John wrote: OK. I'm stumped. Hopefully we can help. Yes - forward-only does get rid of the symptom. I should have mentioned that. It also, however, prevents this named instance from making its own queries, as you mentioned, which was why I was treating it as a work-around instead of a solution. I guess that's OK, but I haven't necessarily gone that route in the past, and I've never run into this problem before. I will probably stay with the forward-only scenario, but it does make me curious. One thought - does your query source IP resolve both forwards reverse? It really sounds like a bind setup/configuration issue so possibly the isc lists/archives may have something? http://www.isc.org/index.pl?/sw/bind/ Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot loop in FreeBSD 5.2-RELEASE after install - FIXED!
Hi, On Fri, Feb 20, 2004 at 04:49:00PM -0500, Mike Newell wrote: Well THAT'S weird... I wondered if there might be some strange data left on the drive (I had a 4.7-RELEASE install on it prior to this), so I stopped the system in POST and entered the Adaptec system utilities. I then did a low-level format of the drive. Reinstalled and Hey Presto - booted up fine! I wonder if the /boot/loader program found some bad data left over from a prior install that it didn't validate and that corrupted the boot process? Dunno, but it's up now. THANKS!! Good to hear it's working! Perhaps if there was a mismatch between boot1/boot2 or something. I'm not expert on the internals so I might leave this one there. Take care, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ahc + vinum raid5 deadlocks?
Hi again, Refer earlier thread on -stable for more background. 4.9-STABLE (cvsup 20th Feb) Kernel was compiled with DDB, INVARIANTS, DIAGNOSTICS. All options removed from /etc/make.conf except 'NOPROFILE=TRUE' I get the following on the console before system freezes: ahc0: WARNING no command for scb 14 (cmdcmplt) QOUTPOS = 44 Dropping into DDB I can run 'ps' and see lots of process in 'flswai' (tar, cvsup etc) plus others in state 'vrlock' (bufdaemon) See below for a full 'ps' output. At this point system was still accessible from network (ping + login via ssh) but new shells froze. As mentioned in other email to -stable I can run some simple remote commands. I managed to get a remote 'sync' command in and there was a quick burst of disk activity before it promptly wedged again. This is repeatable a few times but it just freezes again soon after. No further console output. Hardware is currently Adaptec AHA-2940W S71 (F/w 1.19S8) Same issues occured with Adaptec AHA-2940UW/B (F/w 1.32S8) I have 4 x 4G IBM SCSI disks on the single internal 68-pin connector. Connections are good termination is correct The 4 disks are combined into a single vinum raid5 plex. System is well ventilated and cool to the touch. Pentium 2 200Mhz, 128mb SDRAM, Asus P2V m/b. Currently takes ~2 hours of solid activity to trigger the issue. My 'test bench': Copying files over NFSv3/udp to vinum raid5 volume via cp tar + make -j4 buildworld + Copying large dir trees (/usr/ports, /usr/obj, /usr/src) + cvsuping second copy of /usr/src + extracting tar archive of /usr/obj I have second vinum volume (mirrored/concat) on two IDE drives connected to the m/b and the test bench runs just fine when using these disks/volume. It suggest to me an issue between ahc and vinum or vinum scsi ? Also seem to be experiencing corruption writing to the raid5 volume. - Some files do not have correct md5 checksum after copying to the raid5. Last parts of vinum info -V that I got in just before it froze: 13:52:13.709220 4DN Write 0xc387b23813.5270x3d9471 204812 3d9368 0 0 13:52:13.710332 4DN Write 0xc387b23813.5350x3d9471 204813 3d9368 0 0 13:52:13.710347 Unlock0xc387b238 0xf64ce1 13:52:13.713943 1VS Read 0xc38633a491.0 0x4d2a0 8192 13:52:13.714026 2LR Read 0xc38633a491.0 0x4d2a0 8192 13:52:13.714039 3RQ Read 0xc38633a4116.5350xcd3a9 81925 4d2a0 0 0 13:52:13.716327 1VS Write 0xc386378891.5 0x361e10 65536 13:52:13.716733 2LR Write 0xc386378891.5 0x361e10 65536 13:52:13.716746 Lock 0xc3863788 0x361ce1 13:52:13.716752 3RQ Read 0xc386378813.5350xd8971 65536 13 d8868 0 0 13:52:13.716844 3RQ Read 0xc3863788116.5190x6e3349 65536 10 d8868 0 0 13:52:13.733942 1VS Write 0xc38ab9c091.5 0x15d40e0 8192 13:52:13.734204 2LR Write 0xc38ab9c091.5 0x15d40e0 8192 13:52:13.734218 Lock 0xc38ab9c0 0x15d3da1 13:52:13.734225 3RQ Read 0xc38ab9c013.5430x5753b1 819214 5752a8 0 0 13:52:13.734340 3RQ Read 0xc38ab9c0116.5190xb7fd89 819210 5752a8 0 0 13:52:13.735175 1VS Write 0xc38bca1891.5 0x361ed0 8192 13:52:13.735287 2LR Write 0xc38bca1891.5 0x361ed0 8192 13:52:13.735322 Lockwait 0xc38bca18 0x361ce1 13:52:13.735679 1VS Read 0xc3890dc891.2 0x42018 1024 13:52:13.735747 2LR Read 0xc3890dc891.2 0x42018 1024 13:52:13.735755 3RQ Read 0xc3890dc8116.5190x142121 10242 42018 0 0 13:52:13.740781 4DN Read 0xc386378813.5350xd8971 65536 13 d8868 0 0 13:52:13.745513 4DN Read 0xc38ab9c013.5430x5753b1 819214 5752a8 0 0 13:52:13.765800 4DN Read 0xc38633a4116.5350xcd3a9 81925 4d2a0 0 0 and then again after I did a sync: Flags: 0x80204 Total of 120 blocks malloced, total memory: 253624 Maximum allocs: 732, malloc table at 0xc03bc7c0 10 requests active, maximum 419 active Time Event BufDev OffsetBytes SD SDoff Doffset Goffset 13:57:52.971644 3RQ Write 0xc38a8348116.5350x5f4149 81929 3f4040 0 0 13:57:52.972151 4DN Write 0xc38a8348116.5350x5f4149 81929 3f4040 0 0 13:57:52.972241 4DN Write 0xc38a8348116.5190x5f4149 81924 3f4040 0 0 13:57:52.973372 1VS Write 0xc389ef7091.0 0x2c070 8192 13:57:52.973452 2LR Write 0xc389ef7091.0 0x2c070 8192 13:57:52.973461 3RQ Write 0xc389ef70116.5190xac179 81920 2c070 0 0 13:57:52.973518 3RQ Write 0xc389ef70116.5350xac179 81925 2c070 0 0 13:57:52.973981 4DN Write 0xc389ef70116.5190xac179 81920
Re: Help with Vinum disk crash...
Hi, On Thu, Feb 19, 2004 at 09:46:35AM +0100, Danny Carroll wrote: Thanks for the information... I really need the space now so I am going to wipe it and start from scratch, although I am not sure if I will use vinum again. I guess my main concern is that when one of my disks crashed, the ufs filesystem got corrupted and I really did not expect that to happen. It could be ignorance on my part, I dont know but perhaps someone can help me understand how this could have happened? Filesystems can get corrupted if the system crashes and does not cleanly close the filesystem first. In your case I'm personally not too sure - some more questions perhaps can help. - Were you using softupdates on the filesystem? - Did the system panic/reboot when the disk crashed without shutting down cleanly? - What version of FreeBSD are you / were you running? Another thing, Greg, you mentioned that I should have a second plex if I wanted to protect the data. You mean like a mirror? Surely 1 is enough when we are talking raid-5? Raid-5 should still work if a single subdisk fails. In your original post you did not indicate if you were using raid5 setup. If you had configured the subdisks as a concatenated or striped plex then there would most likely be no way to continue with a disk missing unless there existed a second plex with a copy of the data. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot loop in FreeBSD 5.2-RELEASE after install
Hi, On Thu, Feb 19, 2004 at 09:48:04PM -0500, Mike Newell wrote: On Wed, 18 Feb 2004, Tony Frank wrote: tfrank While I cannot perhaps comment on your problem, you can try either pressing tfrank 'pause' key or 'scrolllock' which might help depending on where the problems tfrank are occuring. They don't work. Fortunately I was able to: 1. Hook a null modem to the serial port and my laptop. 2. Run hyperterm on my laptop to view serial port data. 3. During the initial boot load hit ESC to get the Boot: promt, then do -h to switch to serial console. 4. Capture the stuff on the serial console. What it does is repeatedly go through the BTX boot loader, saying something like (this is from memory): BTX loader... BIOS Drive A is disk 0 BIOS Drive C is disk 1 BIOS Drive D is disk 2 BTX loader... BIOS Drive A is disk 3 BIOS Drive C is disk 4 BIOS Drive D is disk 5 BTX loader... and so on. Eventually it runs out of drive numbers and starts saying Can't figure out our boot device a few times, then crashes with an assert error. Looks like the loader is just looping until it runs out of heap. That suggests that it may be confused somehow. I saw the crash/assert type scenario if the boot blocks are not installed properly. Ie the MBR is updated with the bootmgr (F1 .. bit) but the 2nd/3rd stages were corrupted somehow. (In my case I accidentally overwrote the blocks with some experiementation) You can reinstall boot blocks using bsdlabel (or disklabel on 4.9) If you can boot from floppy/CD, get into fixit mode. Then run: bsdlabel -B da0s1 (assuming da0 is the disk you are trying to boot from) If I try to boot directly into the kernel the cursor changes from a blinking underscore to a solid block and the system just locks up. In no case is there an error message or any other indication that something is weird. Have you tried 4.9-RELEASE on this system? I understand that 5.2.1-RC2 ISO is also available which might be another option. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum - suitablity for use with removable disks
Hi there, On Fri, Feb 20, 2004 at 09:46:48AM +1100, Pietralla, Siegfried P wrote: i want to use vinum with some removable ( e.g. usb2 ) hard disks. i want to use vinum because : it lets me create as many appropriately sized volumes as i need ; and, it doesn't matter whether the disk connects as da0 or da1 since vinum uses it's own label. my question is, will vinum comfortably handle more than one disk where there is an equal chance that none, one or more will be online at any one time. if i plug in a disk, will i need to restart or bring up or whatever the disk, or the plex etc every time a disk comes back online? if so, what is the smallest set of commands i can use to do this? note that i only intend to run single plexes ( no mirrors or raid 5 ) where all subdisks reside on the same physical disk. any thoughts or experiences appreciated. Sounds interesting. Note I have not tried this myself - will have to get USB support running to try it locally. But... Basic setup is quite straightforward (as per any other disk): 1. fdisk the USB drive to put a freebsd slice on there 2. create vinum partition on the disk 3. create vinum drive with the device 4. build subdisks/plex/volumes etc 5. newfs volumes 6. mount volume 7. transfer data as needed I expect you would want to at least umount the volume before removing a device. Probably want to 'stop' the volume/plex/subdisk also. That way vinum says disk is 'down' and wont try to write to it. You should then be able to remove safely (minus any other FreeBSD USB disk caveats that I am not aware of) Possibly camcontrol stop would be appropriate - I'll have to do some research on this. If the disk is used in a different USB port etc such that it gets a different device name I expect Vinum should still be able to recognise it. My experience here is nonexistant. At such time you should be able to start the objects and mount the filesystem again. If nothing else this has raised some ideas for things to spend a day or two on :) Hope there was something useful in that, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: endless sysquery: no addrs found for root
Hi,
On Thu, Feb 19, 2004 at 10:25:04PM -0600, John wrote:
OK. I'm stumped.
Hopefully we can help.
This is on a FreeBSD 4.9-STABLE system with named 8.3.7-REL
Fairly standard setup.
[EMAIL PROTECTED] [119]:/usr/src uname -a
FreeBSD marvin.home.local 4.9-STABLE FreeBSD 4.9-STABLE #122: Fri Jan 23 08:52:48 EST
2004 root@:/data/ad3/obj/usr/src/sys/MARVIN i386
Fri Feb 20 18:26:15 EST 2004
[EMAIL PROTECTED] [120]:/usr/src named -v
named 8.3.7-REL Fri Jan 23 17:43:07 EST 2004
[EMAIL PROTECTED]:/data/ad3/obj/usr/src/usr.sbin/named
I have set up a pretty basic named.conf file:
options {
directory /etc/namedb;
forwarders {
64.81.159.2;
216.231.41.2;
};
zone . {
type hint;
file named.root;
};
zone 0.0.127.IN-ADDR.ARPA {
type master;
file localhost.rev;
};
zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT {
type master;
file localhost-v6.rev;
};
When I try to start named with this config, the log file shows
Feb 19 22:16:50 jsrh named[177]: starting (/etc/namedb/named.conf). named 8.3.7-REL
Tue Feb 17 15:01:48 CST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/usr.sbin/named
Feb 19 22:16:50 jsrh named[178]: Ready to answer queries.
but then I get an endless stream of
Feb 19 22:16:58 jsrh named[178]: sysquery: no addrs found for root NS
(K.ROOT-SERVERS.NET)
for each one of the root name servers. Just for grins, I downloaded the
lastest named.root file, but that didn't help (of course). I also dropped
the firewall, but that didn't help, either.
When I run nslookup with the name nameservers listed as in the forwarders,
I'm able to make queries from this same system, including resolving
the root NS entries that are generating all these errors.
I'm clearly assuming something I shouldn't, or think I know something I
don't - because this just doesn't make sense to me.
fyi I do not get this kind of error, but then I have forward-only configured
in my options section to send all queries to my ISP DNS servers instead of
querying root servers direct. See below.
log messages at startup:
Feb 19 17:39:48 marvin named[28890]: starting (/etc/namedb/named.conf). named
8.3.7-REL Fri Jan 23 17:43:07 EST 2004 [EMAIL
PROTECTED]:/data/ad3/obj/usr/src/usr.sbin/named
Feb 19 17:39:49 marvin named[28890]: limit files set to fdlimit (1024)
Feb 19 17:39:49 marvin named[28890]: hint zone (IN) loaded (serial 0)
Feb 19 17:39:49 marvin named[28890]: master zone 0.0.127.IN-ADDR.ARPA (IN) loaded
(serial 20020407)
Feb 19 17:39:49 marvin named[28890]: master zone
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA (IN) loaded
(serial 20020407)
Feb 19 17:39:49 marvin named[28890]: master zone
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT (IN) loaded
(serial 20020407)
Feb 19 17:39:49 marvin named[28890]: master zone home.local (IN) loaded (serial
2004021902)
Feb 19 17:39:49 marvin named[28890]: master zone 168.192.in-addr.arpa (IN) loaded
(serial 2004021902)
Feb 19 17:39:49 marvin named[28890]: listening on [192.168.3.2].53 (fxp0)
Feb 19 17:39:49 marvin named[28890]: listening on [127.0.0.1].53 (lo0)
Feb 19 17:39:49 marvin named[28890]: Forwarding source address is [0.0.0.0].53
Feb 19 17:39:49 marvin named[28891]: Ready to answer queries.
The only subsequent messages I get (hourly) are:
Feb 20 07:39:49 marvin named[28891]: Cleaned cache of 8 RRsets
Feb 20 08:39:49 marvin named[28891]: Cleaned cache of 2 RRsets
Feb 20 09:39:49 marvin named[28891]: Cleaned cache of 5 RRsets
The named.root I have is the stock file installed by FreeBSD:
; $FreeBSD: src/etc/namedb/named.root,v 1.9.2.1 2002/11/06 09:24:12 dougb Exp $
For reference, my named.conf is:
acl allowed_sources {
localhost;
localnets;
};
options {
directory /etc/namedb;
forward only;
forwarders {
198.142.0.66; // dns01.meb.optusnet.com.au
203.2.75.108; // dns01.syd.optusnet.com.au
211.29.132.154; // dns07.syd.optusnet.com.au
};
query-source address * port 53;
listen-on port 53 {
127.0.0.1;
192.168.3.2;
};
allow-query { allowed_sources; };
};
key DHCP_UPDATER {
algorithm HMAC-MD5.SIG-ALG.REG.INT;
secret ** ;
};
zone . {
type hint;
file named.root;
};
zone 0.0.127.IN-ADDR.ARPA {
type master;
file localhost.rev;
};
zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA {
type master;
file localhost-v6.rev;
};
zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT {
type master;
file localhost-v6.rev;
};
zone home.local {
type master;
notify no;
file p/home.local;
allow-update {
Re: continued make world problems...
Hi, On Fri, Feb 20, 2004 at 12:53:15AM -0600, Eric F Crist wrote: I've managed to get cvsup working (after my botched make world and a power failure a couple days ago). I deleted the /usr/src tree, and the /usr/obj tree and tried to complete a make world afterwards. No matter what I do, I get the following error after 2 hours of a make world: btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/ ../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin btxld: No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 etc. What do I need to do to fix this. I cannot get this to go away with the tiny bit of knowledge I have. Please help. :( What branch/release are you trying to make? RELENG_4 is working for me. (cvsupped last night) Are you running make -j4 world etc? If so try without the -j4 option. Do you have any non-default settings in /etc/make.conf? Try removing them and building again. If you cd to /usr/src/sys/boot/i386/boot2 can you run make to build just this part of the tree manually? About all I can suggest right now. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: power point
Hi, On Fri, Feb 20, 2004 at 08:26:15AM +0100, Martin Vana wrote: is there a way to convert ms powerpoint presentation into jpegs? or to view it under Freebsd? One of the following ports may help you: /usr/ports/textproc/xlhtml /usr/ports/editors/openoffice-1.1 /usr/ports/editors/staroffice60 Otherwise: MS Powerpoint has an export option that lets you save your slides as gif or jpg. File-Save As-Save as type and pick your preference: gif, jpg, png, bmp etc Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with Vinum disk crash...
Hi there, On Wed, Feb 18, 2004 at 09:34:29AM +0100, Danny Carroll wrote: Quoting Greg 'groggy' Lehey [EMAIL PROTECTED]: If this volume has only one plex, you're lost, unless you can bring up the failed disk long enough to make a backup. Here is the output: 20 drives: D data1 State: up Device /dev/ad4s1a Avail: 3/109471 MB (0%) D ftp1 State: up Device /dev/ad4s1e Avail: 0/600 MB (0%) D www1 State: up Device /dev/ad4s1f Avail: 0/2048 MB (0%) D mail1 State: up Device /dev/ad4s1g Avail: 0/2048 MB (0%) D rback1 State: up Device /dev/ad4s1h Avail: 0/3072 MB (0%) D data2 State: up Device /dev/ad5s1a Avail: 6/109471 MB (0%) D ftp2 State: up Device /dev/ad5s1e Avail: 0/600 MB (0%) D www2 State: up Device /dev/ad5s1f Avail: 0/2048 MB (0%) D mail2 State: up Device /dev/ad5s1g Avail: 0/2048 MB (0%) D rback2 State: up Device /dev/ad5s1h Avail: 0/3072 MB (0%) D data3 State: up Device /dev/ad6s1a Avail: 6/109471 MB (0%) D ftp3 State: up Device /dev/ad6s1e Avail: 0/600 MB (0%) D www3 State: up Device /dev/ad6s1f Avail: 0/2048 MB (0%) D mail3 State: up Device /dev/ad6s1g Avail: 0/2048 MB (0%) D rback3 State: up Device /dev/ad6s1h Avail: 0/3072 MB (0%) D data4 State: up Device /dev/ad7s1a Avail: 6/109471 MB (0%) D ftp4 State: up Device /dev/ad7s1e Avail: 0/600 MB (0%) D www4 State: up Device /dev/ad7s1f Avail: 0/2048 MB (0%) D mail4 State: up Device /dev/ad7s1g Avail: 0/2048 MB (0%) D rback4 State: up Device /dev/ad7s1h Avail: 0/3072 MB (0%) Ok, this is wrong - you really just want to define one vinum drive per physical device. Ie for a particular disk, give it a single 'vinum' partition using disklabel. Then use different subdisks to split your space up. 5 volumes: V data State: up Plexes: 1 Size:320 GB This is should be ok - it means vinum thinks the volume is still accessable. 5 plexes: P data.p0R5 State: degraded Subdisks: 4 Size:320 GB From man 4 vinum : degradedA RAID-5 plex entry which is accessible, but one subdisk is down, requiring recovery for many I/O requests. So you have a subdisk down which means Vinum can still read from the plex but has to manually calculate the missing subdisk data. 20 subdisks: S data.p0.s0State: stalePO:0 B Size:106 GB S data.p0.s1State: up PO: 3924 kB Size:106 GB S data.p0.s2State: up PO: 7848 kB Size:106 GB S data.p0.s3State: up PO: 11 MB Size:106 GB Again from man 4 vinum : stale A subdisk entry which has been created completely. All fields are correct, the disk has been updated, and the data was valid, but since then the drive has been crashed and updates have been lost. I am only interested in the big one (data) the others were just for experimentation I thought since the plex was setup as raid5 it would be ok? Yes, Vinum believes it can still access your data. I have 4 106gb subdisks, and see 318Gb of data... The 4th subdisk is becuase of the loss from Raid5 right? Yes, one disk per stripe will be used for parity. Did I set this up incorrectly? I suggest you read http://www.vinumvm.org/cfbsd/vinum.pdf - the last section comments again on the particulars for drive subdisk layout. From your original message: When I do try and mount the volume, it says the following: [02:25 PM [EMAIL PROTECTED]:/var/log]#mount /dev/vinum/data /usr/jails/ftp/data mount: /dev/vinum/data on /usr/jails/ftp/data: incorrect super block Typically I see this problem when trying to mount filesystem with incorrect type. Was your filesystem ufs? If not you probably need to specify the type to mount command using -t parameter. See man 8 mount for details. Have you tried running fsck against the volume? Assuming ufs filesystem, I'd suggest starting with: fsck -n -t ufs /dev/vinum/data Note the -n option tells fsck not to correct any errors but will give you an indication about what is going on. There are extra things you can try (recover using alternate super-block) but perhaps wait and see the results first? Another option would be to force the particular subdisk down and try the above steps again. Hope it helps, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make is not working for me
Hi there, On Wed, Feb 18, 2004 at 12:37:54AM +0800, [EMAIL PROTECTED] wrote: forgive the newbie question please I am trying to install a package called bpalogin (it authorises Bigpond Broadband Cable users (Bigpond is an ISP in Australia)) and I have followed the instructions from the http://bpalogin.sourceforge.net/index.php?page=download I have untarred th file and tried a make the result is /usr/share/mk/bsd.own.mk, line 0: Cannot open /usr/share/mk/bsd.own.mk /usr/ports/Mk/bsd.port.mk, line 0: Cannot open /usr/ports/Mk/bsd.port.mk make: fatal errors encoutered --cannot continue I have set write permissions on both files and write and execute permission on the Directories I would like some pointers to what to look for. I have a clean minimal install of 5.2 Thanks everyone Personally speaking, the port setup is a bit out of date. It hasn't been updated in quite a while (whereas the FreeBSD ports environment has changed) and it actually refers to v2.0 of bpalogin anyway. I suggest you grab the unix source directly and use it instead: % fetch http://bpalogin.sourceforge.net/download/bpalogin-2.0.2.tar.gz % tar zxvf bpalogin-2.0.2.tar.gz % cd bpalogin-2.0.2 % ./configure % make Personally the 'make install' had a few issues for me. Personally I would use: % install -m 755 bpalogin /usr/local/sbin % install -m 600 bpalogin.conf /usr/local/etc % install -m 755 bpalogin.bsd /usr/local/etc/rc.d/bpalogin.sh Then edit /usr/local/etc/bpalogin.conf to set relevant options. % vi /usr/local/etc/bpalogin.conf You should be able to start it up with: % /usr/local/etc/rc.d/bpalogin.sh start Note I have not personally used the software, but 2.0.2 compiles cleanly on my 4.9 system and I expect it will compile ok on 5.2 also. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Name Server error / problem with Win XP
Hi there, On Tue, Feb 17, 2004 at 02:30:49PM -0500, Ajitesh K wrote: We are running NameServ1 Name server on Freebsd 4.8 We are getting some kind of error on my name server nameserv1. FYI, TM25 is laptop of out side client and OS is Windows XP Home. nameserv1.lan.company.com kernel log messages: 31 10:47:32 nameserv1 dhcpd: if IN A TM25.dhcp.company.com domain doesn't exist add 300 IN A TM25.dhcp.company.com 10.1.2.165 add 300 IN TXT TM25.dhcp.company.com 31eb2f5e58786ebab0b6eabd298b28671f: domain already exists I feel its some thing to do with Windows XP. Does any one know the fix? You have your dhcpd configured to use 'dynamic dns' function. When the laptop gets an address via dhcp, the dhcpd sends a message to dns to update the dns name to the new IP address. Some windows clients can do this also if the option is configured in the Windows DNS settings. Here I think it is your server as the log line comes from dhcpd. In this case, the name TM25.dhcp.company.com already exists so dhcpd reports this. This may be due to a static entry in DNS zone files or because the laptop already had an entry configured earlier. You can check by doing a 'dig TM25.dhcp.company.com' and see what results you get from your DNS - you should see the name resolve to the IP address of the laptop. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Video card compatibility
Hi, On Tue, Feb 17, 2004 at 03:10:37PM -0500, bradford fligor wrote: I bought FreeBSD 5.1 and Handbook for my 10 year old computer nut son for Christmas and have had problems installing the full graphical version. When asked for video card on installation, I don't' know what to select. I have on-board video on the motherboard at this site. http://www.albatron.com.tw/english/it/mb/specification.asp?pro_id=35 I also have an old monitor but I don't think that's the problem. Will I need to buy a separate video card and if so would you have any suggestions? If your system is up and running, you should post the results of the command 'pciconf -lv' and 'dmesg' This should tell us what type of hardware you have (perhaps give yourself enough of a hint) As others on the list have suggested, 4.9 or 5.2.1 might be better version choices. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boot loop in FreeBSD 5.2-RELEASE after install
Hi there, On Thu, Feb 12, 2004 at 11:26:18AM -0500, Mike Newell wrote: I am trying to install FreeBSD on a Dell Precision 410 workstation. The system has two 18G SCSI drives (Seagate ST318203LW) on an Adaptec 7890 SCSI adaptor (BIOS V2.01.05). I've gone through the entire install and when the system tries to boot the first time the boot loader loads, then a huge amount of text scrolls VERY rapidly up the screen [I can see the word Can't but this is scrolling VERY fast], then the system resets (clearing the screen of course) and the process starts again. [ ... ] Can anyone help? Is there any way to slow the bootup process so I can at least read the errors? While I cannot perhaps comment on your problem, you can try either pressing 'pause' key or 'scrolllock' which might help depending on where the problems are occuring. Do you get past the F1 FreeBSD part to the loader? ie do you see a - appear on screen? Can you perhaps try a serial console? If you can get into the boot loader you should be able to set com1 as your console. Hope that helps, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with Vinum disk crash...
Hi, On Wed, Feb 18, 2004 at 01:15:18PM +0100, Danny Carroll wrote: Quoting Tony Frank [EMAIL PROTECTED]: So you have a subdisk down which means Vinum can still read from the plex but has to manually calculate the missing subdisk data. But I assume it cant write till I replace it.. I believe it should function for both read write in degraded mode. Any reads will have to be rebuilt hence there will be a big hit in performance. Typically I see this problem when trying to mount filesystem with incorrect type. Was your filesystem ufs? If not you probably need to specify the type to mount command using -t parameter. See man 8 mount for details. Have you tried running fsck against the volume? Assuming ufs filesystem, I'd suggest starting with: fsck -n -t ufs /dev/vinum/data Note the -n option tells fsck not to correct any errors but will give you an indication about what is going on. fsck -n -t ufs did not work...Seems like fsck does not know -t ... You dont want to see the output from that... Nearly every inode has problems.. I got confused with mount there. :) I ran it without the -n and the first entry looks like this: UNKNOWN FILE TYPE I=188225^C[12:39 PM [EMAIL PROTECTED]:/usr/home/danny]#fsck /dev/vinum/data ** /dev/vinum/data ** Last Mounted on /usr/jails/ftp/data ** Phase 1 - Check Blocks and Sizes UNKNOWN FILE TYPE I=29 Well -n is useful in that it makes no changes... There are extra things you can try (recover using alternate super-block) but perhaps wait and see the results first? How do I read an alternative superblock wih a vinum drive??? superblock is a filesystem function - so you run fsck with -b option as so: fsck -b x where x is the replacement superblock. Typically 32 is a valid replacement (says this in fsck man page) so you might want to try fsck -n -b 32 /dev/vinum/data The newfs output will give you a list of the superblocks created. You can 'rerun' newfs with: newfs -N -v /dev/vinum/data Be sure to include the -N as otherwise it will overwrite your volume. If 32 wont work you can try a higher number Another option would be to force the particular subdisk down and try the above steps again. Something like: vinum down data.p0.s0 ??? The command would be vinum stop data.p0.s0 In my case I had to do vinum stop -f data.p0.s0 In your case if you have replaced the faulty drive you should be able to run 'vinum start data.p0.s0' to have the subdisk rebuilt in the background. This will take a long time for your listed volume sizes. However this should not have any impact to your situation. The volume is working at the Vinum level (although degraded) The problem here is that the data on the vinum volume appears to be somehow corrupt. If the fsck option with alternate superblock doesn't help I think the only option is a restore of data. If you do that I would recommend rebuilding the vinum configuration. Arrange a single vinum partition per disk and then use multiple subdisks to share the storage amongst different plexes. Here's output of a scenario I just now ran on my test box: I got a lot of errors with fsck which are strange to me as I have only two files on the filesystem. More investigation ongoing (probably tomorrow as it's now late) Throughout the various activities vinum gives full access to the volume with only one subdisk lost. raider# vinum stop data.p0.s0 Can't stop data.p0.s0: Device busy (16) raider# vinum lv -r data V data State: up Plexes: 1 Size: 16 GB P data.p0R5 State: up Subdisks: 5 Size: 16 GB S data.p0.s0State: up PO:0 B Size: 4298 MB S data.p0.s1State: up PO: 492 kB Size: 4298 MB S data.p0.s2State: up PO: 984 kB Size: 4298 MB S data.p0.s3State: up PO: 1476 kB Size: 4298 MB S data.p0.s4State: up PO: 1968 kB Size: 4298 MB raider# vinum stop -f data.p0.s0 vinum: data.p0.s0 is down by force vinum: data.p0 is degraded raider# vinum lv -r data V data State: up Plexes: 1 Size: 16 GB P data.p0R5 State: degraded Subdisks: 5 Size: 16 GB S data.p0.s0State: down PO:0 B Size: 4298 MB S data.p0.s1State: up PO: 492 kB Size: 4298 MB S data.p0.s2State: up PO: 984 kB Size: 4298 MB S data.p0.s3State: up PO: 1476 kB Size: 4298 MB S data.p0.s4State: up PO: 1968 kB Size: 4298 MB raider# ll /data total 1046000 -rw-r--r-- 1 root wheel 510709760 Feb 17 22:45 objtest.tar -rw-r--r-- 1 root wheel 559839232 Feb 17 22:40 office2k.iso raider# umount /data vinum: data.p0.s0 is obsolete by force raider# vinum lv -r data V data State: up Plexes: 1 Size: 16 GB
4.9-stable system lockup with vinum raid5 activity
Hi all, I'm running 4.9-STABLE built 17th Feb based on cvsup on same day. Custom kernel in use with device polling enabled on fxp0. Kernel config is attached in case anyone can spot anything obvious there. It's an 'older' system, Pentium2-200, 132mb ram, basic Asus slot1 m/b (Via chipset) with 2 ide/ata disks (ad0, ad2) Also has a adaptec 2940UW SCSI (ahc0) with 4x4g scsi drives (da0-da3) kernel + vinum loaded via loader.conf with vinum root environment built around ad0 ad2. See some other messages in questions regarding exact build of this box due to previous problems with vinum raid5 volume. First I noticed fsck had errors right after I newfs'd my raid5 volume. I let fsck fix the errors and mounted the volume. I then copied some test data across and while this appeared to work, the md5 checksum of the files copied across no longer matches my original md5 records taken from both a separate system (transferred via ftp) and from another volume (a vinum mirror) on the same system. My test data is an iso CD image + a tar archive containing /usr/obj from my build system. Around 1gig all up and lots of files/dirs in the tar file. I then tried extracting the tar archive and after about 20 mins the system appeared to freeze. At this time vty switching was still working and I noticed the following on the console: (hand copy) devstat_end_transaction: HELP!! busy_count for da2 is 0 (-1)! devstat_end_transaction: HELP!! busy_count for da2 is 0 (-1)! devstat_end_transaction: HELP!! busy_count for da3 is 0 (-1)! devstat_end_transaction: HELP!! busy_count for da3 is 0 (-1)! devstat_end_transaction: HELP!! busy_count for da3 is 0 (-2)! ahc0: Timedout SCB already complete. Interrupts may not be functioning. ahc0: Timedout SCB already complete. Interrupts may not be functioning. ahc0: Timedout SCB already complete. Interrupts may not be functioning. ahc0: Timedout SCB already complete. Interrupts may not be functioning. ahc0: Timedout SCB already complete. Interrupts may not be functioning. ahc0: Timedout SCB already complete. Interrupts may not be functioning. I tried a few commands but while the first few went through any new command I ran through the console appeared to pause for ~5 mins before running, eg vmstat -i Pressing ctrl-t on the console for vmstat shows: load: 0.00 cmd: vmstat 455 [flswai] 0.00u 0.01s 0% 472k I eventually pressed 'ctl-alt-del' (no debugger in this kernel) and after ~20 mins the box has now rebooted but did no restart. As it is a test system I am now going to further investigate in the morning. Full history of what I was doing: raider# umount /data raider# newfs -v /dev/vinum/data Warning: Block size and bytes per inode restrict cylinders per group to 22. Warning: 1856 sector(s) in last cylinder unallocated /dev/vinum/data:35211456 sectors in 8597 cylinders of 1 tracks, 4096 sectors 17193.1MB in 391 cyl groups (22 c/g, 44.00MB/g, 10944 i/g) super-block backups (for fsck -b #) at: 32, 90144, 180256, 270368, 360480, 450592, 540704, 630816, 720928, 811040, 901152, 991264, 1081376, 1171488, 1261600, 1351712, 1441824, 1531936, 1622048, 1712160, 1802272, 1892384, 1982496, 2072608, 2162720, 2252832, 2342944, 2433056, 2523168, 2613280, 2703392, 2793504, 2883616, 2973728, 3063840, 3153952, 3244064, 3334176, 3424288, 3514400, 3604512, 3694624, 3784736, 3874848, 3964960, 4055072, 4145184, 4235296, 4325408, 4415520, 4505632, 4595744, 4685856, 4775968, 4866080, 4956192, 5046304, 5136416, 5226528, 5316640, 5406752, 5496864, 5586976, 5677088, 5767200, 5857312, 5947424, 6037536, 6127648, 6217760, 6307872, 6397984, 6488096, 6578208, 6668320, 6758432, 6848544, 6938656, 7028768, 7118880, 7208992, 7299104, 7389216, 7479328, 7569440, 7659552, 7749664, 7839776, 7929888, 802, 8110112, 8200224, 8290336, 8380448, 8470560, 8560672, 8650784, 8740896, 8831008, 8921120, 9011232, 9101344, 9191456, 9281568, 9371680, 9461792, 9551904, 9642016, 9732128, 9822240, 9912352, 10002464, 10092576, 10182688, 10272800, 10362912, 10453024, 10543136, 10633248, 10723360, 10813472, 10903584, 10993696, 11083808, 11173920, 11264032, 11354144, 11444256, 11534368, 11624480, 11714592, 11804704, 11894816, 11984928, 12075040, 12165152, 12255264, 12345376, 12435488, 12525600, 12615712, 12705824, 12795936, 12886048, 12976160, 13066272, 13156384, 13246496, 13336608, 13426720, 13516832, 13606944, 13697056, 13787168, 13877280, 13967392, 14057504, 14147616, 14237728, 14327840, 14417952, 14508064, 14598176, 14688288, 14778400, 14868512, 14958624, 15048736, 15138848, 15228960, 15319072, 15409184, 15499296, 15589408, 15679520, 15769632, 15859744, 15949856, 16039968, 16130080, 16220192, 16310304, 16400416, 16490528, 16580640, 16670752, 16760864, 16850976, 16941088, 17031200, 17121312, 17211424, 17301536, 17391648, 17481760, 17571872, 17661984, 17752096, 17842208, 17932320, 18022432, 18112544, 18202656, 18292768, 18382880, 18472992, 18563104, 18653216, 18743328, 18833440, 18923552,
Re: vinum raid5 subdisks keep changing length?
On Tue, Feb 17, 2004 at 05:53:06PM +1030, Greg 'groggy' Lehey wrote: On Tuesday, 17 February 2004 at 11:39:26 +1100, Tony Frank wrote: On Tue, Feb 17, 2004 at 09:51:30AM +1030, Greg 'groggy' Lehey wrote: On Monday, 16 February 2004 at 22:04:44 +1100, Tony Frank wrote: [... snip ...] OK, I tried almost exactly the same thing. My disks are fractionally smaller than yours, so I took a different integral number of stripes. I didn't get any messages, and the config now looks like: volume data plex name data.p0 org raid5 984s vol data sd name data.p0.s0 drive drive1 plex data.p0 len 8374824s driveoffset 265s plexoffset 0s sd name data.p0.s1 drive drive2 plex data.p0 len 8374824s driveoffset 265s plexoffset 984s sd name data.p0.s2 drive drive3 plex data.p0 len 8374824s driveoffset 265s plexoffset 1968s sd name data.p0.s3 drive drive4 plex data.p0 len 8374824s driveoffset 265s plexoffset 2952s sd name data.p0.s4 drive drive5 plex data.p0 len 8374824s driveoffset 265s plexoffset 3936s I've stopped and started vinum a couple of times, and all works well. I then removed the objects and tried again with subdisks 4 sectors longer. Vinum gives the message: vinum: removing 16 blocks of partial stripe at the end of data.p0 printconfig is then identical with the previous version. With no obvious known problems and this being a test system I have wiped the disks and started over. My near exact steps: Rebooted from 4.9-RELEASE CD1 Went to 'fixit' mode with live filesystem CD2 Wiped the disks: dd if=/dev/zero of=/dev/da0 bs=512 count=32 fdisk -BI /dev/da0 dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 disklabel -w -B da0s1 auto First thing I notice is that the geometry for my SCSI disks differs by 1 cylinder between da0 and da0s1. I configured all the vinum slices as da0s1h etc. Anyway, then I went on to a 'standard' installation. I selected ad0 (space), q -no changes (already had a partition from above steps) Selected BootMgr Repeated for each disk (ad0, ad2, da0-da3) Deleted all the prelisted partitions filesystems and performed an 'auto' based on ad2 (leaves ad0, da0-da3 unused) Selected Minimal installation type Sourced from CD Post install configured fxp0 for DHCP, Accepted NFS client, selected no for all other options Set timezone to Australia Victoria Added an extra user tony with additional group wheel. No ports, no packages, no other options. Rebooted System booted from ad2 with 4.9-RELEASE GENERIC kernel Ran disklabel -e da0s1 and added a 'h' slice of: # h: ** vinum Repeated for ad0s1, da0s1-da3s1. ad0 is size 16498692, da0-da3 is size 8803557 The scsi disk being smaller, I use it's size for stripe calculations. For stripe of 984s: (8803557 - 256) / 984 = 8946 (rounded to nearest whole number) 8946 * 984 = 8802864 8802864 + 256 = 8803120 which is less than total drive size so it should fit. I build a vinum config file test-config, just raid5 volume without vinum root: ### start test-config drive vinumdrive0 device /dev/ad0s1h drive vinumdrive1 device /dev/da0s1h drive vinumdrive2 device /dev/da1s1h drive vinumdrive3 device /dev/da2s1h drive vinumdrive4 device /dev/da3s1h volume data plex org raid5 984s sd drive vinumdrive0 len 8802864s driveoffset 265s sd drive vinumdrive1 len 8802864s driveoffset 265s sd drive vinumdrive2 len 8802864s driveoffset 265s sd drive vinumdrive3 len 8802864s driveoffset 265s sd drive vinumdrive4 len 8802864s driveoffset 265s ### end test-config Create the configuration: raider# vinum create test-config 5 drives: D vinumdrive0 State: up Device /dev/ad0s1h Avail: 3757/8056 MB (46%) D vinumdrive1 State: up Device /dev/da0s1h Avail: 0/4298 MB (0%) D vinumdrive2 State: up Device /dev/da1s1h Avail: 0/4298 MB (0%) D vinumdrive3 State: up Device /dev/da2s1h Avail: 0/4298 MB (0%) D vinumdrive4 State: up Device /dev/da3s1h Avail: 0/4298 MB (0%) 1 volumes: V data State: down Plexes: 1 Size: 16 GB 1 plexes: P data.p0R5 State: init Subdisks: 5 Size: 16 GB 5 subdisks: S data.p0.s0State: emptyPO:0 B Size: 4298 MB S data.p0.s1State: emptyPO: 492 kB Size: 4298 MB S data.p0.s2State: emptyPO: 984 kB Size: 4298 MB S data.p0.s3State: emptyPO: 1476 kB Size: 4298 MB S data.p0.s4State: emptyPO: 1968 kB Size: 4298 MB Initialise the plex: raider# vinum init data.p0 raider# vinum[215]: initializing subdisk /dev/vinum/sd/data.p0.s1 vinum[216]: initializing subdisk /dev/vinum/sd/data.p0.s2 vinum[217]: initializing subdisk /dev/vinum/sd/data.p0.s3 vinum[218]: initializing subdisk /dev/vinum/sd/data.p0.s4 vinum[214]: initializing subdisk /dev/vinum/sd/data.p0.s0 While waiting for my SCSI drives to write 4G worth of zeros I
Re: vinum raid5 subdisks keep changing length?
Hi again, On Tue, Feb 17, 2004 at 11:01:36PM +1100, Tony Frank wrote: [ ... ] Despite this logging oddity everything else appears to work just fine using 4.9-RELEASE. I am currently building world based on RELENG_4 cvsup from this evening. Will try it all again with the new kernel world probably tomorrow. Main thing that is different is that I no longer have a vinum root environment. I might try to rebuild that while I wait for world to build. Vinum root needs a bit more planning from the start due to disk offsets and the like... [ ... ] Will further report tomorrow on outcome of further testing. Scenarios: data raid5 with vinum root on 4.9-RELEASE plain data raid5 with RELENG_4 data raid5 with vinum root on RELENG_4 Well I have rebuilt my setup with vinum root + raid5 data volume. I originally rebuilt it on 4.9-RELEASE GENERIC kernel + world from CD #1. Without going so far as to do hardware failure testing, I did not observe any problems other than the lack of vinum entries from bootup in the logs. I then upgraded the system to RELENG_4 GENERIC kernel (cvsup yesterday) and world built from same sources. Still no problems after reboots or as a result of any other 'normal' operations. I then built installed a custom kernel based on RELENG_4 GENERIC (remove lot of drivers and add IPFW etc) and still it all works fine and without any obvious issues. As such I suspect the previous scenario was likely a result of user error and some obscure combination of events. If I'm bored again tomorrow I might rebuild the lot again but starting with the RELENG_4 level instead of 4.9-RELEASE to see if that has any impacts. Thanks for your time, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum raid5 subdisks keep changing length?
Hi all, Running vinum on RELENG_4. No changes to source, vinum loaded as a KLD as per instructions in handbook man pages. As per the subject I am having what appears to be strange behaviour with vinum. After a number of teething problems I eventually setup a vinum root for my system which covers / swap /var and /usr. This works just fine, though I am yet to experiment with failure scenarios. However I also configured a raid5 volume and may be having issues with it. Currently just a test system and no obvious data loss but I have some concerns before I put it into production. Specifically I originally configured five subdisks (on different drives) with identical lengths and then combined them into a raid5 plex. This worked ok and I successfully initialised the plex and used newfs on it. Successfully able to readwrite to the volume (1G/14G used at the moment) The original config looked as so: volume data plex name data.p0 org raid5 984s vol data sd name data.p0.s0 drive eightgig plex data.p0 len 8802864s driveoffset 6335201s plexoffset 0s sd name data.p0.s1 drive vinumdrive0 plex data.p0 len 8802864s driveoffset 265s plexoffset 984s sd name data.p0.s2 drive vinumdrive1 plex data.p0 len 8802864s driveoffset 265s plexoffset 1968s sd name data.p0.s3 drive vinumdrive2 plex data.p0 len 8802864s driveoffset 265s plexoffset 2952s sd name data.p0.s4 drive vinumdrive3 plex data.p0 len 8802864s driveoffset 265s plexoffset 3936s Now after each system reboot I see messages on system console from vinum. (they are not logged in vinum_history or messages) (hand transcript): vinum: updating configuration from /dev/ad0s1h #(repeated for all 6 drives) vinum: removing 2560 blocks of partial stripe at the end of data.p0 vinum: data.p0 must have equal sized subdisks vinum: data.p0 must have equal sized subdisks vinum: data.p0 must have equal sized subdisks vinum: data.p0 must have equal sized subdisks Correcting length of data.p0: was 35191776, is 35197088 vinum: using volume root for root device Mounting root from ufs:/dev/vinum/root A vinum printconfig now shows difference values for the subdisks. This value has changed after each reboot. Current relevant parts of 'printconfig' are: volume data plex name data.p0 org raid5 984s vol data sd name data.p0.s0 drive eightgig plex data.p0 len 8799978s driveoffset 6335201s plexoffset 0s sd name data.p0.s1 drive vinumdrive0 plex data.p0 len 8799486s driveoffset 265s plexoffset 984s sd name data.p0.s2 drive vinumdrive1 plex data.p0 len 8799158s driveoffset 265s plexoffset 1968s sd name data.p0.s3 drive vinumdrive2 plex data.p0 len 8798420s driveoffset 265s plexoffset 2952s sd name data.p0.s4 drive vinumdrive3 plex data.p0 len 8797600s driveoffset 265s plexoffset 3936s Each subdisk len is now a different size which is of some concern to me, especially as the specific len values change after each reboot. Some other perhaps 'relevant' details: uname -a output: FreeBSD raider.home.local 4.9-STABLE FreeBSD 4.9-STABLE #1: Sat Feb 7 01:50:58 EST 2004 [EMAIL PROTECTED]:/data/ad3/obj/usr/src/sys/RAIDER i386 Tail of /var/log/messages output: Feb 16 20:14:42 raider /kernel: da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 16 20:14:42 raider /kernel: da2: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) Feb 16 20:14:42 raider /kernel: Mounting root from ufs:/dev/vinum/root Feb 16 20:14:43 raider savecore: no core dump Feb 16 20:14:37 raider ntpd[115]: ntpd 4.1.0-a Sat Feb 7 00:06:01 EST 2004 (1) Feb 16 20:14:37 raider ntpd[115]: kernel time discipline status 2040 Feb 16 20:14:54 raider su: tony to root on /dev/ttyp0 Feb 16 20:15:03 raider su: tony to root on /dev/ttyp0 Feb 16 20:19:10 raider ntpd[115]: time set 0.007497 s /var/log/vinum_history extract (shows init and subsequent prints) 8 Feb 2004 13:38:58.679668 attach data.p0 data 8 Feb 2004 13:39:01.616409 lv 8 Feb 2004 13:39:02.891476 lv -r 8 Feb 2004 13:39:04.099017 lv 8 Feb 2004 13:39:09.498986 lv -r 8 Feb 2004 13:39:17.697480 init data.p0 8 Feb 2004 13:40:24.011586 lv -r 8 Feb 2004 13:41:23.409672 lv -r 8 Feb 2004 13:42:06.320951 lv -r 8 Feb 2004 13:43:17.928172 *** vinum started *** 8 Feb 2004 13:43:17.943327 lv -r 8 Feb 2004 13:44:26.669794 *** vinum started *** 8 Feb 2004 13:44:26.675611 lv -r 8 Feb 2004 13:46:06.942916 *** vinum started *** 8 Feb 2004 13:46:06.945251 lv -r 8 Feb 2004 13:49:36.588518 *** vinum started *** 8 Feb 2004 13:49:36.590516 lv -r 8 Feb 2004 13:53:32.719039 *** vinum started *** # Rebooted here 8 Feb 2004 15:26:57.032467 *** vinum started *** 8 Feb 2004 15:26:57.053653 list 8 Feb 2004 15:27:00.942329 *** vinum started *** 8 Feb 2004 15:27:00.943709 printconfig 8 Feb 2004 15:27:22.021212 *** vinum started *** 8 Feb 2004 15:27:22.022626 printconfig after_reboot.config 8 Feb 2004 15:29:53.377752 *** vinum started *** 8 Feb 2004 15:29:53.379181 l 8 Feb 2004 15:31:16.065588 *** vinum started *** 8 Feb 2004
Re: vinum raid5 subdisks keep changing length?
Hi, On Tue, Feb 17, 2004 at 09:51:30AM +1030, Greg 'groggy' Lehey wrote: On Monday, 16 February 2004 at 22:04:44 +1100, Tony Frank wrote: Running vinum on RELENG_4. No changes to source, vinum loaded as a KLD as per instructions in handbook man pages. As per the subject I am having what appears to be strange behaviour with vinum. After a number of teething problems I eventually setup a vinum root for my system which covers / swap /var and /usr. This works just fine, though I am yet to experiment with failure scenarios. However I also configured a raid5 volume and may be having issues with it. Currently just a test system and no obvious data loss but I have some concerns before I put it into production. Specifically I originally configured five subdisks (on different drives) with identical lengths and then combined them into a raid5 plex. This worked ok and I successfully initialised the plex and used newfs on it. Successfully able to readwrite to the volume (1G/14G used at the moment) The original config looked as so: volume data plex name data.p0 org raid5 984s vol data sd name data.p0.s0 drive eightgig plex data.p0 len 8802864s driveoffset 6335201s plexoffset 0s sd name data.p0.s1 drive vinumdrive0 plex data.p0 len 8802864s driveoffset 265s plexoffset 984s sd name data.p0.s2 drive vinumdrive1 plex data.p0 len 8802864s driveoffset 265s plexoffset 1968s sd name data.p0.s3 drive vinumdrive2 plex data.p0 len 8802864s driveoffset 265s plexoffset 2952s sd name data.p0.s4 drive vinumdrive3 plex data.p0 len 8802864s driveoffset 265s plexoffset 3936s Now after each system reboot I see messages on system console from vinum. (they are not logged in vinum_history or messages) These messages should appear in /var/log/messages. Have you changed your syslogd.conf? No, default 4.9 config file, the vinum messages do not show up in 'dmesg' either. I have changed to include the 'all.log' and 'console.log' in the syslogd.conf so I will see if that changes this behaviour. vinum: updating configuration from /dev/ad0s1h #(repeated for all 6 drives) vinum: removing 2560 blocks of partial stripe at the end of data.p0 Yes, this is a feature, not a bug. While I accept this for a striped plex made up with subdisk of unequal length, I had already taken that into account, hence the original subdisk length: 8946 * 984 = 8802864 As I understand it, this should have resulted in a whole number of stripes. I have 5 subdisks so I'm not sure if I should have factored that into my calculations? A vinum printconfig now shows difference values for the subdisks. This value has changed after each reboot. Current relevant parts of 'printconfig' are: volume data plex name data.p0 org raid5 984s vol data sd name data.p0.s0 drive eightgig plex data.p0 len 8799978s driveoffset 6335201s plexoffset 0s sd name data.p0.s1 drive vinumdrive0 plex data.p0 len 8799486s driveoffset 265s plexoffset 984s sd name data.p0.s2 drive vinumdrive1 plex data.p0 len 8799158s driveoffset 265s plexoffset 1968s sd name data.p0.s3 drive vinumdrive2 plex data.p0 len 8798420s driveoffset 265s plexoffset 2952s sd name data.p0.s4 drive vinumdrive3 plex data.p0 len 8797600s driveoffset 265s plexoffset 3936s This is a bug, not a feature. I'll try to take a look at it today. Please advise if I can help - I have plenty of free time this week and am willing to get my hands dirty. Another item (which I think I read about somewhere but can no longer find the reference) is that after a reboot the vinum drives all reference da0h ad2h etc rather than the original value of ad2s1h da0s1h. Also after the reboot, each drive is shown as 100% free which is a concern. Thanks, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3Com USRobotics 5699B 56k fax modem install
Hi there, On Sat, Feb 07, 2004 at 10:46:35AM -0800, Alex Teslik wrote: Arg! This is indeed a winmodem according to the USRobotics website. I knew to avoid those like the plague, but since the modem cost twice as much as all the other modems and it didn't say winmodem anywhere on the box I figured it was safe. I thought USR was reputable. This sucks. I feel duped. Off to the store to replace this Try: /usr/ports/comms/ltmdm Works for my laptop builtin winmodem (Compaq Evo N610c) Best of luck, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Starting two instances of bind - method?
Hi there, On Sat, Feb 07, 2004 at 01:45:10PM -0500, Chad M Stewart wrote: I want to run two instances of Bind 9 on the same box. Both will be chrooted and have their own IPs. At some point I may choose to put them in jails, but for now no. One step at a time. :) I'm wondering what suggestions people might have for getting each started up during the normal boot process. I see the options in /etc/defaults/rc.conf and could put my own stuff in /etc/rc.conf but as far as I can tell that would only work for a single instance. How would I get the other instance to start up? The same binary can be used for both, just different configuration files and chroots. Your biggest issue is that unless you are using separate IP for each instance of bind, you will have problems as both will by default need to use port 53 for DNS service. Perhaps you want to investigate the use of Bind9 view function which lets you show different data to different clients. The ISC homepage for bind is an excellent resource: http://www.isc.org/index.pl?/sw/bind/ As is the DNS and BIND book by Albitz Liu from Oreilly. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [maybe OT] IP/UDP/DNS packet manipulation question
Hi there, On Sat, Feb 07, 2004 at 01:46:46PM -0500, Louis LeBlanc wrote: That is to say it will accept DNS requests from local agents, filter out IPV6 request packets, and forward IPV4 requests to our backend DNS server in a way that the backend server will believe it has received them directly from the local server and send the response directly back to the local DNS agent, not the filter/forwarder. As I understand things, this will mean rewriting the outgoing IP header, UDP header (TCP support is not needed), so that they each contain the address of the local agent as the sender IP, and leaving the DNS header unchanged. Or better yet, simply forwarding the entire IP packet unchanged so that even the IP identification field is intact. The DNS header is easy enough, since that's in the application layer, but I'm having trouble finding out how to rewrite the transport and network layer headers, or to simply forward the whole packet. You might be able to do this with one of the various firewalls already. Perhaps check out ipfilter and pf. If using ipfw you can divert all DNS traffic to a divert(4) socket which you can then connect to your DNS application. If the application likes what it sees it can send the packet back via divert for forwarding to the real DNS target - no modifications necessary. If the DNS packet doesnt meet the specs, it can be dropped. Another possibiliy might be a netgraph module, although netgraph seems typically more suited to layer2 type applications. Hope it helps, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Differences between net/vnc ports ?
Hi, On Sun, Feb 08, 2004 at 02:15:11AM +0200, Ion-Mihai Tetcu wrote: In ports/net/ there are 6 vnc ports. Leaving alone vnc2swf could someone tell from experience the difference between them ? For now I am interested in vnc clients to access a mixture of 98/xp/2000 machines, but any other info would be appreciated. I personally have had great success with TridiaVNC. Although it is a little old now I can get the same feature set on all platforms - w32, freebsd, solaris and they all interwork just fine. In other experience most versions will interwork with the basic features. If you want some fancy specific features then you need to investigate the offerings of each individual version. Best regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
