freebsd-questions Digest, Vol 304, Issue 6
freebsd-ques...@freebsd.org
freebsd-...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
or, via email, send a message with subject or body 'help' to
freebsd-ques...@freebsd.org
You can reach the person managing the list at
freebsd-que...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-questions digest..."
Today's Topics:
1. Re: random FreeBSD panics (Anoop Kumar Narayanan)
2. Re: freebsd-8 support for dell R710 SATA raid-0 (Adam Vande More)
3. How to make "man" pages (Fbsd1)
4. Upgrading releases? (Slack-Moehrle)
5. Re: Upgrading releases? (Glen Barber)
6. Re: /boot.config (Fbsd1)
7. uname -a (alexus)
8. Re: uname -a (Jason)
9. Re: uname -a (Glen Barber)
10. Re: How to make "man" pages (Matthew Seaman)
11. Re: How to make "man" pages (Fbsd1)
12. Re: How to make "man" pages (Matthew Seaman)
13. Re: Copying mirrored partitions - will this work? (Mike Clarke)
14. Re: How to make "man" pages (Jerry)
15. Re: dd cloning slightly different disks (Christoph Kukulies)
16. Default labeling and space for rebuilding the kernel.
(Leon Me?ner)
17. Re: freebsd-8 support for dell R710 SATA raid-0 (krad)
18. mkuzip and/or geom_uzip changes? (Tim Judd)
19. Re: Copying mirrored partitions - will this work? (krad)
20. Re: /boot.config (krad)
21. Re: Setting firewall symbolic constants (Walter)
----------------------------------------------------------------------
Message: 1
Date: Wed, 31 Mar 2010 06:43:08 +0530
From: Anoop Kumar Narayanan <anoo...@gmail.com>
Subject: Re: random FreeBSD panics
To: freebsd-...@freebsd.org
Message-ID:
<7ff5545f1003301813o601...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Mar 31, 2010 at 2:33 AM, Paul B Mahol <one...@gmail.com> wrote:
> On 3/30/10, Anoop Kumar Narayanan <anoo...@gmail.com> wrote:
>> On Sun, Mar 28, 2010 at 5:33 PM, Gary Jennejohn
>> <gary.je...@freenet.de> wrote:
>>> On Sun, 28 Mar 2010 11:18:59 +0000
>>> Masoom Shaikh <masoom...@gmail.com> wrote:
>>>
>>>> On Sun, Mar 28, 2010 at 10:32 AM, Ivan Voras <ivo...@freebsd.org> wrote:
>>>> > Masoom Shaikh wrote:
>>>> >>
>>>> >> Hello List,
>>>> >>
>>>> >> I was a happy FreeBSD user, just before I installed FreeBSD8.0-RC1.
>>>> >> Since
>>>> >> then, system randomly just freezes, and there is no option other than
>>>> >> hard
>>>> >> boot. I guessed this will get solved in 8.0-RELEASE, but it was not :(
>>>> >
>>>> > I wild shot - did you try disabling superpages?
>>>> >
>>>> > _______________________________________________
>>>> > freebsd-...@freebsd.org mailing list
>>>> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>>> > To unsubscribe, send any mail to
>>>> > "freebsd-questi...@freebsd.org"
>>>> >
>>>>
>>>> umm, how do I do that ?
>>>>
>>>
>>> Add this to /boot/loader.conf
>>> vm.pmap.pg_ps_enabled="0"
>>
>> I keep getting RW errors while writing into an USB drive, wondering if
>> its the same problem is related to your reply ?
>> USB mass storage driver seems to be broken.
>
> Works for me.
>
>>
>> da0 at umass-sim0 bus 0 target 0 lun 0
>> da0: <Kingston DataTraveler 2.0 1.00> Removable Direct Access SCSI-2 device
>> da0: 40.000MB/s transfers
>> da0: 1940MB (3973120 512 byte sectors: 255H 63S/T 247C)
>> info: [drm] Num pipes: 2
>> info: [drm] Loading R300 Microcode
>> info: [drm] Num pipes: 2
>> g_vfs_done():da0s1[WRITE(offset=648923648, length=32768)]error = 5
>> g_vfs_done():da0s1[WRITE(offset=648956416, length=32768)]error = 5
>> g_vfs_done():da0s1[WRITE(offset=648989184, length=32768)]error = 5
>> g_vfs_done():da0s1[WRITE(offset=649021952, length=65536)]error = 5
>> g_vfs_done():da0s1[WRITE(offset=649087488, length=32768)]error = 5
>
> Are you sure that your device is not dead (weared out)?
>
That seem to have been the case. :P Ran a scan disk on windows and
fixed it. :) But this doesn't solve the FreeBSD 8.0 frequent crashes.
------------------------------
Message: 2
Date: Tue, 30 Mar 2010 19:13:35 -0600
From: Adam Vande More <amvan...@gmail.com>
Subject: Re: freebsd-8 support for dell R710 SATA raid-0
To: John <comp...@googlemail.com>
Cc: Varan Okul <vara...@hotmail.com>, kra...@googlemail.com,
freebsd-...@freebsd.org, freebsd-...@freebsd.org
Message-ID:
<6201873e1003301813o320...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Mar 30, 2010 at 6:56 PM, John <comp...@googlemail.com> wrote:
>
>
> Hi, thanks for your input.
>
> I have an idea. Would the answer be to install the OS to a SD card, boot
> from that then use GPT or ZFS to see the drive once the OS is installed?
>
> What i mean is, the disks are attached to the SATA raid card. if I don't
> select any disks in the raid, will they be seen by the OS? then I could
> just use zfs for raid functionality.
>
> Freebsd 8 sees the card, just not the disks. The server has a sd slot.
> Maybe this is what it's for?
> --
> John - comp dot john at googlemail dot com
> OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop
> GPG: 0xF08A33C5
>
Your best bet would be to configure the drives as JBOD and see if it detects
the disks. Post dmesg from that.
--
Adam Vande More
------------------------------
Message: 3
Date: Wed, 31 Mar 2010 11:00:15 +0800
From: Fbsd1 <fb...@a1poweruser.com>
Subject: How to make "man" pages
To: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <4BB2BABF...@a1poweruser.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Where can I find documentation on the procedure to create "man" pages
for a port?
------------------------------
Message: 4
Date: Tue, 30 Mar 2010 20:25:07 -0700 (PDT)
From: Slack-Moehrle <mailin...@mailnewsrss.com>
Subject: Upgrading releases?
To: freebsd-...@freebsd.org
Message-ID:
<2031098819.96.127000...@indie.theindiecompanyllc.com>
Content-Type: text/plain; charset=utf-8
Hi All,
I have a system with 8.0-RELEASE and I read that 8-STABLE has ZFS v14 (instead of v13)
I am trying:
# freebsd-update upgrade -r 8-STABLE
and it does not work. it tried 3 mirrors, all fail and nada.
Since I am new to FreeBSD, what am I obviously missing? Is there a place that states the releases? Is there an 8.1 or 8.2 out now that has even a new version of ZFS?
Best,
-Jason
------------------------------
Message: 5
Date: Tue, 30 Mar 2010 23:31:12 -0400
From: Glen Barber <glen.j...@gmail.com>
Subject: Re: Upgrading releases?
To: Slack-Moehrle <mailin...@mailnewsrss.com>
Cc: freebsd-...@freebsd.org
Message-ID: <20100331033...@orion.hsd1.pa.comcast.net>
Content-Type: text/plain; charset=us-ascii
Hi Jason,
Slack-Moehrle wrote:
> Hi All,
>
> I have a system with 8.0-RELEASE and I read that 8-STABLE has ZFS v14 (instead of v13)
>
> I am trying:
>
> # freebsd-update upgrade -r 8-STABLE
>
> and it does not work. it tried 3 mirrors, all fail and nada.
>
> Since I am new to FreeBSD, what am I obviously missing? Is there a place that states the releases? Is there an 8.1 or 8.2 out now that has even a new version of ZFS?
>
Have a look at the DESCRIPTION section of the freebsd-update(8) man page,
which explains why you cannot upgrade to -STABLE using this utility. If
you wish to upgrade from -RELEASE to -STABLE, the handbook covers the
proper source-based upgrade procedure.
Regards,
--
Glen Barber
------------------------------
Message: 6
Date: Wed, 31 Mar 2010 11:53:24 +0800
From: Fbsd1 <fb...@a1poweruser.com>
Subject: Re: /boot.config
To: Dan Nelson <dne...@allantgroup.com>
Cc: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <4BB2C734...@a1poweruser.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Dan Nelson wrote:
> In the last episode (Mar 30), Fbsd1 said:
>> During the boot process I want to change the device used to boot from.
>> From the default 0:ad(0,a)/boot/loader
>> to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick.
>>
>> Here is the problem, the bios have no option to boot from USB device. So
>> thinking let the bios point to first drive to start the boot process and
>> have a /boot.config file to redirect to booting from the USB stick. I am
>> assuming the '0' zero will mean the first USB device.
>>
>> Is there any command i can use to verify the single USB stick is the 0
>> device?
>
> If you boot DOS from a floppy, can you see the USB stick as B: or C: ? If
> not, then the BIOS probably has no USB support at all, and you'll need to
> put a small boot partition somewhere on your hard drive to pull the kernel
> from. 128MB is large enough for a /boot directory, and you can set
> vfs.root.mountfrom="ufs:/dev/da0s1a" in loader.conf to make it mount its
> root filesystem from the USB stick (since at that point the kernel has
> loaded its own USB drivers).
>
> If you do see the USB drive from a DOS boot floppy, try entering
> "1:da(0,a)?" at the boot block prompt and see if it lists the files in your
> USB filesystem. If it does, then "1:da(0,a)/boot/loader" should let you
> boot FreeBSD.
>
The USB stick is plugged in before booting. During boot I select option
6 from Freebsd menu to go direct to the loader prompt. I have ok on
command line. I enter
vfs.root.mountfrom="ufs:/dev/da0s1a" and get "not found" after hitting
enter key.
At the ok prompt I enter ? for list of available boot devices and only
have ad0 listed.
It seems the da0 device USB stick is not recognized yet.
------------------------------
Message: 7
Date: Wed, 31 Mar 2010 00:08:08 -0400
From: alexus <ale...@gmail.com>
Subject: uname -a
To: freebsd-...@freebsd.org
Message-ID:
<j2t6ae50c2d1003302108i5...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
su-3.2# uname -a
FreeBSD dd.alexus.org 7.3-RELEASE FreeBSD 7.3-RELEASE #13: Tue Mar 23
20:47:52 UTC 2010 XX...@XXXXX.XXX.:/usr/obj/usr/src/sys/GENERIC
amd64
su-3.2#
why is it showing up #13 here? back when I had 7.2-RELEASE-pX i've had
#12, I then did following:
rm -rf /usr/src
csup /usr/share/examples/cvsup/standard-supfile
cd /usr/src
make buildworld
make buildkernel
...
reboot
now it show shows 7.3 and #13, i thought if i get rid of /usr/src and
re-csup it it should reset to #1? or #0
------------------------------
Message: 8
Date: Tue, 30 Mar 2010 21:12:25 -0700
From: Jason <jhel...@e-e.com>
Subject: Re: uname -a
To: goo...@alexus.org
Cc: freebsd-...@freebsd.org
Message-ID: <2010033104...@Jason-Helfmans-MacBook-Pro.local>
Content-Type: text/plain; charset=us-ascii; format=flowed
On Wed, Mar 31, 2010 at 12:08:08AM -0400, alexus thus spake:
>su-3.2# uname -a
>FreeBSD dd.alexus.org 7.3-RELEASE FreeBSD 7.3-RELEASE #13: Tue Mar 23
>20:47:52 UTC 2010 XX...@XXXXX.XXX.:/usr/obj/usr/src/sys/GENERIC
>amd64
>su-3.2#
>
>why is it showing up #13 here? back when I had 7.2-RELEASE-pX i've had
>#12, I then did following:
>
>rm -rf /usr/src
>csup /usr/share/examples/cvsup/standard-supfile
>cd /usr/src
>make buildworld
>make buildkernel
>...
>reboot
>now it show shows 7.3 and #13, i thought if i get rid of /usr/src and
>re-csup it it should reset to #1? or #0
>
Did you perform a 'make installkernel' ?
>
>
>
>--
>http://alexus.org/
>_______________________________________________
>freebsd-...@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"
>
--
Jason Helfman
System Administrator
experts-exchange.com
http://www.experts-exchange.com/M_4830110.html
------------------------------
Message: 9
Date: Wed, 31 Mar 2010 00:13:21 -0400
From: Glen Barber <glen.j...@gmail.com>
Subject: Re: uname -a
To: goo...@alexus.org
Cc: freebsd-...@freebsd.org
Message-ID: <20100331041...@orion.hsd1.pa.comcast.net>
Content-Type: text/plain; charset=us-ascii
Hi,
alexus wrote:
> su-3.2# uname -a
> FreeBSD dd.alexus.org 7.3-RELEASE FreeBSD 7.3-RELEASE #13: Tue Mar 23
> 20:47:52 UTC 2010 XX...@XXXXX.XXX.:/usr/obj/usr/src/sys/GENERIC
> amd64
> su-3.2#
>
> why is it showing up #13 here? back when I had 7.2-RELEASE-pX i've had
> #12, I then did following:
>
> rm -rf /usr/src
> csup /usr/share/examples/cvsup/standard-supfile
> cd /usr/src
> make buildworld
> make buildkernel
> ...
> reboot
> now it show shows 7.3 and #13, i thought if i get rid of /usr/src and
> re-csup it it should reset to #1? or #0
>
The kernel version is incremented from /usr/obj, not /usr/src. To revert
it to "#0", remove /usr/obj.
Regards,
--
Glen Barber
------------------------------
Message: 10
Date: Wed, 31 Mar 2010 08:25:51 +0100
From: Matthew Seaman <m.se...@infracaninophile.co.uk>
Subject: Re: How to make "man" pages
To: Fbsd1 <fb...@a1poweruser.com>
Cc: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <4BB2F8FF...@infracaninophile.co.uk>
Content-Type: text/plain; charset=UTF-8
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 31/03/2010 04:00:15, Fbsd1 wrote:
> Where can I find documentation on the procedure to create "man" pages
> for a port?
If you want to write a man page from scratch, probably the best way to
get started is to just copy a man page from the base system and edit it
to taste. See groff(1) for documentation on the command used to format
man pages from source, and groff_mdoc(7) for details on the groff macro
syntax. groff+mdoc might be a markup language, but it's nothing at all
like HTML.
If you're after how to install man pages for a port, then look at:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-manpages.html
Note that the MANX and other ports Macros only affect the pkg-list and
compressing the man pages /after/ installation. You'll still have to put
in some code to copy your self-written man page into place.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuy+P8ACgkQ8Mjk52CukIxcggCeLR3OcpdwZ/OZGZv623DawCC9
E+4AoJNMvoINM9xkL2CdYBwz/ozPnAgK
=qVD0
-----END PGP SIGNATURE-----
------------------------------
Message: 11
Date: Wed, 31 Mar 2010 15:54:25 +0800
From: Fbsd1 <fb...@a1poweruser.com>
Subject: Re: How to make "man" pages
To: Matthew Seaman <m.se...@infracaninophile.co.uk>
Cc: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <4BB2FFB1...@a1poweruser.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
>> On 31/03/2010 04:00:15, Fbsd1 wrote:
>> Where can I find documentation on the procedure to create "man" pages
>> for a port?
>
> If you want to write a man page from scratch, probably the best way to
> get started is to just copy a man page from the base system and edit it
> to taste. See groff(1) for documentation on the command used to format
> man pages from source, and groff_mdoc(7) for details on the groff macro
> syntax. groff+mdoc might be a markup language, but it's nothing at all
> like HTML.
>
> If you're after how to install man pages for a port, then look at:
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-manpages.html
>
> Note that the MANX and other ports Macros only affect the pkg-list and
> compressing the man pages /after/ installation. You'll still have to put
> in some code to copy your self-written man page into place.
>
> Cheers,
>
> Matthew
>
OK i want to write a man page from scratch. So lets say i want to use
/usr/share/man/man2/jail.2.gz as my starting sample. How do I convert
this .gz file to a plain text file so I can edit it with ee? And how do
I turn the edited text file back in to a man page .gz file?
------------------------------
Message: 12
Date: Wed, 31 Mar 2010 10:20:45 +0100
From: Matthew Seaman <m.se...@infracaninophile.co.uk>
Subject: Re: How to make "man" pages
To: Fbsd1 <fb...@a1poweruser.com>
Cc: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <4BB313ED...@infracaninophile.co.uk>
Content-Type: text/plain; charset=UTF-8
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 31/03/2010 08:54:25, Fbsd1 wrote:
> OK i want to write a man page from scratch. So lets say i want to use
> /usr/share/man/man2/jail.2.gz as my starting sample. How do I convert
> this .gz file to a plain text file so I can edit it with ee?
% cp /usr/share/man/man2/jail.2.gz .
% gunzip jail.2.gz
% mv jail.2 myname.2
% ee myname.2
> And how do
> I turn the edited text file back in to a man page .gz file?
To compress the groff source:
% gzip myname.2
To render the groff source as ascii text (what the man(1) command does):
% groff -mdoc -Tascii myname.2 | less
or
% gzcat myname.2.gz | groff -mdoc -Tascii | less
In general though, you should keep the man page source uncompressed
while you're working on it and within the port; install it uncompressed
and leave it to the ports machinery to compress it after installation.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuzE+0ACgkQ8Mjk52CukIx6VgCfV9R1LOrqcjzlnwSEMNHAT/Ys
iOEAniohL9mC7ehGZXKub+9RHKmI87px
=fhC7
-----END PGP SIGNATURE-----
------------------------------
Message: 13
Date: Wed, 31 Mar 2010 10:22:43 +0100
From: Mike Clarke <jmc-fr...@milibyte.co.uk>
Subject: Re: Copying mirrored partitions - will this work?
To: freebsd-...@freebsd.org
Message-ID: <201003311022.44...@milibyte.co.uk>
Content-Type: text/plain; charset="iso-8859-1"
On Saturday 20 March 2010, Mike Clarke wrote:
> I'm currently running 8.0-RELEASE and am considering experimenting
> with 8.0-STABLE. I'd like to preserve my existing system in case
> things go pear-shaped so I'll copy the entire system onto a spare
> slice and then use csup to upgrade the copy to STABLE. Normally I'd
> go through the steps of bsdlabel, newfs and then dump|restore to
> create the copy but I'm wondering if I can take advantage of my
> recently created gmirror to cut down the work.
>
> I have two 500GB disks, /dev/ad4 and /dev/ad8, each partitioned into
> 4 slices of 88, 88, 42 and 259GB. My system is installed on the first
> slices (ad4s1 and ad8s1) which are mirrored as /dev/mirror/gm0. The
> second slices (ad4s2 and ad8s2) are currently unused. My thoughts are
> to temporarily add ad4s2 into gm0 with "gmirror insert gm0 ad4s2" and
> wait for the mirror to synchronise. I should then be able to remove
> the temporary addition with "gmirror remove gm0 /dev/ad4s2" at which
> point ad4s2 should be a duplicate of the original system and I can
> then go ahead and create a new mirror with "gmirror label -b load gm1
> ad4s2" and "gmirror insert gm1 ad8s2". After editing /etc/fstab in
> the new mirror to use gm1 instead of gm0 I should then be able to
> boot into the system on slice 2 and upgrade it to STABLE while still
> keeping my original system to fall back to if required.
>
> Is this approach of moving disks from one mirror to another workable,
> or have I missed something that would lead me into deep trouble? I
> don't mind unduly if I make a mess of the second slice and have to
> start again but I don't want to lose the contents of my original
> system on slice 1.
I decided to give it a try and the process went through very smoothly.
It was much less tedious than bsdlabel -> newfs -> dump|restore, and
quicker too. The mirror synchronised at a bit over 100 MB/sec but dump|
restore only gave me about 10 MB/sec.
The system has now been running for a bit over a week without any
problems with either the original or cloned slices so I'm quite
confident that things are OK.
--
Mike Clarke
------------------------------
Message: 14
Date: Wed, 31 Mar 2010 05:34:11 -0400
From: Jerry <freebs...@seibercom.net>
Subject: Re: How to make "man" pages
To: freebsd-...@freebsd.org
Message-ID: <20100331053...@scorpio.seibercom.net>
Content-Type: text/plain; charset=UTF-8
On Wed, 31 Mar 2010 15:54:25 +0800, Fbsd1 <fb...@a1poweruser.com>
articulated:
>
> >> On 31/03/2010 04:00:15, Fbsd1 wrote:
> >> Where can I find documentation on the procedure to create "man"
> >> pages for a port?
> >
> > If you want to write a man page from scratch, probably the best way
> > to get started is to just copy a man page from the base system and
> > edit it to taste. See groff(1) for documentation on the command
> > used to format man pages from source, and groff_mdoc(7) for details
> > on the groff macro syntax. groff+mdoc might be a markup language,
> > but it's nothing at all like HTML.
> >
> > If you're after how to install man pages for a port, then look at:
> >
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-manpages.html
> >
> > Note that the MANX and other ports Macros only affect the pkg-list
> > and compressing the man pages /after/ installation. You'll still
> > have to put in some code to copy your self-written man page into
> > place.
> >
> > Cheers,
> >
> > Matthew
> >
> OK i want to write a man page from scratch. So lets say i want to use
> /usr/share/man/man2/jail.2.gz as my starting sample. How do I convert
> this .gz file to a plain text file so I can edit it with ee? And how
> do I turn the edited text file back in to a man page .gz file?
If you visit this URL:
<http://www.tldp.org/LDP/abs/html/writingscripts.html> you will see
links to various scripts. One of them is for creating 'man' pages:
<http://www.tldp.org/LDP/abs/html/contributed-scripts.html#MANED>
You might want to investigate its usefulness for your project.
--
Jerry
FreeBS...@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
FORTUNE REMEMBERS THE GREAT MOTHERS: #5
"And, and, and, and, but, but, but, but!"
Mrs. Janice Markowsky, April 8, 1965
------------------------------
Message: 15
Date: Wed, 31 Mar 2010 12:20:20 +0200
From: Christoph Kukulies <ku...@kukulies.org>
Subject: Re: dd cloning slightly different disks
To: Peter Steele <pst...@maxiscale.com>
Cc: "freebsd-...@freebsd.org" <freebsd-...@freebsd.org>
Message-ID: <4BB321E4...@kukulies.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thanks, Peter and all others. Indeed, in contrary to the expected, I
went into my office this morning, swapped the
HD against the SSD, and was able to boot both FreeBSD, Windows without a
hitch or any other tweaking.
The dd over USB 2.0 to the SSD from the WD hard disk took 21261 s
(nearly 6 hours)
I would possibly have had better results if I had both disks connected
to a SATA controller
and did the dd there, but so what, I'm there happily.
Thanks for sharing.
--
Christoph
Will post bonnie results later.
Peter Steele schrieb:
> Theoretically, doing a straight dd copy of one disk to another and then swapping in that disk should work. I've done it, with no other tweaking needed. I've never done it with mixed OS instances on the same disk, or for that matter with a solid state drive. You'll lose the trailing 12GB of your disk, although you might be able to expand the last partition of whatever OS uses it to include this lost space....
>
> -----Original Message-----
> From: owner-freeb...@freebsd.org [mailto:owner-freeb...@freebsd.org] On Behalf Of Christoph Kukulies
> Sent: Tuesday, March 30, 2010 8:48 AM
> To: freebsd-...@freebsd.org
> Subject: dd cloning slightly different disks
>
> Though not 100% FreeBSD centric, my question, I know that disk partitioning experts are around here.
> My noteook HD is a WD 5000BEVT, (500GB). Today I bought a Kingston SDnowV+ Solid State drive, 512GB, with the intention to make my notebook a bit faster. It's an Intel Core 2 Duo,
> 7400 CPU.
>
> The WD disk shows as having 976773168 sectors (500108 MB), the SSD has 1000215216 sectors (512110 MB).
>
> At the moment I'm copying (dd) from the WD internal disk to the SSD which I had put into an external SATA Icybox.
>
> I'm hoping to be able to use my FreeBSD and Windows partitions afterwards somehow, possibly with some geometry tweaking or what. Due to the different disk geometry I'm expecting that the partition table entries will be wrong.
>
> Any clues how I should proceed when the copy will be done in 7 hours or so? (20MB/s is the transfer rate I got from a short test that I did before starting the big copy).
>
> --
> Christoph
>
------------------------------
Message: 16
Date: Wed, 31 Mar 2010 12:26:00 +0200
From: Leon Me?ner <l.me...@physik.tu-berlin.de>
Subject: Default labeling and space for rebuilding the kernel.
To: freebsd-...@freebsd.org
Message-ID: <20100331102...@emmi.physik-pool.tu-berlin.de>
Content-Type: text/plain; charset="us-ascii"
Hi,
if one uses the default labeling with current installer it is not
possible to rebuild the kernel (GENERIC). It fails on installing the wlan.ko.
Isn't that wrong somehow ?
===> wi (install)
install -o root -g wheel -m 555 if_wi.ko /boot/kernel
install -o root -g wheel -m 555 if_wi.ko.symbols /boot/kernel
===> wlan (install)
install -o root -g wheel -m 555 wlan.ko /boot/kernel
install -o root -g wheel -m 555 wlan.ko.symbols /boot/kernel
/: write failed, filesystem is full
install: /boot/kernel/wlan.ko.symbols: No space left on device
*** Error code 71
Stop in /usr/src/sys/modules/wlan.
*** Error code 1
regards,
Leon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20100331/e261a84c/attachment-0001.pgp
------------------------------
Message: 17
Date: Wed, 31 Mar 2010 11:56:06 +0100
From: krad <kra...@googlemail.com>
Subject: Re: freebsd-8 support for dell R710 SATA raid-0
To: Adam Vande More <amvan...@gmail.com>
Cc: John <comp...@googlemail.com>, freebsd-...@freebsd.org,
freebsd-...@freebsd.org, Varan Okul <vara...@hotmail.com>
Message-ID:
<d36406631003310356m436...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 31 March 2010 02:13, Adam Vande More <amvan...@gmail.com> wrote:
> On Tue, Mar 30, 2010 at 6:56 PM, John <comp...@googlemail.com> wrote:
>
>>
>>
>> Hi, thanks for your input.
>>
>> I have an idea. Would the answer be to install the OS to a SD card, boot
>> from that then use GPT or ZFS to see the drive once the OS is installed?
>>
>> What i mean is, the disks are attached to the SATA raid card. if I don't
>> select any disks in the raid, will they be seen by the OS? then I could
>> just use zfs for raid functionality.
>>
>> Freebsd 8 sees the card, just not the disks. The server has a sd slot.
>> Maybe this is what it's for?
>> --
>> John - comp dot john at googlemail dot com
>> OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop
>> GPG: 0xF08A33C5
>>
>
> Your best bet would be to configure the drives as JBOD and see if it
> detects the disks. Post dmesg from that.
>
> --
> Adam Vande More
>
we are testing one at work at the moment. I think its a driver issue. We are
looking at either putting in a perc card or swapping it for the next chasis.
------------------------------
Message: 18
Date: Wed, 31 Mar 2010 04:59:52 -0600
From: Tim Judd <taj...@gmail.com>
Subject: mkuzip and/or geom_uzip changes?
To: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID:
<x2lade45ae91003310359qa...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi All,
Just starting to see if I can find other reports. You all probably
have had the "more than one pair of eyes looking at a thing is better
than my eyes alone." This is why I'm writing now, as I'm starting the
discovery.
Let me background this a little bit. I only started looking into this
because mkuzip and it's counterpart, geom_uzip are throwing errors on
FreeBSD8 i386
scenario (/etc/src.conf in effect, removing *LOTS* of stuff with knobs):
make DESTDIR=/home/small8 installworld installkernel distribution
mv /home/small8/boot /home/small8-boot/
makefs -t ffs /home/small8/usr.img /home/small8/usr/
mkuzip -o /home/small8/usr.uzip /home/small8/usr.img [*]
chflags -R noschg /home/small8/usr/*
rm -rf /home/small8/usr/* /home/small8/usr.img
ee /home/small8/etc/rc.d/mountcritlocal
[**]
makefs -t ffs /home/small8-boot/mfsroot /home/small8/
gzip --best /home/small8-boot/mfsroot
ee /home/small8-boot/boot/loader.conf
[***]
rm /home/small8-boot/boot/kernel/*.symbols
gzip --best /home/small8-boot/boot/kernel/kernel
mkisofs -U -J -r -V "FreeBSD8" -b boot/cdboot -no-emul-boot
-iso-level 4 -o /home/small8.iso /home/small8-boot/
[*]: mkuzip inserts a script header that is broken. module name it's
searching for may have been renamed?
[**]: Edited mountcritlocal to mount the usr.uzip file as by using the
above script header, throws errors
[***]: added zlib and geom_uzip modules to load to the boot image, to
satisfy the script header's requirements.
OK, the above scenario creates about a 33MB usr.uzip, and a 68MB iso.
Small enough to apparently fit into the undocumented 50 or 100MB size
limit of mfs_root module
The problem:
mkuzip generates a few lines as a script in the head of the
resulting *.uzip file. Two problems...
1) the module it queries for is geom_uzip (kldstat -m $m), but
FreeBSD8 names the geom_uzip module (i guess, internally) as g_uzip.
mkuzip's generated image will never find the module if they're not
named the same.
2) even with geom_uzip module and it's dependency zlib loaded, i don't
get a mdconfig node '/dev/md?.uzip' to appear.
It's been forever since I touched uzip, so I have to ask.
Looking at the cvsweb, (as a bonus question, what's the svn website
address to look at source files?) mkuzip program last modified 3 years
(2 months for the Makefile), geom_uzip module Makefile last modified 4
years ago.
3-4 years yield a median FreeBSD version 6.2. Have we broken
something in 7 or 8?
The request:
Is it a PEBKAC? ID 10T error? Duplicatable?
I'm gonna research what I can, when I can. I would expect to see
something pop up clearly if it is a regression. Can I ask you all to
use your eyes or past knowledge if something is broken?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: src.conf
Type: application/octet-stream
Size: 1028 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20100331/090756f0/src-0001.obj
------------------------------
Message: 19
Date: Wed, 31 Mar 2010 12:05:44 +0100
From: krad <kra...@googlemail.com>
Subject: Re: Copying mirrored partitions - will this work?
To: Mike Clarke <jmc-fr...@milibyte.co.uk>
Cc: freebsd-...@freebsd.org
Message-ID:
<d36406631003310405i3e3...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 31 March 2010 10:22, Mike Clarke <jmc-fr...@milibyte.co.uk> wrote:
> On Saturday 20 March 2010, Mike Clarke wrote:
>
> > I'm currently running 8.0-RELEASE and am considering experimenting
> > with 8.0-STABLE. I'd like to preserve my existing system in case
> > things go pear-shaped so I'll copy the entire system onto a spare
> > slice and then use csup to upgrade the copy to STABLE. Normally I'd
> > go through the steps of bsdlabel, newfs and then dump|restore to
> > create the copy but I'm wondering if I can take advantage of my
> > recently created gmirror to cut down the work.
> >
> > I have two 500GB disks, /dev/ad4 and /dev/ad8, each partitioned into
> > 4 slices of 88, 88, 42 and 259GB. My system is installed on the first
> > slices (ad4s1 and ad8s1) which are mirrored as /dev/mirror/gm0. The
> > second slices (ad4s2 and ad8s2) are currently unused. My thoughts are
> > to temporarily add ad4s2 into gm0 with "gmirror insert gm0 ad4s2" and
> > wait for the mirror to synchronise. I should then be able to remove
> > the temporary addition with "gmirror remove gm0 /dev/ad4s2" at which
> > point ad4s2 should be a duplicate of the original system and I can
> > then go ahead and create a new mirror with "gmirror label -b load gm1
> > ad4s2" and "gmirror insert gm1 ad8s2". After editing /etc/fstab in
> > the new mirror to use gm1 instead of gm0 I should then be able to
> > boot into the system on slice 2 and upgrade it to STABLE while still
> > keeping my original system to fall back to if required.
> >
> > Is this approach of moving disks from one mirror to another workable,
> > or have I missed something that would lead me into deep trouble? I
> > don't mind unduly if I make a mess of the second slice and have to
> > start again but I don't want to lose the contents of my original
> > system on slice 1.
>
> I decided to give it a try and the process went through very smoothly.
> It was much less tedious than bsdlabel -> newfs -> dump|restore, and
> quicker too. The mirror synchronised at a bit over 100 MB/sec but dump|
> restore only gave me about 10 MB/sec.
>
> The system has now been running for a bit over a week without any
> problems with either the original or cloned slices so I'm quite
> confident that things are OK.
>
> --
> Mike Clarke
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questi...@freebsd.org"
>
ive cloned many systems in this way before, and it does work. Not just
gmirror two, it should work with any mirroring, hardware or software. One
thing to remember though is that it works at the block level. Therefore if
the drive if very big with a small % of data on it might be quicker to copy
it manually.
There is always an exception though. If you are using zfs, then only the
data on the drive is copied. This is because zfs works at block, and file
system levels, and therefore is aware of what is allocated on the disks.
One thing about your dump/restore speed. Did you play around with larger
block sizes? Increasing it should give you better throughput.
------------------------------
Message: 20
Date: Wed, 31 Mar 2010 12:08:36 +0100
From: krad <kra...@googlemail.com>
Subject: Re: /boot.config
To: Fbsd1 <fb...@a1poweruser.com>
Cc: Dan Nelson <dne...@allantgroup.com>, FreeBSD Questions
<freebsd-...@freebsd.org>
Message-ID:
<d36406631003310408u430...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 31 March 2010 04:53, Fbsd1 <fb...@a1poweruser.com> wrote:
> Dan Nelson wrote:
>
>> In the last episode (Mar 30), Fbsd1 said:
>>
>>> During the boot process I want to change the device used to boot from.
>>> From the default 0:ad(0,a)/boot/loader
>>> to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick.
>>>
>>> Here is the problem, the bios have no option to boot from USB device. So
>>> thinking let the bios point to first drive to start the boot process and
>>> have a /boot.config file to redirect to booting from the USB stick. I am
>>> assuming the '0' zero will mean the first USB device.
>>>
>>> Is there any command i can use to verify the single USB stick is the 0
>>> device?
>>>
>>
>> If you boot DOS from a floppy, can you see the USB stick as B: or C: ? If
>> not, then the BIOS probably has no USB support at all, and you'll need to
>> put a small boot partition somewhere on your hard drive to pull the kernel
>> from. 128MB is large enough for a /boot directory, and you can set
>> vfs.root.mountfrom="ufs:/dev/da0s1a" in loader.conf to make it mount its
>> root filesystem from the USB stick (since at that point the kernel has
>> loaded its own USB drivers).
>>
>> If you do see the USB drive from a DOS boot floppy, try entering
>> "1:da(0,a)?" at the boot block prompt and see if it lists the files in
>> your
>> USB filesystem. If it does, then "1:da(0,a)/boot/loader" should let you
>> boot FreeBSD.
>>
>>
>
> The USB stick is plugged in before booting. During boot I select option 6
> from Freebsd menu to go direct to the loader prompt. I have ok on command
> line. I enter
> vfs.root.mountfrom="ufs:/dev/da0s1a" and get "not found" after hitting
> enter key.
> At the ok prompt I enter ? for list of available boot devices and only have
> ad0 listed.
>
> It seems the da0 device USB stick is not recognized yet.
>
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questi...@freebsd.org"
>
try legacy usb in the bios, it may help
------------------------------
Message: 21
Date: Wed, 31 Mar 2010 06:30:28 -0500
From: Walter <walt...@earthlink.net>
Subject: Re: Setting firewall symbolic constants
To: Bob Hall <rjh...@gmail.com>
Cc: Questions <freebsd-...@freebsd.org>
Message-ID: <4BB33254...@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Bob Hall wrote:
>I use
> onet=`ifconfig rl0 | grep "inet " | awk '{print $6}'`
>where rl0 is the outward facing NIC on this gateway.
>
>
Thanks. But I think I like a method which allows me to get the
device names also, to allow a 'hands-off' configuring of the fw.
I'll keep your code for future reference, tho.
------------------------------
End of freebsd-questions Digest, Vol 304, Issue 6
*************************************************