HEADS UP: SUJ Going in to head today

[Jeff Roberson]

On Sun, 25 Apr 2010, Bruce Cran wrote:

> On Sunday 25 April 2010 19:47:00 Scott Long wrote:
>> On Apr 24, 2010, at 8:57 PM, 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.
>>
>> This would preclude enabling journaling on / on an existing system, but I
>> would think that you could enable it on / on a system that is being
>> installed, since (at least in theory) the target / filesystem won't be the
>> actual root of the system, and therefore can be unmounted at will.
>
> It worked here - it's shown as enabled after I booted in single-user mode and
> enabled it yesterday:

I think some people are enabling after returning to single user from a 
live system rather than booting into single user.  This is a different 
path in the filesystem as booting directly just mounts read-only while the 
other option updates a mount from read/write.  I believe this is the path 
that is broken.

Thanks,
Jeff

>
> core# dumpfs / | grep -i journal
> flags   soft-updates+journal
>
> -- 
> Bruce Cran
>