Re: recommendations on the newfs of a 1.0TB fs...
When you say ``the default wasted too much disk space'', do you mean that when you formatted the filesystem, you had less space than you expected, or do you mean that there was less space left after you put all of your data on it? Smaller block sizes mean more space for free block bitmaps, which are allocated at filesystem creation time, but overall they are a win in terms of space because of reduced internal fragmentation. Consider what happens when you put a 10K file on the disk. Depending on whether the filesystem is optimizing for space or time, that file will take up 16K or 64K in your 64/16 filesystem, but substantially less with a 16/2 FS. So unless you are expecting most of your files to be rather large, a smaller block size may be beneficial. Note, however, that I'm not an FFS expert; other factors such as fragmentation may be relevant. The formatted file system had less total available space left on it. Now it was like 5am and I'd been up for the past 24 hours setting things up two years ago so it's a bit fuzzy :-) Right now the FS is optimizing for time. I had read some where (I'll see if I can dig up my notes), but I remember getting the distinct feeling that the larger block size was what I wanted, but like I said, it's all a bit fuzzy. I would also be interested in knowing how FFS and reiserfs compare with respect to filesystem age. Does performance drop significantly after a year? If the research I've seen is right, FFS performance shouldn't drop more than 20% unless the filesystem is nearly full, and reiserfs has a cleaner... I'll see about running some dbench marks or bonnie and see how things shape up. Cheers, Ryan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ping: sendto: No buffer space available
Dag-Erling Smorgrav wrote: Interference is preventing the card from transmitting, causing packets to accumulate in the outgoing queue. Dummynet queues with RED might help -- changing the behavior from tail dropping to early detection may improve performance. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: filesystem disappeared following 4.2 - 4.7 upgrade
At 08:23 PM 2/2/2003 -0600, Mike Meyer, you wrote: In [EMAIL PROTECTED], Brent Kearney [EMAIL PROTECTED] typed: What if this system were an all-IDE system? I was planning to update one soon, and will no doubt run into this problem. The root filesystem device node will change names, and according to this thread: http://www.freebsd.org/cgi/getmsg.cgi?fetch=2388792+2394647+/usr/local/www/db/text/2003/freebsd-questions/20030112.freebsd-questions No, devices *may* change names. They don't have to. The article you quoted changed names drastically because he wasn't using the onboard IDE controller, but had all his drives on the Promise card (would you verify that for me, Oscar)? One solution to the question asked in that message is to disable the IDE on the motherboard so that the Promise controller becomes ata0, and the first drive on it becomes ad0. That also frees up a couple of IRQs, and may be worth doing in any case. It's probably better to try changing /boot/loader.conf to set root_disk_unit to solve the problem, though. Wel ... yes and no. I wasn't putting the drive on the first and second IDE controllers. The motherboard had two additional IDE controllers, Promise ATA66, on it. On some BIOS, you can direct the machine to look at slot devices before onboard devices, that might help your situation. Not that it's any kind of solution, but in the end, while attempting to do another install on the system, I accepted the default sizes for the filesystems and it worked. Creating a / filesystem of 128MB ... and from there it booted fine. Oscar To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
IBM x335 Broadcom BCM5703 NICs not detected by 4.7-R
Greetings, I am attempting to configure FreeBSD 4.7-RELEASE to run on an IBM xSeries 335. The two motherboard Broadcom Gigabit Ethernet devices are not detected by the kernel. Relevant output of 'boot -v'... pcib2: Host to PCI bridge on motherboard found- vendor=0x14e4, dev=0x16a7, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 64, base f5ff, size 16 found- vendor=0x14e4, dev=0x16a7, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=3 map[10]: type 1, range 64, base f5fe, size 16 pci3: PCI bus on pcib2 pci3: unknown card (vendor=0x14e4, dev=0x16a7) at 1.0 irq 11 pci3: unknown card (vendor=0x14e4, dev=0x16a7) at 2.0 irq 3 and 'pciconf -lv'... none1@pci3:1:0: class=0x02 card=0x026f1014 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X Gigabit Ethernet' class= network subclass = ethernet none2@pci3:2:0: class=0x02 card=0x026f1014 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X Gigabit Ethernet' class= network subclass = ethernet I fiddled with BIOS settings (no PnP OS option) and tried a stripped down kernel with no success. Installing a 3c905 PCI card works fine, but I would prefer to use the built in NICs. Any suggestions? Regards, Mike Lambert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
