hi,
since tonight I get millions of error messages from the ISTGT under
8.2-STABLE
Nov 1 02:00:03 iscsihead-m istgt[5152]:
istgt_lu_disk.c:3960:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write()
failed
Nov 1 02:00:03 iscsihead-m istgt[5152]:
istgt_lu_disk.c:6051:istgt_lu_disk_execute:
Denny Schierz schreef:
hi,
since tonight I get millions of error messages from the ISTGT under
8.2-STABLE
Nov 1 02:00:03 iscsihead-m istgt[5152]:
istgt_lu_disk.c:3960:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write()
failed
Nov 1 02:00:03 iscsihead-m istgt[5152]:
hi,
Am Dienstag, den 01.11.2011, 13:48 +0100 schrieb Johan Hendriks:
Could it be that one drive is corrupt, or not available anymore?
Just a wild guess.
nope, all drives are OK. I had to reboot (reset) the server and it works
again, but along ...
cu denny
signature.asc
Description:
On Thu, 27 Oct 2011 18:32:19, Shawn Webb wrote:
SW #!/usr/sbin/dtrace -s
SW
SW #pragma D option quiet
SW
SW proc:::exec-success
SW /uid == $1/
SW {
SW printf(%d:%d:%s:, walltimestamp, uid, execname);
SW trace(curpsinfo-pr_psargs);
SW printf(\n);
SW }
Dtrace port to FreeBSD is not
Thanks. That's what I'm running into. I've partially fixed
walltimestamp. I have walltimestamp in kernel returning to dtrace
userland the seconds since epoch. With my patch, dtrace userland shows
the value fine if printed with %d, but not with %Y.
I'll be moving onto squashing the curpsinfo bug
On Thu, 2011-10-27 at 06:16 -0700, Wojciech A. Koszek wrote:
Dnia 18-10-2011 o 14:12:56 Alberto Villa avi...@freebsd.org napisał(a):
On Tue, Oct 18, 2011 at 1:48 PM, Wojciech A. Koszek
wkos...@freebsd.czest.pl wrote:
Commenting a driver out is almost always a bad idea and should
be done
On Tue, 25 Oct 2011 17:01:29 +0200
Claude Buisson clbuis...@orange.fr wrote:
I will do another test on 9.0 (after rebuilding the ports), and
eventually get rid of ATA_CAM and wait (im)patiently for a
knowledgeable one to have a look at the problem. If this is a real
problem, I may hope that
