Hi,
How do I accomplish atacontrol reinit in 9.0 with ATA_CAM enabled? Plugged
drives don't show up without a reboot and camcontrol reset or rescan does not
help.
Pete
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
Is there a way (loader variable, hints, etc.?) to change the order which
different PCI card ports are enumerated on kernel start?
Pete
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscr
Matthias Buelow wrote:
Petri Helenius wrote:
Are you sure you aren't comparing filesystems with different mount
options? Async comes to mind first.
a) ext3 and xfs are logging filesystems, so the problem with
asynchronous metadata updates possibly corrupting the filesystem on a
crash do
Are you sure you aren't comparing filesystems with different mount
options? Async comes to mind first.
Pete
Nick Pavlica wrote:
All,
I would like to start addressing some of the feedback that I have
been given. I started this discussion because I felt that it was
important to share the informat
Alexander Leidinger wrote:
On Mon, 29 Nov 2004 08:17:40 -0600
Mike Horwath <[EMAIL PROTECTED]> wrote:
On Mon, Nov 29, 2004 at 06:12:20PM +0530, Akhthar Parvez. K wrote:
Hi All,
I am getting the following error message in /var/log/messages
tail -f /var/log/messages
Nov 29 07:24:31 speedy /ke
Is the warning message generated by -Wformat about syslog %m an issue
with FreeBSD header files or gcc itself?
Pete
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL P
Christian Hiris wrote:
About a year ago i observed strong nfs performance decrease when using
RLT8139A nics. Nfs transfers leaded into high system load, because of an
excessive high packet retransmission rate. Switching over to 3Com nics solved
my problem.
The specific model and it's clos
Poul-Henning Kamp wrote:
I am not sure I would advocate 64k blocks yet.
Good to know, I have stuck with 16k so far due to the fact that our
database has pagesize of 16k and I found little benefit tuning that.
(but it´s completely different application)
I tend to stick with 32k block, 4k fragmen
Geoff Buckingham wrote:
- This is a big problem (no pun intended), my smallest requirement is still
5TB... what would you recommend? The smallest file on the storage will be
500MB.
If you files are all going this large I imagine you should look carefully at
what you do with inodes, block and
Poul-Henning Kamp wrote:
2) What is the maximum size of a filesystem that I can present to the host
OS using vinum/ccd? Am I limited anywhere that I am not aware of?
Good question, I'm not sure we currently know the exact barrier.
Just make sure you run UFS2, which is the default on -CURRENT
Is there a counter which would show system calls per process?
Like vm.stats.sys.v_syscall but instead of being systemwide, count
separately for each process.
Pete
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
What would be the correct forum to post RAIDframe questions/problem
reports to?
Couldn't really locate maintainer address on the source tree...
Pete
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
David Schultz wrote:
Most kernel memory is not pageable, so swap probably won't help
you. Your `kmem_map too small' error message should report to you
the size of the attempted allocation and the size of kmem_map.
If the map really isn't full, I'm not sure why you would get this
panic, unless yo
> > With about 150M in use and KVA_PAGES undefined in config (default),
> > both 4.7-STABLE and 5.0-CURRENT panic (1G installed memory).
>
> Yes, the default is 256, IIRC. That corresponds to 1 GB of KVA,
> and you have only 1 GB of physical memory to back it. I take it
> this is a very busy mach
>
> Read LINT (or NOTES) carefully. You can't set KVA_PAGES to 1024,
> because then your kernel would take up the entire 4 GB virtual
> address space. Since the kernel must fit into 4 GB alongside
> every user process, that leaves you no room for programs. Try a
> more reasonable value like 512
David Schultz wrote:
Thus spake Petri Helenius <[EMAIL PROTECTED]>:
I seem to get kmem_map too small panics when using large buffers with
bpf. Is there a tunable I should be increasing?
Yes, increase KVA_PAGES in your kernel config.
I put in KVA_PAGES=1024
with following resu
I seem to get kmem_map too small panics when using large buffers with
bpf. Is there a tunable I should be increasing?
Pete
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
17 matches
Mail list logo
