Re: zpool requires re-import on reboot
On 2013-11-20 02:49, Beeblebrox wrote: Alan: This corrects the zpool import problem (thanks for that): zpool_cache_type=/boot/zfs/zpool.cache zpool_cache_name=/boot/zfs/zpool.cache But boot still drops to single user and needs zfs mount -a to locate the fstab entries. Some datasets have canmount=noauto (but have a corresponding fstab entry). However, the primary dataset of the zpool (where dataset name = zpoll name) for both pools has canmount=on. One other non-standard property I have is that the dataset name is different than mountpoint (zfs set mountpoint=/some other folder) Nothing else out of the ordinary that I can think of. Regards. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/zpool-requires-re-import-on-reboot-tp5861930p5862442.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org having zfs_enable=YES in /etc/rc.conf should automatically run 'zfs mount -a' during boot, and you shouldn't have this problem What does the output of this command look like: zfs get -r -t filesystem canmount,mountpoint $poolname in the zfsboot script, some datasets have canmount=off on purpose, /usr has it so that /usr/bin goes in the root dataset, but the dataset is required to create a separate /usr/local dataset -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: zpool requires re-import on reboot
My apologies, please disregard last message - problem was an error on my part. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/zpool-requires-re-import-on-reboot-tp5861930p5862468.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Please compile ports-mgmt/pkg for i486
On Wed November 20 2013 11:16:03 you wrote: Ah yes, we did attempt to fix those long nops on Geode once and for all, can you please confirm that pkg built with recent clang does not cause SIGILL for you? Not unless -march=geode :( Please see: http://llvm.org/bugs/show_bug.cgi?id=11212 http://llvm.org/bugs/show_bug.cgi?id=17792 Got bitten by that with -march=i486... -- xmpp:stha...@jabster.pl sip:stha...@misaki.pl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: random_harvestq eats much on geode-lx alix2c3
Stanisław Halik wrote: but what do you ask for? Also, can text attachments be put here? For posterity's sake, better not to link to them. It is poor hardware as you said but FreeBSD should run well on it. I also have Alix boards running FreeBSD as router, and cpu load is almost 0. last pid: 2799; load averages: 0.00, 0.00, 0.00up 0+11:29:10 11:29:53 14 processes: 1 running, 13 sleeping CPU: 1.1% user, 0.0% nice, 0.0% system, 0.0% interrupt, 98.9% idle Mem: 8376K Active, 6752K Inact, 23M Wired, 620K Cache, 21M Buf, 195M Free Swap: uname -a FreeBSD firewall 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Sun Mar 20 01:51:47 EET 2011 root@firewall:/usr/obj/nanobsd.custom/usr/src/sys/FIREWALL i386 I did not deployed yet 10.x (I'm waiting for nanobsd.sh to correct problems with pkgng) for now I am running it on VirtualBox, but I hope it will also run well on Alix hardware. Your problems were on 10.x or 11.x? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: random_harvestq eats much on geode-lx alix2c3
On Wed November 20 2013 12:58:28 freebsdonline wrote: I did not deployed yet 10.x (I'm waiting for nanobsd.sh to correct problems with pkgng) for now I am running it on VirtualBox, but I hope it will also run well on Alix hardware. Your problems were on 10.x or 11.x? 10.x. It's a new issue, works fine with 9.x. xmpp:stha...@jabster.pl sip:stha...@misaki.pl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: random_harvestq eats much on geode-lx alix2c3
I did not deployed yet 10.x (I'm waiting for nanobsd.sh to correct
problems with pkgng) for now I am running it on VirtualBox, but I hope it
will also run well on Alix hardware. Your problems were on 10.x or 11.x?
I just wanted to chip in concerning nanobsd: the whole point with it is
that it is easy to overide methods you don't like. Without to much patching
I have nanobsd working on zfs with pkgng.
If you use the official pkgng repo it is almost trivial:
define cust_pkg() in your config file, something like
cust_pkg() {
pkg -c ${NANO_WORLDDIR} install $packages
pkg -c ${NANO_WORLDDIR} clean
}
You might also have to temporarily place a working resolv.conf in
${NANO_WORLDDIR}/etc
If you have your own repo just add
export PACKAGESITE=proto://path/to/repo
to the config file as well.
Given that thats all it takes, why wait for an official fix?
Best regards
Andreas
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Please compile ports-mgmt/pkg for i486
On 20 Nov 2013, at 11:22, Stanisław Halik stha...@misaki.pl wrote: On Wed November 20 2013 11:16:03 you wrote: Ah yes, we did attempt to fix those long nops on Geode once and for all, can you please confirm that pkg built with recent clang does not cause SIGILL for you? Not unless -march=geode :( Please see: http://llvm.org/bugs/show_bug.cgi?id=11212 http://llvm.org/bugs/show_bug.cgi?id=17792 Got bitten by that with -march=i486... Those bugs are about other CPU's, not specifically the Geode, or i486. The version of clang in head, stable/10 and stable/9 produces regular nops for -march=i486, which is the default setting if you don't pass any arch. So how did you get bitten, then? Were you using 9.1-RELEASE, by any chance? -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
FreeBSD-10 microdrive seagate ST1AT 4GB (VIA mbo) problem
Hello .. I have problem with microdrive and some CF cards on IGEL 3/4 compact thin client ( http://www.parkytowers.me.uk/thin/Igel/3210/index.shtml ). Problem is that FreeBSD cannot find microdrive or CF card to mount sytem / on (but kernel is found and loaded from microdrive or CF card). I have one CF card (sandisk ultra II) which boots but with some timeouts before. Here are links to pictures of this problem. (aprobe:ata0:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 http://s24.postimg.org/al2k6qfzp/WP_20131120_003_1.jpg http://s17.postimg.org/wm0s58kzz/WP_20131120_007_1.jpg http://s23.postimg.org/5sp2k4trf/WP_20131120_006_1.jpg i tried same configuration on openbsd5.3 and everething si Ok .. Any suggestions ? Tnx sorry for my English .. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD-10 microdrive seagate ST1AT 4GB (VIA mbo) problem
On Wed, Nov 20, 2013 at 9:27 PM, Berislav Purgar bpur...@gmail.com wrote: Hello .. I have problem with microdrive and some CF cards on IGEL 3/4 compact thin client ( http://www.parkytowers.me.uk/thin/Igel/3210/index.shtml ). Problem is that FreeBSD cannot find microdrive or CF card to mount sytem / on (but kernel is found and loaded from microdrive or CF card). I have one CF card (sandisk ultra II) which boots but with some timeouts before. Here are links to pictures of this problem. (aprobe:ata0:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 http://s24.postimg.org/al2k6qfzp/WP_20131120_003_1.jpg http://s17.postimg.org/wm0s58kzz/WP_20131120_007_1.jpg http://s23.postimg.org/5sp2k4trf/WP_20131120_006_1.jpg i tried same configuration on openbsd5.3 and everething si Ok .. Any suggestions ? Tnx sorry for my English .. i forgot to tell that ata chipset is VIA VT8237R .. atapci0: VIA 8237 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe800-0xe80f at device 15.0 on pci0 ata0: ATA channel at channel 0 on atapci0 ata1: ATA channel at channel 1 on atapci0 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD-10 microdrive seagate ST1AT 4GB (VIA mbo) problem
On Wed, Nov 20, 2013 at 9:45 PM, Berislav Purgar bpur...@gmail.com wrote: On Wed, Nov 20, 2013 at 9:27 PM, Berislav Purgar bpur...@gmail.comwrote: Hello .. I have problem with microdrive and some CF cards on IGEL 3/4 compact thin client ( http://www.parkytowers.me.uk/thin/Igel/3210/index.shtml ). Problem is that FreeBSD cannot find microdrive or CF card to mount sytem / on (but kernel is found and loaded from microdrive or CF card). I have one CF card (sandisk ultra II) which boots but with some timeouts before. Here are links to pictures of this problem. (aprobe:ata0:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 http://s24.postimg.org/al2k6qfzp/WP_20131120_003_1.jpg http://s17.postimg.org/wm0s58kzz/WP_20131120_007_1.jpg http://s23.postimg.org/5sp2k4trf/WP_20131120_006_1.jpg i tried same configuration on openbsd5.3 and everething si Ok .. Any suggestions ? Tnx sorry for my English .. i forgot to tell that ata chipset is VIA VT8237R .. atapci0: VIA 8237 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe800-0xe80f at device 15.0 on pci0 ata0: ATA channel at channel 0 on atapci0 ata1: ATA channel at channel 1 on atapci0 and how openbsd identify same controler : http://s12.postimg.org/bztc7w1zx/WP_20131120_001_1.jpg Beri ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD-10 microdrive seagate ST1AT 4GB (VIA mbo) problem
On Wed, 2013-11-20 at 21:27 +0100, Berislav Purgar wrote: Hello .. I have problem with microdrive and some CF cards on IGEL 3/4 compact thin client ( http://www.parkytowers.me.uk/thin/Igel/3210/index.shtml ). Problem is that FreeBSD cannot find microdrive or CF card to mount sytem / on (but kernel is found and loaded from microdrive or CF card). I have one CF card (sandisk ultra II) which boots but with some timeouts before. Here are links to pictures of this problem. (aprobe:ata0:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 http://s24.postimg.org/al2k6qfzp/WP_20131120_003_1.jpg http://s17.postimg.org/wm0s58kzz/WP_20131120_007_1.jpg http://s23.postimg.org/5sp2k4trf/WP_20131120_006_1.jpg i tried same configuration on openbsd5.3 and everething si Ok .. Any suggestions ? Tnx sorry for my English .. Try adding hw.ata.ata_dma=0 to your /boot/loader.conf. I don't know why the bios can do DMA on a CF and freebsd can't, but we've needed to add that at $work for years (going back to freebsd 4.x at least). Of course, you pay a huge performance penalty for running in PIO mode. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: cron(8) improvement
On Wed, Nov 06, 2013 at 10:57:12AM +0200, Volodymyr Kostyrko wrote: Shouldn't we encourage packages to use periodic(8) when possible? Yes but our default periodic configuration in /etc/crontab is only configured to be as granular as daily. If this is something that should run hourly or at very strange intervals then cron is a better choice. So why we shouldn't add something like: 0 * * * * root periodic hourly @reboot root periodic reboot I already do this on some machines to take hourly and boot snapshots with zfSnap. And I think periodic is much better place for such tasks. While this is the way it has always been done, I'd find it somewhat lacking in the flexibility department, also you might be in for some nasty surprises First, the resolution is limited to hourly, and second, if I'm not mistaken, the jobs are run strictly sequentially. The last point be suboptimal, as the interval may vary wildly. Also, what happens when all jobs' runtime adds up to more than one hour? It's an equivalent of /etc/cron.hourly.d, but going this way we still don't have something like /etc/crond.d. Best regards Thomas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
