newfs(8) parameters from dumpfs -m have bad -s value?
I have a requirement to be able to re-create a largish file system on occasion. The file system was created with some non-default newfs(8) parameters. Once I found about it, it seemed that the output of dumpfs -m would be ideal to use in the script that performs the analysis (if appropriate) re-creation. But I found that that output (in this case, at least) includes a rather bogus -s parameter. A circumvention is to interpose a sed(1) invocation to elide the parameter, but that seems a tad ... ugly (though admittedly effective). I'm running 7.1-RC1 on the systems in question. Here's the supporting evidence: We start with one of the file systems in question as it is supposed to be: pool10(7.1-RC1)[32] df -ki /dev/da1s1d Filesystem 1024-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/da1s1d 17027530304 1566532784 0% 2 2200463320% /b pool10(7.1-RC1)[33] Here's what dumpfs(8) says: pool10(7.1-RC1)[36] dumpfs -m /dev/da1s1d # newfs command for /dev/da1s1d (/dev/da1s1d) newfs -O 2 -U -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o time -s 879031908 /dev/da1s1d pool10(7.1-RC1)[37] I then unmount the file system re-create it naively: pool10(7.1-RC1)[37] umount /dev/da1s1d pool10(7.1-RC1)[38] dumpfs -m /dev/da1s1d | sh /dev/da1s1d: 429214.8MB (879031908 sectors) block size 16384, fragment size 2048 using 2336 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. with soft updates super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, ... 876523968, 876900320, 877276672, 877653024, 878029376, 878405728, 878782080 pool10(7.1-RC1)[39] df -ki /dev/da1s1d Filesystem 1024-blocks Used Avail Capacity iusedifree %iused Mounted on /dev/da1s1d 425686716 4 391631776 0%2 55017468 0% pool10(7.1-RC1)[40] The file system had been 1702753030 KB; it is now 425686716 KB -- 25% of its intended size. By eliding the -s parameter, we get: pool10(7.1-RC1)[40] dumpfs -m /b | sed -Ee 's/ -s [0-9]+ / /' | sh /dev/da1s1d: 1716859.2MB (3516127632 sectors) block size 16384, fragment size 2048 using 9343 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. with soft updates super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, ... 3513622432, 3513998784, 3514375136, 3514751488, 3515127840, 3515504192, 3515880544 pool10(7.1-RC1)[41] df -ki /dev/da1s1d Filesystem 1024-blocks Used Avail Capacity iusedifree %iused Mounted on /dev/da1s1d 1702753030 4 1566532784 0%2 220046332 0% pool10(7.1-RC1)[42] [Sorry about the long lines] Is dumpfs(8) actually behaving as expected (or correctly) in this case? Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpAT91NyuYhn.pgp Description: PGP signature
Re: Make world builderror on 7.1-BETA2 with latest cvsup
Hello Garret, Garrett Cooper wrote: On Jan 1, 2009, at 19:23, Mattias Björk mattias.bj...@sydnet.net wrote: Hello everybody, First of all, my bad if this get sent two times. I have a compile error/problem when building world. My uname -a output is: FreeBSD barabolaptop 7.1-BETA2 FreeBSD 7.1-BETA2 #0: Thu Dec 4 20:52:35 CET 2008 r...@barabolaptop:/usr/obj/usr/src/sys/BARABOLAPTOP i386 My make.conf looks like: # added by use.perl 2008-12-03 00:58:09 PERL_VER=5.8.8 PERL_VERSION=5.8.8 WRKDIRPREFIX=/var/tmp The options.h file in /usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/options.h Here are the output of options.h from pastebin: http://pastebin.com/m254dfedf When I run make -j1 buildworld i get the error is as following: http://pastebin.com/m57738677 I don't know much of programming (if any), but I have tried to change things in (remove OPT_w from both places) options.h and runned make -j1 -DNOCLEAN buildworld But that have not solve anything of this, perhaps some can shine some light on this or have I missed something trivial? I can build ports and so on without any problems. Thank you. Not enough data. Please send a full compressed version of the log to me. Thanks! No thank you, :) I will send it to you directly. -Garrett___ 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: Make world builderror on 7.1-BETA2 with latest cvsup
Hello Claus, Claus Guttesen wrote: I have a compile error/problem when building world. My uname -a output is: FreeBSD barabolaptop 7.1-BETA2 FreeBSD 7.1-BETA2 #0: Thu Dec 4 20:52:35 CET 2008 r...@barabolaptop:/usr/obj/usr/src/sys/BARABOLAPTOP i386 Sync the time on your computer and try the buildworld again. I have tried that several times, even removed /usr/src/* entirely and started from scratch. And tried a couple of other cvsup.XX.freebsd.org servers. Still no go Claus :( Any more suggestions ? Thanks so far. ___ 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 7.1 svn186551
Hi All! I have the question, why reverted the ICH10 support from 7.1? This is the svn commit: http://svnweb.freebsd.org/viewvc/base/releng/?pathrev=186551 What is the PR number of the base of this commit or what is the problem description? I have a motherboard with ich10r with 3 sata2 disc (hitachi) + 1 sata dvd-rw (samsung), without any problem. Sorry for bad spelling or english ___ 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
Update ports on 6.3 or update OS to 7.1(RC2) and update ports?
I have a machine where several of my installed applications are getting way behind. It is not a mission critical server, but I need it to be stable (I have all fairly old well supported hardware, nothing special). Since updating and rebuilding all the ports is pretty much mandatory for the upgrade to 7.x and I plan to take that path soon, would most people consider 7.1RC2 stable enough for a move now? The machine is a home server that provides several services on my network, but is rarely under any load. I know this is rather vague question, so I will be happy with any vague answers; just positive or negative experiences with well supported hardware (old Dell 8250 P4 3.0GHz 1.5GB 1066 RAMBUS). Thanks in advance, Tom Veldhouse ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.1 svn186551
On Fri, 2009-01-02 at 21:09 +0100, Oliver Pinter wrote: Hi All! I have the question, why reverted the ICH10 support from 7.1? This is the svn commit: http://svnweb.freebsd.org/viewvc/base/releng/?pathrev=186551 What is the PR number of the base of this commit or what is the problem description? I have a motherboard with ich10r with 3 sata2 disc (hitachi) + 1 sata dvd-rw (samsung), without any problem. Sorry for bad spelling or english Unfortunately most of the email traffic related to this was off-list. There was one message here on list from Greg Miller saying his system locked up and giving a date for when the problem got introduced which was between 7.1-RC1 and 7.1-RC2 so it had been a regression that snuck in while we were in the RC phase. It turned out the MFC that brought in support for that chip was pulling in pieces of ATA from head that had been intertwined with other work and it seemed likely the MFC wasn't complete - more of the ATA pieces from head would need to be pulled in to stabilize it. Since we were already so far behind on getting 7.1 out we opted to back out the change rather than try to work out what else needed to be MFCed (which would have definitely required RC3 if we tried to do that). Sorry, it will just need to wait for 7.3 (though hopefully this plus the extra stuff needed to stabilize it will work its way into 7-STABLE in the not too distant future). -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.1 svn186551
Thanks the problem description, then I revert the reverted patch in my local tree. I had a similar problem between 7.1-PRERELEASE and 7.1-RC1, it presentdes only 1 week long, under heavy load (csup / kernel compile) crashed the system, but after RC1 the system is very stable (more than 2 week uptime, and ooo3 and kde build, every day several times csup, etc etc..) On 1/2/09, Ken Smith kensm...@cse.buffalo.edu wrote: On Fri, 2009-01-02 at 21:09 +0100, Oliver Pinter wrote: Hi All! I have the question, why reverted the ICH10 support from 7.1? This is the svn commit: http://svnweb.freebsd.org/viewvc/base/releng/?pathrev=186551 What is the PR number of the base of this commit or what is the problem description? I have a motherboard with ich10r with 3 sata2 disc (hitachi) + 1 sata dvd-rw (samsung), without any problem. Sorry for bad spelling or english Unfortunately most of the email traffic related to this was off-list. There was one message here on list from Greg Miller saying his system locked up and giving a date for when the problem got introduced which was between 7.1-RC1 and 7.1-RC2 so it had been a regression that snuck in while we were in the RC phase. It turned out the MFC that brought in support for that chip was pulling in pieces of ATA from head that had been intertwined with other work and it seemed likely the MFC wasn't complete - more of the ATA pieces from head would need to be pulled in to stabilize it. Since we were already so far behind on getting 7.1 out we opted to back out the change rather than try to work out what else needed to be MFCed (which would have definitely required RC3 if we tried to do that). Sorry, it will just need to wait for 7.3 (though hopefully this plus the extra stuff needed to stabilize it will work its way into 7-STABLE in the not too distant future). -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | ___ 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: Update ports on 6.3 or update OS to 7.1(RC2) and update ports?
On Jan 2, 2009, at 12:32, Thomas T. Veldhouse veld...@gmail.com wrote: I have a machine where several of my installed applications are getting way behind. It is not a mission critical server, but I need it to be stable (I have all fairly old well supported hardware, nothing special). Since updating and rebuilding all the ports is pretty much mandatory for the upgrade to 7.x and I plan to take that path soon, would most people consider 7.1RC2 stable enough for a move now? The machine is a home server that provides several services on my network, but is rarely under any load. I know this is rather vague question, so I will be happy with any vague answers; just positive or negative experiences with well supported hardware (old Dell 8250 P4 3.0GHz 1.5GB 1066 RAMBUS). Thanks in advance, Tom Veldhouse Tom, Based on my experimentation, I'd say 7.1 rc2 is stable enough for your hardware. More bleeding edge hardware appears to be a problem with the rc version. Cheers, -Garrett ___ 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 world builderror on 7.1-BETA2 with latest cvsup
Hello again :) Claus Guttesen wrote: Hello Mattias. On Fri, Jan 2, 2009 at 9:04 PM, Mattias Björk mattias.bj...@sydnet.net wrote: Hello Claus, Claus Guttesen wrote: I have a compile error/problem when building world. My uname -a output is: FreeBSD barabolaptop 7.1-BETA2 FreeBSD 7.1-BETA2 #0: Thu Dec 4 20:52:35 CET 2008 r...@barabolaptop:/usr/obj/usr/src/sys/BARABOLAPTOP i386 Sync the time on your computer and try the buildworld again. I have tried that several times, even removed /usr/src/* entirely and started from scratch. And tried a couple of other cvsup.XX.freebsd.org servers. Still no go Claus :( Any more suggestions ? Thanks so far. Unfortunately not. :-/ The only times I've had problems recently building world was because the time on my computer was (way) incorrect. Well I don't think anything is incorrect on the computer, can build everything else fine and it goes on and on. You can try removing /usr/obj as well before doing a new buildworld. AFAIK you don't have to alter options.h to make a buildworld run smoothly. I have tried too make clean ; make clean ; make cleandir ; make cleandir and then rm -rf /usr/obj. Still the same problem I'm afraid. HTH. ___ 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
