Hi
Yes sorry remove that line from vfstab in the new BE
Enda
Mark wrote:
Ok. Thanks. Why does '/' show up in the newly created /BE/etc/vfstab but
not in the current /etc/vfstab? Should '/' be in the /BE/etc/vfstab?
btw, thank you for responding so quickly to this.
Mark
On Wed, Oct 21, 2009 at 12:49 PM, Enda O'Connor <enda.ocon...@sun.com
<mailto:enda.ocon...@sun.com>> wrote:
Mark Horstman wrote:
Then why the warning on the lucreate. It hasn't done that in the
past.
this is from the vfstab processing code in ludo.c, in your case not
causing any issue, but shall be fixed.
Enda
Mark
On Oct 21, 2009, at 12:41 PM, "Enda O'Connor"
<enda.ocon...@sun.com> wrote:
Hi T
his will boot ok in my opinion, not seeing any issues there.
Enda
Mark Horstman wrote:
more input:
# lumount foobar /mnt
/mnt
# cat /mnt/etc/vfstab
# cat /mnt/etc/vfstab
#live-upgrade:<Wed Oct 21 09:36:20 CDT 2009> updated
boot environment <foobar>
#device device mount FS
fsck mount mount
#to mount to fsck point type
pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/zvol/dsk/rpool/swap - - swap
- no -
/devices - /devices devfs -
no -
sharefs - /etc/dfs/sharetab sharefs -
no -
ctfs - /system/contract ctfs -
no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
rpool/ROOT/foobar - / zfs 1
no -
So I'm guessing the '/' entry has to be removed.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
