On Jan 10, 2008, at 9:32 AM, Carson Gaspar wrote: > eric kustarz wrote: >> On Jan 10, 2008, at 9:18 AM, Łukasz K wrote: >> >>> I need automatic system. Now I'm using zfs send but it >>> takes too much human resources to control it. >> >> cron job? > > Oh look, I did a zfs send in cron, and my resilver never finished, > and I > lost a second drive, and now my data has vanished in a puff of smoke!
So use raid-z2 :) Yes we know its a problem. Yes we are working on it. No, it isn't trivial to fix. Still, resilvering should be a rare event. Snapshots can still be used daily/hourly/whatever time you prefer (when a resilver isn't needed). Its less than ideal, but build into your scripts the knowledge that a resilver is active, don't take snapshots, and send an alert. > > This resilver restart bug is an abomination, and the fact that Sun > hasn't considered it a sev 1 priority and produced a fix for Solaris > customers is mind boggling. We are working on a proper fix. > > The OP should use AVS or rsync. zfs send / recv is just not useful > right > now, much to my regret. Neither are snapshots. The zfs universe is > just > a really sad place right now... We are all entitled to our own opinions (whether they are right or wrong). eric _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
