zfs discuss - Oct 2007 - zfs won''t import a pool automatically at boot

Hi,

When jumpstarting s10x_u4_fcs onto a machine, I have a postinstall script which
does:

zpool create tank c1d0s7 c2d0s7 c3d0s7 c4d0s7
zfs create tank/data
zfs set mountpoint=/data tank/data
zpool export -f tank

When jumpstart finishes and the node reboots, the pool is not imported
automatically. I have to do:

zpool import tank

for it to show up. Then on subsequent reboots it imports and mounts
automatically. What I can I do to get it to mount automatically the first time?
When I didn''t have the zpool export I would get an message that I
needed to use zpool import -f because it wasn''t exported properly from
another machine. So it looks like the state of the pool created during the
jumpstart install was lost.

BTW, I love using zfs commands to manage filesystems. They are so easy and
intuitive!

thanks,
Mike
 
 
This message posted from opensolaris.org

On 16/10/2007, Michael Goff <michael.goff at sun.com>
wrote:
> Hi,
>
> When jumpstarting s10x_u4_fcs onto a machine, I have a postinstall script
which does:
>
> zpool create tank c1d0s7 c2d0s7 c3d0s7 c4d0s7
> zfs create tank/data
> zfs set mountpoint=/data tank/data
> zpool export -f tank
Try without the ''-f'' ?


-- 
Rasputin :: Jack of All Trades - Master of Nuns
http://number9.hellooperator.net/

Hi Mike,
   
  After rebooting a UNIX machine (HP-UX/Linux/Solaris), it will mount (or
import) only the file systems which are mounted (or imported) before the reboot.
   
  In your case the zfs file system tank/data is exported(or unmounted) before
reboot.Thats the reason why the zpool is not imported automatically after
reboot.
   
  This is neither a problem nor a bug. ZFS developers designed the import and
export command like this.
   
  Not only ZFS, no file system will mount all the available file systems. Any
UNIX machine will mount only the file systems which are mounted before reboot.
    -Masthan  D

Michael Goff <michael.goff at sun.com> wrote:

  Hi,

When jumpstarting s10x_u4_fcs onto a machine, I have a postinstall script which
does:

zpool create tank c1d0s7 c2d0s7 c3d0s7 c4d0s7
zfs create tank/data
zfs set mountpoint=/data tank/data
zpool export -f tank

When jumpstart finishes and the node reboots, the pool is not imported
automatically. I have to do:

zpool import tank

for it to show up. Then on subsequent reboots it imports and mounts
automatically. What I can I do to get it to mount automatically the first time?
When I didn''t have the zpool export I would get an message that I
needed to use zpool import -f because it wasn''t exported properly from
another machine. So it looks like the state of the pool created during the
jumpstart install was lost.

BTW, I love using zfs commands to manage filesystems. They are so easy and
intuitive!

thanks,
Mike


This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss at opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


       
---------------------------------
Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20071016/fe88e645/attachment.html>

Michael,

If you don''t call "zpool export -f tank" it should work.
However, it would be necessary to understand why you are using the above 
command after creation of the zpool.

Can you avoid exporting after the creation ?

Regards,
Sanjeev


Michael Goff wrote:
> Hi,
>
> When jumpstarting s10x_u4_fcs onto a machine, I have a postinstall script
which does:
>
> zpool create tank c1d0s7 c2d0s7 c3d0s7 c4d0s7
> zfs create tank/data
> zfs set mountpoint=/data tank/data
> zpool export -f tank
>
> When jumpstart finishes and the node reboots, the pool is not imported
automatically. I have to do:
>
> zpool import tank
>
> for it to show up. Then on subsequent reboots it imports and mounts
automatically. What I can I do to get it to mount automatically the first time?
When I didn''t have the zpool export I would get an message that I
needed to use zpool import -f because it wasn''t exported properly from
another machine. So it looks like the state of the pool created during the
jumpstart install was lost.
>
> BTW, I love using zfs commands to manage filesystems. They are so easy and
intuitive!
>
> thanks,
> Mike
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>   

-- 
Solaris Revenue Products Engineering,
India Engineering Center,
Sun Microsystems India Pvt Ltd.
Tel:    x27521 +91 80 669 27521

Hello Sanjeev,

Tuesday, October 16, 2007, 10:14:01 AM, you wrote:

SB> Michael,

SB> If you don''t call "zpool export -f tank" it should
work.
SB> However, it would be necessary to understand why you are using the above
SB> command after creation of the zpool.

SB> Can you avoid exporting after the creation ?


It won''t help during jumpstart as /etc is not the same one as after he
will boot.

Before you export a pool put in your finish script:

    cp -p /etc/zfs/zpool.cache /a/etc/zfs/

Then export a pool. It should do the trick.

-- 
Best regards,
 Robert Milkowski                        mailto:rmilkowski at task.gda.pl
                                       http://milek.blogspot.com

Great, thanks Robert. That''s what I was looking for. I was thinking
that
I would have to transfer the state somehow from the temporary jumpstart 
environment to /a so that it would be persistent. I''ll test it out
tomorrow.

Sanjeev, when I did not have the zpool export, it still did not import 
automatically upon reboot after the jumpstart. And when I imported it 
manually, if gave an error. So that''s why I added the export.

Mike

Robert Milkowski wrote:
> Hello Sanjeev,
> 
> Tuesday, October 16, 2007, 10:14:01 AM, you wrote:
> 
> SB> Michael,
> 
> SB> If you don''t call "zpool export -f tank" it
should work.
> SB> However, it would be necessary to understand why you are using the
above
> SB> command after creation of the zpool.
> 
> SB> Can you avoid exporting after the creation ?
> 
> 
> It won''t help during jumpstart as /etc is not the same one as
after he
> will boot.
> 
> Before you export a pool put in your finish script:
> 
>     cp -p /etc/zfs/zpool.cache /a/etc/zfs/
> 
> Then export a pool. It should do the trick.
>

Thanks Robert ! I missed that part.

-- Sanjeev.

Michael Goff wrote:
> Great, thanks Robert. That''s what I was looking for. I was
thinking
> that I would have to transfer the state somehow from the temporary 
> jumpstart environment to /a so that it would be persistent. I''ll
test
> it out tomorrow.
>
> Sanjeev, when I did not have the zpool export, it still did not import 
> automatically upon reboot after the jumpstart. And when I imported it 
> manually, if gave an error. So that''s why I added the export.
>
> Mike
>
> Robert Milkowski wrote:
>> Hello Sanjeev,
>>
>> Tuesday, October 16, 2007, 10:14:01 AM, you wrote:
>>
>> SB> Michael,
>>
>> SB> If you don''t call "zpool export -f tank" it
should work.
>> SB> However, it would be necessary to understand why you are using 
>> the above
>> SB> command after creation of the zpool.
>>
>> SB> Can you avoid exporting after the creation ?
>>
>>
>> It won''t help during jumpstart as /etc is not the same one as
after he
>> will boot.
>>
>> Before you export a pool put in your finish script:
>>
>>     cp -p /etc/zfs/zpool.cache /a/etc/zfs/
>>
>> Then export a pool. It should do the trick.
>>

-- 
Solaris Revenue Products Engineering,
India Engineering Center,
Sun Microsystems India Pvt Ltd.
Tel:    x27521 +91 80 669 27521