Re: freebsd-update and sources of 9.1-RC3
On 11/03/2012 05:03 PM, jb wrote: Eugene Grosbein eugen at grosbein.net writes: ... My real question is how make freebsd-update download sources they are not installed? I am not 110% sure, but you can not. When freebsd-update runs, it checks its config file /etc/freebsd-update.conf and then takes inventory of your system (that's why it is called update, and that's why you do not get new src set). FREEBSD-UPDATE(8) does not give any override option. So, here you are. But next time (assuming you keep your src) you will be fine. jb Can't this be accomplished by setting StrictComponents yes in /etc/freebsd-update.conf ? Then feebsd-update does not try to figure out the components to update by itself, but updates the components mentioned in Components src world kernel I didn't try what happens if no source is installed. This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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: Why is SU+J undesirable on SSDs?
I personally let it be enabled during installation. I noticed that I was getting errors on fsck even after clean shutdown. After noticing it, I disabled it and the problems go away. Also, fsck works really fast so I don't see much advantage with SU+J. -- Sent from my phone. Please excuse my brevity. Brett Glass br...@lariat.net wrote: Have been following the thread related to SU+J, and am wondering: why is it considered to be undesirable on SSDs (assuming that they have good wear leveling)? I have been enabling it on systems with SSDs, hoping that between the lack of rotating media and the journaling I would have very robust systems. --Brett Glass ___ 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: SU+J on 9.1-RC2 ISO
On 11/04/2012 06:19 AM, Zoran Kolic wrote: There's an existing checkbox to disable it. There was substantial consensus for 9.0 that SUJ was something we wanted Nice to hear. I assume you mean check box during install process? Not mentioned in install guide in handbook. So, after I accept guided partitioning, I should go to modify or else? Sorry to bother again and again, but it is not clear to me at the moment. I'd avoid further tunefs if possible. If not possible, let me clear that branch 8 has no J as default and I found myself wondering. Correct me if I'm wrong. I have to go to single user mode first. Make fsck on partition that contains freebsd-ufs ( / ). Check options for that partition with tunefs -p partition. What exact name that partition would have? Next I have to disable journaling with -j disable and enable trim with -t enable. Reboot and voila? People mention file or partition that has to be deleted. Next few days I will put ssd into laptop and manage install, when release shows up. If there is another point I have to choose for journaling, let me know. Best regards all Zoran I have just installed fresh from 9.1-RC3 ISO and cannot find a checkbox to disable journaling or enable TRIM. Do I miss something here? The only way I can find to customize is to go to the shell, which is an option in bsdinstall partedit and then gpart and newfs from there. This way I can align to 1 or 2 MB, enable TRIM and disable journaling, and make use of all options someone desires. Also I tried using the shell at the end of the install to disable journaling, but this cannot be done since /mnt is busy. Just rebooting to single user mode after the install and then tunefs -j disable /dev/ada0p2 works for me. Replace ada0 with the device your disk is on, p2 is the defalt partition for / After a reboot then I just removed /.sujournal Still I have send a pr with patch to change the default, let's see what goes. This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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: SU+J on 9.1-RC2 ISO
On 11/3/2012 1:31, Mateusz Guzik wrote: Currently when you try to take a snapshot, the kernel checks whether SUJ is enabled on specified mount-point, and if yes it returns EOPNOTSUPP. See this commit (MFCed as r230725): http://svnweb.freebsd.org/base?view=revisionamp;revision=230250 Ahhh excellent to hear. I partition manually these days with 9.0-R because most servers are either using gmirror, which I want setup before the install, or a RAID card which means partitions need to be aligned to the stripe boundaries. So I just newfs -U -L and keep journaling off and wouldn't have realized there is at least some mitigation that will make it into 9.1-R. I still stand by my feeling that it should not be on by default though, because it breaks snapshots and by extension dump -L which I consider to be a pretty awesome feature of FreeBSD. If you have partitions with enabled it means booting up in single user to undo it which is a hassle for a server if it's in production (I realize that's a bit whiny :P). -- Adam Strohl http://www.ateamsystems.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
Re: WITH_LIBCPLUSPLUS buildworld broken on STABLE-9
Quoting Dimitry Andric d...@freebsd.org: On 2012-11-02 19:22, Oleg V. Nauman wrote: ... /usr/src/lib/libc++/../../contrib/libc++/include/cstdlib:134:9: error: no member named 'at_quick_exit' in the global namespace using ::at_quick_exit; ~~^ This was fixed in head by r242472, I will merge it as soon as the MFC timer expires (Nov 5). Sorry about the breakage, this was my fault. No problem. Thanks for your hard work. In the meantime, you can use the attached diff. That patch fixes the issue, thank you. ___ 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-update and sources of 9.1-RC3
Bas Smeelen b.smeelen at ose.nl writes: ... Can't this be accomplished by setting StrictComponents yes in /etc/freebsd-update.conf ? Then feebsd-update does not try to figure out the components to update by itself, but updates the components mentioned in Components src world kernel I didn't try what happens if no source is installed. Good shot, that could be the override option ... I did the test and it did not work out for me. # cat /etc/freebsd-update.conf ... Components src world kernel ... StrictComponents yes ... # # freebsd-update rollback # shutdown -r now # rm -rf /usr/src/ # freebsd-update upgrade -r 9.1-RC3 Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RC2 from update4.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Fetching metadata signature for 9.1-RC3 from update4.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Preparing to download files... done. The following files will be added as part of updating to 9.1-RC3-p0: /usr/src/release/doc/de_DE.ISO8859-1/early-adopter/article.xml ... The following files will be updated as part of updating to 9.1-RC3-p0: /boot/kernel/hpt27xx.ko /boot/kernel/kernel ... To install the downloaded upgrades, run /usr/sbin/freebsd-update install. # # freebsd-update install Installing updates... Kernel updates have been installed. Please reboot and run /usr/sbin/freebsd-update install again to finish installing updates. # # shutdown -r now # freebsd-update install Installing updates...install: ///usr/src/release/doc/de_DE.ISO8859-1/early-adopt er/article.xml: No such file or directory ... # # ls -al /usr/src/ total 12 drwxr-xr-x 3 root wheel 512 Nov 4 10:17 . drwxr-xr-x 16 root wheel 512 Nov 4 10:17 .. drwxr-xr-x 3 root wheel 512 Nov 4 10:17 release # ls -al /usr/src/release/doc/ total 36 drwxr-xr-x 9 root wheel 512 Nov 4 10:17 . drwxr-xr-x 3 root wheel 512 Nov 4 10:17 .. drwxr-xr-x 3 root wheel 512 Nov 4 10:17 de_DE.ISO8859-1 drwxr-xr-x 3 root wheel 512 Nov 4 10:17 en_US.ISO8859-1 drwxr-xr-x 3 root wheel 512 Nov 4 10:17 fr_FR.ISO8859-1 drwxr-xr-x 3 root wheel 512 Nov 4 10:17 ja_JP.eucJP drwxr-xr-x 3 root wheel 512 Nov 4 10:17 ru_RU.KOI8-R drwxr-xr-x 3 root wheel 512 Nov 4 10:17 share drwxr-xr-x 3 root wheel 512 Nov 4 10:17 zh_CN.GB2312 # ls -al /usr/src/release/doc/de_DE.ISO8859-1/ total 12 drwxr-xr-x 3 root wheel 512 Nov 4 10:17 . drwxr-xr-x 9 root wheel 512 Nov 4 10:17 .. drwxr-xr-x 3 root wheel 512 Nov 4 10:17 share # # shutdown -r now # uname -a FreeBSD localhost.localdomain 9.1-RC3 FreeBSD 9.1-RC3 #0 r242324: Tue Oct 30 00: 18:27 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i38 6 No luck. Should we file a PR# (there are some error msgs anyway) ? jb ___ 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: Why is SU+J undesirable on SSDs?
On 11/4/2012 5:32, Karl Denninger wrote: It is utter insanity to enable, by default, filesystem options that break _*the canonical backup solution*_ in the handbook (dump, when used with -L, which it must be to dump a live filesystem SAFELY.) Exactly. -- Adam Strohl http://www.ateamsystems.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
Re: freebsd-update and sources of 9.1-RC3
On 11/04/2012 11:25 AM, jb wrote: Bas Smeelen b.smeelen at ose.nl writes: ... Can't this be accomplished by setting StrictComponents yes in /etc/freebsd-update.conf ? Then feebsd-update does not try to figure out the components to update by itself, but updates the components mentioned in Components src world kernel I didn't try what happens if no source is installed. Good shot, that could be the override option ... I did the test and it did not work out for me. OK, well this could have been expected because freebsd-update is meant to update the components on a system and not to install new components. On the update servers there are delta binaries present but not full binaries (or archives) to add new components. See further below. # cat /etc/freebsd-update.conf ... Components src world kernel ... StrictComponents yes ... # snip # uname -a FreeBSD localhost.localdomain 9.1-RC3 FreeBSD 9.1-RC3 #0 r242324: Tue Oct 30 00: 18:27 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i38 6 No luck. Should we file a PR# (there are some error msgs anyway) ? jb To file a PR it will require some work to find out exactly what the PR should be about. Since freebsd-update is meant to update the system I don't really see a point to make it install sources (or others things) if they are not present on the system being updated. To get the sources you can always use csup and set default release=cvs tag=RELENG_9_1 or use subversion This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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
Failed to attach P_CNT - FreeBSD 9.1 RC3
Dear FreeBSD Community Friends, It is FreeBSD 9.1 RC3, i get the following warning in the message log file. i need assistance to understand the meaning of this error, how serious is it? acpi_throttle23: failed to attach P_CNT History: This error is following FreeBSD for long time because when i was googled the error. i can across a post that was belongs to FreeBSD 6x. http://tgrove.com/2007/10/07/freebsd-6-acpi_throttle1-failed-to-attach-p_cnt/ They Provided the solution as well but did not work. They also said that is is only happening with Intel dual core processor but that is not true. As it is virtual machine, i tried to restore the FreeBSD VM on three different servers, those having different specification of processors (dual cores, quad cores, six cores) still the same then decided to consult with experts. Following was the solution but did not remove the error/warning vi /boot/device.hints # Add this to the end of the file hint.acpi_throttle.0.disabled=1 vi /boot/loader.conf # Add this to the end of the file hint.acpi_throttle.0.disabled=1#8243; Thanks / Shiv. Nath ___ 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-update and sources of 9.1-RC3
Bas Smeelen b.smeelen at ose.nl writes: ... To file a PR it will require some work to find out exactly what the PR should be about. Since freebsd-update is meant to update the system I don't really see a point to make it install sources (or others things) if they are not present on the system being updated. ... Well, that proves my earlier point. But, you brought up that StrictComponents yes option and we have to figure out what it means ... # When upgrading between releases, should the list of Components be # read strictly (StrictComponents yes) or merely as a list of components # which *might* be installed of which FreeBSD Update should figure out # which actually are installed and upgrade those (StrictComponents no)? # StrictComponents no The components are: Components src world kernel Then what gives ? Does it not apply to src component ? jb ___ 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-update and sources of 9.1-RC3
On 11/04/2012 12:08 PM, jb wrote: Bas Smeelen b.smeelen at ose.nl writes: ... To file a PR it will require some work to find out exactly what the PR should be about. Since freebsd-update is meant to update the system I don't really see a point to make it install sources (or others things) if they are not present on the system being updated. ... Well, that proves my earlier point. You are right. But, you brought up that StrictComponents yes option and we have to figure out what it means ... From looking at the freebsd-update script (it's in /usr/sbin) I understand when StrictComponents is set to yes it skips the step, inspecting system and uses the list provided in freebsd-update.conf, so this option might save some time and disk activity. I don't fully understand what the impact might be when running a custom kernel. # When upgrading between releases, should the list of Components be # read strictly (StrictComponents yes) or merely as a list of components # which *might* be installed of which FreeBSD Update should figure out # which actually are installed and upgrade those (StrictComponents no)? # StrictComponents no The components are: Components src world kernel Then what gives ? Does it not apply to src component ? jb This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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: SU+J on 9.1-RC2 ISO
Hi all.
The point is:
There is completely no way to take a snapshot of SU+J partition
unless modify one's kernel.
Whether some issue still exist or not,
how about enabling snapshoting SU+J partition
through sysctl variable?
Would you mind to see patch attached?
1. Taking a snapshot of SU+J partition is controlled through sysctl variable.
2. Default to disable.
One who want to enable it should set the variable manually.
3. The default value in bsdinstall(8) may be left as is.
--
HATANO Tomomi.--- src/sys/ufs/ffs/ffs_snapshot.c.orig 2012-11-04 11:01:58.0 +0900
+++ src/sys/ufs/ffs/ffs_snapshot.c 2012-11-04 11:13:32.0 +0900
@@ -182,8 +182,10 @@
*/
int dopersistence = 0;
-#ifdef DEBUG
#include sys/sysctl.h
+int snapsuj = 0;
+SYSCTL_INT(_debug, OID_AUTO, snapsuj, CTLFLAG_RW, snapsuj, 0, );
+#ifdef DEBUG
SYSCTL_INT(_debug, OID_AUTO, dopersistence, CTLFLAG_RW, dopersistence, 0, );
static int snapdebug = 0;
SYSCTL_INT(_debug, OID_AUTO, snapdebug, CTLFLAG_RW, snapdebug, 0, );
@@ -230,7 +232,7 @@
* At the moment, journaled soft updates cannot support
* taking snapshots.
*/
- if (MOUNTEDSUJ(mp)) {
+ if (MOUNTEDSUJ(mp) (snapsuj == 0)) {
vfs_mount_error(mp, %s: Snapshots are not yet supported when
running with journaled soft updates, fs-fs_fsmnt);
return (EOPNOTSUPP);
___
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: SU+J on 9.1-RC2 ISO
On 11/04/2012 01:13 PM, HATANO Tomomi wrote: Hi all. The point is: There is completely no way to take a snapshot of SU+J partition unless modify one's kernel. Whether some issue still exist or not, how about enabling snapshoting SU+J partition through sysctl variable? Would you mind to see patch attached? 1. Taking a snapshot of SU+J partition is controlled through sysctl variable. 2. Default to disable. One who want to enable it should set the variable manually. 3. The default value in bsdinstall(8) may be left as is. Hi If I understand correctly this still leaves your default installed system with SU+J and if you set the sysctl variable it means okay I am prepared for trouble when taking a snapshot of a SU+J filesystem? Why would I want a sysctl variable that gives me known trouble? Or have I misread your patch? When taking a snapshot of a SU+J filesystem we already get the nice not supported error instead of getting into trouble. I think SU+J should not be default unless it works fine with the rest of the system as described in the handbook. This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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: SU+J on 9.1-RC2 ISO
Hi Bas, thank you for your response. When taking a snapshot of a SU+J filesystem we already get the nice not supported error instead of getting into trouble. It's not nice. Hiding problem will never solve problem. Currently we have no choice. If we have a way to choose (e.g. through sysctl), one who want to use can test it. -- HATANO Tomomi ___ 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: Why is SU+J undesirable on SSDs?
Imho, at least wiki page (http://wiki.freebsd.org/) on setting up FreeBSD on SSDs is needed. Lots of confusion and different opinions (sector size!)... -- View this message in context: http://freebsd.1045724.n5.nabble.com/Why-is-SU-J-undesirable-on-SSDs-tp5757733p5757907.html Sent from the freebsd-stable mailing list archive at Nabble.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
Re: SU+J on 9.1-RC2 ISO
On 11/03/12 15:09, Jeremy Chadwick wrote: (Please keep me CC'd, as I'm not subscribed to -stable) I've CC'd Nathan Whitehorn, who according to bsdinstall(8) is the author (not sure if maintainer) of the code. This default has already begun to bite users/SAs in the ass: http://lists.freebsd.org/pipermail/freebsd-questions/2012-November/246069.html SU+J (the journalling part specifically) needs to be disabled by default in the installer. This default was a very bad choice and should not have been done. It either indicates someone was out of touch with the rest of the issues surrounding the feature, or that someone intentionally decided it's the best way to get people using it for testing (I have seen this justification presented in the past, and it is the wrong approach). However, since some people DO want it (and those folks don't use dump), the installer should be modified to make SU+J support toggleable via a a checkbox. The default, obviously, should be unchecked. If the user checks the checkbox, an ominous warning message should be displayed informing the user of the repercussions. The only option at that point should be OK, after which the checkbox is checked. Do not tell me send patches. This issue/problem has gone on long enough, and the community bitched hard/long enough, that the person who committed this default should be responsible for fixing it. We should operate under the assumption that this bug/problem will never be fixed. It probably will be, but again, we must operate with the assumption that Kirk et al will require years to fix it. (It has already been something like 9 months. Or is it a year?) [...] I will give this comment a BIG, BIG, +1! -- George ___ 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: SU+J on 9.1-RC2 ISO
On 11/04/2012 03:43 PM, George Mitchell wrote: On 11/03/12 15:09, Jeremy Chadwick wrote: (Please keep me CC'd, as I'm not subscribed to -stable) I've CC'd Nathan Whitehorn, who according to bsdinstall(8) is the author (not sure if maintainer) of the code. This default has already begun to bite users/SAs in the ass: http://lists.freebsd.org/pipermail/freebsd-questions/2012-November/246069.html SU+J (the journalling part specifically) needs to be disabled by default in the installer. This default was a very bad choice and should not have been done. It either indicates someone was out of touch with the rest of the issues surrounding the feature, or that someone intentionally decided it's the best way to get people using it for testing (I have seen this justification presented in the past, and it is the wrong approach). However, since some people DO want it (and those folks don't use dump), the installer should be modified to make SU+J support toggleable via a a checkbox. The default, obviously, should be unchecked. If the user checks the checkbox, an ominous warning message should be displayed informing the user of the repercussions. The only option at that point should be OK, after which the checkbox is checked. Do not tell me send patches. This issue/problem has gone on long enough, and the community bitched hard/long enough, that the person who committed this default should be responsible for fixing it. We should operate under the assumption that this bug/problem will never be fixed. It probably will be, but again, we must operate with the assumption that Kirk et al will require years to fix it. (It has already been something like 9 months. Or is it a year?) [...] I will give this comment a BIG, BIG, +1! -- George A small patch already sent via pr http://www.freebsd.org/cgi/query-pr.cgi?pr=173301 Let's see what goes This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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: SU+J on 9.1-RC2 ISO
Just rebooting to single user mode after the install and then tunefs -j disable /dev/ada0p2 works for me. After a reboot then I just removed /.sujournal That crystillized to me as a correct way in this situation. Just one fsck at the very beginning? Manual says about some options available after it only. People mostly mention journaling for servers. Anybody using 9.x on laptop with ssd? Thanks all for help, regarding this option. Zoran ___ 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: SU+J on 9.1-RC2 ISO
On 11/04/2012 04:33 PM, Zoran Kolic wrote: Just rebooting to single user mode after the install and then tunefs -j disable /dev/ada0p2 works for me. After a reboot then I just removed /.sujournal That crystillized to me as a correct way in this situation. Just one fsck at the very beginning? Manual says about some options available after it only. I did not fsck just disable journaling for soft updates reboot and delete ./sujournal People mostly mention journaling for servers. Anybody using 9.x on laptop with ssd? Thanks all for help, regarding this option. I don't have a laptop with ssd Journaling SU is not recommended because of the extra writes but nowadays ssd should be fine with it, though less writes is less wear. Just take care to align your partitions to 1 or 2 MB which can be accomplished by going to shell on the partedit part of bsdinstall and use gpart -a or gpart -b This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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 stability/robustness?
Am Sat, 3 Nov 2012 21:56:45 -0400 schrieb Rick Miller vmil...@hostileadmin.com: On Fri, Nov 2, 2012 at 4:10 AM, Rainer Duffner rai...@ultra-secure.de wrote: Am Thu, 1 Nov 2012 20:14:51 -0600 (MDT) schrieb Brett Glass br...@lariat.net: I need to build up a few servers and routers, and am wondering how FreeBSD 9.1 is shaping up. Will it be likely to be more stable and robust than 9.0-RELEASE? Are there issues that will have to wait until 9.2-RELEASE to be fixed? Opinions welcome. If I'm not mistaken, the bge-stuff that makes the default NICs ins HP G8 servers (360+380) actually run will not make it back into 9.1. Intel cards work much better anyway... I have a blog post at http://blog.hostileadmin.com/2012/06/14/freebsd-on-hp-proliant-dl360p-g8-servers/ which touches on this. It comes up invariably once you google for FreeBSD DL 380 G8... I heard as recently as today that the fixes for the BCM5719 and 5720 were recently committed to -CURRENT. It's too late for them to be rolled into 9.1. Not sure if they'll be committed to to stable/8 or not, but if so they could make it into 8.4-R. Oh - will were be an 8.4 release? That would be interesting. ___ 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 stability/robustness?
At 10:28 AM 11/4/2012, Rainer Duffner wrote: Oh - will were be an 8.4 release? That would be interesting. I'd like to see a trend toward more point versions of FreeBSD. Particularly in 9.x, because it incorporates most of the items that have been on people's wish lists. 4.11 was one of the most robust and stable releases ever, and I used it for many years. --Brett Glass ___ 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 stability/robustness?
Hi! Oh - will were be an 8.4 release? That would be interesting. I'd like to see a trend toward more point versions of FreeBSD. Particularly in 9.x, because it incorporates most of the items that have been on people's wish lists. 4.11 was one of the most robust and stable releases ever, and I used it for many years. I still use 4.11 on two servers 8-} -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ 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
mod_fcgid doesn't work in 9-stable jails after upgrade from 8.x
Hi, I've just tried to upgrade a machine running an older 8-stable to 9-stable@r242549M without success. It runs an apache with mod_fcgid in a jail and the latter can't start with the error message of: [Sun Nov 04 16:09:12 2012] [emerg] (78)Function not implemented: mod_fcgid: Can't create shared memory for size 1192488 bytes security.jail.sysvipc_allowed is enabled (it was needed on 8.x too), nothing else has changed. There are some reports from this, but from earlier versions, and the only confirmed solution was sysvipc_allowed, which works for 8.x, but doesn't with the above version. Any ideas? ___ 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-RC3 not booting
Hi, after upgrading Kernel from 9.1-RC2 # freebsd-update upgrade -r 9.1-RC3 # freebsd-update install # shutdown -r now the Kernel ist not booting. It just reboot's after the boot loader. There no kernel.old. Safe mode also reboots. What can I do to recover the machine? (It was booting/running fine with 9.1-RC2) Thanks for any help! Regards, Thomas. ___ 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
[releng_9_1 tinderbox] failure on mips/mips
TB --- 2012-11-04 19:42:16 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 19:42:16 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 19:42:16 - starting RELENG_9_1 tinderbox run for mips/mips TB --- 2012-11-04 19:42:16 - cleaning the object tree TB --- 2012-11-04 19:42:16 - checking out /src from svn://svn.freebsd.org/base/releng/9.1 TB --- 2012-11-04 19:42:16 - cd /tinderbox/RELENG_9_1/mips/mips TB --- 2012-11-04 19:42:16 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 19:43:08 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:43:08 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:43:08 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 19:43:38 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:43:38 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:43:38 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 19:44:38 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:44:38 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:44:38 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 19:46:08 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:46:08 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:46:08 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 19:48:08 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:48:09 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:48:09 - ERROR: unable to check out the source tree TB --- 2012-11-04 19:48:09 - 3.87 user 4.41 system 352.80 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-mips-mips.full ___ 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
[releng_9_1 tinderbox] failure on powerpc/powerpc
TB --- 2012-11-04 19:48:09 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 19:48:09 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 19:48:09 - starting RELENG_9_1 tinderbox run for powerpc/powerpc TB --- 2012-11-04 19:48:09 - cleaning the object tree TB --- 2012-11-04 19:48:09 - checking out /src from svn://svn.freebsd.org/base/releng/9.1 TB --- 2012-11-04 19:48:09 - cd /tinderbox/RELENG_9_1/powerpc/powerpc TB --- 2012-11-04 19:48:09 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 19:48:33 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:48:33 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:48:33 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 19:49:03 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:49:03 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:49:03 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 19:50:03 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:50:03 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:50:03 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 19:51:33 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:51:33 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:51:33 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 19:53:33 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:53:33 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:53:33 - ERROR: unable to check out the source tree TB --- 2012-11-04 19:53:33 - 3.93 user 4.62 system 324.50 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-powerpc-powerpc.full ___ 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
[releng_9_1 tinderbox] failure on powerpc64/powerpc
TB --- 2012-11-04 19:53:34 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 19:53:34 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 19:53:34 - starting RELENG_9_1 tinderbox run for powerpc64/powerpc TB --- 2012-11-04 19:53:34 - cleaning the object tree TB --- 2012-11-04 19:53:34 - checking out /src from svn://svn.freebsd.org/base/releng/9.1 TB --- 2012-11-04 19:53:34 - cd /tinderbox/RELENG_9_1/powerpc64/powerpc TB --- 2012-11-04 19:53:34 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 19:54:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:54:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:54:02 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 19:54:32 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:54:32 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:54:32 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 19:55:32 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:55:32 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:55:32 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 19:57:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:57:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:57:02 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 19:59:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:59:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:59:02 - ERROR: unable to check out the source tree TB --- 2012-11-04 19:59:02 - 3.92 user 4.38 system 328.82 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-powerpc64-powerpc.full ___ 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
[releng_9_1 tinderbox] failure on sparc64/sparc64
TB --- 2012-11-04 19:59:03 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 19:59:03 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 19:59:03 - starting RELENG_9_1 tinderbox run for sparc64/sparc64 TB --- 2012-11-04 19:59:03 - cleaning the object tree TB --- 2012-11-04 19:59:03 - checking out /src from svn://svn.freebsd.org/base/releng/9.1 TB --- 2012-11-04 19:59:03 - cd /tinderbox/RELENG_9_1/sparc64/sparc64 TB --- 2012-11-04 19:59:03 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 19:59:48 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:59:48 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:59:48 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 20:00:18 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:00:18 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:00:18 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 20:01:18 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:01:18 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:01:18 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 20:02:48 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:02:48 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:02:48 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 20:04:48 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:04:48 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:04:48 - ERROR: unable to check out the source tree TB --- 2012-11-04 20:04:48 - 3.54 user 4.41 system 345.77 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-sparc64-sparc64.full ___ 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: [releng_9_1 tinderbox] failure on powerpc64/powerpc
On 11/04/12 14:59, FreeBSD Tinderbox wrote: TB --- 2012-11-04 19:53:34 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 19:53:34 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 19:53:34 - starting RELENG_9_1 tinderbox run for powerpc64/powerpc TB --- 2012-11-04 19:53:34 - cleaning the object tree TB --- 2012-11-04 19:53:34 - checking out /src from svn://svn.freebsd.org/base/releng/9.1 TB --- 2012-11-04 19:53:34 - cd /tinderbox/RELENG_9_1/powerpc64/powerpc TB --- 2012-11-04 19:53:34 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 19:54:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:54:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:54:02 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 19:54:32 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:54:32 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:54:32 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 19:55:32 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:55:32 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:55:32 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 19:57:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:57:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:57:02 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 19:59:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:59:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:59:02 - ERROR: unable to check out the source tree TB --- 2012-11-04 19:59:02 - 3.92 user 4.38 system 328.82 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-powerpc64-powerpc.full ___ 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 Gosh, I'm SO looking forward to depending on svn instead of csup for software updates.-- George ___ 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
[releng_9 tinderbox] failure on amd64/amd64
TB --- 2012-11-04 20:04:49 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 20:04:49 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 20:04:49 - starting RELENG_9 tinderbox run for amd64/amd64 TB --- 2012-11-04 20:04:49 - cleaning the object tree TB --- 2012-11-04 20:04:49 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-11-04 20:04:49 - cd /tinderbox/RELENG_9/amd64/amd64 TB --- 2012-11-04 20:04:49 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 20:05:26 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:05:26 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:05:26 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 20:05:56 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:05:56 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:05:56 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 20:06:56 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:06:56 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:06:56 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 20:08:26 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:08:26 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:08:26 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 20:10:26 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:10:26 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:10:26 - ERROR: unable to check out the source tree TB --- 2012-11-04 20:10:26 - 3.83 user 4.66 system 337.72 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-amd64-amd64.full ___ 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
[releng_9 tinderbox] failure on arm/arm
TB --- 2012-11-04 20:10:27 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 20:10:27 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 20:10:27 - starting RELENG_9 tinderbox run for arm/arm TB --- 2012-11-04 20:10:27 - cleaning the object tree TB --- 2012-11-04 20:10:27 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-11-04 20:10:27 - cd /tinderbox/RELENG_9/arm/arm TB --- 2012-11-04 20:10:27 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 20:10:58 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:10:58 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:10:58 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 20:11:28 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:11:28 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:11:28 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 20:12:28 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:12:28 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:12:28 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 20:13:58 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:13:58 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:13:58 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 20:15:58 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:15:58 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:15:58 - ERROR: unable to check out the source tree TB --- 2012-11-04 20:15:58 - 3.73 user 4.64 system 331.82 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-arm-arm.full ___ 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
[releng_9 tinderbox] failure on i386/i386
TB --- 2012-11-04 20:15:59 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 20:15:59 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 20:15:59 - starting RELENG_9 tinderbox run for i386/i386 TB --- 2012-11-04 20:15:59 - cleaning the object tree TB --- 2012-11-04 20:15:59 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-11-04 20:15:59 - cd /tinderbox/RELENG_9/i386/i386 TB --- 2012-11-04 20:15:59 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 20:16:41 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:16:41 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:16:41 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 20:17:11 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:17:11 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:17:11 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 20:18:11 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:18:11 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:18:11 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 20:19:41 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:19:41 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:19:41 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 20:21:41 - /usr/local/bin/svn update /src TB --- 2012-11-04 20:21:41 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 20:21:41 - ERROR: unable to check out the source tree TB --- 2012-11-04 20:21:41 - 3.76 user 4.77 system 342.83 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-i386-i386.full ___ 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: [releng_9_1 tinderbox] failure on powerpc64/powerpc
On 4 Nov 2012 20:12, George Mitchell george+free...@m5p.com wrote: On 11/04/12 14:59, FreeBSD Tinderbox wrote: TB --- 2012-11-04 19:53:34 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 19:53:34 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-04 19:53:34 - starting RELENG_9_1 tinderbox run for powerpc64/powerpc TB --- 2012-11-04 19:53:34 - cleaning the object tree TB --- 2012-11-04 19:53:34 - checking out /src from svn:// svn.freebsd.org/base/releng/9.1 TB --- 2012-11-04 19:53:34 - cd /tinderbox/RELENG_9_1/powerpc64/powerpc TB --- 2012-11-04 19:53:34 - /usr/local/bin/svn cleanup /src TB --- 2012-11-04 19:54:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:54:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:54:02 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-04 19:54:32 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:54:32 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:54:32 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-04 19:55:32 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:55:32 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:55:32 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-04 19:57:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:57:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:57:02 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-04 19:59:02 - /usr/local/bin/svn update /src TB --- 2012-11-04 19:59:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-04 19:59:02 - ERROR: unable to check out the source tree TB --- 2012-11-04 19:59:02 - 3.92 user 4.38 system 328.82 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-powerpc64-powerpc.full ___ 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 Gosh, I'm SO looking forward to depending on svn instead of csup for software updates. The subversion server is being moved; a one off thing. No major drama here. Chris ___ 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: [releng_9_1 tinderbox] failure on powerpc64/powerpc
Hello, George. You wrote 5 ноября 2012 г., 0:07:00: GM Gosh, I'm SO looking forward to depending on svn instead of csup for GM software updates.-- George It is planned server outage (migration). -- // Black Lion AKA Lev Serebryakov l...@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 stability/robustness?
On Sun, Nov 4, 2012 at 12:28 PM, Rainer Duffner rai...@ultra-secure.de wrote: Oh - will were be an 8.4 release? That would be interesting. History shows that every release, since 4.x has gone to at least .4. I'd be willing to bet we will see an 8.4. The branch is still being developed. http://en.wikipedia.org/wiki/FreeBSD#Timeline -- Take care Rick Miller ___ 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
