Re: Proper way to share ZFS via NFS
which is why you shouldnt use /etc/exports for zfs datasets. Just because you can do something doesn't mean you should eg dancing down the motorway at night in dark clothing is never a good idea, no matter how confident you are in your skills. On 9 September 2013 15:22, Steve O'Hara-Smith wrote: > On Fri, 6 Sep 2013 11:43:03 -0700 > aurfalien wrote: > > > Hi, > > > > Wondering whats the correct way to share ZFS, /etc/exports or via zfs > > commands which alter /etc/zfs/exports? > > As far as I can see both work just fine. The first has the benefit > that it puts your ZFS exports in the standard place for exports and won't > need fiddling with if you decide that you want to move one of them to some > other filesystem. The second has the benefit that it integrates better with > the ZFS tools. > > The one thing you don't want to do is put the same export in both. > -- > Steve O'Hara-Smith > ___ > 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"
Does KMS work with gen 2 Intel graphics on FreeBSD 9.1?
Hi, I'm running FreeBSD 9.1 on an old IBM Thinkad X30 equiped with Intel 830MG graphics chip (gen 2). The graphics works fine, but I'm wondering if the driver really uses KMS or just switches back to some legacy routine. Is there any way I can check it? Cheers, Vladyslav ___ 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: Proper way to share ZFS via NFS
On Tue, 10 Sep 2013 12:10:13 +0100, krad wrote: > which is why you shouldnt use /etc/exports for zfs datasets. Just because > you can do something doesn't mean you should eg dancing down the motorway > at night in dark clothing is never a good idea, no matter how confident you > are in your skills. ZFS _encourages_ the use of its own toolset instead of those known from UFS. This includes the file system handling as well as backup/restore processes, mounting and exporting. ZFS has its own equivalents for those things. It's probably the best choice to use the _right_ tools here. :-) -- 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"
lang/gcc compile errors to build the port
Hi, I updated the system port: root@acer_casa_FreeBSD:/root # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. root@acer_casa_FreeBSD:/root # I have updated all ports: root@acer_casa_FreeBSD:/root # portmaster -Da ===>>> Starting check of installed ports for available updates ===>>> All ports are up to date ===>>> Exiting root@acer_casa_FreeBSD:/root # I paste the last lines of compile errors: /../gcc-4.6.3/libgfortran/../gcc -I../.././../gcc-4.6.3/libgfortran/../gcc/confi g -I../.././../gcc-4.6.3/libgfortran/../libquadmath -I../.././gcc -D_GNU_SOURCE -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -fcx-fortran-rules -ffunction-sections -fdata-sections -g -O2 -pipe -I/usr/local/include -fno-strict-aliasing -MT fmain.lo -MD -MP -MF .deps/fmain.Tpo -c ../.././../gcc-4.6.3/libgfortran/fmain.c -fPIC -DPIC -o .lib s/fmain.o cc1: error: unrecognized command line option '-fcx-fortran-rules' gmake[3]: *** [fmain.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/lang/gcc/work/build/i386-portbld-freebsd 9.1/libgfortran' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build/i386-portbld-freebsd 9.1/libgfortran' gmake[1]: *** [all-target-libgfortran] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake: *** [bootstrap-lean] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/lang/gcc. *** [build] Error code 1 Stop in /usr/ports/lang/gcc. root@acer_casa_FreeBSD:/usr/ports/lang/gcc # There is just an opening of 20090912 ( for lang/gcc44 ) and I guess is not relevant for this problem. I haven't found any relevant information about this problem. As a last resource I ask in this mailing list, if any can help me to fix this problem. See 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: lpd(8) sending email to the wrong address
On Tue, 10 Sep 2013, Olivier Nicole wrote: My printing system is archaic, based on lpr(8), but it works fine for centralizing printing from Windows (with Samba), Mac and Linux clients. Plus it includes a printing quota system, so I am reluctant to change. Don't apologize, many people use lpd as an alternative to the hidden complexity of CUPS. When a print job is failing, lpr will try to send a warning email to user@client but that e,ail address does not exist; is there a way to send email at user@default.domain instead? Looking at the source (usr.sbin/lpr/lpd/printjob.c), it does not appear there is any option. The sendmail() routine in that file could be modified. Or if you filter outgoing mail at or before the MTA, that filter could be changed to look for mail from lpd and adjust the domain. ___ 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: Does KMS work with gen 2 Intel graphics on FreeBSD 9.1?
The only way to have KMS support in 9.1 right now is to build with WITH_NEW_XORG=true and WITH_KMS=true in your make.conf, do you have these flags enabled? Another good check (right now) is to switch to a text console VT switching is not enabled so the screen will stay black (See https://wiki.freebsd.org/Intel_GPU) You will also have i915kms.ko loaded I am not a X11 dev, I just use the driver day to day so sorry I can't give you a better technical answer! On Tue, Sep 10, 2013 at 01:48:50PM +0200, Vladyslav Shtabovenko wrote: > Hi, > > I'm running FreeBSD 9.1 on an old IBM Thinkad X30 equiped with > Intel 830MG graphics chip (gen 2). The graphics works fine, but I'm > wondering > if the driver really uses KMS or just switches back to some legacy routine. > > Is there any way I can check it? > > Cheers, > Vladyslav > ___ > 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"
Re: Does KMS work with gen 2 Intel graphics on FreeBSD 9.1?
I see. Currently I'm using the stock 9.1 release kernel. It is rather painful to compile something on that laptop (Pentium M with ~1 GHz). I'll have access to the machine only this Friday. Then I'll check the thing with the text console. Thanks! Am 10.09.2013 16:08, schrieb Sean DuBois: The only way to have KMS support in 9.1 right now is to build with WITH_NEW_XORG=true and WITH_KMS=true in your make.conf, do you have these flags enabled? Another good check (right now) is to switch to a text console VT switching is not enabled so the screen will stay black (See https://wiki.freebsd.org/Intel_GPU) You will also have i915kms.ko loaded I am not a X11 dev, I just use the driver day to day so sorry I can't give you a better technical answer! On Tue, Sep 10, 2013 at 01:48:50PM +0200, Vladyslav Shtabovenko wrote: Hi, I'm running FreeBSD 9.1 on an old IBM Thinkad X30 equiped with Intel 830MG graphics chip (gen 2). The graphics works fine, but I'm wondering if the driver really uses KMS or just switches back to some legacy routine. Is there any way I can check it? Cheers, Vladyslav ___ 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"
Problems with stable/9 and LSI controlers?
Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? ___ 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: Problems with stable/9 and LSI controlers?
Whatever changed, happened between r253683 (July 26) and r255451 (today). On Tue, 10 Sep 2013, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? ___ 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"
Re: Problems with stable/9 and LSI controlers?
On Tue, Sep 10, 2013 at 12:35:02 -0700, Dennis Glatting wrote: > On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > >On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: > >>On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > >> > >>>On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > > Today I updated several systems against stable/9 that had not bee > updated > in ~five months. Two of the systems are serviced by LSI 2008 controllers > with a RAID1 array housing the operating system. > > These systems no longer properly boot. > > Specifically, they begin the boot process but bomb when they try to > mount > root. Neither system sees the GPT partitions of the boot disk at the > "mountroot>" prompt. On one system I replaced the hard disks, > repartitioned, and reinstalled but the problem continued. > > I don't see any mention of geom or controller update in UPDATING but I > know they have been updated because I saw their revisions fly actross my > screen during the svn update. Also, I am running IR vers 16 on my > controllers, which is the latest version of LSI firmware. > > Is there some new action I have to take to sucessfully boot LSI disks > against the updated kernel? > >>> > >>>Can you try the mpslsi driver from LSI's web site and see if that works? > >>> > >>>If it does, then it is a problem we've introduced locally. > >>> > >> > >>I'll give it a shot but just to be clear, I have been running the 16 > >>firmware for months. > > > >The issue is very likely in the driver, not the firmware. I'm just > >trying to figure out whether it broke in LSI's Phase 16 or in our > >additional changes in FreeBSD. > > > >In any case, I've reproduced the problem, and hopefully I'll know soon > >where the issue is. > > > >So don't worry about trying LSI's driver. Just go back to the previous > >version of stable/9 that worked for you until we fix it. > > > >This only affects RAID volumes, not regular disks. > > > > Thanks. > > I downloaded the mpslsi.ko driver from LSI under r255451 and the system > now boots. Okay, try the attached patch with the new driver and see whether it fixes the problem for you. The issue was that with the new rescanning code, we weren't rescanning RAID volumes that got created. It fixes the problem for me with a RAID-1 volume. There is still the issue of all of the verbose probe errors that crop up when an Integrated RAID volume is enabled, but it isn't obvious at the moment whether we can easily fix that. Ken -- Kenneth Merry k...@freebsd.org //depot/users/kenm/FreeBSD-stable2/9/sys/dev/mps/mps_sas_lsi.c#10 - /usr/home/kenm/perforce4/kenm/FreeBSD-stable2/9/sys/dev/mps/mps_sas_lsi.c *** /tmp/tmp.91039.2Tue Sep 10 14:13:13 2013 --- /usr/home/kenm/perforce4/kenm/FreeBSD-stable2/9/sys/dev/mps/mps_sas_lsi.c Tue Sep 10 14:07:08 2013 *** *** 892,898 --- 892,901 free(lun, M_MPT2); } SLIST_INIT(&targ->luns); + #if ((__FreeBSD_version >= 100) && (__FreeBSD_version < 139)) || \ + (__FreeBSD_version < 902502) if ((sassc->flags & MPSSAS_IN_STARTUP) == 0) + #endif mpssas_rescan_target(sc, targ); mps_dprint(sc, MPS_MAPPING, "RAID target id %d added (WWID = 0x%jx)\n", targ->tid, wwid); ___ 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: openjdk; iced-tea; itweb-javaws does not open
Dear folks,
I run test java on the browser and it works there. But I launch
*.jnlp file and it does not do anything. Java was working correctly
before updating iced-tea and openjdk. Advice/suggestions are greatly
appreciated to get it working again.
Best Regards,
Antonio
On Fri, Sep 6, 2013 at 10:49 AM, Antonio Olivares
wrote:
> Dear folks,
>
> In case something changed in file /usr/local/bin/itweb-javaws, see the
> following:
>
> root@grullahighschool:/usr/local/bin # cat itweb-javaws
> #!/usr/local/bin/bash
>
> JAVA=/usr/local/openjdk6/jre/bin/java
> LAUNCHER_BOOTCLASSPATH="-Xbootclasspath/a:/usr/local/share/icedtea-web/netx.jar"
> LAUNCHER_FLAGS=-Xms8m
> CLASSNAME=net.sourceforge.jnlp.runtime.Boot
> BINARY_LOCATION=/usr/local/bin/itweb-javaws
> SPLASH_LOCATION=/usr/local/share/icedtea-web/javaws_splash.png
> PROGRAM_NAME=itweb-javaws
> CP=/usr/local/openjdk6/jre/lib/rt.jar
>
> PROPERTY_NAME=deployment.jre.dir
> CUSTOM_JRE_REGEX="^$PROPERTY_NAME *= *"
> CUSTOM_JRE=`grep "$CUSTOM_JRE_REGEX" ~/.icedtea/deployment.properties
> 2>/dev/null | sed "s/$CUSTOM_JRE_REGEX//g"`
> if [ "x$CUSTOM_JRE" = "x" ] ; then
> CUSTOM_JRE=`grep "$CUSTOM_JRE_REGEX"
> /etc/.java/.deploy/deployment.properties 2>/dev/null | sed
> "s/$CUSTOM_JRE_REGEX//g"`
> fi;
> if [ "x$CUSTOM_JRE" != "x" ] ; then
> if [ -e "$CUSTOM_JRE" -a -e "$CUSTOM_JRE/bin/java" -a -e
> "$CUSTOM_JRE/lib/rt.jar" ] ; then
> JAVA=$CUSTOM_JRE/bin/java
> CP=$CUSTOM_JRE/lib/rt.jar
> else
> echo "Your custom JRE $CUSTOM_JRE read from deployment.properties
> under key $PROPERTY_NAME as $CUSTOM_JRE is not valid. Using default
> ($JAVA, $CP) in attempt to start. Please fix this."
> fi
> fi;
>
> JAVA_ARGS=( )
> ARGS=( )
> COMMAND=()
>
> i=0
> j=0
>
> SPLASH="false"
> if [ "x$ICEDTEA_WEB_SPLASH" = "x" ] ; then
> SPLASH="true"
> fi;
> while [ "$#" -gt "0" ]; do
> case "$1" in
> -J*)
> JAVA_ARGS[$i]="${1##-J}"
> i=$((i+1))
> ;;
> *)
> ARGS[$j]="$1"
> j=$((j+1))
> if [ "$1" = "-headless" ] ; then
> SPLASH="false"
> fi
> ;;
> esac
> shift
> done
>
> k=0
> COMMAND[k]="${JAVA}"
> k=$((k+1))
> if [ "$SPLASH" = "true" ] ; then
> COMMAND[k]="-splash:${SPLASH_LOCATION}"
> k=$((k+1))
> fi;
> COMMAND[k]="${LAUNCHER_BOOTCLASSPATH}"
> k=$((k+1))
> COMMAND[k]="${LAUNCHER_FLAGS}"
> k=$((k+1))
> i=0
> while [ "$i" -lt "${#JAVA_ARGS[@]}" ]; do
> COMMAND[k]="${JAVA_ARGS[$i]}"
> i=$((i+1))
> k=$((k+1))
> done
> COMMAND[k]="-classpath"
> k=$((k+1))
> COMMAND[k]="${CP}"
> k=$((k+1))
> COMMAND[k]="-Dicedtea-web.bin.name=${PROGRAM_NAME}"
> k=$((k+1))
> COMMAND[k]="-Dicedtea-web.bin.location=${BINARY_LOCATION}"
> k=$((k+1))
> COMMAND[k]="${CLASSNAME}"
> k=$((k+1))
> j=0
> while [ "$j" -lt "${#ARGS[@]}" ]; do
> COMMAND[k]="${ARGS[$j]}"
> j=$((j+1))
> k=$((k+1))
> done
>
> exec -a "itweb-javaws" "${COMMAND[@]}"
>
> exit $?
> root@grullahighschool:/usr/local/bin #
>
> Thanks in Advance,
>
>
> Antonio
>
> On Fri, Sep 6, 2013 at 10:45 AM, Antonio Olivares
> wrote:
>> Dear folks,
>>
>> While updating ports, openjdk and iced-tea the itweb-javaws jnlp
>> plugin does not launch. It is downloaded, but iced-tea/plugin is not
>> executed. Anybody else have this problem?
>>
>> openjdk6=
>> icedtea-web =
>>
>> Ideas?
>>
>> Thanks,
>>
>>
>> Antonio
___
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: HPN, nonecipher in 8.4
Op dinsdag 10 september 2013 schreef javocado (javoc...@gmail.com): > I have some questions about HPN and ssh, specifically: > > - does 8.4-RELEASE have HPN ssh built in by default? > > - if the only reason I ever installed openssh-portable port was to get HPN, > is there any reason to add that port anymore on 8.4? > > - if I would like to still use nonecipher, what is the easiest way to get > it, given a stock, standard 8.4-RELEASE install? > > Thanks You need to set the following in /etc/src.conf for the nonecipher *WITH**_**OPENSSH**_**NONE**_**CIPHER=yes* * * I think there is an option to rebuild only the ssh stuff without a whole buildworld. I do not know how however. Man src.conf give you some more hints on this http://www.freebsd.org/cgi/man.cgi?query=src.conf&apropos=0&sektion=0&manpath=FreeBSD+8.4-stable&arch=default&format=html Regards Johan Sorry for the bad layout, an ipad is not something I get used to regarding copy/paste, lettertype and size and so on. ___ > 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"
Re: Problems with stable/9 and LSI controlers?
On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? Can you try the mpslsi driver from LSI's web site and see if that works? If it does, then it is a problem we've introduced locally. I'll give it a shot but just to be clear, I have been running the 16 firmware for months. ___ 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: ufs recovery
Dear All, It looks like I'm able to recover all of the deleted files. I'm using UFS Explorer Professional Recovery, I'm working on it for more than 30 hours, its a long time but it works! Yaaay! Laci Sent from my mobile. On 2013.09.09., at 0:36, kpn...@pobox.com wrote: > On Mon, Sep 09, 2013 at 12:03:52AM +0200, Roland Smith wrote: >> On Sun, Sep 08, 2013 at 10:46:35AM +0200, Laszlo Danielisz wrote: >>> Hi, >>> >>> By mistake I forgot to edit my crontab on my FreeBSD 8.3 after I took out >>> one of the hard drives. I had a little rsync script which I used to >>> synchronise a directory between those two hard drives, because one of the >>> hard drives were not present anymore and rsync had the --delete parameter I >>> end up deleting the whole directory, of course with precious informations. >> >> Ouch. I have a similar procedure going. But I put it in a shell-script that >> mounts the destination _and_ checks if the destination is properly mounted >> _before_ >> starting the rsync. I would suggest you do something similar in the future. >> >> Just to be clear, was the information deleted from _both_ harddisks? > > How about using UFS labels and putting the label device into the fstab > instead of the raw block device? Then if the situation happens again > the changed block device names will not matter. > > I believe "tunefs -L" will do the trick. > -- > "A method for inducing cats to exercise consists of directing a beam of > invisible light produced by a hand-held laser apparatus onto the floor ... > in the vicinity of the cat, then moving the laser ... in an irregular way > fascinating to cats,..." -- US patent 5443036, "Method of exercising a cat" ___ 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: Does KMS work with gen 2 Intel graphics on FreeBSD 9.1?
On Tue, Sep 10, 2013 at 4:08 PM, Sean DuBois wrote: > Another good check (right now) is to switch to a text console VT > switching is not enabled so the screen will stay black > (See https://wiki.freebsd.org/Intel_GPU) > This is realy painful that there is no text console :-( This is why I still need to use VESA driver :-( -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: Problems with stable/9 and LSI controlers?
On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: > On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > > >On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > >> > >>Today I updated several systems against stable/9 that had not bee updated > >>in ~five months. Two of the systems are serviced by LSI 2008 controllers > >>with a RAID1 array housing the operating system. > >> > >>These systems no longer properly boot. > >> > >>Specifically, they begin the boot process but bomb when they try to mount > >>root. Neither system sees the GPT partitions of the boot disk at the > >>"mountroot>" prompt. On one system I replaced the hard disks, > >>repartitioned, and reinstalled but the problem continued. > >> > >>I don't see any mention of geom or controller update in UPDATING but I > >>know they have been updated because I saw their revisions fly actross my > >>screen during the svn update. Also, I am running IR vers 16 on my > >>controllers, which is the latest version of LSI firmware. > >> > >>Is there some new action I have to take to sucessfully boot LSI disks > >>against the updated kernel? > > > >Can you try the mpslsi driver from LSI's web site and see if that works? > > > >If it does, then it is a problem we've introduced locally. > > > > I'll give it a shot but just to be clear, I have been running the 16 > firmware for months. The issue is very likely in the driver, not the firmware. I'm just trying to figure out whether it broke in LSI's Phase 16 or in our additional changes in FreeBSD. In any case, I've reproduced the problem, and hopefully I'll know soon where the issue is. So don't worry about trying LSI's driver. Just go back to the previous version of stable/9 that worked for you until we fix it. This only affects RAID volumes, not regular disks. Ken -- Kenneth Merry k...@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"
Re: ufs recovery
On Tue, 10 Sep 2013 22:38:46 +0200, Laszlo Danielisz wrote: > Dear All, > > It looks like I'm able to recover all of the deleted files. > I'm using UFS Explorer Professional Recovery, I'm working on it > for more than 30 hours, its a long time but it works! If recovery works, time does not matter. Success does. :-) -- 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: Problems with stable/9 and LSI controlers?
On Tue, Sep 10, 2013 at 11:21:02AM -0700, Dennis Glatting wrote: > > Today I updated several systems against stable/9 that had not bee updated > in ~five months. Two of the systems are serviced by LSI 2008 controllers > with a RAID1 array housing the operating system. > > These systems no longer properly boot. > > Specifically, they begin the boot process but bomb when they try to mount > root. Neither system sees the GPT partitions of the boot disk at the > "mountroot>" prompt. On one system I replaced the hard disks, > repartitioned, and reinstalled but the problem continued. > > I don't see any mention of geom or controller update in UPDATING but I > know they have been updated because I saw their revisions fly actross my > screen during the svn update. Also, I am running IR vers 16 on my > controllers, which is the latest version of LSI firmware. > > Is there some new action I have to take to sucessfully boot LSI disks > against the updated kernel? Hi, does it use the mfi driver? Because that has been updated. There was an errata notice about it on the 22nd August concerning mfi in JBOD mode and disks >2TB -- 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"
Re: Problems with stable/9 and LSI controlers?
On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 12:35:02 -0700, Dennis Glatting wrote: On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? Can you try the mpslsi driver from LSI's web site and see if that works? If it does, then it is a problem we've introduced locally. I'll give it a shot but just to be clear, I have been running the 16 firmware for months. The issue is very likely in the driver, not the firmware. I'm just trying to figure out whether it broke in LSI's Phase 16 or in our additional changes in FreeBSD. In any case, I've reproduced the problem, and hopefully I'll know soon where the issue is. So don't worry about trying LSI's driver. Just go back to the previous version of stable/9 that worked for you until we fix it. This only affects RAID volumes, not regular disks. Thanks. I downloaded the mpslsi.ko driver from LSI under r255451 and the system now boots. Okay, try the attached patch with the new driver and see whether it fixes the problem for you. The issue was that with the new rescanning code, we weren't rescanning RAID volumes that got created. It fixes the problem for me with a RAID-1 volume. The patch worked for one of my servers. I can't test the second server until tonight however the problem is the same. There is still the issue of all of the verbose probe errors that crop up when an Integrated RAID volume is enabled, but it isn't obvious at the moment whether we can easily fix that. ___ 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: Problems with stable/9 and LSI controlers?
On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: On Tue, 10 Sep 2013, Kenneth D. Merry wrote: On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? Can you try the mpslsi driver from LSI's web site and see if that works? If it does, then it is a problem we've introduced locally. I'll give it a shot but just to be clear, I have been running the 16 firmware for months. The issue is very likely in the driver, not the firmware. I'm just trying to figure out whether it broke in LSI's Phase 16 or in our additional changes in FreeBSD. In any case, I've reproduced the problem, and hopefully I'll know soon where the issue is. So don't worry about trying LSI's driver. Just go back to the previous version of stable/9 that worked for you until we fix it. This only affects RAID volumes, not regular disks. Thanks. I downloaded the mpslsi.ko driver from LSI under r255451 and the system now boots. ___ 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: Proper way to share ZFS via NFS
On Tue, 10 Sep 2013 12:10:13 +0100 krad wrote: > which is why you shouldnt use /etc/exports for zfs datasets. Just because Not so clear, if you are using a mixture of filesystems you may very sensibly opt to keep all your export controls in one place, similarly if you have servers running multiple OSs then not having to remember that the FreeBSD/ZFS box manages it's exports differently to the Linux/ext2fs may well be a benefit. You may have management tools and not wish to extend them to handle ZFS explicitly. There can be good reasons both ways. -- Steve O'Hara-Smith | Directable Mirror Arrays C:>WIN | A better way to focus the sun The computer obeys and wins.|licences available see You lose and Bill collects. |http://www.sohara.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"
Re: Problems with stable/9 and LSI controlers?
On Tue, 10 Sep 2013, John wrote: On Tue, Sep 10, 2013 at 11:21:02AM -0700, Dennis Glatting wrote: Today I updated several systems against stable/9 that had not bee updated in ~five months. Two of the systems are serviced by LSI 2008 controllers with a RAID1 array housing the operating system. These systems no longer properly boot. Specifically, they begin the boot process but bomb when they try to mount root. Neither system sees the GPT partitions of the boot disk at the "mountroot>" prompt. On one system I replaced the hard disks, repartitioned, and reinstalled but the problem continued. I don't see any mention of geom or controller update in UPDATING but I know they have been updated because I saw their revisions fly actross my screen during the svn update. Also, I am running IR vers 16 on my controllers, which is the latest version of LSI firmware. Is there some new action I have to take to sucessfully boot LSI disks against the updated kernel? Hi, does it use the mfi driver? Because that has been updated. There was an errata notice about it on the 22nd August concerning mfi in JBOD mode and disks >2TB (typing by hand) mps0: port 0xb-0xb0ff mem mps0: Firmware: 16.00.00.00, Driver: 16.00.00.00-fbsd mps0: IOCCapabilities: 185c The system I am sitting in front of, appears NOT to see the RAID1 disk but does see the two non-RAID disks. All disks are 1TB Seagate ST31000424SS. The second system, which is remote and I cannot view its console from here, has two 250GB disks RAID1. ___ 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: Problems with stable/9 and LSI controlers?
On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > > Today I updated several systems against stable/9 that had not bee updated > in ~five months. Two of the systems are serviced by LSI 2008 controllers > with a RAID1 array housing the operating system. > > These systems no longer properly boot. > > Specifically, they begin the boot process but bomb when they try to mount > root. Neither system sees the GPT partitions of the boot disk at the > "mountroot>" prompt. On one system I replaced the hard disks, > repartitioned, and reinstalled but the problem continued. > > I don't see any mention of geom or controller update in UPDATING but I > know they have been updated because I saw their revisions fly actross my > screen during the svn update. Also, I am running IR vers 16 on my > controllers, which is the latest version of LSI firmware. > > Is there some new action I have to take to sucessfully boot LSI disks > against the updated kernel? Can you try the mpslsi driver from LSI's web site and see if that works? If it does, then it is a problem we've introduced locally. If it doesn't, then LSI needs to fix it. Ken -- Kenneth Merry k...@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"
HPN, nonecipher in 8.4
I have some questions about HPN and ssh, specifically: - does 8.4-RELEASE have HPN ssh built in by default? - if the only reason I ever installed openssh-portable port was to get HPN, is there any reason to add that port anymore on 8.4? - if I would like to still use nonecipher, what is the easiest way to get it, given a stock, standard 8.4-RELEASE install? 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: Problems with stable/9 and LSI controlers?
Both servers work with this patch applied. On Tue, 2013-09-10 at 14:29 -0600, Kenneth D. Merry wrote: > On Tue, Sep 10, 2013 at 12:35:02 -0700, Dennis Glatting wrote: > > On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > > >On Tue, Sep 10, 2013 at 12:11:38 -0700, Dennis Glatting wrote: > > >>On Tue, 10 Sep 2013, Kenneth D. Merry wrote: > > >> > > >>>On Tue, Sep 10, 2013 at 11:21:02 -0700, Dennis Glatting wrote: > > > > Today I updated several systems against stable/9 that had not bee > > updated > > in ~five months. Two of the systems are serviced by LSI 2008 controllers > > with a RAID1 array housing the operating system. > > > > These systems no longer properly boot. > > > > Specifically, they begin the boot process but bomb when they try to > > mount > > root. Neither system sees the GPT partitions of the boot disk at the > > "mountroot>" prompt. On one system I replaced the hard disks, > > repartitioned, and reinstalled but the problem continued. > > > > I don't see any mention of geom or controller update in UPDATING but I > > know they have been updated because I saw their revisions fly actross my > > screen during the svn update. Also, I am running IR vers 16 on my > > controllers, which is the latest version of LSI firmware. > > > > Is there some new action I have to take to sucessfully boot LSI disks > > against the updated kernel? > > >>> > > >>>Can you try the mpslsi driver from LSI's web site and see if that works? > > >>> > > >>>If it does, then it is a problem we've introduced locally. > > >>> > > >> > > >>I'll give it a shot but just to be clear, I have been running the 16 > > >>firmware for months. > > > > > >The issue is very likely in the driver, not the firmware. I'm just > > >trying to figure out whether it broke in LSI's Phase 16 or in our > > >additional changes in FreeBSD. > > > > > >In any case, I've reproduced the problem, and hopefully I'll know soon > > >where the issue is. > > > > > >So don't worry about trying LSI's driver. Just go back to the previous > > >version of stable/9 that worked for you until we fix it. > > > > > >This only affects RAID volumes, not regular disks. > > > > > > > Thanks. > > > > I downloaded the mpslsi.ko driver from LSI under r255451 and the system > > now boots. > > Okay, try the attached patch with the new driver and see whether it fixes > the problem for you. > > The issue was that with the new rescanning code, we weren't rescanning RAID > volumes that got created. > > It fixes the problem for me with a RAID-1 volume. > > There is still the issue of all of the verbose probe errors that crop up > when an Integrated RAID volume is enabled, but it isn't obvious at the > moment whether we can easily fix that. > > Ken ___ 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: Proper way to share ZFS via NFS
If you cant cope with multiple operating systems and their differences you are probably in the wrong job. On 10 September 2013 19:39, Steve O'Hara-Smith wrote: > On Tue, 10 Sep 2013 12:10:13 +0100 > krad wrote: > > > which is why you shouldnt use /etc/exports for zfs datasets. Just because > > Not so clear, if you are using a mixture of filesystems you may > very sensibly opt to keep all your export controls in one place, similarly > if you have servers running multiple OSs then not having to remember that > the FreeBSD/ZFS box manages it's exports differently to the Linux/ext2fs > may well be a benefit. You may have management tools and not wish to extend > them to handle ZFS explicitly. > > There can be good reasons both ways. > > -- > Steve O'Hara-Smith | Directable Mirror Arrays > C:>WIN | A better way to focus the sun > The computer obeys and wins.|licences available see > You lose and Bill collects. |http://www.sohara.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"
