Re: tcpdump, rl, sis, fxp and multicast problems

[Roman Le Houelleur]

that's very clever indeed ! Well, I was not quite sure it was
actually performing the TCO (not to say I feel stupid ...).

not very important but wouldn't it be better to set the checksum
to 0 instead of some arbitrary (?) and confusing value then ?

thank you anyway,
Roman.

Kris Kennaway wrote:

On Thu, Jan 18, 2007 at 03:34:46PM +0100, Roman Le Houelleur wrote:

Hi everyone,

It's been about a year or so that I upgrade my box to RELENG_6
from time to time. I got some suprises this week, I've seen a
few things that made me think of hardware problems but some are
definitly soft.

First and easy one, tcpdump -v does not show checksum error
for UDP whereas it does for TCP (same w/ tcpdump -vvv).

checksum : I have a double port fxp 82550 Pro/100 board which
makes plenty of checksum errors (UDP & TCP), I suspect this
is related to checksum offloading but am not sure. I strongly
believe this card was working fine a few days/weeks ago.


And a priori it still is: by definition, checksum offload means that
the OS does not compute the checksum for outgoing packets, so tcpdump
doesn't see a valid checksum either.  Unless you have evidence (from
e.g. observation on another host) that the checksums are not being
computed correctly, this is not a bug.  It is, however, a FAQ ;-)

Kris

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Read_dma timeout - FreeBSD 6-1

[Dominic Marks]

On Fri, 19 Jan 2007 08:02:00 +
"Ikare.run" <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> I've got some troubles with sata disks (Maxtor DiamondMax 10 160go) : 
> this is the second one I use in less than 1 month.
> 
> With the first one, I got more and more ofently TIMEOUT - READ_DMA 
> errors ... so I changed it last week (I thought the disk was broken) ! 
> And now, 10 days after installing the _new_ one, I re-get the sames 
> errors. They appear randomly ...
> 
> No log, no debug messages, just TIMEOUT - READ_DMA in dmesg
> 
> Is there some tools on FreeBSD to test the SATA controler or the disks ? 
>   Some known bugs in drivers ?
> Does anyone get the same problem ?
> 
> PS : when error occurs, the disk make a "click" !?!?

Sounds like it is dying. What controller is this attached to?
Have you tried another cable?

SMART reports are useful only if the error is
detectable / reported.

Dom
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dhclient - new IP via DHCP on WAN - NAT dont work

[Max Laier]

[ Moving badly filed pf(sense) PR to the more appropriate list ]

On Friday 19 January 2007 00:51, Andreas Krauß wrote:
> Hi FreeBSD-Team,
>
> i use "PfSende" a FreeBSD based Firewall-System and have a large
> Problem. Please see
>
> http://cvstrac.pfsense.com/tktview?tn=1207

freebsd-stable@ is clearly the wrong mailing list and you do not give 
enough details, either.  In order to debug this problem we need to know 
the pf rules you (or pfsense in this case) are using.  In order to 
operate with dynamic IPs you need to use the "(ifnX)" syntax - I'm not 
sure if pfsense does this by default.  In addition there is a problem 
with ppp under some circumstances that requires "(tun0:0)" in order to 
fully get the IP update.

>
> Ticket 1207: new IP via DHCP on WAN - NAT dont work
>
> I have the same Problem, described at Ticket #1176
>  - and I down know, why
> this Ticket was Closed without any Result ???
>
> My Pfsense works behind a Cable Modem. Some times i get a new
> WAN-IP-Adress from my Provider via DHCP.
>
> Pfsense updates the Interfaces Page und the complete WebGUI show
> the new IP. But NAT-Connections to my server behind the Firewall dont
> work.
>
> And its not a DNS-Problem. My Server behind the Firewall checks the
> IP, and after a IP-Change a little Scripts make a DNS update via
> nsupdate. So the resolved IP is correct !!
>
> After a reboot -> pfsense and NAT-Connections wirks fine !!
>
> Questions - send me a mail.
>
> Best regards
>
> Andreas Krauss
>
> [Append remarks ]
>
>
>   Remarks:
>
> /2007-Jan-18 16:07:54 by anonymous:/
> We have attempted to fix this with no luck. This is a FreeBSD dhclient
> issue. Please install FreeBSD and post a bug report to
> freebsd-stable@freebsd.org

-- 
/"\  Best regards,  | [EMAIL PROTECTED]
\ /  Max Laier  | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | [EMAIL PROTECTED]
/ \  ASCII Ribbon Campaign  | Against HTML Mail and News


pgpvjOv2bm44K.pgp
Description: PGP signature

Failover-HA-Setup

[Michael Schuh]

Hi Richard,

if you are searching a "native" Cluster filesystem, so your chances
are not really good.
But if you would setup a really HA-Solution w/o SPOF so you can use
CODA-FS. (but hold in mind this has its own price - performance - )

Coda is an successor/fork of the legendary AFS (think from Andrew
Morton?) and IBM. With Coda you can figure out an Network-Filesystem-
server with replication and local caching, so you can get the required
filesystem for mysql mounted rw at boot-time and you have only
to start mysql-server with the suggestet commands and configurations.

For coda look in the ports or at:
http://www.coda.cs.cmu.edu/
i have planned out some tests with it in the near future, but no
practices at this time. My knowledge is only based on the documentation.

greetings

michael
--
michael-schuh.net
Michael Schuh
Preußenstr. 13
66111 Saarbrücken
phone: 0681/8319664
mobil:   0177/9738644
@: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: can we resurrect linux-firefox-1.5 ?

[Ruben van Staveren]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


On 16 Jan 2007, at 20:09, Luigi Rizzo wrote:


Additionally,  i could not find a way to make the flash plugin
work, which is a major annoyance given the amount of flash content
that one finds in the services i use daily (some work related too).


You might give the native firefox a try with linuxpluginwrapper,  
linux-flashplugin-7 and run firefox as


env XLIB_SKIP_ARGB_VISUALS=1 firefox

(or edit /usr/local/bin/firefox and insert a export  
XLIB_SKIP_ARGB_VISUALS=1)


still not optimal but trivial flash stuff should be usable.

- - Ruben

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFFsM+OZ88+mcQxRw0RAsJEAJ92iqOiBJaCJQOfoEzgxlRiH77UEwCfVbdR
ZNj+vZj2iG+VswvvwEYDhTQ=
=WmzW
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

6.2 Release - Adaptec 2130SLP driver?? issue - aac driver

[Jeff Royle]

I could use some advice on this issue I have had with my raid controller. 

I am not really running much on the system yet, postfix, Pf + pflogd, 
rlogind, ssh, bsnmp and ntpd.  While I was just reading a file with less 
the system stopped responding.   I thought it was the network interfaces 
but I was able to ping the interface.  


Once I plugged a monitor into the system I saw this (roughly):

AAC0: COMMAND  TIMEOUT AFTER X number of seconds

Not good :)

Reset of the system resolved the issue and it booted fine.Since the 
controller stopped responding nothing was recorded to my logs.


Now I have to figure out how to prevent that from happening again.

Basic run down on the system and some history...

P4 3.2Ghz
Asus P5MT-S MB
2 x 1GB DDR2 667 memory
Adaptec 2130SLP Raid Controller + battery backup module
2 Segate Ultra320 73GB 15k RPM (mirrored)

I have run this same system hardware testing 6.2-BETA3, RC-1 and RC-2 
without this issue.I was using the driver released by Adaptec while 
testing the pre-release installs 
(http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd6_drv_b11518_tgz.htm).   
You could say I am fairly confidient in the hardware itself.   I have 
put this system through a lot of testing since BETA3.


The 6.2 release kernel has not been customized all that much, I just 
pulled out all the drivers I would never use.To be safe I kept just 
about all scsi devices/card models still in as I continued my testing of 
6.2 release.  

Right now I am going to try taking out aac and aacp then try the driver 
I used in my previous tests.However, since I have run a week without 
this issue it will be hard/impossible tell if this did anything to 
resolve it...I almost want a crash on the old driver :)


So I need some advice...  How best do I debug this issue?

Thanks in advance for any direction you guys can offer me.

Cheers,

Jeff


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Read_dma timeout - FreeBSD 6-1

[Mike Jakubik]

Ikare.run wrote:


PS : when error occurs, the disk make a "click" !?!?




If its making sounds like that, then its a physical problem with the 
drive. Bakcup your data and return it if its still on warranty. Maxtor 
provides troubleshooting tools on their website.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: gmirror disks vs partitions

[Ivan Voras]

Andrew Pantyukhin wrote:

> Yes, but that's the kind of functionality I have always
> expected to be present in software raid solutions. I
> hope I'll live to see this implemented in geom.

For adding drives there's gconcat, for resizing (well, you currently
have to decide on the maximum size in advance) there's gvirstor
(http://wikitest.freebsd.org/gvirstor).

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

x server wakes up slowly

[Zoran Kolic]

Dear all!
I've just installed 6.2 amd64 on nforce 3 mobo and mvidia
5700 graphic card. System looks very fine, fvwm2 shows all
usualy, but graphic server goes up and goes down very, very
slowly. It reads .Xauthority and makes new auth pid in $HOME
directory. At exit, the message is that FreeFontPath refcount
is 2 and should be 1. It fixes it finaly. The same xorg.conf
is as on 6.1.


Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath  "/usr/X11R6/lib/X11/rgb"
ModulePath   "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "Module"
Load  "dbe"
Load  "dri"
Load  "extmod"
Load  "glx"
Load  "record"
Load  "xtrap"
Load  "freetype"
Load  "type1"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/sysmouse"
Option  "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor"  # []
#Option "HWcursor"  # []
#Option "NoAccel"   # []
#Option "ShadowFB"  # []
#Option "UseFBDev"  # []
#Option "Rotate"# []
#Option "VideoKey"  # 
#Option "FlatPanel" # []
#Option "FPDither"  # []
#Option "CrtcNumber"# 
#Option "FPScale"   # []
#Option "FPTweak"   # 
Identifier  "Card0"
Driver  "nv"
VendorName  "nVidia Corporation"
BoardName   "NV36 [GeForce FX 5700LE]"
BusID   "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
DefaultDepth24
SubSection "Display"
Viewport   0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 24
Modes   "1280x1024"
EndSubSection
EndSection


Here in xterm, midnight commander goes up slowly. It
looks like x server problem, but cannot debug it for
now. It should be fast. Do you have any clue? What I'm
missing?

Best regards


 Zoran


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.2 Release - Adaptec 2130SLP driver?? issue - aac driver

[Jeff Royle]

Jeff Royle wrote:

I could use some advice on this issue I have had with my raid controller.
I am not really running much on the system yet, postfix, Pf + pflogd, 
rlogind, ssh, bsnmp and ntpd.  While I was just reading a file with 
less the system stopped responding.   I thought it was the network 
interfaces but I was able to ping the interface. 
Once I plugged a monitor into the system I saw this (roughly):


AAC0: COMMAND  TIMEOUT AFTER X number of seconds

Not good :)

Reset of the system resolved the issue and it booted fine.Since 
the controller stopped responding nothing was recorded to my logs.


Now I have to figure out how to prevent that from happening again.

Basic run down on the system and some history...

P4 3.2Ghz
Asus P5MT-S MB
2 x 1GB DDR2 667 memory
Adaptec 2130SLP Raid Controller + battery backup module
2 Segate Ultra320 73GB 15k RPM (mirrored)

I have run this same system hardware testing 6.2-BETA3, RC-1 and RC-2 
without this issue.I was using the driver released by Adaptec 
while testing the pre-release installs 
(http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd6_drv_b11518_tgz.htm).   
You could say I am fairly confidient in the hardware itself.   I have 
put this system through a lot of testing since BETA3.


The 6.2 release kernel has not been customized all that much, I just 
pulled out all the drivers I would never use.To be safe I kept 
just about all scsi devices/card models still in as I continued my 
testing of 6.2 release. 
Right now I am going to try taking out aac and aacp then try the 
driver I used in my previous tests.However, since I have run a 
week without this issue it will be hard/impossible tell if this did 
anything to resolve it...I almost want a crash on the old driver :)


So I need some advice...  How best do I debug this issue?

Thanks in advance for any direction you guys can offer me.

Cheers,

Jeff




It appears the driver I was using in my pre-release testing is newer 
then the release driver.


Stock driver in 6.2r dmesg:

aac0:  mem 
0xfc60-0xfc7f,0xfc5ff000-0xfc5f irq 24 at device 1.0 on pci2

aac0: New comm. interface enabled
aac0: Adaptec Raid Controller 2.0.0-1
aacp0:  on aac0

Currently using:

aacu0:  mem 
0xfc60-0xfc7f,0xfc5ff000-0xfc5f irq 24 at device 1.0 on pci2

aacu0: New comm. interface enabled
aacu0: Adaptec Raid Controller 2.0.7-1
aacpu0:  on aacu0

Going to continue testing with the newer driver.

Cheers,

Jeff




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.2 Release - Adaptec 2130SLP driver?? issue - aac driver

[LI Xin]

Jeff Royle wrote:
> Jeff Royle wrote:
>> I could use some advice on this issue I have had with my raid controller.
>> I am not really running much on the system yet, postfix, Pf + pflogd,
>> rlogind, ssh, bsnmp and ntpd.  While I was just reading a file with
>> less the system stopped responding.   I thought it was the network
>> interfaces but I was able to ping the interface. Once I plugged a
>> monitor into the system I saw this (roughly):
>>
>> AAC0: COMMAND  TIMEOUT AFTER X number of seconds
>>
>> Not good :)
>>
>> Reset of the system resolved the issue and it booted fine.Since
>> the controller stopped responding nothing was recorded to my logs.
>>
>> Now I have to figure out how to prevent that from happening again.
>>
>> Basic run down on the system and some history...
>>
>> P4 3.2Ghz
>> Asus P5MT-S MB
>> 2 x 1GB DDR2 667 memory
>> Adaptec 2130SLP Raid Controller + battery backup module
>> 2 Segate Ultra320 73GB 15k RPM (mirrored)
>>
>> I have run this same system hardware testing 6.2-BETA3, RC-1 and RC-2
>> without this issue.I was using the driver released by Adaptec
>> while testing the pre-release installs
>> (http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd6_drv_b11518_tgz.htm).
>>   
>> You could say I am fairly confidient in the hardware itself.   I have
>> put this system through a lot of testing since BETA3.
>>
>> The 6.2 release kernel has not been customized all that much, I just
>> pulled out all the drivers I would never use.To be safe I kept
>> just about all scsi devices/card models still in as I continued my
>> testing of 6.2 release. Right now I am going to try taking out aac and
>> aacp then try the driver I used in my previous tests.However,
>> since I have run a week without this issue it will be hard/impossible
>> tell if this did anything to resolve it...I almost want a crash on the
>> old driver :)
>>
>> So I need some advice...  How best do I debug this issue?
>>
>> Thanks in advance for any direction you guys can offer me.
>>
>> Cheers,
>>
>> Jeff
>>
>>
> 
> It appears the driver I was using in my pre-release testing is newer
> then the release driver.
> 
> Stock driver in 6.2r dmesg:
> 
> aac0:  mem
> 0xfc60-0xfc7f,0xfc5ff000-0xfc5f irq 24 at device 1.0 on pci2
> aac0: New comm. interface enabled
> aac0: Adaptec Raid Controller 2.0.0-1
> aacp0:  on aac0
> 
> Currently using:
> 
> aacu0:  mem
> 0xfc60-0xfc7f,0xfc5ff000-0xfc5f irq 24 at device 1.0 on pci2
> aacu0: New comm. interface enabled
> aacu0: Adaptec Raid Controller 2.0.7-1
> aacpu0:  on aacu0
> 
> Going to continue testing with the newer driver.

I have some preliminary work on merging the Adaptec driver:

http://people.freebsd.org/~delphij/for_review/patch-aac-vendor-b11518

But one of the reviewers has advised me to request boarder testing,
especially against old cards and CLI tools, so I have hold the commit
for now.

Cheers,
-- 
Xin LI <[EMAIL PROTECTED]>  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature

Re: 6.2 Release - Adaptec 2130SLP driver?? issue - aac driver

[Jeff Royle]

LI Xin wrote:

Jeff Royle wrote:
  

Jeff Royle wrote:


I could use some advice on this issue I have had with my raid controller.
I am not really running much on the system yet, postfix, Pf + pflogd,
rlogind, ssh, bsnmp and ntpd.  While I was just reading a file with
less the system stopped responding.   I thought it was the network
interfaces but I was able to ping the interface. Once I plugged a
monitor into the system I saw this (roughly):

AAC0: COMMAND  TIMEOUT AFTER X number of seconds

Not good :)

Reset of the system resolved the issue and it booted fine.Since
the controller stopped responding nothing was recorded to my logs.

Now I have to figure out how to prevent that from happening again.

Basic run down on the system and some history...

P4 3.2Ghz
Asus P5MT-S MB
2 x 1GB DDR2 667 memory
Adaptec 2130SLP Raid Controller + battery backup module
2 Segate Ultra320 73GB 15k RPM (mirrored)

I have run this same system hardware testing 6.2-BETA3, RC-1 and RC-2
without this issue.I was using the driver released by Adaptec
while testing the pre-release installs
(http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd6_drv_b11518_tgz.htm).  
You could say I am fairly confidient in the hardware itself.   I have

put this system through a lot of testing since BETA3.

The 6.2 release kernel has not been customized all that much, I just
pulled out all the drivers I would never use.To be safe I kept
just about all scsi devices/card models still in as I continued my
testing of 6.2 release. Right now I am going to try taking out aac and
aacp then try the driver I used in my previous tests.However,
since I have run a week without this issue it will be hard/impossible
tell if this did anything to resolve it...I almost want a crash on the
old driver :)

So I need some advice...  How best do I debug this issue?

Thanks in advance for any direction you guys can offer me.

Cheers,

Jeff


  

It appears the driver I was using in my pre-release testing is newer
then the release driver.

Stock driver in 6.2r dmesg:

aac0:  mem
0xfc60-0xfc7f,0xfc5ff000-0xfc5f irq 24 at device 1.0 on pci2
aac0: New comm. interface enabled
aac0: Adaptec Raid Controller 2.0.0-1
aacp0:  on aac0

Currently using:

aacu0:  mem
0xfc60-0xfc7f,0xfc5ff000-0xfc5f irq 24 at device 1.0 on pci2
aacu0: New comm. interface enabled
aacu0: Adaptec Raid Controller 2.0.7-1
aacpu0:  on aacu0

Going to continue testing with the newer driver.



I have some preliminary work on merging the Adaptec driver:

http://people.freebsd.org/~delphij/for_review/patch-aac-vendor-b11518

But one of the reviewers has advised me to request boarder testing,
especially against old cards and CLI tools, so I have hold the commit
for now.

Cheers,
  
I will patch my system and put it through some tests this weekend for you. 

As far as CLI tools are concerned any in particular I should be testing 
the patch with?  The only CLI tool I know of is the aacli1.0 from the 
ports tree which definately does not work with the 2130S :)


Cheers,

Jeff

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

MFC Request: kern/100958?

[Larry Rosenman]

Greetings,
Can we get kern/100958 MFC'd?  It's been in -CURRENT since September,
and fixes a problem for me with my laptop getting the AGPGART device
attached.

Thanks!

-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.2 Release - Adaptec 2130SLP driver?? issue - aac driver

[Vivek Khera]

On Jan 19, 2007, at 11:52 AM, LI Xin wrote:


I have some preliminary work on merging the Adaptec driver:

http://people.freebsd.org/~delphij/for_review/patch-aac-vendor-b11518

But one of the reviewers has advised me to request boarder testing,
especially against old cards and CLI tools, so I have hold the commit
for now.



My newer 2230SLP cards do not work with any extant command line tools  
for freebsd under amd64.  The older cards did.  I've tested FreeBSD  
6.0 and 6.1.  6.2 is on the agenda to test soon.


I shall have a look at your merged driver.  It won't be a regression  
for me if the CLI tools stop working :-(

Re: gmirror disks vs partitions

[Vivek Khera]

On Jan 19, 2007, at 12:42 AM, Vulpes Velox wrote:



When ZFS comes available, I plan to actually run it across multiple
mirrors. It has built in JBOD, but it does not do mirroring. It just
does stripping.


I think you misunderstand ZFS.  It is robust against multiple disk  
failures.  It doesn't do full disk mirroring, but does place multiple  
copies of data on multiple drives.

Re: Failover-HA-Setup

[Ulrich Spoerlein]

Richard wrote:
> > There is no need to make any changes to the script. Put whatever other
> >  options you want for mysql in rc.conf, and set the _enable variable
> > to no. Then you can run /usr/local/etc/rc.d/mysql-server onestart and
> > it will start normally just one time.
> 
> Yes, and mysql will be started at bootup time on both nodes, wouldn't
> it? So one node would fail miserably since the lack of mounted
> diskspace...

No, he wrote to set mysql_enable=NO, ie, the usual startup procedure
will NOT start it.

This doesn't work with heartbeat, however. heartbeat always calls the
resource scripts with either 'start' or 'stop', you can't make it pass
'onestart'.

Only two options remain: modify existing mysql-server script (bad idea,
will be overwritten on update) or go through a proxy script which
"transforms" start|stop -> onestart|onestop

You could also alter the environment of heartbeat (it's really just a
bunch of poorly written shell scripts) and set mysql_enable=YES there,
but that'd be just as fragile as rewriting the existing mysql-server
script.

> But the "nostart"-solution sounds like working...

Till you update the port and forget about your local modification ...

Ulrich Spoerlein
-- 
A: Yes.
>Q: Are you sure?
> >A: Because it reverses the logical flow of conversation.
> >>Q: Why is top posting frowned upon?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: gmirror disks vs partitions

[Tom Samplonius]

- Vulpes Velox <[EMAIL PROTECTED]> wrote:
> On Thu, 18 Jan 2007 10:15:56 +0900
> "Adrian Chadd" <[EMAIL PROTECTED]> wrote:
> 
> > On 17/01/07, Andrew Pantyukhin <[EMAIL PROTECTED]> wrote:
> > 
> > > [...after reading the slashdotter's piece of wisdom...]
> > >
> > > Yes, but that's the kind of functionality I have always
> > > expected to be present in software raid solutions. I
> > > hope I'll live to see this implemented in geom.
> > 
> > That made my eyes bleed.
> > 
> > Bring on ZFS and its method of managing JBODs.
> 
> I second that. I have been way less than impressed with software raid
> and LVM on linux.
...

  But LVM by itself is a good volume manager.  The block level snapshot ability 
is especially good.  LVM can actually notify dependent filesystems so that they 
flush all data, when the block level snapshot is created.  ext3 does not 
support filesystem based snapshots (like ufs2 does), but LVM snapshots are 
better than most filesystem snapshots.

  ZFS is clearly better than LVM+ext3, and is really the only option for really 
big filesystems right now.  ufs2 doesn't support journaling, and background 
fsck isn't a complete replacement for journalling.  ext3 is stable but doesn't 
really scale well, or have leading performance, and doesn't really work on 
FreeBSD anyways.  XFS is virtually unsupported, as SGI laid off all their 
filesystem developers when they went into chapter 11, and ReiserFS, besides 
having some dodgy reliability issues, the head of development is currently in 
jail for suspicion of murder.  So besides, being the best, ZFS is nearly the 
only choice for really big filesystems.

Tom
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: freebsd-update from 6.1 RELEASE to 6.2 RELEASE: directory creation caused failure.

[Colin Percival]

Brian King wrote:
> I'm writing this email from a freebsd 6.2 system, but it was a rocky
> upgrade for me.
> 
> I followed the process outlined at
> http://www.daemonology.net/blog/2006-11-26-freebsd-6.1-to-6.2-binary-upgrade.html
> 
> to upgrade my GENERIC i386 kernel and userland.
> 
> I had changed some configuration files, and when notified about it, i
> created a directory /usr/upgrade/newfiles and downloaded the
> appropriate copies of these files from the cvs into this directory.

Oops.

> # sh freebsd-update.sh -f freebsd-update.conf -d /usr/upgrade install
> Installing updates...freebsd-update.sh: cannot create newfiles: Is a
> directory
> rm: newfiles: is a directory

Yeah, you're not supposed to do that.  In fact, it never occurred to me
that someone would do that, largely because the FreeBSD Update working
directory (/usr/upgrade in this case) is normally /var/db/freebsd-update.
But since people upgrading from FreeBSD 6.1 don't have FreeBSD Update
installed as part of the base system (and thus don't have the "normal"
working directory) I added the flag to tell FreeBSD Update to use a
different directory instead.

> Suggestion for the developer: either permit directory creation in
> /usr/upgrade, or document that it's a no-no.

It will be documented. :-)

Thanks,
Colin Percival



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: MFC rstp

[Andrew Thompson]

On Thu, Jan 18, 2007 at 08:24:14AM +, Bjoern A. Zeeb wrote:
> On Thu, 18 Jan 2007, Andrew Thompson wrote:
> 
> Hi,
> 
> >I have a patch here to MFC the rstp code to RELENG_6. It should be all
> >fine and dandy as for API but will cause the default spanning tree
> >version to change from stp to rstp.
> >
> >Is it ok to change the protocol version for the STABLE users (rstp is
> >backwards compatable with stp) or should it still default to stp and
> >require the OP to enable rstp.
> >
> >Any opinions?
> 
> I think you should leave stp as default and have the user configure rstp
> if (s)he thinks (s)he needs it.
 
Yes, I think thats the safest. It will just need a bit more info in the
man page so people know it exists.


Andrew
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Read_dma timeout - FreeBSD 6-1 - Solved

[Ikare]

Hi,

Thanks for your answer ..
As Clayton suggested, I've bought a new power supply

And now, my 2 maxtor work fine !!

Thanks very much for your help, specially to Clayton Milos !

.. and now, I definitively hate hardware considerations !!

C ya
--
Ivan Kurzweg
Ile de la réunion, Océan Indien
Web : http://www.kurzweg.info


Les concepts sont comme une grille transparente à travers laquelle nous 
voyons l'univers, et qui nous donnent parfois l'illusion que cette 
grille est réellement l'univers. [Herbert & Anderson - La guerre des 
Machines]


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Lenovo X60 em workaround

[Bill Paul]

> Since this was just seen, and the patch below validated as working I wanted
> to send general email to capture this:
> 
> The Lenovo X60 can have issues with long ping times, this is a KNOWN
> hardware problem, and Intel is working with IBM/Lenovo, a final 'fix' has
> not been decided on yet. Nevertheless, the patch below will work, but
> I do not want to check it in as its still temporary.
>
> Address questions to me,

Okay, I have a question. Could you elaborate on just what the problem is?
(I mean, since it's KNOWN and all...) I'm just having a hard time figuring
out what problem could possibly be fixed by setting the RX interrupt
delay timer to a non-zero value (especially since elsewhere in the em(4)
source it says that doing so is a Bad Thing (tm)).

-Bill

> Jack
> 
> PS This is based on 6.2, but is needed for CURRENT as well.
> 
> 
> --- if_em.dist.cWed Jan 17 17:59:46 2007
> +++ if_em.c Wed Jan 17 18:03:13 2007
> @@ -3348,6 +3348,10 @@
> E1000_WRITE_REG(&adapter->hw, RXCSUM, reg_rxcsum);
> }
> 
> +   /* TEMPORARY WORKAROUND for X60 */
> +   if (adapter->hw.mac_type == em_82573)
> +   E1000_WRITE_REG(&adapter->hw, RDTR, 32);
> +
> /* Enable Receives */
> E1000_WRITE_REG(&adapter->hw, RCTL, reg_rctl);
> /*
> 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.2 Release - Adaptec 2130SLP driver?? issue - aac driver

[LI Xin]

Vivek Khera wrote:
> 
> On Jan 19, 2007, at 11:52 AM, LI Xin wrote:
> 
>> I have some preliminary work on merging the Adaptec driver:
>>
>> http://people.freebsd.org/~delphij/for_review/patch-aac-vendor-b11518
>>
>> But one of the reviewers has advised me to request boarder testing,
>> especially against old cards and CLI tools, so I have hold the commit
>> for now.
>>
> 
> My newer 2230SLP cards do not work with any extant command line tools
> for freebsd under amd64.  The older cards did.  I've tested FreeBSD 6.0
> and 6.1.  6.2 is on the agenda to test soon.

Do you mean Linux CLI tools on FreeBSD?  I think I have missed my
src/sys/dev/aac/aac_linux.c,v 1.4 change with re@ so I think there might
be no change.  Just MFC'ed that to RELENG_6.

> I shall have a look at your merged driver.  It won't be a regression for
> me if the CLI tools stop working :-(

Thanks!

Cheers,
-- 
Xin LI <[EMAIL PROTECTED]>  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature