On 09/09/11 14:26, Bernt Hansson wrote:
You have run out of swapspace, based on these 2 lines
panic: ffs_write: dir write
current process = 0 (swapper)
Hmmm...
Cacti woldn't think so: the graph about swap space is plain flat (round
0%, by the way); of course it could have risen so fast that
2011-09-08 22:11, Andrea Venturoli skrev:
Hello.
Anyone can give any hint on this?
Guessing!
You have run out of swapspace, based on these 2 lines
panic: ffs_write: dir write
current process = 0 (swapper)
Or you have a hardware error. Does the "current process"
change between panics or is i
Hello.
Anyone can give any hint on this?
I really have no clue.
bye & Thanks
av.
# uname -a
FreeBSD x..it 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #1: Wed Dec 15
11:53:13 CET 2010 r...@x..it:/usr/obj/usr/src/sys/x i386
# kgdb kernel.debug /var/crash/vmc
Hello.
Any one can make anything out of this crash dump?
It's an SMP amd64 6.2 box with a RAID-5 SCSI controller and a couple GiB
of RAM. We are also using GELI.
bye & Thanks
av.
--
# kgdb kernel.debug /var/crash/vmco
Hello.
I got a reboot and a crash dump on a 6.2/i386 server.
Following is the stack trace.
Any hint?
bye & Thanks
av.
--
# kgdb kernel.debug /var/crash/vmcore.0
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not
Have production server harddisk problem, initially one disk (da5) was
down, then replaced. When trying to add a new (hotswap) drive according
to http://www.vinumvm.org/vinum/replacing-drive.html ,
the system stopped and came up in the state seen below. Is there a way
to get it back up or should
On Tuesday, 12 August 2003 at 0:53:06 +0200, Per olof Ljungmark wrote:
> Have production server harddisk problem, initially one disk (da5) was
> down, then replaced. When trying to add a new (hotswap) drive according
> to http://www.vinumvm.org/vinum/replacing-drive.html ,
> the system stopped and
