On 11/15/05, Jonathan Adams <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 15, 2005 at 08:06:06PM -0500, Dennis Clarke wrote:
> > On 11/15/05, Jonathan Adams <[EMAIL PROTECTED]> wrote:
> > > On Tue, Nov 15, 2005 at 04:49:31PM -0500, Dennis Clarke wrote:
> > > > On 11/15/05, Sean Wilcox <[EMAIL PROTECTED]> wrote:
> > > > > The Statement that the FILE SYSTEM IS BAD is probably a little too
> > > > > harsh
> > > > > but the FS INCONSISTENT statement could be true.
> > > >
> > > You can always boot with '-m milestone=none', and run fsck from that
> > > environment; the root filesystem will be mounted read-only.
> >
> > Hold on .. do you mean from the ok prompt ?
> >
> > ok boot -m milestone=none
> >
> > as opposed to
> >
> > ok boot -sv
> >
> > hmmm fascinating ... let me try that right now.
>
> Yes; it's a completely minimal boot, with nothing but init(1M),
> svc.startd(1M),
> svc.configd(1M), and sulogin(1M) running. When you are ready to bring
> the system up, you can do:
>
> # svcadm milestone all
hmmm cool. I really have to take a pile of my old tools in sysadmin
life and toss them over my shoulder and check out all these new
functions and features.
> and exit the shell (or keep the shell, and watch the system come up
> by running svcs(1) over and over again). The console login prompt won't
> appear until you exit your shell.
Okay .. I'm going to try that in a very experimental kind of way.
Also .. I just noticed something else. I need to recreate my
filesystems after running analyze and thus when I went to newfs my
/dev/rdsk/c0t0d0s0 I noticed a new option or two that was not there
before :
# newfs -?
usage: newfs [ -v ] [ mkfs-options ] raw-special-device
where mkfs-options are:
-N do not create file system, just print out parameters
-T configure file system for eventual growth to over a terabyte
-s file system size (sectors)
-b block size
-f frag size
-t tracks/cylinder
-c cylinders/group
-m minimum free space %
-o optimization preference (`space' or `time')
-r revolutions/minute
-i number of bytes per inode
-a number of alternates per cylinder
-C maxcontig
-d rotational delay
-n number of rotational positions
-S print a textual version of the calculated superblock to stdout
-B dump a binary version of the calculated superblock to stdout
Hmmm a -S option and a -B optiion for dumping the superblock data ?
Let me give that a whirl :
# newfs -s 1048572 -b 8192 -f 1024 -m 10 -i 2048 -S /dev/rdsk/c0t0d0s0
newfs: construct a new file system /dev/rdsk/c0t0d0s0: (y/n)? y
0x0 sblock.fs_link
0x0 sblock.fs_rolled
0x10 sblock.fs_sblkno
0x18 sblock.fs_cblkno
.
.
.
0x0 sblock.fs_sparecon[49]
0x0 sblock.fs_sparecon[50]
0x0 sblock.fs_version
0x0 sblock.fs_logbno
0x0 sblock.fs_reclaim
0x0 sblock.fs_sparecon2
0x38ac117c sblock.fs_state
0xffbffbc000000000 sblock.fs_qbmask
0xffbffbb800000000 sblock.fs_qfmask
0x1 sblock.fs_postblformat
0x8 sblock.fs_nrpos
0x35c sblock.fs_postbloff
0x560 sblock.fs_rotbloff
0x11954 sblock.fs_magic
fsirand: Not a file system (bad magic number in superblock)
/usr/sbin/fsirand /dev/rdsk/c0t0d0s0: failed, status = 256
#
That seemed to generate an error of some sort there. I'll try the old
fashioned method :
# newfs -s 1048572 -b 8192 -f 1024 -m 10 -i 2048 /dev/rdsk/c0t0d0s0
newfs: construct a new file system /dev/rdsk/c0t0d0s0: (y/n)? y
/dev/rdsk/c0t0d0s0: 1048572 sectors in 292 cylinders of 27 tracks,
133 sectors
512.0MB in 19 cyl groups (16 c/g, 28.05MB/g, 13504 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 57632, 115232, 172832, 230432, 288032, 345632, 403232, 460832, 518432,
576032, 633632, 691232, 748832, 806432, 864032, 921632, 979232, 1036832,
#
yep .. okay.
Once I have my filesystems restored I will then experiment with these
new boot options!
Dennis
ps: I love experimenting with new things like this.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
