buildworld kernel" regularly, so any reboots will
automatically have a newer kernel).
There's definite evidence that the newnfs mounts are slower than plain nfs,
and sometimes orders of magnitude slower (as others have shown). But the
old nfs
ng in the read stuff.
I can try disabling SMP too. Should that really matter, if you're not
even pegging one CPU? The locks shouldn't have *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"
264 1080p video does not skip):
mount -t nfs server:/path /mnt
I 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-
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
4299
Any ideas?
-- 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"
out NIS. If someone can prove
that this will cause a problem with NFSv4, we could consider hackingit.
Otherwise I don't think we should 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"
The v4 file system seems
just as fast as v3 did, and I don't need a dozen mountpoints specified
on each client thanks to v4. Once again, I thank you, 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"
; since I like to
build as close to GENERIC as possible. Mostly the WITHOUT_* stuff in
/etc/src.conf is to reduce my overall build 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 s
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
> >
on seeks was less than 0.1 seconds and the playback was never
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 job
the
kernel since I always "make buildworld kernel" and keep things in sync
with mergemaster when I reboot. I'm building new worlds/kernels now
to see if that makes any difference.
-- Rick C. Petty
___
freebsd-stable@freebsd.org mailing lis
t = 5, port = 28416
Jun 27 18:05:12 amanda kernel: NLM: failed to contact remote rpcbind, stat = 5,
port = 28416
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
nf
s, and the ls(1) was executed during that
lockup. I wish there was a way I could unhang these processes and unmount
the NFS mount without panicking the kernel, but alas even this fails:
# umount -f /sw
load: 0.00 cmd: umount 17479 [nfsclumnt] 1.27r 0.00u 0.04s 0% 788k
A "shutdown -p now" result
libtool-2.2.6b/libltdl/config/config.sub:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
||
*
7660
Again, my ports tree is mounted as FSType nfs with option nfsv4.
FreeBSD/amd64 8.1-PRERELEASE r208408M GENERIC kernel.
-- Rick C. Petty
quot;, they show up empty. In dmesg I see:
kernel: nfsv4 client/server protocol prob err=10020
After unmounting /vol, 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
___
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"
.
On the server, I have 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
finish it.
Isn't this sufficient?
http://en.wikipedia.org/wiki/S.M.A.R.T.#Known_ATA_S.M.A.R.T._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
_
6, you'll need to
reboot into single-user again with geom_vinum unloaded.
10). Wipe sector 8 of the vinum 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
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:
> > >
re where the size difference comes from. I have some 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
are only 5 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"
t;buildworld" before doing 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/m
different NIC. 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 -tso".
-- Rick C. Petty
What does this have to do 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
akes no difference since the number of bytes is computed by newfs 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 accep
your line to:
make -j4 buildworld buildkernel && make installkernel
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"
add a parameter ("-z" perhaps) to newfs(8) to accept
number of bytes instead of multiples of sectorsize.
I would be willing to write up 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
rare that -stable breaks on buildworld (even -current isn't
broken often, in terms of build breakage).. something I can't say about
other operating systems. A csup this morning 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]"
eaking things now?
Please Cc: me, 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]"
29 matches
Mail list logo
