Hello.
Finally I have time to look at my build server which gave zfs errors
again. Several weeks ago I've tried to move it from physical server to
KVM host. This attempt failed. Even when I created new zfs pool and
moved data by tar (for example, my home directory), I started receiving
messages like:
errors: Permanent errors have been detected in the following files:
<0xb04>:<0x4832f>
<0x2618>:<0x18a6598>
<0x1a35>:<0x4832f>
<0x2045>:<0x4832f>
data/export/home/alp:<0x1907949>
<0x1596>:<0x4832f>
<0x25fd>:<0x4832f>
from zpool status.
The new server has ECC memory and didn't have any issues with it, so I
started to blame KVM. (Honestly, I don't know what should I blame).
Scary part is that I see similar messages about corrupted files even on
source host after running scrub.
So I'm moving now data to ESXi VM. I'm looking at moving zones. Is it
safe to use zfs send for moving zones data with zfs send if zpool status
says that data pool has corrupted files (on the source side)? Or is it
better to use tar? I'd prefer to transfer tar archives. If I create zfs
filesystems for zones with zoned property on and mount point set to
legacy, transfer files and zoneadm export data, will I be able to attach
zones (I mean without zfs sending/receiving zone zfs filesystem) or are
there some more specific zfs FS properties which I should copy?
--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com
