I was experimenting with iscsi earlier, using both a flat file as the
backing store and also a zvol. I noticed that the zvol was giving me
dreadful performance - reading at about 20 meg/second and writing at
about 12. the fklat file gives about 45 meg/second both ways.
i thouht it was to do wuth t
> On 7.x (where ZFS is really quite broken for server use - don't waste
> too much time on it) the ZVOL code did an "fsync" after every single
> block write. Its a testament to your fast disks that you got as high as
> 12mb/s. I don't know why your read speed was so bad, but you should try
>
I have a number of HP 1U servers, all of which were running 7.0
perfectly happily. I have been testing 7.1 in it's various incarnations
for the last couple of months on our test server and it has performed
perfectly.
So the last two days I have been round upgrading all our servers, knowing
that I
> Are you using the same disk controller as Peter ? Do both of you run
> with quotas on the file system ? By lockup, do you mean it doesnt
> respond to the network either or just anything that needs disk IO ?
I dont think he can be using yhe same controller, as mine is an
embedded HPO unit. th
> Since ULE is now default in 7.1 and not in 7.0, perhaps you can try
> that?
Actually you might be on to something there one of the main differences
between out test GL360 and the live ones is that the test one has less
cores in it, and is under less load. So multiprocessing problems may we
> Alsp, should it actually fail like this? I have ZFS and I plan to do
> all NFS exports from ZFS, so /etc/exports would never be used.
ZFS writes its own exports file to '/etc/zfs/exports' - as far as I can
tell this is pretty much all that happens when you mark a filesystem
as NFS shared under
> FWIW, the other guy I know who is having this problem had already
> switched to using ULE under 7.0-release, and did not have any
> problems with it. So *his* problem was probably not related to
> SCHED_ULE, unless something has recently changed there.
Well, one of my machines just locked up ag
> I noticed a similar problem testing 7.1-RC1, It seemed to be a deep
> deadlock, as it was triggered by lighttpd doing kern_sendfile, and
> never returning. The side effects (being unable to create processes,
> etc) is similar.
Interesting - did you get any responses from anyone else regarding
th
> My kernconf is below, try building the kernel, and send an email
> containing the backtrace from any process that has blocked (in my
Well, I havent managed to get a backtrace, but immediately upon
booting the system halts with the following:
http://www.twisted.org.uk/~pete/71_lor1.jpg
Here is a better set of images. This machine was compiled
with the following config file:
include GENERIC
ident DEBUG
options KDB
options DDB
options SW_WATCHDOG
options DEBUG_VFS_LOCKS
options MUTEX_DEBUG
options WITNESS
options
> Not Found
sorry, see the subsequent email, there are more links there to working PNG's
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubsc
> You don't want WITNESS_KDB, but WITNESS_SKIPSPIN would probably be
> sensible to include.
OK, I will take out the WITNESS_KDB. I am reluctant to add in
WITNESS_SKIPSPIN though, as I understand it stops witnessing spin
locks, is that right ? As the only error message I have ever got out
of all fo
> I've performed five buildworlds decrementing -j from 16 to 6 and I
> can't lock up the server.
Mine never lock up doing buildworlds either. They only lock up when they are
sitting there more of less idle! The machines which have never locked up
are the webservers, which are fairly heavlt loaded.
> I'm not sure if you've done this already, but the normal suggestions apply:
> have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do
> any results / panics / etc result? Sometimes these debugging tools are able
> to convert hangs into panics, which gives us much more abil
> I'm not sure if you've done this already, but the normal suggestions apply:
> have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do
> any results / panics / etc result? Sometimes these debugging tools are able
> to convert hangs into panics, which gives us much more abil
> Just to followup on this: My friend did switch back to a 7.1 kernel with
> SCHED_4BSD, and he still ran into problems. The error messages weren't
Acually, I dont know if I posted it, but that was the same for me too.
The scheduler makes no difference, nor do CPU copile settings.
-pete.
__
> Lock order reversals are warnings of potential deadlock due to a lock cycle,
> but deadlocks may not actually result, either because it's a false positive
> (some locking construct that is deadlock free but involves lock cycles), or
> because a cycle didn't actually form. The message is sugge
> It was mentioned previous in this thread that CPUTYPE could be an
> issue. Did you change this if you customized your kernel?
Actually, I think thats been ruled out as a possible cause, along
with the scheduler. Certainly I have tried it both ways and
there is no difference, and I think i saw th
> Can you break into the debugger with Ctrl-Alt-Esc, or by sending a break
> over the serial line?
No, ctrl-alt-esc doesnt work, and there is no serial line on the machine (not
that I can access anyway)
-pete.
___
freebsd-stable@freebsd.org mailing list
> Silly question but do you have powerd enabled on that server? If so,
> does disabling it help? Also do you have any of these in /etc/rc.conf
> (i.e., they are not the same as the default values in
> /etc/defaults/rc.conf):
> performance_cx_lowest="HIGH"# Online CPU idle state
> performance_cp
> I can't (fortunately) make it lock up. I have a DL360 G5 which is
> unused atm. and can test on it if needed.
Would it be possible to install that under amd64 and hammer it with
DNS requests ? I have been trying to think what the difference might be
between my webservers and the machines which
> If you have BREAK_TO_DEBUGGER compiled into the kernel, then try pressing
> ctrl-alt-break on the console to see if you can drop into the debugger, or
> issue a serial break on a serial console.
Well, I added BREAK_TO_DEBUGGER to the kernel config I had which contained
all the other stuff (WIT
> effect on control flow, unlike, say, WITNESS, which significantly distorts
> timing. Is there any chance you picked up any of the recent fixes that went
> into RELENG_7 without noticing, and that perhaps one of those did it? With
I'm pretty certian of that - I hav just been changing kernel
> a) Only put the disk in a new machine at least a double core with 2GB
> of RAM. My guess is that could boot with a few problems on
> hardware what do you think?
That should work fine - I have moved discs between machines with no
problems.
> b) If is possible to "clone" the same installati
kernel: interrupt storm detected on "irq22:"; throttling interrupt
source
> Opening the case, reading the m/b:
>
> K9A2 Platinum MSI
I hadnt been paying much attention to this thread, but just to let you
know that I also saw the same thing on this machine which has an MSI 790F
Just an update on this - I tried the various kernels, but now the machine is
not locking up at all. As I havent actually chnaged anything then this does
not make me as happy as you might expect. I don;t know what to do now - I
daare not upgrade the machines to an OS that I know locks, but if I can
> Given the inconsistency of the symptoms, I wouldn't preclude something
> environmental: could it be that it was the bottom, or more likely, top box in
> a rack and that your air conditioning isn't quite as effective there when the
> outside temperature is above/below some threshold?
It's a po
> desirable. You might want to give the NMI a test run just to make sure it
> behaves as you think it should, though -- be aware that if DDB/KDB aren't
> compiled into the kernel, then an NMI will panic the box.
Unfortunately it does this...
http://toybox.twisted.org.uk/~pete/71_nmi1.png
That
> a software problem before hardware. Both drives are encrypted geli
> devices. I tried to reproduce the error with 1GB disk images (vs
This is probably a silly question, but are you sure that the drives
are not auto detaching ? I had big problems with a zfs mirror on top
of geli which turned ou
> trouble with onboard re(4) was resolved in -CURRENT and -STABLE, but
> storms are not bound to ethernet only. storm may appear on any device.
> if any device generates enough interrupts rate, storm will arrive.
Yes, I just got another storm, on my ATA controller this time. Ah
well, so much for
> If you are able to get into the debugger, the normal commands would be most
> helpful, especially if you can log the results:
It finally locked up, and ctrl-alt-esc got me into the debugger at
last! is there anything else you want me to get whilst it is
like that aside from:
>ps
>show
>ps
output from 'ps' is here: http://toybox.twisted.org.uk/~pete/71_lock_ps/
there are a lot of processes as this machine runes the same webservices
as the actual webservers, just that nobody connects to them.
>show lockedvnods
nothing - there are no locked vnodes
>show alllocks
th
> hi, please type:
> show lock 0xff0001254d20
> and then show thread 0xXXX where X is 'owner' of previous output.
http://toybox.twisted.org.uk/~pete/71_pdns_lock.png
That's in Power DNS - which is interesting because the one difference
between the boxes that lock and those which d
> trace 832
http://toybox.twisted.org.uk/~pete/71_trace_832_1.png
http://toybox.twisted.org.uk/~pete/71_trace_832_2.png
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
> I rather feared as much. Let's run down the path of "perhaps there's a
> problem with the new UDP locking code" for a bit and see where it takes us.
> Is it possible to run those boxes with WITNESS -- I believe that the fact that
> "show alllocks" is failing is because WITNESS isn't present.
> If you do INVARIANTS + WITNESS + WITNESS_SKIPSPIN, that should be good.
> WITNESS does a number of things, including tracking (and being judgemental
> about) lock order. One nice side effect of that tracking is that we keep
> track of a lot more lock state explicitly, so DDB's "show allocks",
Just confinuing to look at this with the help of Dimity, and the
output from 'bt' is here:
http://toybox.twisted.org.uk/~pete/71_bt.png
The top bit of that is from my 'show alllocks' the full version
of whih is here:
http://toybox.twisted.org.uk/~pete/71_show_alllocks.png
-pete.
___
> yes, do ps - threads in state L or LL and RUN are especially interesting,
> trace of pids 28, 27, and threads wich L on locked chan.
heres the output of alllocks,
http://toybox.twisted.org.uk/~pete/71_show_alllocks.png
here are the pages of PS:
http://toybox.twisted.org.uk/~pe
> Probably it is your case, try please.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=130652&cat=
OK, will give this a try, unless anyone else wants any traces from
this locked machine ? Is there a known way to tickle this bug
when I've rebooted, to make sure it's fixed ?
thanks,
-pete.
___
> Probably it is your case, try please.
> http://www.freebsd.org/cgi/query-pr.cgi?pr=130652&cat=
Well, I have been running this for a while now. I still get this:
http://toybox.twisted.org.uk/~pete/71_lor3.png
On the console, but so far the machine has not crashed. Obviously it's
only be
> http://www.freebsd.org/cgi/query-pr.cgi?pr=130652&cat=
Looks like I spoke too soon - It just locked up again I am afraid.
Sitting there now at the debug prompt. It does, however, look very
different this time: For example here is 'show alllocks':
http://toybox.twisted.org.uk/~pete/71_al
> There are significant changes in UDP locking between 7.0 and 7.1, so it could
> be that we're looking at a regression there. If you're able to reproduce this
> reliably, it might well be worth doing a little search-and-replace in
> udp_usrreq.c along the following lines:
>
>INP_RLOCK_ASSERT
> load. Kip Macy has corrected at least one (both?) problems in head, and
> plans to MFC the fixes in the near future. We'll follow up further once
> the fixes are merged, and if any further problems transpire.
Hi, just wondering if we are any closer to having the MFC for this yet, or
if there a
> Sure, it's possible, given sufficient toolchain knowledge, time, and
> skills, but it's not a sensible thing to do aside from experimentation
> and learning purposes.
Theres an intermediate method between upgrading in place and doing
a full re-install which si what I used when I did this.
1
> FYI, I'm currently awaiting testing results from Pete on the MFC of a number
> of routing table locking fixes, and once that's merged (hopefully tomorrow?)
> I'll start on the patches in the above PR. I've taken a crash-course in
> routing table locking in the last few days... :-)
Just to le
Sometime on sunday our main server paniced with the following error:
panic: solaris assert: sm->sm_space == space (0x5e45000 == 0x5e45600), file:
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/space_map.c,
line: 361
I did some goolging and found a couple of refereces
> better driver for this marvell chip. If someone gets to port it to
> FreeBSD, the card may be pretty decent choice for those who have PCI-X
> slot on-board.
I have PCI-X and just purchased an unbranded card based
on the SiL3124 chipset, as I was only using SATA 1 before.
I didn't expect much, bu
I observer that when I mount a UFS filesystem using the device
name then the entry vanishes from /dev/ufsid, and glabel list no longer
shows the device. Which begs the question, how do I find
out the ufsid of a mountde filesystem (e.g. '/' so that I can change it's
fstab entry for the next reboot?)
Thanks for the advice guys - dumpfs works fine, and I didnt even know
it existed until now which is king of embarassings given how old it is!
cheers,
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-st
> FYI, since upgrading to 8.0-PRERELEASE on Oct 30, there have been no
> interrupt storms.
I was about to email exactly the same thing today :) This bug is
not present on 8.0 as far as I can make out. Nice work.
-pete.
___
freebsd-stable@freebsd.org ma
> Usually the error you're seeing is indication that either the client or
> server changed from DSA to RSA, or vice-versa. I don't see anything in
> /etc/ssh/ssh_config or /etc/ssh/sshd_config between 7.2-STABLE and
> 8.0-STABLE which would indicate this changed.
There is, however, a not on /usr/
> This would indicate the OP was running a 7.2-STABLE system which was
> built prior to 2008/08/01 (with some variance; sometimes the commit
> times do not match the timestamp in src/UPDATING), or a system which had
> not had mergemaster run on it to populate the changes into /etc/ssh.
Well, I adm
Only just noticed this, but there seems to be a small, but annoying,
pieece of breakage in email under 8.0
try and send a simple piece of email, type a few lines, then
use '~h' to try and change the 'to' header (or any of them actually).
what you get is a set of blank headers, instead of the origi
I've been gradually testing 8.0 on several machines propr to deploying it
live, but I currently have a machine which appears to lock-up at 3am
every day. The symptoms are that the machine is still pingable, but doing
anything which requires access to the disc just freezes (so you cant login for
exa
> i'm trying to track down the same problem. The box in question has
> everything on UFS (mirrored ataraid) and a backup disk with ZFS on it
> attached to USB.
This is very interesting to know! It seems you have managed to get a lot
more information out of it than I have.
> As the box is remote w
> Same here!
I am wondering what happens if I disable the automatic run,
then wait until 3am and run by hand... possibly its something
to do with the data it is having to work on at 3am ?
> But the box has been running 8-STABLE since around end of August, and
> the first time it happened was abou
> Ehm... what happens if you just run daily by hand?
Nothingm ... that was the first thing I tried :(
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-un
Interesting... I just got another hard lock on the system, not at 3am
this time. The only other common factor in this is that the lockup
is always preceeded by a flood of failed ssh logins. I;m sure we've
all seen these - I get them on every BSD system I have - they look
like this:
Dec 22 17:37:10
Just to report that the machine didn't crash last night - which doesn't
make me happy as it makes me think maybe I am chasing the wrong thing!
I now have DDB and KDb in the kernel now, will get traces next
tme it keels over.
-pete.
___
freebsd-stable@fr
> When you say "lock up" and "can't login" (in your original mail) - are
> you sure this really is a lockup and not e.g. sshd dieing because of the
> attacks? E.g. can you ping the machine, can you leave something like
> "date >> /root/run.txt && vmstat 1 3 >> /root/run.txt" in crontab so you
>
> By the way, here is another little tool that can be used to
> watch changes in 8-stable conveniently:
>
> http://www.secnetix.de/olli/FreeBSD/svnews/?p=stable/8/sys
Have you seen Fresh BSD ? It does a very similary thing except
it's not just restricted to FreeBSD. For example to track RELENG_8..
am still trying to get the machine which ocks up to lock up
when I have DDb, KDB and WITNESS in the ernel. It's not locked yet
but I have got the following in dmesg...
lock order reversal:
1st 0xff8052321e50 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559
2nd 0xff000384a800 dirhash
> I think this is LOR #261 and therefore harmless.
> http://sources.zabbadoz.net/freebsd/lor.html
...and the second one is possibly 280 according to that page I guess ? (not
harmless though, just unknown in that instance).
Thanks for the link BTW, I didn't know about that page.
-pete.
__
TIOCSTI appears to be broken - the code attached at the bottom
works fine in 7.x but fails in 8.0. What the code is attempting to
do is to print a prompt for text input, along with an initial
value for that text which can be edited by the user. I am assuming
this is a bug, and not incorrect usage o
> http://80386.nl/pub/tty.diff
>
> Wrote it some time ago, but nobody wanted to test it for me, which made
> me asume nobody cared. ;-)
Ah, well I care a lot and am testing it now, thankyou :-) Will report back
later this evening...
-pete.
___
fre
> http://80386.nl/pub/tty.diff
Just tested the patch - works beautifully! Please commit and MFC if
you can :-)
cheers,
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, sen
> GELI+ZFS and Debian Linux with MDRAID and cryptofs. Has anyone here
> made any benchmarks regarding how much of a performance hit is caused
> by using 2 geli devices as vdevs for a ZFS mirror pool in FreeBSD (a
I havent done it directly on the same boxes, but I have two systems
with idenitical d
> How fast is the CPU in the system showing no overhead? Having no
> noticable overhead whatsoever sounds extremely unlikely unless you are
> actually using it on something like a very modern dualcore or better.
It's a very modern dual core :-) Phenom 550 - the other machine is an old
Opteron 252.
> In order to allow a MFC, a similar approach, being a bit sub-optimal,
> but not breaking ABI, has been prepared for STABLE_8:
> http://www.freebsd.org/~attilio/lockmgr_fix8.diff
>
> I'm seeking for testers here.
> Any report would be very much appreciated.
I'll give this a shot - I ahve a machin
> http://www.freebsd.org/~attilio/lockmgr_fix8.diff
>
> I'm seeking for testers here.
> Any report would be very much appreciated.
I tested the patch on my machine which locks up, and I am afraid that it
still locks, even with the patch applied. The last things on the console
before the lock are.
> Also enable INVARIANTS.
Including INVARIANTS stops my kernel from building. It
has been this way since 8.0 (this is why I only
had WITNESS compiled in). It fails with many many
errors like this:
/usr/src/sys/vm/vm_map.c:575: undefined reference to `_mtx_assert'
My kernel config file looks like
> INVARIANTS requires INVARIANT_SUPPORT [sic] in the kernel config (see
> comments in GENERIC).
Ah, right, that would explain it. Thanks!
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To uns
Well, the machine has been running the WITNESS + INVARIANTS kernel
for 20 hours now without locking up.This looks like what I
saw before - compiling in WITNESS stops it locking up -(
Is there any use in my runing a kernel with just INVARIANTS to see if
that will lcok ? I know it locks with KDN and
> One may never know, try without WITNESS but still the same setup.
Well, I have been running like this for three days with no lockups
dissapointingly. I just saw that you commited the lock patches, so
am going to update to the latest STABLE and go back to GENERIC to see if
that still locks up (as
> May you post your kernel config?
sure...
include GENERIC
ident DEBUG
options KDB
options DDB
options WITNESS
options INVARIANT_SUPPORT
options INVARIANTS
That one doesnt lockup, or
> Ok then, remove the debugging (WITNESS, INVARIANT*), leave in place
> KDB and DDB, add GDB and try at least to get a coredump when it
> deadlocks.
OK, will do. Am building a KDB/GDB/DDB kenel now.
-pete.
___
freebsd-stable@freebsd.org mailing list
htt
> I like to use pci-x with aoc-sat2-mv8 cards or pci-e cardsthat way you
> get a lot more bandwidth..
I would goalong with that - I have precisely the same controller, with
a pair of eSATA drives, running ZFS mirrored. But I get a nice 100
meg/second out of them if I try. My controller is, how
This patch fixes a problem of mail missing addresses when replying
to emails generated by some Microsoft systems, which do not insert a
space after the comma in lists of addresses. Was filed as PR bin/131861
If anyone who still uses /usr/bin/mail as their primarly email client
could test it then I
> For what it's worth: note that Outlook, by default, uses semi-colon as
> its delimiter between addresses in To/Cc/Bcc fields. The SMTP portion
> of the Exchange interface might turn these into commas though, but I'm
> not 100% certain (I'd have to manually check -- let me know if you want
> me t
> I run a similar network setup at home, and am unable to replicate your
> experience regardless which host is being copied to/from. Perhaps you have
> a more specific issue eg nic driver ?
I missed the start of this thread, but I have also seen scp stalling
on 8-STABLE, except in my case it as i
Having just updated a couple of machines to the latest stable, I am
seeing warnings like this out of rsync when writing to a ZFS filesystem
on the machine:
default_perms_for_dir: sys_acl_get_file(., ACL_TYPE_DEFAULT): Invalid argument,
falling back on umask
ANy ideas whats going on here ?
chee
> Can others with remote systems comment about what they do in this step?
installkernel, reboot, installworld, mergemaster, reboot.
*But* - for remote systems I never make huge leaps. I would
certainly never upgrade across a major version like you are doing.
Fpr those upgrades (which are only onc
> soulution similar to drbd+heartbeat on Linux? Geom_gate looks nice, but
> I have no idea if it has been used in a production enviroment.
I use it for production - it works nicely, but you wont get automatic
failover that way.
-pete.
___
freebsd-stab
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/131861
I've been using the patch now for a couple of months with no
observable problems. It is very small, and does fix a real
annoyance with using /usr/bin/mail as your primary mail
reader. I realise this is probably a very small number of
people, b
> Sorry Pete, but the patch still seems incomplete. You merely catch the
> case when a comma is followed by space or quotation marks, but the email
> header might look like this:
> To: f...@domain.com,b...@otherdomain.com
I think the original code handles cases like that fine, my patch merely
look
> Well, the following header didn't work:
> Cc: ,
Ah, indeed - with the angle brackets on it does not work,
either with my patch or in the original.
> Postfix will re-write this as part of sanitization, so I had to revert
> to creating mbox files by hand. Anyway, could you please test the
> follo
I have a machine used as a firewall which boots from a pair of
drives mirrored using gmirror. This has been in situ for a long
time, and was upgraded to 8.0 a while ago. Just before the weekend
I upgraded the kernel to the latest STABLE to get the new em code.
After doing this I observed that at s
Just following up my own email, but soemthing is definitely up
with gmirror, as it has got to 100% complete on the
resync, but stays in degraded mode... i.e.
$ gmirror status
NameStatus Components
mirror/pair0 DEGRADED da0s1
da1s1 (100%)
this, obviously, sh
> RELENG_8 csup'd with date=2010.02.14.00.00 works perfectly for days.
>
> RELENG_8 csup'd with date=2010.02.15.00.00 dead-locks the disk I/O
> subsystem. Network still operational but anything needing disk hangs.
> Power-cycle required.
An aditional point (and thanks to Andy for doing all the wor
> Well, the following header didn't work:
> Cc: ,
>
> Postfix will re-write this as part of sanitization, so I had to revert
> to creating mbox files by hand. Anyway, could you please test the
> following patch with a wider variety of mails?
Sorry for not getting around to this util now - am testi
> I have some 29160N locally and I'll try to reproduce this.
I would suggest you try gmirror across two drives - that is how
both myself and the original poster first noticed the issue.
cheers,
-pete.
___
freebsd-stable@freebsd.org mailing list
http:/
> 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" error same time. The rest of system works
> fine. If
> Seems like I've found the reason. Attached patch fixes problem for me.
Thanks, am trying this now
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebs
> Seems like I've found the reason. Attached patch fixes problem for me.
Inetersting - one of my machines has ginished a gmirror resync. The first
time I tried this it did lock up, but with media rea errors (which may be
genuine on these old drives). But this tiime it has finished, and without
the
...and my other test amchine just completed a gmirror rebuild as well, with no
problems. So intially it does look very much like it
is fixed. Thanks Alexander! IIf I have any mmore problems I will
let you know
-pete.
___
freebsd-stable@freebsd.org mailin
> I'm glad to hear it. But gmirror rebuild itself may be not enough for
> test. It uses very few requests same time. You should manage "Queue
> full" state, so you should make at least 150 concurrent write requests
> to the mirror running same time.
Am going to hammer it for a bit with a number of
> Postfix will re-write this as part of sanitization, so I had to revert
> to creating mbox files by hand. Anyway, could you please test the
> following patch with a wider variety of mails?
I've been testing your patch for a few weeks now as my main email
client, and I havent encountered any prob
> Do you feel strongly about merging the fix to 8 or 7 or both?
Not really - it;s such a small change that it would seem a shame
not to commit it to earlier releases, but then I used 7 thoughout
it;s lifetime with the bug only being a minor annoyance.
-pete.
__
> 1. Go to your kernel configuration directory (e.g. /sys/i386/conf)
> 2. run "config CONFNAME" (e.g. config GENERIC)
> 3. chdir to the printed directory and follow the instructions about make
> cleandepend;make depend;make; make install
>
> (if you need to re-make the kernel with changes to existi
> If you are using RSDT, then RsdtPhysicalAddress is what you care about
> rather than XsdtPhysicalAddress.
O.K., I have this now - RsdtPhysicalAddress is 0x7fec7f40 on
return from madt_map_table
-pete.
___
freebsd-stable@freebsd.org mailing list
http:/
101 - 200 of 789 matches
Mail list logo
