Re: FYI: merging TCP, UDP, netisr locking changes
On Tue, 24 May 2011, Robert Watson wrote: Over the next few days, I will be merging a number of TCP-related locking changes, as well as changes to various network stack infrastructure bits, such as the netisr implementation. The goal, generally, has been to move us in the direction of supporting more clear CPU affinity for network flows, the ability to program filters in network cards to support those affinities explicitly, and elimination of cache line contention (whether by locks, stats, etc) during high-volume parallel steady-state TCP load, with ancillary benefits (hopefully) for UDP and other protocols. This has implied non-trivial changes to our inpcb locking model, netisr code, etc. Detailed information will appear in commit messages as I go; some elements, such a programming of card filters based on setting TCP socket options, are very much a work in progress. Obviously, there are no bugs in this code at all. However, if they are, they might manifest as network problems, new WITNESS warnings, etc, and network stack exercise + reports would be greatly appreciated! This work has been sponsored by Juniper Networks. Thanks also to Bjoern Zeeb, who has been reviewing changes! After a series of smaller commits, I've just merged some initial decomposition of the pcbinfo lock into an additional pcbhash lock, which changes lock ordering and lookup with respect to inpcbs significantly (r222488; commit message below). I expect there to be some initial instability as people shake out edge cases I didn't bump into in my testing. Please report bugs to current@, and I'll pick them up there! Robert N. M. Watson University of Cambridge Computer Laboratory Decompose the current single inpcbinfo lock into two locks: - The existing ipi_lock continues to protect the global inpcb list and inpcb counter. This lock is now relegated to a small number of allocation and free operations, and occasional operations that walk all connections (including, awkwardly, certain UDP multicast receive operations -- something to revisit). - A new ipi_hash_lock protects the two inpcbinfo hash tables for looking up connections and bound sockets, manipulated using new INP_HASH_*() macros. This lock, combined with inpcb locks, protects the 4-tuple address space. Unlike the current ipi_lock, ipi_hash_lock follows the individual inpcb connection locks, so may be acquired while manipulating a connection on which a lock is already held, avoiding the need to acquire the inpcbinfo lock preemptively when a binding change might later be required. As a result, however, lookup operations necessarily go through a reference acquire while holding the lookup lock, later acquiring an inpcb lock -- if required. A new function in_pcblookup() looks up connections, and accepts flags indicating how to return the inpcb. Due to lock order changes, callers no longer need acquire locks before performing a lookup: the lookup routine will acquire the ipi_hash_lock as needed. In the future, it will also be able to use alternative lookup and locking strategies transparently to callers, such as pcbgroup lookup. New lookup flags are, supplementing the existing INPLOOKUP_WILDCARD flag: INPLOOKUP_RLOCKPCB - Acquire a read lock on the returned inpcb Decompose the current single inpcbinfo lock into two locks: - The existing ipi_lock continues to protect the global inpcb list and inpcb counter. This lock is now relegated to a small number of allocation and free operations, and occasional operations that walk all connections (including, awkwardly, certain UDP multicast receive operations -- something to revisit). - A new ipi_hash_lock protects the two inpcbinfo hash tables for looking up connections and bound sockets, manipulated using new INP_HASH_*() macros. This lock, combined with inpcb locks, protects the 4-tuple address space. Unlike the current ipi_lock, ipi_hash_lock follows the individual inpcb connection locks, so may be acquired while manipulating a connection on which a lock is already held, avoiding the need to acquire the inpcbinfo lock preemptively when a binding change might later be required. As a result, however, lookup operations necessarily go through a reference acquire while holding the lookup lock, later acquiring an inpcb lock -- if required. A new function in_pcblookup() looks up connections, and accepts flags indicating how to return the inpcb. Due to lock order changes, callers no longer need acquire locks before performing a lookup: the lookup routine will acquire the ipi_hash_lock as needed. In the future, it will also be able to use alternative lookup and locking strategies transparently to callers, such as pcbgroup lookup. New lookup flags are, supplementing the existing INPLOOKUP_WILDCARD flag: INPLOOKUP_RLOCKPCB - Acquire a read lock on the returned inpcb INPLOOKUP_WLOCKPCB - Acquire a write lock on the returned inpcb Callers must pass exactly one
Re: ZFS install from -CURRENT snapshot
--As of May 29, 2011 9:10:57 AM -0400, George Kontostanos, freebsd-current@freebsd.org is alleged to have said: --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to have said: The new bsdinstall has a different layout so the previous guides don't work. I have prepared one that works for recent 9-Current at : http://www.aisecure.net/?p=132; --As for the rest, it is mine. Thanks, that's about what I expected the install procedure to be at this point. Nice to have the reminder about the zpool.cache. (Do I have to use the Live CD mode? Can I use shell mode instead?) --As for the rest, it is mine. Ok, I've tried shell mode and live CD mode. I've re-partitioned my disks several different ways. Nothing gets me a system that will actually boot. Or even recognize that there is an OS loaded anywhere. Help? (My preferred partitioning: ada1: 1 freebsd-boot 2 freebsd-swap 8G 3 freebsd-zfs 4G (zil) 4 freebsd-zfs 17G (cache) ada0: Managed by ZFS, ~250G Main filesystem. This takes advantage of the mSATA SSD in ada1.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
Could you please explain where did you actually got stacked ?
Have you installed the OS by :
for file in base.txz lib32.txz kernel.txz doc.txz ports.txz src.txz;
do (cat $file | tar --unlink -xpJf - -C ${DESTDIR:-/}); done
Did you copy zpool.cache ?
On Mon, May 30, 2011 at 6:01 PM, Daniel Staal dst...@usa.net wrote:
--As of May 29, 2011 9:10:57 AM -0400, George Kontostanos,
freebsd-current@freebsd.org is alleged to have said:
--As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to
have said:
The new bsdinstall has a different layout so the previous guides don't
work. I have prepared one that works for recent 9-Current at :
http://www.aisecure.net/?p=132;
--As for the rest, it is mine.
Thanks, that's about what I expected the install procedure to be at this
point. Nice to have the reminder about the zpool.cache. (Do I have to
use the Live CD mode? Can I use shell mode instead?)
--As for the rest, it is mine.
Ok, I've tried shell mode and live CD mode. I've re-partitioned my disks
several different ways.
Nothing gets me a system that will actually boot. Or even recognize that
there is an OS loaded anywhere. Help?
(My preferred partitioning:
ada1:
1 freebsd-boot
2 freebsd-swap 8G
3 freebsd-zfs 4G (zil)
4 freebsd-zfs 17G (cache)
ada0: Managed by ZFS, ~250G Main filesystem.
This takes advantage of the mSATA SSD in ada1.)
Daniel T. Staal
---
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
--
George Kontostanos
aisecure.net http://www.aisecure.net
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
--As of May 30, 2011 6:11:19 PM +0300, George Kontostanos is alleged to
have said:
Could you please explain where did you actually got stacked ?
Have you installed the OS by :
for file in base.txz lib32.txz kernel.txz doc.txz ports.txz src.txz;
do (cat $file | tar --unlink -xpJf - -C ${DESTDIR:-/}); done
Did you copy zpool.cache ?
--As for the rest, it is mine.
Did both of those. A half-dozen times. ;)
The machine fails to find a bootable drive. It searches, tries PXE booting
a couple of times, then dumps me into the BIOS's boot drive chooser. I can
try selecting either of the internal drives at that point if I wish, and it
will just loop back to there.
Daniel T. Staal
---
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
I suppose that you didn't forget to add a boot code to your boot disk(s) ?
gpart bootcode -b boot/pmbr -p boot/gptzfsboot -i 1 ada0
On Mon, May 30, 2011 at 6:25 PM, Daniel Staal dst...@usa.net wrote:
--As of May 30, 2011 6:11:19 PM +0300, George Kontostanos is alleged to
have said:
Could you please explain where did you actually got stacked ?
Have you installed the OS by :
for file in base.txz lib32.txz kernel.txz doc.txz ports.txz src.txz;
do (cat $file | tar --unlink -xpJf - -C ${DESTDIR:-/}); done
Did you copy zpool.cache ?
--As for the rest, it is mine.
Did both of those. A half-dozen times. ;)
The machine fails to find a bootable drive. It searches, tries PXE booting
a couple of times, then dumps me into the BIOS's boot drive chooser. I can
try selecting either of the internal drives at that point if I wish, and it
will just loop back to there.
Daniel T. Staal
---
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
--
George Kontostanos
aisecure.net http://www.aisecure.net
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
--As of May 30, 2011 6:29:06 PM +0300, George Kontostanos is alleged to have said: I suppose that you didn't forget to add a boot code to your boot disk(s) ? gpart bootcode -b boot/pmbr -p boot/gptzfsboot -i 1 ada0 --As for the rest, it is mine. Nope, I got that. Although that line as written threw errors. I used: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 (Normally I was installing the boot code to the mSATA drive, as it was the one I was partitioning.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
Sorry about the typos. The bootcode should be installed to the drive that you are booting from. I see that you have: ada1: 1 freebsd-boot 2 freebsd-swap 8G 3 freebsd-zfs 4G (zil) 4 freebsd-zfs 17G (cache) ada0: Managed by ZFS, ~250G Main filesystem. I don't think that ada1 holds any OS files therefore you will need to boot from ada0 gpart create -s gpt ada0 gpart add -b 34 -s 64k -t freebsd-boot ada0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 On Mon, May 30, 2011 at 6:33 PM, Daniel Staal dst...@usa.net wrote: --As of May 30, 2011 6:29:06 PM +0300, George Kontostanos is alleged to have said: I suppose that you didn't forget to add a boot code to your boot disk(s) ? gpart bootcode -b boot/pmbr -p boot/gptzfsboot -i 1 ada0 --As for the rest, it is mine. Nope, I got that. Although that line as written threw errors. I used: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 (Normally I was installing the boot code to the mSATA drive, as it was the one I was partitioning.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- George Kontostanos aisecure.net http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
On 29.05.11 16:10, Daniel Staal wrote: --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to have said: http://www.aisecure.net/?p=132; Thanks, that's about what I expected the install procedure to be at this point. Nice to have the reminder about the zpool.cache. (Do I have to use the Live CD mode? Can I use shell mode instead?) Actually, you don't need to go via the trouble to make /boot writable. You can obtain zpool.cache by using zpool import -c /tmp/zpool.cache zroot Then copy that file to the mounted root filesystem of the zpool. Daniel ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
Thanks, I will reproduce it and update the guide. On Mon, May 30, 2011 at 6:26 PM, Daniel Kalchev dan...@digsys.bg wrote: On 29.05.11 16:10, Daniel Staal wrote: --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to have said: http://www.aisecure.net/?p=132; Thanks, that's about what I expected the install procedure to be at this point. Nice to have the reminder about the zpool.cache. (Do I have to use the Live CD mode? Can I use shell mode instead?) Actually, you don't need to go via the trouble to make /boot writable. You can obtain zpool.cache by using zpool import -c /tmp/zpool.cache zroot Then copy that file to the mounted root filesystem of the zpool. Daniel ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- George Kontostanos aisecure.net http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
--As of May 30, 2011 6:47:32 PM +0300, George Kontostanos is alleged to have said: The bootcode should be installed to the drive that you are booting from. I see that you have: ada1: 1 freebsd-boot 2 freebsd-swap 8G 3 freebsd-zfs 4G (zil) 4 freebsd-zfs 17G (cache) ada0: Managed by ZFS, ~250G Main filesystem. I don't think that ada1 holds any OS files therefore you will need to boot from ada0 gpart create -s gpt ada0 gpart add -b 34 -s 64k -t freebsd-boot ada0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 --As for the rest, it is mine. I said that was my preferred partitioning. I had tried others. ;) I just double-checked putting the bootcode on ada0. It doesn't help. (Note that if it did that'd be an interesting regression from 8.2. My home server is running with *only* the bootcode on one drive, and the OS loaded from a ZFS RAIDZ array.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
mount root from zfs fails under current with error 6
Hi, I get the following error with recent -current (r222417) during boot: ... Trying to mount root from zfs:boot/ROOT/root []... Mounting from zfs:boot/ROOT/root failed with error 6. ... What does error 6 mean? The strange thing is, that I could boot with r222417 a few times but after applying a (here unrelated) one-liner from rmacklem@ to nfs_clkdtrace.c, recompile the module and reinstall, I could'n load either kernel nor kernel.old. I didn't even use the patched module. Only loading a kernel r221381 let me boot again. So may it be a race condition of some form? Anyone else sees this? Any further infos are available on request. Bye/2 --- Michael Reifenberger mich...@reifenberger.com http://www.Reifenberger.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: mount root from zfs fails under current with error 6
On Mon, May 30, 2011 at 9:48 AM, Michael Reifenberger m...@reifenberger.com wrote: Hi, I get the following error with recent -current (r222417) during boot: ... Trying to mount root from zfs:boot/ROOT/root []... Mounting from zfs:boot/ROOT/root failed with error 6. ... What does error 6 mean? See ENXIO under errno(2). The strange thing is, that I could boot with r222417 a few times but after applying a (here unrelated) one-liner from rmacklem@ to nfs_clkdtrace.c, recompile the module and reinstall, I could'n load either kernel nor kernel.old. I didn't even use the patched module. Only loading a kernel r221381 let me boot again. So may it be a race condition of some form? Anyone else sees this? Any further infos are available on request. dmesg for starters (boot -v if possible) would be extremely helpful. More details like your disk subsystem that you're booting off of, whether you're using GPT/MBR when booting via ZFS, etc would be helpful. Also being able to better trace down the root cause would be nice (not being able to boot a recent kernel, but being able to boot a kernel from almost a month ago is unfortunately a bit of a non-starter for tracking down the actual issue because that's such a long span of time). Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
Could you please post the output of: gpart show On Mon, May 30, 2011 at 8:04 PM, Daniel Staal dst...@usa.net wrote: --As of May 30, 2011 6:47:32 PM +0300, George Kontostanos is alleged to have said: The bootcode should be installed to the drive that you are booting from. I see that you have: ada1: 1 freebsd-boot 2 freebsd-swap 8G 3 freebsd-zfs 4G (zil) 4 freebsd-zfs 17G (cache) ada0: Managed by ZFS, ~250G Main filesystem. I don't think that ada1 holds any OS files therefore you will need to boot from ada0 gpart create -s gpt ada0 gpart add -b 34 -s 64k -t freebsd-boot ada0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 --As for the rest, it is mine. I said that was my preferred partitioning. I had tried others. ;) I just double-checked putting the bootcode on ada0. It doesn't help. (Note that if it did that'd be an interesting regression from 8.2. My home server is running with *only* the bootcode on one drive, and the OS loaded from a ZFS RAIDZ array.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- George Kontostanos aisecure.net http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
*zpool import -c /tmp/zpool.cache zroot can not import /tmp/zpool.cache no such pool available * Well, it seems that -c switch is for specifying where to read from and not where to write. I haven't been able to import the pool and find a way to store zpool.cache in a diffrent place other than /boot/zfs On Mon, May 30, 2011 at 6:26 PM, Daniel Kalchev dan...@digsys.bg wrote: On 29.05.11 16:10, Daniel Staal wrote: --As of May 29, 2011 12:06:30 PM +0300, George Kontostanos is alleged to have said: http://www.aisecure.net/?p=132; Thanks, that's about what I expected the install procedure to be at this point. Nice to have the reminder about the zpool.cache. (Do I have to use the Live CD mode? Can I use shell mode instead?) Actually, you don't need to go via the trouble to make /boot writable. You can obtain zpool.cache by using zpool import -c /tmp/zpool.cache zroot Then copy that file to the mounted root filesystem of the zpool. Daniel ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- George Kontostanos aisecure.net http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
mountd, rpc.lockd and rpc.statd patches for testing
Hi, I have patches for the mountd, rpc.statd and rpc.lockd daemons that are meant to keep them from failing when a dynamically selected port# is not available for some combination of udp,tcp X ipv4,ipv6 If anyone would like to test these patches, they can be found at: http://people.freebsd.org/~rmacklem/mountd.patch statd.patch lockd.patch Although I think I got them correct, they are rather big and ugly. rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
George Kontostanos gkontos.m...@gmail.com writes: *zpool import -c /tmp/zpool.cache zroot can not import /tmp/zpool.cache no such pool available Try modifying pool's property: $ zpool import -o cachefile=/tmp/zpool.cache zroot Well, it seems that -c switch is for specifying where to read from and not where to write. I haven't been able to import the pool and find a way to store zpool.cache in a diffrent place other than /boot/zfs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
Bingo! That did it. I will update the guide soon. @Daniel my apologies it seems that another typo is preventing you from booting. You have to set the bootfs in the pool. zpool set bootfs=zroot zroot On Tue, May 31, 2011 at 12:30 AM, Pan Tsu iny...@gmail.com wrote: George Kontostanos gkontos.m...@gmail.com writes: *zpool import -c /tmp/zpool.cache zroot can not import /tmp/zpool.cache no such pool available Try modifying pool's property: $ zpool import -o cachefile=/tmp/zpool.cache zroot Well, it seems that -c switch is for specifying where to read from and not where to write. I haven't been able to import the pool and find a way to store zpool.cache in a diffrent place other than /boot/zfs -- George Kontostanos aisecure.net http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
--As of May 31, 2011 1:21:49 AM +0300, George Kontostanos is alleged to have said: Bingo! That did it. I will update the guide soon. @Daniel my apologies it seems that another typo is preventing you from booting. You have to set the bootfs in the pool. zpool set bootfs=zroot zroot --As for the rest, it is mine. I'd actually caught that one... (Yesterday afternoon.) I was hoping this was something people had seen before. At this point, I've been trying to get a FreeBSD+ZFS install on this box for about a month - including spending much of my first vacation in two years on it - and I know that even if I do manage to do so I'll still have a problem with the screen resolution. (Sandy Bridge integrated graphics. It works in VERSA mode, but doesn't detect the native mode.) I've decided to call it quits for now. A current Linux runs fine. The power management isn't as good as FreeBSD, I'm loosing the ZFS coolness, and the other advantages of a FreeBSD box over Linux, but it means I've got a working laptop for the moment. I'll revisit putting FreeBSD on it sometime in the future, once the hardware isn't quite so current-edge. For now, I've invested too much time into just getting this running. George, a couple other notes on your walkthrough: (I'd decided to wait until I was done to go over all of these.) cd /tmp copy -R * /boot# Needs to be cp. zpool create -O mountpoint=/mnt zroot /dev/gpt/disk0 # Will avoid the export/import later. And in theory it doesn't make *much* difference, but setting the checksum before creating usr, var, and tmp is slightly better practice. (The directory entries are checksummed as well, which would be the only difference. If any files were created in between they'd get the fletcher2 checksum.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS install from -CURRENT snapshot
oops typos, typos! That's one of the bad things that happens when you type without having the copy - paste functionality. On Tue, May 31, 2011 at 1:48 AM, Daniel Staal dst...@usa.net wrote: --As of May 31, 2011 1:21:49 AM +0300, George Kontostanos is alleged to have said: Bingo! That did it. I will update the guide soon. @Daniel my apologies it seems that another typo is preventing you from booting. You have to set the bootfs in the pool. zpool set bootfs=zroot zroot --As for the rest, it is mine. I'd actually caught that one... (Yesterday afternoon.) I was hoping this was something people had seen before. At this point, I've been trying to get a FreeBSD+ZFS install on this box for about a month - including spending much of my first vacation in two years on it - and I know that even if I do manage to do so I'll still have a problem with the screen resolution. (Sandy Bridge integrated graphics. It works in VERSA mode, but doesn't detect the native mode.) I've decided to call it quits for now. A current Linux runs fine. The power management isn't as good as FreeBSD, I'm loosing the ZFS coolness, and the other advantages of a FreeBSD box over Linux, but it means I've got a working laptop for the moment. I'll revisit putting FreeBSD on it sometime in the future, once the hardware isn't quite so current-edge. For now, I've invested too much time into just getting this running. George, a couple other notes on your walkthrough: (I'd decided to wait until I was done to go over all of these.) cd /tmp copy -R * /boot# Needs to be cp. zpool create -O mountpoint=/mnt zroot /dev/gpt/disk0 # Will avoid the export/import later. And in theory it doesn't make *much* difference, but setting the checksum before creating usr, var, and tmp is slightly better practice. (The directory entries are checksummed as well, which would be the only difference. If any files were created in between they'd get the fletcher2 checksum.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- -- George Kontostanos aisecure.net http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
