Date: Sat, 24 Apr 2010 20:17:07 -0700 From: Matthew Jacob <mj@feral.com> To: Jeff Roberson <jroberson@jroberson.net> Cc: Alex Keda <admin@lissyara.su>, freebsd-current@freebsd.org Subject: Re: HEADS UP: SUJ Going in to head today Message-ID: <4BD3B433.2080009@feral.com> In-Reply-To: <alpine.BSF.2.00.1004241656270.1398@desktop> References: r2x7d6fde3d1004210606o25fdf542j42cb5fdef75991e2@mail.gmail.com <4BD35437.2060208@lissyara.su> <alpine.BSF.2.00.1004241656270.1398@desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff Roberson wrote: > On Sun, 25 Apr 2010, Alex Keda wrote: > >> try in single user mode: >> >> tunefs -j enable / >> tunefs: Insuffient free space for the journal >> tunefs: soft updates journaling can not be enabled >> >> tunefs -j enable /dev/ad0s2a >> tunefs: Insuffient free space for the journal >> tunefs: soft updates journaling can not be enabled >> tunefs: /dev/ad0s2a: failed to write superblock > > There is a bug that prevents enabling journaling on a mounted > filesystem. So for now you can't enable it on /. I see that you have > a large / volume but in general I would also suggest people not enable > suj on / anyway as it's typically not very large. I only run it on my > /usr and /home filesystems. > > I will send a mail out when I figure out why tunefs can't enable suj > on / while it is mounted read-only. > > Thanks, > Jeff One of the attractions for suj would be for appliancized FreeBSD which now has to set 'fsck -y' for power fail/resets- and this means root as well.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BD3B433.2080009>