Date: Sun, 19 Jul 2009 03:01:02 -0600 From: Anthony Chavez <acc@hexadecagram.org> To: freebsd-fs@freebsd.org Subject: Re-starting a gjournal provider Message-ID: <4A62E0CE.1000508@hexadecagram.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1A46517B3DE33B53F0705681 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello freebsd-fs, I'm trying to get gjournal working on a "removable" hard disk. I use the term loosely, because I'm using a very simple eSATA enclosure: an AMS Venus DS5 [1]. If I swap out disks, atacontrol cap ad0 seems sufficient enough to detect the new drive: the reported device model, serial number, firmware revision, and CHS values change as one would expect. My interpretation of [2] section 5.3 and gjournal(8) is that the following sequence of commands should ensure me that all write buffers have been flushed and bring the system to a point where it is safe to remove a disk. sync; sync; sync gjournal sync umount /dev/ad0s1.journal gjournal stop ad0s1.journal However, once they are executed, /dev/ad0s1.journal disappears and when I swap out the disk it doesn't come back. The only way I've found to bring it back is atacontrol detach ata0; atacontrol attach ata0, which doesn't seem like a wise thing to do if I have another device on the same channel. My question is, do I need to issue gjournal stop before I swap disks? And if so, is there any way that I can avoid the atacontrol detach/attach cycle that would need to take place before any mount is attempted so that /dev/ad0s1.journal appears (if in the drive inserted at the time does in fact utilize gjournal; I may want to experiment with having disks with either gjournal or soft updates)? And while I'm on the subject, are the (gjournal) syncs commands preceeding umount absolutely necessary in the case of removable media? [1] http://www.american-media.com/product/external/ds/ds.html [2] http://www.freebsd.org/doc/en/articles/gjournal-desktop/article.html --=20 Anthony Chavez http://hexadecagram.org/ mailto:acc@hexadecagram.org xmpp:acc@hexadecagram.org --------------enig1A46517B3DE33B53F0705681 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpi4NcACgkQbZTbIaRBRXHA8ACfSY5wcSsQjXGE1lHhMrIBVtaV br0AnRpeo1Jbi56/i9Qp5F60W/sAtLwU =eBD0 -----END PGP SIGNATURE----- --------------enig1A46517B3DE33B53F0705681--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A62E0CE.1000508>