Date: Wed, 3 Jan 2007 12:22:42 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Willem Jan Withagen <wjw@withagen.nl> Cc: stable@freebsd.org Subject: Re: running mksnap_ffs Message-ID: <20070103102242.GB21325@deviant.kiev.zoral.com.ua> In-Reply-To: <459AE536.5040007@withagen.nl> References: <459ABB40.7050603@digiware.nl> <20070102222003.GB90174@in-addr.com> <459AE536.5040007@withagen.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--7oQ1FFvyVKNZi+9s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 03, 2007 at 12:05:26AM +0100, Willem Jan Withagen wrote: > Gary Palmer wrote: > >On Tue, Jan 02, 2007 at 09:06:24PM +0100, Willem Jan Withagen wrote: > >>Hi, > >> > >>I got the following Filesystem: > >>Filesystem Size Used Avail Capacity iused ifree %iused=20 > >>/dev/da0a 1.3T 422G 823G 34% 565952 182833470 0% > >> > >>Running of a 3ware 9550, on a dual core Opteron 242 with 1Gb. > >>The system is used as SMB/NFS server for my other systems here. > >> > >>I would like to make weekly snapshots, but manually running mksnap_ffs= =20 > >>freezes access to the disk (I sort of expected that) but the process=20 > >>never terminates. So I let is sit overnight, but looking a gstat did no= t=20 > >>reveil any activity what so ever... > >>The disk was not released, mksnap_ffs could not be terminated. > >>And things resulted in me rebooting the system. > >> > >>So: > >> - How long should I expect making a snapshot to take: > >> 5, 15, 30min, 1, 2 hour or even more??? > >> - How do I diagnose the reason why it is not terminating? > > > >You forgot to mention what revision of FreeBSD you are running, and > >if you are using quotas or anything else on the filesystem that > >could impact this. >=20 > Yes, I pressed send somewhat to fast: >=20 > [~] wjw@bigsurf> uname -a > FreeBSD bigsurf.digiware.nl 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #3: Wed= =20 > Sep 27 15:57:20 CEST 2006 =20 > wjw@bigsurf.digiware.nl:/usr/obj/usr/src/sys/BIGSURF amd64 See http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel= debug-deadlocks.html for instruction how to gather information needed to debug the problem. --7oQ1FFvyVKNZi+9s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFm4PyC3+MBN1Mb4gRAglOAKCwqzl43xDEXWR+2p/r5SueP38KSgCfR7Qd 7fQCwQqCBGNkB/4BNzOZoj8= =uFpu -----END PGP SIGNATURE----- --7oQ1FFvyVKNZi+9s--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070103102242.GB21325>