Re: libarchive, lzma, and xz interaction
On Fri, Jul 1, 2011 at 7:19 PM, Kevin Oberman kob6...@gmail.com wrote: I'm trying to understand the problems I am having on some systems regarding libarchive, lzma, and xz. I have an 8-Stable system updated yesterday. As far as I can tell, libarchive does include the lzma stuff from libzma. At least I see the references. But several ports seem to still pull in xz-5.0.1 and link to it. This has a wonderful potential to cause library symbol conflicts. I get: /usr/lib/libarchive.so: undefined reference to `lzma_stream_encoder@XZ_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_alone_decoder@XZ_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_memusage@XZ_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_stream_decoder@XZ_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_code@XZ_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_end@XZ_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_lzma_preset@XZ_5.0' /usr/lib/libarchive.so: undefined reference to `lzma_alone_encoder@XZ_5.0' ldd shows libarchive linked against liblzma.so.5 and an objdump of the dynamic symbols from liblzma.so.5 shows the undefined symbols defined with the XZ_5.0 version, so I am mystified. It looks o me like it is there. Is confusion with xz-5.0.1 causing this? Should get rid of it? Even so, I don't understand why the loader is claiming that these symbols are undefined when they seem to be defined as far as I can tell. 7c60 g DF .text 0084 XZ_5.0 lzma_stream_encoder Any clues to what i happening would be greatly appreciated! Replying to myself, I re-built all programs that depended on xz and then deleted the port. Now everything works fine. I still don't completely understand what I was seeing, but it is working, now. -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
dell latitude 13
Dear folks! I see threads on the laptop subject, some forums also, but no clue for cheap lapper with freebsd compatibility. There is a chance to get mentioned box for about 450 euros, without OS and with specs like this: Intel Core#2 Duo SU7300 1.3GHz, 3MB L2 cache, FSB 800MHz Intel GS45 Express + Intel ICH9M-Enhanced (chipset) Intel GMA 4500 MHD (graphics) 13.3 1366x768 HD WLED Anti-Glare (screen) Intel Link 5100 IEEE 802.11a/b/g/n WiFi (wifi) ExpressCard 6-cell Li-lon battery FreeDos (OS) I'm aware of something called optimus to optimize graphics and inability to know prior getting laptop home. Someone already has this laptop? To me it looks like it should work out of the box. I tend to like box to be cold and silent. If you have idea or better laptop in the price range, I'd be eager to know. Best regards all 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: Crashes with Promise controller
Tom Evans tevans...@googlemail.com wrote: On Thu, Jun 30, 2011 at 6:31 PM, Christian Baer christian.b...@uni-dortmund.de wrote: A serial console is easy enough to set up on a Sun for example, but in this case, I am running a simple AthlonXP, which has nothing for that sort of help. I would need a special card for that and those cose quite a bit. :-( Not that special - you just need a serial port on two computers. If your computers don't have serial ports, USB serial adapters work fine, While it should work up to a point, a USB serial port is not the ideal choice for a console port (on the machine that is crashing), because it requires the USB stack to be working. If that machine has no built-in serial port, but has an available PCI slot, adding a PCI serial port is likely the best choice. and are cheap, as are (single port) PCI serial cards. Alternatively, if both computers have firewire ports, you can use dcons, and all you need is a cable. ___ 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
devel/subversion: svn: Couldn't perform atomic initialization
Hello. Since two days now I realize on several recently ports-updated servers a failure of the subversion server running on those servers. Sneaking around the internet I found several issues exactly targeting this error with an sqlite 3.7.7/3.7.7.1 issue, which has been fixed in sqlite-3.7.7.2. At this very moment, our subversion servers in question has all recently been updated and it seems, they all fail the same way. Does anyone also realize this behaviour shown below when commiting? Is there a workaround? Any help or hint is appreciated. Thanks in advance, Oliver Transmitting file data .svn: Commit failed (details follow): svn: Couldn't perform atomic initialization svn: database schema has changed svn: Your commit message was left in a temporary file: ___ 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: dell latitude 13
While NVIDIA provides a FreeBSD driver for their stand-alone video, Optimus is not supported and NVIDIA has stated that they have no plans to support it for Linux or BSD. If you Google FreeBSD NVIDIA optimus, you will find that not only is it useless other than for Windows, but that it interferes with the main graphics system, usually Intel 3000 which is actually a part of the Sandy Bridge CPU. Since the Intel chip is also still unsupported by FreeBSD, you will be limited to VEDA support which is very limited. R. Kevin Oberman, Network Engineer Retired kob6...@gmail.com On Jul 1, 2011 8:04 PM, Zoran Kolic zko...@sbb.rs wrote: Dear folks! I see threads on the laptop subject, some forums also, but no clue for cheap lapper with freebsd compatibility. There is a chance to get mentioned box for about 450 euros, without OS and with specs like this: Intel Core#2 Duo SU7300 1.3GHz, 3MB L2 cache, FSB 800MHz Intel GS45 Express + Intel ICH9M-Enhanced (chipset) Intel GMA 4500 MHD (graphics) 13.3 1366x768 HD WLED Anti-Glare (screen) Intel Link 5100 IEEE 802.11a/b/g/n WiFi (wifi) ExpressCard 6-cell Li-lon battery FreeDos (OS) I'm aware of something called optimus to optimize graphics and inability to know prior getting laptop home. Someone already has this laptop? To me it looks like it should work out of the box. I tend to like box to be cold and silent. If you have idea or better laptop in the price range, I'd be eager to know. Best regards all 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 ___ 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: dell latitude 13
On Sat, Jul 2, 2011 at 1:24 AM, Zoran Kolic zko...@sbb.rs wrote: Dear folks! I see threads on the laptop subject, some forums also, but no clue for cheap lapper with freebsd compatibility. There is a chance to get mentioned box for about 450 euros, without OS and with specs like this: Intel Core#2 Duo SU7300 1.3GHz, 3MB L2 cache, FSB 800MHz Intel GS45 Express + Intel ICH9M-Enhanced (chipset) Intel GMA 4500 MHD (graphics) 13.3 1366x768 HD WLED Anti-Glare (screen) Intel Link 5100 IEEE 802.11a/b/g/n WiFi (wifi) ExpressCard 6-cell Li-lon battery FreeDos (OS) I'm aware of something called optimus to optimize graphics and inability to know prior getting laptop home. Someone already has this laptop? To me it looks like it should work out of the box. I tend to like box to be cold and silent. If you have idea or better laptop in the price range, I'd be eager to know. Best regards all Zoran For laptops you may check the following site : http://laptop.bsdgroup.de/freebsd/ Also check FreeBSD Hardware lists such as ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/8.2-RELEASE/HARDWARE.HTM ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/HARDWARE.HTM for hardware compatibility issues , for example , search Intel GMA 4500 MHD (graphics) , and other chips . It is NOT possible to know in advance without any prior knowledge whether a computer is working with FreeDOS will work with FreeBSD because these are very different systems . Therefore my idea is to avoid FreeDOS loaded computers if it is to be used for FreeBSD or Linux . The producer/seller can install FreeBSD or Linux without cost ( if the computer is NOT a DOS computer , i.e. , FreeBSD ( Unix ) , Linux can work on it ) . Over the years , always my suggestion to my friends is to select at least a computer having Linux installed . If there is Linux on it and it is working it is very likely that it will work with FreeBSD . If you can find a laptop as FreeBSD is installed , it is much better than any other ones . Another way is to test the computer for FreeBSD is to start it with a FreeBSD LiveCD ( This will not show the FreeBSD can be installed and run successfully . Over time , some programs may crash due to missing circuit parts because such parts are NOT included into the circuits because they are NOT necessary for DOS or its children . With a few run , this point can not be understood without applying test programs ( which I do NOT know any such program name ) . Such a feature may turn your computer unusable for you with FreeBSD or Linux over time when it occurs under a required program . ) . As a summary , to such Live CD checks , do NOT rely on much , actually ignore such pseudo-tests . For other BSD related GUI Live CD distributions , you may check the following site : http://www.livebsd.org/ Thank you very much . Mehmet Erol Sanliturk ___ 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: libarchive, lzma, and xz interaction
On Fri, Jul 1, 2011 at 7:19 PM, Kevin Oberman kob6558 at gmail.com wrote:
I'm trying to understand the problems I am having on some systems
regarding libarchive, lzma, and xz.
I have an 8-Stable system updated yesterday. As far as I can tell,
libarchive does include the lzma stuff
from libzma. At least I see the references. But several ports seem to
still pull in xz-5.0.1 and link to it.
This has a wonderful potential to cause library symbol conflicts. I get:
/usr/lib/libarchive.so: undefined reference to `lzma_stream_encoder at
XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_alone_decoder at
XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_memusage at XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_stream_decoder at
XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_code at XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_end at XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_lzma_preset at XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_alone_encoder at
XZ_5.0'
ldd shows libarchive linked against liblzma.so.5 and an objdump of the
dynamic symbols from liblzma.so.5
shows the undefined symbols defined with the XZ_5.0 version, so I am
mystified. It looks o me like it is
there. Is confusion with xz-5.0.1 causing this? Should get rid of it?
Even so, I don't understand why the
loader is claiming that these symbols are undefined when they seem to
be defined as far as I can tell.
7c60 g   DF .text  0084  XZ_5.0
lzma_stream_encoder
Any clues to what i happening would be greatly appreciated!
Nothing mysterious here:
src/lib/libarchive/archive_write_set_compression_xz.c uses some code
from the base system /usr/lib/liblzma.so shared library, from
src/lib/liblzma, which is derived from the base system xz 5.0.1, in
src/contrib/xz. Hence the symbols are present, with the symbol
versions that you noted, but undefined in libarchive, because it is
obtaining them from liblzma at run-time. It nudges rtld(1) to do this
in the usual way, via it's DT_NEEDED tag for that library:
objdump -x /usr/lib/libarchive.so | egrep 'NEEDED.*lzma'
Replying to myself, I re-built all programs that depended on xz and
then deleted the port. Now everything works fine. I still don't
completely understand what I was seeing, but it is working, now.
Perhaps you recently updated your base system, but were using old
ports or packages? With up-to-date ports and a recent version of
8-stable you should not have been able to build the archivers/xz port,
even if other ports mistakenly tried to drag it in, because of the
following lines in the ports/archivers/xz Makefile:
.if ${OSVERSION} = 900012 || (${OSVERSION} 90 ${OSVERSION} = 800505)
IGNORE= is already in the base system
.endif
Of course, you could have overridden this, by setting NO_IGNORE.
b.
___
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: dell latitude 13
Thanks for answering my question. Since the Intel chip is also still unsupported by FreeBSD, you will be limited to VEDA support which is very limited. I found that dell sells ubuntu on mentioned laptop in some parts of the globe. Further, my old laptop (HP nx9020) has intel chip and works under intel driver. I need simple 2d, no frills. Does newer chip run for plain graphics at all? No acceleration? Fine. I don't use it neither on my NVIDIA GeForce 6200 card with nv driver. For laptops you may check the following site : http://laptop.bsdgroup.de/freebsd/ Old and no newer machines on the site. Also check FreeBSD Hardware lists such as ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/8.2-RELEASE/HARDWARE.HTM Intel 5100 wifi should work with device iwn5000fw or 5150? It is NOT possible to know in advance without any prior knowledge whether a computer is working with FreeDOS will work with FreeBSD because these are very different systems . It is sold with freedos to be cheap enough. I appreciate that. The producer/seller can install FreeBSD or Linux without cost Not where I live. When I bought my previous laptop, live cd was the guide if it worked at all. It is a matter of buy it as it is now. More, no cd on latitude 13, which is fine, since it keeps it at 3 lb. My two fears are acpi and graphics 4500mhd. I found links that show 4500 supported. http://freebsd.1045724.n5.nabble.com/subnotebooks-once-again-td4197868.html If the list thinks I should wait, it is a metter of adding the code as on this link: http://forums.freebsd.org/archive/index.php/t-21852.html Best regards all 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: HAST + ZFS: no action on drive failure
On Thu, 30 Jun 2011 20:02:19 -0700 Timothy Smith wrote: TS First posting here, hopefully I'm doing it right =) TS I also posted this to the FreeBSD forum, but I know some hast folks monitor TS this list regularly and not so much there, so... TS Basically, I'm testing failure scenarios with HAST/ZFS. I got two nodes, TS scripted up a bunch of checks and failover actions between the nodes. TS Looking good so far, though more complex that I expected. It would be cool TS to post it somewher to get some pointers/critiques, but that's another TS thing. TS Anyway, now I'm just seeing what happens when a drive fails on primary node. TS Oddly/sadly, NOTHING! TS Hast just keeps on a ticking, and doesn't change the state of the failed TS drive, so the zpool has no clue the drive is offline. The TS /dev/hast/resource remains. The hastd does log some errors to the system TS log like this, but nothing more. TS messages.0:Jun 30 18:39:59 nas1 hastd[11066]: [ada6] (primary) Unable to TS flush activemap to disk: Device not configured. TS messages.0:Jun 30 18:39:59 nas1 hastd[11066]: [ada6] (primary) Local request TS failed (Device not configured): WRITE(4736512, 512). Although the request to local drive failed it succeeded on remote node, so data was not lost, it was considered as successful, and no error was returned to ZFS. TS So, I guess the question is, Do I have to script a cronjob to check for TS these kinds of errors and then change the hast resource to 'init' or TS something to handle this? Or is there some kind of hastd config setting TS that I need to set? What's the SOP for this? Currently the only way to know is monitoring logs. It is not difficult to hook event for these errors in the HAST code (like it is done for connect/disconnect, syncstart/done etc) so one could script what to do on an error occurrence but I am not sure it is a good idea -- the errors may be generated with high rate. TS As something related too, when the zpool in FreeBSD does finally notice that TS the drive is missing because I have manually changed the hast resource to TS INIT (so the /dev/hast/res is gone), my zpool (raidz2) hot spare doesn't TS engage, even with autoreplace=on. The zpool status of the degraded pool TS seems to indicate that I should manually replace the failed drive. If that's TS the case, it's not really a hot spare. Does this mean the FMA Agent TS referred to in the ZFS manual is not implemented in FreeBSD? TS thanks! TS ___ TS freebsd-stable@freebsd.org mailing list TS http://lists.freebsd.org/mailman/listinfo/freebsd-stable TS To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Mikolaj Golub ___ 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: libarchive, lzma, and xz interaction
On Fri, Jul 1, 2011 at 11:32 PM, b. f. bf1...@googlemail.com wrote:
On Fri, Jul 1, 2011 at 7:19 PM, Kevin Oberman kob6558 at gmail.com wrote:
I'm trying to understand the problems I am having on some systems
regarding libarchive, lzma, and xz.
I have an 8-Stable system updated yesterday. As far as I can tell,
libarchive does include the lzma stuff
from libzma. At least I see the references. But several ports seem to
still pull in xz-5.0.1 and link to it.
This has a wonderful potential to cause library symbol conflicts. I get:
/usr/lib/libarchive.so: undefined reference to `lzma_stream_encoder at
XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_alone_decoder at
XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_memusage at XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_stream_decoder at
XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_code at XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_end at XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_lzma_preset at XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_alone_encoder at
XZ_5.0'
ldd shows libarchive linked against liblzma.so.5 and an objdump of the
dynamic symbols from liblzma.so.5
shows the undefined symbols defined with the XZ_5.0 version, so I am
mystified. It looks o me like it is
there. Is confusion with xz-5.0.1 causing this? Should get rid of it?
Even so, I don't understand why the
loader is claiming that these symbols are undefined when they seem to
be defined as far as I can tell.
7c60 g   DF .text  0084  XZ_5.0
lzma_stream_encoder
Any clues to what i happening would be greatly appreciated!
Nothing mysterious here:
src/lib/libarchive/archive_write_set_compression_xz.c uses some code
from the base system /usr/lib/liblzma.so shared library, from
src/lib/liblzma, which is derived from the base system xz 5.0.1, in
src/contrib/xz. Hence the symbols are present, with the symbol
versions that you noted, but undefined in libarchive, because it is
obtaining them from liblzma at run-time. It nudges rtld(1) to do this
in the usual way, via it's DT_NEEDED tag for that library:
objdump -x /usr/lib/libarchive.so | egrep 'NEEDED.*lzma'
Replying to myself, I re-built all programs that depended on xz and
then deleted the port. Now everything works fine. I still don't
completely understand what I was seeing, but it is working, now.
Perhaps you recently updated your base system, but were using old
ports or packages? With up-to-date ports and a recent version of
8-stable you should not have been able to build the archivers/xz port,
even if other ports mistakenly tried to drag it in, because of the
following lines in the ports/archivers/xz Makefile:
.if ${OSVERSION} = 900012 || (${OSVERSION} 90 ${OSVERSION} =
800505)
IGNORE= is already in the base system
.endif
Of course, you could have overridden this, by setting NO_IGNORE.
Thanks! Now I understand what was happening much better. It does make sense.
And you were right about the sequence o events. Due to a bug in the
atkbd driver in 8.1 and 8.2 I installed 8.0-RELEASE and, after
installing a few critical ports (which must have pulled in xz), I
csuped RELENG_8, I applied the required patch (which has now been
MFCed), and built a stable system. Unfortunately, I now had xz and got
into the problems I reported.
I am a bit disturbed to note that there is no entry in either
/usr/src/UPDATING or /usr/ports/UPDATING about lzma moving into the
base system and the need to re-install ports that had depended on the
xz port and delete xz. While googling for the problem I found many
reports of the problem with no solutions. A note in UPDATING (in this
case, probably both of them, but at least /usr/src) could have made
them easily resolved.
Thanks for taking the time to educate me. I've been working with
FreeBSD for several years, but I still don't know a great many things
about it.
--
R. Kevin Oberman, Network Engineer - Retired
E-mail: kob6...@gmail.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: devel/subversion: svn: Couldn't perform atomic initialization
On Sat, 02 Jul 2011 09:27:42 +0200 Hartmann, O. ohart...@zedat.fu-berlin.de wrote: Hello. Since two days now I realize on several recently ports-updated servers a failure of the subversion server running on those servers. Sneaking around the internet I found several issues exactly targeting this error with an sqlite 3.7.7/3.7.7.1 issue, which has been fixed in sqlite-3.7.7.2. At this very moment, our subversion servers in question has all recently been updated and it seems, they all fail the same way. Does anyone also realize this behaviour shown below when commiting? Is there a workaround? Any help or hint is appreciated. Thanks in advance, Oliver Transmitting file data .svn: Commit failed (details follow): svn: Couldn't perform atomic initialization svn: database schema has changed svn: Your commit message was left in a temporary file: Update database/sqlite3 port to the 3.7.7.1 version committed today. -- Alexander Kabaev signature.asc Description: PGP signature
Re: libarchive, lzma, and xz interaction
On 7/2/11, Kevin Oberman kob6...@gmail.com wrote: On Fri, Jul 1, 2011 at 11:32 PM, b. f. bf1...@googlemail.com wrote: On Fri, Jul 1, 2011 at 7:19 PM, Kevin Oberman kob6558 at gmail.com ... And you were right about the sequence o events. Due to a bug in the atkbd driver in 8.1 and 8.2 I installed 8.0-RELEASE and, after installing a few critical ports (which must have pulled in xz), I csuped RELENG_8, I applied the required patch (which has now been MFCed), and built a stable system. Unfortunately, I now had xz and got into the problems I reported. I am a bit disturbed to note that there is no entry in either /usr/src/UPDATING or /usr/ports/UPDATING about lzma moving into the base system and the need to re-install ports that had depended on the xz port and delete xz. While googling for the problem I found many reports of the problem with no solutions. A note in UPDATING (in this case, probably both of them, but at least /usr/src) could have made them easily resolved. Yes, this probably should have been mentioned in UPDATING. Oddly, it did make it into the 8.1 Release Notes. A complicating factor for those using packages from the FreeBSD build cluster is that the packages for 8* (i.e., packages-stable or packages-8-stable) are usually built on some version of the oldest supported security branch of 8, so for a period of time after the addition of xz to 8-stable those packages included an unnecessary dependency on archivers/xz for users of 8-stable, 8.1, and 8.1-stable. Fortunately, in this case, there probably wouldn't have been any adverse effects, other than a small waste of space and some confusion. b. ___ 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: HAST + ZFS: no action on drive failure
Hello Mikolaj, So, just to be clear, if a local drive fails in my pool, but the corresponding remote drive remains available, then hastd will both write to and read from the remote drive? That's really very cool! I looked more closely at the hastd(8) man page. There is some indication of what you say, but not so clear: Read operations (BIO_READ) are handled locally unless I/O error occurs or local version of the data is not up-to-date yet (synchronization is in progress). Perhaps this can be modified a bit? Adding, or the local disk is unavailable. In such a case, the I/O operation will be handled by the remote resource. It does makes sense however, since HAST is base on the idea of raid. This feature increases the redundancy of the system greatly. My boss will be very impressed, as am I! I did notice however that when the pulled drive is reinserted, I need to change the associated hast resource to init, then back to primary to allow hastd to once again use it (perhaps the same if the secondary drive is failed?). Unless it will do this on it's own after some time? I did not wait more than a few minutes. But this is easy enough to script or to monitor the log and present a notification to admin at such a time. Thank you so much for the help! On Sat, Jul 2, 2011 at 8:49 AM, Mikolaj Golub troc...@freebsd.org wrote: On Thu, 30 Jun 2011 20:02:19 -0700 Timothy Smith wrote: TS First posting here, hopefully I'm doing it right =) TS I also posted this to the FreeBSD forum, but I know some hast folks monitor TS this list regularly and not so much there, so... TS Basically, I'm testing failure scenarios with HAST/ZFS. I got two nodes, TS scripted up a bunch of checks and failover actions between the nodes. TS Looking good so far, though more complex that I expected. It would be cool TS to post it somewher to get some pointers/critiques, but that's another TS thing. TS Anyway, now I'm just seeing what happens when a drive fails on primary node. TS Oddly/sadly, NOTHING! TS Hast just keeps on a ticking, and doesn't change the state of the failed TS drive, so the zpool has no clue the drive is offline. The TS /dev/hast/resource remains. The hastd does log some errors to the system TS log like this, but nothing more. TS messages.0:Jun 30 18:39:59 nas1 hastd[11066]: [ada6] (primary) Unable to TS flush activemap to disk: Device not configured. TS messages.0:Jun 30 18:39:59 nas1 hastd[11066]: [ada6] (primary) Local request TS failed (Device not configured): WRITE(4736512, 512). Although the request to local drive failed it succeeded on remote node, so data was not lost, it was considered as successful, and no error was returned to ZFS. TS So, I guess the question is, Do I have to script a cronjob to check for TS these kinds of errors and then change the hast resource to 'init' or TS something to handle this? Or is there some kind of hastd config setting TS that I need to set? What's the SOP for this? Currently the only way to know is monitoring logs. It is not difficult to hook event for these errors in the HAST code (like it is done for connect/disconnect, syncstart/done etc) so one could script what to do on an error occurrence but I am not sure it is a good idea -- the errors may be generated with high rate. TS As something related too, when the zpool in FreeBSD does finally notice that TS the drive is missing because I have manually changed the hast resource to TS INIT (so the /dev/hast/res is gone), my zpool (raidz2) hot spare doesn't TS engage, even with autoreplace=on. The zpool status of the degraded pool TS seems to indicate that I should manually replace the failed drive. If that's TS the case, it's not really a hot spare. Does this mean the FMA Agent TS referred to in the ZFS manual is not implemented in FreeBSD? TS thanks! TS ___ TS freebsd-stable@freebsd.org mailing list TS http://lists.freebsd.org/mailman/listinfo/freebsd-stable TS To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Mikolaj Golub ___ 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: dell latitude 13
On Jul 2, 2011 4:16 AM, Zoran Kolic zko...@sbb.rs wrote: Thanks for answering my question. Since the Intel chip is also still unsupported by FreeBSD, you will be limited to VEDA support which is very limited. I found that dell sells ubuntu on mentioned laptop in some parts of the globe. Further, my old laptop (HP nx9020) has intel chip and works under intel driver. I need simple 2d, no frills. Does newer chip run for plain graphics at all? No acceleration? Fine. Linux has the required GEM/KMS support, but FreeBSD does not. It is being worked on, but I don't think it's near ready. I don't use it neither on my NVIDIA GeForce 6200 card with nv driver. The Optimus is a GPU designed in conjunction with Intel Sandy Bridge CPUs which have integrated Intel 5000 graphics. Optimus acts as an external accelerator using the Intel frame buffer. It will not work with any NVIDIA driver; nv, the NVIDIA binary driver, or the nouveau driver. NVIDIA has been clear that there is no plan to ever support Optimus on non-Windows systems. For laptops you may check the following site : http://laptop.bsdgroup.de/freebsd/ Old and no newer machines on the site. Also check FreeBSD Hardware lists such as ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/8.2-RELEASE/HARDWARE.HTM Intel 5100 wifi should work with device iwn5000fw or 5150? It is NOT possible to know in advance without any prior knowledge whether a computer is working with FreeDOS will work with FreeBSD because these are very different systems . It is sold with freedos to be cheap enough. I appreciate that. The producer/seller can install FreeBSD or Linux without cost Not where I live. When I bought my previous laptop, live cd was the guide if it worked at all. It is a matter of buy it as it is now. More, no cd on latitude 13, which is fine, since it keeps it at 3 lb. My two fears are acpi and graphics 4500mhd. I found links that show 4500 supported. http://freebsd.1045724.n5.nabble.com/subnotebooks-once-again-td4197868.html If the list thinks I should wait, it is a metter of adding the code as on this link: http://forums.freebsd.org/archive/index.php/t-21852.html If it is a 4500, you will have at least minimal graphics support. You should be able to disable the NVIDIA daughter card on BIOS, but I would not want to guarantee it. Good luck! R. Kevin Oberman, Network Engineer Retired kob6...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: scp: Write Failed: Cannot allocate memory
On Jul 2, 2011, at 12:54 AM, jhell wrote:
On Fri, Jul 01, 2011 at 03:22:32PM -0700, Jeremy Chadwick wrote:
On Fri, Jul 01, 2011 at 03:13:17PM -0400, Scott Sipe wrote:
I'm running 8.2-RELEASE and am having new problems with scp. When scping
files to a ZFS directory on the FreeBSD server -- most notably large files
-- the transfer frequently dies after just a few seconds. In my last test, I
tried to scp an 800mb file to the FreeBSD system and the transfer died after
200mb. It completely copied the next 4 times I tried, and then died again on
the next attempt.
On the client side:
Connection to home closed by remote host.
lost connection
In /var/log/auth.log:
Jul 1 14:54:42 freebsd sshd[18955]: fatal: Write failed: Cannot allocate
memory
I've never seen this before and have used scp before to transfer large files
without problems. This computer has been used in production for months and
has a current uptime of 36 days. I have not been able to notice any problems
copying files to the server via samba or netatalk, or any problems in
apache.
Uname:
FreeBSD xeon 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Sat Feb 19 01:02:54 EST
2011 root@xeon:/usr/obj/usr/src/sys/GENERIC amd64
I've attached my dmesg and output of vmstat -z.
I have not restarted the sshd daemon or rebooted the computer.
Am glad to provide any other information or test anything else.
{snip vmstat -z and dmesg}
You didn't provide details about your networking setup (rc.conf,
ifconfig -a, etc.). netstat -m would be useful too.
Next, please see this thread circa September 2010, titled Network
memory allocation failures:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/thread.html#58708
The user in that thread is using rsync, which relies on scp by default.
I believe this problem is similar, if not identical, to yours.
Please also provide your output of ( /usr/bin/limits -a ) for the server
end and the client.
I am not quite sure I agree with the need for ifconfig -a but some
information about the networking driver your using for the interface
would be helpful, uptime of the boxes. And configuration of the pool.
e.g. ( zpool status -a ;zfs get all poolname ) You should probably
prop this information up somewhere so you can reference by URL whenever
needed.
rsync(1) does not rely on scp(1) whatsoever but rsync(1) can be made to
use ssh(1) instead of rsh(1) and I believe that is what Jeremy is
stating here but correct me if I am wrong. It does use ssh(1) by
default.
Its a possiblity as well that if using tmpfs(5) or mdmfs(8) for /tmp
type filesystems that rsync(1) may be just filling up your temp ram area
and causing the connection abort which would be expected. ( df -h ) would
help here.
Hello,
I'm not using tmpfs/mdmfs at all. The clients yesterday were 3 different OSX
computers (over gigabit). The FreeBSD server has 12gb of ram and no bce
adapter. For what it's worth, the server is backed up remotely every night with
rsync (remote FreeBSD uses rsync to pull) to an offsite (slow cable connection)
FreeBSD computer, and I have not seen any errors in the nightly rsync.
Sorry for the omission of networking info, here's the output of the requested
commands and some that popped up in the other thread:
http://www.cap-press.com/misc/
In rc.conf: ifconfig_em1=inet 10.1.1.1 netmask 255.255.0.0
Scott
___
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
