Is the intention to eventually replace the zfs code in src/ ? What will be the
long-term relationship between src/ and ports/ for this?
Scott
> On Apr 17, 2020, at 12:35 PM, Ryan Moeller wrote:
>
> FreeBSD support has been merged into the master branch of the openzfs/zfs
> repository, and t
> On Nov 13, 2018, at 11:11 AM, Harry Schmalzbauer wrote:
>
> Am 13.11.2018 um 19:02 schrieb Scott Long:
>>> On Nov 12, 2018, at 10:03 AM, Harry Schmalzbauer wrote:
>>>
>>> Am 11.06.2018 um 20:28 schrieb Harry Schmalzbauer:
>>>> Am 05.06.2018 u
> On Nov 12, 2018, at 10:03 AM, Harry Schmalzbauer wrote:
>
> Am 11.06.2018 um 20:28 schrieb Harry Schmalzbauer:
>> Am 05.06.2018 um 19:54 schrieb Scott Long:
>> …
>>>>>> Late in the 11.2 phase, I identified this commit as a regression for MSI
>>&
It’s harmless unless you run your machine under severe and sustained memory
exhaustion.
Scott
> On Nov 2, 2018, at 8:15 AM, Harry Schmalzbauer wrote:
>
> Hello,
>
> unnfortunately I can't determine if this is begnin, so I'd like to ask the
> experts:
>
> uma_zalloc_arg: zone "64" with the
> On May 1, 2016, at 9:07 AM, Trond Endrestøl
> wrote:
>
> On Wed, 27 Apr 2016 13:46-0400, Scott Long wrote:
>
>> Thanks for the report. I might be mistaken, but the default system
>> is not configured to direct devd messages to user.info, so I didn’t
>&g
Hi Trond,
Thanks for the report. I might be mistaken, but the default system is not
configured to direct devd messages to user.info, so I didn’t see this during my
development. However, what you’re reporting is definitely annoying, so Warner
Losh and I are working on a solution.
Scott
> On
> On Mar 8, 2016, at 11:02 AM, Slawa Olhovchenkov wrote:
>
> On Tue, Mar 08, 2016 at 10:56:39AM -0800, Scott Long wrote:
>
>>
>>> On Mar 8, 2016, at 10:48 AM, Slawa Olhovchenkov wrote:
>>>
>>> On Tue, Mar 08, 2016 at 10:34:23AM -0800, Scott Long
> On Mar 8, 2016, at 10:48 AM, Slawa Olhovchenkov wrote:
>
> On Tue, Mar 08, 2016 at 10:34:23AM -0800, Scott Long wrote:
>
>>
>>> On Mar 8, 2016, at 10:07 AM, Slawa Olhovchenkov wrote:
>>>
>>> On Mon, Mar 07, 2016 at 02:10:12PM +0300, Slawa Olh
> On Mar 8, 2016, at 10:07 AM, Slawa Olhovchenkov wrote:
>
> On Mon, Mar 07, 2016 at 02:10:12PM +0300, Slawa Olhovchenkov wrote:
>
>> This allocated one for all controllers, or allocated for every
>> controller?
>
> It’s per-controller.
>
> I’ve thought about making t
> On Mar 6, 2016, at 10:04 PM, Slawa Olhovchenkov wrote:
>
> On Sun, Mar 06, 2016 at 06:20:06PM -0800, Scott Long wrote:
>
>>
>>> On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
>>>
>>> On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long w
> On Mar 6, 2016, at 1:27 PM, Slawa Olhovchenkov wrote:
>
> On Sun, Mar 06, 2016 at 01:10:42PM -0800, Scott Long wrote:
>
>> Hi,
>>
>> The message is harmless, it's a reminder that you should tune the kernel for
>> your workload. When the messag
Hi,
The message is harmless, it's a reminder that you should tune the kernel for
your workload. When the message is triggered, it means that a potential
command was deferred, likely for only a few microseconds, and then everything
moved on as normal.
A command uses anywhere from 0 to a few
This is really weird. According to what you’ve posted, it’s advertising itself
as an SMBus controller with no BARs. Maybe you’re passing through the wrong
device, or someone added the wrong PCI device id data to the driver?
Scott
> On Sep 7, 2015, at 11:34 AM, Bradley W. Dutton
> wrote:
>
On Apr 23, 2013, at 4:33 AM, Steven Hartland wrote:
>>>
>>> If we can't reach an agreement, I'm happy to wrap the relevant bits with
>>> an "if (bootverbose)", but I really feel users should have some way to
>>> see this information outside of bootverbose.
>> Both da and ada drivers already hav
Your meta-commentary here is irritating.
They're called "quirks" because that is the named given to them in CAM>
Scott
On Apr 23, 2013, at 9:33 AM, Adrian Chadd wrote:
> .. are we really debating this?
>
> Stop calling them quirks. That sounds like something that won't mess
> up your actual r
On Mar 31, 2013, at 7:04 AM, Victor Balada Diaz wrote:
> On Wed, Mar 27, 2013 at 11:22:14PM +0200, Alexander Motin wrote:
>> Hi.
>>
>> Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA
>> stack, using only some controller drivers of old ata(4) by having
>> `options ATA_CA
On Mar 28, 2013, at 8:00 AM, Ian Lepore wrote:
> On Thu, 2013-03-28 at 09:17 +0200, Alexander Motin wrote:
>> On 28.03.2013 02:43, Adrian Chadd wrote:
>>> My main concern with the new stuff is that it requires CAM and that's
>>> reasonably big compared to the standalone ATA code.
>>>
>>> It'd b
On Mar 27, 2013, at 6:43 PM, Adrian Chadd wrote:
> My main concern with the new stuff is that it requires CAM and that's
> reasonably big compared to the standalone ATA code.
>
>From a code execution standpoint? No, it's not.
> It'd be nice if we could slim down the CAM stack a bit first; it
On Aug 6, 2012, at 12:06 PM, Gleb Smirnoff wrote:
> Michael,
>
> On Sat, Aug 04, 2012 at 12:49:49PM -0400, Michael Butler wrote:
> M> Something in -current and recently MFC'd to -stable is causing all of my
> M> gmirror drives to rebuild on reboot :-(
> M>
> M> Being remote and these being pr
On Jun 5, 2012, at 6:16 PM, Scott Long wrote:
>
> Yes, we are indeed using FreeBSD at Netflix! For those who are interested, I
> recently moved from Yahoo to Netflix to help support FreeBSD for them, and
> I'm definitely impressed with what is going on there. Other than a fe
On Jun 7, 2012, at 3:09 AM, Daniel Kalchev wrote:
>
>
> On 06.06.12 03:16, Scott Long wrote:
>
> [...]
>> Each disk has its own UFS+J filesystem, except for
>> the SSDs that are mirrored together with gmirror. The SSDs hold the OS image
>> and cache some o
On Jun 5, 2012, at 6:42 PM, David Magda wrote:
> On Jun 5, 2012, at 20:16, Scott Long wrote:
>
>> If you have any questions, let me know or follow the information links on the
>> OpenConnect web site.
>
> Out of curiosity, given that Linux seems popular in so many
On Jun 5, 2012, at 9:56 AM, Benjamin Francom wrote:
> I just saw this, and thought I'd share:
>
> Open Connect Appliance Software
>
> Netflix delivers streaming content using a combination of intelligent
> clients, a central control system, and a network of Open Connect appliances.
>
> When de
On Feb 20, 2012, at 12:24 PM, Alex Samorukov wrote:
> On 02/15/2012 05:50 AM, Scott Long wrote:
>>
>> What would be nice is a generic caching subsystem that any FS can use
>> - similar to the old block devices but with hooks to allow the FS to
>> request read-ahead
On Feb 14, 2012, at 1:02 PM, Peter Jeremy wrote:
> On 2012-Feb-13 08:28:21 -0500, Gary Palmer wrote:
>> The filesystem is the *BEST* place to do caching. It knows what metadata
>> is most effective to cache and what other data (e.g. file contents) doesn't
>> need to be cached.
>
> Agreed.
>
>
On Feb 14, 2012, at 4:34 PM, Victor Balada Diaz wrote:
> On Tue, Feb 14, 2012 at 03:09:58PM -0800, Jeremy Chadwick wrote:
>> On Tue, Feb 14, 2012 at 11:15:27PM +0100, Victor Balada Diaz wrote:
>>> On Tue, Feb 14, 2012 at 06:17:19PM +0100, Harald Schmalzbauer wrote:
schrieb Jeremy Chadwick am
On Jul 20, 2011, at 3:54 AM, Stefan Esser wrote:
>
> This is a very good idea, IMHO.
>
> When I committed pciconf back in 1996 (it had been contributed by
> gwollman) for PCI 1.0 (at a time when their was no standard for PCI to
> PCI brigdes, yet ;-) ), the current format seemed sensible, but the
On Jul 19, 2011, at 7:31 AM, John Baldwin wrote:
>>
>> If we're going to change it, might as well break it down into 4 fields.
>> Maybe
>> we retain the old format under a legacy switch and/or env variable for users
>> that have tools that parse the output (cough yahoo cough).
>
> The only reas
On Jul 18, 2011, at 3:14 PM, John Baldwin wrote:
> On Monday, July 18, 2011 5:06:40 pm Scott Long wrote:
>> On Jul 18, 2011, at 12:02 PM, John Baldwin wrote:
>>> On Friday, July 15, 2011 6:07:31 pm Mark McConnell wrote:
>>>> Dear folks,
>>>>
>>
On Jul 18, 2011, at 12:02 PM, John Baldwin wrote:
> On Friday, July 15, 2011 6:07:31 pm Mark McConnell wrote:
>> Dear folks,
>>
>> I have two LSI raid cards, one of which (SCSI 320-I) supports
>> 64-bit DMA when 4GB+ of DDR is present and another which
>> does not (SATA 150-D) . Consquently I'v
On Jun 30, 2011, at 4:28 AM, Ivan Voras wrote:
> On 29/06/2011 23:03, Mark Saad wrote:
>
>> The svn sources are here http://svn.freebsd.org/base/projects/suj/8/ .
>>
>> Why would suj not make it into 8-STABLE ?
>
> It is a too large patch, and it changes a lot of important, known and
> working
On Jun 15, 2010, at 6:22 PM, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 2010/06/15 17:05, Sean Bruno wrote:
>> On Tue, 2010-06-15 at 17:10 -0500, Sean Bruno wrote:
>>> http://svn.freebsd.org/viewvc/base?limit_changes=0&view=revision&revision=208361
>>>
>>> I'm not su
On Apr 29, 2010, at 10:56 PM, Alexander Motin wrote:
> Scott Long wrote:
>> On Apr 29, 2010, at 7:47 AM, Robert Noland wrote:
>>>
>>> Scott Long wrote:
>>>> On Apr 29, 2010, at 2:50 AM, Pete French wrote:
>>>>>> Thanks. First step succes
On Apr 29, 2010, at 7:47 AM, Robert Noland wrote:
>
>
> Scott Long wrote:
>> On Apr 29, 2010, at 2:50 AM, Pete French wrote:
>>>> Thanks. First step successful - I can steadily reproduce problem on
>>>> CURRENT. raidtest with 200 I/O streams over gm
On Apr 29, 2010, at 2:50 AM, Pete French wrote:
>> Thanks. First step successful - I can steadily reproduce problem on
>> CURRENT. raidtest with 200 I/O streams over gmirror of two disks on same
>> channel triggers issue in seconds. Any I/O on channel dying after both
>> disks report "Queue full"
On Jan 19, 2010, at 9:12 AM, Alexander Motin wrote:
Hi.
I've made a patch, that should solve set of problems of CAM ATA and
CAM
generally. I would like to ask for testing and feedback.
What patch does:
- It unifies bus reset/probe sequence. Whenever bus attached at boot
or
later, CAM wi
Did you ever get a resolution for this? The 6.x bugs definitely need
to be fixed. The reported timeouts on 7.x might be due to the adapter
taking a log time to do the command.
Scott
On Oct 22, 2009, at 8:30 AM, pluknet wrote:
2009/10/15 John Baldwin :
On Thursday 15 October 2009 5:51:19
xactly what the error message means, but out of
curiosity what kind of hardware are you running? A PERC6 controller
perhaps?
Yes, mfi0: .
You may want to contact Scott Long, sco...@freebsd.org, to see if he can
help. I believe he's the author/maintainer of the mfi(4) driver. He may
Andre Oppermann wrote:
Scott Long wrote:
Andre Oppermann wrote:
Today I upgraded an AMD64 server from FreeBSD 6.4 to 7-STABLE and got
a big
nasty surprise with the Areca RAID controller:
arcmsr0: mem 0xfdbff000-0xfdb40 irq16 at device 14.0 on pci18
ARECA RAID ADAPTER0: Driver Version
Andre Oppermann wrote:
Today I upgraded an AMD64 server from FreeBSD 6.4 to 7-STABLE and got a big
nasty surprise with the Areca RAID controller:
arcmsr0: mem 0xfdbff000-0xfdb40 irq16 at device 14.0 on pci18
ARECA RAID ADAPTER0: Driver Version 1.20.00.15 2007-10-07
ARECA RAID ADAPTER0: FIRM
The just-released 7.2-RC2 should fix this problem. Please let me
know ASAP if it works for you.
Scott
Jeroen Hofstee wrote:
Hello All,
I encountered the same problem as reported to this list earlier,
http://lists.freebsd.org/pipermail/freebsd-stable/2009-February/048305.html,
but then with
Danny Braniss wrote:
Danny Braniss wrote:
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of rela
Danny Braniss wrote:
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of related commits. Try
upda
Danny Braniss wrote:
it seems March 12 was a bit off :-)
it took some time, but I managed to close the gap:
189100 ok
189150 fails
I will continue tomorrow, but this should be helpful.
189150 is in the middle of a big string of related commits. Try
updating to the following
Danny Braniss wrote:
Danny Braniss wrote:
at least for me :-)
[and sorry for the cross posting]
old (March 12 , i know need the svn rev number but...)
None of the commit activity on March 12 is jumping out at me as being
suspicious. However, you are now the second person who has told me
abou
Danny Braniss wrote:
at least for me :-)
[and sorry for the cross posting]
old (March 12 , i know need the svn rev number but...)
None of the commit activity on March 12 is jumping out at me as being
suspicious. However, you are now the second person who has told me
about AMR problems in 7.
en the drive is reconnected and the rebuild completes.
This is apparently some problem in the CAM layer, not the mpt driver, but
it's something to be aware of. Scott Long has noted that this is being
worked on in 8.x.
Yes, I tried to remove a drive today. Of course I need to see if it
w
Bruce Evans wrote:
On Tue, 17 Feb 2009, Gary Jennejohn wrote:
I tested this with an Adaptec 29160. I saw no real improvement in
performance, but also no regressions.
I suspect that the old disk I had attached just didn't have enough
performance reserves to show an improvement.
My test scenar
subclass = RAID
root:# camcontrol tags da0
(pass0:asr0:0:0:0): device openings: 255
On Monday 16 February 2009, Scott Long wrote:
FWI. I need lots of testing on this. Only real SCSI controllers,
please, not RAID controllers (except for MPT-SCSI with
. FreeBSD 6 is only affected by this problem
when CAM_NEW_TRAN_CODE is enabled.
Scott
Original Message
Subject: svn commit: r188671 - head/sys/cam
Date: Mon, 16 Feb 2009 14:57:15 + (UTC)
From: Scott Long
To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
svn-src-h
Ivan Voras wrote:
2009/2/13 Scott Long :
Ivan Voras wrote:
Scott Long wrote:
I have committed a fix for this problem for FreeBSD 8-CURRENT as of SVN
revision 188570. FreeBSD 7-STABLE will be updated with the fix in a few
days once I've gotten confirmation that the fix works and doesn&#x
Ivan Voras wrote:
Scott Long wrote:
I have committed a fix for this problem for FreeBSD 8-CURRENT as of SVN
revision 188570. FreeBSD 7-STABLE will be updated with the fix in a few
days once I've gotten confirmation that the fix works and doesn't cause
any adverse side-effects. Anyo
Tom Evans wrote:
On Fri, 2009-02-13 at 03:55 -0700, Scott Long wrote:
All,
A major performance regression was introduced to the CAM subsystem in
FreeBSD 7.1. The following configurations are known to be affected:
VMWare ESX
VMWare Fusion
(using bt or lsilogic controller options)
HP CISS
All,
A major performance regression was introduced to the CAM subsystem in
FreeBSD 7.1. The following configurations are known to be affected:
VMWare ESX
VMWare Fusion
(using bt or lsilogic controller options)
HP CISS RAID
Some MPT-SAS combinations with SATA drives attached
(Includes De
Steve Polyack wrote:
Scott Long wrote:
The fix for this that I was thinking of is already in 7.1. There
might still be a driver bug, but I'm leaning more towards the
controller simply being busy. Do you have a reproducible test case
that I could
try?
Scott
We saw this one while ba
Steve Polyack wrote:
We have multiple systems using LSILogic PERC4 cards (PERC4e/Si,
PERC4/DC, amr driver). After recently upgrading two of them from 6.3 to
7.1, we have begun to see the following errors in our logs during heavy
use in both systems:
amr0: Too many retries on command 0x
I might have a fix for this, let me check and get back to you.
Scott
Sent from my iPhone
On Jan 22, 2009, at 12:49 PM, Steve Polyack wrote:
We have multiple systems using LSILogic PERC4 cards (PERC4e/Si,
PERC4/DC, amr driver). After recently upgrading two of them from
6.3 to 7.1, we have
Patrick M. Hausen wrote:
h, all,
On Tue, Nov 04, 2008 at 03:32:01PM +0100, d_elbracht wrote:
Hi list,
can someone please explain, why
stat -x /dev/da1
show the SCSI-Drive as a character-device ?
http://www.freebsd.org/doc/en/books/arch-handbook/driverbasics-block.html
Wow that's a co
Oliver Lehmann wrote:
Hi,
I've problems with my 3ware controller. Havingg heavy I/O load (e.g.
running 40 port builds the day over with tinderbox which involves
un-taring a whole FreeBSD tree 40 times), my system hangs with the well
known
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2,
JoaoBR wrote:
On Sunday 12 October 2008 14:10:36 Scott Long wrote:
I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS
controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac
driver) with a 5th generation RAID card with 8G of ram, both have no
such corruption problems
Gary Jennejohn wrote:
On Sat, 11 Oct 2008 09:52:50 -0700
Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
[big snip]
Is your LSI SAS controller driven by mpt(4) or mfi(4)?
Let's break down what we know for sure at this point:
aac(4) - not affected
aha(4) - unknown
ahb(4) - unknown
ahc(4) - affected
SCSI then you'll have to limit
memory to 3.5 GB.
What you're saying is that Adaptec and LSI Logic SCSI controllers behave
badly (and can cause data loss) on amd64 systems which contain more than
3.5GB of RAM. This is a very big claim.
Have you talked to Scott Long about this?
Please
Ken Smith wrote:
I'm with Scott in that I like the "other distros" being around. I don't
think that necessarily means we shouldn't try harder. But IMHO trying
harder needs to be reflected in a new installer. Lets face it,
sysinstall s*cks... For the type of folks who want the installer to do
Dan Allen wrote:
On 3 Sep 2008, at 1:53 PM, Guido Falsi wrote:
If you just want na instant workstation, why you just don't try
Freesbie or something like that?
Because I want something from the source -- from the main team -- and
not something downstream.
What's wrong with "downstream"?
On Wed, 3 Sep 2008, Igor Sysoev wrote:
On Wed, Sep 03, 2008 at 03:39:55PM +0300, Kostik Belousov wrote:
On Wed, Sep 03, 2008 at 01:53:52PM +0400, Igor Sysoev wrote:
Hi,
could anyone tell what does vfs.ffs.rawreadahead enable ?
As I understand it's used in DIRECTIO code that allows read data
d
On Wed, 3 Sep 2008, Igor Sysoev wrote:
On Wed, Sep 03, 2008 at 10:44:46AM -0600, Scott Long wrote:
On Wed, 3 Sep 2008, Igor Sysoev wrote:
On Wed, Sep 03, 2008 at 03:39:55PM +0300, Kostik Belousov wrote:
On Wed, Sep 03, 2008 at 01:53:52PM +0400, Igor Sysoev wrote:
Hi,
could anyone tell
Jo Rhett wrote:
On Jun 4, 2008, at 5:44 PM, Scott Long wrote:
Really, if it's such a big issue that you have time to bitch an moan
on the mailing lists, I don't understand why you don't have time to also
help a goddamned developer identify the problem. Are you actually
experi
Jo Rhett wrote:
On Jun 4, 2008, at 5:05 PM, Scott Long wrote:
Jo Rhett wrote:
On Jun 4, 2008, at 12:00 PM, Scott Long wrote:
Can you describe the bugs that are affecting you?
gmirror failures, 3ware raid driver timeouts, bge0 problems. All
three in production use on dozens of systems
Jo Rhett wrote:
On Jun 4, 2008, at 12:00 PM, Scott Long wrote:
Can you describe the bugs that are affecting you?
gmirror failures, 3ware raid driver timeouts, bge0 problems. All three
in production use on dozens of systems.
Give me specific details on the 3ware and bge problems.
Scott
Jo Rhett wrote:
Okay, I totally understand that FreeBSD wants people to upgrade from 6.2
to 6.3. But given that 6.3 is still experiencing bugs with things that
are working fine and stable in 6.2, this is a pretty hard case to make.
Can you describe the bugs that are affecting you?
This is
Andriy Gapon wrote:
on 16/05/2008 19:48 Scott Long said the following:
There is no write support in UDF in FreeBSD. When I wrote the fs code,
packet writing was the only way to do discrete writes, and it's very
hard to make that work with a traditional VM system. Now with DVD+R,
it'
Jeremy Chadwick wrote:
On Fri, May 16, 2008 at 07:08:11PM +0300, Stefan Lambrev wrote:
From man mount_udf (FreeBSD7)
HISTORY
The mount_udf utility first appeared in FreeBSD 5.0.
FreeBSD 7.0 March 23, 2002 FreeBSD
7.0
I have no idea for newfs_udf ,
Mark Kirkwood wrote:
Jeremy Chadwick wrote:
I am too, but PRs that are 2 years old which include patches for severe
bugs that affect reliability of RAID is (in my opinion) not acceptable.
I've been spanked over saying this before ("you don't understand how
open source works"), but necessity eas
Jack Vogel wrote:
On Sat, May 3, 2008 at 4:45 AM, Kostik Belousov <[EMAIL PROTECTED]> wrote:
On Sat, May 03, 2008 at 12:14:32AM -0700, Jack Vogel wrote:
I got the new drivers in Friday afternoon for those that don't see CVS
> messages.
>
> The igb driver is for 82575 and 82576 adapters, i
Stephen Hurd wrote:
This shows you've had 4 reallocated sectors, meaning your disk does in
fact have bad blocks. In 90% of the cases out there, bad blocks
continue to "grow" over time, due to whatever reason (I remember reading
an article explaining it, but I can't for the life of me find the U
Adrian Penisoara wrote:
Hi,
I would agree with Mark and Jim, this is a serious issue for enterprise
servers. Yet another example where I would have wanted to see a more
supportive response from the FreeBSD project members, like Robert Watson
just did. This would benefit keeping a good relation
Dag-Erling Smørgrav wrote:
Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
Purely in the interest of showing off, here is my version. It is 81
bytes shorter than yours, it is valid C99 with POSIX extensions (yours
is not), and it produces 11,450 files in about 0.2% of the time yours
takes to pr
driver instead. Please direct any questions or concerns about
this to me. The driver will also be removed from the upcoming 7.0
release.
Scott Long wrote:
scottl 2008-02-03 07:28:39 UTC
FreeBSD src repository
Modified files:(Branch: RELENG_7)
sys/i386/confGENERIC NOTES
Josh Endries wrote:
Hello,
I'm buying a new server and will put 6.3 on it and would like to use
SAS; normally I use 3ware SATA. I've been reading a lot including man
pages but can't seem to find definitive information on SAS cards that
are well-supported and work well. I've found reports that
Eirik Øverby wrote:
On Jan 22, 2008, at 7:23 PM, Marius Strobl wrote:
On Tue, Jan 22, 2008 at 07:16:16AM +0100, Eirik verby wrote:
Hi list,
by disabling the isp driver (set hint.isp.o.disabled=1), the system
comes up. This of course denies us access to the external disk array
hosted by th
David Wood wrote:
[ambrisko@ and scottl@ added to CCs]
Hi there,
What really needs to happen as a result of this thread is the following,
and I would appreciate volunteers taking up these tasks in some form:
1) FAQ entries written/updated/clarified/advertised as to how FreeBSD,
disklabels, F
Vivek Khera wrote:
On Jan 15, 2008, at 1:40 PM, John Baldwin wrote:
Where can one go to read up on what MSI is and how it helps us?
Is enabling it just setting a sysctl? Does that have to be done in
loader.conf or can it happen later?
loader.conf (though it is now default on in RELENG_6).
Vivek Khera wrote:
On Jan 15, 2008, at 1:40 PM, John Baldwin wrote:
Where can one go to read up on what MSI is and how it helps us?
Is enabling it just setting a sysctl? Does that have to be done in
loader.conf or can it happen later?
loader.conf (though it is now default on in RELENG_6).
John Baldwin wrote:
On Monday 07 January 2008 10:08:57 pm Adrian Wontroba wrote:
I've recently switched some of my home systems to RELENG7.
All seemed fairly well until I tried printing a CUPS test page on my
backup and print server to an elderly Laserjet IIIp, where I seem to
have a reproducib
Ed Maste wrote:
On Wed, Jan 02, 2008 at 10:19:15AM -0500, Vivek Khera wrote:
On Jan 2, 2008, at 3:54 AM, Mike Andrews wrote:
Command Error: the current AFAAPI.DLL.>
In my experience, this was caused by the firmware rev of the adaptec
card. Basically, the combination of FreeBSD, amd64, and
Mike Tancsa wrote:
At 12:12 PM 12/24/2007, Scott Long wrote:
For others who might want help with this, tweaking
vfs.ufs.dirhash_maxmem is what is needed. A bit of a balancing act is
needed if you're on i386 since you'll risk exhausting KVA unless you
also tweak KVA_PAGES.
Adrian Chadd wrote:
On 25/12/2007, Brett Glass <[EMAIL PROTECTED]> wrote:
It sounds like you're pretty convinced you know what the problem is.
Again, I'd have to instrument either the FreeBSD kernel or Squid to
be 100% sure. But it APPEARS that it's a problem with large
numbers of threads tryin
Brett Glass wrote:
At 09:10 AM 12/24/2007, Scott Long wrote:
Did you also nuke malloc debugging?
I believe I did. I tried to take out all debugging to make it a fair test.
They were. The drives are SATA.
Connected to what controller?
Whatever comes standard on the Intel S5000
Brett Glass wrote:
At 07:14 AM 12/24/2007, Scott Long wrote:
Brett,
There could be several problems here:
1. WITNESS, INVARIANTS, malloc debugging. Are any of these turned on for you?
I don't recall if malloc debugging got turned off yet for the
7.0 snapshots.
I nuked debugging w
Brett Glass wrote:
I will need to build several Web caches over the next few months, and
just took advantage of the Christmas lull (and a snowy day, when I
couldn't work outside) to test FreeBSD 7.0 BETA 4 to see how it will
perform at this task. I built up a 4 core FreeBSD box, and asked a
fr
Bruce Evans wrote:
On Mon, 17 Dec 2007, David G Lawrence wrote:
One more comment on my last email... The patch that I included is not
meant as a real fix - it is just a bandaid. The real problem appears to
be that a very large number of vnodes (all of them?) are getting synced
(i.e. calling f
Jack Vogel wrote:
I was curious, is there any organized method to funnel new IDs into
the code or is it just willy nilly as a driver owner notices it?
I will be having some patches to add IDs from this bringup I've
been working on and wondered if there was a 'canonical' way to
make this stuff ha
John Baldwin wrote:
On Wednesday 07 February 2007 04:58:17 am Daniel O'Connor wrote:
On Wednesday 07 February 2007 19:23, Artem Kuchin wrote:
FreeBSD/amd64 is a very young platform on FreeBSD. While the core FreeBSD
kernel and base system components are generally fairly robust, there are
likely
Jack Vogel wrote:
I have found that the FAST interrupt handling is implicated
in the watchdog resets that I have seen.
What I plan to do is revert to the way 6.2 had things, meaning
that FAST interrupts will be available but defined off by default.
I wanted to know if anyone has an issue with
Jack Vogel wrote:
On 10/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
At Mon, 29 Oct 2007 10:45:17 -0700,
Jack Vogel wrote:
I have an important decision to make and I thought rather than just make
it and spring it on you I'd present the issues and see what opinions were.
Our newer hardwa
CmdLnKid wrote:
_ ._ _ , _ ._
(_ ' ( ` )_ .__)
( ( () `) ) _)
(__ (_ (_ . _) _) ,__)
`~~`\ ' . /`~~`
,:::
Boris Samorodov wrote:
Hi!
Since nobody answered so far, here is my two cents. I'm not an expert
here so it's only my imho.
On Wed, 17 Oct 2007 22:52:49 +0400 Alexey Popov wrote:
interrupt total rate
irq6: fdc0 8 0
irq14: ata
Jan Mikkelsen wrote:
Scott Long wrote:
Ivan Voras wrote:
Either that or file system errors. Does fsck run ok or does
it say
anything unusual?
No, filesystem corruption has nothing to do with g_vfs_done
messages.
Well, perhaps not directly but I think filesystem corruption can
indirectly
Ivan Voras wrote:
d_elbracht wrote:
we are trying to diagnose errors seen on 6.2, SMP, amd64, cvsup'ed of
2007-10-09
Mainboard is a Tyan Thunder h2000M (S3992-E) with 16 GB RAM and 2 x Opteron
2216, da3 is on a 3ware 9550-12
we are seeing this error:
g_vfs_done():da3s1a[READ(offset=81064794762
Lars Eighner wrote:
On Sun, 14 Oct 2007, d_elbracht wrote:
we are trying to diagnose errors seen on 6.2, SMP, amd64, cvsup'ed of
2007-10-09
Mainboard is a Tyan Thunder h2000M (S3992-E) with 16 GB RAM and 2 x
Opteron
2216, da3 is on a 3ware 9550-12
we are seeing this error:
g_vfs_done():da3s
1 - 100 of 473 matches
Mail list logo
