Actually a regular file (on a RAID1 setup with gmirror and 2 identical disks) is used as backing store for ZFS. The hardware should be fine as nothing else seems to be corrupt. Wonder if a server reset could have caused the issue? There are 2 things that surely do not work perfectly: 1. Startup: [root@xxx /etc/rc.d]# cat /etc/rc.conf | grep mdconfig mdconfig_md0="-f /usr/local/zfs/store" [root@xxx /etc/rc.d]# /etc/rc.d/mdconfig start Creating md0 device (-f). mount: /dev/md0: unknown special file or file system
I have to run 2 times "zfs mount all", to see the folders. 2. Shutdown: ... +++ /tmp/security.Z3SCbf2M 2011-10-26 03:07:20.000000000 +0200 +Waiting (max 60 seconds) for system process `vnlru' to stop...done +Waiting (max 60 seconds) for system process `bufdaemon' to stop...done +Wait +iSnygn ci(nmga xd is6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr5oc ess `syncer' to stop...4 1 3 3 2 2 0 0 0 done +All buffers synced. The computer does not reboot after this, just waits for ??? . Manual reset is needed. Is ZFS not recommended with file backing store? B. ---------------------------------------- > From: opensolarisisdeadlongliveopensola...@nedharvey.com > To: sbre...@hotmail.com; zfs-discuss@opensolaris.org > Subject: RE: [zfs-discuss] Remove corrupt files from snapshot > Date: Mon, 14 Nov 2011 09:36:58 -0500 > > > From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- > > boun...@opensolaris.org] On Behalf Of sbre...@hotmail.com > > > > What does this error mean? I cannot even "scan" the ZFS file system > > anymore? Is there any "fsck" for ZFS? > > There is zpool scrub. It will check all the checksums previously > calculated, verifying the data that was actually written is the data ZFS > previously thought it wrote. If you have sufficient redundancy (mirror or > raid) it will self-correct any errors it finds. > > Since you're experincing corruption that doesn't go away, I'm supposing you > don't have redundancy, or else the corruption happened in something higher > up, such as a failing cpu or non-ecc ram, or a flaky disk controller. > > In any event, do you have any reason to believe you've eliminated the cause > of the corruption? The behavior you're experiencing is normal if you have > failing hardware. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
