On Thu, May 20, 2004 at 10:44:14AM -0500, Eric Anderson wrote:
That's good to hear. Did you do any other tweaks? sysctl settings?
mbufs?
net.inet.udp.recvspace=524288
kern.ipc.maxsockbuf=1048576
net.inet.icmp.drop_redirect=1
net.inet.icmp.log_redirect=1
Telus-nfs1:# w
12:41PM up 212
On Fri, May 21, 2004 at 01:06:41PM -0500, Eric Anderson wrote:
Disk design issues matter cause it is the ultimate
bottleneck. RAID is you friend.
Just curious - what RAID level/configuration do you use? I've typically
used RAID5, but RAID0+1 might be acceptable.
Howdy!
I have done some simulations with NFS servers - Intel SCB2 (4G RAM)
serving files from 500G RAID devices. I created a treed directory structure
with 300G of 32k files that approximates our homedirectory structure.
I had about 6 diskless front ends (tyan 2518 with
Howdy!
Some hardware will not boot FreeBSD from SCSI disks unless
the disk is formated and labled in dedicated mode.
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/formating-media/x65.html
In general SCSI disk that only contain FreeBSD should be
formated/labled in
On Thu, Feb 13, 2003 at 03:28:58PM +0100, Roman Neuhauser wrote:
interesting. all I see is backpedalling from dangerously dedicated
disks in /stand/sysinstall and elsewhere
Many IDE drives will not boot if setup in dangerously dedicated
mode. So, for normal people who are
Howdy!
I have 4 identical disks, labels etc are also identical.
It looks like vinum after reboot does not recognize drives
properly, as it did immedialtely after initial configuration.
One drive/subdisk in each plex isn't recognized, and the other one
is duplicated, which
On Mon, Jul 12, 2004 at 06:40:01AM +0930, Greg 'groggy' Lehey wrote:
I get the following incorrect configuration. Notice that
drives data0 and data1 are missing and drives data2 and data3 are
duplicated where data0 and data1 should be.
I see no drives.
Not sure what you
On Mon, Jul 12, 2004 at 06:40:01AM +0930, Greg 'groggy' Lehey wrote:
I see no drives.
Ideas?
I have concluded that this is the result of somekind
of vinum/hardware incompatibility. The problem in question
occured during the upgrade to faster disks, specifically,
Seagate Cheetah
