able
via public IP. All the IPs are defined in rc.conf the normal _alias way.
FIB support as I remember needs a custom kernel - not sure about 9, this
is in 8.2.
I even run openbsd spamd on the host and using FIBs to start the spamd
daemon via a 'setfib 1' wrapper script:
%cat /usr/loc
sdpkg:#grep -R packages-9 *
add/main.c: { 90, 900499, "/packages-9.0-release" },
add/main.c: { 90, 999000, "/packages-9-current" },
They haven't updated main.c for -stable yet and -stable is at 900500 per
sys/sys/param.h [or URL]. I'm
md child (perl5.8.8)
the read ignores all white space...the last variable in that 'while read'
will hold everything beyond it...
ie;
poshta:$ps axuww| while read USER PID CPU MEM VSZ RSS TT STAT STARTED
TIME; do echo $PID $CPU $USER $TIME;done |head -3
PID %CPU USER TIME COMMAND
11 77.9 ro
ATING?view=markup
It just confused me for awhile after I did a 'svn up' and did not see the
release notes...
[for the 7.X series, both stable/ and release/ mention the release in
UPDATING]
]Peter[
___
freebsd-stable@freebsd.o
as I try to get a Windows VM running on there, and it starts using
some swap, anywhere from 20MB to 150MB it eventually panics [usually
within an hour or so].
Any ideas ? hardware issues?
Anyone successfull in running several VMs on FreeBSD -> VirtualBox ?
[overlo
Hi,
when creating partitions directly adjacent without a safety free space
between them, the kernel may crash.
Does anybody know how big that free space needs to be?
How I found out (and how to reproduce the crash):
https://forums.freebsd.org/threads/create-degraded-raid-5-with-2-disks-on-fr
Trying to compile my custom kernel in Rel. 11.3 results in this:
[code]--- kernel.full ---
linking kernel.full
atomic.o: In function `atomic_add_64':
/usr/obj/usr/src/sys/E1R11V1/./machine/atomic.h:629: multiple definition of
`atomic_add_64'
opensolaris_atomic.o:/usr/src/sys/cddl/contrib/opensola
> Trying to compile my custom kernel in Rel. 11.3 results in this:
>
> -- kernel.full ---
> linking kernel.full
> atomic.o: In function `atomic_add_64':
> /usr/obj/usr/src/sys/E1R11V1/./machine/atomic.h:629: multiple definition of
> `atomic_add_64'
> opensolaris_atomic.o:/usr/src/sys/cddl/contrib
Hi Hans Petter,
glad to read You! :)
On Thu, Jul 25, 2019 at 09:39:26AM +0200, Hans Petter Selasky wrote:
! On 2019-07-25 01:00, Peter wrote:
! >> The offending feature is either
! >> options ZFS
! >> or
! >> device dtrace
! >> (Adding any of these to the
Hi @all,
I felt the need to look into my ZFS ARC, but DTRACE provided misleading
(i.e., wrong) output (on i386, 11.3-RELEASE):
# dtrace -Sn 'arc-available_memory { printf("%x %x", arg0, arg1); }'
DIFO 0x286450a0 returns D type (integer) (size 8)
OFF OPCODE INSTRUCTION
00: 29010601ldg
On Mon, 02 Dec 2019 21:58:36 +0100, Mark Johnston
wrote:
The DTRACE_PROBE* macros cast their parameters to uintptr_t, which
will be 32 bits wide on i386. You might be able to work around the
problem by casting arg0 to uint32_t in the script.
Thanks for the info - good that it has a logical e
On Fri, 06 Dec 2019 06:21:04 +0100, O'Connor, Daniel
wrote:
vm.pmap.pti="0"# Disable page table isolation
hw.ibrs_disable="1"# Disable Indirect Branch Restricted Speculation
hw.mds_disable="0" # Disable Microarchitectural Data Sampling flush
hw.vmm.vmx="1" # Don't flus
pgrp = getpid();
if(setpgid(0, pgrp) < 0)
err(1, "setpgid");
This appears to me a program trying to deemonize itself (in the old style
when there was only job control but no session management).
In the case this program is already properly daemonized, e.g. by starting
it from
On Wed, 18 Dec 2019 17:22:16 +0100, Karl Denninger
wrote:
I'm curious if anyone has come up with a way to do this...
I have a system here that has two pools -- one comprised of SSD disks
that are the "most commonly used" things including user home directories
and mailboxes, and another that
On Mon, 06 Jan 2020 01:10:57 +0100, Christoph Moench-Tegeder
wrote:
When a program is invoked via /usr/sbin/daemon, it should already be
session leader AND group leader, and then the above code WOULD be a
NOOP, unless POSIX would require the setpgid() to fail and thereby the
program to abort
> Not much room to argue?
Why that? This is not about laws you have to follow blindly whether
you understand them or not, this is all about an Outcome - a working
machine that should properly function.
"Not much to argue about what behaviour is required by the standard".
The standard could have
I met an Issue:
When I kldload jedec_dimm durig runtime, it works just as expected,
and the DIMM data appears in sysctl.
But when I do
* load the jedec_dimm at the loader prompt, or
* add it to loader.conf, or
* compile it into a custom kernel,
it does not boot anymore.
My custom kernel doe
Front up: I do not like loadable modules. They are nice to try
something out, but when you start to depend on some dozen loaded
modules, debugging becomes a living hell: say you hunt some spurious
misbehaviour and compare logfiles with those from four weeks ago,
you will not know exactly which modu
On Wed, Mar 04, 2020 at 11:41:22PM +0300, Yuri Pankov wrote:
! On 04.03.2020 19:09, Peter wrote:
! > When I kldload jedec_dimm durig runtime, it works just as expected,
! > and the DIMM data appears in sysctl.
! >
! > But when I do
! > * load the jedec_dimm at the loader prompt,
Hi all,
my machine should use about 3-4, maybe 5 GB swapspace. Today I found
it suddenly uses 8 GB (which is worryingly near the configured 10G).
I stopped all the big suckers - nothing found.
I stopped all the jails - no success.
I brought it down to singleuser: it tried to swapoff, but failed.
On Tue, Sep 22, 2020 at 12:33:19PM -0400, Mark Johnston wrote:
! On Tue, Sep 22, 2020 at 06:08:01PM +0200, Peter wrote:
! > my machine should use about 3-4, maybe 5 GB swapspace. Today I found
! > it suddenly uses 8 GB (which is worryingly near the configured 10G).
! >
! > I sto
I think I can reproduce the problem now. See below.
On Tue, Sep 22, 2020 at 02:09:01PM -0400, Mark Johnston wrote:
! On Tue, Sep 22, 2020 at 07:31:07PM +0200, Peter wrote:
! > There is something, and I don't know who owns that:
! > $ vmstat -m | grep shmfd
! > shmf
On Wed, Sep 23, 2020 at 12:03:32AM +0300, Konstantin Belousov wrote:
! On Tue, Sep 22, 2020 at 09:11:49PM +0200, Peter wrote:
! > So what happens then is this:
! >
! > $ file scc.e
! > scc.e: ELF 32-bit LSB executable, Intel 80386, version 1
! > (FreeBSD), dynamically linked, inter
Hi all,
I was forced to upgrade 11.4 -> 12.2, as QT5 reqires openssl 1.1.1.
I did a full rebuild from source as of this:
12.2-RC2 FreeBSD 12.2-RC2 #11 r366648M#N1055:1078
(local patches applied - some published via sendbug 10 or 12 years ago)
I did a full rebuild of ALL ports from source, a
After upgrading 11.4 -> 12.2, cpuset now behaves rather different:
# cpuset -C -p NNN
11.4: a new set is created with all cpu enabled, and the process
is moved into that set, with the thread mask unchanged.
12.2: nothing is done, but an error raises if threadmask == setmask.
# cpuset -l
Hiya,
after upgrading 11.4 -> 12.2, I get this error:
> sysctl: unknown oid 'vm.pageout_wakeup_thresh' at line 105
How do I adjust the paging now? The ARC is much too small:
Mem: 1929M Active, 109M Inact, 178M Laundry, 1538M Wired, 37M Buf, 88M Free
ARC: 729M Total, 428M MFU, 154M MRU, 196K An
After clean upgrade (from source) from 11.4 to 12.2-p1 my jails do
no longer work correctly.
Old-fashioned jails seem to work, but most are VIMAGE+NETGRAPH style,
and do not work properly.
All did work flawlessly for nearly a year with Rel.11.
If I start 2-3 jails, and then stop them again, the
Stopping a VIMAGE+Netgraph jail in 12.2 in the same way as it
did work with Rel. 11.4, crashes the kernel after 2 or 3 start/stop
iterations.
Specifically. this does not work:
exec.poststop = "/usr/sbin/ngctl shutdown ${ifname1l}:";
Also this new option from Rel.12 does not work either, it j
Hi Kristof,
it's great to read You!
On Mon, Dec 07, 2020 at 09:11:32PM +0100, Kristof Provost wrote:
! That smells a lot like the epair/vnet issues in bugs 238870, 234985, 244703,
! 250870.
epair? No. It is purely Netgraph here.
! I pushed a fix for that in CURRENT in r368237. It’s schedul
On Tue, Dec 08, 2020 at 04:50:00PM +0100, Kristof Provost wrote:
! Yeah, the bug is not exclusive to epair but that’s where it’s most easily
! seen.
Ack.
! Try
http://people.freebsd.org/~kp/0001-if-Fix-panic-when-destroying-vnet-and-epair-simultan.patch
Great, thanks a lot.
Now I have bad news
Here is the next funny crashdump - I obtained this one twice
and also the sysctl_rtsock() again.
I can reproduce this by just starting and stopping a most simple jail
that does only
exec.start = "/bin/sleep 4 &";
(And as usual, when I let it time out, nothing bad happens.)
Fatal trap 9:
On Tue, Dec 08, 2020 at 08:02:47PM +0100, Kristof Provost wrote:
! > Sorry for the bad news.
! >
! You appear to be triggering two or three different bugs there.
That is possible. Then there are two or three different bugs in the
production code.
In any case, my current workaround, i.e. delayi
On Tue, Dec 08, 2020 at 07:51:07PM -0600, Kyle Evans wrote:
! You seem to have misinterpreted this; he doesn't want to narrow it
! down to one bug, he wants simple steps that he can follow to reproduce
Maybe I did misinterpret, but then I don't really understand it.
I would suppose, when testing
On Wed, Dec 09, 2020 at 02:00:37PM +1100, Dewayne Geraghty wrote:
! On a jail with config:
! exec.start = "/bin/sh -x /etc/rc";
! exec.stop = "/bin/sh /etc/rc.shutdown";
! exec.clean;
!
! test_prod { jid=7; persist; ip4.addr =
! "10.0.7.96,10.0.5.96,127.0.5.96"; devfs_ruleset = "6";
! host.hostu
details to follow
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Details:
After upgrading 2 machines from 9.3 to 10.3-STABLE, on one of them the
l2arc stays empty (capacity alloc = 0), although it is online and gets
accessed. It did work well on 9.3.
I did the following tests:
* Create a zpool on a stick, with two volumes: one filesystem and one
cache. The
sendbug seems not to work anymore, I end up on websites with marketing-
babble and finally get asked to provide some login and passwd. :(
But the former mail looks like having come back to me, so it seems I'm
still allowed to post here...
*** sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c
Pete French wrote:
Ok, thats a bit worry if true - but I can confirm that l2arc works fine
under 10.3 on amd64, so what you say about cross-compling might be true.
Am taking an inetrest in this as I have just dpeloyed a lot of machines
which are going to be relying on l2arc working to get reasob
Andrea Venturoli wrote:
Hello.
Last week I upgraded a 9.3/amd64 box to 10.3: since then, it crashed and
rebooted at least once every night.
Hi,
I have quite similar issue, crash dumps every night, but then my
stacktrace is different (crashing mostly in cam/scsi/scsi.c), and my
env is also q
Eugene M. Zheganin wrote:
Hi.
I have FreeBSD 10.2-STABLE r289293 (but I have observed this situation
on different releases) and a zfs. I also have one directory that used to
have a lot of (tens of thousands) files. I surely takes a lot of time to
get a listing of it. But now I have 2 files and a
Eugene Grosbein wrote:
Hi!
Recently I've upgraded one of my server running 9.3-STABLE with jail containing
4.11-STABLE system.
The host was source-upgraded upto 10.3-STABLE first and next to 11.0-STABLE
and jail configuration migrated to /etc/jail.conf. The jail kept intact.
"service jail star
I observe a strange reading of the ZFS memory stats:
Mem: 298M Active, 207M Inact, 446M Wired, 10M Cache, 91M Buf, 29M Free
ARC: 339M Total, 8758K MFU, 43M MRU, 52K Anon, 35M Header, 40M Other
Swap: 2441M Total, 402M Used, 2040M Free, 16% Inuse
Usually I perceived the "Total" value being approx.
Question: how to get ZFS l2arc working on FBSD 10.3 (RELENG or STABLE)?
Problem using 10.3 RELENG:
When ZFS is called the first time after boot, it will delete all device
nodes of the drive carrying l2arc. ZFS itself will access it's slices
by a "diskid/" string, but all other access is impossib
FYI, please check if reproducible and/or issue:
Installed this from SVN & local build:
11.1-BETA1 FreeBSD 11.1-BETA1 #0 r319858:319867M ... amd64
Then tried to update lsof-4.90.f,8 and got this error:
cc -pipe -DNEEDS_BOOL_TYPEDEF -DHASTASKS -DHAS_PAUSE_SBT
-DHASEFFNLINK=i_effnlink -DHASF_V
Larry Rosenman wrote:
Current lsof is 4.90M.
Ack, that does.
Larry
Sysutils/lsof maintainer
On 6/14/17, 8:13 AM, "Peter" wrote:
FYI, please check if reproducible and/or issue:
Installed this from SVN & local build:
11.1-BETA1 FreeBSD 11.1-BETA1 #0 r
After upgrading to 11.1-RELEASE, a new line appears in the output of
"top" which contains rubbish:
> last pid: 10789; load averages: 5.75, 5.19, 3.89up 0+00:34:46
03:23:51
> 1030 processes:9 running, 1004 sleeping, 17 waiting
> CPU 0: 16.0% user, 0.0% nice, 78.7% system, 4.9% interru
After upgrading 11.0-RELEASE-p10 to 11.1-RELEASE I suddenly see a huge
amount of kstat.zfs.misc.arcstats.l2_cksum_bad (nearly 2% of
kstat.zfs.misc.arcstats.l2_hits).
I have set
> vfs.zfs.compressed_arc_enabled="0"
in loader.conf. When removing this, the errors are gone. It seems that
option is
Glen Barber wrote:
On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote:
After upgrading to 11.1-RELEASE, a new line appears in the output of "top"
which contains rubbish:
last pid: 10789; load averages: 5.75, 5.19, 3.89up 0+00:34:46
03:23:51
1030 processes:9 running, 100
Glen Barber wrote:
On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote:
After upgrading to 11.1-RELEASE, a new line appears in the output of "top"
which contains rubbish:
last pid: 10789; load averages: 5.75, 5.19, 3.89up 0+00:34:46 03:23:51
1030 processes:9 running, 100
Glen Barber wrote:
On Fri, Jul 28, 2017 at 07:04:51PM +0200, Peter wrote:
Glen Barber wrote:
On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote:
After upgrading to 11.1-RELEASE, a new line appears in the output of "top"
which contains rubbish:
last pid: 10789; load avera
This is mostly for the search engines, so others running into it may
find it easier to solve.
While updating some ports via "portupgrade", I got this panic:
Panic String: acl_from_aces: a_type is 0x4000
The phenomen was reproducible; it appeared while creating a backup
package from the "gl
Eugene M. Zheganin wrote:
Hi,
On 05.08.2017 22:08, Eugene M. Zheganin wrote:
pool: userdata
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise re
Just found that my scripts that would detect image types by means of the
"file" command do not work anymore in RELEASE-11. :(
Whats happening in R11.1 is this:
$ scanimage > /tmp/SCAN
$ file /tmp/SCAN
/tmp/SCAN: data
While on R10 in looked this way, which appears slightly more useful:
$ scani
For a long time already, I get these strange messages whenever building
a port:
pkg: Bad argument on pkg_set 2143284626
Today I looked into it, and found it is easily reproducible:
# pkg audit whatever
pkg: Bad argument on pkg_set 2143284618
0 problem(s) in the installed packages found.
#
Loo
Occasionally I noticed that the system would not quickly process the
tasks i need done, but instead prefer other, longrunning tasks. I
figured it must be related to the scheduler, and decided it hates me.
A closer look shows the behaviour as follows (single CPU):
Lets run an I/O-active task, e.
George Mitchell wrote:
On 04/04/18 06:39, Alban Hertroys wrote:
[...]
That said, SCHED_ULE (the default scheduler for quite a while now) was designed
with multi-CPU configurations in mind and there are claims that SCHED_4BSD
works better for single-CPU configurations. You may give that a try,
Stefan Esser wrote:
I'm guessing that the problem is caused by kern.sched.preempt_thresh=0, which
prevents preemption of low priority processes by interactive or I/O bound
processes.
For a quick test try:
# sysctl kern.sched.preempt_thresh=1
Hi Stefan,
thank You, thats an interesting knob!
Hi Alban!
Alban Hertroys wrote:
Occasionally I noticed that the system would not quickly process the
tasks i need done, but instead prefer other, longrunning tasks. I
figured it must be related to the scheduler, and decided it hates me.
If it hated you, it would behave much worse.
Thats enco
Andriy Gapon wrote:
On 04/04/2018 03:52, Peter wrote:
Lets run an I/O-active task, e.g, postgres VACUUM that would
continuousely read from big files (while doing compute as well [1]):
Not everyone has a postgres server and a suitable database.
Could you please devise a test scenario that
Andriy Gapon wrote:
Not everyone has a postgres server and a suitable database.
Could you please devise a test scenario that demonstrates the problem and that
anyone could run?
Alright, simple things first: I can reproduce the effect without
postgres, with regular commands. I run this on my d
Eugene Grosbein wrote:
I see no reasons to use SHED_ULE for such single core systems and use SCHED_BSD.
Nitpicking: it is not a single core system, it's a dual that for now is
equipped with only one chip, the other is in the shelf.
But seriously, I am currently working myself through the de
Julian Elischer wrote:
for a single CPU you really should compile a kernel with SMP turned off
and 4BSD scheduler.
ULE is just trying too hard to do stuff you don't need.
Julian,
if we agree on this, I am fine.
(This implies that SCHED_4BSD will *not* be retired for an indefinite time!)
I te
Hi all,
in the meantime I did some tests and found the following:
A. The Problem:
---
On a single CPU, there are -exactly- two processes runnable:
One is doing mostly compute without I/O - this can be a compressing job
or similar; in the tests I used simply an endless-loop. Lets ca
I forgot to attach the commands used to create the logs - they are ugly
anyway:
[1]
dtrace -q -n '::sched_choose:return { @[((struct thread
*)arg1)->td_proc->p_pid, stringof(((struct thread
*)arg1)->td_proc->p_comm), timestamp] = count(); } tick-1s { exit(0); }'
| sort -nk 3 | awk '$1 > 27 {$
Hi Stefan,
I'm glad to see You're thinking along similar paths as I did. But let
me fist answer Your question straight away, and sort out the remainder
afterwards.
> I'd be interested in your results with preempt_thresh set to a value
> of e.g.190.
There is no difference. Any value above 7
Results:
1. The tdq_ridx pointer
The perceived slow advance (of the tdq_ridx pointer into the circular
array) is correct behaviour. McKusick writes:
The pointer is advanced once per system tick, although it may not
advance on a tick until the currently selected queue is empty. Since
each th
EBFE via freebsd-stable wrote:
On Tue, 17 Apr 2018 09:05:48 -0700
Freddie Cash wrote:
# Tune for desktop usage
kern.sched.preempt_thresh=224
Works quite nicely on a 4-core AMD Phenom-II X4 960T Processor
(3010.09-MHz K8-class CPU) running KDE4 using an Nvidia 210 GPU.
For interactive tasks
Hi all of You,
thank You very much for Your commenting and reports!
From what I see, we have (at least) two rather different demands here:
while George looks at the over-all speed of compute throughput, others
are concerned about interactive response.
My own issue is again a little bit dif
Release/update 11.1-p8 introduced so-called "mitigation for speculative
execution vulnerabilities".
In RElease 11.2 these "mitigation" have been removed. What is the reason
for the removal, and specifically why is Security advisory 18:03 still
mentioned in the release notes?
Behaviour with 1
--- Renato Botelho <[EMAIL PROTECTED]> wrote:
> I'm trying to use pf + ftp-proxy n a 6.1-PRERELEASE machine.
>
> I have this line on inetd.conf:
>
> ftp-proxy stream tcp nowait root/usr/libexec/ftp-proxy
>
> ftp-proxy -n
>
> And this lines on pf.conf:
>
> rdr on $int_if proto
ith kind regards,
Peter Batenburg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
ll about.
I'm also happy to patch the code but feel that both PXE and BOOTP should
be consistent and I'm not sure which is the correct approach.
>BTW, it would be kind if the line in the pxeboot(8):
> As PXE is still in its infancy ...
>can be changed :-)
Well, there ar
; and/or setting POSIXLY_CORRECT.
This is part of the GNU/FSF "lockin" policy that encourages people
to use their non-standard extensions to ensure that you don't have
any choice other than to use their software.
--
Peter Jeremy
pgpd7zj0Dn2kG.pgp
Description: PGP signature
picture of the screen showing the issue).
--
Peter Jeremy
pgptX1VTtosbn.pgp
Description: PGP signature
_hal", rather than the hardware-specific HAL fix the problem?
--
Peter Jeremy
pgpL0aiDu3NMN.pgp
Description: PGP signature
On 2011-Mar-05 11:48:54 +0200, Kostik Belousov wrote:
>On Sat, Mar 05, 2011 at 07:50:05PM +1100, Peter Jeremy wrote:
>> I have a Atheros AR5424 and so, based on the 8.2-STABLE i386 NOTES
>> and some rummaging in the sources, I tried to build a kernel with:
>>
>&g
Hello
I'm trying to enable C3 states to allow TurboBoost on RELENG_8_2 and
dmesg is throwing a lot of t_delta too short messages while using boot
-v.
This platform is 2x Xeon E5620 Gulftown quad core 2.4ghz CPUs on
whatever boards Dell ships them on these days (probably Intel X58
derivative.)
Kern
ng
http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/010862.html
(note that mailman has split it into at least 3 threads).
--
Peter Jeremy
pgpQGveibDZlq.pgp
Description: PGP signature
e have about 55 modem ports over ten 8-port Xr cards (PCI) that connect
>remote sites via dial-up.
I've only got access to PCI Xem cards that are used for serial console
concentration so it would be useful for you to test both the Xr cards
and dial-in support.
--
Peter Jeremy
pgpjTK58Q
if nothing
happens for hours the buffer isn't released..
My machine was still running 8.2-PRERELEASE so I am upgrading.
I am happy to give information gathered on old/new kernel if it helps.
Regards
Peter
Quoting "Scott Sipe" :
On Jul 2, 2011, at 12:54 AM, jhell wrote:
Hi all,
just as an addition: an upgrade to last Friday's FreeBSD-Stable and to
VirtualBox 4.0.8 does not fix the problem.
I will experiment a bit more tomorrow after hours and grab some statistics.
Regards
Peter
Quoting "Peter Ross" :
Hi all,
I noticed a similar problem l
Scott
On Jul 5, 2011, at 3:00 AM, Peter Ross wrote:
Hi all,
just as an addition: an upgrade to last Friday's FreeBSD-Stable
and to VirtualBox 4.0.8 does not fix the problem.
I will experiment a bit more tomorrow after hours and grab some statistics.
Regards
Peter
Quoting "Pete
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 12:23:39PM +1000, Peter Ross wrote:
Quoting "Jeremy Chadwick" :
>On Tue, Jul 05, 2011 at 01:03:20PM -0400, Scott Sipe wrote:
>>I'm running virtualbox 3.2.12_1 if that has anything to do with it.
>&
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 01:07:53PM +1000, Peter Ross wrote:
Quoting "Jeremy Chadwick" :
>On Wed, Jul 06, 2011 at 12:23:39PM +1000, Peter Ross wrote:
>>Quoting "Jeremy Chadwick" :
>>
>>>On Tue, Jul 05, 2011
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 01:54:12PM +1000, Peter Ross wrote:
Quoting "Jeremy Chadwick" :
>On Wed, Jul 06, 2011 at 01:07:53PM +1000, Peter Ross wrote:
>>Quoting "Jeremy Chadwick" :
>>
>>>On Wed, Jul 06, 2011 at 1
Quoting "Peter Ross" :
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 01:54:12PM +1000, Peter Ross wrote:
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 01:07:53PM +1000, Peter Ross wrote:
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 20
Quoting "Peter Ross" :
Quoting "Peter Ross" :
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 01:54:12PM +1000, Peter Ross wrote:
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 01:07:53PM +1000, Peter Ross wrote:
Quoting "Jeremy Cha
Quoting "Scott Sipe" :
On Wed, Jul 6, 2011 at 4:21 AM, Peter Ross
wrote:
Quoting "Peter Ross" :
Quoting "Peter Ross" :
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 01:54:12PM +1000, Peter Ross wrote:
Quoting "Jeremy Chadwick&
by the local OS rep (this was a Motorola SVR2).
--
Peter Jeremy
pgp9GiYFCh7fP.pgp
Description: PGP signature
Quoting "Peter Ross" :
Quoting "Scott Sipe" :
On Wed, Jul 6, 2011 at 4:21 AM, Peter Ross
wrote:
Quoting "Peter Ross" :
Quoting "Peter Ross" :
Quoting "Jeremy Chadwick" :
On Wed, Jul 06, 2011 at 01:54:12PM +1000, Peter Ross wrote:
understand; I think I can recall reading about issues
>with the 915 chipset. I agree a "check, don't assume" warning is
>reasonable.
I have also run into problems (wouldn't POST from memory) trying to
use a NIC in the x16 slot of Dell GX620 boxes, which use an i945
chipset.
--
Peter Jeremy
pgpxVKRjcgfQY.pgp
Description: PGP signature
(including Solaris) behave badly in this scenario but
4.4BSD derivatives will release unused space at the end of a directory
and have smarts to more efficiently skip unused entries at the start
of a directory.
--
Peter Jeremy
pgpmdeH6w8Ny5.pgp
Description: PGP signature
Hi All
I just ran freebsd-update to upgrade from 7.0 to 7.4 I figured
everything went ok. This is what I did.
1. freebsd-update upgrade -r 7.4-RELEASE
2. freebsd-update install
3. shutdown -r now
4. freebsd-update install
5. shutdown -r now
The system came back up ok but now if I run another
t for visible bad sectors (and Solaris UFS still reserves
space for this, though I don't know if it still works) but the code
was removed from FreeBSD long ago.
AFAIR, wd(4) supported bad sectors but it was removed long ago.
--
Peter Jeremy
pgpzqxeB9mDZP.pgp
Description: PGP signature
pseudo-random pattern and then verify).
--
Peter Jeremy
pgpo8PkzVBfqo.pgp
Description: PGP signature
udp6 0 0 *.123 *.*
Thanks!
--
Peter Olssonp...@leissner.se
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
--
Pete
First post failed, because the attachment was too big. (Or maybe you got
a copy anyway since you are also in the To)
Here it is again:
On 10/21/2011 01:32 PM, Peter Maloney wrote:
> On 10/21/2011 01:04 PM, Steven Hartland wrote:
>> - Original Message - From: "Peter Malo
run script
#!/usr/local/bin/bash
#
# Author: Peter Maloney
# Purpose: try to crash ZFS by doing IO and renaming snapshots
#
# Result: it crashes every system I put it on, as long as there is a
zvol in the pool
dataset=tank
count=0
nextprint=$(date +%s)
while true; do
echo Snapshot
zfs
On 21 October 2011 16:00, wrote:
>
> ...snip...
>
> Both connections were using the same (short) Cat5 cable, I tried two
> different ports on the 10/100 hub, and other systems work OK on that
> 10/100 hub.
>
> How do I get this interface to operate properly at 100MB?
>
>
...snip...
"Auto-negotia
1 - 100 of 1261 matches
Mail list logo
