zfs discuss - Oct 2009 - Strange problem with liveupgrade on zfs (10u7 and u8)

I am have a strange problem with liveupgrade of ZFS boot environment.   I found
a similar discussion on the zones-discuss, but, this happens for me on installs
with and without zones, so I do not think it is related to zones.  I have been
able to reproduce this on both sparc (ldom) and x86 (phsyical).   I was
originally trying to luupdate to u8, but, this is easily reproducible with 3
simple steps: lucreate, luactivate, reboot.

I have a fairly simple install of Solaris 10 u7 with no BE defined.  
Very recent 10 recommended cluster applied.  
121430-42 is present.
Kernel is 141414-10.   
Installed the lu utilities from the Solaris 10 u8 10/09 dvd.  
ZFS root.
/var on a separate dataset.

[b]lucreate -n sol10alt[/b]
Noticed the following warning during lucreate: WARNING: split filesystem
</> file system type <zfs> cannot inherit mount point options
<-> from parent filesystem </> file type <-> because the two
file systems have different types.

[b]luactivate sol10alt[/b]

[b]/usr/sbin/shutdown -g0 -i6 -y[/b]

Boot device: /virtual-devices at 100/channel-devices at 200/disk at 1:a  File
and args:
SunOS Release 5.10 Version Generic_141414-10 64-bit <snip>
Hostname: SOL10WE001
ERROR: svc:/system/filesystem/minimal:default failed to mount /var  (see
''svcs -x'' for details)
Oct 14 23:59:48 svc.startd[7]: svc:/system/filesystem/minimal:default: Method
"/lib/svc/method/fs-minimal" failed with exit status 95.
Oct 14 23:59:48 svc.startd[7]: system/filesystem/minimal:default failed fatally:
transitioned to maintenance (see ''svcs -xv'' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run

Root password for system maintenance (control-d to bypass):

[b]cat /etc/svc/volatile/system-filesystem-minimal:default.log[/b]
[ Oct 14 16:17:19 Enabled. ]
[ Oct 14 16:17:33 Executing start method
("/lib/svc/method/fs-minimal") ]
ERROR: /sbin/mount -O -F zfs   /var failed, err=1
filesystem ''rpool/ROOT/sol10u8BE/var'' cannot be mounted using
''mount -F zfs'' Use ''zfs set mountpoint=/var''
instead. If you must use ''mount -F zfs'' or /etc/vfstab, use
''zfs set mountpoint=legacy''. See zfs(1M) for more information.
[ Oct 14 16:17:33 Method "start" exited with status 95 ]

This appears to be easily fixed by logging in, removing the last two lines of
vfstab :
rpool/ROOT/sol10alt     -       /       zfs     1       no      -
rpool/ROOT/sol10alt/var -       /var    zfs     1       no      -
and rebooting.   The new BE then appears to be fine.    I don''t know if
there are any further ramifications that will appear later, nor why this is
happening exactly.


[b]lucreate output:[/b]
Analyzing system configuration.
Comparing source boot environment <root> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <sol10alt>.
Source boot environment is <root>.
Creating boot environment <sol10alt>.
Cloning file systems from boot environment <root> to create boot
environment <sol10alt>.
Creating snapshot for <rpool/ROOT/root> on <rpool/ROOT/root at
sol10alt>.
Creating clone for <rpool/ROOT/root at sol10alt> on
<rpool/ROOT/sol10alt>.
Setting canmount=noauto for </> in zone <global> on
<rpool/ROOT/sol10alt>.
Creating snapshot for <rpool/ROOT/root/var> on <rpool/ROOT/root/var at
sol10alt>.
Creating clone for <rpool/ROOT/root/var at sol10alt> on
<rpool/ROOT/sol10alt/var>.
Setting canmount=noauto for </var> in zone <global> on
<rpool/ROOT/sol10alt/var>.
WARNING: split filesystem </> file system type <zfs> cannot inherit
mount point options <-> from parent filesystem </> file
type <-> because the two file systems have different types.
Population of boot environment <sol10alt> successful.
Creation of boot environment <sol10alt> successful.

[b]luactivate sol10alt output[/b]
A Live Upgrade Sync operation will be performed on startup of boot environment
<sol10alt>.
**********************************************************************
<snip>
Modifying boot archive service
Activation of boot environment <sol10alt> successful.
-- 
This message posted from opensolaris.org

On 14 October, 2009 - Brian sent me these 4,3K bytes:
> I am have a strange problem with liveupgrade of ZFS boot environment.
> I found a similar discussion on the zones-discuss, but, this happens
> for me on installs with and without zones, so I do not think it is
> related to zones.  I have been able to reproduce this on both sparc
> (ldom) and x86 (phsyical).   I was originally trying to luupdate to
> u8, but, this is easily reproducible with 3 simple steps: lucreate,
> luactivate, reboot.  
...
> [b]lucreate -n sol10alt[/b]
> Noticed the following warning during lucreate: WARNING: split
> filesystem </> file system type <zfs> cannot inherit mount
point
> options <-> from parent filesystem </> file type <->
because the two
> file systems have different types.
Got the same warning and the same end result, was planning on filing it
with Sun yesterday but haven''t have time to do that yet. I got it on
sparc (physical) too. I didn''t install LU from the u8 iso, but it was
patched with latest LU patches through PCA.
> [b]luactivate sol10alt[/b]
If you lumount, comment out those rpool/ROOT/.... thingies, then luumont
here, it''ll work too.
> [b]/usr/sbin/shutdown -g0 -i6 -y[/b]
/Tomas
-- 
Tomas ?gren, stric at acc.umu.se, http://www.acc.umu.se/~stric/
|- Student at Computing Science, University of Ume?
`- Sysadmin at {cs,acc}.umu.se

Hi
This is 6884728 which is a regression from 6837400.
the workaround is as you done, remove the lines from vfstab

Enda


Brian wrote:
> I am have a strange problem with liveupgrade of ZFS boot environment.   I
found a similar discussion on the zones-discuss, but, this happens for me on
installs with and without zones, so I do not think it is related to zones.  I
have been able to reproduce this on both sparc (ldom) and x86 (phsyical).   I
was originally trying to luupdate to u8, but, this is easily reproducible with 3
simple steps: lucreate, luactivate, reboot.
> 
> I have a fairly simple install of Solaris 10 u7 with no BE defined.  
> Very recent 10 recommended cluster applied.  
> 121430-42 is present.
> Kernel is 141414-10.   
> Installed the lu utilities from the Solaris 10 u8 10/09 dvd.  
> ZFS root.
> /var on a separate dataset.
> 
> [b]lucreate -n sol10alt[/b]
> Noticed the following warning during lucreate: WARNING: split filesystem
</> file system type <zfs> cannot inherit mount point options
<-> from parent filesystem </> file type <-> because the two
file systems have different types.
> 
> [b]luactivate sol10alt[/b]
> 
> [b]/usr/sbin/shutdown -g0 -i6 -y[/b]
> 
> Boot device: /virtual-devices at 100/channel-devices at 200/disk at 1:a 
File and args:
> SunOS Release 5.10 Version Generic_141414-10 64-bit <snip>
> Hostname: SOL10WE001
> ERROR: svc:/system/filesystem/minimal:default failed to mount /var  (see
''svcs -x'' for details)
> Oct 14 23:59:48 svc.startd[7]: svc:/system/filesystem/minimal:default:
Method "/lib/svc/method/fs-minimal" failed with exit status 95.
> Oct 14 23:59:48 svc.startd[7]: system/filesystem/minimal:default failed
fatally: transitioned to maintenance (see ''svcs -xv'' for
details)
> Requesting System Maintenance Mode
> (See /lib/svc/share/README for more information.)
> Console login service(s) cannot run
> 
> Root password for system maintenance (control-d to bypass):
> 
> [b]cat /etc/svc/volatile/system-filesystem-minimal:default.log[/b]
> [ Oct 14 16:17:19 Enabled. ]
> [ Oct 14 16:17:33 Executing start method
("/lib/svc/method/fs-minimal") ]
> ERROR: /sbin/mount -O -F zfs   /var failed, err=1
> filesystem ''rpool/ROOT/sol10u8BE/var'' cannot be mounted
using ''mount -F zfs'' Use ''zfs set
mountpoint=/var'' instead. If you must use ''mount -F
zfs'' or /etc/vfstab, use ''zfs set mountpoint=legacy''.
See zfs(1M) for more information.
> [ Oct 14 16:17:33 Method "start" exited with status 95 ]
> 
> This appears to be easily fixed by logging in, removing the last two lines
of vfstab :
> rpool/ROOT/sol10alt     -       /       zfs     1       no      -
> rpool/ROOT/sol10alt/var -       /var    zfs     1       no      -
> and rebooting.   The new BE then appears to be fine.    I don''t
know if there are any further ramifications that will appear later, nor why this
is happening exactly.
> 
> 
> [b]lucreate output:[/b]
> Analyzing system configuration.
> Comparing source boot environment <root> file systems with the file
> system(s) you specified for the new boot environment. Determining which
> file systems should be in the new boot environment.
> Updating boot environment description database on all BEs.
> Updating system configuration files.
> Creating configuration for boot environment <sol10alt>.
> Source boot environment is <root>.
> Creating boot environment <sol10alt>.
> Cloning file systems from boot environment <root> to create boot
environment <sol10alt>.
> Creating snapshot for <rpool/ROOT/root> on <rpool/ROOT/root at
sol10alt>.
> Creating clone for <rpool/ROOT/root at sol10alt> on
<rpool/ROOT/sol10alt>.
> Setting canmount=noauto for </> in zone <global> on
<rpool/ROOT/sol10alt>.
> Creating snapshot for <rpool/ROOT/root/var> on
<rpool/ROOT/root/var at sol10alt>.
> Creating clone for <rpool/ROOT/root/var at sol10alt> on
<rpool/ROOT/sol10alt/var>.
> Setting canmount=noauto for </var> in zone <global> on
<rpool/ROOT/sol10alt/var>.
> WARNING: split filesystem </> file system type <zfs> cannot
inherit
> mount point options <-> from parent filesystem </> file
> type <-> because the two file systems have different types.
> Population of boot environment <sol10alt> successful.
> Creation of boot environment <sol10alt> successful.
> 
> [b]luactivate sol10alt output[/b]
> A Live Upgrade Sync operation will be performed on startup of boot
environment <sol10alt>.
> **********************************************************************
<snip>
> Modifying boot archive service
> Activation of boot environment <sol10alt> successful.

On Wed, 14 Oct 2009 22:07:54 PDT
Brian <bmullen at gmail.com> wrote:
> ERROR: svc:/system/filesystem/minimal:default failed to mount /var
You have found it yourself already. LU packages from update 8 create
lines in /etc/vfstab for ZFS filesystems! Former LU packages never did!
They left a good working vfstab alone. This behaviour is also related
to errors with zones btw. The fact that lines in vfstab are created is
neglected in reactions so far. I think that is weird.

-- 
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
+ http://nagual.nl/ | SunOS 10u8 10/09 | OpenSolaris 2010.02 b123
+ All that''s really worth doing is what we do for others (Lewis Carrol)

On Thu, 15 Oct 2009, Enda O''Connor wrote:
> This is 6884728 which is a regression from 6837400.
> the workaround is as you done, remove the lines from vfstab
Oh, ok, this is the problem described in CR 6884728? Disregard my earlier
inquiry for more details on that CR then.

I ran into exactly the same problem :(. There are no additional issues
other than simply removing the lines from vfstab? I have an open service
request but they haven''t responded yet.

I actually did that, and booted into the U8 boot environment, and then
decided to revert to my previous U6 in case there were any other issues;
unfortunately, now the system won''t boot at all :(, a panic message
flashes
shortly on the screen but I don''t have enough time to see what it is.
And
the stinking java remote console for the x4500 seems to be broken and is
not passing keystrokes through. I haven''t had the time yet to
physically
visit the data center and plug a physical keyboard in to try to boot into
failsafe to resolve it.

-- 
Paul B. Henson  |  (909) 979-6361  |  http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst  |  henson at csupomona.edu
California State Polytechnic University  |  Pomona CA 91768

I''m seeing the same [b]lucreate[/b] error on my fresh SPARC sol10u8
install (and my SPARC sol10u7 machine I keep patches up to date), but I
don''t have a separate /var:

# zfs list
NAME                    USED  AVAIL  REFER  MOUNTPOINT
pool00                 3.36G   532G    20K  none
pool00/global          3.51M   532G    20K  none
pool00/global/appl       20K   532G    20K  /appl
pool00/global/home      324K   532G   324K  /home
pool00/global/local      26K   532G    26K  /usr/local
pool00/global/patches  3.13M   532G  3.13M  /usr/local/patches
pool00/shared          3.35G   532G    20K  none
pool00/shared/install  2.52G   532G  2.52G  /install
pool00/shared/local     849M   532G   849M  /opt/local
rpool                  44.6G  89.2G    97K  /rpool
rpool/ROOT             4.63G  89.2G    21K  legacy
rpool/ROOT/sol10u8     4.63G  89.2G  4.63G  /
rpool/dump             8.01G  89.2G  8.01G  -
rpool/swap               32G   121G    16K  -

# lucreate -n foobar
Analyzing system configuration.
Comparing source boot environment <sol10u8> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <foobar>.
Source boot environment is <sol10u8>.
Creating boot environment <foobar>.
Cloning file systems from boot environment <sol10u8> to create boot
environment <foobar>.
Creating snapshot for <rpool/ROOT/sol10u8> on <rpool/ROOT/sol10u8 at
foobar>.
Creating clone for <rpool/ROOT/sol10u8 at foobar> on
<rpool/ROOT/foobar>.
Setting canmount=noauto for </> in zone <global> on
<rpool/ROOT/foobar>.
WARNING: split filesystem </> file system type <zfs> cannot inherit
mount point options <-> from parent filesystem </> file
type <-> because the two file systems have different types.
Population of boot environment <foobar> successful.
Creation of boot environment <foobar> successful.

# cat /etc/vfstab
#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     -

I don''t see anything wrong with my /etc/vfstab. Until I get this
resolved, I''m afraid to patch and use the new BE.
-- 
This message posted from opensolaris.org

Neither the virgin SPARC sol10u8 nor the (update to date) patched SPARC sol10u7
have any local zones.
-- 
This message posted from opensolaris.org

Hi
This looks ok to me, message but not an indicator of an issue

could you post
cat /etc/lu/ICF.1
cat /etc/ICF.2 ( the foobar Be )

also lumount foobar /a
and cat /a/etc/vfstab


Enda

Mark Horstman wrote:
> I''m seeing the same [b]lucreate[/b] error on my fresh SPARC
sol10u8 install (and my SPARC sol10u7 machine I keep patches up to date), but I
don''t have a separate /var:
> 
> # zfs list
> NAME                    USED  AVAIL  REFER  MOUNTPOINT
> pool00                 3.36G   532G    20K  none
> pool00/global          3.51M   532G    20K  none
> pool00/global/appl       20K   532G    20K  /appl
> pool00/global/home      324K   532G   324K  /home
> pool00/global/local      26K   532G    26K  /usr/local
> pool00/global/patches  3.13M   532G  3.13M  /usr/local/patches
> pool00/shared          3.35G   532G    20K  none
> pool00/shared/install  2.52G   532G  2.52G  /install
> pool00/shared/local     849M   532G   849M  /opt/local
> rpool                  44.6G  89.2G    97K  /rpool
> rpool/ROOT             4.63G  89.2G    21K  legacy
> rpool/ROOT/sol10u8     4.63G  89.2G  4.63G  /
> rpool/dump             8.01G  89.2G  8.01G  -
> rpool/swap               32G   121G    16K  -
> 
> # lucreate -n foobar
> Analyzing system configuration.
> Comparing source boot environment <sol10u8> file systems with the
file
> system(s) you specified for the new boot environment. Determining which
> file systems should be in the new boot environment.
> Updating boot environment description database on all BEs.
> Updating system configuration files.
> Creating configuration for boot environment <foobar>.
> Source boot environment is <sol10u8>.
> Creating boot environment <foobar>.
> Cloning file systems from boot environment <sol10u8> to create boot
environment <foobar>.
> Creating snapshot for <rpool/ROOT/sol10u8> on <rpool/ROOT/sol10u8
at foobar>.
> Creating clone for <rpool/ROOT/sol10u8 at foobar> on
<rpool/ROOT/foobar>.
> Setting canmount=noauto for </> in zone <global> on
<rpool/ROOT/foobar>.
> WARNING: split filesystem </> file system type <zfs> cannot
inherit
> mount point options <-> from parent filesystem </> file
> type <-> because the two file systems have different types.
> Population of boot environment <foobar> successful.
> Creation of boot environment <foobar> successful.
> 
> # cat /etc/vfstab
> #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     -
> 
> I don''t see anything wrong with my /etc/vfstab. Until I get this
resolved, I''m afraid to patch and use the new BE.
-- 
Enda O''Connor x19781  Software Product Engineering
Patch System Test : Ireland : x19781/353-1-8199718

Mark Horstman wrote:
> I don''t see anything wrong with my /etc/vfstab. Until I get this
resolved, I''m afraid to patch and use the new BE.
>   
It''s the vfstab file in the newly created ABE that is
"wrongly" written to.
Try to mount this new ABE and check out for yourself.

-- 
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
+ http://nagual.nl/ | SunOS 10u8 10/09 | OpenSolaris 2010.02 b123
+ All that''s really worth doing is what we do for others (Lewis Carrol)

More input:

# cat /etc/lu/ICF.1
sol10u8:-:/dev/zvol/dsk/rpool/swap:swap:67108864
sol10u8:/:rpool/ROOT/sol10u8:zfs:0
sol10u8:/appl:pool00/global/appl:zfs:0
sol10u8:/home:pool00/global/home:zfs:0
sol10u8:/rpool:rpool:zfs:0
sol10u8:/install:pool00/shared/install:zfs:0
sol10u8:/opt/local:pool00/shared/local:zfs:0
sol10u8:/usr/local:pool00/global/local:zfs:0
sol10u8:/usr/local/patches:pool00/global/patches:zfs:0

# cat /etc/lu/ICF.2
foobar:-:/dev/zvol/dsk/rpool/swap:swap:67108864
foobar:/:rpool/ROOT/foobar:zfs:0
foobar:/appl:pool00/global/appl:zfs:0
foobar:/home:pool00/global/home:zfs:0
foobar:/install:pool00/shared/install:zfs:0
foobar:/opt/local:pool00/shared/local:zfs:0
foobar:/rpool:rpool:zfs:0
foobar:/usr/local:pool00/global/local:zfs:0
foobar:/usr/local/patches:pool00/global/patches:zfs:0

Should I not be concerned about the [b]WARNING: split filesystem </> file
system type <zfs> cannot inherit[/b] message? Like I just have to lumount
the new BE and modify it''s /etc/vfstab and then proceed as normal using
luupgrade to apply patches to the new BE?
-- 
This message posted from opensolaris.org

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.
-- 
This message posted from opensolaris.org

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.

Then why the warning on the lucreate. It hasn''t done that in the past.

Mark

On Oct 21, 2009, at 12:41 PM, "Enda O''Connor"
<Enda.Oconnor at 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.
>

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.Oconnor at 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.
>>

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.Oconnor at
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.Oconnor at 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.
>>>>
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20091021/806f60e7/attachment.html>

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.Oconnor
at sun.com
> <mailto:Enda.Oconnor at 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.Oconnor at 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.
> 
> 
> 
>