Re: Poudriere failed to build pkg in 13-stable jail under 12-stable

2021-01-28 Thread Ronald Klop

On Mon, 25 Jan 2021 05:46:43 +0100, Thomas Legg  wrote:


The build of a 13-stable source and kernel were a success under 12-stable
(though with some issues on freeze-ups and hard reboots that I suspect
might be related to the bufdaemon issue and my 0x15 gen AMD cpu).

Created a 13-stable poudriere jail with the knowledge that there may be
issues with builds under a 12-stable r369076 kernel. I didn't expect this
failure on packaging pkg.

> Compressing man pages (compress-man)
===>   Installing ldconfig configuration file
===
===>

===>  Building package for pkg-1.16.2
cp: /wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg/pkg-1.16.2.txz: Function  
not

implemented
*** Error code 1



cp in 13-stable uses the system call copy_file_range which is not in the  
12-stable kernel.
In general running newer code (13) on older kernel (12) is unsupported.  
Version 12 is not forwards compatible.


Regards,
Ronald.





Stop.
make[1]: stopped in /usr/ports/ports-mgmt/pkg
*** Error code 1

Stop.
make: stopped in /usr/ports/ports-mgmt/pkg
=>> Cleaning up wrkdir
===>  Cleaning for pkg-1.16.2
build of ports-mgmt/pkg | pkg-1.16.2 ended at Mon Jan 25 12:16:12 HKT  
2021

build time: 00:02:01
!!! build failure encountered !!!
___
freebsd-curr...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to  
"freebsd-current-unsubscr...@freebsd.org"

___
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"


Re: How to handle the pack files now we have switched to git?

2021-01-05 Thread Ronald Klop


Van: Pete French 
Datum: dinsdag, 5 januari 2021 12:08
Aan: FreeBSD Stable Mailing List 
Onderwerp: How to handle the pack files now we have switched to git?


So, for me the switch to git went very smoothly. I havent moved to etcupdate 
yet, but will probably do that soon. Hopwever I did hit one issue. What I do is 
to build on a single machine, and then send that to a number of places using 
rsync.

But what seems to happen wuth git is that it has a big pack file of objects, 
and the name of the opack file is the SHA1 of whatever is inside it. So if 
something chnages then the filename chnages - and thus rsync tries to move the 
entire lot all over again, even if the change is tiny.

Does anyone have a solution to this ? Currently I am telling rsync to ignore 
.git when it sends the source, but am not entirely happy with that.

But apart from that, git works fine ;)

-pete.
___
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"






Why are you not happy with ignoring .git? It sounds like a pretty reasonable 
thing to do for your setup.
Otherwise (if you keep the .git dir) there is nothing you can do about this 
(AFAIK) and you will rsync quite some data now and then.

Regards,
Ronald.

___
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"


Re: 12.2-STABLE: Commit 367740 breaks IMAP/SMTP server authentication

2020-11-22 Thread Ronald Klop
On Sun, 22 Nov 2020 14:37:33 +0100, Michael Grimm   
wrote:



Hi,

I am running 12.2-STABLE and VNET jails, one of which host a recent  
Dovecot IMAP and a recent postfix SMTP server. Authentication is forced  
via TLS/SSL for both services (ports 587 and 993). Setup is as follows:


extIF0/pf/NAT <—> epairXa (bridge0) epairXb <-> jail

A recent upgrade broke mailing of IMAP clients running at macOS 10.14.6  
(Mojave) und AVM's push service (Fritzbox), but *not* for IMAP clients  
running at macOS 10.15.7 (Catalina). Strange.


Findings at macOS 10.14.6 (examplified for IMAP):

1)  mac$ nc -4vw 1 mail.xyz.zzz 993
found 0 associations
found 1 connections:
1:  flags=82
outif en0
src 1.2.3.4 port 49583
dst 11.22.33.44 port 993
rank info not available
TCP aux info available

Connection to mail.xyz.zzz port 993 [tcp/imaps] succeeded!

2)  mac$ openssl s_client -crlf -connect mail.xyz.zzz:993 -debug
CONNECTED(0005)
write to 0x7fa32ef01ae0 [0x7fa33080a803] (200 bytes => 200 (0xC8))
 - 16 03 01 00 c3 01 00 00-bf 03 03 32 f7 fe fa b4 ...2
0010 - e8 9a 60 38 ef 34 99 70-84 ce dc 1a 08 b8 76 90   ..`8.4.p……v.
	0020 - 19 8c 81 f4 a6 37 19 37-09 70 6f 00 00 60 c0 30
.7.7.po..`.0
	0030 - c0 2c c0 28 c0 24 c0 14-c0 0a 00 9f 00 6b 00 39
.,.(.$...k.9

0040 - cc a9 cc a8 cc aa ff 85-00 c4 00 88 00 81 00 9d   ….
	0050 - 00 3d 00 35 00 c0 00 84-c0 2f c0 2b c0 27 c0 23
.=.5./.+.'.#
	0060 - c0 13 c0 09 00 9e 00 67-00 33 00 be 00 45 00 9c
...g.3...E..

0070 - 00 3c 00 2f 00 ba 00 41-c0 11 c0 07 00 05 00 04   .<./...A……..
0080 - c0 12 c0 08 00 16 00 0a-00 15 00 09 00 ff 01 00   ….
0090 - 00 36 00 0b 00 02 01 00-00 0a 00 08 00 06 00 1d   .6..
00a0 - 00 17 00 18 00 23 00 00-00 0d 00 1c 00 1a 06 01   .#……….
00b0 - 06 03 ef ef 05 01 05 03-04 01 04 03 ee ee ed ed   ….
00c0 - 03 01 03 03 02 01 02 03-  

hanging at that stage forever
	(and client complaining of its inability to authenticate and reports  
timeout after 60 seconds)



I did identify commit 367740 being responsible for that:

mike>svn up -r 367740
Updating '.':
Usys/netinet/ip_fastfwd.c
Usys/netinet/ip_input.c
Usys/netinet/ip_var.h
 U   .
Updated to revision 367740.


Any Ideas, especially why clients at different OS behave different?

FYI: I do have no access to AVM's push service, and very limited access  
to the macOS 10.14.6 computer.


Thanks in advance and with kind regards,
Michael

P.S. How may I update a local svn copy and simultaneously omit commit  
367740 from being applied, or how may I revert commit 367740, only?



From the top of my head you can do something like:

Assuming your svn checkout is in /usr/src:
cd /usr/src
svn up
svn diff -c -367740 | patch

This will get the reverse of commit 367740 (because of the -) and patch  
the code with it.


Regards,
Ronald.
___
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"


Re: kqueue and NFS

2020-11-11 Thread Ronald Klop

Hi,

I don't think NFS has the possibility to push notifications about changes in 
the filesystem to the clients. NFSv3 is stateless so the server does not even 
know about the clients. NFSv4 I don't know much about, but I have never heard 
of notifications.

So for NFS kqueue would only trigger if the change is on the same client as 
where the kqueue is lurking.

Otherwise you could run some daemon on the server which pushes the notifications out of band 
of the NFS protocol to the clients. Which probably gives interesting results together with the 
caching of the NFS client. But that is another story we see at work. (postfix -> you have 
mail! -> NFS -> imap -> no you don't -> O yes, you have. :-) )

Regards,
Ronald.


Van: Daniel Braniss 
Datum: woensdag, 11 november 2020 09:40
Aan: sta...@freebsd.org
Onderwerp: kqueue and NFS


Hi,
I have a vague recollection that kqueue does not work for NFS files,
any chance that this will be made possible?

cheers,
danny

___
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"




___
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"


Re: zfs meta data slowness

2020-07-22 Thread Ronald Klop


Van: mike tancsa 
Datum: dinsdag, 21 juli 2020 21:37
Aan: Ronald Klop , FreeBSD-STABLE Mailing List 

Onderwerp: Re: zfs meta data slowness


Hi,
Thanks for the response. Reply in line

On 7/20/2020 9:04 AM, Ronald Klop wrote:
> Hi,
>
> My first suggestion would be to remove a lot of snapshots. But that my
> not match your business case.

As its a backup server, its sort of the point to have all those snapshots.


> Maybe you can provide more information about your setup:
> Amount of RAM, CPU?
64G, Xeon(R) CPU E3-1240 v6 @ 3.70GHz
> output of "zpool status"
# zpool status -x

all pools are healthy
 


That is nice to know.
Instead of zpool status -x, the output of "zpool status" is very interesting. And 
"zpool list" also. That gives the reader information about your setup, which helps 
thinking along about the possible cause.

But as somebody else mentioned. Profiling the kernel might be the best thing to 
do. Dtrace can be used for it. But I don't know these commands by heart.

If I remember correctly there is an optimization for "zfs list -o name". This 
is much faster because it does not get extra information from the disks.
See: https://svnweb.freebsd.org/base?view=revision=230438

Regards,
Ronald.

> 

> output of "zfs list" if possible to share

its a big list

# zfs list | wc
 8244120  107511


> Type of disks/ssds?
old school Device Model: WDC WD80EFAX-68KNBN0
> What is the load of the system? I/O per second, etc.
its not cpu bound, disks are sometimes running at 100% based on gstat,
but not always
> Do you use dedup, GELI?

no and no


> Something else special about the setup.
> output of "top -b"
>

ports are right now being built in a VM, but the problem (zrepl hanging)
and zfs list -t snapshots taking forever happens regardless

  PID USERNAMETHR PRI NICE   SIZERES STATEC   TIMEWCPU
COMMAND
 4439 root 12  40   20  6167M  5762M kqread   3 535:13 200.00% bhyve
98783 root  2  21016M  5136K hdr->b   4   0:01   1.95% zfs
76489 root 21  230   738M54M uwait1   2:18   0.88% zrepl
98784 root  1  21013M  3832K piperd   3   0:01   0.59% zfs
99563 root  1  20013M  4136K zio->i   4   0:00   0.39% zfs
16136 root 18  250   705M56M uwait3  29:58   0.00%
zrepl-freebsd-amd64
 1845 root  1  20012M  3772K nanslp   7   5:54   0.00%
ossec-syscheckd
 1567 root  1  20011M  2744K select   0   2:22   0.00%
syslogd
 1737 root 32  20011M  2844K rpcsvc   6   1:40   0.00% nfsd
 1660 root  1 -52   r011M11M nanslp   5   1:18   0.00%
watchdogd
 1434 root  1  200  9988K   988K select   3   0:27   0.00% devd
 2435 mdtancsa  1  20020M  8008K select   0   0:21   0.00% sshd
 1754 root  3  20018M  3556K select   1   0:11   0.00%
apcupsd
 5917 root  1  20011M  2672K select   2   0:06   0.00%
script
 1449 _pflogd   1  20012M  3572K bpf  3   0:05   0.00%
pflogd

---Mike

> That kind of information.
>
> Regards,
> Ronald.
>
>
> Van: mike tancsa 
> Datum: zondag, 19 juli 2020 16:17
> Aan: FreeBSD-STABLE Mailing List 
> Onderwerp: zfs meta data slowness
>>
>> Are there any tweaks that can be done to speed up or improve zfs
>> metadata performance ? I have a backup server with a lot of snapshots
>> (40,000)  and just doing a listing can take a great deal of time.  Best
>> case scenario is about 24 seconds, worst case, I have seen it up to 15
>> minutes.  (FreeBSD 12.1-STABLE r363078)
>>
>>
>> ARC Efficiency: 79.33b
>> Cache Hit Ratio:92.81%  73.62b
>> Cache Miss Ratio:   7.19%   5.71b
>> Actual Hit Ratio:   92.78%  73.60b
>>
>> Data Demand Efficiency: 96.47%  461.91m
>> Data Prefetch Efficiency:   1.00%   262.73m
>>
>> CACHE HITS BY CACHE LIST:
>>   Anonymously Used: 0.01%   3.86m
>>   Most Recently Used:   3.91%   2.88b
>>   Most Frequently Used: 96.06%  70.72b
>>   Most Recently Used Ghost: 0.01%   5.31m
>>   Most Frequently Used Ghost:   0.01%   10.47m
>>
>> CACHE HITS BY DATA TYPE:
>>   Demand Data:  0.61%   445.60m
>>   Prefetch Data:0.00%   2.63m
>>   Demand Metadata:  99.36%  73.15b
>>   Prefetch Metadata:0.03%   21.00m
>>
>> CACHE MISSES BY DATA TYPE:
>>   Demand Data:  0.29%   16.31m
>>   Pr

Re: zfs meta data slowness

2020-07-20 Thread Ronald Klop

Hi,

My first suggestion would be to remove a lot of snapshots. But that my not 
match your business case.
Maybe you can provide more information about your setup:
Amount of RAM, CPU?
output of "zpool status"
output of "zfs list" if possible to share
Type of disks/ssds?
What is the load of the system? I/O per second, etc.
Do you use dedup, GELI?
Something else special about the setup.
output of "top -b"

That kind of information.

Regards,
Ronald.


Van: mike tancsa 
Datum: zondag, 19 juli 2020 16:17
Aan: FreeBSD-STABLE Mailing List 
Onderwerp: zfs meta data slowness


Are there any tweaks that can be done to speed up or improve zfs
metadata performance ? I have a backup server with a lot of snapshots
(40,000)  and just doing a listing can take a great deal of time.  Best
case scenario is about 24 seconds, worst case, I have seen it up to 15
minutes.  (FreeBSD 12.1-STABLE r363078)


ARC Efficiency: 79.33b
Cache Hit Ratio:92.81%  73.62b
Cache Miss Ratio:   7.19%   5.71b
Actual Hit Ratio:   92.78%  73.60b

Data Demand Efficiency: 96.47%  461.91m
Data Prefetch Efficiency:   1.00%   262.73m

CACHE HITS BY CACHE LIST:
  Anonymously Used: 0.01%   3.86m
  Most Recently Used:   3.91%   2.88b
  Most Frequently Used: 96.06%  70.72b
  Most Recently Used Ghost: 0.01%   5.31m
  Most Frequently Used Ghost:   0.01%   10.47m

CACHE HITS BY DATA TYPE:
  Demand Data:  0.61%   445.60m
  Prefetch Data:0.00%   2.63m
  Demand Metadata:  99.36%  73.15b
  Prefetch Metadata:0.03%   21.00m

CACHE MISSES BY DATA TYPE:
  Demand Data:  0.29%   16.31m
  Prefetch Data:4.56%   260.10m
  Demand Metadata:  95.02%  5.42b
  Prefetch Metadata:0.14%   7.75m


Other than increase the metadata max, I havent really changed any tuneables


ZFS Tunables (sysctl):
kern.maxusers   4416
vm.kmem_size66691842048
vm.kmem_size_scale  1
vm.kmem_size_min0
vm.kmem_size_max1319413950874
vfs.zfs.trim.max_interval   1
vfs.zfs.trim.timeout30
vfs.zfs.trim.txg_delay  32
vfs.zfs.trim.enabled1
vfs.zfs.vol.immediate_write_sz  32768
vfs.zfs.vol.unmap_sync_enabled  0
vfs.zfs.vol.unmap_enabled   1
vfs.zfs.vol.recursive   0
vfs.zfs.vol.mode1
vfs.zfs.version.zpl 5
vfs.zfs.version.spa 5000
vfs.zfs.version.acl 1
vfs.zfs.version.ioctl   7
vfs.zfs.debug   0
vfs.zfs.super_owner 0
vfs.zfs.immediate_write_sz  32768
vfs.zfs.sync_pass_rewrite   2
vfs.zfs.sync_pass_dont_compress 5
vfs.zfs.sync_pass_deferred_free 2
vfs.zfs.zio.dva_throttle_enabled1
vfs.zfs.zio.exclude_metadata0
vfs.zfs.zio.use_uma 1
vfs.zfs.zio.taskq_batch_pct 75
vfs.zfs.zil_maxblocksize131072
vfs.zfs.zil_slog_bulk   786432
vfs.zfs.zil_nocacheflush0
vfs.zfs.zil_replay_disable  0
vfs.zfs.cache_flush_disable 0
vfs.zfs.standard_sm_blksz   131072
vfs.zfs.dtl_sm_blksz4096
vfs.zfs.min_auto_ashift 9
vfs.zfs.max_auto_ashift 13
vfs.zfs.vdev.trim_max_pending   1
vfs.zfs.vdev.bio_delete_disable 0
vfs.zfs.vdev.bio_flush_disable  0
vfs.zfs.vdev.def_queue_depth32
vfs.zfs.vdev.queue_depth_pct1000
vfs.zfs.vdev.write_gap_limit4096
vfs.zfs.vdev.read_gap_limit 32768
vfs.zfs.vdev.aggregation_limit_non_rotating131072
vfs.zfs.vdev.aggregation_limit  1048576
vfs.zfs.vdev.initializing_max_active1
vfs.zfs.vdev.initializing_min_active1
vfs.zfs.vdev.removal_max_active 2
vfs.zfs.vdev.removal_min_active 1
vfs.zfs.vdev.trim_max_active64
vfs.zfs.vdev.trim_min_active1
vfs.zfs.vdev.scrub_max_active   2
vfs.zfs.vdev.scrub_min_active   1
vfs.zfs.vdev.async_write_max_active 10

Re: swap space issues

2020-06-26 Thread Ronald Klop


Van: Bob Bishop 
Datum: vrijdag, 26 juni 2020 17:18
Aan: Peter Jeremy 
CC: Donald Wilde , freebsd-stable 

Onderwerp: Re: swap space issues




> On 26 Jun 2020, at 11:23, Peter Jeremy  wrote:
>
> On 2020-Jun-25 11:30:31 -0700, Donald Wilde  wrote:
>> Here's 'pstat -s' on the i3 (which registers as cpu HAMMER):
>>
>> Device  1K-blocks UsedAvail Capacity
>> /dev/ada0s1b 335544320 33554432 0%
>> /dev/ada0s1d 335544320 33554432 0%
>> Total671088640 67108864 0%
>
> I strongly suggest you don't have more than one swap device on spinning
> rust - the VM system will stripe I/O across the available devices and
> that will give particularly poor results when it has to seek between the
> partitions.
 
If you configure a ZFS mirror in bsdinstall you get a swap partition per drive by default.


If you are running on multiple disks (a mirror) it can provide extra speed. The 
example above is on the same disk. On one disk multiple swap partitions will 
only spread the data non-optimal for the heads of the disk.


> 

> Also, you can't actually use 64GB swap with 4GB RAM.  If you look back
> through your boot messages, I expect you'll find messages like:
> warning: total configured swap (524288 pages) exceeds maximum recommended 
amount (498848 pages).
> warning: increase kern.maxswzone or reduce amount of swap.
> or maybe:
> WARNING: reducing swap size to maximum of MB per unit
>
> The absolute limit on swap space is vm.swap_maxpages pages but the realistic
> limit is about half that.  By default the realistic limit is about 4×RAM (on
> 64-bit architectures), but this can be adjusted via kern.maxswzone (which
> defines the #bytes of RAM to allocate to swzone structures - the actual
> space allocated is vm.swzone).
>
> As a further piece of arcana, vm.pageout_oom_seq is a count that controls
> the number of passes before the pageout daemon gives up and starts killing
> processes when it can't free up enough RAM.  "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


--
Bob Bishop   t: +44 (0)118 940 1243
r...@gid.co.uk m: +44 (0)783 626 4518




 



 

___
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"


Re: Buildworld and buildkernel with very slow compilation, recently

2020-06-21 Thread Ronald Klop

Building ports/pkgs is also significantly slower on 13 (new clang) than on 12.1.
http://thunderx1.nyi.freebsd.org/
13 = 140 hours12.1 = 103 hoursFor roughly the same amount of ports.

Regards, Ronald

Van: Michael Grimm 
Datum: 21 juni 2020 14:12
Aan: FreeBSD-STABLE Mailing List 
Onderwerp: Buildworld and buildkernel with very slow compilation, recently




Hi,

I am following FreeBSD 12.1-STABLE. 


Clang has been upgraded to version 10.0.0 on May, 1st, and ever since that 
time, I do observe a dramatic increase in compilation times of building world, 
kernel and ports. I didn't benchmark the exact times, but compilation times are 
at least increased by a factor of 1.5. Nothing has changed of the last month 
besides upgrading 12.1-Stable every other week.

Has anyone else been bitten by this?

Regards,
Michael
___
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"





___
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"


Re: jexec as user?

2019-11-20 Thread Ronald Klop

Yeah, ssh is also possible. See my original mail :-) 
https://lists.freebsd.org/pipermail/freebsd-stable/2019-November/091742.html

I run my jails with "ip4 = inherit;". So I would need to do some 
port-forwarding trickery with ssh on different ports.
The users already login on the host to do various actions. Jailme gives the 
easiest access without to much maintenance for now.

Regards,
Ronald.

Van: Eugene Grosbein 
Datum: woensdag, 20 november 2019 11:44
Aan: Ronald Klop , Miroslav Lachman <000.f...@quip.cz>
CC: Christos Chatzaras , freebsd-stable 

Onderwerp: Re: jexec as user?


20.11.2019 16:47, Ronald Klop wrote:

> Thanks for all the advice. I am indeed looking for using jail from the 
non-root user in the host. Jailme sounds like a good solution.
>
> My use case is providing a relatively save way of giving a user the 
possibility to experiment with root rights (like creating and installing ports) 
without wracking the host system.
> The users are trusted so it is not so much about security. More about keeping 
the host system clean.

You also could run ssh service inside the jail and give users opportunity to 
experiment with ssh and keys :-)
 





___
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"


Re: jexec as user?

2019-11-20 Thread Ronald Klop

Thanks for all the advice. I am indeed looking for using jail from the non-root 
user in the host. Jailme sounds like a good solution.

My use case is providing a relatively save way of giving a user the possibility 
to experiment with root rights (like creating and installing ports) without 
wracking the host system.
The users are trusted so it is not so much about security. More about keeping 
the host system clean.

Regards,
Ronald.

Van: Miroslav Lachman <000.f...@quip.cz>
Datum: dinsdag, 19 november 2019 20:31
Aan: Christos Chatzaras , freebsd-stable 

CC: Ronald Klop 
Onderwerp: Re: jexec as user?


Christos Chatzaras wrote on 2019/11/19 14:09:
>
>
>> On 19 Nov 2019, at 15:02, mike tancsa  wrote:
>>
>> On 11/19/2019 6:42 AM, Ronald Klop wrote:
>>> Hi,
>>>
>>> Is it possible to jexec into a jail as a regular user. Or to enable
>>> that somewhere?
>>> Or is the way to do such a thing to set up ssh in the jail?
>>>
>> On 11.3 at least, does not the built in functionality of jexec do what
>> you need ?
>>
>> jexec [-l] [-u username | -U username] jail [command ...]
>>
>> # jexec -U testuser 3 csh
>> testuser@cacticonsole:/ % id
>> uid=1005(testuser) gid=1005(testuser) groups=1005(testuser)
>> testuser@cacticonsole:/ %
>>
>
> I think he wants to use jexec as a normal user from the main OS.
>
> If he wants to run jexec as root and login to jail as user then your command 
works.

If you want to use jexec as normal user in host, look at sysutils/jailme from 
ports:

https://www.freshports.org/sysutils/jailme/
This version is installed setuid and does some sanity checking to ensure the 
username and UID match between the jail and the host system.

WWW: https://github.com/Intermedix/jailme

Miroslav Lachman

PS: I never used jailme personally




___
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"


jexec as user?

2019-11-19 Thread Ronald Klop

Hi,

Is it possible to jexec into a jail as a regular user. Or to enable that 
somewhere?
Or is the way to do such a thing to set up ssh in the jail?

Regards,
Ronald.
___
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"


Re: pkg thinks kernel is old

2019-10-10 Thread Ronald Klop

This message of pkg is misleading.

It looks at /bin/sh or something like that for the version. And prints that as 
the 'kernel' version. So if you did an incremental build and /bin/sh was not 
changed the version stays the same.
To fix it you can do a clean buildworld/installworld.

Regards,
Ronald.

Van: Bengt Ahlgren 
Datum: woensdag, 9 oktober 2019 23:38
Aan: sta...@freebsd.org
Onderwerp: pkg thinks kernel is old


I've ran into this on my 11.3-STABLE system:

# uname -K
1103500
# pkg update -f
Updating ivyp repository catalogue...
Fetching meta.txz: 100%560 B   0.6kB/s00:01
Fetching packagesite.txz: 100%  410 KiB 419.9kB/s00:01
Processing entries:   0%

Newer FreeBSD version for package zziplib:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1103000
- running kernel: 1102509
Ignore the mismatch and continue? [Y/n]:

I build my own packages with poudriere, and have just switched from an
11.2-REL to an 11.3-REL jail.  I didn't force-upgrade everything after
the switch, perhaps that's needed to make pkg recognise the correct
kernel version?

Bengt
___
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"




___
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"


boot 11.3-BETA1 hangs om armv5

2019-05-27 Thread Ronald Klop
Was running "FreeBSD 11.2-RELEASE-p4 (SHEEVAPLUG) #4 r339336M: Sat Oct 13  
23:31:51 CEST 2018".
Compiled 11.3-BETA1, installed kernel.bin in /boot/msdos and started it.  
Output below. It hangs. I guess in starting the random/entropy stuff.


Any thoughts or advise?
Don't spend to much time on it, I'm happy to phase it out.

Regards,
Ronald.


Rebooting...

 __  __  _ _
|  \/  | __ _ _    _| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|\_/ \___|_|_|
 _   _   _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/|/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Mar 19 2009 - 16:06:59) Marvell version: 3.4.16

U-Boot code: 0060 -> 0067FFF0  BSS: -> 006CEE80

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x   size 256MB
DRAM CS[1] base 0x1000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 4 USB Device(s) found
   scanning bus for storage devices... 1 Storage Device(s) found
reading kernel.bin
.


4345316 bytes read
## Starting application at 0x0090 ...
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.3-BETA1 #0 r348277M: Sun May 26 14:17:08 CEST 2019
builder@rpi3:/data/src/obj-11.3/arm.arm/data/src/11.3/sys/SHEEVAPLUG  
arm
FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM  
8.0.0)

CPU: Feroceon 88FR131 rev 1 (**unknown 4** core)
  Little-endian DC enabled IC disabled WA disabled DC streaming enabled
  BTB disabled L2 enabled L2 prefetch enabled
  WB enabled LABT branch prediction disabled
  16KB/32B 4-way instruction cache
  16KB/32B 4-way write-back-locking-C data cache
real memory  = 536866816 (511 MB)
avail memory = 518778880 (494 MB)
SOC: Marvell 88F6281 rev A0, TClock 200MHz
  Instruction cache prefetch enabled, data cache prefetch enabled
  256KB 4-way set-associative write-through unified L2 cache
random: entropy device external interface
___
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"


Re: FreeBSD 12.0-RC2 Now Available

2018-12-01 Thread Ronald Klop

On Fri, 30 Nov 2018 21:52:59 +0100, Jonathan Chen  wrote:


On Sun, 25 Nov 2018 at 15:06, Glen Barber  wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The second RC build of the 12.0-RELEASE release cycle is now available.

[...]

o 12.0-RC2 aarch64 RPI3


Is wifi working for 12.0/aarch64 RPI3? Or has something changed in  
FreeBSD-12?


# sysctl net.wlan.devices
sysctl: unknown oid 'net.wlan.devices'

What did I miss?

Cheers.



Integrated WiFi of RPI3(+) is not supported. It is connected via the SDIO  
interface which is not implemented on FreeBSD yet.


See https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi for an overview of  
supported devices.


Regards,
Ronald.
___
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"


Re: sudo not available after configuring ipmi serial over lan

2018-11-08 Thread Ronald Klop
On Wed, 07 Nov 2018 23:56:26 +0100, Jordan Caraballo  
 wrote:



Hi guys,

After configuring ipmi serial over lan console, I am not being able to
execute any command related to sudo; not even "sudo su -". I am using  
ttyu0

and COM1 on a Dell R530. Everything regarding receiving output and typing
at the serial console is fine; the only command not working is sudo.



What do you mean by 'not working'? Is there an error message? Does it  
hang? Do you get logged out?


Regards,
Ronald.




Any ideas? Below are the configurations.

/etc/ttys

# Serial terminals
# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
#ttyu0  "/usr/libexec/getty 3wire"  vt100   onifconsole secure
ttyu0   "/usr/libexec/getty std.115200" vt100   on  secure
ttyu1   "/usr/libexec/getty 3wire"  vt100   onifconsole secure
ttyu2   "/usr/libexec/getty 3wire"  vt100   onifconsole secure
ttyu3   "/usr/libexec/getty 3wire"  vt100   onifconsole secure
# Dumb console
dcons   "/usr/libexec/getty std.9600"   vt100   off secure

/boot/loader.conf

# ipmi enabled
ipmi_load="YES"
# ipmi configurations
boot_multicons="YES"
boot_serial="YES"
# serial configurations for COM1
console="comconsole,vidconsole"
comconsole_speed="115200"
comconsole_port="0x3F8"
hint.uart.0.flags="0x00"
hint.uart.2.flags="0x10"


___
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"


Re: 'loadable library and perl binaries are mismatched' rebuilding ports after upgrade to 12.0-BETA2 r339930

2018-10-31 Thread Ronald Klop

On Wed, 31 Oct 2018 11:55:59 +0100, Raúl  wrote:


Hi!

Coming from 11.2p4, using sources, everything went fine and is already
running without noticeable problem. Mariadb101 had some known problem so
after trying well documented workaround on it's rc.d script it finally
get promoted to Mariadb102 ...

*Great work*, version 12 already feels smooth, performant, snappy ...
well rounded.

Before deleting old-libs I tried a 'portmaster -Raf' and there is where
I'm getting into trouble. This installation has survived three server
boxes and in the meantime (since FreeBSD version ~6) lots of big changes
on the ports tree have happened. It has more than 800 ports installed so
it's a bit complex setup. I try everything on this box. Maybe I broke
some port dependencies, or I miss something, I'm not sure. Build fails
for me with:

[]
Dumper.c loadable library and perl binaries are mismatched (got
handshake key 0xd480080, needed 0xe180080)
[]

It can be on Dumper.c, vxs.c ... and others.
No matter how I try always get stuck on this perl mismatch.

I have no ports / portmaster tricks left to try, can anyone give me a  
hint?.



What version of perl is being upgraded to what version?
In /usr/ports/UPDATING there are instructions on how to update perl using  
portmaster.


Regards,
Ronald.




Thanks in advance.

Raúl.
___
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"

___
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"


Re: Failing to retrieve source tarballs for anything.

2018-09-02 Thread Ronald Klop

First guess... Connect a network cable.


Please copy-paste the error message in your mail. It helps people helping you.
Any relevant message in /var/log/messages? 



Regards, 
Ronald.



Sorry for top posting, my mobile mail app does this.


Van: Alex McKeever 
Datum: 01 september 2018 23:06
Aan: Ronald Klop , FreeBSD Stable , 
FreeBSD Current 
Onderwerp: Re: Failing to retrieve source tarballs for anything.





I simply changed directory to which thing I want to compile in /ports, run the 
command make install, and after a short while it fails to retrieve the source 
archive (.tar.gz)


Sent from Yahoo Mail for iPhone


On Saturday, September 1, 2018, 4:56 PM, Ronald Klop  
wrote:


It helps a lot of you send the exact command you run with the error message. Or 
all the significant output.




Regards,
Ronald


Van: Alex McKeever 
Datum: 01 september 2018 19:50
Aan: FreeBSD Stable , FreeBSD Current 

Onderwerp: Failing to retrieve source tarballs for anything.



After compiling PKG, when I go to ports to compile anything (my eMac can run 
FreeBSD but not modern Linux due to the version of the Radeon GPU) it fails to 
retrieve any of the source tarballs for any of the software, desktop 
environments etc. I would like help to fix this, as I’d like to run something 
current.


Sent from Yahoo Mail for iPhone
___
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"









___
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"


Re: Failing to retrieve source tarballs for anything.

2018-09-01 Thread Ronald Klop

It helps a lot of you send the exact command you run with the error message. Or 
all the significant output.




Regards,
Ronald


Van: Alex McKeever 
Datum: 01 september 2018 19:50
Aan: FreeBSD Stable , FreeBSD Current 

Onderwerp: Failing to retrieve source tarballs for anything.




After compiling PKG, when I go to ports to compile anything (my eMac can run 
FreeBSD but not modern Linux due to the version of the Radeon GPU) it fails to 
retrieve any of the source tarballs for any of the software, desktop 
environments etc. I would like help to fix this, as I’d like to run something 
current.


Sent from Yahoo Mail for iPhone
___
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"



___
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"


Re: Two USB 4 disk enclosure and a panic

2018-04-27 Thread Ronald Klop
On Wed, 25 Apr 2018 14:15:03 +0200, Nenhum_de_Nos  
 wrote:



On Mon, April 23, 2018 23:18, Nenhum_de_Nos wrote:

Hi,

I would like to know how to debug this. I have two 4 disk enclosures:

Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure – USB 3.0 & eSATA
(HF2-SU3S2)
NexStar HX4 - NST-640SU3-BK

and both have 4 disk on them, and not all disk are equal.

The issue comes when I plug the probox usb3 enclosure on the system. I
can't even read the /var/log/message, it crashes very quickly.

I can see on the boot process up to the point where the second enclosure
comes to be loaded. The 4 disk are shown on the dmesg/console, and then  
a
core dump happens, the boot process goes to the debug screen and a  
restart

happens like a flash.

The motherboard is a Intel® Desktop Board D525MW running 8GB RAM.
All disk use ZFS, 4 or 5 zpools, one raidz, one mirror and two or three
single disk pools.
FreeBSD xxx 11.1-RELEASE-p7 FreeBSD 11.1-RELEASE-p7 #1 r330596: Thu  
Mar  8

06:45:59 -03 2018 root@xxx:/usr/obj/usr/src/sys/FreeBSD-11-amd64-PF
amd64

The kernel is a slightly modified generic, just to have altq.

How can I debug this? I have no idea. I have to use two machines to run
all those disks, and I would really like to have just one for it.

Can it be the amount of RAM? The other box is and APU2 from PCEngines  
and

have 4GB ram. apu2 uname -a: FreeBSD yyy 11.1-RELEASE-p4 FreeBSD
11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

I tried to plug the Vantec hardware on the apu2 box, but there it would
not panic, but won't load all vantec disks neither. I really run out of
ideas here :(

thanks.

--
"We will call you Cygnus,
the God of balance you shall be."


Hi,

I found some logs on the daily security output:

+ZFS filesystem version: 5
+ZFS storage pool version: features support (5000)
+panic: Solaris(panic): blkptr at 0xf8000b93c848 DVA 1 has invalid  
VDEV 1

+cpuid = 0
+KDB: stack backtrace:
+#0 0x80ab65c7 at kdb_backtrace+0x67
+#1 0x80a746a6 at vpanic+0x186
+#2 0x80a74513 at panic+0x43
+#3 0x82623192 at vcmn_err+0xc2
+#4 0x824a73ba at zfs_panic_recover+0x5a
+#5 0x824ce893 at zfs_blkptr_verify+0x2d3
+#6 0x824ce8dc at zio_read+0x2c
+#7 0x82445fb4 at arc_read+0x6c4
+#8 0x824636a4 at dmu_objset_open_impl+0xd4
+#9 0x8247eafa at dsl_pool_init+0x2a
+#10 0x8249b093 at spa_load+0x823
+#11 0x8249a2de at spa_load_best+0x6e
+#12 0x82496a81 at spa_open_common+0x101
+#13 0x824e2879 at pool_status_check+0x29
+#14 0x824eba3d at zfsdev_ioctl+0x4ed
+#15 0x809429f8 at devfs_ioctl_f+0x128
+#16 0x80ad1f15 at kern_ioctl+0x255
+CPU: Intel(R) Atom(TM) CPU D525   @ 1.80GHz (1800.11-MHz K8-class CPU)
+avail memory = 8246845440 (7864 MB)
+Timecounter "TSC" frequency 1800110007 Hz quality 1000
+GEOM_PART: integrity check failed (ada0s1, BSD)
+GEOM_PART: integrity check failed (diskid/DISK-5LZ0ZDBBs1, BSD)


This error also looks interesting.



+ugen1.2:  at usbus1
+ukbd0 on uhub0
+ukbd0:  on usbus1
+kbd2 at ukbd0
+ZFS filesystem version: 5
+ZFS storage pool version: features support (5000)
+re0: link state changed to DOWN
+uhid0 on uhub0
+uhid0:  on usbus1
+ums0 on uhub0
+ums0:  on usbus1
+ums0: 3 buttons and [XYZ] coordinates ID=0
+re0: promiscuous mode enabled
+re0: link state changed to UP

For what I see can be ZFS related.

If anyone have any hints, please tell :)

I kinda got curious about this:

+ZFS storage pool version: features support (5000)

How can I figure out if my pools are from different versions and may this
be the culprit here?


zpool upgrade [-v]

But I think you can only run this if your machine does not panic. Maybe on  
another machine.


Can you get the output of the coredump? On reboot the /etc/rc.d/savecore  
script will look for a valid core dump in the dumpdev (see /etc/rc.conf,  
/etc/defaults/rc.conf) and write it to /var/crash/. That will contain  
information which can help people debug this.


Regards,
Ronald.




thanks,

matheus

___
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"


portsmon.freebsd.org via freshports?

2018-03-24 Thread Ronald Klop

Hello,

Is portsmon ever coming back?


http://portsmon.freebsd.org/portoverview.py?category=net=samba46
->
"The latest Python updated failed. Repairs are in progress 20171025 -- mcl"

It is referenced from the freshports.org site.
https://www.freshports.org/net/samba46/

I found it a useful tool to see why packages are not available for some  
version.


Regards and thanks for all the work for these services,
Ronald.
___
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"


Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE

2018-02-26 Thread Ronald Klop
On Sun, 25 Feb 2018 16:48:44 +0100, Johannes M Dieterich   
wrote:



Dear all,

Please CC me as I am not subscribed.

On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
report that the graphics/drm-next-kmod port just received an update to
Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent
CURRENT and 11-STABLE.

We have tested this on a range of hardware ourselves:
* Haswell
* Broadwell
* Skylake
* Evergreen
* Kaveri (both radeon and amgpu KMS)
* Carrizo
* Polaris

Needless to say, the possible space of hardware this could run on is
significantly larger. Hence, if you find issues and/or want to propose
patches, please do so at our development github:

https://github.com/FreeBSDDesktop/kms-drm

We absolutely do welcome contributions!

Johannes



Nice work. It might be nice to edit the linux 4,9 reference from pkg-descr.

Regards,
Ronald.
___
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"


Re: Fwd: rpi2 daily run weird output (480.leapfile-ntpd)

2017-11-28 Thread Ronald Klop

The attached diff fixes the issue for me.
NB: The variable is also used in ntpd_precmd() if you used chroot. I guess  
that use case was broken too.


Regards,
Ronald.


On Tue, 28 Nov 2017 21:06:46 +0100, Ronald Klop <ronald-li...@klop.ws>  
wrote:



Ah, it comes from the script after it.

[ronald@rpi2 /etc/periodic/daily]$ ./480.leapfile-ntpd
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
[--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
[-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list]
[--no-sslv3] [--no-tlsv1] [--no-verify-hostname]  
[--no-verify-peer]

[-o file] [--referer=URL] [-S bytes] [-T seconds]
[--user-agent=agent-string] [-w seconds] URL ...
fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
[--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
[-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list]
[--no-sslv3] [--no-tlsv1] [--no-verify-hostname]  
[--no-verify-peer]

[-o file] [--referer=URL] [-S bytes] [-T seconds]
[--user-agent=agent-string] [-w seconds] -h host -f file [-c dir]

Apparently $ntp_tmp_leapfile is empty on this line in /etc/rc.d/ntpd:
 fetch $ntp_leapfile_fetch_opts -o  
$ntp_tmp_leapfile $url && break


[ronald@rpi2 ~]$ sh -x /etc/rc.d/ntpd onefetch

+ fetch -mq -o https://www.ietf.org/timezones/data/leap-seconds.list
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]


The variable $ntp_tmp_leapfile is missing since the fetch method was  
split in r325256.

https://svnweb.freebsd.org/base/stable/11/etc/rc.d/ntpd?r1=325256=325255=325256

Cc-ing the committer.

Regards,

Ronald.


On Tue, 28 Nov 2017 20:34:57 +0100, Ronald Klop <ronald-li...@klop.ws>  
wrote:



Isn't this very weird in the output of last night:
"Checking for rejected mail hosts:
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]"

I don't see yet how the script  
/etc/periodic/daily/460.status-mail-rejects can try to call fetch.


Any thoughts on this?

For the record. I run dma instead of sendmail.
$ cat /etc/mail/mailer.conf
# $FreeBSD: stable/11/libexec/dma/dmagent/mailer.conf 289087 2015-10-09  
22:09:44Z bapt $


sendmail  /usr/libexec/dma
send-mail /usr/libexec/dma
mailq /usr/libexec/dma

on
FreeBSD rpi2 11.1-STABLE FreeBSD 11.1-STABLE #2 r325879: Thu Nov 16  
02:03:21 CET 2017  
root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2  arm


Ronald.



--- Forwarded message ---
From: r...@klop.ws
To: root
Cc:
Subject: rpi2 daily run output
Date: Tue, 28 Nov 2017 03:12:48 +0100


Removing stale files from /var/preserve:

Cleaning out old system announcements:

Removing stale files from /var/rwho:

Removing stale entries from sendmail host status cache:
mailwrapper: no mapping in /etc/mail/mailer.conf

Backup passwd and group files:

Verifying group file syntax:
/etc/group is fine

Backing up mail aliases:

Disk status:
FilesystemSizeUsed   Avail Capacity  Mounted on
/dev/ufs/rootfs   1.8G1.4G242M86%/
devfs 1.0K1.0K  0B   100%/dev
/dev/msdosfs/MSDOSBOOT 50M7.4M 43M15%/boot/msdos
tmpfs 128M628K127M 0%/tmp
/dev/da0s1a14G7.8G4.7G62%/mnt/usbdisk
tmpfs 512M4.0K512M 0%
/var/tmp/ports-build

Network interface status:
NameMtu Network   Address  Ipkts Ierrs Idrop 
Opkts

Oerrs  Coll  Drop
lo0   16384 <Link#1>  lo0  0 0 0
0 0 0 0
lo0   - localhost localhost0 - -
0 - - -
lo0   - fe80::%lo0/64 fe80::1%lo0  0 - -
0 - - -
lo0   - your-net  localhost0 - -
0 - - -
ue01500 <Link#2>  b8:27:eb:77:37:63   581144 0 0
95090 0 0 0
ue0   - 192.168.1.0/2 192.168.1.14895132 - -
84713 - - -

Local system status:
   3:01AM  up 11 days, 11:05, 2 users, load averages: 0.36, 0.09, 0.03

Mail in local queue:
Mail queue is empty

Mail in submit queue:
mailq: invalid arguments

Security check:
  (output mailed separately)

Checking for rejected mail hosts:
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
 [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
 [-i file] [--key=file] [-N file] [--no-passive]  
[--no-proxy=list]
 [--no-sslv3] [--no-tlsv1] [--no-verify-hostname]  
[--no-verify-peer]

 [-o file] [--referer=URL] [-S bytes] [-T seconds]
 [--user-agent=agent-string] [-w seconds] URL ...
 fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
 [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
 [-i 

Re: Fwd: rpi2 daily run weird output (480.leapfile-ntpd)

2017-11-28 Thread Ronald Klop

Ah, it comes from the script after it.

[ronald@rpi2 /etc/periodic/daily]$ ./480.leapfile-ntpd
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
   [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
   [-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list]
   [--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer]
   [-o file] [--referer=URL] [-S bytes] [-T seconds]
   [--user-agent=agent-string] [-w seconds] URL ...
   fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
   [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
   [-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list]
   [--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer]
   [-o file] [--referer=URL] [-S bytes] [-T seconds]
   [--user-agent=agent-string] [-w seconds] -h host -f file [-c dir]

Apparently $ntp_tmp_leapfile is empty on this line in /etc/rc.d/ntpd:
fetch $ntp_leapfile_fetch_opts -o  
$ntp_tmp_leapfile $url && break


[ronald@rpi2 ~]$ sh -x /etc/rc.d/ntpd onefetch

+ fetch -mq -o https://www.ietf.org/timezones/data/leap-seconds.list
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]


The variable $ntp_tmp_leapfile is missing since the fetch method was split  
in r325256.

https://svnweb.freebsd.org/base/stable/11/etc/rc.d/ntpd?r1=325256=325255=325256

Cc-ing the committer.

Regards,

Ronald.


On Tue, 28 Nov 2017 20:34:57 +0100, Ronald Klop <ronald-li...@klop.ws>  
wrote:



Isn't this very weird in the output of last night:
"Checking for rejected mail hosts:
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]"

I don't see yet how the script  
/etc/periodic/daily/460.status-mail-rejects can try to call fetch.


Any thoughts on this?

For the record. I run dma instead of sendmail.
$ cat /etc/mail/mailer.conf
# $FreeBSD: stable/11/libexec/dma/dmagent/mailer.conf 289087 2015-10-09  
22:09:44Z bapt $


sendmail  /usr/libexec/dma
send-mail /usr/libexec/dma
mailq /usr/libexec/dma

on
FreeBSD rpi2 11.1-STABLE FreeBSD 11.1-STABLE #2 r325879: Thu Nov 16  
02:03:21 CET 2017  
root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2  arm


Ronald.



--- Forwarded message ---
From: r...@klop.ws
To: root
Cc:
Subject: rpi2 daily run output
Date: Tue, 28 Nov 2017 03:12:48 +0100


Removing stale files from /var/preserve:

Cleaning out old system announcements:

Removing stale files from /var/rwho:

Removing stale entries from sendmail host status cache:
mailwrapper: no mapping in /etc/mail/mailer.conf

Backup passwd and group files:

Verifying group file syntax:
/etc/group is fine

Backing up mail aliases:

Disk status:
FilesystemSizeUsed   Avail Capacity  Mounted on
/dev/ufs/rootfs   1.8G1.4G242M86%/
devfs 1.0K1.0K  0B   100%/dev
/dev/msdosfs/MSDOSBOOT 50M7.4M 43M15%/boot/msdos
tmpfs 128M628K127M 0%/tmp
/dev/da0s1a14G7.8G4.7G62%/mnt/usbdisk
tmpfs 512M4.0K512M 0%
/var/tmp/ports-build

Network interface status:
NameMtu Network   Address  Ipkts Ierrs IdropOpkts
Oerrs  Coll  Drop
lo0   16384 <Link#1>  lo0  0 0 0
0 0 0 0
lo0   - localhost localhost0 - -
0 - - -
lo0   - fe80::%lo0/64 fe80::1%lo0  0 - -
0 - - -
lo0   - your-net  localhost0 - -
0 - - -
ue01500 <Link#2>  b8:27:eb:77:37:63   581144 0 0
95090 0 0 0
ue0   - 192.168.1.0/2 192.168.1.14895132 - -
84713 - - -

Local system status:
   3:01AM  up 11 days, 11:05, 2 users, load averages: 0.36, 0.09, 0.03

Mail in local queue:
Mail queue is empty

Mail in submit queue:
mailq: invalid arguments

Security check:
  (output mailed separately)

Checking for rejected mail hosts:
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
 [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
 [-i file] [--key=file] [-N file] [--no-passive]  
[--no-proxy=list]
 [--no-sslv3] [--no-tlsv1] [--no-verify-hostname]  
[--no-verify-peer]

 [-o file] [--referer=URL] [-S bytes] [-T seconds]
 [--user-agent=agent-string] [-w seconds] URL ...
 fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
 [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
 [-i file] [--key=file] [-N file] [--no-passive]  
[--no-proxy=list]
 [--no-sslv3] [--no-tlsv1] [--no-verify-hostname]  
[--no-verify-peer]

 [-o file] [--referer=URL] [-S bytes] [-T seconds]
 [--user-agent=agent-string] [-w seconds] -h host -f file [-c  

Fwd: rpi2 daily run weird output

2017-11-28 Thread Ronald Klop

Isn't this very weird in the output of last night:
"Checking for rejected mail hosts:
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]"

I don't see yet how the script /etc/periodic/daily/460.status-mail-rejects  
can try to call fetch.


Any thoughts on this?

For the record. I run dma instead of sendmail.
$ cat /etc/mail/mailer.conf
# $FreeBSD: stable/11/libexec/dma/dmagent/mailer.conf 289087 2015-10-09  
22:09:44Z bapt $


sendmail  /usr/libexec/dma
send-mail /usr/libexec/dma
mailq /usr/libexec/dma

on
FreeBSD rpi2 11.1-STABLE FreeBSD 11.1-STABLE #2 r325879: Thu Nov 16  
02:03:21 CET 2017  
root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2  arm


Ronald.



--- Forwarded message ---
From: r...@klop.ws
To: root
Cc:
Subject: rpi2 daily run output
Date: Tue, 28 Nov 2017 03:12:48 +0100


Removing stale files from /var/preserve:

Cleaning out old system announcements:

Removing stale files from /var/rwho:

Removing stale entries from sendmail host status cache:
mailwrapper: no mapping in /etc/mail/mailer.conf

Backup passwd and group files:

Verifying group file syntax:
/etc/group is fine

Backing up mail aliases:

Disk status:
FilesystemSizeUsed   Avail Capacity  Mounted on
/dev/ufs/rootfs   1.8G1.4G242M86%/
devfs 1.0K1.0K  0B   100%/dev
/dev/msdosfs/MSDOSBOOT 50M7.4M 43M15%/boot/msdos
tmpfs 128M628K127M 0%/tmp
/dev/da0s1a14G7.8G4.7G62%/mnt/usbdisk
tmpfs 512M4.0K512M 0%
/var/tmp/ports-build

Network interface status:
NameMtu Network   Address  Ipkts Ierrs IdropOpkts
Oerrs  Coll  Drop
lo0   16384   lo0  0 0 0
0 0 0 0
lo0   - localhost localhost0 - -
0 - - -
lo0   - fe80::%lo0/64 fe80::1%lo0  0 - -
0 - - -
lo0   - your-net  localhost0 - -
0 - - -
ue01500   b8:27:eb:77:37:63   581144 0 0
95090 0 0 0
ue0   - 192.168.1.0/2 192.168.1.14895132 - -
84713 - - -

Local system status:
  3:01AM  up 11 days, 11:05, 2 users, load averages: 0.36, 0.09, 0.03

Mail in local queue:
Mail queue is empty

Mail in submit queue:
mailq: invalid arguments

Security check:
 (output mailed separately)

Checking for rejected mail hosts:
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
[--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
[-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list]
[--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer]
[-o file] [--referer=URL] [-S bytes] [-T seconds]
[--user-agent=agent-string] [-w seconds] URL ...
fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
[--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
[-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list]
[--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer]
[-o file] [--referer=URL] [-S bytes] [-T seconds]
[--user-agent=agent-string] [-w seconds] -h host -f file [-c dir]

Checking userland and kernel versions:
Userland and kernel are in sync.

Backing up pkgng database:

-- End of daily output --
___
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"


Re: file system deadlock in RELENG_11

2017-08-26 Thread Ronald Klop
Running procstat -kk  will display on what syscall a process/thread  
is blocking.

That might give some valuable information to people.

Regards,
Ronald.


On Thu, 24 Aug 2017 22:01:25 +0200, Mike Tancsa  wrote:


OK, this is fairly easy to repeat. If I start a sync of a snapshot via
zrep, it hangs the box.  CTRL+T shows


DEBUG: overiding stale lock on zroot/chyves from pid 19378
sending zroot/chyves@zrep_10 to 10.151.9.2:zroot/chyves
cannot receive new filesystem stream: destination
'zroot/chyves/guests/resi/disk1' exists
must specify -F to overwrite it
^C
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 358.94r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 360.42r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 360.79r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 360.99r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.19r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.37r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.55r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.74r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.92r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.11r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.31r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.50r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.69r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.90r 0.00u 0.00s 0%
3476k
load: 0.52  cmd: zfs 29690 [tx->tx_sync_done_cv] 363.08r 0.00u 0.00s 0%
3476k



On 8/24/2017 11:48 AM, Mike Tancsa wrote:

I upgraded a server yesterday from RELENG_11 from march 2017 to r322800
(Aug 22) and noticed that under heavy disk IO in a VM, the server is
locking up.  In the vm, I was doing a large untar and I noticed that
prior to the lockup, the hypervisor would be struggling to keep up the
disk writes.  The VM is on a zvol if that makes any difference. A few
times in the VM, IO would be clogged to the point that the disk would
timeout in the VM

Aug 24 08:32:02 kernel: ahcich6: Timeout on slot 14 port 0
Aug 24 08:32:02 kernel: ahcich6: is  cs  ss  rs
 tfd 50 serr  cmd 0001db17
Aug 24 08:32:02 kernel: (ada1:ahcich6:0:0:0): WRITE_FPDMA_QUEUED. ACB:
61 00 a8 47 d8 40 01 00 00 01 00 00
Aug 24 08:32:02 kernel: (ada1:ahcich6:0:0:0): CAM status: Command  
timeout

Aug 24 08:32:02 kernel: (ada1:ahcich6:0:0:0): Retrying command

When the parent deadlocks, I cant run anything thats not already in RAM.
shutdown doesnt work and I have to reboot the box via IPMI.

Any ideas how to debug this or try and better understand the problem so
I can at least work around it ?

---Mike




___
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"


Re: some general zfs tuning (for iSCSI)

2017-08-02 Thread Ronald Klop
On Fri, 28 Jul 2017 12:56:11 +0200, Eugene M. Zheganin   
wrote:



Hi,


I'm using several FreeBSD zfs installations as the iSCSI production  
systems, they basically consist of an LSI HBA, and a JBOD with a bunch  
of SSD disks (12-24, Intel, Toshiba or Sandisk (avoid Sandisks btw)).  
And I observe a problem very often: gstat shows 20-30% of disk load, but  
the system reacts very slowly: cloning a dataset takes 10 seconds,  
similar operations aren't lightspeeding too. To my knowledge, until the  
disks are 90-100% busy, this shouldn't happen. My systems are equipped  
with 32-64 gigs of RAM, and the only tuning I use is limiting the ARC  
size (in a very tender manner - at least to 16 gigs) and playing with  
TRIM. The number of datasets is high enough - hundreds of clones, dozens  
of snapshots, most of teh data ovjects are zvols. Pools aren't  
overfilled, most are filled up to 60-70% (no questions about low space  
pools, but even in this case the situation is clearer - %busy goes up in  
the sky).


So, my question is - is there some obvious zfs tuning not mentioned in  
the Handbook ? On the other side - handbook isn't much clear on how to  
tune zfs, it's written mostly in the manner of "these are sysctl iods  
you can play with". Of course I have seen several ZFS tuning guides.  
Like Opensolaris one, but they are mostly file- and  
application-specific. Is there some special approach to tune ZFS in the  
environment with loads of disks ? I don't know like tuning the vdev  
cache or something simllar. ?



Thanks.

Eugene.



What version of FreeBSD are you running?
What is the system doing during all this?
How are your pools setup (raidz1/2/3, mirror, 3mirror)?
How is your iSCSI configured and what are the clients doing with it?
Is the data distributed evenly on all disks?
Do the clients write a lot of sync data?

I think this kind of information helps people helping you.

Regards,
Ronald.
___
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"


mdconfig zpool from copied partition?

2017-06-05 Thread Ronald Klop

Hi,

I'm trying something like this:
# dd if=/dev/da0p2 of=/somefile
# mdconfig -f /somefile
# zpool import md0

da0p2 comes from my external usb-disk:
=>34  1953458109  da0  GPT  (931G)
  342014   - free -  (1.0M)
2048   5368709121  ms-basic-data  (256G)
   536872960  14165831682  freebsd-zfs  (675G)
  19534561282015   - free -  (1.0M)

Is this possible? Or will I miss some partion info in the end?

I already have this:
# mdconfig -lv
md0 vnode 104G  /mnt/files/ronald/freebsd-zfs.da0p2

NB: my dd was interrupted after 104GB, but I'm making a new copy already.

Regards,
Ronald.
___
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"


Re: Horrible console fonts in 11.0 stable

2017-03-11 Thread Ronald Klop
On Sat, 11 Mar 2017 19:38:33 +0100, Lars Eighner  
 wrote:


What is with the horrible console fonts in 11.0 stable? I have tried  
them all and they are each more hiddeous than the other.


Is there anyway to get the VGA fonts back. I never want any characters  
outside of Latin I.


Text programs are the only reason I use FreeBSD (it sure is not for the  
pathetic X.org). How can anyone work with the horrible text fonts which  
I suspect are some horrible raster fonts which reset video every time I  
switch virtual terms?






From 'man vt':

 hw.vga.textmode
 Set to 1 to use virtual terminals in text mode instead of
 graphics mode.  Features that require graphics mode, like
 loadable fonts, will be disabled.

You can set this in /boot/loader.conf.

Regards,
Ronald.
___
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"


Re: pkg upgrade deletes firefox?

2017-02-09 Thread Ronald Klop

Interesting:

# 21:12:51 root@sjakie [~]
pkg install firefox
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
pkg: No packages available to install matching 'firefox' have been found  
in the repositories


I guess this is a temporary hickup.

Ronald.



On Thu, 09 Feb 2017 21:12:28 +0100, Ronald Klop <ronald-li...@klop.ws>  
wrote:



Hi,

Today I get this...

# 21:08:42 root@sjakie [~]
pkg upgrade
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%944 B   0.9kB/s00:01
Fetching packagesite.txz: 100%6 MiB   3.0MB/s00:02
Processing entries: 100%
FreeBSD repository update completed. 25950 packages processed.
Checking for upgrades (13 candidates): 100%
Processing candidates (13 candidates): 100%
The following 13 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
firefox-51.0.1,1

Installed packages to be UPGRADED:
xkeyboard-config: 2.19 -> 2.20
xconsole: 1.0.6_1 -> 1.0.7
xauth: 1.0.9_1 -> 1.0.10
vim-lite: 8.0.0252 -> 8.0.0301
tmux: 2.3 -> 2.3_1
opencollada: 1.6.25 -> 1.6.37
mplayer: 1.3.0.20161228_2 -> 1.3.0.20161228_3
libevent2: 2.0.22_1 -> 2.1.8
libass: 0.13.5 -> 0.13.6
gstreamer1: 1.8.0 -> 1.8.0_1
gstreamer: 0.10.36_5 -> 0.10.36_6
ffmpeg: 3.2.2_5,1 -> 3.2.2_6,1

Number of packages to be removed: 1
Number of packages to be upgraded: 12

The operation will free 124 MiB.
25 MiB to be downloaded.

Proceed with this action? [y/N]:


Why would upgrade want to remove firefox?

Regards,
Ronald.
___
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"

___
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"


pkg upgrade deletes firefox?

2017-02-09 Thread Ronald Klop

Hi,

Today I get this...

# 21:08:42 root@sjakie [~]
pkg upgrade
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%944 B   0.9kB/s00:01
Fetching packagesite.txz: 100%6 MiB   3.0MB/s00:02
Processing entries: 100%
FreeBSD repository update completed. 25950 packages processed.
Checking for upgrades (13 candidates): 100%
Processing candidates (13 candidates): 100%
The following 13 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
firefox-51.0.1,1

Installed packages to be UPGRADED:
xkeyboard-config: 2.19 -> 2.20
xconsole: 1.0.6_1 -> 1.0.7
xauth: 1.0.9_1 -> 1.0.10
vim-lite: 8.0.0252 -> 8.0.0301
tmux: 2.3 -> 2.3_1
opencollada: 1.6.25 -> 1.6.37
mplayer: 1.3.0.20161228_2 -> 1.3.0.20161228_3
libevent2: 2.0.22_1 -> 2.1.8
libass: 0.13.5 -> 0.13.6
gstreamer1: 1.8.0 -> 1.8.0_1
gstreamer: 0.10.36_5 -> 0.10.36_6
ffmpeg: 3.2.2_5,1 -> 3.2.2_6,1

Number of packages to be removed: 1
Number of packages to be upgraded: 12

The operation will free 124 MiB.
25 MiB to be downloaded.

Proceed with this action? [y/N]:


Why would upgrade want to remove firefox?

Regards,
Ronald.
___
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"


Re: FBSD 10.3 + ZFS + Sun x4500 = utter lock up.

2017-02-08 Thread Ronald Klop
At work we used to run such a machine with 9.1 and 10.2. My colleague  
tells me 10.3 gave errors, but he does not remember what.
The machine is not in use anymore, because of other upgrades, so I can't  
verify for you.


Any reason not to try 11? I don't know if it fixes anything, but it would  
be a nice data point for comparison.


Ronald.


On Tue, 07 Feb 2017 22:44:01 +0100, Lee Damon  wrote:


FreeBSD [redacted] 10.3-STABLE FreeBSD 10.3-STABLE #2 r313008: Tue Jan
31 01:50:49 PST 2017 lvd@[redacted]:/usr/obj/usr/src/sys/GENERIC   
amd64


I'm trying to get FBSD 10.3 working on a Sun x4500 (don't ask) for use
as a ZFS-based backup server. However, whenever any amount of data is
put into a zpool and then zpool scrub is run the host locks up hard. On
reboot it complains that a "Hyper transport sync flood occurred".

I found
https://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065542.html
which seems to match but when I try the cpuset command mentioned there I
get an error:

; sudo cpuset -c -l 0 -x 58
cpuset: setaffinity: Invalid argument

Looks like the -c was invalid. After removing that I was informed -x 58
wasn't valid. Sure enough, there's no mpt0 or IRQ 58 on the host:

; vmstat -i
interrupt  total   rate
irq17: ohci28578  2
irq18: ohci3 473  0
irq19: ohci0 ohci1+ 4924  1
irq24: mvs0  457  0
irq32: mvs1  453  0
irq38: mvs2  451  0
irq46: mvs3 8063  1
irq52: em0152354 35
irq53: em1   140  0
irq68: mvs4  450  0
irq76: mvs5  454  0
cpu0:timer208311 48
cpu1:timer 98318 23
cpu2:timer105704 24
cpu3:timer106202 24
Total 695332162

Looking around with some help from #freebsd on efnet I found mvs0-5
which are connected to the Marvel drive controllers on the host. I then
used
  ; sudo cpuset -l 0 -x ##
where I replaced ## with 24, 32, 38, 46, 68, and 76.

After rebuilding the zpool I started writing to it. It took a lot less
time to crash - I didn't even need to run zpool scrub - but instead of
completely locking up it just rebooted. I did not see reference to the
hyper transport problem while watching it boot but given the poor
performance of the serial console I can't be 100% sure it wasn't there.

So now I turn here to ask for guidance. Is anyone currently successfully
running 10.x on a x4500 and if so, how are you doing it? If not, how can
I get this working?

thanks,
nomad
___
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"

___
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"


Re: FreeBSD 11.0-STABLE #0 r310265 amd64 seems to be cpi-ing garbage to mounted FAT32 fs after 10-20 GB.

2017-02-01 Thread Ronald Klop
On Thu, 29 Dec 2016 20:06:31 +0100, Jakub Lach   
wrote:



Hello,

I've recently tried to make a switch to a bigger memory card in some
device; what I've discovered, is that FreeBSD is cp-ing garbage to a
mounted FAT32 fs after first 10-20 GB (depending on luck).

What I mean by garbage are non removable 'files' with random names
which cannot be escaped. The fastest way to get rid of them is newfs.

I've initially thought the problem were faulty memory card(s) but
I was able to test them (mounted as FAT32 still) with sysutils/f3.
They are fine, the utility writes(!) and reads them correctly.

However, as soon as cp (-a) gets involved, the garbage appears,
sometimes with CAM errors and reboots.

Additionally, I saw exactly the same errors with FAT32 on HDD
mounted via USB, so the cards are not a problem.

What I can do?

1. Reading is not at all affected, I can backup (cp -a) mounted FAT32
cards to UFS2 (local disk) without problems.
2. I can mount FAT32 and test the cards with sysutils/f3. The medium
(card) is tested via the same USB dual card reader as below.

What I can't do reliably, as garbage appears after first 10-20 GB?

1. I can't cp (-a) from UFS2 to mounted FAT32 partition. Smaller writes
are a matter of luck.
2. I can't cp (-a) from FAT32 (mounted fs on memory card A in dual card
reader)
to another FAT32 (mounted fs on memory card B in a dual card reader).  
Same

problem as above.

Any ideas?



I see nobody replied. I don't have an answer, but this might help.
You can try the freebsd-fs mailinglist. It is about filesystems.
You can also provide more information about your system. What version of  
FreeBSD are you running? 'uname -a' and the content of /var/run/dmesg.boot  
as a starter.
You can file a problem report (PR) at https://bugs.freebsd.org/ with a  
reproducable test case.

Does the problem also occur if you use rsync to copy the files?

Regards,
Ronald.







--
View this message in context:  
http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-STABLE-0-r310265-amd64-seems-to-be-cpi-ing-garbage-to-mounted-FAT32-fs-after-10-20-GB-tp6154963.html

Sent from the freebsd-stable mailing list archive at Nabble.com.
___
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"

___
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"


update /usr/ports to same version as pkg upgrade?

2017-02-01 Thread Ronald Klop

Hi,

Is it possible to update the /usr/ports tree to the same version as is  
used by the default pkg repositories?
I use some ports which are not distributed as pkgs. When I 'portsnap auto'  
the ports tree gets new updates which are not in the pkgs yet and I don't  
want to rebuild those.
I'm also able to fetch the ports tree by svn if that gives more  
possibilities than portsnap for this.


So, is there a way to know from which svn revision the pkgs are build by  
the FreeBSD servers? Or something similar.


Regards,
Ronald.
___
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"


Re: network after resume

2017-01-25 Thread Ronald Klop
On Tue, 24 Jan 2017 11:58:11 +0100, Marko Cupać   
wrote:



Hi,

I am running 11.0-RELEASE-p6 amd64, and I'm having a strange problem on
my ThinkPad T440: after resuming from suspend, wifi resumes operation
and I can ping around, play music from NFS share etc., but I can't open
websites in chromium, pidgin won't reconnect to xmpp server, ownclound
client won't connect etc.

Restarting network with `service netif restart` tears wifi connection
apart and re-establishes it again, but those applications just won't
connect.

Any idea why those applications won't work when underlying OS has
network connectivity? Could it have something to do with those
applications connecting via SSL/TLS?

Thank you in advance,



What error do those applications give? Some applications do their own DNS  
caching. That cache might be stale, but the real error message would  
provide more hints than me guessing.


Regards,
Ronald.
___
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"

Re: NFS and amd on older FreeBSD

2017-01-17 Thread Ronald Klop
On Fri, 13 Jan 2017 09:06:56 +0100, Daniel Braniss   
wrote:





On 12 Jan 2017, at 21:01, Karl Young  wrote:

Daniel Braniss(da...@cs.huji.ac.il)@2017.01.12 10:25:03 +0200:


On 12 Jan 2017, at 9:49 AM, Daniel Braniss   
wrote:




On 12 Jan 2017, at 1:47 AM, Karl Young  wrote:

I inherited a lab that has a few hundred hosts running FreeBSD 7.2.
These hosts run test scripts that access files that are stored on
FreeBSD 6.3 host.  The 6.3 host exports a /data directory with NFS


On the 7.2 hosts, I can see the exported directory:

$ showmount -e 6.3-host
Exports list on 6.3-host
/data  Everyone

And access it with amd

$ ls -l /net/6-3.host/data

drwxr-xr-x 5 root  wheel  512 Jun  4  2009 git
drwxr-xr-x  4586 root  wheel83968 Nov  2 04:50 home

I'm trying to retire the 6.3 host and replace it with 9.3 (I know  
it's

old, but it's the best I can do for now).

I export the /data directory on the 9.3 system, and I can see it on  
my

7.2 hosts.

$ showmount -e  9.3-host
Exports list on 9.3-host:
/data   Everyone

But I can't automount it:

$ ls -l /net/9.3-host/data
ls: /net/9.3-host/data: No such file or directory

If I manually mount the exported directory, it works:

$ sudo mount -t nfs 9.3-host:/data /mnt/data/
$ mount | grep nfs
9.3-host:/data on /mnt/data (nfs)

$ ls -l /mnt/data
total 4
drwxr-xr-x  9 root  wheel  512 Dec 20 17:41 iaf2

I've spent some time on Google, but haven't found a solution.  I  
realize
these are very old versions, but I'm not in a position to upgrade  
them

right now.  My last resort will be to use /etc/fstab to do the NFS
mount, but I'd rather avoid that if I can.

Thanks for any pointers on how to resolve this.

-karl




if you changed the export file on the server after you tried to mount  
in on the client,
and will not realise this, if that’s the case, usually rebooting the  
client helps.



s/and/amd/ ^%$# hate spell checkers



Thanks Danny

I did try rebooting the client (and server) multiple times to no avail.



what does amq say?
you can, from another host do: amq -h client-host

btw, I thing that nfs_server must also run on the client …
I have nfs_server_enable=YES



$ 20:10:57 ronald@sjakie [~]
grep nfs_ser /etc//defaults/rc.conf
nfs_server_enable="NO"# This host is an NFS server (or NO).


Is your client a NFS server? If not than there is not need for  
nfs_server_enable YES on the client.


Regards,
Ronald.



danny

___
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"

___
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"

Re: broken source upgrade 9.3-STABLE to 10.3-STABLE

2016-12-15 Thread Ronald Klop
On Wed, 14 Dec 2016 08:27:13 +0100, Eugene Grosbein   
wrote:



Hi!

I've got legacy FreeBSD server running 8.4-STABLE and I'm trying to  
upgrade it.

Source upgrade for 8.4 to 9.3-STABLE r310015 went flawlessly.
After reboot, I checked out stable/10 r310043 sources and ran buildworld  
again.

It fails:

===> lib/clang/libllvmanalysis (all)
c++  -O2 -pipe  
-I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/include  
-I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/tools/clang/include  
-I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis  
-I.  
-I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/../../lib/clang/include  
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS  
-D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing  
-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.3\"  
-DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd10.3\"  
-DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\"  
-I/usr/obj/usr/src/tmp/legacy/usr/include  -fno-exceptions -fno-rtti -c  
/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis/LazyValueInfo.cpp  
-o LazyValueInfo.o
/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis/LazyValueInfo.cpp:  
In member function 'llvm::Constant*  
llvm::LazyValueInfo::getConstant(llvm::Value*, llvm::BasicBlock*)':
/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis/LazyValueInfo.cpp:1054:  
error: 'nullptr' was not declared in this scope

*** Error code 1

Does it mean that FreeBSD clang version 3.4.1  
(tags/RELEASE_34/dot1-final 208032) 20140512

is unable to build more recent clang version?



Check /usr/src/UPDATING:
20141231:
Clang, llvm and lldb have been upgraded to 3.5.0 release.

As of this release, a prerequisite for building clang, llvm and  
lldb is
a C++11 capable compiler and C++11 standard library.  This means  
that to
be able to successfully build the cross-tools stage of buildworld,  
with
clang as the bootstrap compiler, your system compiler or cross  
compiler

should either be clang 3.3 or later, or gcc 4.8 or later, and your
system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
later.

On any standard FreeBSD 10.x or 11.x installation, where clang and
libc++ are on by default (that is, on x86 or arm), this should  
work out

of the box.

On 9.x installations where clang is enabled by default, e.g. on  
x86 and

powerpc, libc++ will not be enabled by default, so libc++ should be
built (with clang) and installed first.  If both clang and libc++  
are

missing, build clang first, then use it to build libc++.

On 8.x and earlier installations, upgrade to 9.x first, and then  
follow

the instructions for 9.x above.


Regards,
Ronald.
___
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"


negative number of logins

2016-12-01 Thread Ronald Klop

Hi,

See this forwarded status message from this morning below. Funny numbers.

$ uname -a
FreeBSD sheeva2.klop.ws 11.0-STABLE FreeBSD 11.0-STABLE #25 r308727M: Wed  
Nov 16 13:46:35 CET 2016  
r...@sjakie.klop.ws:/usr/obj-arm/arm.arm/usr/src-arm/sys/SHEEVAPLUG  arm


$ w
 3:44PM  up 1 day, 17:57, 1 users, load averages: 0.08, 0.07, 0.02
USER   TTY  FROM  LOGIN@  IDLE  
WHAT
ronald pts/0klop.ws   3:43PM -  
w



Cheers,
Ronald.


--- Forwarded message ---
From: "Charlie Root" 
To: r...@klop.ws
Cc:
Subject: sheeva2.klop.ws monthly run output
Date: Thu, 01 Dec 2016 05:30:02 +0100


Doing login accounting:
ronald  35.24
total-72020.26
root -72055.50

Security check:
 (output mailed separately)

-- End of monthly output --
___
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"


Re: Postfix and tcpwrappers?

2016-07-25 Thread Ronald Klop
On Mon, 25 Jul 2016 18:48:25 +0200, Karl Denninger   
wrote:



This may not belong in "stable", but since Postfix is one of the
high-performance alternatives to sendmail

Question is this -- I have sshguard protecting connections inbound, but
Postfix appears to be ignoring it, which implies that it is not paying
attention to the hosts.allow file (and the wrapper that enables it.)

Recently a large body of clowncars have been targeting my sasl-enabled
https gateway (which I use for client machines and thus do in fact need)
and while sshguard picks up the attacks and tries to ban them, postfix
is ignoring the entries it makes which implies it is not linked with the
tcp wrappers.

A quick look at the config for postfix doesn't disclose an obvious
configuration solutiondid I miss it?



Don't know if postfix can handle tcp wrappers, but I use bruteblock [1]  
for protecting connections via the ipfw firewall. I use this for ssh and  
postfix.


Regards,
Ronald.

[1] http://www.freshports.org/security/bruteblock/
___
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"


Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-16:09.freebsd-update

2016-07-25 Thread Ronald Klop
On Mon, 25 Jul 2016 18:07:55 +0200, George L. Yermulnik   
wrote:



Hello!

On Mon, 25 Jul 2016 at 15:22:31 (+), FreeBSD Errata Notices wrote:

[...]

3) To update your system via a source code patch:



The following patches have been verified to apply to the applicable
FreeBSD release branches.



a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.


# fetch  
https://security.FreeBSD.org/patches/EN-16:09/freebsd-update.patch
# fetch  
https://security.FreeBSD.org/patches/EN-16:09/freebsd-update.patch.asc

# gpg --verify freebsd-update.patch.asc



b) Apply the patch.  Execute the following commands as root:



# cd /usr/src
# patch < /path/to/patch



c) Recompile the operating system using buildworld and installworld as
described in .

[...]

Do we really need to recompile the world after applying this patch? %-\
It's only one-letter diff in sh-file...



This is the formal procedure. A lawyer would say: you can shortcut it at  
your own risk. A practical computer user can just put the character in the  
sh-file.
Easy thing of the recompile is that the version of your FreeBSD install is  
updated also.


Regards,
Ronald.
___
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"


Re: Problem with libjpeg when updating packages

2016-07-21 Thread Ronald Klop
On Thu, 21 Jul 2016 09:28:21 +0200, Jörg Preiß   
wrote:



Hi all,

I just updated from 10.3 to stable. This worked fine, except when pkg
install updated the packages. There was a conflict within the libjpeg
package (sorry, I did not write down the exact message).

Now I don't know how to get slim working again, because libjpeg.so.8 is
not found.

So, maybe there is still an error in some update scripts or something
like that?




Reinstall slim. That should install its dependencies and/or give the error  
again.

pkg install -f slim

Regards,
Ronald.
___
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"

Re: Building "extra" kernels in stable/11...?

2016-07-18 Thread Ronald Klop
On Mon, 18 Jul 2016 10:11:24 +0200, Ronald Klop <ronald-li...@klop.ws>  
wrote:


On Sat, 16 Jul 2016 22:56:47 +0200, David Wolfskill  
<da...@catwhisker.org> wrote:



On Sat, Jul 16, 2016 at 05:45:11PM +0200, Herbert J. Skuhra wrote:


Well, I cannot reproduce this issue on my stable/11 machine.



For good reason.  It turns out that I was so *sure* I had my kernel
config files (for ALBERT & BATS) in place thta I didn't even check to
verify that.

And when I did:

freebeast(11.0)[1] ls -lT /usr/src/sys/amd64/conf/{GENERIC,ALBERT,BATS}
ls: /usr/src/sys/amd64/conf/ALBERT: No such file or directory
ls: /usr/src/sys/amd64/conf/BATS: No such file or directory
-rw-r--r--  1 david  wheel  14315 Jul  8 04:00:47 2016  
/usr/src/sys/amd64/conf/GENERIC

freebeast(11.0)[2] cd

Oops.  :-(  sorry for the noise.

Once I corrected that & re-tested... well, GENERIC built; ALBERT
is building as I type

Thanks for the reality check! :-}

Peace,
david


Coincidentally there was just a fix committed about this last week.

https://svnweb.freebsd.org/base/head/Makefile.inc1?view=log=302865

Regards,
Ronald.


Oooh :-)

https://svnweb.freebsd.org/base?view=revision=302898

It is still some work in progress.

Regards,
Ronald.
___
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"


Re: Building "extra" kernels in stable/11...?

2016-07-18 Thread Ronald Klop
On Sat, 16 Jul 2016 22:56:47 +0200, David Wolfskill   
wrote:



On Sat, Jul 16, 2016 at 05:45:11PM +0200, Herbert J. Skuhra wrote:


Well, I cannot reproduce this issue on my stable/11 machine.



For good reason.  It turns out that I was so *sure* I had my kernel
config files (for ALBERT & BATS) in place thta I didn't even check to
verify that.

And when I did:

freebeast(11.0)[1] ls -lT /usr/src/sys/amd64/conf/{GENERIC,ALBERT,BATS}
ls: /usr/src/sys/amd64/conf/ALBERT: No such file or directory
ls: /usr/src/sys/amd64/conf/BATS: No such file or directory
-rw-r--r--  1 david  wheel  14315 Jul  8 04:00:47 2016  
/usr/src/sys/amd64/conf/GENERIC

freebeast(11.0)[2] cd

Oops.  :-(  sorry for the noise.

Once I corrected that & re-tested... well, GENERIC built; ALBERT
is building as I type

Thanks for the reality check! :-}

Peace,
david


Coincidentally there was just a fix committed about this last week.

https://svnweb.freebsd.org/base/head/Makefile.inc1?view=log=302865

Regards,
Ronald.
___
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"


Re: Not-so stable if you take a CAM error....

2016-07-11 Thread Ronald Klop
On Mon, 11 Jul 2016 02:54:38 +0200, Karl Denninger   
wrote:



Got a (nasty) surprise this afternoon on my sandbox machine.

I was updating some Raspberry Pi2 machines which involved taking the sd
card out, sticking it in an adapter and plugging it into the sandbox,
then mounting the partition and using rsync.

Unfortunately one of the cards was, unknown to me, bad and returned a
write error during the update.

The machine panic'd immediately after the CAM write error popped up.

I was quite surprised by this, since (1) the SD card was (of course)
mounted as a UFS filesystem; it shows up as a CAM device, (2) the
machine itself is running off a ZFS root on a normal host-adapter and
thus there is no comingling of the buffer cache and (3) there were no
images being run from (can't, wrong architecture!) nor any system I/O
(e.g. pagefile) going to the SD card.

I certainly understand that under some circumstances (maybe even most
circumstances) taking a hard I/O error to a system device is going to
hose you and a panic() is arguably "least astonishment" when the price
of being wrong might be a corrupted system file or worse (e.g. corrupted
paged-out RSS, etc.)  But I didn't expect a panic out a failed write to
a device that is mounted and being used purely for data.

I don't have a crash dump but can almost-certainly reproduce this if
it's something that shouldn't happen and thus merits investigation.



Hi,

I understand you are surprised by this. I don't think it is the way it  
should work.
Is there _any_ debugging information for people to use and try to help  
you? Like which FreeBSD version are you running? Which FreeBSD version was  
used to create the UFS fs? Does it use softupdates (SU) or also journaling  
(SU+J)?
Maybe some output of dmesg? Or type of SD-card and reader. Other people  
might have similar problems with similar hardware.


Regards,
Ronald.
___
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"


Re: unbound and ntp issuse

2016-06-07 Thread Ronald Klop
On Tue, 07 Jun 2016 12:43:35 +0200, Slawa Olhovchenkov   
wrote:



On Tue, Jun 07, 2016 at 11:35:59AM +0100, krad wrote:


Like i said you could configure ntpdate as well as ntpd, but give it a
known good ip. It will only run once at boot, and ntpd will start after  
so

that can use the nice pool names.

A slightly better way maybe to give ntpdate a server hostname like
ntp-server and populated the hosts file with one of the ips from
pool.ntp.org. You could then have a periodic script to check and update  
the

ip in the hosts every day, so it works over a reboot. The ip would
obviously have to have an initial seed value, but you could work this  
out

progmatically at system configuration time with tools like ansible.


What purpose don't do it by standart scripts from base systems?
Enforcing DNSSEC must be prevent this strange works on all systems
lack CMOS time.



If the system lacks CMOS time it is hard to fix this problem. It is not  
only about NTP+DNSSEC, but also about the lack of timekeeping. This  
timekeeping problem can be solved by using a local ntp-server. That would  
break the deadlock of NTP+DNSSEC.


Ronald.



I am not expert in sh scripting for this automation.


On 7 June 2016 at 09:47, Slawa Olhovchenkov  wrote:

> On Tue, Jun 07, 2016 at 09:00:29AM +0100, krad wrote:
>
> > Well there is a deadlock situation there so you have to relax one  
of the

> > conditions, for one time at least.
> >
> > Your best bet is to do a manual ntpdate against a fixed ip of known
> > goodness. If you have a lot of machines you need to do this on, use
> ansible
> > or similar to do the heavy lifting for you. Ansible is best in my  
opinion

> > if you dont have anything setup as its quick to get going. It does
> require
> > python on the target machines so you would need to install that  
first.
> > Something like the following should get it working (as you dont  
have dns

> on
> > the target machine, package fetches wont work, so i would tunnel a  
squid

> > proxy and let that handle all the internet stuff.
> >
> > add something like the following to your ssh_config
> >
> > Host *
> > RemoteForward 31280 squid_server:3128
> >
> > then run some stuff like this (after installing ansible on your
> > desktop/bastion host)
> >
> > ansible  -b -m raw -a '/usr/bin/env ASSUME_ALWAYS_YES=1 http_proxy=
> > http://127.0.0.1:31280 /usr/sbin/pkg bootstrap -f' -u root -i
> >  -kS --ask-su-pass
> >
> > ansible  -b -m raw -a 'env ASSUME_ALWAYS_YES=YES http_proxy=
> > http://127.0.0.1:31280 pkg install python' -u root -i  


> > -kS --ask-su-pass
> >
> > ansible -m shell -a "ntpdate "  -kS  
--ask-su-pass -i

> > 
> >
> > from here on you should be able to start unbound and then ntpd eg
> >
> > ansible -m service -a "name=local_unbound state=restarted"
> >  -kS --ask-su-pass -i 
> > ansible -m service -a "name=ntpd state=restarted"  -kS  
--ask-su-pass -i

> >  >
> > Alternatively you could just relax your dnssec rules on first boot  
to

> give
> > ntp a chance. Probably much easier 8)
>
> How I am do it? I am don't touch dnssec rules and don't know unbound.
> May be this is posible by startup scripts?
> Also, some platforms lack of CMOS time, RPi, for example.
>
> > Also make sure you are using the '-g' flag on ntpd
>
> Yes, I am add `ntpd_sync_on_start=yes` to rc.conf.
> I am suggest do it by checkbox in bsdinstall.
>
>
> > On 6 June 2016 at 14:50, Slawa Olhovchenkov  wrote:
> >
> > > On Mon, Jun 06, 2016 at 09:33:02AM -0400, Lowell Gilbert wrote:
> > >
> > > > Slawa Olhovchenkov  writes:
> > > >
> > > > > On Fri, Jun 03, 2016 at 02:34:18PM -0400, Lowell Gilbert  
wrote:

> > > > >
> > > > >> Slawa Olhovchenkov  writes:
> > > > >>
> > > > >> > Default install with local_unbound and ntpd can't be  
functional

> with
> > > > >> > incorrect date/time in BIOS:
> > > > >> >
> > > > >> > Unbound requred correct time for DNSSEC check and refuseing
> queries
> > > > >> > ("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed  
to

> prime
> > > > >> > trust anchor -- DNSKEY rrset is not secure . DNSKEY IN")
> > > > >> >
> > > > >> > ntpd don't have any numeric IP of ntp servers in ntp.conf  
--

> only
> > > > >> > symbolic names like 0.freebsd.pool.ntp.org, as result --  
can't

> > > > >> > resolve (see above, about DNSKEY).
> > > > >>
> > > > >> I can't see how this would happen. DNSSEC doesn't seem to be
> required
> > > in
> > > > >> a regular install as far as I can see. Certainly I don't  
have any

> > > > >
> > > > > I don't know reasson for enforcing DNSSEC in regular install.
> > > > > I am just select `local_unbound` at setup time and enter
> `127.0.0.1` as
> > > > > nameserver address.
> > > >
> > > > That's not enough to configure unbound as a fully recursive DNS
> > > > server.
> > >
> > > What I am missing?
> > > Need to fix unbound setup scripts? bsdinstall scripts?
> > > As I see unbound setup scripts detects 

Re: if_iwn wifi broke on 11-CURRENT

2016-05-03 Thread Ronald Klop
On Tue, 03 May 2016 02:51:56 +0200, Ronald Klop <ronald-li...@klop.ws>  
wrote:



Hi,

I upgraded my laptop and Wifi stopped working.

It still worked on:
May  2 20:11:13 sjakie kernel: FreeBSD 11.0-CURRENT #8 r296724M: Sun Mar  
13 16:03:31 CET 2016

but broke on:
May  2 20:24:53 sjakie kernel: FreeBSD 11.0-CURRENT #9 r298900M: Mon  
May  2 05:00:46 CEST 2016.


I booted the old kernel again and grabbed this information:
The device is an:
iwn0:  mem 0xf800-0xf8001fff irq 17 at  
device 0.0 on pci3


ifconfig:
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu  
1500

ether **:**:**:**:**:**
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid ** channel 11 (2462 MHz 11g ht/20) bssid **:**:**:**:**:**
regdomain ETSI country NL authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi
wme roaming MANUAL
groups: wlan

It works on 5Ghz also.


This looks exactly like my issue:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208933
I was just 41 commit short of a working version. ;-) I will try this  
tomorrow.


Regards,
Ronald.

___
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"


if_iwn wifi broke on 11-CURRENT

2016-05-02 Thread Ronald Klop

Hi,

I upgraded my laptop and Wifi stopped working.

It still worked on:
May  2 20:11:13 sjakie kernel: FreeBSD 11.0-CURRENT #8 r296724M: Sun Mar  
13 16:03:31 CET 2016

but broke on:
May  2 20:24:53 sjakie kernel: FreeBSD 11.0-CURRENT #9 r298900M: Mon May   
2 05:00:46 CEST 2016.


I booted the old kernel again and grabbed this information:
The device is an:
iwn0:  mem 0xf800-0xf8001fff irq 17 at  
device 0.0 on pci3


ifconfig:
wlan0: flags=8843 metric 0 mtu 1500
ether **:**:**:**:**:**
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid ** channel 11 (2462 MHz 11g ht/20) bssid **:**:**:**:**:**
regdomain ETSI country NL authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi
wme roaming MANUAL
groups: wlan

It works on 5Ghz also.

Regards,
Ronald.
___
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"


Re: Process stuck in "vnread"

2016-03-02 Thread Ronald Klop

Hello,

Would it be possible this has to do with the resolved 'system hangs when  
using ZFS caused by VFS' in 10.3-BETA3?

https://lists.freebsd.org/pipermail/freebsd-stable/2016-February/084238.html

Regards,
Ronald.

On Wed, 02 Mar 2016 10:12:31 +0100, Maxim Sobolev   
wrote:



Hi, I've encountered cp(1) process stuck in the vnread state on one of my
build machines that got recently upgraded to 10.3.

   0 79596 1   0  20  0   170921396 wait I 1
0:00.00

/bin/sh /usr/local/bin/autoreconf -f -i
   0 79602 79596   0  52  0   414889036 wait I 1
0:00.07

/usr/local/bin/perl -w /usr/local/bin/autoreconf-2.69 -f -i
   0 79639 79602   0  72  0   0   0 -Z 1
0:00.27


   0 79762 79602   0  20  0   170921396 wait I 1
0:00.00

/bin/sh /usr/local/bin/automake --add-missing --copy --force-missing
   0 79768 79762   0  52  0   49736   13936 wait I 1
0:00.11

/usr/local/bin/perl -w /usr/local/bin/automake-1.15 --add-missing --copy
--force-missing
   0 79962 79768   0  20  0   123681024 vnread   DL1
0:00.00

cp /usr/local/share/automake-1.15/compile ./compile

I am not sure if it's related to that OS version upgrade, but I have not
seen any such issues on the same machine in 2-3 years running essentially
the same build process with version 9.x, 10.0, 10.1 and 10.2.

$ uname -a
FreeBSD van01.sippysoft.com 10.3-PRERELEASE FreeBSD 10.3-PRERELEASE #1
80de3e2(master)-dirty: Tue Feb  2 12:19:57 PST 2016
sobo...@abc.sippysoft.com:/usr/obj/usr/home/sobomax/projects/freebsd103/sys/ABC
 amd64

The kernel stack trace is:

(kgdb) thread 360
[Switching to thread 360 (Thread 100515)]#0  0x8095244e in
sched_switch ()
(kgdb) bt
#0  0x8095244e in sched_switch ()
#1  0x809313b1 in mi_switch ()
#2  0x8097089a in sleepq_wait ()
#3  0x80930dd7 in _sleep ()
#4  0x809b230e in bwait ()
#5  0x80b511f3 in vnode_pager_generic_getpages ()
#6  0x80dd1607 in VOP_GETPAGES_APV ()
#7  0x80b4f59a in vnode_pager_getpages ()
#8  0x80b30031 in vm_fault_hold ()
#9  0x80b2f797 in vm_fault ()
#10 0x80cb5a75 in trap_pfault ()
#11 0x80cb51dd in trap ()
#12 0x80c9b122 in calltrap ()
#13 0x80cb36f1 in copyin ()
#14 0x80977ddf in uiomove_faultflag ()

The FS stack configuration is somewhat unique, so I am not sure if I am
hitting some rare race condition or lock ordering issues specific to  
that.

It's basically ZFS (ZRAID) on top of pair or SATA SSDs with big file on
that FS attached via md(4) and UFS2 on that md(4). The build itself runs  
in

chroot with that UFS2 fs as its primary root.

Just maybe additional bit of info, attempting to list the directory with
that UFS image also got my bash process stuck in "zfs" state, backtrace
from that is:

(kgdb) thread 353
[Switching to thread 353 (Thread 100508)]#0  0x8095244e in
sched_switch ()
(kgdb) bt
#0  0x8095244e in sched_switch ()
#1  0x809313b1 in mi_switch ()
#2  0x8097089a in sleepq_wait ()
#3  0x809069ad in sleeplk ()
#4  0x809060e0 in __lockmgr_args ()
#5  0x809b8b7c in vop_stdlock ()
#6  0x80dd0a3b in VOP_LOCK1_APV ()
#7  0x809d6d23 in _vn_lock ()
#8  0x81a8c9cd in ?? ()
#9  0x in ?? ()
___
freebsd...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org"

___
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"


Re: Swap Questions

2015-08-16 Thread Ronald Klop
On Sat, 15 Aug 2015 21:07:55 +0200, Tim Daneliuk tun...@tundraware.com  
wrote:



On 08/14/2015 12:39 PM, Warren Block wrote:

On Fri, 14 Aug 2015, Tim Daneliuk wrote:

I just built a 10.2 machine on a cloud-based VPS (Digital Ocean) that  
has
512M of memory and 1G of swap partition.  I am seeing a ton of errors  
like

this:

Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(10): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(14): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(11): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(6): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(7): failed
Aug 14 00:01:22 myhost last message repeated 2 times


So, I added this to fstab (after creating /usr/swap0):

md99noneswapsw,file=/usr/swap000

And then did this:

swapon -aq


But, when I do a swapinfo, all I can see is the disk swap partition
that comes standard with the VPS:


Device  1K-blocks UsedAvail Capacity
/dev/gpt/swapfs   1048576   456572   59200444%


Add the -L (late) option to swapon.  How this works might differ  
between 10-Release, 10-Stable, and 11.


Incidentally, md99 does not have to be literal, it's just meant to get  
the md device number up out of the way of common interactive usage of  
mdconfig.



So -L does fix the problem - sort of.  The machine picks up the file as
additional swap on boot just fine.  HWOEVER, when I try to reboot or shut
down the host, I get a panic telling me some noise about not being able
to shutdown swap for some reason.


It helps if you provide the exact text of the panic. People regularly  
don't get to see these inside there crystal ball. ;-) You call it noise.  
Others might get an helpful hint from it to help you.


Regards,
Ronald.



So ... I decided to just add a second disk partition for swap and -
for some reason - it works fine interactively, but upon reboot,
the newly created swap partition no longer exists and gpart shows
the space as free again.  I tried a gpart commit, but get
operation not permitted.  So now I am trying to figure out
how to make gpart changes stick.  This may be an artifact of
the way Digital Ocean droplets are set up 

G

___
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


Re: Swap Questions

2015-08-16 Thread Ronald Klop
On Sun, 16 Aug 2015 14:51:49 +0200, Ronald Klop ronald-li...@klop.ws  
wrote:


On Sat, 15 Aug 2015 21:07:55 +0200, Tim Daneliuk tun...@tundraware.com  
wrote:



On 08/14/2015 12:39 PM, Warren Block wrote:

On Fri, 14 Aug 2015, Tim Daneliuk wrote:

I just built a 10.2 machine on a cloud-based VPS (Digital Ocean) that  
has
512M of memory and 1G of swap partition.  I am seeing a ton of errors  
like

this:

Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(10): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(14): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(11): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(6): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(7): failed
Aug 14 00:01:22 myhost last message repeated 2 times


So, I added this to fstab (after creating /usr/swap0):

md99noneswapsw,file=/usr/swap000

And then did this:

swapon -aq


But, when I do a swapinfo, all I can see is the disk swap partition
that comes standard with the VPS:


Device  1K-blocks UsedAvail Capacity
/dev/gpt/swapfs   1048576   456572   59200444%


Add the -L (late) option to swapon.  How this works might differ  
between 10-Release, 10-Stable, and 11.


Incidentally, md99 does not have to be literal, it's just meant to get  
the md device number up out of the way of common interactive usage of  
mdconfig.



So -L does fix the problem - sort of.  The machine picks up the file as
additional swap on boot just fine.  HWOEVER, when I try to reboot or  
shut

down the host, I get a panic telling me some noise about not being able
to shutdown swap for some reason.


It helps if you provide the exact text of the panic. People regularly  
don't get to see these inside there crystal ball. ;-) You call it noise.  
Others might get an helpful hint from it to help you.



Maybe you already knew, but adding dumpdev=AUTO in /etc/rc.conf can  
provide a kernel dump on panic which can be analyzed after reboot.


Ronald.




Regards,
Ronald.



So ... I decided to just add a second disk partition for swap and -
for some reason - it works fine interactively, but upon reboot,
the newly created swap partition no longer exists and gpart shows
the space as free again.  I tried a gpart commit, but get
operation not permitted.  So now I am trying to figure out
how to make gpart changes stick.  This may be an artifact of
the way Digital Ocean droplets are set up 

G

___
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

___
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


Re: Swap Questions

2015-08-14 Thread Ronald Klop
On Fri, 14 Aug 2015 15:15:26 +0200, Tim Daneliuk tun...@tundraware.com  
wrote:



I just built a 10.2 machine on a cloud-based VPS (Digital Ocean) that has
512M of memory and 1G of swap partition.  I am seeing a ton of errors  
like

this:

Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(10): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(14): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(11): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(6): failed
Aug 14 00:01:22 myhost kernel: swap_pager_getswapspace(7): failed
Aug 14 00:01:22 myhost last message repeated 2 times


So, I added this to fstab (after creating /usr/swap0):

md99noneswapsw,file=/usr/swap0  0   0

And then did this:

swapon -aq


But, when I do a swapinfo, all I can see is the disk swap partition
that comes standard with the VPS:


Device  1K-blocks UsedAvail Capacity
/dev/gpt/swapfs   1048576   456572   59200444%



Two questions:

1) Is this reasonable behavior from  a machine wiht 512M of memory and
   a 1G swap partition?  I am doing things like running clamscan and
   buildworld at the same time. That's why I tried to add space with
   a file.

2) Why doesn't the extra swap disk appear in the hostinfo output.



Does the /dev/md99 device exist now? Otherwise something went wrong when  
you tried adding swap. Try swapon -a without the -q.


Ronald
___
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


Re: Swap Questions

2015-08-14 Thread Ronald Klop

On Fri, 14 Aug 2015 16:44:31 +0200, Tim Daneliuk tun...@tundraware.com
wrote:


On 08/14/2015 08:35 AM, Ronald Klop wrote:
Does the /dev/md99 device exist now? Otherwise something went wrong  
when you tried adding swap. Try swapon -a without the -q.


Yes, the device exists and yes, swapon claims is is in use:

swapon -a
swapon: md99 on /usr/swap0: Device already in use

But swapinfo doesn't know about it, if it is:

swapinfo
Device  1K-blocks UsedAvail Capacity
/dev/gpt/swapfs   1048576   500300   54827648%


I don't know whether this is just an artifact of how swapinfo reports  
things,
but the system acts like it's not seeing the additional swap when it is  
under

heavy load.

The main culprit here, BTW, is clamav which chews through memory like  
crazy
as best as I can determine, and this is a VM with only 512M of memory,  
hence

the desire to increase swap space.




I tested this on my 11-CURRENT/amd64 laptop and I get this:

# grep swap /etc/fstab
/dev/gpt/swap0  noneswapsw  0   0
md99noneswapsw,file=/tmp/test   0   0

# dd if=/dev/zero of=/tmp/test bs=1M count=10

# swapon -a
swapon: adding /dev/md99 as swap device

[root@sjakie /tmp]# swapinfo
Device  1K-blocks UsedAvail Capacity
/dev/gpt/swap04193280   276744  3916536 7%
/dev/md99   10240010240 0%
Total 4203520   276744  3926776 7%

Works ok for me.

Regards,
Ronald.
___
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


what to do with corrupt /var/db/portsnap directory?

2015-08-04 Thread Ronald Klop

Hi,

I have a computer which crashed and fsck removed some files in  
/var/db/portsnap/files. If I run portsnap I get this error now.


/usr/ports/devel/elixir-combine/
files/d542ae5f0048c430905d5f8de805dc81db255b5fe8aa35d2d63569c76086e902.gz  
not found -- snapshot corrupt.


Is there a way to let portsnap fix the corrupted state without removing  
/var/db/portsnap/files and re-downloading everything?


Regards,
Ronald.
___
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


Re: mount_msdosfs: msdosfs_iconv: Operation not permitted

2015-07-29 Thread Ronald Klop
I think you should make sure the msdosfs_iconv module is already loaded.  
Mount_msdosfs loads this module for you if it has the rights. That is why  
it works if root has done that ones.


Add this to rc.conf and reboot:
kld_list=msdosfs_iconv

Regards,
Ronald.


On Wed, 29 Jul 2015 21:32:00 +0200, ae...@posteo.de wrote:


Hello,

it looks like an old issue [1,2,3], but it's bugging me.

Generally, I'm not able to mount msdos file system as a regular user
with extra charset options (-L) before the superuser.  After the
superuser mounts (and unmounts) the file system, regular users can do it
to.  Below is more info about my system and the detailed steps to
reproduce the issue.

Thanks for suggestions.
Stefan


[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=109024
[2]  
https://forums.freebsd.org/threads/mount_msdosfs-msdosfs_iconv-operation-not-permitted.36897/

[3] https://forums.freebsd.org/threads/mount_msdosfs-bug.2668/



** my system

% uname -a
FreeBSD silver.local 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed  
May 13 06:54:13 UTC 2015  
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64



% locale
LANG=en_GB.UTF-8
LC_CTYPE=en_GB.UTF-8
LC_COLLATE=en_GB.UTF-8
LC_TIME=en_GB.UTF-8
LC_NUMERIC=en_GB.UTF-8
LC_MONETARY=en_GB.UTF-8
LC_MESSAGES=en_GB.UTF-8
LC_ALL=


% cat /etc/fstab
/dev/da1/home/user/mnt/u0  msdosfs  
rw,noauto,noexec,-L=en_GB.UTF-8,-m=600,-M=700   0   0
/dev/da1s1  /home/user/mnt/u1  msdosfs  
rw,noauto,noexec,-L=en_GB.UTF-8,-m=600,-M=700   0   0



% sysctl vfs.usermount
vfs.usermount: 1



% cat /etc/rc.conf | grep kiconv
kiconv_preload=YES
kiconv_local_charset=UTF-8
kiconv_foreign_charset=UTF-16BE UTF-8
kiconv_fstypes=msdosfs


% pkg info|grep kiconv
kiconvtool-0.97Tool to preload kernel iconv charset  
tables





** initially loaded tables

% kiconvtool -d
UTF-8 - UTF-16BE
UTF-16BE - UTF-8


** try to mount as a regular user

% mount /home/user/mnt/u1
mount_msdosfs: msdosfs_iconv: Operation not permitted



** mount fs as root

# mount /home/user/mnt/u1
# umount /home/user/mnt/u1


** tables after root mounted the fs

% kiconvtool -d
UTF-8 - UTF-16BE
UTF-16BE - UTF-8
UTF-8 - _wctype


** now a regular user can mount too

% mount /home/user/mnt/u1
___
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


Re: iwn Intel Centrino Advanced-N 6235 support in 10-stable

2015-07-20 Thread Ronald Klop
On Mon, 15 Jun 2015 23:08:36 +0200, Oliver Pinter  
oliver.pin...@hardenedbsd.org wrote:



On 6/15/15, Ronald Klop ronald-li...@klop.ws wrote:

On Wed, 03 Jun 2015 14:25:23 +0200, Oliver Pinter
oliver.pin...@hardenedbsd.org wrote:


On 6/3/15, Ronald Klop ronald-li...@klop.ws wrote:

Hello,

I see support for the 6235 in iwn(4) is committed in Dec 2013 to  
CURRENT

[1]. I would like to buy one of these for a reasonable price [2]. Will
it
be easy to use the driver from current in 10-stable? Or is there a
reason
support for this hardware is not MFC'ed?

[1] http://svnweb.freebsd.org/base?view=revisionrevision=259116
[2]
http://www.routercenter.nl/product/294857/intel-centrino-advanced-n-6235.html

A recommendation for a better supported card is also welcome.


Hi Ronald!

Try this branch:
https://github.com/opntr/opBSD/tree/op/stable/10-stable-hbsd-iwn .

I backported most of the net80211 and iwn related changes till 2014.
August to 10-STABLE in this branch.


Hi,

The card is ordered. Will try your branch soon. Is there more in that
branch or only WiFi changes?


The changes are ontop of HardenedBSD, so there are many of changes.



Cheers,
Ronald.




Oliver,

Thanks for your info. In the end I decided to go with 11-CURRENT which is  
running ok with this wifi network card while I'm typing this.


Regards,
Ronald.
___
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


Re: RealTek 8179CE

2015-06-29 Thread Ronald Klop
On Mon, 29 Jun 2015 15:32:39 +0200, Gardner Bell gardnerb...@gmail.com  
wrote:



I've installed 10.1-RELEASE on a Toshiba Satellite but the on-board
wireless nics are not being picked up by any drivers. From the pciconf
utility it is showing as.

none2@pci0:2:0:0: class=0x028000 card=0x019110ec chip=0x817910ec rev=0x01
hdr=0x0
vendor = 'RealTek Semiconductor Ltd'
class = network




I don't know.
Googleing for the chip number gives me only somebody else asking the same  
question.

https://www.google.com/search?q=0x817910ec



none3@pci0:3:0:0: class=0x02000 card=0xfa401179 chip=0x10a01969 rev=0x10
hdr=0x0
vendor = 'Atheros Communications Inc'
class = network
subclass= ethernet



I guess this should be handled by the if_ath driver, but I don't know if  
it supports this specific chipset.
Googleing for the card and/or chip idea also gives more questions from  
people trying to make it work.


If anyone has an idea what driver these cards may fall under or how to  
have

these attach to a driver would be appreciated



I just bought an 'Intel Centrino Advanced 6235' which is only supported by  
if_iwn in 11-CURRENT and not in 10.

You might try to boot from a USB stick with a 11 image on it.
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/11.0/

Regards,
Ronald.
___
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


Re: Getting going with a new Dell 7810

2015-06-17 Thread Ronald Klop

On Tue, 16 Jun 2015 22:29:48 +0200, Richard Kuhns r...@wintek.com wrote:


On 06/16/15 15:58, John Nielsen wrote:

On Jun 16, 2015, at 12:39 PM, Ronald Klop ronald-li...@klop.ws wrote:

What does 'sysctl kern.vty' say? If it is not 'vt', you need the  
following stuff.


/boot/loader.conf should contain
kern.vty=vt

And /etc/rc.conf
kld_list=radeonkms

Or something similar.

FreeBSD is in the transition of old-style syscons- and vt-terminal.  
The last one has support for modern KMS graphics, but is not the  
default on 10 yet.


With UEFI boot it will be using vt but with the efifb driver by  
default. Hopefully loading the radeon KMS driver (as Ronald suggests  
above) will let it take over. Try it with just a “kldload radeonkms”  
before adding it to rc.conf, just in case something gets wedged..


As you said, it is using vt. Unfortunately loading radeonkms didn't
help. It actually seems to be a regression; the only RADEON line
/var/log/Xorg.0.log now is the one that lists all the supported
chipsets.  Immediately after that line it ends with


[  4005.835] (II) VESA: driver for VESA chipsets: vesa
[  4005.835] (++) Using config file: /home/rjk/xorg.conf.new
[  4005.836] (==) ServerLayout X.org Configured
[  4005.836] (**) |--Screen Screen0 (0)
[  4005.836] (**) |   |--Monitor Monitor0
[  4005.836] (**) |   |--Device Card0
[  4005.836] (**) |--Screen Screen1 (1)
[  4005.836] (**) |   |--Monitor Monitor1
[  4005.836] (**) |   |--Device Card1
[  4005.836] (**) |--Input Device Mouse0
[  4005.836] (**) |--Input Device Keyboard0
[  4005.836] (==) Automatically adding devices
[  4005.836] (==) Automatically enabling devices
[  4005.836] (==) Not automatically adding GPU devices
[  4005.836] (**) FontPath set to:
/usr/local/share/fonts/misc/,
/usr/local/share/fonts/TTF/,
/usr/local/share/fonts/OTF/,
/usr/local/share/fonts/Type1/,
/usr/local/share/fonts/100dpi/,
/usr/local/share/fonts/75dpi/,
/usr/local/share/fonts/misc/,
/usr/local/share/fonts/TTF/,
/usr/local/share/fonts/OTF/,
/usr/local/share/fonts/Type1/,
/usr/local/share/fonts/100dpi/,
/usr/local/share/fonts/75dpi/
[  4005.836] (**) ModulePath set to /usr/local/lib/xorg/modules
[  4005.836] (WW) Hotplugging is on, devices using drivers 'kbd',
'mouse' or 'vmmouse' will be disabled.
[  4005.836] (WW) Disabling Mouse0
[  4005.836] (WW) Disabling Keyboard0
[  4005.836] (II) [KMS] Kernel modesetting enabled.
[  4005.836] (WW) Falling back to old probe method for vesa
[  4005.836] Number of created screens does not match number of detected
devices.
  Configuration failed.
[  4005.836] (EE) Server terminated with error (2). Closing log file.


I noticed in the previous log that it said


[  1292.463] (--) Using syscons driver with X support (version 2.0)


which made me think I had something set up incorrectly, since it's using
vt, not syscons.



Hi, I don't know about the other issues, but can confirm that my  
Xorg.0.log also says syscons here while I'm using vt. That is normal.


Regards,
Ronald.






On Tue, 16 Jun 2015 18:55:10 +0200, Richard Kuhns r...@wintek.com  
wrote:



Greetings all,

I've just received a new Dell Precision 7810. I've installed FreeBSD
10.1 (UEFI boot), checked out sources, built world  kernel and am now
running r284449. So far, so good.

The problem is Xorg. I'm running the latest Xorg in ports; I just did  
a

'make install clean' in /usr/ports/x11/xorg with no errors.

The display card is a FirePro W4100. lspci shows:

03:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Cape Verde GL [FirePro W4100]

It has 4 DisplayPorts, and I have 2 monitors plugged in. If I run  
'Xorg

-configure' it says

Number of created screens does not match number of detected devices.
 Configuration failed.

Looking through /var/log/Xorg.0.log it appears that the X server is
trying to use the RADEON driver, but ends with:

=
[  1292.463] (--) Using syscons driver with X support (version 2.0)
[  1292.463] (--) using VT number 9

[  1292.485] (II) [KMS] Kernel modesetting enabled.
[  1292.485] (WW) Falling back to old probe method for vesa
[  1292.485] (WW) VGA arbiter: cannot open kernel arbiter, no  
multi-card

support
[  1292.485] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[  1292.485] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes  
(32

bpp pixmaps)
[  1292.485] (==) RADEON(0): Default visual is TrueColor
[  1292.485] (==) RADEON(0): RGB weight 888
[  1292.485] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[  1292.485] (--) RADEON(0): Chipset: VERDE (ChipID = 0x682c)
[  1292.579] (EE) RADEON(0): [drm] Failed to open DRM device for
pci::03:00.0: No such file or directory
[  1292.579] (EE) RADEON(0): Kernel modesetting setup failed
[  1292.579] (II) UnloadModule: radeon
[  1292.579] (EE) Screen(s) found, but none have a usable  
configuration.

[  1292.579] (EE)
Fatal server error:
[  1292.579] (EE

Re: Getting going with a new Dell 7810

2015-06-16 Thread Ronald Klop
What does 'sysctl kern.vty' say? If it is not 'vt', you need the following  
stuff.


/boot/loader.conf should contain
kern.vty=vt

And /etc/rc.conf
kld_list=radeonkms

Or something similar.

FreeBSD is in the transition of old-style syscons- and vt-terminal. The  
last one has support for modern KMS graphics, but is not the default on 10  
yet.


Regards,
Ronald.


On Tue, 16 Jun 2015 18:55:10 +0200, Richard Kuhns r...@wintek.com wrote:


Greetings all,

I've just received a new Dell Precision 7810. I've installed FreeBSD
10.1 (UEFI boot), checked out sources, built world  kernel and am now
running r284449. So far, so good.

The problem is Xorg. I'm running the latest Xorg in ports; I just did a
'make install clean' in /usr/ports/x11/xorg with no errors.

The display card is a FirePro W4100. lspci shows:

03:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Cape Verde GL [FirePro W4100]

It has 4 DisplayPorts, and I have 2 monitors plugged in. If I run 'Xorg
-configure' it says

Number of created screens does not match number of detected devices.
  Configuration failed.

Looking through /var/log/Xorg.0.log it appears that the X server is
trying to use the RADEON driver, but ends with:

=
[  1292.463] (--) Using syscons driver with X support (version 2.0)
[  1292.463] (--) using VT number 9

[  1292.485] (II) [KMS] Kernel modesetting enabled.
[  1292.485] (WW) Falling back to old probe method for vesa
[  1292.485] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card
support
[  1292.485] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[  1292.485] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32
bpp pixmaps)
[  1292.485] (==) RADEON(0): Default visual is TrueColor
[  1292.485] (==) RADEON(0): RGB weight 888
[  1292.485] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[  1292.485] (--) RADEON(0): Chipset: VERDE (ChipID = 0x682c)
[  1292.579] (EE) RADEON(0): [drm] Failed to open DRM device for
pci::03:00.0: No such file or directory
[  1292.579] (EE) RADEON(0): Kernel modesetting setup failed
[  1292.579] (II) UnloadModule: radeon
[  1292.579] (EE) Screen(s) found, but none have a usable configuration.
[  1292.579] (EE)
Fatal server error:
[  1292.579] (EE) no screens found(EE)
[  1292.580] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[  1292.580] (EE) Please also check the log file at
/var/log/Xorg.0.log for additional information.
[  1292.580] (EE)
[  1292.580] (EE) Server terminated with error (1). Closing log file.


Should I be able to use this video card? I've done some googling, and
apparently at least some Linux people are using it.

It's not a huge deal if it doesn't work; I can install a Radeon HD 4670
that I know works. If I've mis-configured something, though, I'd like to
fix it.

Thanks for any comments!

___
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


Re: iwn Intel Centrino Advanced-N 6235 support in 10-stable

2015-06-15 Thread Ronald Klop
On Wed, 03 Jun 2015 14:25:23 +0200, Oliver Pinter  
oliver.pin...@hardenedbsd.org wrote:



On 6/3/15, Ronald Klop ronald-li...@klop.ws wrote:

Hello,

I see support for the 6235 in iwn(4) is committed in Dec 2013 to CURRENT
[1]. I would like to buy one of these for a reasonable price [2]. Will  
it
be easy to use the driver from current in 10-stable? Or is there a  
reason

support for this hardware is not MFC'ed?

[1] http://svnweb.freebsd.org/base?view=revisionrevision=259116
[2]
http://www.routercenter.nl/product/294857/intel-centrino-advanced-n-6235.html

A recommendation for a better supported card is also welcome.


Hi Ronald!

Try this branch:
https://github.com/opntr/opBSD/tree/op/stable/10-stable-hbsd-iwn .

I backported most of the net80211 and iwn related changes till 2014.
August to 10-STABLE in this branch.


Hi,

The card is ordered. Will try your branch soon. Is there more in that  
branch or only WiFi changes?


Cheers,
Ronald.
___
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


Re: Vbox kernel module panic on boot

2015-06-15 Thread Ronald Klop
On Sun, 14 Jun 2015 21:23:40 +0200, Marko Turk mark...@markoturk.info  
wrote:



On Fri, Jun 12, 2015 at 03:54:23PM -0400, Lowell Gilbert wrote:

You rebuilt the vbox module, yes?


No, I didn't have to before.

Thanks for the answer, I will rebuild the module and try again.

BR,
Marko


You can use PORTS_MODULES to prevent this in the future.
See https://www.freebsd.org/cgi/man.cgi?query=build(7)sektion=

Regards,
Ronald.
___
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


Re: Kernel Source - Noob question

2015-06-11 Thread Ronald Klop

On Thu, 11 Jun 2015 14:39:19 +0200, Mihai Vintila uni...@gmail.com wrote:


Seems that it's working with:
svnlite checkout https://svn0.eu.freebsd.org/base/releng/10.1 /usr/src


Well done!

;-)




Best regards,
Vintila Mihai Alexandru

On 6/11/2015 3:23 PM, Mihai Vintila wrote:

Hi,
I want to compile only mlx drivers since they don't seem available by  
default. But i'm having a hard time finding the source for FreeBSD 10.1  
p10.
Can you guys indicate what is the best way to do it without recompiling  
full kernel.
Right now i've taken the src.tgz from  
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/10.1-STABLE/

Compiled the modules but when i try to load them i end up with:

KLD mlx4.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type

Kernel i'm using is FreeBSD nvme 10.1-RELEASE-p10 FreeBSD  
10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015  
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64





___
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


iwn Intel Centrino Advanced-N 6235 support in 10-stable

2015-06-03 Thread Ronald Klop

Hello,

I see support for the 6235 in iwn(4) is committed in Dec 2013 to CURRENT  
[1]. I would like to buy one of these for a reasonable price [2]. Will it  
be easy to use the driver from current in 10-stable? Or is there a reason  
support for this hardware is not MFC'ed?


[1] http://svnweb.freebsd.org/base?view=revisionrevision=259116
[2]  
http://www.routercenter.nl/product/294857/intel-centrino-advanced-n-6235.html


A recommendation for a better supported card is also welcome.

Regards,
Ronald.
___
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


Re: zfs, cam sticking on failed disk

2015-05-07 Thread Ronald Klop
On Thu, 07 May 2015 15:23:58 +0200, Steven Hartland  
kill...@multiplay.co.uk wrote:





On 07/05/2015 14:10, Slawa Olhovchenkov wrote:

On Thu, May 07, 2015 at 02:05:11PM +0100, Steven Hartland wrote:



On 07/05/2015 13:51, Slawa Olhovchenkov wrote:

On Thu, May 07, 2015 at 01:46:40PM +0100, Steven Hartland wrote:

Yes in theory new requests should go to the other vdev, but there  
could

be some dependency issues preventing that such as a syncing TXG.

Currenly this pool must not have write activity (from application).
What about go to the other (mirror) device in the same vdev?
Same dependency?

Yes, if there's an outstanding TXG, then I believe all IO will stall.

Where this TXG released? When all devices in all vdevs report
'completed'? When at the least one device in all vdevs report
'completed'? When at the least one device in at least one vdev report
'completed'?

When all devices have report completed or failed.

Thanks for explained.


Hence if you pull the disk things should continue as normal, with the
failed device being marked as such.

I am have trouble to phisical access.
May be someone can be suggest software method to forced detach device
from system.
In 11 that should be possible with devctl, but under 10 I'm not aware of  
anything that wouldn't involve some custom kernel level code I'm afraid.





Maybe I'm talking BS here, but does 'camcontrol eject' do something on a  
disk?


Ronald.
___
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


Re: protecting some processes from out-of-swap killer

2015-04-30 Thread Ronald Klop
On Wed, 29 Apr 2015 19:09:05 +0200, David Magda dma...@ee.ryerson.ca  
wrote:



On Tue, April 28, 2015 05:51, Ronald Klop wrote:

The OS trying to kill a process is probably not what you want. So when  
you
protect(1) postgres the OS will kill another process, which I hope is  
not

running without reason.
My advice would be to
- or increase your swap space
- or tune postgresql to use less memory
- or limit tmpfs (tmpfs uses swap if RAM is short)
- or tune zfs to use less memory


Personally I didn't even know FreeBSD had an OOM killer. I regularly run
into Linux's though, but that's because by default Linux allows
over-committing of memory.

I was under the impression that FreeBSD did not over-subscribe memory,  
and

so would not allow a process to do a malloc() unless there was enough
RAM+swap to satisfy it.

Is this a mistaken assumption? (I probably have to buy the McKusick,
Neville-Neil, Watson book.)




See sysctl vm.overcommit, which is also documented here:  
https://wiki.freebsd.org/SystemTuning and in man tuning(7).


Regards,
Ronald.
___
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


Re: protecting some processes from out-of-swap killer

2015-04-28 Thread Ronald Klop
On Sat, 25 Apr 2015 13:15:32 +0200, Dmitry Morozovsky ma...@rinet.ru  
wrote:



On Sat, 25 Apr 2015, Baptiste Daroussin wrote:

 However, sometimes postgres processes got killed by 'out of swap  
space'.
 I suppose the source of problem could be that VSZ size of postgres  
processes

 (8-9 G) is bigger than swap congigured (4G).

 Is there any way to prevent this, besides reallocating space for swap?

protect(1) ?


Of course.  I really do not understand how google hides the man page  
from me.


Thanks, and sorry fot the noise.




The OS trying to kill a process is probably not what you want. So when you  
protect(1) postgres the OS will kill another process, which I hope is not  
running without reason.

My advice would be to
- or increase your swap space
- or tune postgresql to use less memory
- or limit tmpfs (tmpfs uses swap if RAM is short)
- or tune zfs to use less memory

Regards,
Ronald.
___
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


Re: hanging processes, nfs, automount

2015-03-31 Thread Ronald Klop
On Tue, 31 Mar 2015 10:24:05 +0200, Dominic Fandrey kamik...@bsdforen.de  
wrote:



I don't know where to ask this, so I'm putting it out here.

Introductions first:
FreeBSD AprilRyan.norad 10.1-STABLE FreeBSD 10.1-STABLE #2 r280373: Mon  
Mar 23 17:43:09 CET 2015  
root@AprilRyan.norad:/usr/obj/S403/amd64/usr/src/sys/S403  amd64


I have an nfs-share that I access via automount in /net/host/share.

The following scenario:
- cd /net/host/share inside tmux
- Do stuff
- S4 the laptop and take it to work the next morning
- Resume and the tmux session hangs infinitely
- Kill all shells belonging to the tmux session
- tmux server process hangs in state rpcrec

It's bad enough that there apparently is no path for NFS to fail
and reanimate the shell that accesses the share.

But the really bad problem is, that tmux in rpcrec state is not
killable. I.e. not kill -9 able. And as long as that process is around
any new tmux server I try to start just hangs.


For this killable stuff there is the 'intr' mount option. See also the  
'soft' mount option if you don't want NFS to wait indefinitely for a lost  
server.

man mount_nfs describes this all.

Regards,
Ronald.




My only recourse so far is a reboot.

___
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


Re: FreeBSD 9.2-RELEASE stability?

2013-10-01 Thread Ronald Klop

On Mon, 30 Sep 2013 21:01:26 +0200, Brett Glass br...@lariat.net wrote:

How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements  
are welcome, but there have been a few troubling messages about kernel  
panics and VM issues on the various mailing lists. It's never clear  
until the release drops whether these are actual problems with the  
software or hardware defects in individual systems, so I am eager to  
hear how the new release is working for everyone.


--Brett Glass


I agree that on the mailinglist it looks like this happens:

1. X.Y-RELEASE
2. bugfixes on X.Y-STABLE
3. half way between 2 releases X.Y-STABLE looks pretty good
4. announcement code freeze X.(Y+1)-RELEASE is coming
5. MFC all kinds of new features from -HEAD to -STABLE
6. A lot of mails about bugs and also fixes
7. X.(Y+1)-RELEASE
8. bugfixes on X.(Y+1)-STABLE
9. half way between 2 releases X.(Y+1)-STABLE is pretty good

But in the end a mailinglist is a collection of problem reports and not a  
collection of success stories. For a lot of people it runs very well and  
you never here them.

So I guess it all runs pretty well unless your system does not.

Cheers,
Ronald.
___
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


Re: Running a script via PHP

2013-10-01 Thread Ronald Klop

On Fri, 27 Sep 2013 23:50:02 +0200, Charles Swiger cswi...@mac.com wrote:


Hi--

On Sep 27, 2013, at 2:18 AM, Michael BlackHeart amdm...@gmail.com  
wrote:

Hello there,
It's quite off-topic, but I'm using freebsd-stable,so

The priblem is - running a script that requires root privileges via PHP  
(or

probably CGI - I do not care, just want it to be secure and working).


Unfortunately the combination of PHP, doing something which needs root,  
and

security are inherently contradictory.

The least risky approach would be to invoke the needed command via sudo,  
or
possibly a small setuid-root C wrapper program which launches only the  
needed script
with root permissions.  Use sudo unless your C wrapper is careful enough  
to use
exec() and not system(), sanitizes $PATH and other env variables, and  
guards against

games with $IFS, shell metachars, and such.

Regards,


Use sudo, because your home grown C wrapper will make all the mistakes  
which are already solved in sudo. Or will be spotted in the future in sudo  
and will never be spotted in your program.
Chances are high that future requirements of your C wrapper will turn it  
in a little sudo.


Ronald.
___
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


Re: lock order reversal in 10-alpha2

2013-09-27 Thread Ronald Klop
On Fri, 27 Sep 2013 05:57:45 +0200, Shane Ambler free...@shaneware.biz  
wrote:


After booting from a 10-alpha2 disk I am seeing lock order reversal  
messages show up from time to time. Current logs have 35 entries.


FreeBSD 10-ALPHA is still being build with kernel option WITNESS on. This  
gives more diagnostics of internal state of the kernel.
A lot of these LORs (Lock Order Reverals) should be fixed some day, but  
are harmless for the continues working of the machine.

If you compile FreeBSD 9 with WITNESS on, you will some LORs also.

Ronald.



The machine normally is running 9.1 from zfs root and I have setup a  
separate disk (eSATA case connected through backplane port to onboard  
SATA port) that I have installed 10-alpha amd64 onto a ufs partition to  
test port building with. I started by building 10 alpha1 and installing  
onto the new disk. I have since done svn up (last revision is 255868)  
then rebuilt and installed kernel and world while running 10 and still  
see these messages.


I mentioned the existing 9.1 on zfs which I am not importing while  
running 10 from ufs as I noticed zfs mentioned in one of the entries.


Initially I built with an empty src.conf but the last build I used the  
following -


WITH_BSD_GREP=yes
WITH_CLANG_EXTRAS=yes
WITH_CTF=yes
WITHOUT_LIB32=yes
WITH_LLDB=yes

Hardware is ASUS P8H61-M LE/USB3 corei5 8GB RAM nvidia GT520

I can provide full copy of log/messages or dmesg if required.

A few samples --

messages:Sep 26 02:01:27 leader kernel: lock order reversal:
messages-Sep 26 02:01:27 leader kernel: 1st 0xfe01eebd07f8 bufwait  
(bufwait) @ /usr/src/sys/kern/vfs_bio.c:3059
messages-Sep 26 02:01:27 leader kernel: 2nd 0xf800122f8200 dirhash  
(dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284

messages-Sep 26 02:01:27 leader kernel: KDB: stack backtrace:
messages-Sep 26 02:01:27 leader kernel: db_trace_self_wrapper() at  
db_trace_self_wrapper+0x2b/frame 0xfe0238a8f270
messages-Sep 26 02:01:27 leader kernel: kdb_backtrace() at  
kdb_backtrace+0x39/frame 0xfe0238a8f320
messages-Sep 26 02:01:27 leader kernel: witness_checkorder() at  
witness_checkorder+0xd23/frame 0xfe0238a8f3b0
messages-Sep 26 02:01:27 leader kernel: _sx_xlock() at  
_sx_xlock+0x75/frame 0xfe0238a8f3f0
messages-Sep 26 02:01:27 leader kernel: ufsdirhash_add() at  
ufsdirhash_add+0x3b/frame 0xfe0238a8f430
messages-Sep 26 02:01:27 leader kernel: ufs_direnter() at  
ufs_direnter+0x688/frame 0xfe0238a8f4f0
messages-Sep 26 02:01:27 leader kernel: ufs_makeinode() at  
ufs_makeinode+0x573/frame 0xfe0238a8f6b0
messages-Sep 26 02:01:27 leader kernel: VOP_CREATE_APV() at  
VOP_CREATE_APV+0xea/frame 0xfe0238a8f6e0
messages-Sep 26 02:01:27 leader kernel: vn_open_cred() at  
vn_open_cred+0x300/frame 0xfe0238a8f830
messages-Sep 26 02:01:27 leader kernel: kern_openat() at  
kern_openat+0x261/frame 0xfe0238a8f9a0
messages-Sep 26 02:01:27 leader kernel: amd64_syscall() at  
amd64_syscall+0x265/frame 0xfe0238a8fab0
messages-Sep 26 02:01:27 leader kernel: Xfast_syscall() at  
Xfast_syscall+0xfb/frame 0xfe0238a8fab0
messages-Sep 26 02:01:27 leader kernel: --- syscall (5, FreeBSD ELF64,  
sys_open), rip = 0x80185baca, rsp = 0x7fffd168, rbp = 0x7fffd1a0  
---


messages.0:Sep 23 10:08:11 leader kernel: lock order reversal:
messages.0-Sep 23 10:08:11 leader kernel: 1st 0xf801ba2e65f0 ufs  
(ufs) @ /usr/src/sys/kern/vfs_syscalls.c:3435
messages.0-Sep 23 10:08:11 leader kernel: 2nd 0xfe01ef93c1c0 bufwait  
(bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:262
messages.0-Sep 23 10:08:11 leader kernel: 3rd 0xf801ba2e6240 ufs  
(ufs) @ /usr/src/sys/kern/vfs_subr.c:2099

messages.0-Sep 23 10:08:11 leader kernel: KDB: stack backtrace:
messages.0-Sep 23 10:08:11 leader kernel: db_trace_self_wrapper() at  
db_trace_self_wrapper+0x2b/frame 0xfe02397c2300
messages.0-Sep 23 10:08:11 leader kernel: kdb_backtrace() at  
kdb_backtrace+0x39/frame 0xfe02397c23b0
messages.0-Sep 23 10:08:11 leader kernel: witness_checkorder() at  
witness_checkorder+0xd23/frame 0xfe02397c2440
messages.0-Sep 23 10:08:11 leader kernel: __lockmgr_args() at  
__lockmgr_args+0x6f2/frame 0xfe02397c2570
messages.0-Sep 23 10:08:11 leader kernel: ffs_lock() at  
ffs_lock+0x84/frame 0xfe02397c25c0
messages.0-Sep 23 10:08:11 leader kernel: VOP_LOCK1_APV() at  
VOP_LOCK1_APV+0xf5/frame 0xfe02397c25f0
messages.0-Sep 23 10:08:11 leader kernel: _vn_lock() at  
_vn_lock+0xab/frame 0xfe02397c2660
messages.0-Sep 23 10:08:11 leader kernel: vget() at vget+0x70/frame  
0xfe02397c26b0
messages.0-Sep 23 10:08:11 leader kernel: vfs_hash_get() at  
vfs_hash_get+0xf5/frame 0xfe02397c2700
messages.0-Sep 23 10:08:11 leader kernel: ffs_vgetf() at  
ffs_vgetf+0x41/frame 0xfe02397c2790
messages.0-Sep 23 10:08:11 leader kernel: softdep_sync_buf() at  
softdep_sync_buf+0x8fa/frame 0xfe02397c2840
messages.0-Sep 23 10:08:11 leader kernel: ffs_syncvnode() at  

Re: Running a script via PHP

2013-09-27 Thread Ronald Klop
On Fri, 27 Sep 2013 11:18:40 +0200, Michael BlackHeart amdm...@gmail.com  
wrote:



Hello there,
It's quite off-topic, but I'm using freebsd-stable,so

The priblem is - running a script that requires root privileges via PHP  
(or

probably CGI - I do not care, just want it to be secure and working).

It's all about minidlna service (I use upnp to so mediatomb and other are
no options). On FreeBSD it should be resync-ed manually, so I've got a
simple script placed in /etc/periodic/daily:

more 957.dlna_update
#!/bin/sh
#Script to daily update minidlna DB

a=$*

if (/usr/local/etc/rc.d/minidlna stop 1/dev/null);then
sleep 10
if /usr/local/etc/rc.d/minidlna rescan;then
/usr/bin/logger -t minidlna DB updated.
exit 0
else
/usr/bin/logger -t minidlna Error. Failed to update DB.
exit 1
fi
else
/usr/bin/logger -t minidlna Error. Failed to update DB.
exit 1
fi

And it's working fine to me. But it uses service infrastructure. So when
I'm trying to run via PHP it fails. For example running under  
unprivileged

user:

id
uid=1001(amd_miek) gid=0(wheel) groups=0(wheel),5(operator)

-rwsr-sr-x 1 root wheel 394 27 сен 10:58 957.dlna_update*

sh -x 957.dlna_update
+ a=''
+ /usr/local/etc/rc.d/minidlna stop
kill: 10786: Operation not permitted
+ /usr/bin/logger -t minidlna 'Error. Failed to update DB.'
+ exit 1

What is the best way to run it via WEB?


You can't setuid a shell script. The executable actually is '/bin/sh'  
which just reads the shell script. So you should setuid /bin/sh which is a  
security problem.

You can use sudo to do this. (/usr/ports/security/sudo)

Ronald.
___
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

Re: Fwd: Package database

2013-09-06 Thread Ronald Klop

Than I'll top-post too. Anyway. Try this:

$ ls -al /var/backups/
total 16417
drwxr-x---   2 root  wheel   10 Sep  6 03:03 ./
drwxr-xr-x  25 root  wheel   25 Sep  5 14:42 ../
-rw-r--r--   1 root  wheel 1688 Dec  6  2012 aliases.bak
-rw-r--r--   1 root  wheel 1665 Aug  4  2011 aliases.bak2
-rw-r--r--   1 root  wheel  761 Feb  6  2013 group.bak
-rw-r--r--   1 root  wheel  761 Jan  2  2013 group.bak2
-rw---   1 root  wheel 2994 Feb  6  2013 master.passwd.bak
-rw---   1 root  wheel 2994 Jan  2  2013 master.passwd.bak2
-rw-r--r--   1 root  wheel  8362370 Sep  6 03:03 pkgdb.bak.tbz
-rw-r--r--   1 root  wheel  8362370 Sep  5 03:03 pkgdb.bak.tbz.2



On Thu, 05 Sep 2013 14:52:06 +0200, Jim Ballantine  
j.ballant...@gmail.com wrote:



Sorry these didn't get to the list.
gmail responses only to sender and not cc,
it also seems to top post.

-- Forwarded message --
From: Jim Ballantine j.ballant...@gmail.com
Date: Wed, Sep 4, 2013 at 3:09 PM
Subject: Re: Package database
To: Freddie Cash fjwc...@gmail.com


I looked in /var/db and there is not dir/file named backup.  There is a  
dir

named pkg.bak but it is empty.


On Wed, Sep 4, 2013 at 1:46 PM, Jim Ballantine  
j.ballant...@gmail.comwrote:



I'm trying to upgrade with portmaster and getting:

portmaster -Gadv
=== Sorting ports by category
=== Gathering distinfo list for installed ports

=== No ORIGIN in /var/db/pkg/ORBit2-2.14.19/+CONTENTS

=== No ORIGIN in /var/db/pkg/R-3.0.1/+CONTENTS



On Wed, Sep 4, 2013 at 1:43 PM, Freddie Cash fjwc...@gmail.com wrote:

On Wed, Sep 4, 2013 at 10:41 AM, Jim Ballantine  
j.ballant...@gmail.comwrote:


My /var/db/pkg has become corrupt, and I can't find an archive of it  
to

install in it's place.  Does one exist and if so where?  If not any
ideas on
how to rebuild the db?



Are you using PKGng or the old pkg_* tools?

Meaning, is your data stored as individual files under
/var/db/pkg/PORTNAME/*, or as a single sqlite database under  
/var/db/pkg?


If using PKGng, there's a backup copy under /var/db/backup*

If using the older pkg_* tools, you're screwed.  :)


--
Freddie Cash
fjwc...@gmail.com





___
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


Re: Requesting Technical Assistance

2013-09-05 Thread Ronald Klop

On Thu, 05 Sep 2013 02:54:12 +0200, No Wait suko...@hotmail.com wrote:


Hello.

For the last 3 weeks or so, I've been unable to load AFF properly.

The page comes up, but the hyperlinks are placed oddly and I get  
placeholders instead of pictures.  I can't even check messages.


I appreciate any insight you might have.  Thank you in advance!

Username = Sukokov




I have no idea what you are talking about. Maybe the wrong mailinglist?

Ronald.
___
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


Re: Boot problem if a ZFS log device is missing

2013-08-30 Thread Ronald Klop
On Fri, 30 Aug 2013 12:58:29 +0200, Johan Hendriks  
joh.hendr...@gmail.com wrote:



Maurizio Vairani wrote:

On 29/08/2013 11.01, Andriy Gapon wrote:

on 29/08/2013 11:27 Maurizio Vairani said the following:
I am able to boot the PC without a cache device but not without a log  
device. Why ?
The log could potentially contain uncommitted entries.  Without the  
log device
there is no knowing if it did or did not.  And if it did then the pool  
is
inconsistent state without the log device and so it can not be  
imported.


The cache is not persistent and so there is nothing needed from it  
upon a boot.



Thank you for the clear and concise reply.

Yesterday I have done some test. If I remove the stick from the USB  
port, before the shutdown the PC, it  don't crash but continues to  
works. Then  I am able to reboot the laptop without inserting the stick  
with a pool that works in degraded mode.


From the end user point of view a PC should always boot, even with a  
missing ZFS log device.


Regards
Maurizio

___
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to freebsd-fs-unsubscr...@freebsd.org

I do not agree with the following.
 From the end user point of view a PC should always boot, even with  
a missing ZFS log device.


I think it should give you a option to import the pool or not import the  
pool!
There could be a situation when you are not sure that the ZIL is  
commited, in that situation it would be handy if you can suspend the  
boot and make sure the ZIL is there when you reboot or import after you  
attached the ZIL.
I would hate it when it corrups my data just because we always import.  
with or without the ZIL.


In your test you remove the ZIL, and when you reboot then it imports  
correctly, as far as my knowledge goes this is ok, because when the pool  
is exported there is no left data in the ZIL, it was not there when we  
exported, so we can import even without the missing ZIL without problem.


I think he was just lucky his system wasn't writing a lot to the ZIL at  
the moment of removal. So his system was in a consistent state. Otherwise  
you just miss data which is in the ZIL and not on disk.
BTW: Not everything goes through the ZIL. It is not the same as a journal.  
Only sync writes go to the ZIL. If you don't use databases or NFS or other  
software which wants to make sure data is on stable storage, you might  
rarely use the ZIL.


Ronald.



regards
Johan





___
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


Re: how to remove usb-storage devices without CAM errors

2013-08-08 Thread Ronald Klop
On Thu, 08 Aug 2013 05:56:21 +0200, Michael Schuh  
michael.sc...@gmail.com wrote:



H i@list,

i have a simple wuestion caused by a device loss.

is there a special routine for unplugging usb-storage devices?
in the meaning:
may be settle some commends before unplugging the device
other than umount.
according to the handbook there ist no special routine.
unmounting should be enough and pull the USB-Devie out of the bus.

i could not find anything related by the help of the big oracle.


i have some usb-sticks that i need to write with prepared disk-images by
using dd.
two or more drives are already plugged in
and da0 is already finished, da1 or da2 still at writing.
unplugging da0 causes a CAM error and interrupts the ongoing write.
i am not sure if all writes to each different device gets stopped.
this is a reproduceable behaviour thats new to me.
see the listing below.

let me know if i can and what to do to help to further identify
and investigate this error.

iirc this happens for the first time this way.
my last upgrade before this was feb./march.
time of svn checkout was 2013-07-22 so its may be already fixed?

many thanks in advance

regards

michael




Does 'camcontrol eject device_id' help? It tells CAM to eject the  
device. This is usefull for CD's, but maybe to for preventing errors for  
USB-storage.


Ronald.





===

ugen3.2: Verbatim at usbus3
umass0: Verbatim STORE N GO, class 0/0, rev 2.10/1.10, addr 2 on usbus3
umass0:  SCSI over Bulk-Only; quirks = 0x0100
umass0:8:0:-1: Attached to scbus8
da0 at umass-sim0 bus 0 scbus8 target 0 lun 0
da0: Verbatim STORE N GO PMAP Removable Direct Access SCSI-6 device
da0: 40.000MB/s transfers
da0: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C)
da0: quirks=0x2NO_6_BYTE
ugen7.2: Verbatim at usbus7
umass1: Verbatim STORE N GO, class 0/0, rev 2.10/1.10, addr 2 on usbus7
umass1:  SCSI over Bulk-Only; quirks = 0x0100
umass1:9:1:-1: Attached to scbus9
da1 at umass-sim1 bus 1 scbus9 target 0 lun 0
da1: Verbatim STORE N GO PMAP Removable Direct Access SCSI-6 device
da1: 40.000MB/s transfers
da1: 7385MB (15124992 512 byte sectors: 255H 63S/T 941C)
da1: quirks=0x2NO_6_BYTE
(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00
ugen3.2: Verbatim at usbus3 (disconnected)
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
umass0: (da0:at uhub3, port 3, addr 2 (disconnected)
umass-sim0:0:0:0): Retrying command
(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command
(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 02 44 80 00 00 80 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Error 5, Retries exhausted
(da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00  
00

00 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command
(da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00  
00

00 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Error 5, Retries exhausted
(da0:umass-sim0:0:0:0): got CAM status 0x44
(da0:umass-sim0:0:0:0): fatal error, failed to attach to device
(da0:umass-sim0:0:0:0): lost device - 0 outstanding, 5 refs
(da0:umass-sim0:0:0:0): removing device entry
___
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


Re: Bind in FreeBSD, security advisories

2013-07-30 Thread Ronald Klop
On Tue, 30 Jul 2013 15:32:44 +0200, Daniel Kalchev dan...@digsys.bg  
wrote:




On 30.07.13 16:13, Mehmet Erol Sanliturk wrote:




On Tue, Jul 30, 2013 at 8:47 AM, Daniel Kalchev dan...@digsys.bg  
mailto:dan...@digsys.bg wrote:



Going that direction, we should consider Comrade Stalin's maxim
FreeBSD exists, there are problems, here is the solution -- no
FreeBSD, no problems! :-)

Daniel




Then , there exists a new problem :


There is no FreeBSD ...


We already know Comrade Stalin's solution had... bugs. Not before  
millions parted with their lives...


When/if we remove BIND from FreeBSD, we might find out whether that  
solution has bugs, or not. Not until then, though.


Back to the topic :)

My take on this is that removing BIND from the base today is..  
irresponsible. First, most who use FreeBSD expect an DNS server to be  
readily available.


Interesting. What are your statistics of 'most' based on?

Ronald.


Some people would just avoid to use any ports etc.
BIND in base is well tested and known evil. If we are ever to replace it  
with something else, that something else has to prove itself -  
demonstrate that it is at least as good as BIND -- in the base system.  
In practice, not in theory.


This is very much an situation like replacing gcc with clang/llvm.  
However, in the case of BIND we have no licensing problems, stability  
problems, performance problems etc --- just concerns that BIND generates  
many SAs -- which might be actually good indicator, as it demonstrates  
that BIND is worked on.


I personally see no reason to remove BIND from base. If someone does not  
want BIND in their system, they could always use the WITHOUT_BIND build  
switch.


Daniel
___
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


Re: Bind in FreeBSD, security advisories

2013-07-30 Thread Ronald Klop

On Tue, 30 Jul 2013 16:04:46 +0200, Mark Felder f...@freebsd.org wrote:


On Tue, Jul 30, 2013, at 8:32, Daniel Kalchev wrote:



This is very much an situation like replacing gcc with clang/llvm.
However, in the case of BIND we have no licensing problems, stability
problems, performance problems etc --- just concerns that BIND generates
many SAs -- which might be actually good indicator, as it demonstrates
that BIND is worked on.



There's a man with a name whose initials match DJB that would strongly
disagree. Now he's not always the best person to reference, but he's
made a succinct point with his own software, whether or not you like
using it.

Unbound/NSD are suitable replacements if we really need something in
base, and they have been picked up by OpenBSD for a good reason --
clean, secure, readable, maintainable codebases and their use across the
internet and on the ROOT servers is growing.


I personally see no reason to remove BIND from base. If someone does not
want BIND in their system, they could always use the WITHOUT_BIND build
switch.


I'd be inclined to agree if it wasn't such a wholly insecure chunk of
code. You don't see people whining about Sendmail in base when they
prefer Postfix or Exim, but Sendmail doesn't have a new exploit every
week. You do tend to need an MTA for getting messages off the system
more than you need a local recursor/cache, but at least it's not causing
you maintenance headaches. If you consider the possibility that a large
enough percentage of users really desire a local recursor/cache it
should be our duty to give them the best option available.



DragonflyBSD also removed BIND from base some time ago.
http://www.shiningsilence.com/dbsdlog/2010/05/06/5853.html

Ronald.
___
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


Re: Bind in FreeBSD, security advisories

2013-07-30 Thread Ronald Klop
On Tue, 30 Jul 2013 15:53:08 +0200, Tim Daneliuk tun...@tundraware.com  
wrote:



On 07/30/2013 08:13 AM, Mehmet Erol Sanliturk wrote:
On Tue, Jul 30, 2013 at 8:47 AM, Daniel Kalchev dan...@digsys.bg  
wrote:




On 30.07.13 15:21, Mark Felder wrote:


People don't seem upset about not having a webserver, IMAP/POP daemon,
or LDAP server in base, so I don't understand what the big deal is  
about

removing BIND.



I believe the primary reason these things are not in the base system is
that they have plenty of dependencies, with possibly conflicting  
licenses

etc.

  If the concern is over the rare case when you absolutely
need a DNS recursor and there are none you can reach I suppose we  
should

just import Unbound.



There are many and good reasons to include an fully featured name  
server,
or at least full recursive resolver. For example, for properly  
supporting

DNSSEC.
We could in theory remove the BIND's authoritative name server
executable... if that is attracting the SAs.

The justification reduce the number of SA's, that is, the bad PR is
probably not enough. Going that direction, we should consider Comrade
Stalin's maxim FreeBSD exists, there are problems, here is the  
solution --

no FreeBSD, no problems! :-)

Daniel





Then , there exists a new problem :


There is no FreeBSD ...


Thank you very much .




Exactly.  Either strip everything out of the base
including things like perl or admit that there is more
to a modern OS than just kernel and admin tools.





You have perl in base?
http://bsd.slashdot.org/story/02/05/14/0015234/freebsd-perl-to-be-removed
;-)

Ronald.
___
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


Re: Bind in FreeBSD, security advisories

2013-07-30 Thread Ronald Klop

On Tue, 30 Jul 2013 16:07:30 +0200, Mark Felder f...@freebsd.org wrote:


On Tue, Jul 30, 2013, at 8:42, sth...@nethelp.no wrote:


and every contrib part which is removed, detracts from this.



And every contrib part that is added to base is another piece of
software that rots for the life of a major release and ends up getting
replaced by frustrated endusers with the latest in ports...

The tight integration of the base system that everyone appreciates and
respects is far below high-level software like BIND.


+1

___
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


Re: Bind in FreeBSD, security advisories

2013-07-30 Thread Ronald Klop

On Tue, 30 Jul 2013 16:14:57 +0200, Freddie Cash fjwc...@gmail.com wrote:

On 2013-07-30 12:55 AM, David Demelier demelier.da...@gmail.com  
wrote:


Hi,

For years, a lot of security advisories have been present for bind.
I'm just guessing if it's not a good idea to remove bind from base?

This will probably free by half the number of FreeBSD SA's in the  
future.


Hasn't this discussion occurred several times already on the -current
mailing list over the past year?


http://lists.freebsd.org/pipermail/freebsd-hackers/2012-July/039830.html


And hadn't unbound and/or ldns been
imported into - current already?


http://lists.freebsd.org/pipermail/svn-src-all/2012-July/056004.html
And next messages.

Regards,
Ronald.
___
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


Re: Bind in FreeBSD, security advisories

2013-07-30 Thread Ronald Klop
On Tue, 30 Jul 2013 16:55:09 +0200, Ronald Klop  
ronald-freeb...@klop.yi.org wrote:


On Tue, 30 Jul 2013 16:14:57 +0200, Freddie Cash fjwc...@gmail.com  
wrote:


On 2013-07-30 12:55 AM, David Demelier demelier.da...@gmail.com  
wrote:


Hi,

For years, a lot of security advisories have been present for bind.
I'm just guessing if it's not a good idea to remove bind from base?

This will probably free by half the number of FreeBSD SA's in the  
future.


Hasn't this discussion occurred several times already on the -current
mailing list over the past year?


http://lists.freebsd.org/pipermail/freebsd-hackers/2012-July/039830.html


And hadn't unbound and/or ldns been
imported into - current already?


http://lists.freebsd.org/pipermail/svn-src-all/2012-July/056004.html
And next messages.


Even more:
http://svnweb.freebsd.org/base/head/contrib/ldns/
http://svnweb.freebsd.org/base/head/contrib/unbound/


Regards,
Ronald.
___
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


Re: zpool on a zvol inside zpool

2013-07-25 Thread Ronald Klop
On Mon, 22 Jul 2013 10:04:19 +0200, Eugene M. Zheganin e...@norma.perm.ru  
wrote:



Hi.

I'm moving some of my geli installation to a new machine. On an old
machine it was running UFS. I use ZFS on a new machine, but I don't have
an encrypted main pool (and I don't want to), so I'm kinda considering a
way where I will make a zpool on a zvol encrypted by geli. Would it be
completely insane (should I use UFS instead ?) or would it be still
valid  ?

Thanks.
Eugene.


I think that depends on your configuration and situation.
If you have a spare disk to use for GELI+UFS. That is more simple to  
configure/maintain.
But if you are running a big fileserver than the overhead of ZFS+GELI+UFS  
might be negligible.


Ronald.
___
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


Re: [SOLVED] Re: Shutdown problem with an USB memory stick as ZFS cache device

2013-07-24 Thread Ronald Klop
On Thu, 18 Jul 2013 09:52:13 +0200, Maurizio Vairani  
maurizio.vair...@cloverinformatica.it wrote:



On 17/07/2013 17:29, Julian H. Stacey wrote:

Maurizio Vairani wrote:

On 17/07/2013 11:50, Ronald Klop wrote:

On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani
maurizio.vair...@cloverinformatica.it  wrote:


Hi all,


on a Compaq Presario laptop I have just installed the latest stable


#uname -a

FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16
16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC   
amd64



For speed up the compilation I have added to the pool, tank0,  a
SanDisk memory stick as cache device with the command:


# zpool add tank0 cache /dev/da0


But when I shutdown the laptop the process will halt with this screen
shot:


http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html



and I need to press the power button for more than 4 seconds to
switch off the laptop.

The problem is always reproducible.

Does sysctl hw.usb.no_shutdown_wait=1 help?

Ronald.

Thank you Ronald it works !

In /boot/loader.conf added the line
hw.usb.no_shutdown_wait=1

Maurizio

I wonder (from ignorance as I dont use ZFS yet),
if that merely masks the symptom or cures the fault ?

Presumably one should use a ZFS command to disassociate whatever
might have the cache open ?  (in case something might need to be
written out from cache, if it was a writeable cache ?)

I too had a USB shutdown problem (non ZFS, now solved)  several people
made useful comments on shutdown scripts etc, so I'm cross referencing:

http://lists.freebsd.org/pipermail/freebsd-mobile/2013-July/012803.html

Cheers,
Julian
Probably it masks the symptom. Andriy Gapon hypothesizes a bug in the  
ZFS clean up code:

http://lists.freebsd.org/pipermail/freebsd-fs/2013-July/017857.html

Surely one can use a startup script with the command:
zpool add tank0 cache /dev/da0
and a shutdown script with:
zpool remove tank0 /dev/da0
but this mask the symptom too.

I prefer the Ronald solution because:
- is simpler: it adds only one line (hw.usb.no_shutdown_wait=1) to one  
file (/boot/loader.conf).
- is fastest: the zpool add/remove commands take time and  
“hw.usb.no_shutdown_wait=1” in /boot/loader.conf speeds up the shutdown  
process.
- is cleaner: the zpool add/remove commands pair will fill up the tank0  
pool history.


Regards
Maurizio


Keep an eye on this commit when it is merged to 9-stable.
http://svnweb.freebsd.org/changeset/base/253606
It might be the fix of the problem.

Ronald.
___
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

Re: stopping amd causes a freeze

2013-07-22 Thread Ronald Klop
On Mon, 22 Jul 2013 14:19:44 +0200, Dominic Fandrey kamik...@bsdforen.de  
wrote:



On 22/07/2013 12:07, Konstantin Belousov wrote:

On Mon, Jul 22, 2013 at 11:50:24AM +0200, Dominic Fandrey wrote:

Occasionally stopping amd freezes my system. It's a rare occurrence,
and I haven't found a reliable way to reproduce it.

It's also a real freeze, so there's no way to get into the debugger
or grab a core dump. I only can perform the 4 seconds hard shutdown to
revive the system.

I run amd through sysutils/automounter, which is a scripting solution
that generates an amd.map file based on encountered devices and devd
events. The SIGHUP it sends to amd to tell it the map file was updated
does not cause problems, only a SIGKILL may cause the freeze.

Nothing was mounted (by amd) during the last freeze.

I don't see any angle to tackle this, but I'm throwing it out here
any way, in the hopes that someone actually has an idea how to approach
the issue.


Are you sure that the machine did not paniced ?  Do you have serial  
console ?


No, I don't have one. All that I can tell is that everything freezes
(i.e. Xorg screen and mouse). ACPI events like shutdown don't cause a
reaction. And the system doesn't respond to ICMP queries.


The amd(8) locks itself into memory, most likely due to the fear of
deadlock. There are some known issues with user wirings in stable/9.
If the problem you see is indeed due to wiring, you might try to apply
r253187-r253191.


From head? That may be worth a try. It would be better for testing if I
managed to reproduce the problem reliably, before I test patches.

I see it's scheduled for MFC, soon.



Did you try a run with the INVARIANTS, etc. options in the kernel? That  
enables more sanity checking for locks which is too slow for production.


Ronald.
___
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


Re: Shutdown problem with an USB memory stick as ZFS cache device

2013-07-17 Thread Ronald Klop
On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani  
maurizio.vair...@cloverinformatica.it wrote:



Hi all,


on a Compaq Presario laptop I have just installed the latest stable


#uname -a

FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16  
16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC  amd64



For speed up the compilation I have added to the pool, tank0,  a SanDisk  
memory stick as cache device with the command:



# zpool add tank0 cache /dev/da0


But when I shutdown the laptop the process will halt with this screen  
shot:



http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html


and I need to press the power button for more than 4 seconds to switch  
off the laptop.


The problem is always reproducible.


Does sysctl hw.usb.no_shutdown_wait=1 help?

Ronald.
___
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


Re: What are the ideal ranges for kern.ipc.shm*?

2013-07-12 Thread Ronald Klop

On Fri, 12 Jul 2013 05:24:55 +0200, Chris H bsd-li...@1command.com wrote:


Greetings,
 Over the years using the xfce4 desktop, I would occasionally receive
SHM ERROR messages. As they never interfered (so's I could notice), I
always put off attempting to track the cause down. However, now having
performed a fairly major upgrade (~1yr since last), The error appears
to greatly affect KDE4 (used to use kde3) applications I run within
xfce4. The windows don't re-draw correctly, and I receive additional
errors,as well:
...
Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
QCoreApplication::postEvent: Unexpected null receiver
...
After much searching, it would appear to be related to the
kern.ipc.shm* values.
pertinent details follow:
FreeBSD udns 8.4-STABLE FreeBSD 8.4-STABLE #3: Tue Jul  2 13:41:21 PDT  
2013

root@udns:/usr/obj/usr/src/sys/AMD64  amd64
with 64Gb ram, and 3 cores, and nvidia-driver-308.88_1.
# ipcs -M
shminfo:
shmmax: 33554432(max shared memory segment size)
shmmin:1(min shared memory segment size)
shmmni:  192(max number of shared memory identifiers)
shmseg:  128(max shared memory segments per process)
shmall: 8192(max amount of shared memory in pages)


My 9.1-STABLE amd64 with 4GB RAM has these default settings:
ipcs -M
shminfo:
shmmax:536870912(max shared memory segment size)
shmmin:1(min shared memory segment size)
shmmni: 1024(max number of shared memory identifiers)
shmseg: 1024(max shared memory segments per process)
shmall:   131072(max amount of shared memory in pages)

Regards,
Ronald.
___
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


Re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade?

2013-06-28 Thread Ronald Klop

On Thu, 27 Jun 2013 16:14:31 +0200, Chris H bsd-li...@1command.com wrote:


Warren Block wrote:

On Wed, 26 Jun 2013, Chris H wrote:

On Wed, 26 Jun 2013, Chris H wrote:

Okay, look up the last time you installed or upgraded a port:
% ls -ltr /var/db/pkg

The last one is the most recently modified. Update your ports tree,
follow all the steps that apply to your system since that date.


That should say all the steps in /usr/ports/UPDATING that apply to  
your

system since that date.


There is a nice command that helps you to list only relevant entries
from UPDATING (entries from UPDATING for already installed ports)

pkg_updating -d MMDD

Where MMDD is the last time you did ports update, for example
pkg_updating -d 20120923

Miroslav Lachman

Greetings Miroslav,
That _is_ nice. Thank you for taking the time post this.
That'll help quite a bit!


/usr/ports/ports-mgmt/portupdate-scan is also very usefull

Ronald.
___
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


Re: shutdown -r / shutdown -h / reboot all hang and don't cleanly dismount

2013-06-19 Thread Ronald Klop
On Wed, 19 Jun 2013 14:53:19 +0200, Adam Strohl  
adams-free...@ateamsystems.com wrote:



On 6/19/2013 19:21, Jeremy Chadwick wrote:

On Wed, Jun 19, 2013 at 06:35:57PM +0700, Adam Strohl wrote:

Hello -STABLE@,

So I've seen this situation seemingly randomly on a number of both
physical 9.1 boxes as well as VMs for I would say 6-9 months at
least.  I finally have a physical box here that reproduces it
consistently that I can reboot easily (ie; not a production/client
server).


Hi,

My home computer had the same symptom (not rebooting after 'all buffers  
flushed' message) a couple of months ago. But I follow 9-STABLE and the  
problem is gone for a while now.


Ronald.



No matter what I do:

reboot
shutdown -p
shutdown -r

This specific server will stop at All buffers synced and not
actually power down or reboot.  KB input seems to be ignored.  This
server is a ZFS NAS (with GMIRROR for boot blocks) but the other
boxes which show this are using GMIRRORs for root/swap/boot (no
ZFS).

Here is what happens on the console: http://i.imgur.com/1H8JMyB.jpg

When I reset the server it appears that disks were not dismounted
cleanly ... on this ZFS box it comes back quick because ZFS is good
like that but on the other servers with GMIRROR roots rebuilding the
GMIRROR and fscking at the same time is murder on the
disk/performance until it finishes.


1. You mention as well as VMs.  Anything under a virtual machine or
under a hypervisor is going to be very, very, **VERY** different than
bare metal.  So I hope the issues you're talking about above are on bare
metal -- I will assume so.


Nope, I see basically the same thing sometimes under ESXi 5.0 Hypervisor  
(and yes it worries me the implications of something so broad).  Those  
unites I just haven't been able to isolate on a server which isn't  
critical.  Lets focus on this server for now though per your suggestion  
below.




2. We need to know what version of 9.1 you're using, i.e. 9.1-RELEASE.
If you use stable/9 (RELENG_9) we need to see uname -a output (you can
hide the machine name if you want).


Sorry, this ZFS box is 9.1-R P4 (kernel built today):

FreeBSD ilos.dsn 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #6: Wed Jun 19  
15:31:12 ICT 2013 root@hostname:/usr/obj/usr/src/sys/ATEAMSYSTEMS   
amd64




3. Can we please have dmesg from this machine?  The controller and some
other hardware details matter.


Sure take a look at the full log here: http://pastebin.com/k55gVVuU

This includes a boot, then a reboot as I describe (you can see it logs  
the All Buffers Synced, etc) then powering back on.




4. Does sysctl hw.usb.no_shutdown_wait=1 help you?


Weirdly this allowed it to reboot on the first try (without needing to  
be reset), but not the second.  The Starting background file system  
checks in 60 seconds message appeared ... that only happens when  
something is dirty, right?


So the second try with just this I could ctrl alt del it and it  
responded .. kind of:

http://i.imgur.com/POAIaNg.jpg

Still had to reset it though.



5. Does sysctl hw.acpi.handle_reboot=1 help you?


No change, still responded to a ctrl alt del like above, but like that  
still needs to be reset and comes back dirty.




6. Does sysctl hw.acpi.disable_on_reboot=1 help you?


No change.  Same as above, ctrl alt del responds but needs a hard reset  
still.




7. If none of the above helps, can you please boot verbose mode and then
when the system locks up on shutdown -r now take a picture of the
VGA console?


Lots of debug on boot obviously but not much different on shutdown/hang:
http://i.imgur.com/SgzSsoP.jpg



8. Does the machine run moused(8) (check the process list please, do not
rely on rc.conf) ?


ps -auxww | grep moused reveals nothing running (which is how I have  
things set).





Another interesting thing is that this particular server runs slapd
(OpenLDAP) which, when it comes back up, has a corrupted DB
(easily fixed with db_recover, but still).  This might be because FS
commits aren't happening at the end.   I can even manually stop
slapd (service slapd stop) then run sync(8) (I assume this does
something for ZFS too) and it still comes back as hosed if I reboot
shortly after.  If I start/stop slapd it's fine.  So I feel like
there is an FS/dismount thing going on here.


sync(8) does not do what you think it does.  Please read (not skim) this
entire thread starting here:

http://lists.freebsd.org/pipermail/freebsd-fs/2013-April/thread.html#16982
http://lists.freebsd.org/pipermail/freebsd-fs/2013-April/016982.html


Groking this now ..



Your problem is related to unclean shutdown; fix that and your issues go
away.


Yeah that is my feeling as well.




Additional information: I also have some boxes which will reboot
(ie; they don't freeze like some do at the end) but they don't
dismount cleanly either and have to rebuild both GMIRROR and fsck.
This might be a different issue, too.


Every issue needs to be handled/treated separately.


Sure, I 

Re: Weird I/O hangs (9.1R, arcsas, interrupt spikes on uhci0)

2013-06-19 Thread Ronald Klop

On Wed, 19 Jun 2013 15:01:14 +0200, Dennis Kögel d...@neveragain.de wrote:


Hi,

very periodically, we see I/O hangs for about 10 seconds, roughly once  
per minute.


Each time this happens, the I/O rate simply drops to zero, and all disk  
access hangs; this is also very noticeable on the shell, for NFS clients  
etc. Everything else (networking, kernel, …) seems to continue normally.


Environment: FreeBSD 9.1R GENERIC on amd64, using ZFS, on a ARC1320 PCIe  
with 24x Seagate ST33000650SS (3rd party arcsas.ko driver).


It's easy to observe these hangs under write load, e.g. with 'zpool  
iostat 1':


void22.4T  42.6T 34  2.73K  1.07M   293M
void22.4T  42.6T 20  2.74K   623K   289M
void22.4T  42.6T144  2.62K  4.83M   279M
void22.4T  42.6T 13  2.60K   437K   283M
void22.4T  42.6T  0  0  0  0 -- hang starts
void22.4T  42.6T  0  0  0  0
void22.4T  42.6T  0  0  0  0
void22.4T  42.6T  0  0  0  0
void22.4T  42.6T  0  0  0  0
void22.4T  42.6T  0  0  0  0
void22.4T  42.6T  0  0  0  0
void22.4T  42.6T  0  0  0  0
void22.4T  42.6T  0296  4.00K  34.2M -- hang ends
void22.4T  42.6T  2  2.64K  73.8K   288M
void22.4T  42.6T  8  3.12K   278K   329M

Each time this happens, there is a completely unexplained spike of  
interrupts on uhci0: 'systat -vm' then displays numbers around 270k.


# vmstat -i | grep -E '(arcsas|uhci0|Total)'
irq16: uhci0  1227020890  67708
irq24: arcsas0  12045211664
Total 1266417827  69882

Things to note:

- Booting an USB-less kernel or disabling all USB in the BIOS doesn't  
change a thing (no interrupt spikes to be seen, but the hangs remain)
- The hangs / interrupt spikes happen just as often when the system is  
idle

- Board is a Supermicro x8dth
- There's two igb cards
- Root is ZFS as well (separate pool though)
- BIOS, Areca FW and driver already are latest versions
- Putting the controller to a different slot doesn't change the behaviour
- We have two identical systems and both show the exact same symptoms,  
so flaky hardware is probably not the issue


Any ideas would be appreciated.

Thanks,
D.


First send more information about the system:
- The content of /var/run/dmesg.boot.
- Install /usr/ports/sysutils/zfs-stats and send the output of zfs-stats  
-a.

- Send the output of zpool status + zpool list.
- Did you configure compression or dedup on the pool?
- Do you keep a lot of snapshots?
- Do you run a cronjob every minute which does something with the pool?  
Gathers statistics or something like that.


Ronald.
___
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

Re: ZFS crashing while zfs recv in progress

2013-05-29 Thread Ronald Klop
On Wed, 29 May 2013 11:04:00 +0200, Pascal Braun, Continum  
pascal.br...@continum.net wrote:




Hi,


I'm trying to send a zfs pool from an old freebsd 9.0 installation to a  
new machine with freebsd 9.1. The pool is quite heavy (about 16TB, lots  
of snapshots) and the receiving side keeps crashing on me. The command  
used to transfer (run on the old 9.0 installation):

zfs send -R tank@snapshot | ssh 10.10.xx.xx zfs recv -F -d -v tank


After a few hours the system stops all writing and I can't start any new  
processes. Processes still running like 'zpool iostat' are still  
working, or at least it is still reporting something. To me it looks  
like the filesystem just disappeared. Unfortunately I'm running root on  
zfs so I don't have any logs about this.
The only message I sometimes find on the console are about not being  
able to write to swap, which is also on zfs.



Do you have any ideas? I don't even know where to start.



Please send more information about the new server. Sometimes there are  
bugs found in drivers with large disks, etc. Or firmware of hardware.

The contents of /var/run/dmesg.boot is interesting to a lot of people.
As is the output of zpool status.

As you are having trouble with swap on zfs. Is it possible to put that on  
a separate disk for the test?


Ronald.
___
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


Re: Swap Warning Message?

2013-05-23 Thread Ronald Klop

On Thu, 23 May 2013 14:55:20 +0200, Michael Gass mg...@csbsju.edu wrote:


Updated 9.1 to 9 stable on an old PII with 256 MB of memory.
(FreeBSD runs fine on this machine).  After updating have
been getting the following warning on startup:

warning: total configured swap (524288 pages) exceeds maximum recommended
amount (497056 pages).
warning: increase kern.maxswzone or reduce amount of swap space.

I allocated 2.0 GB of swap when I installed.  This was not a problem
in the past.

Should I ignore this warning or do I need to do something?


Do you ever use that amount of swap?
Swap needs some memory for administration of which page goes where so it  
has a cost to increase swap too much.
If you are swapping 2 GB on 256 MB I don't think you have a very usable  
machine, but I don't know the details of what you are doing. Maybe your  
swap is on very fast SSD.


My advice would be to monitor your swap usage and reduce the amount of  
swap to a little more than you really use. Probably 1 or 2 times the  
amount of RAM.


Ronald.
___
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


Re: still mbuf leak in 9.0 / 9.1?

2013-05-18 Thread Ronald Klop

On Fri, 17 May 2013 19:31:01 +0200, Jeremy Chadwick j...@koitsu.org wrote:


On Fri, May 17, 2013 at 11:37:23AM +0200, dennis berger wrote:

Hi List,
I can confirm that it is the bug you mentioned steven.
Here is how I found it.

I recorded hourly zfskern and nfsd stats. like this.

echo PROCSTAT  $reportname
pgrep -S (zfskern|nfsd) | xargs procstat -kk  $reportname

luckily it crashed this night and logged this.

 1910 101508 nfsd nfsd: servicemi_switch+0x186  
sleepq_wait+0x42 _sleep+0x376 arc_lowmem+0x77 kmem_malloc+0xc1  
uma_large_malloc+0x4a malloc+0xd9 arc_get_data_buf+0xb5  
arc_read_nolock+0x1ec arc_read+0x93 dbuf_prefetch+0x12c  
dmu_zfetch_dofetch+0x10b dmu_zfetch+0xaf8 dbuf_read+0x4a7  
dmu_buf_hold_array_by_dnode+0x16b dmu_buf_hold_array+0x67  
dmu_read_uio+0x3f zfs_freebsd_read+0x3e3


Maybe it would be good to merge this fix into RELENG_9_1 and distribute  
a fix via freebsd-update what do you think?


best,
-dennis


Am 16.05.2013 um 11:42 schrieb dennis berger:

 This is indeed a ZFS+NFS system and I can see that istgt and nfs are  
stuck in some ZIO state. Maybe it's this.

 Thank's for pointing out.

 Is it this ZFS+NFS deadlock?

 --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c
 +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c
 @@ -3720,8 +3720,16 @@ arc_lowmem(void *arg __unused, int howto  
__unused)

mutex_enter(arc_reclaim_thr_lock);
needfree = 1;
cv_signal(arc_reclaim_thr_cv);
 -  while (needfree)
 -   msleep(needfree, arc_reclaim_thr_lock, 0, zfs:lowmem, 0);
 +
 +  /*
 +	 * It is unsafe to block here in arbitrary threads, because we can  
come
 +	 * here from ARC itself and may hold ARC locks and thus risk a  
deadlock

 +   * with ARC reclaim thread.
 +   */
 +  if (curproc == pageproc) {
 +   while (needfree)
 +   msleep(needfree, arc_reclaim_thr_lock, 0, zfs:lowmem, 0);
 +  }
mutex_exit(arc_reclaim_thr_lock);
mutex_exit(arc_lowmem_lock);
 }

 I'll try to crash our testsystem. I'll assume that stressing NFS  
backed with ZFS a lot might trigger this bug?


 -dennis


 Am 16.05.2013 um 00:03 schrieb Steven Hartland:

 - Original Message - From: dennis berger d...@nipsi.de
 FreeBSD  9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec  4  
09:23:10 UTC 2012


 3. Regarding this:
 A clean shutdown isn't possible though. It hangs after vnode
 cleaning, normally you would see detaching of usb devices here,  
or

 other devices maybe?
 Please don't conflate this with your above issue.  This is almost
 certainly unrelated.  Please start a new thread about that if  
desired.


 Maybe this is a misunderstanding normally this system will shutdown  
cleanly, of course.

 This hang only appears after the network problem above.

 If this is a ZFS system, its a known issue which is fixed in current,
 stable-9, stable-8 and the upcoming 8.4 release.

 If not and you have USB devices see if the following sysctl helps:
 hw.usb.no_shutdown_wait=1


I'm sorry to say it won't happen.  The only updates that the -RELEASE
branches get are for security.  If you want fixes for other things, you
need to follow/run stables branches (i.e. stable/9), otherwise you will
need to wait until 9.2-RELEASE comes out.



And errata notices? Are they for security?

Ronald.
___
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


Re: kernel panic: ffs_valloc: dup alloc

2013-05-13 Thread Ronald Klop
On Mon, 13 May 2013 11:10:04 +0200, Andriy Kornatskyy  
andriy.kornats...@live.com wrote:


The core.txt and info files can be found in attached archive (there are  
2 crash reports there). If you need vmcores, just let me know where I  
can upload them.


ASUS K73E
Architecture: i386
OS: FreeBSD 9.1-RELEASE-p3

Please let me know should you need some other information.

Thanks.

Andriy  


Attachments are stripped by the mailinglist. Put them inline or on  
something like http://pastebin.com/.


Ronald.
___
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


Re: recommended memory for zfs

2013-05-10 Thread Ronald Klop
On Fri, 10 May 2013 04:18:42 +0200, Benjamin Adams  
benjamindad...@gmail.com wrote:



On 05/09/2013 10:06 PM, Jeremy Chadwick wrote:

On Thu, May 09, 2013 at 09:47:27PM -0400, Benjamin Adams wrote:

On 05/09/2013 08:53 PM, Shane Ambler wrote:

On 09/05/2013 22:48, Benjamin Adams wrote:

Hello zfs question about memory.
I heard zfs is very ram hungry.
Service looking to run:
- nginx
- postgres
- php-fpm
- python

I have a machine with two quad core cpus but only 4 G Memory

I'm looking to buy more ram now.
What would be the recommend amount of memory for zfs across 6 drives  
on

this setup?


I believe I heard a calculation of 1GB cache per 1TB of disk. But
basically zfs will use all free ram available if you access that
much data from disk. You will want to set vfs.zfs.arc_max to allow
enough ram for your apps to work in.

If you consider the files for your website and the data you store
you may find that you would never fill more than 500MB of cache.

If you will be serving large media files that will easily use up
the cache you could give them their own filesystem that only
caches metadata - zfs set primarycache=metadata zroot/mediafiles



Thanks for all the replies  Size of DB and HD's are:

Current DB Size = 23 GB
HD sizes = (6) 500 GB drives

Nobody is going to be able to give you a precise/accurate recommendation
given the lack of detail provided, I'm sorry to say.  What's the RES
size of nginx (all processes combined)?  What's the RES size of
postgres (same)?  Do you have PHP scripts that run amok for long
periods of time and take up lots of RAM?  Same with python?  How many
concurrent visitors and what sort of content are you hosting?  Do you
maintain/write your own PHP/Python code or are you using some crap like
Wordpress?

This is just a **small** list of questions -- and what may come as a
shock is that I do not expect you to provide answers to any of them.
They are questions that you should, for yourself, attempt to answer and
work out what you need from there (teach a man to fish and all that).

The advice of 1GB of RAM per 1TB of disk space is absolute nonsense on
numerous levels -- whoever gave this advice to Shane either has no
understanding of how filesystems/ZFS works, or does but chose to
simplify to the point where they're providing half-ass information.
There is no direct, or even indirect, correlation between disk capacity
and ZFS ARC size -- what matter is your working set (to quote Tom).
You need to have some idea of how much disk I/O you're doing, and what
type of I/O (sequential or random).

If you want my general advice, Benjamin, it's this: get yourself a
system with *minimum* 8GB of RAM but has the physical possibility of
supporting more (and only add more RAM when/if you know you need it); do
not bother with ZFS on a system with 4GB.  Run amd64, not i386 (I don't
recommend bothering with ZFS on i386 -- I am not going to get into a
discussion about this either).  Run stable/9, not 9.1-RELEASE.  Avoid
compression and dedup.  And test disk failures as well (don't get caught
with your pants down later).

The above advice comes from someone who did hosting (web/ssh/etc.) for
almost 20 years with KISS principle applied at all levels.  YMMV though,
depending on what all you're doing/what you truly need.

Good luck.


Jeremy,

Was just see if I should just get raid controller and more ram down the  
road.

List of priorities.

Main thing is I move from BSD when 9.0 came out.  Was looking to see if  
zfs is included in the installer.  Now.


Sum up:
upgrade ram to 16GB (not 64 like plained)
and  raid controller that supports level 5.



Let ZFS do the RAID stuff. Do not use a RAID controller, but give the  
plain disks to ZFS. Some of the nice features come from ZFS doing the RAID  
stuff.


Ronald.
___
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


Re: Ghosted logins in w/who

2013-04-10 Thread Ronald Klop

On Wed, 10 Apr 2013 16:09:52 +0200, damon...@mac.hush.com wrote:


If I wipe the utmp file all the w/who content goes away, resets if you
will. But in a matter of moments the problem reappears.. is this
something that needs to be submitted as a bug report do you think?
Thanks!
Damon


Did you upgrade correctly? Did you also ran make delete-old and make  
delete-old-libs? And did you rebuild all ports after that?

Some things might use the old stuff still.

Ronald.



On 4/9/2013 at 9:42 AM, Fabian Wenk  wrote:Hello Daniel

On 09.04.2013 12:07, Daniel Braniss wrote:

something changed beteen 8 and 9 with respect of handling of utmp,
I tried to research this but got bogged down with other things.


According to /usr/src/UPDATING:

20100113:
  The utmp user accounting database has been replaced with utmpx,
  the user accounting interface standardized by POSIX.
  Unfortunately the semantics of utmp and utmpx don't match,
  making it practically impossible to support both interfaces.
  The user accounting database is used by tools like finger(1),
  last(1), talk(1), w(1) and ac(8).

  All applications in the base system use utmpx.  This means only
  local binaries (e.g. from the ports tree) may still use these
  utmp database files.  These applications must be rebuilt to make
  use of utmpx.

  After the system has been upgraded, it is safe to remove the old
  log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
  assuming their contents is of no importance anymore.  Old wtmp
  databases can only be used by last(1) and ac(8) after they have
  been converted to the new format using wtmpcvt(1).
Could this have any impact regarding this issue with telnet login?
bye
Fabian
___
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

___
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


Re: FreeBSD 9.1 excessive memory allocations [SOLVED]

2013-03-27 Thread Ronald Klop

On Wed, 27 Mar 2013 19:33:46 +0100, Unga unga...@yahoo.com wrote:




- Original Message -


From: Ian Lepore i...@freebsd.org
To: Unga unga...@yahoo.com
Cc: freebsd-stable@freebsd.org freebsd-stable@FreeBSD.org
Sent: Wednesday, March 27, 2013 2:06 PM
Subject: Re: FreeBSD 9.1 excessive memory allocations

On Tue, 2013-03-26 at 11:35 -0700, Unga wrote:

 Hi all


 I have a heavily threaded C application, developed on an Intel Core i5

laptop (2 cores) running FreeBSD 8.1-RELEASE.


 When this application compile and run on another Intel Core i7 laptop  
(4
cores) running FreeBSD 9.1-RELEASE, this application immediately starts  
grabbing

memory by over 100MB per second and soon exit with not enough RAM.



 Both laptops having 4GB RAM.

 All malloc and free are mutex locked.

 Very rarely this problem happens on the i5 (2 cores) laptop too, but  
on the

i7 laptop, it happens every time.


 Appreciate any feedback to identify and fix this issue.

 Best regards
 Unga



Too many moving parts, you need to partition the problem.  Is it the
change in OS (and especially libraries) that causes the problem, or the
change in the number of cores (more concurrent threads) is exposing some
sort of application-side race condition?  Given the fact that it does
occur on 2 cores + freebsd 8.1, even if more rarely, it's almost surely
an application problem.
Perhaps you could use a tool such as valgrind to help track down the
runaway allocations?

Another way to expose thread race problems is to force more thread
context switches.  A blunt tool for doing so is to set hz=5000 or even
higher in /boot/loader.conf.  I've never done that on a desktop or
laptop system, only on embedded systems, but it should still work okay.
If changing the application code is easier, you can get a similar effect
by creating a thread whose only job is to preempt other threads, by
using rtprio_thread() to set it to real time priority, then just have it
sleep for short random intervals (microseconds), all it does is wakes up
and goes right back to sleep.

Also, FYI, there's no need to use a mutex in your application to protect
allocations.  The memory allocator in libc is thread-safe, and in fact
is particularly designed for efficient multi-threaded allocation.

-- Ian



Dear Tony, Alexander, Jan, Ian and Jeremy

Thank you very much for your very valuable comments.

Problem seems to be solved. But require more testing.

1. Fixed an application-level crucial bug. This is nearly a 7000 lines C  
app. It was really hard to see as the application is designed with 8  
dedicated threads.


2. At run-time, this application shoots up to about 400 dynamic threads  
on the i7 machine, whereas on the i5 machine, it only shoots up 57  
dynamic threads. It was bit scaring, therefore, made a hard limit on  
total number of threads to 64.


Regarding mutex locks on allocations, as per the malloc(3), it says  
small and medium size allocations are done from per thread caches,  
therefore, thread-safe. My allocations are large in nature, about 5-7MB.


The per thread caches are for speed. Not for thread-safety.

Ronald.
___
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


Re: problem compiling openjdk6

2013-03-13 Thread Ronald Klop

You can ask this on freebsd-j...@freebsd.org also.

Ronald.

On Sat, 09 Mar 2013 15:59:22 +0100, Filippo Moretti  
filippom...@yahoo.com wrote:



I get the following compile error when attempting to build openjdk6 on
FreeBSD STING.teletu.it 9.1-STABLE FreeBSD 9.1-STABLE #0: Sun Mar  3  
00:09:06 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  
 i386





va/openjdk6/work/hotspot/src/share/vm/adlc/adlparse.cpp 
/usr/ports/java/openjdk6/work/hotspot/src/share/vm/adlc/adlparse.cpp:1:  
sorry, unimplemented: 64-bit mode not compiled in

gmake[6]: *** [../generated/adfiles/adlparse.o] Error 1
gmake[6]: Leaving directory  
`/usr/ports/java/openjdk6/work/build/bsd-i386/hotspot/outputdir/bsd_amd64_compiler2/product'

gmake[5]: *** [ad_stuff] Error 2
gmake[5]: Leaving directory  
`/usr/ports/java/openjdk6/work/build/bsd-i386/hotspot/outputdir/bsd_amd64_compiler2/product'

gmake[4]: *** [product] Error 2
gmake[4]: Leaving directory  
`/usr/ports/java/openjdk6/work/build/bsd-i386/hotspot/outputdir'

gmake[3]: *** [generic_build2] Error 2
gmake[3]: Leaving directory `/usr/ports/java/openjdk6/work/hotspot/make'
gmake[2]: *** [product] Error 2
gmake[2]: Leaving directory `/usr/ports/java/openjdk6/work/hotspot/make'
gmake[1]: *** [hotspot-build] Error 2
gmake[1]: Leaving directory `/usr/ports/java/openjdk6/work'
gmake: *** [build_product_image] Error 2
*** [do-build] Error code 1

Stop in /usr/ports/java/openjdk6.
*** [install] Error code 1

Stop in /usr/ports/java/openjdk6.
*** [build-depends] Error code 1

Stop in /usr/ports/java/icedtea-web.
*** [install] Error code 1

Stop in /usr/ports/java/icedtea-web.
sincerely
Filippo
___
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


Re: make_dev_physpath_alias

2013-03-05 Thread Ronald Klop
On Tue, 05 Mar 2013 15:10:52 +0100, Johan Hendriks  
joh.hendr...@gmail.com wrote:



Hello all.

I have a supermicro 16 bay box with a LSI 9211-8i card.
We use it for temp data storage, and we wanted to try the l4z  
compression.


After updating the source tree to r247839: and doing a make buildworld  
cycle all works fine.

But at boot time we get some warnings.
make_dev_physpath_alias: WARNING - Unable to alias  
gptid/281951f4-a996-11e1-83eb-00259061b51a to  
enc@n500304800182f4fd/type@0/slot@1/elmdesc@Slot_01/gptid/281951f4-a996-11e1-83eb-00259061b51a  
- path too long


Do i need to worry!!!


Only if you want to use the paths it can't create.

Ronald.



Gr
johan

Here is my full dmesg

Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights  
reserved.

FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.1-STABLE #0 r247839: Tue Mar  5 13:17:25 CET 2013
 r...@backup.neuteboom.com:/usr/obj/usr/src/sys/KRNL amd64
CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU)
   Origin = GenuineIntel  Id = 0x206a7  Family = 0x6  Model = 0x2a  
Stepping = 7

Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
Features2=0x1fbae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX
   AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM
   AMD Features2=0x1LAHF
   TSC: P-state invariant, performance statistics
real memory  = 34359738368 (32768 MB)
avail memory = 33075630080 (31543 MB)
Event timer LAPIC quality 600
ACPI APIC Table: SUPERM SMCI--MB
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  2
  cpu2 (AP): APIC ID:  4
  cpu3 (AP): APIC ID:  6
ioapic0 Version 2.0 irqs 0-23 on motherboard
kbd1 at kbdmux0
ctl: CAM Target Layer loaded
acpi0: SUPERM SMCI--MB on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of 67, 1 (4) failed
cpu0: ACPI CPU on acpi0
cpu1: ACPI CPU on acpi0
cpu2: ACPI CPU on acpi0
cpu3: ACPI CPU on acpi0
hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0
Timecounter HPET frequency 14318180 Hz quality 950
Event timer HPET frequency 14318180 Hz quality 550
Event timer HPET1 frequency 14318180 Hz quality 440
Event timer HPET2 frequency 14318180 Hz quality 440
Event timer HPET3 frequency 14318180 Hz quality 440
Event timer HPET4 frequency 14318180 Hz quality 440
atrtc0: AT realtime clock port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
Event timer RTC frequency 32768 Hz quality 0
attimer0: AT timer port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter i8254 frequency 1193182 Hz quality 0
Event timer i8254 frequency 1193182 Hz quality 100
Timecounter ACPI-fast frequency 3579545 Hz quality 900
acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge irq 19 at device 6.0 on pci0
pci1: ACPI PCI bus on pcib1
mps0: LSI SAS2008 port 0xe000-0xe0ff mem  
0xf760-0xf7603fff,0xf758-0xf75b irq 19 at device 0.0 on pci1

mps0: Firmware: 15.00.00.00, Driver: 14.00.00.01-fbsd
mps0: IOCCapabilities:  
1285cScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc
em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xf020-0xf03f mem  
0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0 on pci0

em0: Using an MSI interrupt
em0: Ethernet address: 00:25:90:75:c8:09
ehci0: EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff irq  
16 at device 26.0 on pci0

usbus0: EHCI version 1.0
usbus0 on ehci0
pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0
pci2: ACPI PCI bus on pcib2
pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0
pci3: ACPI PCI bus on pcib3
em1: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xd000-0xd01f mem  
0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0 on pci3

em1: Using MSIX interrupts with 3 vectors
em1: Ethernet address: 00:25:90:75:c8:08
ehci1: EHCI (generic) USB 2.0 controller mem 0xf7823000-0xf78233ff irq  
23 at device 29.0 on pci0

usbus1: EHCI version 1.0
usbus1 on ehci1
pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0
pci4: ACPI PCI bus on pcib4
vgapci0: VGA-compatible display mem  
0xf500-0xf5ff,0xf700-0xf7003fff,0xf680-0xf6ff irq 19  
at device 3.0 on pci4

isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
ahci0: Intel Cougar Point AHCI SATA controller port  
0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf000-0xf01f  
mem 0xf7822000-0xf78227ff irq 19 at device 31.2 on pci0

ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
ahcich0: AHCI channel at channel 0 on ahci0
ahcich1: AHCI 

Re: make_dev_physpath_alias

2013-03-05 Thread Ronald Klop
On Tue, 05 Mar 2013 16:40:52 +0100, Johan Hendriks  
joh.hendr...@gmail.com wrote:



Ronald Klop schreef:
On Tue, 05 Mar 2013 15:10:52 +0100, Johan Hendriks  
joh.hendr...@gmail.com wrote:



Hello all.

I have a supermicro 16 bay box with a LSI 9211-8i card.
We use it for temp data storage, and we wanted to try the l4z  
compression.


After updating the source tree to r247839: and doing a make buildworld  
cycle all works fine.

But at boot time we get some warnings.
make_dev_physpath_alias: WARNING - Unable to alias  
gptid/281951f4-a996-11e1-83eb-00259061b51a to  
enc@n500304800182f4fd/type@0/slot@1/elmdesc@Slot_01/gptid/281951f4-a996-11e1-83eb-00259061b51a  
- path too long


Do i need to worry!!!


Only if you want to use the paths it can't create.

Ronald.


Thanks for the quick responce.
Do you know why it can not create the path.
The system is installed normally, why is it trying to use path names it  
can not use?


No, I am not familiar with the details of this. What I see is that it  
tries to make aliases for the device in /dev. So there already is a name  
for the device you can use, but the alias (which might be a symlink with a  
convenient name) is not a valid filename, so it is not created.

The code in 9-stable is in sys/kern/kern_conf.c line 995.

NB: I re-added the mailinglist in the addresses. Other people might know  
more.


Regards,
Ronald.



gr
Johan


Gr
johan

Here is my full dmesg

Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,  
1994
 The Regents of the University of California. All rights  
reserved.

FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.1-STABLE #0 r247839: Tue Mar  5 13:17:25 CET 2013
 r...@backup.neuteboom.com:/usr/obj/usr/src/sys/KRNL amd64
CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU)
   Origin = GenuineIntel  Id = 0x206a7  Family = 0x6  Model = 0x2a  
Stepping = 7
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE  
Features2=0x1fbae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX  
   AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM

   AMD Features2=0x1LAHF
   TSC: P-state invariant, performance statistics
real memory  = 34359738368 (32768 MB)
avail memory = 33075630080 (31543 MB)
Event timer LAPIC quality 600
ACPI APIC Table: SUPERM SMCI--MB
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  2
  cpu2 (AP): APIC ID:  4
  cpu3 (AP): APIC ID:  6
ioapic0 Version 2.0 irqs 0-23 on motherboard
kbd1 at kbdmux0
ctl: CAM Target Layer loaded
acpi0: SUPERM SMCI--MB on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of 67, 1 (4) failed
cpu0: ACPI CPU on acpi0
cpu1: ACPI CPU on acpi0
cpu2: ACPI CPU on acpi0
cpu3: ACPI CPU on acpi0
hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on  
acpi0

Timecounter HPET frequency 14318180 Hz quality 950
Event timer HPET frequency 14318180 Hz quality 550
Event timer HPET1 frequency 14318180 Hz quality 440
Event timer HPET2 frequency 14318180 Hz quality 440
Event timer HPET3 frequency 14318180 Hz quality 440
Event timer HPET4 frequency 14318180 Hz quality 440
atrtc0: AT realtime clock port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
Event timer RTC frequency 32768 Hz quality 0
attimer0: AT timer port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter i8254 frequency 1193182 Hz quality 0
Event timer i8254 frequency 1193182 Hz quality 100
Timecounter ACPI-fast frequency 3579545 Hz quality 900
acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge irq 19 at device 6.0 on pci0
pci1: ACPI PCI bus on pcib1
mps0: LSI SAS2008 port 0xe000-0xe0ff mem  
0xf760-0xf7603fff,0xf758-0xf75b irq 19 at device 0.0 on  
pci1

mps0: Firmware: 15.00.00.00, Driver: 14.00.00.01-fbsd
mps0: IOCCapabilities:  
1285cScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc
em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xf020-0xf03f  
mem 0xf780-0xf781,0xf7825000-0xf7825fff irq 20 at device 25.0  
on pci0

em0: Using an MSI interrupt
em0: Ethernet address: 00:25:90:75:c8:09
ehci0: EHCI (generic) USB 2.0 controller mem 0xf7824000-0xf78243ff  
irq 16 at device 26.0 on pci0

usbus0: EHCI version 1.0
usbus0 on ehci0
pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0
pci2: ACPI PCI bus on pcib2
pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0
pci3: ACPI PCI bus on pcib3
em1: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xd000-0xd01f  
mem 0xf770-0xf771,0xf772-0xf7723fff irq 16 at device 0.0  
on pci3

em1: Using MSIX interrupts with 3 vectors
em1: Ethernet address: 00

Re: Musings on ZFS Backup strategies

2013-03-02 Thread Ronald Klop
On Fri, 01 Mar 2013 21:34:39 +0100, Daniel Eischen deisc...@freebsd.org  
wrote:



On Fri, 1 Mar 2013, Ben Morrow wrote:


Quoth Daniel Eischen deisc...@freebsd.org:


Yes, we still use a couple of DLT autoloaders and have nightly
incrementals and weekly fulls.  This is the problem I have with
converting to ZFS.  Our typical recovery is when a user says
they need a directory or set of files from a week or two ago.
Using dump from tape, I can easily extract *just* the necessary
files.  I don't need a second system to restore to, so that
I can then extract the file.


As Karl said originally, you can do that with snapshots without having
to go to your backups at all. With the right arrangements (symlinks to
the .zfs/snapshot/* directories, or just setting the snapdir property to
'visible') you can make it so users can do this sort of restore
themselves without having to go through you.


It wasn't clear that snapshots were traversable as a normal
directory structure.  I was thinking it was just a blob
that you had to roll back to in order to get anything out
of it.


That is the main benefit of snapshots. :-) You can also very easily diff  
files between them.

Mostly a lot of data is static so it does not cost a lot to keep snapshots.
There are a lot of scripts online and in ports which make a nice retention  
policy like e.g. 7 daily snaphots, 8 weekly, 12 monthly, 2 yearly. See  
below for (an incomplete list of) what I keep about my homedir at home.



Under our current scheme, we would remove snapshots
after the next (weekly) full zfs send (nee dump), so
it wouldn't help unless we kept snapshots around a
lot longer.


Why not.


Am I correct in assuming that one could:

   # zfs send -R snapshot | dd obs=10240 of=/dev/rst0

to archive it to tape instead of another [system:]drive?


Yes, your are correct. The manual page about zfs send says: 'The format of  
the stream is committed. You will be able to receive your streams on  
future versions of ZFS.'



Ronald.



tank/home 115G  65.6G   
53.6G  /home
tank/home@auto-2011-10-25_19.00.yearly   16.3G  -   
56.8G  -
tank/home@auto-2012-06-06_22.00.yearly   5.55G  -   
53.3G  -
tank/home@auto-2012-09-02_20.00.monthly  2.61G  -   
49.3G  -
tank/home@auto-2012-10-15_06.00.monthly  2.22G  -   
49.9G  -
tank/home@auto-2012-11-26_13.00.monthly  2.47G  -   
50.2G  -
tank/home@auto-2013-01-07_13.00.monthly  2.56G  -   
51.5G  -
tank/home@auto-2013-01-21_13.00.weekly   1.06G  -   
52.4G  -
tank/home@auto-2013-01-28_13.00.weekly409M  -   
52.3G  -
tank/home@auto-2013-02-04_13.00.monthly   625M  -   
52.5G  -
tank/home@auto-2013-02-11_13.00.weekly689M  -   
52.5G  -
tank/home@auto-2013-02-16_13.00.weekly   17.7M  -   
52.5G  -
tank/home@auto-2013-02-17_13.00.daily17.7M  -   
52.5G  -
tank/home@auto-2013-02-18_13.00.daily17.9M  -   
52.5G  -

___
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


Re: Musings on ZFS Backup strategies

2013-03-02 Thread Ronald Klop
On Fri, 01 Mar 2013 18:55:22 +0100, Volodymyr Kostyrko c.kw...@gmail.com  
wrote:



01.03.2013 16:24, Karl Denninger:

Dabbling with ZFS now, and giving some thought to how to handle backup
strategies.

ZFS' snapshot capabilities have forced me to re-think the way that I've
handled this.  Previously near-line (and offline) backup was focused on
being able to handle both disasters (e.g. RAID adapter goes nuts and
scribbles on the entire contents of the array), a double-disk (or worse)
failure, or the obvious (e.g. fire, etc) along with the aw crap, I just
rm -rf'd something I'd rather not!

ZFS makes snapshots very cheap, which means you can resolve the aw
crap situation without resorting to backups at all.  This turns the
backup situation into a disaster recovery one.

And that in turn seems to say that the ideal strategy looks more like:

Take a base snapshot immediately and zfs send it to offline storage.
Take an incremental at some interval (appropriate for disaster recovery)
and zfs send THAT to stable storage.

If I then restore the base and snapshot, I get back to where I was when
the latest snapshot was taken.  I don't need to keep the incremental
snapshot for longer than it takes to zfs send it, so I can do:

zfs snapshot pool/some-filesystem@unique-label
zfs send -i pool/some-filesystem@base pool/some-filesystem@unique-label
zfs destroy pool/some-filesystem@unique-label

and that seems to work (and restore) just fine.


Yes, I'm working with backups the same way, I wrote a simple script that  
synchronizes two filesystems between distant servers. I also use the  
same script to synchronize bushy filesystems (with hundred thousands of



Your filesystems grow a lot of hair? :-)





files) where rsync produces a too big load for synchronizing.

https://github.com/kworr/zfSnap/commit/08d8b499dbc2527a652cddbc601c7ee8c0c23301

I left it where it was but I was also planning to write some purger for  
snapshots that would automatically purge snapshots when pool gets low on  
space. Never hit that yet.



Am I looking at this the right way here?  Provided that the base backup
and incremental are both readable, it appears that I have the disaster
case covered, and the online snapshot increments and retention are
easily adjusted and cover the oops situations without having to resort
to the backups at all.

This in turn means that keeping more than two incremental dumps offline
has little or no value; the second merely being taken to insure that
there is always at least one that has been written to completion without
error to apply on top of the base.  That in turn makes the backup
storage requirement based only on entropy in the filesystem and not time
(where the tower of Hanoi style dump hierarchy imposed both a time AND
entropy cost on backup media.)


Well, snapshots can pose a value in a longer timeframe depending on  
data. Being able to restore some file accidentally deleted two month ago  
already saved 2k$ for one of our customers.

___
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


Re: Panic at shutdown (acpi related)

2013-03-01 Thread Ronald Klop
On Sun, 24 Feb 2013 13:04:52 +0100, David Demelier  
demelier.da...@gmail.com wrote:



Le mardi 12 février 2013 21:42:01 Ronald Klop a écrit :

On Tue, 12 Feb 2013 19:44:49 +0100, David Demelier

demelier.da...@gmail.com wrote:
 Le mardi 12 février 2013 10:01:10 Andriy Gapon a écrit :
 on 12/02/2013 09:57 David Demelier said the following:
  Yes I have added debugging option in my kernel. I have makeoptions
  DEBUG=-g in my config. Do I need more ?

 .symbols?

 I don't understand what you are saying, I have
 /boot/kernel/kernel.symbols.
 Please tell me what I'm doing wrong. I've just read and done the steps
 written
 there :

 http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-
 gdb.html

 So I've run

 # cd /usr/obj/usr/src/sys/Melon
 # kgdb kernel.debug /var/crash/vmcore.0

Why not something like kgdb /boot/kernel/kernel.symbols
/var/crash/vmcore.0?
That looks like what the manual page of kgdb seems to suggest.

Regards,
Ronald.

 and that's the only trace I get using bt full :

 229 #define IS_BSP()(PCPU_GET(cpuid) == 0)
 (kgdb) bt full
 #0  doadump (textdump=value optimized out) at pcpu.h:229
 No locals.
 #1  0x in ?? ()
 No symbol table info available.



I have that, in fact I was using bt full instead of short bt :

#0  doadump (textdump=Variable textdump is not available.
) at pcpu.h:224
#1  0x0004 in ?? ()
#2  0x805146b6 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:448
#3  0x80514b79 in panic (fmt=0x1 Address 0x1 out of bounds)
at /usr/src/sys/kern/kern_shutdown.c:636
#4  0x8071e919 in trap_fatal (frame=0xc, eva=Variable eva is  
not

available.
) at /usr/src/sys/amd64/amd64/trap.c:857
#5  0x8071eca4 in trap_pfault (frame=0xff80d63db5d0,  
usermode=0)

at /usr/src/sys/amd64/amd64/trap.c:773
#6  0x8071f09b in trap (frame=0xff80d63db5d0) at
/usr/src/sys/amd64/amd64/trap.c:456
#7  0x8070993f in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:228
#8  0x802ddbf5 in AcpiOsAcquireObject (Cache=0xfe00015de400)
at /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:316
#9  0x802e27c1 in AcpiUtAllocateObjectDescDbg
(ModuleName=0x80795110 dsutils,
LineNumber=703, ComponentId=Variable ComponentId is not available.
) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:437
#10 0x802e2972 in AcpiUtCreateInternalObjectDbg
(ModuleName=0x80795110 dsutils,
LineNumber=703, ComponentId=64, Type=1)
at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:112
#11 0x802b32ea in AcpiDsCreateOperand  
(WalkState=0xfe000380fc00,

Arg=0xfe00017d39c0,
ArgIndex=0) at  
/usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:703
#12 0x802b3686 in AcpiDsCreateOperands  
(WalkState=0xfe000380fc00,

FirstArg=0xfe00017d39c0) at
/usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:798
#13 0x802b4323 in AcpiDsExecEndOp (WalkState=0xfe000380fc00)
at /usr/src/sys/contrib/dev/acpica/dispatcher/dswexec.c:449
#14 0x802d55e9 in AcpiPsParseLoop (WalkState=0xfe000380fc00)
at /usr/src/sys/contrib/dev/acpica/parser/psloop.c:1249
#15 0x802d6a5b in AcpiPsParseAml (WalkState=0xfe000380fc00)
at /usr/src/sys/contrib/dev/acpica/parser/psparse.c:525
#16 0x802d7ad7 in AcpiPsExecuteMethod (Info=0xfe00411b9500)
at /usr/src/sys/contrib/dev/acpica/parser/psxface.c:368
#17 0x802ce3af in AcpiNsEvaluate (Info=0xfe00411b9500)
at /usr/src/sys/contrib/dev/acpica/namespace/nseval.c:193
#18 0x802d3567 in AcpiEvaluateObject (Handle=0xfe00017d6d40,
Pathname=0x807b2e9b _TMP, ExternalParams=0x0,
ReturnBuffer=0xff80d63dba50)
at /usr/src/sys/contrib/dev/acpica/namespace/nsxfeval.c:289
#19 0x8031ca84 in acpi_GetInteger (handle=0xfe00017d6d40,
path=0x807b2e9b _TMP, number=0xff80d63dbab4) at
/usr/src/sys/dev/acpica/acpi.c:2204
#20 0x80331756 in acpi_tz_get_temperature (sc=0xfe0001a2fa00)
at /usr/src/sys/dev/acpica/acpi_thermal.c:462
#21 0x803329d6 in acpi_tz_monitor (Context=0xfe0001a2fa00)
at /usr/src/sys/dev/acpica/acpi_thermal.c:497
#22 0x80332f92 in acpi_tz_thread (arg=Variable arg is not  
available.

) at /usr/src/sys/dev/acpica/acpi_thermal.c:864
#23 0x804e7a3d in fork_exit (callout=0x80332e50
acpi_tz_thread, arg=0x0,
frame=0xff80d63dbc00) at /usr/src/sys/kern/kern_fork.c:992
#24 0x80709dfe in fork_trampoline () at
/usr/src/sys/amd64/amd64/exception.S:602
#25 0x in ?? ()
#26 0x in ?? ()
#27 0x0001 in ?? ()
#28 0x in ?? ()
#29 0x in ?? ()
#30 0x in ?? ()
#31 0x in ?? ()
#32 0x in ?? ()
#33 0x in ?? ()
#34 0x in ?? ()
#35 0x in ?? ()
#36

  1   2   3   4   >