>From: "Benjamin P. Grubin" <[EMAIL PROTECTED]>
>Date: Thu, 5 Jul 2001 19:46:54 -0400

>As of a month ago or so, there was some discussion that concluded it was
>unsafe to enable softupdates on a root partition.  Is it safe to go back in
>the water there, now?

Well, despite the warnings, I've been running with soft updates turned
on for each UFS on my laptop; although there were some cases (around 5
or 6 weeks ago, if my time sense isn't totally screwed up) where
-CURRENT wouldn't stay up, and fsck was doing some Very Unpleasant
Things, I was able to cope OK.

However, I've configured the laptop in what is arguably a rather
peculiar way:  I can boot from any of 3 slices, each of which has its
own / and /usr.  (/var is common to all, and /usr/local, as well as
/home and /cvs are all symlinks in each to a common file system.)
Regardless of which slice is booted, each slice's file systems are
mounted and visible.  There's more detail about that stuff at

I've been running the box this way since early March, and have -STABLE
(from different days, or with other differences, such as experimental
code) on the 1st 2 slices, and -CURRENT on the 3rd.  I've been tracking
each of -STABLE and -CURRENT daily (modulo a few cases where I couldn't
build -CURRENT a while back).

Thus, I have some levels of fallback that a more conventional layout might
not have.  (I also have some additional exposure, since a
suitably-corrupted "fsck" could trash everything.)  But one of my purposes
here is to try things out & try to help identify (& fix) any problems I
see....  :-}

m147[1] uname -a
FreeBSD m147.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #60: Thu Jul  5 09:27:4
9 PDT 2001     [EMAIL PROTECTED]:/common/C/obj/usr/src/sys/LAPTOP_30W  i386
m147[2] df -k
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/ad0s3a    158783    79807    66274    55%    /
devfs               1        1        0   100%    /dev
/dev/ad0s1a    158783    41766   104315    29%    /S1
/dev/ad0s1e   1870791   791927   929201    46%    /S1/usr
/dev/ad0s2a    158783    41839   104242    29%    /S2
/dev/ad0s2e   1870791   813249   907879    47%    /S2/usr
/dev/ad0s3e   1870751   767973   953118    45%    /usr
/dev/ad0s3g   1016303    32365   902634     3%    /var
/dev/ad0s3h  10277074  5458487  3996422    58%    /common
procfs              4        4        0   100%    /proc
/dev/md10c     520140      444   478088     0%    /tmp
m147[3] swapinfo
Device          1K-blocks     Used    Avail Capacity  Type
/dev/ad0s3b       1048448     4688  1043760     0%    Interleaved
m147[4] mount
/dev/ad0s3a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local)
/dev/ad0s1a on /S1 (ufs, local, soft-updates)
/dev/ad0s1e on /S1/usr (ufs, NFS exported, local, soft-updates)
/dev/ad0s2a on /S2 (ufs, local, soft-updates)
/dev/ad0s2e on /S2/usr (ufs, NFS exported, local, soft-updates)
/dev/ad0s3e on /usr (ufs, NFS exported, local, soft-updates)
/dev/ad0s3g on /var (ufs, local, soft-updates)
/dev/ad0s3h on /common (ufs, NFS exported, local, soft-updates)
procfs on /proc (procfs, local)
/dev/md10c on /tmp (ufs, local, soft-updates)
m147[5] sudo boot0cfg -v ad0
#   flag     start chs   type       end chs       offset         size
1   0x00     73:  0: 1   0xa5    349:239:63      1103760      4188240
2   0x00    350:  0: 1   0xa5    626:239:63      5292000      4188240
3   0x80    627:  0: 1   0xa5   1023:239:63      9480240     29589840
4   0x00      0:  1: 1   0xa0     72:239:63           63      1103697

version=1.0  drive=0x80  mask=0x7  ticks=182
default_selection=F3 (Slice 3)

David H. Wolfskill                              [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to