Date: Wed, 09 Jul 2008 14:56:43 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: aslam_mohamed@wordbank.com Cc: Dmitry Morozovsky <marck@rinet.ru>, current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system Message-ID: <4874B58B.7000108@FreeBSD.org> In-Reply-To: <4874A981.7080106@wordbank.com> References: <bd9320b30807072315x105cf058tf9f952f0f5bb2a6a@mail.gmail.com> <20080708100701.57031cda@twoflower.in.publishing.hu> <bd9320b30807080131j5e0e02a4y3231d7bfa1738517@mail.gmail.com> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> <20080709152739.Q58331@woozle.rinet.ru> <4874A453.7060406@FreeBSD.org> <4874A981.7080106@wordbank.com>
next in thread | previous in thread | raw e-mail | index | archive | help
aslam_mohamed@wordbank.com wrote: > Hi, > I have been using FreeBSD/ZFS for our backup system for last few > months.. We had 6TB external disks connected through Firewire to the > Server. Last week all the backup data disappeared along with the pool > and everything!!!..When I typed zpool status - it says no pool > available..Build up to this incident has always been a firefighting > situation for me. We use Rsync to sync all the servers to FreeBSD's ZFS > pool everyday. Most of the time Rsync hung on the middle of the syncing > process. When this happen I have to restart the server to run the > backup again and mount the ZFS pool (it requires manual mounting most > of the time!!). Sometimes it throws some error like - > GEOM: da0: corrupt or invalid GPT detected. > GEOM: da0: GPT rejected -- may not be recoverable. > GEOM: da1: corrupt or invalid GPT detected. > GEOM: da1: GPT rejected -- may not be recoverable > I don't know what caused the disappearance of the ZFS pool and if > someone could explain how I can retrieve the data from the external > disks, that would be really helpful?.. What you pasted says that the disks were rejected by GEOM because the partition table was "corrupt or invalid". I don't know for sure why this might be, but one possible cause would be if there is data corruption in your I/O path. Do you get errors from ZFS about checksum failures or other errors? Maybe there is a problem with the firewire stack, or support for your firewire hardware. The rsync hanging is almost certainly either for the same memory reasons we have been discussing, or a side effect of I/O problems to the disks. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4874B58B.7000108>