Date: Mon, 23 Jan 2012 08:50:52 +0100 From: Patrick Lamaiziere <patfbsd@davenulle.org> To: Dale Scott <dalescott@shaw.ca> Cc: questions@freebsd.org Subject: Re: non-responsive FreeBSD-9.0 after dump command Message-ID: <20120123085052.678c34d4@davenulle.org> In-Reply-To: <fba43dba8b435.4f16f662@shaw.ca> References: <fba43dba8b435.4f16f662@shaw.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Le Wed, 18 Jan 2012 16:42:10 -0700, Dale Scott <dalescott@shaw.ca> a écrit : > # mount > /dev/ada0p2 on / (ufs, local, journaled soft-updates) > devfs on /dev (devfs, local, multilabel) > /dev/ad1as1d on /backup (ufs, local, soft-updates) > # > # cd /backup > # dump -0aLf 20120118.dump / > > There is no output after hitting <enter>, and afterwards the system > is generally unresponsive. A command (e.g., whoami) typed into the > VirtualBox server console and an ssh terminal is echo'd, but that's > all. I had started "top" in a seperate ssh terminal before issuing > the dump command, and it shows mksnap_ffs running with 98%-100% WCPU > for about 55 minutes, at which point "top" stops updating. I gave up > after 70 minutes and yanked the virtual power cord. There are several reports that snapshots are broken on ufs+SUJ and dump takes a snapshot. Regards.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120123085052.678c34d4>