FreeBSD as Samba Server and Windows as Client
There are just so many things that could go wrong on a samba setup that it is beyond funny in my opinion. You have authentication method (kerberos, pam, txt), ports, winbind and dns just to list a few. I suggest you start samba in debug mode and enable full logging. The documentation from samba its self is probably going to be much more comprehensive: http://www.samba.org/samba/docs/man/manpages-3/smbd.8.html I would also try to connect with various clients like a linux, XP, vista or win7. These connection attempts should generate comprehensive logs when samba is running in debug mode. You can then start to get some idea why the connection is being refused by reading through the generated logs. Also, several how-to's already exist on the FreeBSD forums - as an example: http://forums.freebsd.org/showthread.php?t=36137 - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-as-Samba-Server-and-Windows-as-Client-tp5804306p5804418.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Freight forwarder logistics provider shared an album with you.
Dear My Friend Nice day, Hyun Young is a leading professional freight forwarder and logistics provider who focus on the shipment from South China to all the world. Hyun Young started freight forwarding operation at Shenzhen in 2004. Based at Shenzhen, our ambition have pushed us forward to expand to other cities in south of China. Now we have capacity of handing shipment to or from all the ports in south of China. Holds while whole - heartedly achieves the best enterprise objective, With the great support of our global agency, we provide services to our customers through process-driven operation team, advanced information system, and strong management team. Glance to our company: 1. Sea Freight, included FCLLCL; 2. Air Freight; 3. Express, included DHL,UPS,FEDEX,SAGAWA and SCOREJP; 4. Import Export; 5. Land Transportation. We seek no strongest only more specialized, senior. Your satisfied will be our maximal pride. Shenzhen Hyun Young International Transportation CO.,LTD Jacky Yang Add: Floor 78, South Bao’an Road, Luohu District, Shenzhen, Guangdong, China. https://picasaweb.google.com/lh/sredir?uname=113765074073636421886target=ALBUMid=5867348222053903169authkey=Gv1sRgCIurka7titavLwinvite=CPCp2usMfeat=email ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
Hi Andreas and Polytropon,
In the case your are tracking -RELEASE branch, you can use freebsd-update
tool to apply binary security patches on your system and upgrade versions
(e.g. 9.0 to 9.1 or 9.x to 10.0 when available).
Freebsd-update tool apply binary updates to your system and GENERIC kernel.
Furthermore, this tool syncs sources (by default). So if you are using
custom kernel, you just have to rebuild and install your custom kernel.
It is recommended to not use SVN to update your system sources if you are
using freebsd-update tool to avoid troubles.
Regards,
Alexandre
On Tue, Apr 16, 2013 at 10:18 PM, Polytropon free...@edvax.de wrote:
On Tue, 16 Apr 2013 21:38:16 +0200, andreas scherrer wrote:
Dear FreeBSD savvies
I am (still) struggling to understand how to keep my FreeBSD system up
to date (world/system, not ports). I want to track RELEASE (not a
development branch) and I want to receive security related updates. And
I want to run a custom kernel.
Without actually havint tested it, it seems that if you want
to use freebsd-update (binary updating), you should note this:
In /etc/freebsd-update.conf, you should have the line for what
to update as Components src world.
This should prevent overwriting of the kernel, but you need to
compile your kernel and install it. The component src will
make sure you have the proper kernel sources. I assume a custom
kernel configuration file in /usr/src/sys/{i386|amd64}/conf/
is _not_ being overwritten by freebsd-update.
Use the -r option of freebsd-update to specify the correct
release if required. It should follow -RELEASE-pN for the
currentl patchlevel N (which you intend to follow) normally.
From what I understand I cannot use freebsd-update in this case
because it will invariably either overwrite my custom kernel (if I have
Components kernel in the config file) or not update the kernel sources
in /usr/src/sys (when I do not have Components kernel in the config
file). See [1].
As far as I read from man freebsd-update.conf, the src component
will not exclude kernel sources; kernel refers to the kernel and
the modules as binary stuff.
This is the relevant text passage:
The components are ``src''
(source code), ``world'' (non-kernel binaries),
and ``kernel''; the sub-components are the indi-
vidual distribution sets generated as part of
the release process (e.g., ``src/base'',
``src/sys'', ``world/base'', ``world/catpages'',
``kernel/smp''). Note that prior to
FreeBSD 6.1, the ``kernel'' component was dis-
tributed as part of ``world/base''.
So src will include src/sys which is the kernel sources you
will need to build your custom kernel.
This leaves me with the only possibility to use SVN to update /usr/src,
right?
No, but it might be the more advanced alternative, and it should
work. Note that in _this_ case, you will also have to rebuild the
world, so kernel and world are in sync after an update. Refer to
the comment header of /usr/src/Makefile for the whole process that
has to be performed after updating (or see in the Handbook: the
section about updating by source).
I have a copy of the SVN sources (for the outdated RELEASE-9.0.0
but that's a different story), see below for svn info). As I
understand [2] I cannot mix freebsd-update and SVN, right?
It could cause trouble. Deciding for _one_ way should be better.
So I can run svn update in /usr/src whenever I like. But what then? Do
I need to rebuild the world and my custom kernel every time I run svn
update (and there are some updates)?
Yes, or better: As soon as it is required. This depends on _what_
has been part of the update. For example, kernel updates _can_
require updates of userland programs or libraries, but it's also
possible that it's not the case. To be sure, rebuild.
I'm on a low powered consumer
device and it takes considerable amount of time to build the world and
kernel (plus I still don't feel comfortable doing such tasks remotely).
In this case, use freebsd-update as explained at the beginning of
my message: Update components world and src, leave out kernel,
the rebuild the kernel by source and install it. Then reboot.
Is this really the way to do it or am I missing something?
There are _several_ ways to do it. :-)
There are quite some posts, websites and threads out there (see [3] or
[4] for example) about this topic but (surprisingly?) I could not (yet)
find a conclusive answer.
This is because the answer depends on what you actually want to do
(follow RELEASE, STABLE, CURRENT), and how you want to do it (binary,
by source).
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
How to manually start firewall after system completed boot.
I have special purpose situation where I need to wait until the boot process has completed the starting of the system and then start the firewall (ipfw or pf). Commenting out the firewall statements from the hosts /etc/rc.conf does stop the firewall from starting at boot time. Is there some format of the service command that could be used to manually start the selected firewall? Any ideas on how to accomplish this is welcome. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to manually start firewall after system completed boot.
Joe writes: I have special purpose situation where I need to wait until the boot process has completed the starting of the system and then start the firewall (ipfw or pf). Commenting out the firewall statements from the hosts /etc/rc.conf does stop the firewall from starting at boot time. Is there some format of the service command that could be used to manually start the selected firewall? Any ideas on how to accomplish this is welcome. The boot process, as used here, is simply a series of calls to various scripts in /etc/rc.d ... any of which can (theoretically) be invoked by itself. The details of this may be important; _please_ do more research before blowing yourself up. :-) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to manually start firewall after system completed boot.
Le Wed, 17 Apr 2013 08:25:46 -0400, Joe fb...@a1poweruser.com a écrit : Hello, I have special purpose situation where I need to wait until the boot process has completed the starting of the system and then start the firewall (ipfw or pf). Commenting out the firewall statements from the hosts /etc/rc.conf does stop the firewall from starting at boot time. Is there some format of the service command that could be used to manually start the selected firewall? You can use onestart/onestop if the service is not enabled in rc.conf. service pf onestart or /etc/rc.d/pf onestart Regard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.1 Postfix problem
Paul Kraus p...@kraus-haus.org writes: When building postfix under 91. I am running into an odd problem. I use the INST_BASE option, which seems to cause the problem (it worked fine with 9.0). The 'make' goes fine, but the 'make install' fails when trying to install the startup script to /usr/etc/rc.d instead of /etc/rc.d. It works fine if INST-BASE is disabled. I looked through the Makefile but could not suss out how that difference in configuration was actually causing the problem. Has anyone else run into this problem and what was the fix (or did you just install into /usr/local) ? I use /usr/local, but this seems to be a typo in the last checkin, which changed the internal names of the port options to our brave new naming scheme. If you look in the Makefile clause for installing to base, renaming the option itself went correctly, but both halves of the '.if' now invoke USE_RC_SUBR. That's correct for PREFIX, but for installing into base should be USE_RCORDER instead. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pwd.db/spwd.db file corupption when having unsafe system poweroff
Allow me a few additions: On Tue, 16 Apr 2013 16:45:59 -0400, Michael Powell wrote: Pressing the power button for 4 seconds as described is invoking the ACPI layer to stimulate call(s) down to the system BIOS. No. In most (but of course not all) default settings the long press will forcedly (and with _no_ message to the OS) turn off the system's power. The short press will emit the ACPI signal to the OS to deal with the power-off sequence itself. Still it's possible to have a different programming for the button. For example, it seems to be common to have this button perform a ACPI sleep, ACPI hibernate or ACPI powersafe mode on short press, and (as you mentioned) the ACPI power down on long press. But as I said: _What_ the button actually does is defined in the CMOS setup. http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface#Power_states have a look at this page to find out more about the various possible signals (power states). Whatever is set in the BIOS wrt to power control and various power-savings modes are passed through the ACPI layer. The problem with this is the acpi module in FreeBSD may, or may not, be a perfect implementation for every possible piece of hardware in existance. This statement especially applies in regards to laptops, where closing the lid can also trigger a specific signal, and opening the device again sends another signal. Vendors don't agree on how to properly do this, so there are many different ACPI implementations. % ls /boot/kernel/acpi* /boot/kernel/acpi.ko* /boot/kernel/acpi_ibm.ko* /boot/kernel/acpi_aiboost.ko* /boot/kernel/acpi_panasonic.ko* /boot/kernel/acpi_asus.ko* /boot/kernel/acpi_sony.ko* /boot/kernel/acpi_dock.ko* /boot/kernel/acpi_toshiba.ko* /boot/kernel/acpi_fujitsu.ko* /boot/kernel/acpi_video.ko* /boot/kernel/acpi_hp.ko*/boot/kernel/acpi_wmi.ko* You can see from this example that FreeBSD only supports a subset of what can be considered possible. Of course there are many fields of compatibility, but it may still result in specific hardware not working properly -- mostly in the area of laptops and their accessories (like docking stations). The piece of that which really concerns me are individual manufactuer BIOS quirks can be just enough 'off' so as to misbehave even when the FreeBSD acpi implentation is basically sound. Even though I did not experience that myself, it can be considered possible. A sloppy ACPI implementation can be the source of many kinds of trouble, even involving such simple devices like a power button. The jist of this is (IMHO here - YMMV) is I consider it a bad procedure to turn off a server as you've described. Definitely. :-) Use the shutdown command properly instead. I would never do what your coworker did to any of my servers. A mechanicl protection could prevent that. Caveat being sometimes you have no other choice but to do a hard power-down. A hard power-down is done by using the switch on the power supply, and not using the ACPI/BIOS from pressing the power switch on the front. This is also possible. Both this _and_ the default forced power off (the long press in many defaults) equal the action of pulling the power cord. When you do have an 'uh-oh' like this, FreeBSD normally boots back into an unclean file system with corresponding whinings and complaints about how the file system(s) were not properly dismounted. This is an intended behaviour. TO prevent further damage and to make data recovery possible (worst case), the system does not try to boot by all means, just to make the (clueless) user happy. :-) Normally a background fsck ensues after 60 seconds of idle. This _can_ be dangerous, because at this time, the system has already been booted into a somehow working state. You should ask yourself the question: Can I invest the time to have _no_ background fsck (i. e., a foreground fsck which maybe will ask prior to doing anything heavy) to make sure my data is consistent, because it is important data which _needs_ to be okay? In this case, put background_fsck=NO in /etc/rc.conf -- and wait. When using UFS, there _may_ be file system damages so severe that fsck will _not_ correct them manually (which often leads to data loss of important data that could have been saved if the proper _user decision_ would have been taken place). This will only happen in the interactive mode at system startup. In your case whatever files were left open and not properly closed this background fsck, had it been allowed to run and complete, would have cleaned this up. Maybe, maybe not. It highly depends on what actually happened, and it's nearly impossible to find that out, especially when there is no control about what the background fsck does (while the system is already happily running and humming). The problem starts when someone presses the power off button again, and again, before this process
zdb queries give error on healthy zpools
*SOLVED* I apparently already had an answer from a previous question of mine. http://freebsd.1045724.n5.nabble.com/ZFS-How-to-fix-corrupt-ZDB-td5758864.html # zpool reguid pool Corrects the problem. With thanks to Steve Hartland for that tip. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/zdb-queries-give-error-on-healthy-zpools-tp5804408p5804493.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
vBSDCon Announcement
vBSDCon • SAVE THE DATE! Dulles, VA • October 25-27, 2013 Please join us October 25-27, 2013 at the Hyatt in Dulles, Virginia for the first biennial vBSDCon event. This exciting weekend will bring together members of the BSD community for a series of roundtable discussions, educational sessions, best practice conversations, and exclusive networking opportunities. See below for details on this industry weekend not to be missed: AGENDA • Friday, October 25: Evening Reception • Saturday, October 26: General Session, Birds of a Feather Sessions • Sunday, October 27: General Session, Breakout Sessions WHO SHOULD ATTEND • Developers • Engineers • Administrators • Innovators TOPICS • PkgNG w/ Baptiste Daroussin • A comprehensive look at bsdinstall with Devin Teske • Netflix Demo/Presentation with Scott Long • netmap with Luigi Rizzo • Migration from GCC to LLVM/Clang with David Chisnall Registration information will be sent to you in May! Questions? Please contact: eventst...@verisign.commailto:eventst...@verisign.com -- Vincent (Rick) Miller Systems Engineer vmil...@verisign.com t: 703.948.4395 m: 703.581.3068 12061 Bluemont Way, Reston, VA 20190 http://www.verisigninc.com “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.” ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
chromium won't build on FreeBSD 9.1 ports rev 315799
Hello list, In my daily vulnerability report, I'm seeing this: Affected package: chromium-25.0.1364.160 Type of problem: chromium -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/bdd48858-9656-11e2-a9a8-00262d5ed8ee.html Latest ports update as of 1630 UTC - 315981 I try to update it. I get: portupgrade chromium --- Upgrading 'chromium-25.0.1364.160' to 'chromium-25.0.1364.172' (www/chromium) --- Building '/usr/ports/www/chromium' === Cleaning for chromium-25.0.1364.172 To build Chromium, you should have around 1 GB of memory and a fair amount of free diskspace (~ 2.2GB). === chromium-25.0.1364.172 has known vulnerabilities: Affected package: chromium-25.0.1364.172 Type of problem: chromium -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/bdd48858-9656-11e2-a9a8-00262d5ed8ee.html = Please update your ports tree and try again. *** [check-vulnerable] Error code 1 Stop in /usr/ports/www/chromium. *** [build] Error code 1 Stop in /usr/ports/www/chromium. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20130417-83106-6ngbzf-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=chromium-25.0.1364.160 UPGRADE_PORT_VER=25.0.1364.160 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/chromium (chromium-25.0.1364.160) (unknown build error) = I know the code is now at revision 26.something. I have a look at https://wiki.freebsd.org/Chromium and follow the instructions there. I get up to here: ../../depot_tools/gclient sync --force Error: Can't update/checkout ~/tmp/depot_tools/src if an unversioned directory is present. Delete the directory and try again. Please advise if/how I can proceed? thanks, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: chromium won't build on FreeBSD 9.1 ports rev 315799
On 04/17/13 18:40, John wrote: Hello list, In my daily vulnerability report, I'm seeing this: Affected package: chromium-25.0.1364.160 Type of problem: chromium -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/bdd48858-9656-11e2-a9a8-00262d5ed8ee.html Latest ports update as of 1630 UTC - 315981 I try to update it. I get: portupgrade chromium --- Upgrading 'chromium-25.0.1364.160' to 'chromium-25.0.1364.172' (www/chromium) --- Building '/usr/ports/www/chromium' === Cleaning for chromium-25.0.1364.172 To build Chromium, you should have around 1 GB of memory and a fair amount of free diskspace (~ 2.2GB). === chromium-25.0.1364.172 has known vulnerabilities: Affected package: chromium-25.0.1364.172 Type of problem: chromium -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/bdd48858-9656-11e2-a9a8-00262d5ed8ee.html = Please update your ports tree and try again. *** [check-vulnerable] Error code 1 Stop in /usr/ports/www/chromium. *** [build] Error code 1 Stop in /usr/ports/www/chromium. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20130417-83106-6ngbzf-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=chromium-25.0.1364.160 UPGRADE_PORT_VER=25.0.1364.160 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/chromium (chromium-25.0.1364.160) (unknown build error) = I know the code is now at revision 26.something. I have a look at https://wiki.freebsd.org/Chromium and follow the instructions there. I get up to here: ../../depot_tools/gclient sync --force Error: Can't update/checkout ~/tmp/depot_tools/src if an unversioned directory is present. Delete the directory and try again. Please advise if/how I can proceed? thanks, ___ You can try: portupgrade -m -DDISABLE_VULNERABILITIES chromium From what I can see there is no update yet for the mentioned security vulnerability. Regards, Andrei ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Bad kernel with make -j?
Everyone: I've just had to resurrect a machine which apparently failed because the kernel was built with the make -j option. As reported in the make(1) man page, the purpose of the -j option is to let the make program build multiple portions of a program concurrently on a machine with multiple CPUs. The idea is to make use of SMP to speed up the build process. Unfortunately, after updating a FreeBSD 9.0 system with freebsd-update (and seeing some changes that would affect the custom kernel the machine was running), I rebuilt the kernel using the -j5 option. (The machine has 2 cores and 4 threads, but threads block due to I/O as well as memory access. So, when it works properly, -j5 is the fastest option.) The result was a kernel in which some compiled-in modules -- in particular, netgraph nodes -- weren't accessible. mpd5 began spewing odd messages, and VPN connections would not come up. I'd built the kernel with the NO_MODULES option, so the modules that were missing couldn't be loaded dynamically. Rebuilding the kernel using a single-threaded make solved the problem. Have others seen the same symptoms? I'd like to be able to do fast, multithreaded kernel builds, but will obviously have to avoid it if the resulting kernels are corrupted. --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
portmaster -- no execute command
Does portmaster have a --noexecute flag like portupgrade? Specifically, I want to run the following command and see exactly what would be updated / modified sans actually doing it. portmaster -o new_app old_app -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
Thank you very much for your detailed answer!
on 16.4.13 22:18 Polytropon said the following:
On Tue, 16 Apr 2013 21:38:16 +0200, andreas scherrer wrote:
I am (still) struggling to understand how to keep my FreeBSD system up
to date (world/system, not ports). I want to track RELEASE (not a
development branch) and I want to receive security related updates. And
I want to run a custom kernel.
Without actually havint tested it, it seems that if you want
to use freebsd-update (binary updating), you should note this:
In /etc/freebsd-update.conf, you should have the line for what
to update as Components src world.
That's what I thought (and currently have).
This should prevent overwriting of the kernel, but you need to
compile your kernel and install it. The component src will
make sure you have the proper kernel sources. I assume a custom
kernel configuration file in /usr/src/sys/{i386|amd64}/conf/
is _not_ being overwritten by freebsd-update.
A custom kernel configuration file is *not* overwritten by
freebsd-update, I can confirm this. Of course I will have to compile and
install my custom kernel manually.
For some reason I was under the impression that /usr/src/sys is not
being updated by freebsd-update if I remove kernel from the
Components directive in freebsd-update.conf. But I might be wrong (I
will check).
Maybe related to this: how does freebsd-update know what
sources/binaries to get when I don't use the -r switch? Does it rely
on /usr/src/sys/conf/newvers.sh?
Could it be that I never saw a change to my kernel sources
(/usr/src/sys) because freebsd-update was tracking some static sources?
[snip]
I'm on a low powered consumer
device and it takes considerable amount of time to build the world and
kernel (plus I still don't feel comfortable doing such tasks remotely).
In this case, use freebsd-update as explained at the beginning of
my message: Update components world and src, leave out kernel,
the rebuild the kernel by source and install it. Then reboot.
That's what I am planning to do. Let's see.
As I currently have a checkout from SVN in /urs/src I need to get rid of
this. Can I just copy (read: move) back my previous /usr/src directory
and continue to use freebsd-update? I think this should work, right? I
am just not sure if freebsd-update still knows what sources/binaries
to track (see my previous comment about how freebsd-update knows what
source to use).
Cheers
andreas
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bad kernel with make -j?
on 17.4.13 21:18 Brett Glass said the following: I've just had to resurrect a machine which apparently failed because the kernel was built with the make -j option. [snip] The result was a kernel in which some compiled-in modules -- in particular, netgraph nodes -- weren't accessible. mpd5 began spewing odd messages, and VPN connections would not come up. I'd built the kernel with the NO_MODULES option, so the modules that were missing couldn't be loaded dynamically. Rebuilding the kernel using a single-threaded make solved the problem. I am not very experienced but I stumbled over the following note in /usr/src/UPDATING before: Avoid using make -j when upgrading. While generally safe, there are sometimes problems using -j to upgrade. If your upgrade fails with -j, please try again without -j. From time to time in the past there have been problems using -j with buildworld and/or installworld. This is especially true when upgrading between distant versions (eg one that cross a major release boundary or several minor releases, or when several months have passed on the -current branch). Maybe that's a hint? --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Cheers andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portmaster -- no execute command
On Wed, 17 Apr 2013 16:34:24 -0400, Jerry wrote: Does portmaster have a --noexecute flag like portupgrade? Specifically, I want to run the following command and see exactly what would be updated / modified sans actually doing it. portmaster -o new_app old_app Is the -n option what you are looking for? From man portmaster: -n run through all steps, but do not make or install any ports This common flag seems to be allowed for installation via -o, according to the synopsis: portmaster [Common Flags] -o new port dir in /usr/ports installed port -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keeping FreeBSD with custom kernel up to date: freebsd-update no option?
On Wed, 17 Apr 2013 22:37:06 +0200, andreas scherrer wrote: For some reason I was under the impression that /usr/src/sys is not being updated by freebsd-update if I remove kernel from the Components directive in freebsd-update.conf. But I might be wrong (I will check). According to the documentation, /usr/src (and therefor the /usr/src/sys subtree) is part of the src component, not of kernel, so it should be updated properly. Maybe related to this: how does freebsd-update know what sources/binaries to get when I don't use the -r switch? Does it rely on /usr/src/sys/conf/newvers.sh? Could it be that I never saw a change to my kernel sources (/usr/src/sys) because freebsd-update was tracking some static sources? Not neccessarily. For example, if only a userland program has received a security update, and the kernel was kept the same, no change would be done in /usr/src/sys. In this case, the kernel version output (as seen by the uname program) would not have changed. As I currently have a checkout from SVN in /urs/src I need to get rid of this. Can I just copy (read: move) back my previous /usr/src directory and continue to use freebsd-update? You should not switch between both methods, it may cause problems. The simplest way would be to # mv /usr/src /usr/src.svn and let freebsd-update populate the sources with the required version. Note that it will install the world your (custom) kernel will finally have to match, and so it should make sure you have the correct revision of the sources to avoid a version conflict. However, it's basically not a problem to use SVN to track -RELEASE, but in this case, you should recompile world and kernel from that sources, instead of relying on freebsd-update for a binary update of the world only. But as you said you're only interested in a custom kernel (which _requires_ building from source), you can safely leave everything else to freebsd-update and don't use SVN. (It would be a totally different thing if you would track -STABLE or -CURRENT which is not possible with freebsd-update, and which would _force_ you to build everything from source.) By following -RELEASE, freebsd-update will apply _that_ snapshot of the source tree and the prebuild world and kernel at the revision when X.Y-RELEASE-pZ has been verified, sloppily said. So it basically doesn't matter what sources you have on your machine (or even if you have any sources) as long as you're not going to compile anything. But because this is a requirement in your specific setting, freebsd-update will take care of that by having the src component on its list. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: chromium won't build on FreeBSD 9.1 ports rev 315799
On 17/04/2013 19:27, Andrei Brezan wrote: You can try: portupgrade -m -DDISABLE_VULNERABILITIES chromium From what I can see there is no update yet for the mentioned security vulnerability. Regards, Andrei Hi Andrei It seems there is an update in the source but not in the ports. Source is up to 26.mumble -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
gmultipath, ses and shared disks / cant seem to share between local nodes
Ok, maybe im at a loss here in the way my brain is viewing this we have a box, its got 2 nodes in the chassis, and 32 sata drives attached to a SATA/SAS backplane via 4 (2 per node) LSI MPT SAS2 cards should i not logically be seeing 4 controllers X #drive count ?? camcontrol devlist shows 32 devices, daX,passX and sesX,passX SEAGATE ST33000650SS 0004at scbus0 target 9 lun 0 (da0,pass0) STORBRICK-3 1400at scbus0 target 10 lun 0 (ses0,pass1) SEAGATE ST33000650SS 0004at scbus0 target 11 lun 0 (da1,pass2) STORBRICK-1 1400at scbus0 target 12 lun 0 (ses1,pass3) SEAGATE ST33000650SS 0004at scbus0 target 13 lun 0 (da2,pass4) STORBRICK-2 1400at scbus0 target 14 lun 0 (ses2,pass5) SEAGATE ST33000650SS 0004at scbus0 target 15 lun 0 (da3,pass6) STORBRICK-4 1400at scbus0 target 16 lun 0 (ses3,pass7) SEAGATE ST33000650SS 0004at scbus0 target 17 lun 0 (da4,pass8) STORBRICK-6 1400at scbus0 target 18 lun 0 (ses4,pass9) SEAGATE ST33000650SS 0004at scbus0 target 19 lun 0 (da5,pass10) STORBRICK-0 1400at scbus0 target 20 lun 0 (ses5,pass11) SEAGATE ST33000650SS 0004at scbus0 target 21 lun 0 (da6,pass12) STORBRICK-7 1400at scbus0 target 22 lun 0 (ses6,pass13) SEAGATE ST33000650SS 0004at scbus0 target 23 lun 0 (da7,pass14) STORBRICK-5 1400at scbus0 target 24 lun 0 (ses7,pass15) SEAGATE ST9300605SS 0004 at scbus1 target 0 lun 0 (da8,pass16) SEAGATE ST9300605SS 0004 at scbus1 target 1 lun 0 (da9,pass17) STORBRICK-3 1400at scbus8 target 10 lun 0 (ses8,pass19) SEAGATE ST33000650SS 0004at scbus8 target 11 lun 0 (da11,pass20) STORBRICK-1 1400at scbus8 target 12 lun 0 (ses9,pass21) SEAGATE ST33000650SS 0004at scbus8 target 13 lun 0 (da12,pass22) STORBRICK-2 1400at scbus8 target 14 lun 0 (ses10,pass23) SEAGATE ST33000650SS 0004at scbus8 target 15 lun 0 (da13,pass24) STORBRICK-4 1400at scbus8 target 16 lun 0 (ses11,pass25) SEAGATE ST33000650SS 0004at scbus8 target 17 lun 0 (da14,pass26) STORBRICK-6 1400at scbus8 target 18 lun 0 (ses12,pass27) SEAGATE ST33000650SS 0004at scbus8 target 19 lun 0 (da15,pass28) STORBRICK-0 1400at scbus8 target 20 lun 0 (ses13,pass29) SEAGATE ST33000650SS 0004at scbus8 target 21 lun 0 (da16,pass30) STORBRICK-7 1400at scbus8 target 22 lun 0 (ses14,pass31) SEAGATE ST33000650SS 0004at scbus8 target 23 lun 0 (da17,pass32) STORBRICK-5 1400at scbus8 target 24 lun 0 (ses15,pass33) USB 2.0 Flash Drive 8.07 at scbus9 target 0 lun 0 (da18,pass34) we would like to create a zpool from all the devices, that in theory if nodeA failed then nodeB could force import the pool, nodeA and NodeB are attached through dual LSI controllers, to the SATA/SAS backplane. but i cant seem to create a zpool from sesX or passX devices, i can however create a 16 drive zp0ol on either node, from any daX device. what did i miss? ive looked at gmirror, and also ses documents. Any insight is appreciated, thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmultipath, ses and shared disks / cant seem to share between local nodes
On Apr 17, 2013, at 3:26 PM, Outback Dingo wrote: Ok, maybe im at a loss here in the way my brain is viewing this we have a box, its got 2 nodes in the chassis, and 32 sata drives attached to a SATA/SAS backplane via 4 (2 per node) LSI MPT SAS2 cards should i not logically be seeing 4 controllers X #drive count ?? camcontrol devlist shows 32 devices, daX,passX and sesX,passX SEAGATE ST33000650SS 0004at scbus0 target 9 lun 0 (da0,pass0) STORBRICK-3 1400at scbus0 target 10 lun 0 (ses0,pass1) SEAGATE ST33000650SS 0004at scbus0 target 11 lun 0 (da1,pass2) STORBRICK-1 1400at scbus0 target 12 lun 0 (ses1,pass3) SEAGATE ST33000650SS 0004at scbus0 target 13 lun 0 (da2,pass4) STORBRICK-2 1400at scbus0 target 14 lun 0 (ses2,pass5) SEAGATE ST33000650SS 0004at scbus0 target 15 lun 0 (da3,pass6) STORBRICK-4 1400at scbus0 target 16 lun 0 (ses3,pass7) SEAGATE ST33000650SS 0004at scbus0 target 17 lun 0 (da4,pass8) STORBRICK-6 1400at scbus0 target 18 lun 0 (ses4,pass9) SEAGATE ST33000650SS 0004at scbus0 target 19 lun 0 (da5,pass10) STORBRICK-0 1400at scbus0 target 20 lun 0 (ses5,pass11) SEAGATE ST33000650SS 0004at scbus0 target 21 lun 0 (da6,pass12) STORBRICK-7 1400at scbus0 target 22 lun 0 (ses6,pass13) SEAGATE ST33000650SS 0004at scbus0 target 23 lun 0 (da7,pass14) STORBRICK-5 1400at scbus0 target 24 lun 0 (ses7,pass15) SEAGATE ST9300605SS 0004 at scbus1 target 0 lun 0 (da8,pass16) SEAGATE ST9300605SS 0004 at scbus1 target 1 lun 0 (da9,pass17) STORBRICK-3 1400at scbus8 target 10 lun 0 (ses8,pass19) SEAGATE ST33000650SS 0004at scbus8 target 11 lun 0 (da11,pass20) STORBRICK-1 1400at scbus8 target 12 lun 0 (ses9,pass21) SEAGATE ST33000650SS 0004at scbus8 target 13 lun 0 (da12,pass22) STORBRICK-2 1400at scbus8 target 14 lun 0 (ses10,pass23) SEAGATE ST33000650SS 0004at scbus8 target 15 lun 0 (da13,pass24) STORBRICK-4 1400at scbus8 target 16 lun 0 (ses11,pass25) SEAGATE ST33000650SS 0004at scbus8 target 17 lun 0 (da14,pass26) STORBRICK-6 1400at scbus8 target 18 lun 0 (ses12,pass27) SEAGATE ST33000650SS 0004at scbus8 target 19 lun 0 (da15,pass28) STORBRICK-0 1400at scbus8 target 20 lun 0 (ses13,pass29) SEAGATE ST33000650SS 0004at scbus8 target 21 lun 0 (da16,pass30) STORBRICK-7 1400at scbus8 target 22 lun 0 (ses14,pass31) SEAGATE ST33000650SS 0004at scbus8 target 23 lun 0 (da17,pass32) STORBRICK-5 1400at scbus8 target 24 lun 0 (ses15,pass33) USB 2.0 Flash Drive 8.07 at scbus9 target 0 lun 0 (da18,pass34) we would like to create a zpool from all the devices, that in theory if nodeA failed then nodeB could force import the pool, gmultipath (which you mention in the subject) is the appropriate tool for this, but there's no need for an import of the pool if you build the pool out of multipath devices. In our experience, we can pull a cable and zfs continues working just fine. In other words, don't build the pool out of the devices, put a gmultipath label on each device and then use /dev/multipath/LABEL for the zpool devices. nodeA and NodeB are attached through dual LSI controllers, to the SATA/SAS backplane. but i cant seem to create a zpool from sesX or passX devices, i can however create a 16 drive zp0ol on either node, from any daX device. what did i miss? ive looked at gmirror, and also ses documents. Any insight is appreciated, thanks in advance. gmirror is the wrong tool, gmultipath is what you want. The basic task is to use gmultipath label FOO da# to write a cookie on the disk (used to identify new/existing paths during GOEM taste events for example). After you've labeled the da# devices with gmultipath you say gmultipath status to see the components of each label and you use multipath/LABEL as your disk name when creating the zpool (these correspond directly to /dev/multipath/LABEL, but zpool create … or zpool add … allow you to omit the leading /dev). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmultipath, ses and shared disks / cant seem to share between local nodes
On Wed, Apr 17, 2013 at 6:39 PM, Teske, Devin devin.te...@fisglobal.comwrote: On Apr 17, 2013, at 3:26 PM, Outback Dingo wrote: Ok, maybe im at a loss here in the way my brain is viewing this we have a box, its got 2 nodes in the chassis, and 32 sata drives attached to a SATA/SAS backplane via 4 (2 per node) LSI MPT SAS2 cards should i not logically be seeing 4 controllers X #drive count ?? camcontrol devlist shows 32 devices, daX,passX and sesX,passX SEAGATE ST33000650SS 0004at scbus0 target 9 lun 0 (da0,pass0) STORBRICK-3 1400at scbus0 target 10 lun 0 (ses0,pass1) SEAGATE ST33000650SS 0004at scbus0 target 11 lun 0 (da1,pass2) STORBRICK-1 1400at scbus0 target 12 lun 0 (ses1,pass3) SEAGATE ST33000650SS 0004at scbus0 target 13 lun 0 (da2,pass4) STORBRICK-2 1400at scbus0 target 14 lun 0 (ses2,pass5) SEAGATE ST33000650SS 0004at scbus0 target 15 lun 0 (da3,pass6) STORBRICK-4 1400at scbus0 target 16 lun 0 (ses3,pass7) SEAGATE ST33000650SS 0004at scbus0 target 17 lun 0 (da4,pass8) STORBRICK-6 1400at scbus0 target 18 lun 0 (ses4,pass9) SEAGATE ST33000650SS 0004at scbus0 target 19 lun 0 (da5,pass10) STORBRICK-0 1400at scbus0 target 20 lun 0 (ses5,pass11) SEAGATE ST33000650SS 0004at scbus0 target 21 lun 0 (da6,pass12) STORBRICK-7 1400at scbus0 target 22 lun 0 (ses6,pass13) SEAGATE ST33000650SS 0004at scbus0 target 23 lun 0 (da7,pass14) STORBRICK-5 1400at scbus0 target 24 lun 0 (ses7,pass15) SEAGATE ST9300605SS 0004 at scbus1 target 0 lun 0 (da8,pass16) SEAGATE ST9300605SS 0004 at scbus1 target 1 lun 0 (da9,pass17) STORBRICK-3 1400at scbus8 target 10 lun 0 (ses8,pass19) SEAGATE ST33000650SS 0004at scbus8 target 11 lun 0 (da11,pass20) STORBRICK-1 1400at scbus8 target 12 lun 0 (ses9,pass21) SEAGATE ST33000650SS 0004at scbus8 target 13 lun 0 (da12,pass22) STORBRICK-2 1400at scbus8 target 14 lun 0 (ses10,pass23) SEAGATE ST33000650SS 0004at scbus8 target 15 lun 0 (da13,pass24) STORBRICK-4 1400at scbus8 target 16 lun 0 (ses11,pass25) SEAGATE ST33000650SS 0004at scbus8 target 17 lun 0 (da14,pass26) STORBRICK-6 1400at scbus8 target 18 lun 0 (ses12,pass27) SEAGATE ST33000650SS 0004at scbus8 target 19 lun 0 (da15,pass28) STORBRICK-0 1400at scbus8 target 20 lun 0 (ses13,pass29) SEAGATE ST33000650SS 0004at scbus8 target 21 lun 0 (da16,pass30) STORBRICK-7 1400at scbus8 target 22 lun 0 (ses14,pass31) SEAGATE ST33000650SS 0004at scbus8 target 23 lun 0 (da17,pass32) STORBRICK-5 1400at scbus8 target 24 lun 0 (ses15,pass33) USB 2.0 Flash Drive 8.07 at scbus9 target 0 lun 0 (da18,pass34) we would like to create a zpool from all the devices, that in theory if nodeA failed then nodeB could force import the pool, gmultipath (which you mention in the subject) is the appropriate tool for this, but there's no need for an import of the pool if you build the pool out of multipath devices. In our experience, we can pull a cable and zfs continues working just fine. In other words, don't build the pool out of the devices, put a gmultipath label on each device and then use /dev/multipath/LABEL for the zpool devices. nodeA and NodeB are attached through dual LSI controllers, to the SATA/SAS backplane. but i cant seem to create a zpool from sesX or passX devices, i can however create a 16 drive zp0ol on either node, from any daX device. what did i miss? ive looked at gmirror, and also ses documents. Any insight is appreciated, thanks in advance. gmirror is the wrong tool, gmultipath is what you want. The basic task is to use gmultipath label FOO da# to write a cookie on the disk (used to identify new/existing paths during GOEM taste events for example). After you've labeled the da# devices with gmultipath you say gmultipath status to see the components of each label and you use multipath/LABEL as your disk name when creating the zpool (these correspond directly to /dev/multipath/LABEL, but zpool create … or zpool add … allow you to omit the leading /dev). sanity check me on node A i did zpool destroy master gmultipath label FOO da0 gmultipath status NameStatus Components multipath/FOO DEGRADED da0 (ACTIVE) multipath/FOO-619648737 DEGRADED da1 (ACTIVE) multipath/FOO-191725652 DEGRADED da2 (ACTIVE) multipath/FOO-1539342315 DEGRADED da3 (ACTIVE) multipath/FOO-1276041606 DEGRADED da4 (ACTIVE) multipath/FOO-2000832198 DEGRADED da5 (ACTIVE) multipath/FOO-1285640577 DEGRADED da6 (ACTIVE) multipath/FOO-1816092574 DEGRADED da7 (ACTIVE) multipath/FOO-110225 DEGRADED da8 (ACTIVE) multipath/FOO-330300690 DEGRADED da9 (ACTIVE) multipath/FOO-92140635 DEGRADED da10 (ACTIVE)
Re: gmultipath, ses and shared disks / cant seem to share between local nodes
On Apr 17, 2013, at 4:10 PM, Outback Dingo wrote: On Wed, Apr 17, 2013 at 6:39 PM, Teske, Devin devin.te...@fisglobal.commailto:devin.te...@fisglobal.com wrote: On Apr 17, 2013, at 3:26 PM, Outback Dingo wrote: Ok, maybe im at a loss here in the way my brain is viewing this we have a box, its got 2 nodes in the chassis, and 32 sata drives attached to a SATA/SAS backplane via 4 (2 per node) LSI MPT SAS2 cards should i not logically be seeing 4 controllers X #drive count ?? camcontrol devlist shows 32 devices, daX,passX and sesX,passX SEAGATE ST33000650SS 0004at scbus0 target 9 lun 0 (da0,pass0) STORBRICK-3 1400at scbus0 target 10 lun 0 (ses0,pass1) SEAGATE ST33000650SS 0004at scbus0 target 11 lun 0 (da1,pass2) STORBRICK-1 1400at scbus0 target 12 lun 0 (ses1,pass3) SEAGATE ST33000650SS 0004at scbus0 target 13 lun 0 (da2,pass4) STORBRICK-2 1400at scbus0 target 14 lun 0 (ses2,pass5) SEAGATE ST33000650SS 0004at scbus0 target 15 lun 0 (da3,pass6) STORBRICK-4 1400at scbus0 target 16 lun 0 (ses3,pass7) SEAGATE ST33000650SS 0004at scbus0 target 17 lun 0 (da4,pass8) STORBRICK-6 1400at scbus0 target 18 lun 0 (ses4,pass9) SEAGATE ST33000650SS 0004at scbus0 target 19 lun 0 (da5,pass10) STORBRICK-0 1400at scbus0 target 20 lun 0 (ses5,pass11) SEAGATE ST33000650SS 0004at scbus0 target 21 lun 0 (da6,pass12) STORBRICK-7 1400at scbus0 target 22 lun 0 (ses6,pass13) SEAGATE ST33000650SS 0004at scbus0 target 23 lun 0 (da7,pass14) STORBRICK-5 1400at scbus0 target 24 lun 0 (ses7,pass15) SEAGATE ST9300605SS 0004 at scbus1 target 0 lun 0 (da8,pass16) SEAGATE ST9300605SS 0004 at scbus1 target 1 lun 0 (da9,pass17) STORBRICK-3 1400at scbus8 target 10 lun 0 (ses8,pass19) SEAGATE ST33000650SS 0004at scbus8 target 11 lun 0 (da11,pass20) STORBRICK-1 1400at scbus8 target 12 lun 0 (ses9,pass21) SEAGATE ST33000650SS 0004at scbus8 target 13 lun 0 (da12,pass22) STORBRICK-2 1400at scbus8 target 14 lun 0 (ses10,pass23) SEAGATE ST33000650SS 0004at scbus8 target 15 lun 0 (da13,pass24) STORBRICK-4 1400at scbus8 target 16 lun 0 (ses11,pass25) SEAGATE ST33000650SS 0004at scbus8 target 17 lun 0 (da14,pass26) STORBRICK-6 1400at scbus8 target 18 lun 0 (ses12,pass27) SEAGATE ST33000650SS 0004at scbus8 target 19 lun 0 (da15,pass28) STORBRICK-0 1400at scbus8 target 20 lun 0 (ses13,pass29) SEAGATE ST33000650SS 0004at scbus8 target 21 lun 0 (da16,pass30) STORBRICK-7 1400at scbus8 target 22 lun 0 (ses14,pass31) SEAGATE ST33000650SS 0004at scbus8 target 23 lun 0 (da17,pass32) STORBRICK-5 1400at scbus8 target 24 lun 0 (ses15,pass33) USB 2.0 Flash Drive 8.07 at scbus9 target 0 lun 0 (da18,pass34) we would like to create a zpool from all the devices, that in theory if nodeA failed then nodeB could force import the pool, gmultipath (which you mention in the subject) is the appropriate tool for this, but there's no need for an import of the pool if you build the pool out of multipath devices. In our experience, we can pull a cable and zfs continues working just fine. In other words, don't build the pool out of the devices, put a gmultipath label on each device and then use /dev/multipath/LABEL for the zpool devices. nodeA and NodeB are attached through dual LSI controllers, to the SATA/SAS backplane. but i cant seem to create a zpool from sesX or passX devices, i can however create a 16 drive zp0ol on either node, from any daX device. what did i miss? ive looked at gmirror, and also ses documents. Any insight is appreciated, thanks in advance. gmirror is the wrong tool, gmultipath is what you want. The basic task is to use gmultipath label FOO da# to write a cookie on the disk (used to identify new/existing paths during GOEM taste events for example). After you've labeled the da# devices with gmultipath you say gmultipath status to see the components of each label and you use multipath/LABEL as your disk name when creating the zpool (these correspond directly to /dev/multipath/LABEL, but zpool create … or zpool add … allow you to omit the leading /dev). sanity check me on node A i did zpool destroy master gmultipath label FOO da0 gmultipath status NameStatus Components multipath/FOO DEGRADED da0 (ACTIVE) multipath/FOO-619648737 DEGRADED da1 (ACTIVE) multipath/FOO-191725652 DEGRADED da2 (ACTIVE) multipath/FOO-1539342315 DEGRADED da3 (ACTIVE) multipath/FOO-1276041606 DEGRADED da4 (ACTIVE) multipath/FOO-2000832198 DEGRADED da5 (ACTIVE) multipath/FOO-1285640577 DEGRADED da6 (ACTIVE) multipath/FOO-1816092574 DEGRADED da7 (ACTIVE) multipath/FOO-110225 DEGRADED da8 (ACTIVE) multipath/FOO-330300690 DEGRADED da9 (ACTIVE) multipath/FOO-92140635 DEGRADED da10
Strange console behavior - hangs every few minutes until a key is pressed
I'm experiencing something odd from a few new servers I've been setting up today. I'll do something at the console that takes some amount of time and produces lots of output such as fetching the ports tree, svn updating /usr/src/, or building world, and the console will hang. The console ceases to produce any additional output until a key is pressed. It doesn't seem to be the case that program execution is affected, the source tree continues to checkout, for example, but the console is 'frozen' and produces no additional output. Has anyone run into this before? Any thoughts as to what's going wrong or how to fix this? I'm running 8.2 and am in the process of updating to 8.3 (buildworld is running at the moment on several of them at the moment, with these hiccups every few minutes.. it's very odd). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmultipath, ses and shared disks / cant seem to share between local nodes
On Wed, Apr 17, 2013 at 7:29 PM, Teske, Devin devin.te...@fisglobal.comwrote: On Apr 17, 2013, at 4:10 PM, Outback Dingo wrote: On Wed, Apr 17, 2013 at 6:39 PM, Teske, Devin devin.te...@fisglobal.comwrote: On Apr 17, 2013, at 3:26 PM, Outback Dingo wrote: Ok, maybe im at a loss here in the way my brain is viewing this we have a box, its got 2 nodes in the chassis, and 32 sata drives attached to a SATA/SAS backplane via 4 (2 per node) LSI MPT SAS2 cards should i not logically be seeing 4 controllers X #drive count ?? camcontrol devlist shows 32 devices, daX,passX and sesX,passX SEAGATE ST33000650SS 0004at scbus0 target 9 lun 0 (da0,pass0) STORBRICK-3 1400at scbus0 target 10 lun 0 (ses0,pass1) SEAGATE ST33000650SS 0004at scbus0 target 11 lun 0 (da1,pass2) STORBRICK-1 1400at scbus0 target 12 lun 0 (ses1,pass3) SEAGATE ST33000650SS 0004at scbus0 target 13 lun 0 (da2,pass4) STORBRICK-2 1400at scbus0 target 14 lun 0 (ses2,pass5) SEAGATE ST33000650SS 0004at scbus0 target 15 lun 0 (da3,pass6) STORBRICK-4 1400at scbus0 target 16 lun 0 (ses3,pass7) SEAGATE ST33000650SS 0004at scbus0 target 17 lun 0 (da4,pass8) STORBRICK-6 1400at scbus0 target 18 lun 0 (ses4,pass9) SEAGATE ST33000650SS 0004at scbus0 target 19 lun 0 (da5,pass10) STORBRICK-0 1400at scbus0 target 20 lun 0 (ses5,pass11) SEAGATE ST33000650SS 0004at scbus0 target 21 lun 0 (da6,pass12) STORBRICK-7 1400at scbus0 target 22 lun 0 (ses6,pass13) SEAGATE ST33000650SS 0004at scbus0 target 23 lun 0 (da7,pass14) STORBRICK-5 1400at scbus0 target 24 lun 0 (ses7,pass15) SEAGATE ST9300605SS 0004 at scbus1 target 0 lun 0 (da8,pass16) SEAGATE ST9300605SS 0004 at scbus1 target 1 lun 0 (da9,pass17) STORBRICK-3 1400at scbus8 target 10 lun 0 (ses8,pass19) SEAGATE ST33000650SS 0004at scbus8 target 11 lun 0 (da11,pass20) STORBRICK-1 1400at scbus8 target 12 lun 0 (ses9,pass21) SEAGATE ST33000650SS 0004at scbus8 target 13 lun 0 (da12,pass22) STORBRICK-2 1400at scbus8 target 14 lun 0 (ses10,pass23) SEAGATE ST33000650SS 0004at scbus8 target 15 lun 0 (da13,pass24) STORBRICK-4 1400at scbus8 target 16 lun 0 (ses11,pass25) SEAGATE ST33000650SS 0004at scbus8 target 17 lun 0 (da14,pass26) STORBRICK-6 1400at scbus8 target 18 lun 0 (ses12,pass27) SEAGATE ST33000650SS 0004at scbus8 target 19 lun 0 (da15,pass28) STORBRICK-0 1400at scbus8 target 20 lun 0 (ses13,pass29) SEAGATE ST33000650SS 0004at scbus8 target 21 lun 0 (da16,pass30) STORBRICK-7 1400at scbus8 target 22 lun 0 (ses14,pass31) SEAGATE ST33000650SS 0004at scbus8 target 23 lun 0 (da17,pass32) STORBRICK-5 1400at scbus8 target 24 lun 0 (ses15,pass33) USB 2.0 Flash Drive 8.07 at scbus9 target 0 lun 0 (da18,pass34) we would like to create a zpool from all the devices, that in theory if nodeA failed then nodeB could force import the pool, gmultipath (which you mention in the subject) is the appropriate tool for this, but there's no need for an import of the pool if you build the pool out of multipath devices. In our experience, we can pull a cable and zfs continues working just fine. In other words, don't build the pool out of the devices, put a gmultipath label on each device and then use /dev/multipath/LABEL for the zpool devices. nodeA and NodeB are attached through dual LSI controllers, to the SATA/SAS backplane. but i cant seem to create a zpool from sesX or passX devices, i can however create a 16 drive zp0ol on either node, from any daX device. what did i miss? ive looked at gmirror, and also ses documents. Any insight is appreciated, thanks in advance. gmirror is the wrong tool, gmultipath is what you want. The basic task is to use gmultipath label FOO da# to write a cookie on the disk (used to identify new/existing paths during GOEM taste events for example). After you've labeled the da# devices with gmultipath you say gmultipath status to see the components of each label and you use multipath/LABEL as your disk name when creating the zpool (these correspond directly to /dev/multipath/LABEL, but zpool create … or zpool add … allow you to omit the leading /dev). sanity check me on node A i did zpool destroy master gmultipath label FOO da0 gmultipath status NameStatus Components multipath/FOO DEGRADED da0 (ACTIVE) multipath/FOO-619648737 DEGRADED da1 (ACTIVE) multipath/FOO-191725652 DEGRADED da2 (ACTIVE) multipath/FOO-1539342315 DEGRADED da3 (ACTIVE) multipath/FOO-1276041606 DEGRADED da4 (ACTIVE) multipath/FOO-2000832198 DEGRADED da5 (ACTIVE) multipath/FOO-1285640577 DEGRADED da6 (ACTIVE) multipath/FOO-1816092574 DEGRADED da7 (ACTIVE)
Re: How to manually start firewall after system completed boot.
On Wed, 17 Apr 2013 08:25:46 -0400, Joe wrote: Is there some format of the service command that could be used to manually start the selected firewall? How about the rc.d framework? # /etc/rc.d/ipfw start Or # service ipfw start Both will honor the firewall_type= setting in /etc/rc.conf (here: for IPFW). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmultipath, ses and shared disks / cant seem to share between local nodes
On Apr 17, 2013, at 4:56 PM, Outback Dingo wrote: On Wed, Apr 17, 2013 at 7:29 PM, Teske, Devin devin.te...@fisglobal.commailto:devin.te...@fisglobal.com wrote: On Apr 17, 2013, at 4:10 PM, Outback Dingo wrote: On Wed, Apr 17, 2013 at 6:39 PM, Teske, Devin devin.te...@fisglobal.commailto:devin.te...@fisglobal.com wrote: On Apr 17, 2013, at 3:26 PM, Outback Dingo wrote: Ok, maybe im at a loss here in the way my brain is viewing this we have a box, its got 2 nodes in the chassis, and 32 sata drives attached to a SATA/SAS backplane via 4 (2 per node) LSI MPT SAS2 cards should i not logically be seeing 4 controllers X #drive count ?? camcontrol devlist shows 32 devices, daX,passX and sesX,passX SEAGATE ST33000650SS 0004at scbus0 target 9 lun 0 (da0,pass0) STORBRICK-3 1400at scbus0 target 10 lun 0 (ses0,pass1) SEAGATE ST33000650SS 0004at scbus0 target 11 lun 0 (da1,pass2) STORBRICK-1 1400at scbus0 target 12 lun 0 (ses1,pass3) SEAGATE ST33000650SS 0004at scbus0 target 13 lun 0 (da2,pass4) STORBRICK-2 1400at scbus0 target 14 lun 0 (ses2,pass5) SEAGATE ST33000650SS 0004at scbus0 target 15 lun 0 (da3,pass6) STORBRICK-4 1400at scbus0 target 16 lun 0 (ses3,pass7) SEAGATE ST33000650SS 0004at scbus0 target 17 lun 0 (da4,pass8) STORBRICK-6 1400at scbus0 target 18 lun 0 (ses4,pass9) SEAGATE ST33000650SS 0004at scbus0 target 19 lun 0 (da5,pass10) STORBRICK-0 1400at scbus0 target 20 lun 0 (ses5,pass11) SEAGATE ST33000650SS 0004at scbus0 target 21 lun 0 (da6,pass12) STORBRICK-7 1400at scbus0 target 22 lun 0 (ses6,pass13) SEAGATE ST33000650SS 0004at scbus0 target 23 lun 0 (da7,pass14) STORBRICK-5 1400at scbus0 target 24 lun 0 (ses7,pass15) SEAGATE ST9300605SS 0004 at scbus1 target 0 lun 0 (da8,pass16) SEAGATE ST9300605SS 0004 at scbus1 target 1 lun 0 (da9,pass17) STORBRICK-3 1400at scbus8 target 10 lun 0 (ses8,pass19) SEAGATE ST33000650SS 0004at scbus8 target 11 lun 0 (da11,pass20) STORBRICK-1 1400at scbus8 target 12 lun 0 (ses9,pass21) SEAGATE ST33000650SS 0004at scbus8 target 13 lun 0 (da12,pass22) STORBRICK-2 1400at scbus8 target 14 lun 0 (ses10,pass23) SEAGATE ST33000650SS 0004at scbus8 target 15 lun 0 (da13,pass24) STORBRICK-4 1400at scbus8 target 16 lun 0 (ses11,pass25) SEAGATE ST33000650SS 0004at scbus8 target 17 lun 0 (da14,pass26) STORBRICK-6 1400at scbus8 target 18 lun 0 (ses12,pass27) SEAGATE ST33000650SS 0004at scbus8 target 19 lun 0 (da15,pass28) STORBRICK-0 1400at scbus8 target 20 lun 0 (ses13,pass29) SEAGATE ST33000650SS 0004at scbus8 target 21 lun 0 (da16,pass30) STORBRICK-7 1400at scbus8 target 22 lun 0 (ses14,pass31) SEAGATE ST33000650SS 0004at scbus8 target 23 lun 0 (da17,pass32) STORBRICK-5 1400at scbus8 target 24 lun 0 (ses15,pass33) USB 2.0 Flash Drive 8.07 at scbus9 target 0 lun 0 (da18,pass34) we would like to create a zpool from all the devices, that in theory if nodeA failed then nodeB could force import the pool, gmultipath (which you mention in the subject) is the appropriate tool for this, but there's no need for an import of the pool if you build the pool out of multipath devices. In our experience, we can pull a cable and zfs continues working just fine. In other words, don't build the pool out of the devices, put a gmultipath label on each device and then use /dev/multipath/LABEL for the zpool devices. nodeA and NodeB are attached through dual LSI controllers, to the SATA/SAS backplane. but i cant seem to create a zpool from sesX or passX devices, i can however create a 16 drive zp0ol on either node, from any daX device. what did i miss? ive looked at gmirror, and also ses documents. Any insight is appreciated, thanks in advance. gmirror is the wrong tool, gmultipath is what you want. The basic task is to use gmultipath label FOO da# to write a cookie on the disk (used to identify new/existing paths during GOEM taste events for example). After you've labeled the da# devices with gmultipath you say gmultipath status to see the components of each label and you use multipath/LABEL as your disk name when creating the zpool (these correspond directly to /dev/multipath/LABEL, but zpool create … or zpool add … allow you to omit the leading /dev). sanity check me on node A i did zpool destroy master gmultipath label FOO da0 gmultipath status NameStatus Components multipath/FOO DEGRADED da0 (ACTIVE) multipath/FOO-619648737 DEGRADED da1 (ACTIVE) multipath/FOO-191725652 DEGRADED da2 (ACTIVE) multipath/FOO-1539342315 DEGRADED da3 (ACTIVE) multipath/FOO-1276041606 DEGRADED da4 (ACTIVE) multipath/FOO-2000832198 DEGRADED da5 (ACTIVE) multipath/FOO-1285640577 DEGRADED da6 (ACTIVE) multipath/FOO-1816092574
Re: gmultipath, ses and shared disks / cant seem to share between local nodes
On Wed, Apr 17, 2013 at 8:05 PM, Teske, Devin devin.te...@fisglobal.comwrote: On Apr 17, 2013, at 4:56 PM, Outback Dingo wrote: On Wed, Apr 17, 2013 at 7:29 PM, Teske, Devin devin.te...@fisglobal.comwrote: On Apr 17, 2013, at 4:10 PM, Outback Dingo wrote: On Wed, Apr 17, 2013 at 6:39 PM, Teske, Devin devin.te...@fisglobal.comwrote: On Apr 17, 2013, at 3:26 PM, Outback Dingo wrote: Ok, maybe im at a loss here in the way my brain is viewing this we have a box, its got 2 nodes in the chassis, and 32 sata drives attached to a SATA/SAS backplane via 4 (2 per node) LSI MPT SAS2 cards should i not logically be seeing 4 controllers X #drive count ?? camcontrol devlist shows 32 devices, daX,passX and sesX,passX SEAGATE ST33000650SS 0004at scbus0 target 9 lun 0 (da0,pass0) STORBRICK-3 1400at scbus0 target 10 lun 0 (ses0,pass1) SEAGATE ST33000650SS 0004at scbus0 target 11 lun 0 (da1,pass2) STORBRICK-1 1400at scbus0 target 12 lun 0 (ses1,pass3) SEAGATE ST33000650SS 0004at scbus0 target 13 lun 0 (da2,pass4) STORBRICK-2 1400at scbus0 target 14 lun 0 (ses2,pass5) SEAGATE ST33000650SS 0004at scbus0 target 15 lun 0 (da3,pass6) STORBRICK-4 1400at scbus0 target 16 lun 0 (ses3,pass7) SEAGATE ST33000650SS 0004at scbus0 target 17 lun 0 (da4,pass8) STORBRICK-6 1400at scbus0 target 18 lun 0 (ses4,pass9) SEAGATE ST33000650SS 0004at scbus0 target 19 lun 0 (da5,pass10) STORBRICK-0 1400at scbus0 target 20 lun 0 (ses5,pass11) SEAGATE ST33000650SS 0004at scbus0 target 21 lun 0 (da6,pass12) STORBRICK-7 1400at scbus0 target 22 lun 0 (ses6,pass13) SEAGATE ST33000650SS 0004at scbus0 target 23 lun 0 (da7,pass14) STORBRICK-5 1400at scbus0 target 24 lun 0 (ses7,pass15) SEAGATE ST9300605SS 0004 at scbus1 target 0 lun 0 (da8,pass16) SEAGATE ST9300605SS 0004 at scbus1 target 1 lun 0 (da9,pass17) STORBRICK-3 1400at scbus8 target 10 lun 0 (ses8,pass19) SEAGATE ST33000650SS 0004at scbus8 target 11 lun 0 (da11,pass20) STORBRICK-1 1400at scbus8 target 12 lun 0 (ses9,pass21) SEAGATE ST33000650SS 0004at scbus8 target 13 lun 0 (da12,pass22) STORBRICK-2 1400at scbus8 target 14 lun 0 (ses10,pass23) SEAGATE ST33000650SS 0004at scbus8 target 15 lun 0 (da13,pass24) STORBRICK-4 1400at scbus8 target 16 lun 0 (ses11,pass25) SEAGATE ST33000650SS 0004at scbus8 target 17 lun 0 (da14,pass26) STORBRICK-6 1400at scbus8 target 18 lun 0 (ses12,pass27) SEAGATE ST33000650SS 0004at scbus8 target 19 lun 0 (da15,pass28) STORBRICK-0 1400at scbus8 target 20 lun 0 (ses13,pass29) SEAGATE ST33000650SS 0004at scbus8 target 21 lun 0 (da16,pass30) STORBRICK-7 1400at scbus8 target 22 lun 0 (ses14,pass31) SEAGATE ST33000650SS 0004at scbus8 target 23 lun 0 (da17,pass32) STORBRICK-5 1400at scbus8 target 24 lun 0 (ses15,pass33) USB 2.0 Flash Drive 8.07 at scbus9 target 0 lun 0 (da18,pass34) we would like to create a zpool from all the devices, that in theory if nodeA failed then nodeB could force import the pool, gmultipath (which you mention in the subject) is the appropriate tool for this, but there's no need for an import of the pool if you build the pool out of multipath devices. In our experience, we can pull a cable and zfs continues working just fine. In other words, don't build the pool out of the devices, put a gmultipath label on each device and then use /dev/multipath/LABEL for the zpool devices. nodeA and NodeB are attached through dual LSI controllers, to the SATA/SAS backplane. but i cant seem to create a zpool from sesX or passX devices, i can however create a 16 drive zp0ol on either node, from any daX device. what did i miss? ive looked at gmirror, and also ses documents. Any insight is appreciated, thanks in advance. gmirror is the wrong tool, gmultipath is what you want. The basic task is to use gmultipath label FOO da# to write a cookie on the disk (used to identify new/existing paths during GOEM taste events for example). After you've labeled the da# devices with gmultipath you say gmultipath status to see the components of each label and you use multipath/LABEL as your disk name when creating the zpool (these correspond directly to /dev/multipath/LABEL, but zpool create … or zpool add … allow you to omit the leading /dev). sanity check me on node A i did zpool destroy master gmultipath label FOO da0 gmultipath status NameStatus Components multipath/FOO DEGRADED da0 (ACTIVE) multipath/FOO-619648737 DEGRADED da1 (ACTIVE) multipath/FOO-191725652 DEGRADED da2 (ACTIVE) multipath/FOO-1539342315 DEGRADED da3 (ACTIVE) multipath/FOO-1276041606 DEGRADED da4 (ACTIVE)
SV: Strange console behavior - hangs every few minutes until a key is pressed
I'm seeing the same type of behaviour on my computer. It's a 9.1-RELEASE with xfce as desktop environment. I usually ssh to a remote server and do port upgrades. I leave the terminal on it's own desktop and upon returning it's frozen. I can't get it to react on keyboard input. I close the terminal window and reconnect to solve this. /Leslie Originalmeddelande Från: David Noel david.i.n...@gmail.com Datum: Till: freebsd-questions@freebsd.org Rubrik: Strange console behavior - hangs every few minutes until a key is pressed I'm experiencing something odd from a few new servers I've been setting up today. I'll do something at the console that takes some amount of time and produces lots of output such as fetching the ports tree, svn updating /usr/src/, or building world, and the console will hang. The console ceases to produce any additional output until a key is pressed. It doesn't seem to be the case that program execution is affected, the source tree continues to checkout, for example, but the console is 'frozen' and produces no additional output. Has anyone run into this before? Any thoughts as to what's going wrong or how to fix this? I'm running 8.2 and am in the process of updating to 8.3 (buildworld is running at the moment on several of them at the moment, with these hiccups every few minutes.. it's very odd). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
