On 2021-May-16 11:48:24 +1000, Peter Jeremy via freebsd-stable
wrote:
>I am running 13-stable from a couple of weeks ago, without Capsicum
>(neither CAPABILITY_MODE nor CAPABILITIES are specified in my kernel).
>Despite this, I am getting Capsicum-related errors. As an example:
&g
psicum, there's no
way to change the processes capabilities.
--
Peter Jeremy
signature.asc
Description: PGP signature
On 2021-May-06 19:07:23 -0400, monochrome wrote:
...
>On 5/6/21 7:49 AM, Peter Jeremy via freebsd-stable wrote:
...
>> server% tail /COPYRIGHT <&-
>> Assertion failed: (procfd > STDERR_FILENO), function service_clean, file
>> /usr/src/lib/libcasper/libcasper/servi
On 2021-May-06 12:59:54 +0200, Mariusz Zaborski wrote:
>Could you provide details how to reproduce this?
>
>On Thu, 6 May 2021 at 12:13, Peter Jeremy via freebsd-stable
> wrote:
>>
>> Since updating from 12-stable to 13-stable, I've found that tail(1)
>> cras
of stdin, stdout and stderr are open. Whilst it
probably doesn't make sense to call tail without stdout open. there's
no obvious reason to require that stdin or stderr must be open.
--
Peter Jeremy
signature.asc
Description: PGP signature
On 2021-Mar-06 10:39:02 -0800, Oleksandr Tymoshenko wrote:
>Peter Jeremy via freebsd-current (freebsd-curr...@freebsd.org) wrote:
>> [Adding arm@ and making it clearer that this is armv8-only]
>>
>> On 2021-Mar-06 20:26:19 +1100, Peter Jeremy
>> wrote:
>> >
[Adding arm@ and making it clearer that this is armv8-only]
On 2021-Mar-06 20:26:19 +1100, Peter Jeremy wrote:
>On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable
> wrote:
>>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>>(releng/13.0-n244592-
On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable
wrote:
>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
>RK3399, arm64) has changed so that a geli-encrypted partition (using
>AES-X
that just talks about AES-GCM,
it does a reasonable job of roto-tilling the entire armv8crypto stack.
I notice that there are a fixes to f76393a6305b that don't seem to
have made it into releng/13.0 and I will continue to investigate.
--
Peter Jeremy
signature.asc
Description: PGP signature
y. I have a FreeBSD test
system that's running ZFS in <1GB RAM and rebuilding itself daily for
multiple years and haven't run into any ZFS corruption issues.
--
Peter Jeremy
signature.asc
Description: PGP signature
TL;DR: Ensure you explicitly destroy all ZFS labels on disused root pools.
On 2020-Jul-19 21:21:02 +1000, Peter Jeremy wrote:
>I'm sending this to -stable, rather than the src groups because I
>don't believe the problem is the commit itself, rather the commit
>has uncover
On 2020-Jul-21 00:47:23 +0300, Konstantin Belousov wrote:
>On Tue, Jul 21, 2020 at 07:20:44AM +1000, Peter Jeremy wrote:
>> On 2020-Jul-19 14:48:28 +0300, Konstantin Belousov
>> wrote:
>> >On Sun, Jul 19, 2020 at 09:21:02PM +1000, Peter Jeremy wrote:
>>
On 2020-Jul-19 14:48:28 +0300, Konstantin Belousov wrote:
>On Sun, Jul 19, 2020 at 09:21:02PM +1000, Peter Jeremy wrote:
>> I'm sending this to -stable, rather than the src groups because I
>> don't believe the problem is the commit itself, rather the commit
>>
ut haven't dug into it).
Does anyone have any ideas?
--
Peter Jeremy
signature.asc
Description: PGP signature
4GB RAM without problems.
That said, I notice that the first log file suggests you were building
3 ports in parallel, and each port build was running 3 jobs - that's 9
jobs in parallel on a low-spec CPU with 4 threads. You should limit
the number of CPU-bound processes to the number of
"out of swap space" messages
generally mean that this number is too low, rather than there being a
shortage of swap - particularly if your swap device is rather slow.
--
Peter Jeremy
signature.asc
Description: PGP signature
ING entry says that it's switched from devd to udev. There's no
mention of evdev or that the keycodes have been roto-tilled. It's basically
a vanilla "things have been changed, see the documentation" entry. Given
that entry, it's hardly surprising that people are
blem is that if ntpd decides to switch away from
the clock for any reason (eg a burst of jitter), it may get stuck on
the local clock as it drifts further from "real" time.
--
Peter Jeremy
signature.asc
Description: PGP signature
t's probably not relevant but it would be useful for you to say up front
which ntpd you are having problems with and which version of the port you
have installed.
--
Peter Jeremy
signature.asc
Description: PGP signature
rerunning kldxref (with the clock set correctly).
--
Peter Jeremy
signature.asc
Description: PGP signature
On 2019-Aug-20 14:36:14 +0200, Trond Endrestøl
wrote:
>Maybe NFS is to blame, particularly if file locks cannot be obtained.
Yes, it is. SVN tries to obtain locks, even for read-only commands like
"svn info". My solution is to mount /usr/src with the option "nolockd&q
>root: /etc/rc: WARNING: failed to start unbound
I have seen unbound fail to start for a variety of reasons but in all cases, it
has
written a useful hint to the console. Can you confirm that it's not writing
anything
to your console. Are you able to share your configuration?
--
Peter Je
s built explicitly with ashift=9
* The initial disks reported 512B native (I think this is most likely)
* That version of ZFS was using logical, rather than native blocksize.
My guess (given that only ada1 is reporting a blocksize mismatch) is that
your disks reported a 512B native blocksize. In the abs
kg database, and could also include hardware information.
There's ports/sysutils/bsdstats but I'm not sure how popular that is.
--
Peter Jeremy
signature.asc
Description: PGP signature
ends to cover nearly all 100 cards, yet no
>one (pardon me if I missed those) asks for 10. So how about making this
>proposal cover only 10 cards,
What is the purpose in keeping unused FastEthernet cards in the tree?
>if you can't resist the itch to remove
>something from th
red memory are in use but I can't find anything
in "vmstat -mz" that would explain where it's going.
Does anyone have any suggestions for digging into this?
[1] I get the same behaviour using a VBox instance with similar dimensioning
and the same tuning)
--
Peter Jeremy
signature.asc
Description: PGP signature
On 2018-Feb-18 09:06:38 -0600, Kyle Evans wrote:
>On Sun, Feb 18, 2018 at 3:12 AM, Peter Jeremy wrote:
>> Sometime between r329122 and r329157, my 11-stable i386 box stopped
>> being able to buildworld with a readonly /usr/src. I've been updating
>> regularly but th
e /usr/src/share/mk/bsd.init.mk
/usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk
/usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk
/usr/src/stand/efi/../Makefile.inc /usr/src/stand/efi/../defs.mk
/usr/src/share/mk/src.opts.mk /usr/src/share/mk/bsd.own.mk
/usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd.compiler.mk
/usr/src/share/mk/bsd.subdir.mk'
.PATH='. /usr/src/stand/efi'
*** Error code 1
--
Peter Jeremy
signature.asc
Description: PGP signature
chan right = leftmost;
for (i = 0; i < n; i++) {
left = right;
right = chmake(int, 0);
go(f(left, right));
}
chs(right, int, 0);
i = chr(leftmost, int);
printf("result = %d\n", i);
return 0;
}
server%
--
Peter Jeremy
signature.asc
Description: PGP signature
ons" returns policy was one
of the things that swayed me to try it. It was AUD249 but I've found
something by "Pendo" for AUD229 that looks like it came off the same
production line.
I hadn't realised just how weird the insides of some "PC compatible"
computers had become.
--
Peter Jeremy
signature.asc
Description: PGP signature
On 2017-Mar-25 10:19:57 +1100, Peter Jeremy wrote:
>I've just bought a Unisurf Notebook[1] and am trying to boot it from a
>FreeBSD-11.0-RELEASE-amd64-memstick.img. The boot starts OK but hangs
>whilst probing devices. With safe and verbose enabled, it hangs after
>complainin
point neither Ctrl-Alt-Del nor Ctrl-Alt-Esc have any effect and
the only option is to hold the power button down until it powers off.
Does anyone have any suggestions on troubleshooting?
[1] http://unisurf.com.au/unisurf-14-Notebook.html
--
Peter Jeremy
signature.asc
Description: PGP signature
There is no intention of merge of the removal.
>The stable@ mailing list added for wider audience.
Can I suggest that we put some warnings into the SVr4 image activation
code and MFC that to at least 11 to try and smoke out anyone who might
actually be using it.
--
Peter Jeremy
signature.asc
D
On 2016-Nov-22 10:07:49 +, Pete French wrote:
>to another machine and trying to import the pools causes an instant panic.
Can you provide details of the panic, please.
--
Peter Jeremy
signature.asc
Description: PGP signature
Have you done any ZFS tuning?
Could you try installing ports/sysutils/zfs-stats and posting the output
from "zfs-stats -a". That might point to a bottleneck or poor cache
tuning.
--
Peter Jeremy
signature.asc
Description: PGP signature
thout my init!
Uptime: 55s
Changing serial settings was 0/0 now 3/0
Start bios (version 1.7.2-20150226_170051-google)
gce1$ uname -a
FreeBSD gce1.rulingia.com 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #83 r306704M:
Thu Oct 6 13:22:27 AEDT 2016
r...@gce1.rulingia.com:/usr/obj/usr/src/sys/GCE amd64
I haven't investigated the cause yet.
--
Peter Jeremy
signature.asc
Description: PGP signature
ly to date) without problem.
--
Peter Jeremy
signature.asc
Description: PGP signature
On 2016-Jun-03 22:12:55 +0700, Eugene Grosbein wrote:
>> all your media content is valid. I've also had bad experiences with
>> gmirror volumes silently getting out of sync on a crash.
>
>
>gmirror or (gmirror+gjournal) ones?
Plain gmirror.
--
Peter Jeremy
sign
ng RAID of any sort under ZFS defeats a lot of the smarts
in ZFS. In particular, you can no longer rely on scrub verifying that
all your media content is valid. I've also had bad experiences with
gmirror volumes silently getting out of sync on a crash.
--
Peter Jeremy
signature.asc
Description: PGP signature
mstat -mz" when the
system is running normally and as the non-ARC wired memory increases to
identify where the RAM is going.
--
Peter Jeremy
signature.asc
Description: PGP signature
ole so I can't
do anything other than reboot at this point.
(This is 10-stable/amd64 r295088).
If I have some spare time, I'll try reproducing this in a local VBox over
the next few days.
--
Peter Jeremy
signature.asc
Description: PGP signature
sounds like you may need to explicitly reduce vfs.zfs.arc_max (note
that this is a soft limit).
You might like to install sysutils/zfs-stats and do some ZFS tunung.
--
Peter Jeremy
signature.asc
Description: PGP signature
my initial suspicion is ZFS,
though I haven't identified any smoking gun.
Unfortunately, GCE only offers read access to the console, so I can't
use DDB to poke around after it wedges.
--
Peter Jeremy
signature.asc
Description: PGP signature
better. IMHO, this sort of
alamist message should only be output if there is no decent entropy
source available when the random device is unblocked.
--
Peter Jeremy
signature.asc
Description: PGP signature
being used for?
I don't think this can be trivially done. "procstat -v" will show
the number of resident pages within each swap-backed region, any
pages in that region that have been touched but are not resident
are on the swap device but any pages that have never been touched
aren
On 2015-Jul-13 04:31:40 +1000, Peter Jeremy wrote:
>>The import of 4.2.8p2 several months ago resulted in complete failure of
>>timekeeping on all my arm systems. Just last week I tracked it down to
>>a kernel bug (which I haven't committed the fix for yet). While th
ions that trigger the bug or the kernel bug itself? A quick search
failed to find anything.
--
Peter Jeremy
pgpN60GLK7zew.pgp
Description: PGP signature
is still "install $bar from ports".
That's a non-answer. It just changes the question to "why bother to
include $bar in base when I need to install the port anyway".
--
Peter Jeremy
pgpKqgl4dmmHG.pgp
Description: PGP signature
x27; in /boot/loader.conf and post
(or make available) the dmesg from a verbose boot.
--
Peter Jeremy
pgp18RHROUkCO.pgp
Description: PGP signature
n: UFS for a root filesystem is guaranteed to work
>without any fiddling about and, barring drive failures or controller
>issues, is (again, my opinion) a lot more risk-free than ZFS-on-root.
AFAIK, you can't boot from anything other than a single disk (ie no
graid).
--
Peter Jeremy
pgp7H3m449swl.pgp
Description: PGP signature
fs send is a stream of bytes that you can treat
as you would any other stream of bytes. But this approach isn't
recommended.
--
Peter Jeremy
pgp61ijyBCuu8.pgp
Description: PGP signature
lieve it has bugs, feel free to
submit PRs. If the bugs don't affect the base system, they are unlikely
--
Peter Jeremy
pgpzlf8YtE7jb.pgp
Description: PGP signature
ch the head of pre-configured branches. The only
way to get an older tree is to not apply deltas (ZFS snapshots are
the best work-around here).
--
Peter Jeremy
pgpbZzqAVCO6F.pgp
Description: PGP signature
etches new deltas and runs
>svnsup-apply. New trees are "bootstrapped" from other sources,
>e.g. weekly tarballs (still to be developed).
I think you've just re-invented CTM. Before spending too much more
time on svnsup, I suggest you read ctm(1).
--
Peter Jeremy
pgpfk7Isksqu6.pgp
Description: PGP signature
t
that most people who currently use c[v]sup could readily migrate to
using ctm.
See http://www.freebsd.org/doc/handbook/ctm.html for details.
Note that mirroring the actual SVN repo via ctm requires some patches.
There is a README and patches in ftp://ftp.freebsd.org/pub/FreeBSD/CTM/svn-
nches
in any case).
CVS is (and will remain) available in ports (devel/cvs).
--
Peter Jeremy
pgp0orRYshWTs.pgp
Description: PGP signature
ssage buffer. Should be N * pagesize.
options MSGBUF_SIZE=40960
--
Peter Jeremy
pgpwUscTboaAO.pgp
Description: PGP signature
>
>No, svn created the directory. I moved /usr/ports out of the way and ran
>'svn co'.
Can you give the exact steps (including commands) you performed?
--
Peter Jeremy
pgpkZK9jxVe7D.pgp
Description: PGP signature
On 2012-Nov-02 09:30:04 -, Steven Hartland wrote:
>From: "Peter Jeremy"
>> Many years ago, I wrote a simple utility that fills a raw disk with
>> a pseudo-random sequence and then verifies it. This sort of tool
>
>Sounds useful, got a link?
Sorry, no. I
mfi on tbolt 2208 based cards before).
There has been a recent thread about various strange behaviours from
LSI controllers and it has been stated that (at least for the 2008)
the card firmware _must_ match the FreeBSD driver version. See
http://lists.freebsd.org/pipermail/freebsd-stable/2012-August
adata updates (stop scrubs, delete
files, etc) even when it is "full" but I have seen reports of this not
working correctly in the past. A truncate-in-place may work.
You could also try asking on zfs-disc...@opensolaris.org
--
Peter Jeremy
pgptbOF1VVAh4.pgp
Description: PGP signature
.
>Since I switch to HPET, it hasn't happened at all in the last 3 days..
That suggests that there's something peculiar about your TSC. There
are a variety of possibilities... Does your CPU support multiple
Cx states and are you using them ("sysctl dev.cpu | grep cx_")?
--
Peter Jeremy
pgpeGw8Kk7Rhc.pgp
Description: PGP signature
[Moving to -stable and adding jhb@ for his input]
On 2012-Aug-29 11:32:44 +0200, Gustau Pérez i Querol
wrote:
>Al 29/08/2012 11:02, En/na Peter Jeremy ha escrit:
>> On 2012-Aug-28 11:44:44 +0200, Gustau Pérez i Querol
>> wrote:
>>>I'm running FreeBSD 9.1 R
ee (without needing
to install subversion). Failing that, csup should probably also go.
--
Peter Jeremy
pgpNb5AENPidH.pgp
Description: PGP signature
stigating fixes to
libedit but do not have a solution yet. There is a possibility that
sh(1) is relying on bugs in the old libedit.
At this stage, it seems likely that the libedit update (r237738)
will be reverted for 9.1-RELEASE.
--
Peter Jeremy
pgpUCwQdtnSJm.pgp
Description: PGP signature
On 2012-Jul-04 20:03:32 +1000, Peter Jeremy wrote:
>I've recently updated a box from 8-stable to 9-stable/amd64 (r237995),
>compiled with gcc, and now sh(1) exits if I change the window size
>(ssh'ing to the target system within an xterm). I don't recall ever
>se
66 sh RET close 0
1766 sh CALL exit(0)
Does this ring any bells with anyone?
--
Peter Jeremy
pgp5N9G6c8SWr.pgp
Description: PGP signature
en logging out of
X. This is with X.Org X Server 1.10.6 and a "ATI Radeon HD 2400 Pro"
on 8-STABLE r235229. The problem seems to go away after a couple of hours.
--
Peter Jeremy
pgpiZRKfLAQrH.pgp
Description: PGP signature
ake (and any other build
infrastructure it needs) for RELENG_6_4 or later and run "make" in
that directory. You could even grab the files from the 6.4-RELEASE
src install bundle on an FTP site.
--
Peter Jeremy
pgpF0FRK4GTke.pgp
Description: PGP signature
r auto-tuning.
I'd strongly recommend against running ZFS on i386 as anything other
than an experiment.
--
Peter Jeremy
pgpsJbLUQk3mc.pgp
Description: PGP signature
re absorbed by vm.v_cache_min and vm.v_free_reserved in
the first instance. The current vfs.zfs.arc_max default may be a bit
high for some workloads but at this point in time, you will need to
tune it manually.
--
Peter Jeremy
pgpb0kzq1SDsY.pgp
Description: PGP signature
side of the "each FS does its own caching" in that the caches
are all separate and need careful integration into the VM subsystem to
prevent starvation (eg past problems with UFS starving ZFS L2ARC).
--
Peter Jeremy
pgpa3o0LQ2kfG.pgp
Description: PGP signature
like the RAM layout when a SB1500 has 2GB RAM. There's
no problem with 1GB or 4GB RAM. The OP has created sparc64/164227
--
Peter Jeremy
pgpg7mKRrjkxp.pgp
Description: PGP signature
are not listed in
http://www.freebsd.org/platforms/sparc.html
and it's likely that they aren't supported.
>Is there any work around/solution for this issue ?
If you wanted to assist with support for the M3000, I suggest you
start a thread on freebsd-sparc64.
--
Peter Jeremy
pgpsIPp38DaXh.pgp
Description: PGP signature
in posted, the SO had to decide between two unpalatable options
and, IMHO, he made the correct decision. The details and fixes are
now available - it's up to you to weigh up the risks of patching vs
the risks of not patching.
--
Peter Jeremy
pgpwPaYsswqdf.pgp
Description: PGP signature
ng holiday period)
but I think the SO made the right call. Hopefully, this was all that
was holding up 9.0-RELEASE and RE will be giving us a more welcome
Xmas present.
--
Peter Jeremy
pgpJ5YZU425S5.pgp
Description: PGP signature
inal result.
>A PR has been submitted.
sparc64/163460 for the record. Thank you for tracking that down.
--
Peter Jeremy
pgp7m3HL1diGx.pgp
Description: PGP signature
pseudo-random pattern and then verify).
--
Peter Jeremy
pgpo8PkzVBfqo.pgp
Description: PGP signature
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
(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
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
by the local OS rep (this was a Motorola SVR2).
--
Peter Jeremy
pgp9GiYFCh7fP.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
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
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
_hal", rather than the hardware-specific HAL fix the problem?
--
Peter Jeremy
pgpL0aiDu3NMN.pgp
Description: PGP signature
picture of the screen showing the issue).
--
Peter Jeremy
pgptX1VTtosbn.pgp
Description: PGP signature
; 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
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
rg/dokuwiki/doku.php/zfsraid
Note that, even for a home system, backups are worthwhile. In my
case, I backup onto a 2TB disk in an eSATA enclosure. That's
currently (just) adequate but I'll soon need to identify data that I
can leave off that backup.
--
Peter Jeremy
pgpOSt5NCO7Do.pgp
Description: PGP signature
everal
incompatible ways) but none actually work. A quick look at -current
suggests that the situation there remains equally broken.
Has anyone else tried to use any of this? And would anyone be interested
in trying to make it actually work?
--
Peter Jeremy
pgpVVITD1dFyb.pgp
Description: PGP signature
bout ½day tracking that down - not helped by the
lack of any documentation or a useful error message (though there is a
comment in the code when you eventually track it down).
--
Peter Jeremy
pgpObQwMbJjKU.pgp
Description: PGP signature
intensive than UFS and a more powerful
CPU may help - especially if you want gzip compression and/or sha256
checksumming.
--
Peter Jeremy
pgpRE0BXxVZbL.pgp
Description: PGP signature
which is a known issue with ZFS.
--
Peter Jeremy
pgp9CvWOJe1I9.pgp
Description: PGP signature
aditional info I'll give it all, just ask.
What is the SVN revision of a kernel that works?
What is the SVN revision of a kernel that fails?
Can you please post a verbose dmesg of a successful boot.
Can you please post a dmesg of an unsuccessful boot (see above).
--
Peter Jeremy
pgpHUhVzb3Hvu.pgp
Description: PGP signature
_free_count);
at the top of the function. This fixes the worst bug but there are
lots of other fixes if you upgrade.
--
Peter Jeremy
pgpMi5QjNUH8u.pgp
Description: PGP signature
On 2010-Nov-28 02:24:21 -0600, Adam Vande More wrote:
>On Sun, Nov 28, 2010 at 1:26 AM, Peter Jeremy wrote:
>> Since all the boinc processes are running at i31, why are they impacting
>> a buildkernel that runs with 0 nicety?
>
>With the setup you presented you're goin
TNESS and WITNESS_SKIPSPIN, 8GB RAM, src and obj
are both on ZFS.
--
Peter Jeremy
pgpTYgNUsxZxp.pgp
Description: PGP signature
On 2010-Nov-24 11:07:23 +0100, Alexander Leidinger
wrote:
>Quoting Peter Jeremy (from Wed, 24 Nov 2010
>06:32:07 +1100):
>
>> BTW, the entire export is performed at the current compression level -
>> recompressing existing data.
>
>Are you sure the compression is do
on import.
BTW, the entire export is performed at the current compression level -
recompressing existing data.
--
Peter Jeremy
pgpJ45k6nVaUR.pgp
Description: PGP signature
1 - 100 of 639 matches
Mail list logo
