, thanks,
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
caused the problem to go
away. Thanks, guys!
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
with FreeBSD-stable? This question is better
asked on freebsd-questions.
Since cdda2wav is in the base, I suppose people
use it regurarly. Something like:
What do you mean by base? It is a port and not in the base system.
-- Rick C. Petty
___
freebsd
. This option controls whether
we offload segmenting to the NIC. My NIC seemed to be limited by the
number of interrupts which could be delivered. You can also do this on a
card-by-card basis using ifconfig interface -tso.
-- Rick C. Petty
___
freebsd
a buildkernel, as the
toolchain which builds the kernel might have changed. Also
KERNCONF=GENERIC is implied.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail
choices, maximum.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
sparc64
systems running -current with symbols and the size of /boot/kernel is
more comparable to i386, even with the 8-byte pointer size:
Um, probably there are a lot of devices on amd64 that aren't available for
sparc64?
-- Rick C. Petty
___
freebsd
On Tue, Jul 07, 2009 at 11:24:51AM +0200, Ruben de Groot wrote:
On Mon, Jul 06, 2009 at 04:20:45PM -0500, Rick C. Petty typed:
On Mon, Jul 06, 2009 at 11:39:04AM +0200, Ruben de Groot wrote:
On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed:
Right, so it's a lot bigger
slick on disk1.
11). Add disk1 to the gmirror, which should start a sync.
12). Load the geom_vinum module again, if you have other volumes not part
of this mirror. If this panics the kernel, or if the kernel panicked after
step 11, a normal restart might be successful.
-- Rick C. Petty
patches for dumpfs and newfs to both add the
raw byte size and the 512-byte sector size handling to correct said
mistake, unless someone else would rather.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman
or just:
make -j4 buildworld kernel echo success
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
and
then divided by the actual sector size when calling bwrite(3). I still
would prefer:
Better yet would be to add a parameter (-z perhaps) to newfs(8) to accept
number of bytes instead of multiples of sectorsize.
-- Rick C. Petty
___
freebsd-stable
._attributes
If not, could you make the changes on wikipedia? This isn't a
FreeBSD-specific topic, and the larger community would benefit from such
documentation.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman
these tunables explicitly set:
kern.ipc.maxsockbuf=524288
vfs.newnfs.issue_delegations=1
On the client, I just have the maxsockbuf setting (this is twice the
default value). I'm open to trying other tunables or patches. TIA,
-- Rick C. Petty
___
freebsd-stable
, I discovered that my client already had /vol/a/b and
/vol/a/c directories (because pre-NFSv4, I had to mount each filesystem
separately). Once I removed those empty dirs and remounted, the problem
went away. But it did drive me crazy for a few hours.
-- Rick C. Petty
||
*
7660
Again, my ports tree is mounted as FSType nfs with option nfsv4.
FreeBSD/amd64 8.1-PRERELEASE r208408M GENERIC kernel.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
constantly and no console output.
It's possible the NICs are all suspect, but all of this worked fine a
couple of days ago when I was only using NFSv3.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
client, when noticing the mounting-over-directories problem:
NLM: failed to contact remote rpcbind, stat = 5, port = 28416
nfsv4 client/server protocol prob err=10020
nfsv4 client/server protocol prob err=10020
...
No other related messages were found in /var/log/messages either.
--
-- Rick C
I reboot. I'm building new worlds/kernels now
to see if that makes any difference.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable
jittery.
I can try it again with v3 client and v4 server, if you think that's
worthy of pursuit. If it makes any difference, the server's four CPUs are
pegged at 100% (running nice +4 cpu-bound jobs). But that was the case
before I enabled v4 server too.
-- Rick C. Petty
On Mon, Jun 28, 2010 at 10:09:21PM -0400, Rick Macklem wrote:
On Mon, 28 Jun 2010, Rick C. Petty wrote:
If it makes any difference, the server's four CPUs are
pegged at 100% (running nice +4 cpu-bound jobs). But that was the case
before I enabled v4 server too.
If it is practical
times, since I don't need some
of those tools.
I'm okay with the messages though; I'll probably comment out WITHOUT_INET6.
Thanks again for your suggestions,
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman
, Rick, for all your
hard work!
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
change this behavior yet.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
44069 38
cpu1: timer 2293983 1998
Total4935757 4299
Any ideas?
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
On Sun, Aug 29, 2010 at 11:44:06AM -0400, Rick Macklem wrote:
Hi. I'm still having problems with NFSv4 being very laggy on one
client.
When the NFSv4 server is at 50% idle CPU and the disks are 1% busy,
I am
getting horrible throughput on an idle client. Using dd(1) with 1 MB
block
guess I will have to wait for you to bring the v4 client up to date.
Thanks again for all of your contributions and for porting NFSv4 to
FreeBSD!
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
*that* much overhead...
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
mounts are slower than plain nfs,
and sometimes orders of magnitude slower (as others have shown). But the
old nfs is so broken in other ways that I'd prefer slower yet more stable.
Thanks again for all your help, Rick!
-- Rick C. Petty
___
freebsd-stable
29 matches
Mail list logo