tunefs problem

Look at the output from fsck.  It very clearly tells you
that it  
found problems, but didn't fix them (probably because the
partition  
is mounted).  Notice the following lines:
** /dev/ad2s1a (NO WRITE)
and
CLEAR? no

Boot to single user mode and try it again.

Also, if you add fsck_y_enable="YES" to rc.conf
these should be fixed  
automatically at boot (IIRC).

HTH

On Oct 8, 2005, at 2:32 AM, Sasa Stupar wrote:

>
>
> --On 8. oktober 2005 0:20 -0700 David Kirchner
<dpkdpk.net> wrote:
>
>
>> On 10/8/05, Sasa Stupar <sasastupar.homelinux.net> wrote:
>>
>>> I am trying to enable tunefs for my filesystem
but I get the  
>>> following:
>>> -------------
>>> # tunefs -n enable /
>>> tunefs: soft updates cannot be enabled until
fsck is run
>>> tunefs: /dev/ad2s1a: failed to write superblock
>>> -------------
>>>
>>> But AFAIK fsck is not running.
>>>
>>> What am I missing here?
>>>
>>> Regards,
>>> Sasa
>>>
>>
>> It means that you need to run fsck on the partition
before you can
>> enable softupdates. Something like "fsck -y
/" will do it.
>>
>
> I have done it but:
> -----------
> # fsck -y /
> ** /dev/ad2s1a (NO WRITE)
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> UNREF FILE I=1719827  OWNER=mysql MODE=100600
> SIZE=0 MTIME=Oct  6 12:19 2005
> CLEAR? no
>
> UNREF FILE I=1719847  OWNER=mysql MODE=100600
> SIZE=0 MTIME=Oct  6 12:19 2005
> CLEAR? no
>
> UNREF FILE I=1719855  OWNER=mysql MODE=100600
> SIZE=0 MTIME=Oct  6 12:19 2005
> CLEAR? no
>
> ** Phase 5 - Check Cyl groups
> 405241 files, 14013004 used, 4821771 free (72987 frags,
593598  
> blocks, 0.4% fragmentation)
> mig29# tunefs -n enable /
> tunefs: soft updates cannot be enabled until fsck is
run
> tunefs: /dev/ad2s1a: failed to write superblock
> ------------
>
> Still the same issue.
> Anything else should I do?
>
> Regards,
> Sasa
>
>

_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

On Saturday 08 October 2005 16:02, Gunter Wambaugh wrote:
> Look at the output from fsck.  It very clearly tells
you that it  
> found problems, but didn't fix them (probably because
the partition  
> is mounted).  Notice the following lines:
> ** /dev/ad2s1a (NO WRITE)
> and
> CLEAR? no
> 
> Boot to single user mode and try it again.
> 
> Also, if you add fsck_y_enable="YES" to
rc.conf these should be fixed  
> automatically at boot (IIRC).
> 
> HTH
> 
> On Oct 8, 2005, at 2:32 AM, Sasa Stupar wrote:
> 

It is not fsck that is cousing the trouble but tunefs
itself.

From the man-page you can read:

  The tunefs utility cannot be run on an active file system.
 
  To change an active file system, it must
  be downgraded to read-only or unmounted.

So to change the / partition with tunefs, you have to run
another system wich is not using that / partition.
( for instance with the fix-it cdrom )
Or you can, as the manual says, mount it read-only.
I never tried that, but maybe it will work. 


_______________________________________________
freebsd-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

--On 8. oktober 2005 9:02 -0500 Gunter Wambaugh
<unixgeeksix-two.net> 
wrote:

> Look at the output from fsck.  It very clearly tells
you that it  found
> problems, but didn't fix them (probably because the
partition  is
> mounted).  Notice the following lines:
> ** /dev/ad2s1a (NO WRITE)
> and
> CLEAR? no
>
> Boot to single user mode and try it again.
>
> Also, if you add fsck_y_enable="YES" to
rc.conf these should be fixed
> automatically at boot (IIRC).
>
> HTH
>


Thanx for the tip.

Sasa