Lion-O <nosp@m.catslair.org> writes:

>That or a "mount -o remount,ro /var" are possible candidates to prevent
>filesystem access while the fsck can do its work. I think it might be able to
>repair things because fsck will access the device and not so much the
>filesystem.

"ro" remounts do not work.


You can always boot with -mmilestone=none and you'll be left with
only "/".

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Cactus Paul <dufus@dumbdown.com> wrote:
>> What control do you want? You can always do 'fsck -n' on a live
>> filesystem because it won't do anything behind the mount point's back.
>> If the fsck at boot time fails (or runs into serious issues), it will
>> fail and drop you at a prompt where you can run it yourself.

> Full control. fsck -n won't do what I want. If fsck has a problem at boot,
> it will determine if the problem is serious enough to warrant stopping. It
> does have problems and is not dropping me out because it is not serious
> enough to prevent mounting.

I guess I missed that you were still having problems. What problems are
happening that the boot fsck isn't picking up?

>> The command itself is used as part of the checkfs() function defined in
>> /sbin/rcS. I suppose you could modify that if you wanted to (although I
>> get a bit nervous modifying things that run before a single-user
>> prompt).

> I can't find any function checkfs() in /sbin/rcS.
> Modifying these scripts doesn't sound like a "correct method" for what I
> want to do..

>> ufs) foptions="-o p"

> Doesn't sound like a great idea, but where is it anyway?

Sorry. That was the pre-10 location. For 10, it's in
/lib/svc/share/fs_include.sh

>> If you really want to, do a 'boot -b' and you'll stop the boot before

> I can't find this option either.

Hmm. I didn't realize that was gone from 10 also. There's no milestone
which corresponds to the old -b stopping point. I'll have to see how
that might be possible...

--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

Casper H.S. Dik <Casper.Dik@sun.com> wrote:
> You can always boot with -mmilestone=none and you'll be left with
> only "/".

Ahh, thanks. That's what I was thinking of in my other post. I didn't
see an explicit milestone like that on the system, and I didn't realize
you could ask for 'none'.

--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

Casper H.S. Dik wrote:

> Lion-O <nosp@m.catslair.org> writes:
>
>
>>That or a "mount -o remount,ro /var" are possible candidates to prevent
>>filesystem access while the fsck can do its work. I think it might be able to
>>repair things because fsck will access the device and not so much the
>>filesystem.
>
>
> "ro" remounts do not work.
>
>
> You can always boot with -mmilestone=none and you'll be left with
> only "/".
>
> Casper

That's good to know. Thanks.

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.

OK! This looks good. And worked too. Looks like I have a lot to learn
about this milestone stuff.


"Darren Dunham" <ddunham@redwood.taos.com> wrote in message
news:sZwvf.10576$oW.4642@newssvr11.news.prodigy.co m...
> Casper H.S. Dik <Casper.Dik@sun.com> wrote:
>> You can always boot with -mmilestone=none and you'll be left with
>> only "/".
>
> Ahh, thanks. That's what I was thinking of in my other post. I didn't
> see an explicit milestone like that on the system, and I didn't realize
> you could ask for 'none'.
>
> --
> Darren Dunham ddunham@taos.com
> Senior Technical Consultant TAOS http://www.taos.com/
> Got some Dr Pepper? San Francisco, CA bay area
> < This line left intentionally blank to confuse you. >