similar to: How do I protect my zfs pools?

Morning all ... 'K, this one is a first for me ... server crashed this aft and savecore wouldn't dump the resultant core: pluto# savecore -v /vm/crash dumplo = 4362141696 (8519808 * 512) savecore: warning: /kernel version mismatch: "FreeBSD 4.8-STABLE #1: Sat May 31 22:57:04 ADT 2003 " and " #(#(#(" savecore: reboot savecore: dump time is zero

David gave me some suggestions to check out on the servers, but so far, its all drawing a blank ... I have two servers right now that are updated to recent 4.8-STABLE kernels ... one was June 22nd, and the other was upgraded June 20th ... both of them have crashed since that date, and both of them tell me that they are unable to produce a core file, with the same errors: Jun 26 04:27:14 jupiter

Hi All, I''d like to set up dumping to a file. This file is on a mirrored pool using zfs. It seems that the dump setup doesn''t work with zfs. This worked for both a standard UFS slice and a SVM mirror using zfs. Is there something that I''m doing wrong, or is this not yet supported on ZFS? Note this is Solaris 10 Update 3, but I don''t think that should

Hi! I've got FreeBSD 8.3-STABLE/i386 server that can be reliably panicked using just 'squid -k rotatelog' command. It seems the system suffers from the problem described here: http://cxsecurity.com/issue/WLB-2010090156 I could not find any FreeBSD Security Advisory containing a fix. My server has 4G physical RAM (about 3.2G available) and runs squid (about 110M VSS) with 500

Greetings I am having trouble with suspend/resume on my Thinkpad X31, running 7.0-STABLE as of April 23. Any help would be appreciated. First problem: When I run "acpiconf -s3" from mulituser mode, the system suspends immediately, without executing /etc/rc.suspend (which has mode 755); then on resume, I get a panic. Second problem: When the system panics, I don't get a dump (or

'k, now one of my other machines is getting the same thing on a crash: savecore: warning: /kernel version mismatch: "FreeBSD 4.8-STABLE #2: Fri Jun 20 18:34:14 ADT 2003 " and "" It was working, last successful savecore on that machine was Jun 6th: -rw------- 1 root wheel 4227792896 Jun 6 23:58 vmcore.1 -rw------- 1 root wheel 4227792896 Jun 6 10:37

My home NAS box, that I''d upgraded to Solaris 2008.11 after a series of crashes leaving the smf database damaged, and which ran for 4 days cleanly, suddenly fell right back to where the old one had been before. Looking at the logs, I see something similar to (this is manually transcribed to paper and retyped): Bad trap: type=e (page fault) rp=f..f00050e3250 addr=28 module ZFS null

I started three new threads recently, "Feature proposal: differential pools" "Feature proposal: trashcan via auto-snapshot with every txg commit" "Flushing synchronous writes to mirrors" Matthew Ahrens and Henk Langeveld both replied to my first thread by sending their messages to both me and to zfs-discuss at opensolaris.org, and Matt did likewise for my second

Hello all, I am not sure my original mail got through to the list (I haven''t received it back), so I attach it below. Anyhow, now I have a saved kernel crash dump of the system panicking when it tries to - I believe - deferred-release the corrupted deduped blocks which are no longer referenced by the userdata/blockpointer tree. As I previously wrote in my thread on unfixeable

On 11/3/2017 1:31 AM, hw wrote: >> 2.5" SAS drives spinning at 10k and 15k RPM are the performance >> solution for online storage, like databases and so forth.?? also make >> more sense for large arrays of SSDs, as they don't even come in >> 3.5".??? With 2.5" you can pack more disks per U (24-25 2.5" per 2U >> face, vs 12 3.5" max per

Is it still the case that there is a kernel panic if the device(s) with the ZFS pool die? I was thinking to attach some cheap SATA disks to a system to use for nearline storage. Then I could use ZFS send/recv on the local system (without ssh) to keep backups of the stuff in the main pool. The main pool is replicated across 2 arrays on the SAN and we have multipathing and it''s quite

One of our Solaris 10 update 3 servers paniced today with the following error: Sep 18 00:34:53 m2000ef savecore: [ID 570001 auth.error] reboot after panic: assertion failed: ss != NULL, file: ../../common/fs/zfs/space_map.c, line: 125 The server saved a core file, and the resulting backtrace is listed below: $ mdb unix.0 vmcore.0 > $c vpanic() 0xfffffffffb9b49f3() space_map_remove+0x239()

Greetings, I have a USB external 2TB HDD with one NTFS partition which is to be used for backup up from about 5-8 workstations (all Win*) all are shut down when the office is closed I am playing around with Amanda server on Centos 5.7. (It is over 3 years since I last implemented Amanda for about 50 workstations mostly Fedora and couple of XP boxes -- it sang and danced quite nicely.) Now the

On 2/2/2015 8:11 PM, Jatin Davey wrote: > disk 252:1 | 0-0-0 | 9XG7TNQVST91000640NS CC03 | Online, Spun Up > disk 252:2 | 0-0-1 | 9XG4M4X3ST91000640NS CC03 | Online, Spun Up > disk 252:3 | 0-1-1 | 9XG4LY7JST91000640NS CC03 | Online, Spun Up > disk 252:4 | 0-1-0 | 9XG51233ST91000640NS CC03 | Online, Spun Up > End of Output ************************** > > Let me know if i need to

We recently installed a 24 disk SATA array with an LSI controller attached to a box running Solaris X86 10 Release 4. The drives were set up in one big pool with raidz, and it worked great for about a month. On the 4th, we had the system kernel panic and crash, and it''s now behaving very badly. Here''s what diagnostic data I''ve been able to collect so far: In the

I believe concerns like this should go to you? Bev. -------- Original Message -------- Subject: [zfs-discuss] zfs discussion forum bug Date: Sat, 29 Jul 2006 00:03:13 -0700 (PDT) From: Andrew <andrewee2@yahoo.com> To: zfs-discuss@opensolaris.org I started three new threads recently, "Feature proposal: differential pools" "Feature proposal: trashcan via auto-snapshot with

I am trying to configure a samba with openldap as a PDC on SuSE9.1 with samba-3.0.4, openldap2-2.2.6, samba-winbind-3.0.4, following the book Samba-3 By Example, by John H. Terpstra. I am getting errors "NT_STATUS_LOGON_FAILURE" from smbclient commands and "The username or password was not correct." from 'net' commands. Anonymous smbclient access seems to work, and I

On 2/3/2015 10:00 AM, John R Pierce wrote: > On 2/2/2015 8:11 PM, Jatin Davey wrote: >> disk 252:1 | 0-0-0 | 9XG7TNQVST91000640NS CC03 | Online, Spun Up >> disk 252:2 | 0-0-1 | 9XG4M4X3ST91000640NS CC03 | Online, Spun Up >> disk 252:3 | 0-1-1 | 9XG4LY7JST91000640NS CC03 | Online, Spun Up >> disk 252:4 | 0-1-0 | 9XG51233ST91000640NS CC03 | Online, Spun Up >> End of

Hi Robert - I'm running it successfully on C7 using xinetd.? Do you have documentation for running it directly from systemd?? Working xinetd configuration: cat /etc/xinetd.d/amanda # default: off # description:? The client for the Amanda backup system.\ #?????????????? This must be on for systems being backed up\ #?????????????? by Amanda. service amanda { ??? disable???????? = no ???

hello puppet list My puppet server is now working quite wonderfully. Thanks go out to all who have assisted in getting it to this point. At this point in time my config is now correctly installing packages according to arch,os and release. Centos is working quite well as of now, but I am attempting to get the ubuntu side of things to work as well. I am frankly more familiar with RHEL under