Bug#636668: kfreebsd-amd64: various failures
> - The hard disk was properly discovered, but the partitioning step was
> awfully slow.
This may be related to partman-zfs. For now I've only worried about
adding the missing features and correcting bugs, I think it still has
much room for optimization.
If someone wants to help with this, I suggest instrumenting all calls
to zpool(8) and zfs(8) commands. I suspect they may be called LOTS of
times in certain situations.
> I noticed on console 4 that it was complaining about
> partitions not being properly aligned on slices, about 5 times, one
> per second.
This is a harmless message (see #603380), but I thought the fix made
it to squeeze.
I guess kfreebsd-kernel-di needs an update.
> - However, /usr and /var were not mounted. Actually /etc/fstab did not
> even mention them.
Was your root filesystem missing in fstab too?
Btw, which version of partman-zfs were you using?
> root@hermes:/# mount /dev/da0s8 /usr
> mount: /dev/da0s8 : Invalid argument
> root@hermes:/# mount /dev/da0s8 /usr -t zfs
> mount: /dev/da0s8 : Invalid argument
> root@hermes:/# mount /dev/da0s8 /usr -t zfs -o local
> mount: /dev/da0s8 : Invalid argument
That's not correct; on ZFS you mount the dataset from a ZFS pool,
never directly from a physical device.
With legacy mount command this would be:
mount mypool/myfilesystem /usr
which is equivalent to:
zfs set mountpoint=/usr mypool/myfilesystem
You can obtain a list of pools and filesystems with:
zfs list
Or display the status of all imported pools (including their physical
devices) with:
zpool status
If you want more info I recommend
http://wiki.freebsd.org/ZFSQuickStartGuide as a quick introduction.
--
Robert Millan
Reply to: