Peter B wrote:
3ware 9650 in RAID6 mode with firmware version 3.08.00.004 seems to cause
data corruption when rebuilding a single disc with raid6.
http://www.webmasternetwork.se/f4t23551.html (Swedish)
I thought this was serious enough for people to know. If another mailinglist
is more
3ware 9650 in RAID6 mode with firmware version 3.08.00.004 seems to cause
data corruption when rebuilding a single disc with raid6.
http://www.webmasternetwork.se/f4t23551.html (Swedish)
I thought this was serious enough for people to know. If another mailinglist
is more appropiate
Peter B wrote:
3ware 9650 in RAID6 mode with firmware version 3.08.00.004 seems to cause
data corruption when rebuilding a single disc with raid6.
http://www.webmasternetwork.se/f4t23551.html (Swedish)
I thought this was serious enough for people to know. If another mailinglist
is more
We are trying to fix a bug in the uhid interrupt handler/driver
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/72935
where it can inadvertently walk into another handler working with
clist data structures in sys/kern/tty_subr.c.
Uhid is a bio class device, which means that its not masked when
FreeBSD hackers,
Here is a message I sent to freebsd-questions and I was hoping I could
get some help debugging this.
Thanks
FYI the only way I could recover the partitions semi successfully was
rebuilding the arrays identically and then use gpart to recover the
partition info. This would
On Tue, Jul 15, 2003 at 06:26:24AM -0700, Sumit Shah wrote:
Here is a message I sent to freebsd-questions and I was hoping I could
get some help debugging this.
It seems very unlikely that restarting mountd cound cause an error
like:
ad4: hard error reading fsbn 242727552
The error means
Thanks for the reply.
ad4: hard error reading fsbn 242727552
The error means that that the disk said that there was an error
trying to read this block. You say that when you rebooted that the
controler said a disk had gone bad, so this would sort of confirm
this. (I could believe that restarting
that linux has a problem with
data corruption when using these controllers disabled IDE DMA in linux.
Thinking that FreeBSD was immune (these boxes spend 90% of their time
in FreeBSD doing driver development crashing frequently, haven't
lost a fs yet), I continued to run the disk at UDMA33
Søren Schmidt writes:
Hmm, the problem is known, but belived to be fixed *IF* your BIOS
setup things the right way. I've newer seen the problem on my
ASUS CUR-DLS, but I have several reports of TYAN's (forgot the model#)
that fails all over. I have not verified if ASUS has done some
Andrew Gallatin wrote:
Søren Schmidt writes:
However the Serverworks
ROSB4 chips is not one I would recommend using, if you need serious
ATA support on such a board, install a Promise TX2 or later or a
HPT370 or later ...
I don't much care about serious ATA support on these
Terry Lambert writes:
So.. Is PIO safe? Is there any sort of CRC being done on PIO data?
He just said: if your chipset is programmed correctly
by the BIOS, then there will not be a problem, but
apparently, there is a very narrow band of correctly
(perhaps even only a single
Andrew Gallatin wrote:
Terry Lambert writes:
So.. Is PIO safe? Is there any sort of CRC being done on PIO data?
He just said: if your chipset is programmed correctly
by the BIOS, then there will not be a problem, but
apparently, there is a very narrow band of correctly
On Wed, 20 Feb 2002, Terry Lambert wrote:
FWIW, Julian had to fix a similar problem by programming
the heck out of a Cyrix MediaGX chipset via a custom
BIOS.
*snort* (wakes up)..
wha? wha?
what is the problem?
The one I had to program around was bad DMA for transfers not on a 16 byte
basically yes.
there is a CRC on the disk block right?
On Wed, 20 Feb 2002, Andrew Gallatin wrote:
Terry Lambert writes:
So.. Is PIO safe? Is there any sort of CRC being done on PIO data?
He just said: if your chipset is programmed correctly
by the BIOS, then there will not
Terry Lambert writes:
Andrew Gallatin wrote:
Terry Lambert writes:
So.. Is PIO safe? Is there any sort of CRC being done on PIO data?
He just said: if your chipset is programmed correctly
by the BIOS, then there will not be a problem, but
apparently, there is a
It seems Terry Lambert wrote:
Andrew Gallatin wrote:
Terry Lambert writes:
So.. Is PIO safe? Is there any sort of CRC being done on PIO data?
He just said: if your chipset is programmed correctly
by the BIOS, then there will not be a problem, but
apparently, there is a
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 fsck on
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 damn
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 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 trust data to a port of
JFS or XFS.
This is a killer feature.
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
JFS
* 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
be available
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 that's not
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 trust
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
At 12:24 PM -0800 12/16/01, Matthew Dillon wrote:
program runs fine in an overnight test. We still have a known issue
with out-of-order operations from nfsiod's that apparently may come
up after a week or so of testing. I asked Jordan to try to track down
the NeXT guy who fixed
:...
:with out-of-order operations from nfsiod's that apparently may come
:up after a week or so of testing. I asked Jordan to try to track down
:the NeXT guy who fixed that one in the old NFS stack.
:
:This bug showed up recently here with fsx testing. I seem to have fixed it
:last
At 5:22 PM -0800 12/15/01, Matthew Dillon wrote:
Ho! Will do. I'm going to try to speed things up a bit by
having the NFS server export an MFS filesystem.
-Matt
Two things I've done to speed it up are to restrict the size of transfers
(use the
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-changes
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
:Two things I've done to speed it up are to restrict the size of transfers
:(use the -o flag) and eliminate all the size checks (use the -n flag).
:
:Why would MFS be much faster than UFS? On the server doesn't the whole
:file end up cached? ...and the metadata changes likewise via softupdates.
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 has
got
At 10:08 PM -0800 12/12/01, Matthew Dillon wrote:
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
:Once it runs aok for a few million operations, try concurrently running:
:
:#! /bin/sh
:while :
:do
: sync
: sleep 1
:done
:
:In OS X I used that to flush :) out a couple more bugs.
:
:--
:Conrad Minshall, [EMAIL PROTECTED], 408 974-2749
:Apple Computer, Mac OS X Core Operating Systems
:
: 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
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.
Ok, here is the latest patch set. This patch set survived an
overnight run of the nfs torture test that Jordan posted... it
got through 597,000 test calls over NFSv3, 367,000 over NFSv2, and
1.35 million on a local filesystem.
This patch set is for -stable. It again has
On Thu, 13 Dec 2001, Matthew Dillon wrote:
Ok, here is the latest patch set. This patch set survived an
overnight run of the nfs torture test that Jordan posted... it
got through 597,000 test calls over NFSv3, 367,000 over NFSv2, and
1.35 million on a local filesystem.
Matthew Dillon wrote:
[ ... ]
I would appreciate other VM gurus taking a look at the
vm_page_set_validclean() changes.
[ ... ]
Not to appoint myself a guru or anything...
+#if 1
+ if ((base (DEV_BSIZE - 1)) || (size (DEV_BSIZE - 1))) {
+ int adj;
+
+
:Hmm. I'm OK with a commit to -CURRENT, but would really appreciate it if
:you made it a week before MFC to -STABLE. Given your statement just a few
:lines earlier about needing more review from VM types, that would allow a
:bit more time for necessary review. I agree, given the impending 4.5
On Thu, Dec 13, 2001 at 11:03:54AM -0800, Matthew Dillon wrote:
I can hold-off the vm_page_set_validclean() patch for a week but there
is no reason not to 3-day MFC the rest of the bug fixes.
I would also be more comfortable if we gave this change a week in
-CURRENT. This is great
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 is
: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
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 reader
:Matthew Dillon wrote:
:[ ... ]
: I would appreciate other VM gurus taking a look at the
: vm_page_set_validclean() changes.
:[ ... ]
:
:Not to appoint myself a guru or anything...
:
: +#if 1
: + if ((base (DEV_BSIZE - 1)) || (size (DEV_BSIZE - 1))) {
: + int adj;
: +
:
Terry's interest prompted me to redo my algorithm a bit and write
a program to test it with various combinations of base and size.
I've included the program below. My fixed algorithm appears to
produce the correct results, which is to generate the DEV_BSIZE
aligned range
Matthew Dillon wrote:
Hmm. Well, my code is definitely broken. My 'adj' calculation is
all wrong. However, my size calculation appears to be correct.
(size - adj) is the size of the block after the base has been adjusted
to the next full chunk. The number of chunks we then
Are any of these client-side performance upgrades as well as bug fixes?
On Wed, 12 Dec 2001, Matthew Dillon wrote:
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),
On Wed, 12 Dec 2001, Matthew Dillon wrote:
:
:Are any of these client-side performance upgrades as well as bug fixes?
No, just bug fixes. The softupdates bug fix is server-side. All
the other bug fixes are client side (so far).
:Does the softupdates fix affect normal ffs operations as well?
:
:Mike Silby Silbersack
Yes, we believe so. It's a bug in ftruncate()'s interaction
with softupdates.
-Matt
Matthew Dillon
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
I'm seeing data corruption on the Promise channel of a A7V133,
WITH the southbridge fix applied and NO sound card of any kind in
the system (the built-in is disabled in the bios; current wouldn't boot
at all with it enabled, when I bought the mb). All the cards are
video (a TNT2 card of some
On Sun, 2 Dec 2001, Pete Carah wrote:
I'm seeing data corruption on the Promise channel of a A7V133,
WITH the southbridge fix applied and NO sound card of any kind in
the system (the built-in is disabled in the bios; current wouldn't boot
at all with it enabled, when I bought the mb
On Mon, 18 Jun 2001, Attila Nagy wrote:
I have a mid-loaded server which runs each daemon in jail()-ed
environments. The data space is union-mounted, because nullfs paniced the
kernel when someting did a chroot on it (this was the case with
4.2-STABLE).
On friday I upgraded from 4.3-RC
Hello,
I have a mid-loaded server which runs each daemon in jail()-ed
environments. The data space is union-mounted, because nullfs paniced the
kernel when someting did a chroot on it (this was the case with
4.2-STABLE).
On friday I upgraded from 4.3-RC to the latest 4.3-STABLE and noticed
Thus spake Bill Fumerola ([EMAIL PROTECTED]):
PS. No, it's not something stupid like file flags or something.
No, it was something even stupider. Completely ignore this.
Oh, come on now, tell us the details! :-)
It involves this running in another window:
[hawk-billf] $ while `true`;
I fully expect to be physically assulted by all who I encounter the
next time I'm in California for this act of stupidity.
Physically assaulted? No, why do that when we can point and laugh?
It's legal, and much more devastating.
Just noticed you're in Michigan. Are you aware of any
Out of da blue Adam aka ([EMAIL PROTECTED]) said:
On Thu, 6 Jul 2000, Michael Lucas wrote:
I fully expect to be physically assulted by all who I encounter the
next time I'm in California for this act of stupidity.
Physically assaulted? No, why do that when we can point and
On Thu, Jul 06, 2000 at 08:46:10AM -0400, Michael Lucas wrote:
I fully expect to be physically assulted by all who I encounter the
next time I'm in California for this act of stupidity.
Physically assaulted? No, why do that when we can point and laugh?
It's legal, and much more
[ moved to -advocacy from -hackers ]
On Thu, Jul 06, 2000 at 11:51:29AM -0400, Bush Doctor wrote:
I keep mentioning to bill and others on irc from michigan that someone
should start one :p
Well if anyone is ever down East Lansing way, a couple of co-workers
and I have an informal group.
Well if anyone is ever down East Lansing way, a couple of co-workers
and I have an informal group. Everyone is more than welcome to come
here or maybe we could meet somewhere in between ...
I always wondered why the Voyager Michigan guys were a little screwy :-)
(incidentally also located in
-hackers,
This is the most fucked up thing I've ever experienced with FreeBSD:
[hawk-billf] /home/billf/helpdesk ls
./ ../ Makefilehdesk.c
[hawk-billf] /home/billf/helpdesk cd ..
[hawk-billf] /home/billf ls hdesk
ls: hdesk: No such file or directory
On Wed, Jul 05, 2000 at 04:08:24PM -0400, Bill Fumerola wrote:
PS. No, it's not something stupid like file flags or something.
No, it was something even stupider. Completely ignore this.
--
Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES
e-mail: [EMAIL PROTECTED] / [EMAIL
Bill Fumerola wrote:
On Wed, Jul 05, 2000 at 04:08:24PM -0400, Bill Fumerola wrote:
PS. No, it's not something stupid like file flags or something.
No, it was something even stupider. Completely ignore this.
Oh, come on now, tell us the details! :-)
Cheers,
-Peter
--
Peter Wemm - [EMAIL
On Wed, Jul 05, 2000 at 05:57:56PM -0700, Peter Wemm wrote:
PS. No, it's not something stupid like file flags or something.
No, it was something even stupider. Completely ignore this.
Oh, come on now, tell us the details! :-)
It involves this running in another window:
[hawk-billf]
It may be a compiler optimisation.
i think all memory-mapped registers should be declared volatile to
avoid such things occur. I remember when i was looking at both the
meteor and bt848 drivers, there was some confusion about it.
Depending on when you looked, the stuff you excepted
Please read this. It affects our commercial users.
I'm trying to find out if/how we initialise the PCI bus and any
memory controllers differently in 3.x compared to 2.2.x
Since upgrading from 2.2.x to 3.x or 4.x, many many users have
noticed garbage on the video grabbed by the bt848 in
Please read this. It affects our commercial users.
I'm trying to find out if/how we initialise the PCI bus and any
memory controllers differently in 3.x compared to 2.2.x
Since upgrading from 2.2.x to 3.x or 4.x, many many users have
noticed garbage on the video grabbed by the bt848 in their
68 matches
Mail list logo
