Quoting Greg Lehey <[EMAIL PROTECTED]>:
> > I've submitted kern/22021 which was left untouched, it has all the
> needed
> > details.
>
> You don't mention that you resubmitted this PR as 22103. Despite my
> requests,
my fault, I meant 22103 indeed, and not 22021 which was closed.
> 1. You insisted on including the config file and dmesg, which
> just bloat the PR and make it more difficult to read.
yes I did. sed(1) is your friend.
> 2. The backtrace still does not include Vinum symbols, making it
> pretty useless.
To the very least it's not true.
Please check again http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22103
During symbol reading, inner block (0xc1505000-0xc150500a) not inside outer
block (0xc150bc0c-0xc150c3c2).
During symbol reading, block at 0xc15050d4 out of order.
#5 0xc150fc67 in complete_rqe () at
/usr/src/sys/modules/vinum/../../dev/vinum/vinuminterrupt.c:199
#6 0xc0178d6b in biodone (bp=0xc16e6420) at ../../kern/vfs_bio.c:2637
as you see, frame #5 is from vinum module, and symbols are included.
> 3. It includes (without comment) a mail exchange with Andy Newman,
> which have been twice mutilated, once before I received the
> message, once after.
This is completely irrelevant.
> After fighting my way through this PR, I don't have any additional
> information.
You fighted your way too fast.
> Dealing with this kind of PR is an absolute pain. It's bloated,
> illegible, full of irrelevant information and lacking the information
> I need. It is, however, one of the few cases I've seen of a
..or any other reason that prevents you from working on it.
I haven't heard from you since the last time I updated te PR with the kdb
session which had symbols.
> particular buffer header corruption which occurs only in RAID-5, and I
> would like to fix it. If you want to help, instead of sending "me
> too" messages about what is obviously a completely different problem,
> help me find the problem you're having.
I'm terribly sorry, but I won't be able to assist you any further. The machine
in question uses vinum raid-1 now, and is going to receive Mylex very soon.
vinum RAID-5 is dangerous, shouldn't be used in sensitive environments, and it
cost me much health.
--Roman Shterenzon, UNIX System Administrator and Consultant
[ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message