Date: Sun, 25 Apr 2010 13:24:13 +0200 From: Gary Jennejohn <gljennjohn@googlemail.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: <20100425132413.44d66b10@ernst.jennejohn.org> In-Reply-To: <alpine.BSF.2.00.1004241656270.1398@desktop> References: <4BD35437.2060208@lissyara.su> <alpine.BSF.2.00.1004241656270.1398@desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Apr 2010 16:57:59 -1000 (HST) Jeff Roberson <jroberson@jroberson.net> 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. > Jeff - One thing which surprised me was that I couldn't reuse the existing .sujournal files on my disks. I did notice that there are now more flags set on them. Was that the reason? Or were you just being careful? -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100425132413.44d66b10>