On Sat, 15 Aug 2009 01:48:27 -0400
grarpamp grarp...@gmail.com wrote:
Wanted to put in a suggestion. Users are constantly confused and
asking questions about the FreeBSD version naming scheme, somehow
not quite picking it up right, which is which, where to use it,
etc.
And though I know
In message d2e731a10908142248o6ee77e1ie89a62f3c0937...@mail.gmail.com,
grarpamp (grarp...@gmail.com) wrote:
[...]
uname: '7.2-STABLE #0 date of compile' isn't quite the same solid
reference as RELENG_7 as of yesterdays code. Which is what it is,
not the zero-eth 7.2
Hi,
STABLE and CURRENT could only point to two things and there were about
10 potential tags involved.
Tags... You say tags. Now, freebsd is an constantly evolving project. It's
never finished. And when a branch is, it's EOL.
It took me two minutes, back in 97 to get the grasp and at that
I am now trying to rsync large files from the 320GB gmirror+gjournal device to
the 2nd 1TB gmirror+gjournal device. Using gstat I see the 320GB device active
all the time while the 1TB device loads in spurts. There will be periods of
multiple seconds where the target providers are completely
I was checking sysctl and noticed skipped_byes, alloc_failures,low_mem all
increasing on geom.journal.
$sysctl -a | grep geom
kern.geom.collectstats: 1
kern.geom.debugflags: 0
kern.geom.label.debug: 0
kern.geom.mirror.sync_requests: 2
kern.geom.mirror.disconnect_on_failure: 1
Dan Allen wrote:
I cvsup and build RELENG_7 many times a week. This has served me well
(except for the ZFS boot problem I had that went in and was backed out)
for quite a while.
I like to track a STABLE release. When BSD 7 went to 7.1 and to 7.2, it
all just happened automatically with
Jeff,
On 15 aug 2009, at 05:04, Jeff Richards wrote:
(da6:umass-sim6:6:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0
0 0
...
I've had lots of stability issues with USB drives until I added some
quirks to prevent the SYNCHRONIZE CACHE from happening. For example:
Index:
