Date: Mon, 18 Aug 2003 15:47:38 -0700 From: Kris Kennaway <kris@obsecurity.org> To: "Branko F. Gra?nar" <bfg@noviforum.si> Cc: freebsd-current@freebsd.org Subject: Re: mksnap_ffs, snapshot issues, again Message-ID: <20030818224738.GA74620@rot13.obsecurity.org> In-Reply-To: <003e01c365c8$b9a1a930$fac8a8c0@MORDOR> References: <003e01c365c8$b9a1a930$fac8a8c0@MORDOR>
next in thread | previous in thread | raw e-mail | index | archive | help
--Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 18, 2003 at 10:38:47PM +0200, Branko F. Gra?nar wrote: > # mksnap_ffs /export aaa.snap >=20 > ... after 30 minutes ... snapshot was not created (!!! On a empty > filesystem !!!)... Ok, long snapshot creation would be fine if it > would not hang all processes, which would like to do something on > /export (ls /export for example.). Filesystem cannot be > unmounted. mksnap_ffs process cannot be killed. Reboot and > foreground fsck helps. Please wrap your lines at 70 characters so your emails can be easily read. The behaviour of filesystem activity stalling during snapshot creation is intentional, but 30 minutes to snapshot an empty FS is not. Is there disk activity during this time? It's not clear from your mail whether bg fsck is in operation during this time. If so, that's probably the cause, since bg fsck itself uses a snapshot to check the FS consistency. Kris --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/QVeKWry0BWjoQKURAjSWAKDXlEU2jLan8iIMnG6nEd86CH7dzQCgpfXu ny1RT72JwysKHx+7SyHTJjU= =hh40 -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030818224738.GA74620>