In article <[EMAIL PROTECTED]>, Sergey Babkin
<[EMAIL PROTECTED]> writes
>
>By the way the journaling filesystems don't neccessary guarantee that
>you won't need fsck: for example, if VXFS crashes at a particularly
>bad moment, it will require you to do "fsck -o full" which is as slow
>as the fsc
On Tue, 18 Dec 2001, Brandon D. Valentine wrote:
> On Tue, 18 Dec 2001, Mike Bristow wrote:
>
> >I suspect that the background fsck[1] that's available in FreeBSD-current
> >fits the bill just as well as JFS or XFS - and I'll also bet that it'll
> >be available in a FreeBSD-release before I'd t
Alfred Perlstein wrote:
> > By the way the journaling filesystems don't neccessary guarantee that
> > you won't need fsck: for example, if VXFS crashes at a particularly
> > bad moment, it will require you to do "fsck -o full" which is as slow
> > as the fsck on traditional UFS.
>
> Yeah, but tha
* Sergey Babkin <[EMAIL PROTECTED]> [011218 19:45] wrote:
> Dan Nelson wrote:
> >
> > In the last episode (Dec 18), Mike Bristow said:
> > > I suspect that the background fsck[1] that's available in FreeBSD-current
> > > fits the bill just as well as JFS or XFS - and I'll also bet that it'll
> >
Dan Nelson wrote:
>
> In the last episode (Dec 18), Mike Bristow said:
> > I suspect that the background fsck[1] that's available in FreeBSD-current
> > fits the bill just as well as JFS or XFS - and I'll also bet that it'll
> > be available in a FreeBSD-release before I'd trust data to a port of
In the last episode (Dec 18), Mike Bristow said:
> I suspect that the background fsck[1] that's available in FreeBSD-current
> fits the bill just as well as JFS or XFS - and I'll also bet that it'll
> be available in a FreeBSD-release before I'd trust data to a port of
> JFS or XFS.
The problems
On Thu, Dec 13, 2001 at 04:39:58AM -0500, Brandon D. Valentine wrote:
> On Wed, 12 Dec 2001, Matthew Dillon wrote:
>
> >All I can say is... holy shit!
>
> Dude, you kick ass. At work I've been dealing with Linux's crappy NFS
> implementation for years, while FreeBSD has always been pretty d
I'm trying to get the license issue clarified, then it can go in
/usr/src/tools/regression.
- Jordan
> Jordan Hubbard <[EMAIL PROTECTED]> writes:
>
> > Guy Harris of NetApp sent me a whole mess-o-changes to it and when I
> > went to forward them to you, I found that I must have been in
> > dele
In article <[EMAIL PROTECTED]>, Brandon
D. Valentine <[EMAIL PROTECTED]> writes
>
[snip]
>but it still can't touch the FreeBSD NFS implementation. The more
>robust you make it the easier it is for me to argue for deployment of
>more FreeBSD systems in NFS server roles. The only advantage Linux h
Aloha!
Sorry to jump in here but..
I've read the thread starting with Jordans posting of the Apple testcase
code with great interest.
To me this has been one of the most interesting and reassuring readings in
hackers for a long time. (Yes, I'm a lurker here).
First, I take the testcase code
JFWIW, you can build fsx with minimal or no changes on Windows with David
Korn's UWIN kit. All of the other posix-y kits have internal problems
that will cause spurious failures.
If you want to use Windows boxes as test clients (probably a good idea)
this is fairly important...
> > I gave o
> I gave out fsx source code at the recent CIFS (SMB) plugfest. If I make
> the 2002 Connectathon I'll give it out there too. I don't test it on
> Windows so those defines may be in need of repair. Please send me any
> patches or cool additions.
Guy Harris of NetApp sent me a whole mess-o-chan
At 8:19 PM -0800 12/12/01, Jordan Hubbard wrote:
>> To be clear, what exactly are you doing?
>>
>> It sounds like you're exporting something from freebsd, mounting it on OSX
>> and running this tool on OSX against the filesystem exported from freebsd ?
>>
>> If so, What mount options? NFSv2 or v3
At 2:56 PM -0800 12/12/01, Jordan Hubbard wrote:
>> The only thing I get is a math exception because "closeprob" is zero
>> since no -c option was given.
>>
>> Can you provide some sample parameters please ?
>
>Hmmm, how strange, now that I look at the code it's obvious that a
>divide by zero will
On Thu, Dec 13, 2001 at 01:40:46PM -0800, Matthew Dillon wrote:
>
> :Matt,
> :
> :what the hell, this seems to very near by a problem I wanted to
> :report since a week:
> :
> :in a data acquisition I have a write process writing to a file
> :backed shared mmapped ringbuffer. There can be several
:Matt,
:
:what the hell, this seems to very near by a problem I wanted to
:report since a week:
:
:in a data acquisition I have a write process writing to a file
:backed shared mmapped ringbuffer. There can be several reader
:processes on this this ringbuffer. Now once i killed the writer for
:re
:
:I can't seem to get a crash dump out of it, but the panic I'm seeing is:
:
:panic: allocdirect_check: old 30246736 ! = new 30246736 || ibn 4 >= 12
:
:For some reason the dump also dies, resettting the ata0 bus over and over
:but not writing out to swap.
:
:- Jordan
That's the softupdates
On Thu, 13 Dec 2001, Jordan Hubbard wrote:
> I can't seem to get a crash dump out of it, but the panic I'm seeing is:
>
> panic: allocdirect_check: old 30246736 ! = new 30246736 || ibn 4 >= 12
>
> For some reason the dump also dies, resettting the ata0 bus over and over
> but not writing out to
On Thu, Dec 13, 2001 at 02:58:28AM -0800, Matthew Dillon wrote:
>
> @#$@#$ crap. I think I found a dirty-mmap edge case with truncation.
> It requires a change to vm_page_set_validclean(), which of course is
> one of the core routines in the VM system.
>
> Basically what happens
I can't seem to get a crash dump out of it, but the panic I'm seeing is:
panic: allocdirect_check: old 30246736 ! = new 30246736 || ibn 4 >= 12
For some reason the dump also dies, resettting the ata0 bus over and over
but not writing out to swap.
- Jordan
> :
> :> I should point out that FSX c
:> And if you hadn't heard, Matt just fixed a couple of bugs in the tcp
:> stack which improves NFS greatly. It sounds like after this round of
:> NFS fixes, the first answer to NFS questions should be: Upgrade to
:> 4.5!
:
:I don't even bother with TCP mounts; my default amd rule says
:proto=ud
* void <[EMAIL PROTECTED]> [011213 11:00] wrote:
> Has anyone brought this code to the attention of the NetBSD people?
> I imagine that they would be interested. If not, I will forward it
> along myself, as soon as I determine the appropriate list. (List
> recommendations from the dual citizens
:
:Matt didnt feel the fixes were primarily performance related, just bug
:fixes.
I meant just the last two days worth of NFS stuff are just bug fixes.
The TCP fixes from earlier in the month are definitely performance fixes.
-Matt
To Un
On Thu, 13 Dec 2001, Geoff Mohler wrote:
> Matt didnt feel the fixes were primarily performance related, just bug
> fixes.
Right, the fact that they are bug fixes is what seems to be the most
powerful reason to recommend upgrading.
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL
On Thu, 13 Dec 2001, Dan Nelson wrote:
> In the last episode (Dec 13), Mike Silbersack said:
> > And if you hadn't heard, Matt just fixed a couple of bugs in the tcp
> > stack which improves NFS greatly. It sounds like after this round of
> > NFS fixes, the first answer to NFS questions should
For some people, the overhead is an acceptible tradeoff to redundancy.
Ever since Cisco released thier 6500 10/100 blades that to crappy
buffering between a Gigabit NFS server (could be anything, just an
example) and an 100Mbit client, people have somewhat been adding that
overhead to thier CPU a
Has anyone brought this code to the attention of the NetBSD people?
I imagine that they would be interested. If not, I will forward it
along myself, as soon as I determine the appropriate list. (List
recommendations from the dual citizens here are welcome.)
On Wed, Dec 12, 2001 at 08:23:56AM -0
Matt didnt feel the fixes were primarily performance related, just bug
fixes.
On Thu, 13 Dec 2001, Mike Silbersack wrote:
>
> On Wed, 12 Dec 2001, Matthew Dillon wrote:
>
> > :I suppose while were on the topic..
> > :
> > :Are there any hidden secrets to eeking out more performance from the BS
In the last episode (Dec 13), Mike Silbersack said:
> On Wed, 12 Dec 2001, Matthew Dillon wrote:
> > Geoff Mohler wrote:
> > :Are there any hidden secrets to eeking out more performance from
> > :the BSD NFS client (other than version types and the normal fstab
> > :tweaks).
>
> And if you hadn't
On Wed, 12 Dec 2001, Mike Smith wrote:
> Many of the key issues in making OS X NFS work were related to its
> interaction with the UBC and the subtly different VFS semantics,
> although the same issues probably exist in different form in the
> FreeBSD code. I get dragged into some really shocki
@#$@#$ crap. I think I found a dirty-mmap edge case with truncation.
It requires a change to vm_page_set_validclean(), which of course is
one of the core routines in the VM system.
Basically what happens is that ftruncate() calls vnode_pager_setsize()
which eventually calls
> Thanks! I'm slowly whacking the bugs. I just fixed another one...
That's awesome... I'd hoped this program might help you find a few
things, but I never expected you to find so many bugs in NFS
so... quickly! I certainly didn't expect you to tickle any local
filesystem problems either.
:
: Very cool. Good job!
:
:-DG
:
:David Greenman
:Co-founder, The FreeBSD Project - http://www.freebsd.org
Thanks! I'm slowly whacking the bugs. I just fixed another one...
vtruncbuf() handles the buffers beyond the file EOF but doesn't handle
the buffer straddling the truncatio
On Wed, 12 Dec 2001, Matthew Dillon wrote:
> :I suppose while were on the topic..
> :
> :Are there any hidden secrets to eeking out more performance from the BSD
> :NFS client (other than version types and the normal fstab tweaks).
> :
> :Im the CS Labs manager at NetApp..and Im always trying to
:I suppose while were on the topic..
:
:Are there any hidden secrets to eeking out more performance from the BSD
:NFS client (other than version types and the normal fstab tweaks).
:
:Im the CS Labs manager at NetApp..and Im always trying to store away a
:secret here or there when someone comes t
Very cool. Good job!
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
President, TeraSolutions, Inc. - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the bo
I suppose while were on the topic..
Are there any hidden secrets to eeking out more performance from the BSD
NFS client (other than version types and the normal fstab tweaks).
Im the CS Labs manager at NetApp..and Im always trying to store away a
secret here or there when someone comes to me wit
Ok, here is the latest patch for -stable. Note that Kirk comitted a
slightly modified version of the softupdates fix to -current already
(the VOP_FSYNC stuff), which I will be MFCing in 3 days.
This still doesn't fix all the problems the nfstest program that Jordan
posted fin
> To be clear, what exactly are you doing?
>
> It sounds like you're exporting something from freebsd, mounting it on OSX
> and running this tool on OSX against the filesystem exported from freebsd ?
>
> If so, What mount options? NFSv2 or v3?
That is correct. As to the NFS options used, I ho
I found a second bug... nfs truncation code race.
I've enclosed both patches below. NFS truncation race first, softupdates
bug second. The patches are against -stable.
There are still more bugs... the nfstest code is seeing data corruption
on read. It looks like another t
Jordan Hubbard wrote:
> > I should point out that FSX can be used against any filesystem, and
> > that there are reports locally (at Apple) that it's great for killing
> > FreeBSD machines. I wasn't able to reproduce this when I tried, but I
> > may not have let it run long enough.
>
> Oh, it bl
:
:> I should point out that FSX can be used against any filesystem, and
:> that there are reports locally (at Apple) that it's great for killing
:> FreeBSD machines. I wasn't able to reproduce this when I tried, but I
:> may not have let it run long enough.
:
:Oh, it blows freebsd.apple.com rig
> I should point out that FSX can be used against any filesystem, and
> that there are reports locally (at Apple) that it's great for killing
> FreeBSD machines. I wasn't able to reproduce this when I tried, but I
> may not have let it run long enough.
Oh, it blows freebsd.apple.com right out of
:
:
:I should point out that FSX can be used against any filesystem, and
:that there are reports locally (at Apple) that it's great for killing
:FreeBSD machines. I wasn't able to reproduce this when I tried, but I
:may not have let it run long enough.
Well, I already found and tracked down
I should point out that FSX can be used against any filesystem, and
that there are reports locally (at Apple) that it's great for killing
FreeBSD machines. I wasn't able to reproduce this when I tried, but I
may not have let it run long enough.
> Oooh. Very cool! I'll start messing with i
> The only thing I get is a math exception because "closeprob" is zero
> since no -c option was given.
>
> Can you provide some sample parameters please ?
Hmmm, how strange, now that I look at the code it's obvious that a
divide by zero will occur with a zero closeprob and the docs state the
def
In message <[EMAIL PROTECTED]>, Jordan Hubbard writ
es:
>Usage:
> cc fsx.c -o fsx
> ./fsx /some/nfs/mounted/scratchfile
> [ ** kaboom! ** ]
The only thing I get is a math exception because "closeprob" is zero
since no -c option was given.
Can you provide some sample parameters
In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: Oooh. Very cool! I'll start messing with it (oops, that's going to
: make both Paul and Alfred annoyed with me!)
Well, I can understand you not wanting to upset Paul, but anything
that annoys Alfred can't be all bad, can it :-)
Wa
Oooh. Very cool! I'll start messing with it (oops, that's going to
make both Paul and Alfred annoyed with me!)
-Matt
:It came up in a meeting today at Apple just how fragile the BSD NFS
:implementation was before significant work was put in to st
It came up in a meeting today at Apple just how fragile the BSD NFS
implementation was before significant work was put in to stabilizing it,
and in that discussion came up a little test tool written originally by
Avie Tevanian and subsequently improved by one of the folks here.
This tool basicall
50 matches
Mail list logo
