Date: Sun, 12 Apr 2009 22:32:07 -0400 From: Ben Kelly <ben@wanderview.com> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-stable@freebsd.org, Ivan Voras <ivoras@freebsd.org> Subject: Re: ZFSKnownProblems - needs revision? Message-ID: <AE786821-358D-4DF5-A2A1-CF86F1BD169A@wanderview.com> In-Reply-To: <49DD1E2E.4030009@quip.cz> References: <gri5d9$15l$1@ger.gmane.org> <gri6io$4n7$1@ger.gmane.org> <49DD1E2E.4030009@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 8, 2009, at 5:59 PM, Miroslav Lachman wrote: > Rsync is used for "snapshots" with --link-dest= (each day has own > directory and all unchenged files are hardlinked to previous day and > I have history of two month back). > Backups are stored on /vol0 with compression enabled. (compression > is enabled on /usr/ports, /usr/src, /var/db/pkg, /vol0) > > # df -hi /vol0/ > Filesystem Size Used Avail Capacity iused ifree %iused > Mounted on > tank/vol0 2.7T 1.3T 1.3T 50% 17939375 11172232 62% / > vol0 > > This backup server is in service from october 2008 with just one > panic (kmem related). After proper loader.conf tuning it is working > well. You might want to look at this commit if you are using rsync --link- dest and getting kmem panics: http://svn.freebsd.org/viewvc/base?view=revision&revision=187460 and the MFC: http://svn.freebsd.org/viewvc/base?view=revision&revision=190837 It seems quite possible to me that kmem panics could be mistakenly attributed to zfs when the name cache is eating up memory. Hope that helps. - Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE786821-358D-4DF5-A2A1-CF86F1BD169A>