Re: Make Buildworld Fails (Broken Servers)
> The root cause was a bad cvsup server. Randy posted to freebsd-hubs > about the problem (I haven't looked to find the mail though). found four bad servers while upgrading various systems. entropy seems to have struck the hub system. randy ___ 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: Make Buildworld Fails (Broken Servers)
On Fri, Jan 27, 2012 at 08:26:28PM -0800, Thomas D. Dean wrote: > On 01/27/12 15:46, Thomas D. Dean wrote: > > I earlier used cvsup4.FreeBSD.org. No files were updated. > Buildworld was broken as I reported earlier. > > # cvsup10.FreeBSD.org ### > Now, I used cvsup10.FreeBSD.org. Many (~150?) files were updated. > > # cd /usr/src > # env -i make cleandir > # env -i make cleandir > # env -i make -j 10 buildworld > ... > failed on iterator.c - redo to check if -j 10 broke things. > > # env -i make cleandir > # env -i make cleandir > # env -i make buildworld > ... > mkdep -f .depend -a-I/usr/obj/usr/src/tmp/legacy/usr/include > /usr/src/games/fortune/strfile/strfile.c > echo strfile: /usr/lib/libc.a > /usr/obj/usr/src/tmp/legacy/usr/lib/libegacy.a >> .depend > cc -O2 -pipe -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include > -c /usr/src/games/fortune/strfile/strfile.c > cc -O2 -pipe -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include > -static -L/usr/obj/usr/src/tmp/legacy/usr/lib -o strfile strfile.o > -legacy > sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 strfile > /usr/obj/usr/src/tmp/legacy/usr/games > ===> gnu/usr.bin/gperf (obj,depend,all,install) > /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/gperf created for > /usr/src/gnu/usr.bin/gperf > ===> gnu/usr.bin/gperf/doc (obj) > /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/gperf/doc created for > /usr/src/gnu/usr.bin/gperf/doc > make: don't know how to make iterator.cc. Stop > *** Error code 2 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > No, -j10 did not break it. This error shown here is *exactly* what Randy Bush posted about a few days ago. Please read the ENTIRE THREAD. http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065616.html The root cause was a bad cvsup server. Randy posted to freebsd-hubs about the problem (I haven't looked to find the mail though). > # cvsup5.FreeBSD.org ### > > # cd /usr/src > # env -i make cleandir > # env -i make cleandir > # env -i make buildworld > ... > same problem as with cvsup4, > cd /usr/src/kerberos5/tools/asn1_compile/../make-print-version && make > make: don't know how to make /usr/src/tmp/legacy/usr/lib/libegacy.a. Stop No, this is a different error, which could ALSO be caused by a bad cvsup server. You should post these problems to freebsd-hubs; the owners of the cvsup servers need to be made aware of these problems. Finally: please stop with the "cleandir". rm -fr /usr/obj/* and do not use make -jX at all. This will rule out any inconsistencies. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: Make Buildworld Fails (Broken Servers)
On 01/27/12 15:46, Thomas D. Dean wrote: I earlier used cvsup4.FreeBSD.org. No files were updated. Buildworld was broken as I reported earlier. # cvsup10.FreeBSD.org ### Now, I used cvsup10.FreeBSD.org. Many (~150?) files were updated. # cd /usr/src # env -i make cleandir # env -i make cleandir # env -i make -j 10 buildworld ... failed on iterator.c - redo to check if -j 10 broke things. # env -i make cleandir # env -i make cleandir # env -i make buildworld ... mkdep -f .depend -a-I/usr/obj/usr/src/tmp/legacy/usr/include /usr/src/games/fortune/strfile/strfile.c echo strfile: /usr/lib/libc.a /usr/obj/usr/src/tmp/legacy/usr/lib/libegacy.a >> .depend cc -O2 -pipe -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/games/fortune/strfile/strfile.c cc -O2 -pipe -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include -static -L/usr/obj/usr/src/tmp/legacy/usr/lib -o strfile strfile.o -legacy sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 strfile /usr/obj/usr/src/tmp/legacy/usr/games ===> gnu/usr.bin/gperf (obj,depend,all,install) /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/gperf created for /usr/src/gnu/usr.bin/gperf ===> gnu/usr.bin/gperf/doc (obj) /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/gperf/doc created for /usr/src/gnu/usr.bin/gperf/doc make: don't know how to make iterator.cc. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. No, -j10 did not break it. # cvsup5.FreeBSD.org ### # cd /usr/src # env -i make cleandir # env -i make cleandir # env -i make buildworld ... same problem as with cvsup4, cd /usr/src/kerberos5/tools/asn1_compile/../make-print-version && make make: don't know how to make /usr/src/tmp/legacy/usr/lib/libegacy.a. Stop Tom Dean ___ 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: Make Buildworld Fails
On 01/27/12 16:52, Jeremy Chadwick wrote: What cvsup mirror did you use? There has been a recent influx of problems people have reported with building world all of which have related to problems with certain cvsup servers. You can read about those problems on freebsd-stable, or look on freebsd-hubs (which is the place such issues get reported). I recommend you try a different cvsup mirror for starters. Also: was this system "upgraded" from 8.2 to 9.0 by changing a release tag in one of your supfiles, or was it always 9.0? Always on FreeBSD 9.0. I will try a different server. # cat /sup/stable-supfile|sed '/^#/d' *default host=cvsup4.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_9 *default delete use-rel-suffix *default compress src-all Tom Dean ___ 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: Make Buildworld Fails
On Fri, Jan 27, 2012 at 03:46:53PM -0800, Thomas D. Dean wrote: > # uname -a > FreeBSD P9X79.tddhome 9.0-STABLE FreeBSD 9.0-STABLE #0: Wed Jan 4 > 14:16:41 PST 2012 tomdean@P9X79.tddhome:/usr/src/sys/GENERIC > amd64 > > Source up-to-date as of now, via cvsup. What cvsup mirror did you use? There has been a recent influx of problems people have reported with building world all of which have related to problems with certain cvsup servers. You can read about those problems on freebsd-stable, or look on freebsd-hubs (which is the place such issues get reported). I recommend you try a different cvsup mirror for starters. Also: was this system "upgraded" from 8.2 to 9.0 by changing a release tag in one of your supfiles, or was it always 9.0? > # env -i make cleandir > # env -i make cleandir > # env -i make buildworld > ... > cc -O2 -pipe -I. -DGCCVER=\"4.2\" -DIN_GCC -DHAVE_CONFIG_H > -DPREFIX=\"/usr\" > -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc > -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config > -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include > -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include > -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber > -g -DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89 > -I/usr/obj/usr/src/tmp/legacy/usr/include > -L/usr/obj/usr/src/tmp/legacy/usr/lib -o genchecksum genchecksum.o > errors.o libiberty.a > ===> kerberos5/tools (obj,depend,all) > ===> kerberos5/tools/make-print-version (obj) > ===> kerberos5/tools/make-roken (obj) > ===> kerberos5/tools/asn1_compile (obj) > ===> kerberos5/tools/slc (obj) > ===> kerberos5/tools/make-print-version (depend) > ===> kerberos5/tools/make-roken (depend) > ===> kerberos5/tools/asn1_compile (depend) > cd /usr/src/kerberos5/tools/asn1_compile/../make-print-version && make > make: don't know how to make /usr/src/tmp/legacy/usr/lib/libegacy.a. Stop > *** Error code 2 > > Stop in /usr/src/kerberos5/tools/asn1_compile. > *** Error code 1 Nothing in either of these trees has changed in many years: http://www.freebsd.org/cgi/cvsweb.cgi/src/kerberos5/tools/ http://www.freebsd.org/cgi/cvsweb.cgi/src/kerberos5/tools/asn1_compile/ http://www.freebsd.org/cgi/cvsweb.cgi/src/kerberos5/tools/make-print-version/ Also, please do not rely on "cleandir" to remove all old /usr/obj objects. Please rm -fr /usr/obj/* instead. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: kerberized NFS
Giulio Ferro wrote: > I'm trying to setup a kerberized NFS system made of a server and a > client (both freebsd 9 amd64 stable) > > I've tried to follow this howto: > http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > But couldn't get much out of it. > > First question : is this howto still valid or something more recent > should be followed? I've searched with Google but I've come up empty. > It's all there is. I don't think anything has changed since it was written. (I haven't had a kerberos setup for about 2 years, so I know I haven't changed anything recently.) It was a google wiki, since I hoped others would add to it, but I don't think that has happened? > I've set up kerberos heimdal, created the dns entries for both > client and server, set up krb5.keytab and copied it to client, set > up nfs4 according to man nfsv4: > > (server) > cat /etc/exports > V4: /usr/src -sec=krb5:krb5i:krb5p > The V4: line doesn't export any file system. It only defines where the root of the directory tree is for NFSv4 and what authentication can be used for "system operations" which do not take any file handle and, therefore, aren't tied to any server file system. For example, the above would need to be something like: V4: /usr/src -sec=krb5:krb5i:krb5p /usr/src -sec=krb5:krb5i:krb5p - If /usr/src is not the root of a file system on the server, it is less confusing to export the root of the file system, such as "/usr" or "/". > and then tried to mount it from the client: > > mount_nfs -o ntfsv4,sec=krb5i,gssname=nfs > nfsinternal1.dcssrl.it:/usr/src /usr/src > To make the "gssname" case work, you need a couple of things: - You need the patch it refers to applied to the client's kernel, so it can handle "host based initiator credentials". After applying the patch, you also need to have an entry in the client's /etc/keytab that looks like: nfs/client-host.dnsdomain@YOUR.REALM Without the above, the client can only do an NFSv4 mount as a user (not root) that has a valid credential. For example: - non-root mounts enabled via # sysctl vfs.usermount=1 - then a user logs in - gets a kerberos TGT via "kinit" - then does a mount command that looks like: % mount -t nfs -o nfsv4,sec=krb5i :/path - this mount breaks if this user's TGT expires, so it either must be maintained via some utility (there are a couple out there, but I can't remember the name of one offhand) or manually by doing "kinit" again before it expires - this user must umount the file system when done with it (I know, it would be nice if the host based initiator cred. worked, "out of the box", but the patch is ugly and the reviewer understandably didn't agree with it. However, I don't know how to do it another way for the version of Heimdal in FreeBSD. There is a bug that has apparently been fixed for newer Heimdal releases, where it gets confused w.r.t. encryption type for the keytab entry unless it is forced to one encryption type only.) Also, you need the following in the server's /etc/rc.conf: nfsv4_server_enable="YES" gssd_enable="YES" and in the client: nfsuserd_enable="YES" gssd_enable="YES" Finally, I'd suggest that you get NFSv4 mounts over "sys" working first and then you can try Kerberos. > but it failed with : > [tcp] nfsinternal1.dcssrl.it:/usr/src: Permission denied > > Can you point me to something that I might have got wrong? > > Thanks in advance. > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-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"
Make Buildworld Fails
# uname -a FreeBSD P9X79.tddhome 9.0-STABLE FreeBSD 9.0-STABLE #0: Wed Jan 4 14:16:41 PST 2012 tomdean@P9X79.tddhome:/usr/src/sys/GENERIC amd64 Source up-to-date as of now, via cvsup. # env -i make cleandir # env -i make cleandir # env -i make buildworld ... cc -O2 -pipe -I. -DGCCVER=\"4.2\" -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber -g -DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89 -I/usr/obj/usr/src/tmp/legacy/usr/include -L/usr/obj/usr/src/tmp/legacy/usr/lib -o genchecksum genchecksum.o errors.o libiberty.a ===> kerberos5/tools (obj,depend,all) ===> kerberos5/tools/make-print-version (obj) ===> kerberos5/tools/make-roken (obj) ===> kerberos5/tools/asn1_compile (obj) ===> kerberos5/tools/slc (obj) ===> kerberos5/tools/make-print-version (depend) ===> kerberos5/tools/make-roken (depend) ===> kerberos5/tools/asn1_compile (depend) cd /usr/src/kerberos5/tools/asn1_compile/../make-print-version && make make: don't know how to make /usr/src/tmp/legacy/usr/lib/libegacy.a. Stop *** Error code 2 Stop in /usr/src/kerberos5/tools/asn1_compile. *** Error code 1 Stop in /usr/src/kerberos5/tools. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Tom Dean _ ___ 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: kerberized NFS
Yuri Pankov wrote: > On Fri, Jan 27, 2012 at 06:58:47PM +0100, Giulio Ferro wrote: > > I'm trying to setup a kerberized NFS system made of a server and a > > client (both freebsd 9 amd64 stable) > > > > I've tried to follow this howto: > > http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > > > But couldn't get much out of it. > > > > First question : is this howto still valid or something more recent > > should be followed? I've searched with Google but I've come up > > empty. > > > > I've set up kerberos heimdal, created the dns entries for both > > client and server, set up krb5.keytab and copied it to client, set > > up nfs4 according to man nfsv4: > > > > (server) > > cat /etc/exports > > V4: /usr/src -sec=krb5:krb5i:krb5p > > > > and then tried to mount it from the client: > > > > mount_nfs -o ntfsv4,sec=krb5i,gssname=nfs > > nfsinternal1.dcssrl.it:/usr/src /usr/src > > > > but it failed with : > > [tcp] nfsinternal1.dcssrl.it:/usr/src: Permission denied > > > > Can you point me to something that I might have got wrong? > > Not really related to Kerberos question, but.. Some problems here: > - ntfsv4 - probably a typo > - more serious one - V4: line specifies the ROOT of NFSv4 exported FS > - nfsinternal1.dcssrl.it:/usr/src points to /usr/src/usr/src. > > What you /etc/exports could look like (the way it works for me, > doesn't > mean that it's correct though): > > /usr/src > V4: / -sec=krb5:krb5i:krb5p > Yes. If you specify "/", then the tree starts at the root. The main problem with doing this is that, for ZFS, you then have to export all file systems from "/" down to where you want to mount. (Again, these are done by export lines separate from the "V4:" line.) If you specify: V4: /usr/src -sec=krb5:krb5i:krb5p /usr/src -sec=krb5:krb5i:krb5p then the client mounts /usr/src via: % mount -t nfs -o nfsv4,sec=krb5i server:/ /mntpoint rick > > Yuri ___ 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: kerberized NFS
Yuri Pankov wrote: > On Fri, Jan 27, 2012 at 06:58:47PM +0100, Giulio Ferro wrote: > > I'm trying to setup a kerberized NFS system made of a server and a > > client (both freebsd 9 amd64 stable) > > > > I've tried to follow this howto: > > http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > > > But couldn't get much out of it. > > > > First question : is this howto still valid or something more recent > > should be followed? I've searched with Google but I've come up > > empty. > > > > I've set up kerberos heimdal, created the dns entries for both > > client and server, set up krb5.keytab and copied it to client, set > > up nfs4 according to man nfsv4: > > > > (server) > > cat /etc/exports > > V4: /usr/src -sec=krb5:krb5i:krb5p > > > > and then tried to mount it from the client: > > > > mount_nfs -o ntfsv4,sec=krb5i,gssname=nfs > > nfsinternal1.dcssrl.it:/usr/src /usr/src > > > > but it failed with : > > [tcp] nfsinternal1.dcssrl.it:/usr/src: Permission denied > > > > Can you point me to something that I might have got wrong? > > Not really related to Kerberos question, but.. Some problems here: > - ntfsv4 - probably a typo > - more serious one - V4: line specifies the ROOT of NFSv4 exported FS > - nfsinternal1.dcssrl.it:/usr/src points to /usr/src/usr/src. > > What you /etc/exports could look like (the way it works for me, > doesn't > mean that it's correct though): > > /usr/src > V4: / -sec=krb5:krb5i:krb5p > > > Yuri Btw, Guilio, your email address bounces for me, so hopefully you read the mailing list and see the previous messages. rick ___ 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: kerberized NFS
On Fri, Jan 27, 2012 at 06:58:47PM +0100, Giulio Ferro wrote: > I'm trying to setup a kerberized NFS system made of a server and a > client (both freebsd 9 amd64 stable) > > I've tried to follow this howto: > http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > But couldn't get much out of it. > > First question : is this howto still valid or something more recent > should be followed? I've searched with Google but I've come up empty. > > I've set up kerberos heimdal, created the dns entries for both > client and server, set up krb5.keytab and copied it to client, set > up nfs4 according to man nfsv4: > > (server) > cat /etc/exports > V4: /usr/src -sec=krb5:krb5i:krb5p > > and then tried to mount it from the client: > > mount_nfs -o ntfsv4,sec=krb5i,gssname=nfs > nfsinternal1.dcssrl.it:/usr/src /usr/src > > but it failed with : > [tcp] nfsinternal1.dcssrl.it:/usr/src: Permission denied > > Can you point me to something that I might have got wrong? Not really related to Kerberos question, but.. Some problems here: - ntfsv4 - probably a typo - more serious one - V4: line specifies the ROOT of NFSv4 exported FS - nfsinternal1.dcssrl.it:/usr/src points to /usr/src/usr/src. What you /etc/exports could look like (the way it works for me, doesn't mean that it's correct though): /usr/src V4: / -sec=krb5:krb5i:krb5p Yuri pgppn2KRnhQoB.pgp Description: PGP signature
kerberized NFS
I'm trying to setup a kerberized NFS system made of a server and a client (both freebsd 9 amd64 stable) I've tried to follow this howto: http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup But couldn't get much out of it. First question : is this howto still valid or something more recent should be followed? I've searched with Google but I've come up empty. I've set up kerberos heimdal, created the dns entries for both client and server, set up krb5.keytab and copied it to client, set up nfs4 according to man nfsv4: (server) cat /etc/exports V4: /usr/src -sec=krb5:krb5i:krb5p and then tried to mount it from the client: mount_nfs -o ntfsv4,sec=krb5i,gssname=nfs nfsinternal1.dcssrl.it:/usr/src /usr/src but it failed with : [tcp] nfsinternal1.dcssrl.it:/usr/src: Permission denied Can you point me to something that I might have got wrong? Thanks in advance. ___ 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: Panic on 7.4-RELEASE-p5
On 01/27/2012 04:43 AM, Gary Palmer wrote: > > After scanning selected spans, do NOT read-scan remainder of disk. > If Selective self-test is pending on power-up, resume after 0 minute delay. > > I noticed a while ago that there were some "bad" sectors on the disk, and > at the time they were under the swap partition if my math was correct, > and the box never swaps so it wasn't a problem. I don't know if > the errors above are the same ones I saw earlier or not. > > There were no read or write errors on the console prior to the panic > earlier today. In fact the previos output on the console relates to > the last reboot for a software upgrade (fixing some packages) 11 > days prior. The only thing in logs going back to November relating > to ad1 are boot messages. > > Thanks, > > Gary > Unmount your swap, and then write zeros to it to relocate the bad sectors. in one shell: gstat -I 100ms -f da#p# in another: swapoff /dev/da#p# sysctl kern.geom.debugflags=0x10 dd if=/dev/zero of=/dev/da#p# bs=1M (eventually it stops saying end of device or no space left; at this point I am not sure if you should then continue writing where it stopped in 512 byte blocks, or if it wrote a partial 1M in the last 1M) Watch first shell. If the speed goes up, settles at a certain number, then wildly goes down low and back up to that number, it is possibly working. Then repeat. If the same wild fluctuations happen, then the drive didn't relocate enough, because it is trying to keep some semi-bad ones, or they are only bad when reading. If it is just settling at a speed and staying there, then it is probably successful. I don't know how reliable it is. I have found it to be 100% reliable in my testing though. But some/most disks lie to you on the "relocated sector count". And then remount the swap and change that kernel parameter back. sysctl kern.geom.debugflags=0 swapon /dev/da#p# Your relocated sector count: 5 Reallocated_Sector_Ct 0x0033 100 100 005Pre-fail Always - 0 However, this does not fix your disk. eg. If you have heads grinding the platter, you have dust flying around, and your disk will get worse. Be VERY careful using dd to write directly to disks. If you use the wrong slice, or you use the main device without slices and miscalculate, bad things happen. This is why that kernel parameter was set to stop 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" -- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.malo...@brockmann-consult.de Internet: http://www.brockmann-consult.de ___ 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 Quarterly Status Report October-December, 2011
FreeBSD Quarterly Status Report October-December, 2011
Introduction
This report covers FreeBSD-related projects between October and
December 2011. It is the last of the four reports planned for 2011.
This quarter was mainly devoted to polishing the bits for the next
major version of FreeBSD, 9.0, which was already successfully released
in the beginning of January 2012.
Thanks to all the reporters for the excellent work! This report
contains 32 entries and we hope you enjoy reading it.
Please note that the deadline for submissions covering the period
between January and March 2012 is April 15th, 2012.
__
Projects
* Auditdistd Project
* BSD-Licensed C++ Stack
* pfSense
User-land Programs
* Replacing the Regular Expression Code
* System Configuration Utilities
FreeBSD Team Reports
* FreeBSD Ports Management Team Status Report
* Release Engineering Team Status Report
* The FreeBSD Foundation Status Report
Kernel
* CAM Target Layer (CTL)
* FreeBSD No-IPv4 ("IPv6-Only") Support
* GEOM MULTIPATH Rewrite
* HDA Sound Driver (snd_hda) Improvements
* LSI Supported mps(4) SAS driver
* SCSI Direct Access Driver (da) Improvements
* Status Report for NFS
* The New CARP
Documentation
* A Tool to Check for Mistakes in Documentation -- igor
* The FreeBSD German Documentation Project
* The FreeBSD Japanese Documentation Project
Architectures
* FreeBSD/390
* FreeBSD/arm on Marvell Armada XP
* FreeBSD/powerpc on AppliedMicro APM86290
* FreeBSD/powerpc on Freescale QorIQ DPAA
* Improving Support for New Features in the Intel SandyBridge CPUs
Ports
* FreeBSD Haskell Ports
* FreeBSD Ruby Ports
* FreeBSD/GNOME
* FreeBSD/KDE
* Multimedia -- Watching/Recording Digital TV
* Perl Ports Testing
* Public FreeBSD Ports Development Infrastructure -- redports.org
* Up to Date X.Org Server
__
A Tool to Check for Mistakes in Documentation -- igor
URL: http://www.wonkity.com/~wblock/igor/
Contact: Warren Block
igor is a program that proofreads man pages, DocBook SGML source, and
other text files for many common mistakes.
Files are tested for spelling mistakes, repeated words, and white-space
problems. Man pages are also checked for minimal structure, and DocBook
SGML source files are checked for formatting and tag problems.
If you write or edit FreeBSD documentation, let igor help you check it
for correctness.
Open tasks:
1. Find a testing or parsing framework that can do a faster or better
job, or that can understand the state of DocBook tags.
2. Add more tests.
3. Improve speed.
__
Auditdistd Project
Contact: Pawel Jakub Dawidek
Current weakness of FreeBSD's Security Event Audit facility is that
audit records are stored locally and can be modified or removed by an
attacker after a system compromise.
The auditdistd will allow to reliably and securely distribute audit
trail files over TCP/IP network to remote system. In case of system
compromise it will enable administrators to analyze audit records in
trusted environment.
This project is sponsored by the FreeBSD Foundation and should be
completed by the end of February 2012.
__
BSD-Licensed C++ Stack
Contact: David Chisnall
Two new libraries, libc++ (providing a C++11 STL implementation) and
libcxxrt (providing an implementation of the C++ ABI specification)
have been added. This is enabled by adding WITH_LIBCPLUSPLUS=yes to
src.conf. It is not enabled by default because libc++ does not build
with the version of gcc in the base system and requires you to build
with clang.
Once it is built, you can select between using GNU libstdc++ and libc++
by adding -stdlib=libc++ or -stdlib=libstdc++ to your compile and link
flags (when building with clang).
If you are running head (or have a spare [virtual] machine you can try
it on) then please try building your C++ code with libc++ and let me
know of any failures, ideally with reduced test cases.
Open tasks:
1. Test ports with libc++. Hopefully most will Just Work., but others
may need patches or have a hard dependency on libstdc++.
2. Make libstdc++ dynamically link to libsupc++. This will allow us to
use libmap.conf to switch between libsupc++ and libcxxrt.
3. Enable building libc++ by default (hopefully in the 9.1 time-frame,
when clang becomes the default system compiler) and switch to using
libcxxrt instead of libsupc++ by default.
4. Lots more testing. Followed by even more testing.
5. Remov
Re: kernel: panic: softdep_sync_buf: Unknown type jnewblk
Hi :) On Thu, 26 Jan 2012 17:54:30 -0800 Jeremy Chadwick wrote: > I'll also point out, though the OP isn't using snapshots, that it's > confirmed use of snapshots on SU+J can result in a full filesystem hang. > Confirmation is from Kirk McKusick (author of SU and designer of SU+J): > > http://lists.freebsd.org/pipermail/freebsd-fs/2012-January/013429.html > > Something really needs to be done about this combination of problems. > > Since SU+J is the default choice for all UFS filesystems on 9.0-RELEASE, > the only solution I can think of is to send a massive announcement to > relevant mailing lists, AND put something on the freebsd.org home page > about these issues. The problem was analyzed but no immediate solution found. Therefor snapshots on filesystems with SU+J (but not SU alone) were disabled by Kirk McKusick in SVN r230250. The MFC to 9-STABLE has still to be done. Maybe this fix is a candidate for an errata notice / patch, distributed by freebsd-update? > For the snapshot issue, I believe not using SU+J (and only SU) works > around the problem, so possibly that would be the best choice of > recommendation at this time. Yes, snapshots with SU alone are working. > I urge key members of the community and (as always) kernel developers to > chime in here with advice. Something needs to be done, users need to be > made aware of these problems, and so on. Due to lack of time and not being the author of the rather complex code Kirk McKusick was not able to fix the problem. We're now waiting for Jeff Roberson to step up, but I was told that he is very busy and has no time too. > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | > > ___ > freebsd...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org" > -- Homepage: www.yamagi.org XMPP: yam...@yamagi.org GnuPG/GPG: 0xEFBCCBCB pgpu9XP6eQiPl.pgp Description: PGP signature
