Re: Problem with dump stalling

2008-10-09 Thread Christoph Schug
On Wed, Oct 08, 2008, David Peall wrote:

 I'm running 7.0-RELEASE-p4 and trying to backup to an external USB
 drive.
 
 I'm using the following command
 
 dump -a0Lf /backup/diskimages/root /dev/mfid0s1a
[...]
 But it just stops at a random percentage,  the system continues to run
 and the processes are killable?

This is a know bug which mainly affects multi-core CPU systems. It is
fixed in RELENG_7, see also PR bin/121684 [1] where the relevant patch
is referenced.

[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/121684

-cs

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


Re: if_re losinbg ability to communicate, even with latest patches

2008-02-29 Thread Christoph Schug
On Thu, Feb 28, 2008, Pete French wrote:

 yesterday I had my first experience of an if_re interface simply stopping
 responding. I ma running 7.0-RELEASE on the machine, but with
 the lates files taken from here:
 
   http://people.freebsd.org/~yongari/re/7.0R/if_re.c
   http://people.freebsd.org/~yongari/re/7.0R/if_rlreg.h

Just wondering whether you disabled any hardware offloadings. I'm
running a RELENG_7/amd64 as of 2008-Feb-22 with the re(4) driver from
the URLs above. As a precaution, I disabled all kinds of hardware
offloadings.

| # grep ^ifconfig_re.= /etc/rc.conf 
| ifconfig_re0=inet x.x.x.x netmask 255.255.255.224 media auto -rxcsum -txcsum 
-tso -lro -vlanhwtag

| # ifconfig re0
| re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
| options=88VLAN_MTU,VLAN_HWCSUM
| ether 00:1d:92:x:x:x
| inet6 fe80::21d:92ff:fexx:%re0 prefixlen 64 scopeid 0x1 
| inet x.x.x.x netmask 0xffe0 broadcast 78.46.41.63
| inet x.x.x.x netmask 0xfff8 broadcast 78.47.124.7
| inet x.x.x.x netmask 0xfff8 broadcast 78.47.124.7
| inet x.x.x.x netmask 0xfff8 broadcast 78.47.124.7
| inet x.x.x.x netmask 0xfff8 broadcast 78.47.124.7
| inet x.x.x.x netmask 0xfff8 broadcast 78.47.124.7
| inet x.x.x.x netmask 0xfff8 broadcast 78.47.124.7
| media: Ethernet autoselect (100baseTX full-duplex)
| status: active

| # pciconf -lv
[...]
| [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x368c1462 chip=0x816810ec 
rev=0x01 hdr=0x00
| vendor = 'Realtek Semiconductor'
| device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
| class  = network
| subclass   = ethernet
[...]

After almost one week uptime, the machine is still stable. Before it
started lossing packets after very few hours uptime. I'm wondering if
this is related to the options I disabled, so I'm interested in your
settings.

-cs

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


Re: if_re losinbg ability to communicate, even with latest patches

2008-02-29 Thread Christoph Schug
On Fri, Feb 29, 2008, Pete French wrote:

 ...and it is stable for you ? I will defintely go and turn these off in
 that case! Also, I note your are runnign RELENG_7 and not RELENG_7_0 - any
 idea what changes there might have been in that ?

Up to I haven't encountered a real show stopper beside the re(4) issues
which seem to be fixed at least for my configuration. Nevertheless all
those minor glitches which come with a new major release will hopefully
be fixed sooner in RELENG_7 than RELENG_7_0. That's the reasone why I
don't track RELENG_7_0, but up to now there should be much difference
anyway. I think I will track RELENG_7 til RELENG_7_1 will be branched.

 This is extermely interesting! I have applied those settings by hand just
 now, and will see if it helps. Not quite sure how to get them
 into rc.conf yet - I am using ipv4_addrs_re0=195.144.8.6/28 195.144.8.4/28
 and am not sure how an ifconfig_re0 line might interact with it as yet. 
 I dont want to edit rc.conf in case it reboots...

Should be oka, to put your primary IP address and the interface options
in an 'ifconfig_re0' line and to add additional IPs to the interface
using a 'ipv4_addrs_re0' line. At least I've tested it on a VMware and
it seems to work just fine.

-cs

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


Re: vnode_pager_putpages errors on 6.2

2007-05-31 Thread Christoph Schug
On Tue, May 29, 2007, steve wrote:

 Howdy!
 
   I had this issue on 4.x, which is basically, I have
 machines that do cgi stuff for customers, and there is a local
 md device that is used as a tmp. When it fills the machine 
 logs errors
 
 vnode_pager_putpages I/O error 28..
[...]

Just for the record: there's still an open discussion on the same issue
in PR kern/67919 [1]. Is this issue resolved completely with this patch?

[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/67919

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


Re: Running large DB's on FreeBSD

2006-10-24 Thread Christoph Schug
On Mon, Oct 23, 2006, Mike Jakubik wrote:

I am in the process of implementing a fairly large mysql server for 
 an even larger company, and naturally i want to use FreeBSD. The 
 hardware will be an HP DL385, 2 x dual-core Opterons, 16GB RAM,  7 x 15k 
 rpm disks in a RAID5 setup. I'm not exactly informed as to the specific 
 workload yet, however i know the database will have several million rows 
 and be larger than 10GB.

Again, don't use RAID 5 for databases. Distribute your data over a
bunch of table spaces on RAID 1/10 volumes. Furthermore ensure that
your external storge can cope with high concurrent disk I/O. Speaking
of HP we had very poor results with the cheaper storage boxes like
MSA1000/MSA1500. It seems that their I/O processors can saturated
very easily under concurrent I/O. If you stick to HP, choose an EVA
for performance reasons. Later you can easily improve speed by adding
additional disks.

If you have big tables you may want to use one of the newer PostgreSQL
features, Partitioning and Constraint Exclusion. See [1] for details.

Disabling setproctitle() gains additional performance points, too.

[1] 
http://www.postgresql.org/docs/8.1/static/ddl-partitioning.html#DDL-PARTITIONING-CONSTRAINT-EXCLUSION

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


Re: FreeBSD 6.1-STABLE: Unexplained power off

2006-08-15 Thread Christoph Schug
On Tue, Aug 15, 2006, Android Andrew [:] wrote:

 At first I thought that problem could be in CPU, power supply, mobo 
 chips overheating, but temperature sensors reported everything is OK. To 
 be on the safe side I installed additional radiators and coolers. But it 
 doesn't solve the problem.
 I've noticed that system is unstable under high disk io load during 
 compilation.

How have you checked your power supply? Is it capable enough to run all
your components under high load?

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


Re: Question about current rc scripts

2006-06-22 Thread Christoph Schug
On Tue, Jun 20, 2006, M.Hirsch wrote:

 As stated in my initial post, I used BEFORE: rcconf up to and 
 including 6.0.
 
 So what is an appropriate BEFORE entry for 6-STABLE?

This might be a crude hack but _should_ (untested) work. What about
wrapping rcorder like this ...

/usr/local/sbin/rcorder.local
| #!/bin/sh
| echo '/very/first/rcscript'
| exec /sbin/rcorder $@

and inject it using an alias in rc.conf

rc.conf:
:
| alias rcorder='/usr/local/sbin/rcorder.local'
:

Since /very/first/rcscript will be called during system shutdown as
well, it might be reasonable to have a 'faststart' case statement in
place

| case $1 in
|faststart ) ... ;;
| esac

Hope this helps (and actually works)
-cs
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ciss0: ADAPTER HEARTBEAT FAILED? on a new bought HP dl360g3

2006-05-31 Thread Christoph Schug
On Mon, May 29, 2006, Dennis Berger wrote:

 ciss0: ADAPTER HEARTBEAT FAILED yes this are capital chars.
 I wonder if this can be a driver problem or if it definitly a hardware 
 failure.

We have had similar messages on a DL380 G3 in the past. They were gone
as we replaced the system board incl SmartArray controller.

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


Re: Messages from rc-scripts are not displayed at all

2006-05-18 Thread Christoph Schug
On Wed, May 17, 2006, Sergei Mozhaisky wrote:

 This does not help :( There is no output at all, commands
 aren't display too.

Maybe 'dmesg -a' will give you a hint what's going on.

-cs

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


Re: Gmirror'd SWAP: no dump?

2006-01-19 Thread Christoph Schug
On Thu, Jan 19, 2006, Larry Rosenman wrote:

 All the HOWTO's I've seen have the entire disk mirrored, including
  all the pieces.

See [1] how to setup a GEOM on a slice basis. You only have to skip swap
and mind the correct /etc/fstab entry. From my experience, it is best to
hardcode all providers using '-h' at all gmirror insert operations for
a slice based setup.

[1] http://people.freebsd.org/~rse/mirror/

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


Re: Gmirror'd SWAP: no dump?

2006-01-19 Thread Christoph Schug
On Thu, Jan 19, 2006, Larry Rosenman wrote:

 Would the lack of -h cause gmirror to hang at startup?  I'd see the
 Gmirror code come up, and then the machine would hang.

IIRC I had the problem that 'gmirror insert' without '-h' not always
inserted the slice specified by the entire block device (e.g. /dev/ad4s1
vs. /dev/ad4). Apparently there is some auto detection code and/or
gmirror cannot differ correctly, but that's just a guess. Specifing '-h'
fixed it in my case.

 In this kind of setup, I still saw the 'b' partition mirrored. (since I
 basically
 Only have da0s1/da1s1).

If I understand you correctly moving swap to a different slice should do
the job.

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