Date: Mon, 07 Mar 2005 11:58:02 -0500 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Dmitry Morozovsky <marck@rinet.ru> Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_5, snapshots and disk lock time Message-ID: <1110214682.63484.9.camel@zappa.Chelsea-Ct.Org> In-Reply-To: <20050307151733.I4264@woozle.rinet.ru> References: <20050307151733.I4264@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2005-03-07 at 15:21 +0300, Dmitry Morozovsky wrote:
> Dear colleagues,
>
> dumping the snapshot of 140G ufs2 fyle system under contemporary RELENG_5 I
> found that during mksnap_ffs file system is unresponsible even for reading for
> more than 3 minutes (it's on modern SATA disk with 50+ MBps linear transfer).
> Is it normal?
Oddly enough, this happened to me last night on a RELENG_5 system. In
my case, things were so bad that mksnap_ffs appeared to wedge
everything, meaning I'll have to make a trek in to where the machine is
located and press the ol' reset button to get things going again. :-(
The machine in question makes and mounts snapshots of all its
filesystems for backup each night via Tivoli TSM. This has worked
flawlessly for many months. Last night, I had many BitTorrent sessions
active on the filesystem that wedged. I guess the activity broke the
snapshot mechanism. :-( The odd thing is that it survived the night
before, when there were also BitTorrent sessions active.
I wonder how much activity mksnap_ffs can take?
Cheers,
Paul.
PS: The problematic file system was not low on space, which could be an
issue for snapshot creation.
--
e-mail: paul@gromit.dlib.vt.edu
"Without music to decorate it, time is just a bunch of boring production
deadlines or dates by which bills must be paid."
--- Frank Vincent Zappa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1110214682.63484.9.camel>