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
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
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
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
@#$@#$ 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
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
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
19 matches
Mail list logo
