Date: Wed, 2 Apr 2008 01:31:10 -0600 From: "Cyrus Rahman" <crahman@gmail.com> To: "Kris Kennaway" <kris@freebsd.org> Cc: freebsd-fs@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org> Subject: Re: Trouble with snapshots Message-ID: <9e77bdb50804020031r2fba0840g7281e879522120d5@mail.gmail.com> In-Reply-To: <47F298C2.7040606@FreeBSD.org> References: <9e77bdb50804011251q65eca371kc6bc9a60ac0c248@mail.gmail.com> <47F298C2.7040606@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > This is happening on a system set up with journaled ufs filesystems, > > so that may be part of the problem. The system is running amd64 > > with an Intel Q6600. > > I thought gjournal and soft updates were supposed to be mutually > exclusive (the latter is required for UFS snapshots). Anyway, even if > they are supposed to work together this interaction is almost certainly > the cause. I actually think that snapshots are a part of UFS2 and that they work just fine with or without soft updates. I was wondering if the problems I've seen are limited strictly to gjournal-based UFS2 systems. I'm guessing that they are, based upon the fact that the problems are dramatic enough to have shown up in discussion if they were widespread. But I also wondered if perhaps the additional concurrency associated with multiple processors might be a factor. As it is, it may be prudent for someone intending to use dump with snapshots to hold off on building filesystems with gjournal until this is resolved. Other than this problem, the gjournal/ufs integration has worked flawlessly here.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9e77bdb50804020031r2fba0840g7281e879522120d5>