similar to: Error reporting & backup with tar

Dear all, given a DVD drive and DAT Tape Drive, and using Solaris 10 U7 (5/09), how can we plan for a total backup of ZFS root disk and procedure to recover that? Previously using UFS, we just need to use boot from Solaris OS DVD media, also using ufsdump, ufsrestore and installboot. Anybody can point me on how to achieve the same thing when the whole system disk are busted? Thanks in

While testing a zpool with a different storage adapter using my "blkdev" device, I did a test which made a disk unavailable -- all attempts to read from it report EIO. I expected my configuration (which is a 3 disk test, with 2 disks in a RAIDZ and a hot spare) to work where the hot spare would automatically be activated. But I''m finding that ZFS does not behave this way

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, On 10/2/20 4:59 am, Francis Augusto Medeiros-Logeay wrote: > What I do: > > 1 - I ran a maildirlock command to my mail folder 2 - I then rsync > the folder where my maildirs are, as well as the indexes, to a > remote location If rsync is not fast... then how about doing a snapshot and then rsync off the snapshot? (I do rsync

I looked into backing up ZFS and quite honostly I can''t say I am convinced about its usefullness here when compared to the traditional ufsdump/restore. While snapshots are nice they can never substitute offline backups. And although you can keep quite some snapshots lying about it will consume diskspace, one of the reasons why people also keep offline backups. However, while you can make

Apologies up front for failing to find related posts... Am I overlooking a way to get ''zfs send -i fs at 0 fs at 1 | zfs receive -n -v ...'' to show the contents of the stream? I''m looking for the equivalent of ufsdump 1f - fs ... | ufsrestore tv - . I''m hoping that this might be a faster way than using ''find fs -newer ...'' to learn

>> How do i compile mbuffer for our system, Thanks to Mike Futerko for help with the compile, i now have it installed OK. >> and what syntax to i use to invoke it within the zfs send recv? Still looking for answers to this one? Any example syntax, gotchas etc would be much appreciated. -- Kind regards, Jules free. open. honest. love. kindness. generosity. energy. frenetic.

On Solaris x86, does zpool (or anything) support PATA (or SATA) IDE SMART data? With the Predictive Self Healing feature, I assumed that Solaris would have at least some SMART support, but what I''ve googled so far has been discouraging. http://prefetch.net/blog/index.php/2006/10/29/solaris-needs-smart-support-please-help/ Bug ID: 4665068 SMART support in IDE driver

This morning we got a fault management message from one of our production servers stating that a fault in one of our pools had been detected and fixed. Looking into the error using fmdump gives: fmdump -v -u 90ea244e-1ea9-4bd6-d2be-e4e7a021f006 TIME UUID SUNW-MSG-ID Oct 22 09:29:05.3448 90ea244e-1ea9-4bd6-d2be-e4e7a021f006 FMD-8000-4M Repaired

Hi all, We are having some problems getting a solaris 9(sparc) file server running samba 2.2.2 to authenticate aginst a windows NT 4 PDC. Let me say first that this was all working at one time, then we had some data corrumption on our NFS mounted /usr/local, and had to restore from tape. Due to some issues with solaris ufsdump and ufsrestore, stuff was not quite put back properly. We do

How can I diagnose why a resilver appears to be hanging at a certain percentage, seemingly doing nothing for quite a while, even though the HDD LED is lit up permanently (no apparent head seeking)? The drives in the pool are WD Raid Editions, thus have TLER and should time out on errors in just seconds. ZFS nor the syslog however were reporting any IO errors, so it weren''t the disks.

I''ve been using a 5-disk raidZ for years on SXCE machine which I converted to OSOL. The only time I ever had zfs problems in SXCE was with snv_120, which was fixed. So, now I''m at OSOL snv_111b and I''m finding that scrub repairs errors on random disks. If I repeat the scrub, it will fix errors on other disks. Occasionally it runs cleanly. That it doesn''t

We recently had a disk fail on one of our whitebox (SuperMicro) ZFS arrays (Solaris 10 U9). The disk began throwing errors like this: May 5 04:33:44 dev-zfs4 scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci15d9,400 at 0 (mpt_sas0): May 5 04:33:44 dev-zfs4 mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31110610 And errors for the drive were

I''m looking for a way to backup my entire system, the rpool zfs pool to an external HDD so that it can be recovered in full if the internal HDD fails. Previously with Solaris 10 using UFS I would use ufsdump and ufsrestore, which worked so well, I was very confident with it. Now ZFS doesn''t have an exact replacement of this so I need to find a best practice to replace it.

Using build 70, I followed the zfsboot instructions at http:// www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/ to the letter. I tried first with a mirror zfsroot, when I try to boot to zfsboot the screen is flooded with "init(1M) exited on fatal signal 9" Than I tried with a simple zfs pool (not mirrored) and it just reboots right away. If I try to setup grub

On 09.02.2020 19:08, Andrew McGlashan wrote: > > If rsync is not fast... then how about doing a snapshot and then rsync > off the snapshot? (I do rsync over lvm snapshots to back up file > systems cleanly) and, btw, perform file system dumps [ufsdump / > ufsrestore like, but dump and restore on Linux] of *non-mounted* > backup file systems fwiw. > > I have other rsyncs

I have a zpool which has grown "organically". I had a 60Gb disk, I added a 120, I added a 500, I got a 750 and sliced it and mirrored the other pieces. The 60 and the 120 are internal PATA drives, the 500 and 750 are Maxtor OneTouch USB drives. The original system I created the 60+120+500 pool on was Solaris 10 update 3, patched to use ZFS sometime last fall (November I believe). In

Does anyone have a solution for the problem of file and directory names containing characters which are OK in DOS/Windows but illegal (or at least unwise) in Unix? I have Windows clients who have written directory names containing "$" characters to Samba shares on a Solaris box. This is fine for the clients, but plays havoc with Solaris programs needing to access the files, eg. backups

Hi all, First, I''ll say my intent is not to spam a bunch of lists, but after posting to opensolaris-discuss I had someone communicate with me offline that these lists would possibly be a better place to start. So here we are. For those on all three lists, sorry for the repetition. Second, this message is meant to solicit help in diagnosing the issue described below. Any hints on

So, I noticed that a lot of the fixes discussed here recently, including the ZFS/NFS interaction bug fixes and the deadlock fix has made it into 20060327 that was released this morning. My question is whether we''ll see all these up to the minute bug fixes in the Solaris 10 update that brings ZFS to that product, or if there is a specific date where no further updates will make it in to

how does one free segment(offset=77984887808 size=66560) on a pool that won''t import? looks like I found http://bugs.opensolaris.org/view_bug.do?bug_id=6580715 http://mail.opensolaris.org/pipermail/zfs-discuss/2007-September/042541.html when I luupgrade a ufs partition with a dvd-b62 that was bfu to b68 with a dvd of b74 it booted fine and I was doing the same thing that I had done on