On Thu, 16 Sep 2004, Sam wrote:
1PB is - what? 2^50 bytes? That looks closer to 2^64 than your
figures indicate. I'd imagine an exabyte a year ought to be topping out
after 16 years. I'm missing about half-a-dozen orders of magnitude
somewhere it seems.
Where on earth would you find a disk
On Fri, May 14, 2004 at 11:33:49AM -0400, John Baldwin wrote:
Do 'l *0xc0519a64' in gdb to get the line that it actually faulted on. Since
this is likely a NULL pointer deref that might help you fix the bug or at
least find out its cause.
Wow. That's interesting to me. I didn't expect
The situation:
Dell PowerEdge 1750, Dual 3.2 GHz, 1 GB RAM.
Sources compiled from CVS on 4 May 2004, RELENG_5_2 branch.
# uname -a
FreeBSD hr-stc-file2.smartrafficenter.net 5.2.1-RELEASE-p5 FreeBSD 5.2.1-RELEASE-p5
#0: Tue May 4 11:02:47 EDT 2004 [EMAIL
On Thu, May 13, 2004 at 01:16:59PM -0400, Kevin A. Pieckiel wrote:
One filesystem NFS mounted from another FBSD 4.9 box.
Samba 3.0.4 is installed and running (AD member server).
Samba is mapping home directories to the NFS-mounted files.
When accessing a home directory from a Windows
On Thu, May 13, 2004 at 05:19:39PM -0600, Shawn Webb wrote:
I can't tell exactly what's going on, but from that output, it seems as
though it's smbd's fault, not NFS's
How can I dive deeper? Or _CAN_ I dive deeper? Can I identify the
faulting instruction and determine why it's faulting? At
I want to modify sys/param.h to increase the value of MAXLOGNAME. I know
I'll need to recompile world/kernel after such a change. Do I need to
only modify /usr/src/sys/sys/param.h, or rather do I need to modify
/usr/include/sys/param.h? I'm assuming when I make buildworld or make
buildkernel,
On Sat, Dec 27, 2003 at 10:53:57AM +0100, Soren Schmidt wrote:
It seems Kevin A. Pieckiel wrote:
I have a Promise FastTrak SATA150 controller with two 120 GB drives
that are mirrored. Using 5.1-RELEASE-p10 with sources from Nov 3.
I tried to upgrade from 5.1 to 5.2-RC today and the new
I have a Promise FastTrak SATA150 controller with two 120 GB drives
that are mirrored. Using 5.1-RELEASE-p10 with sources from Nov 3.
I tried to upgrade from 5.1 to 5.2-RC today and the new kernel couldn't
mount my root partition (/dev/ar0s1a) after doing make installkernel
and rebooting into
I have a Promise FastTrak SATA150 controller with two 120 GB drives
that are mirrored. Using 5.1-RELEASE-p10 with sources from Nov 3.
I tried to upgrade from 5.1 to 5.2-RC today and the new kernel couldn't
mount my root partition (/dev/ar0s1a) after doing make installkernel
and rebooting into
)
pci2: network, ethernet at device 8.0 (no driver attached)
This is from sources cvs'ed and compiled today (21 Aug 2003).
Any help would be appreciated.
Kevin A. Pieckiel
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo
.
Thanks much,
Kevin A. Pieckiel
#dmesg
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002
[EMAIL
Mike,
On Wed, Jul 23, 2003 at 04:57:38PM -0500, Mike Silbersack wrote:
Your panic seems to indicate that the mbuf cluster chain became corrupted,
which could have happened in one of a few ways. I'll address your
question in two parts:
1. How do I prevent the system from using all mbuf
12 matches
Mail list logo
