Migrate /var from UFS to ZFS

  • Follow


Hi,

I am quite new to Solaris10 and ZFS and I want to change /var from UFS 
to ZFS.

What I did:

ufsdump -0f /export/var.dump /var
umount -f /var
zpool create -f -m /var var c0t2d0s4
cd /var
ufsrestore rvf /export/var.dump

Now after removing the /var mount point from /etc/vfstab and rebooting, 
no /var is mounted at all - therefore the system doesn't come up 
correctly.

Relating to svcs -x and some console errors, I got the following hints:
"set mountpoint=/var" to automount, or:
"set mountpoint=legacy" and set a proper entry in /etc/vfstab

None of these worked. Can you give me any help? How has the /etc/vfstab 
entry to look like? What am I missing?

Thanks in advance,
Dietmar
0
Reply Dietmar 12/4/2007 11:49:00 AM

On Dec 4, 11:49 am, Dietmar Braun <spam2007-09...@arath.org> wrote:
> Hi,
>
> I am quite new to Solaris10 and ZFS and I want to change /var from UFS
> to ZFS.
>
Don't.

0
Reply Tim 12/4/2007 12:47:30 PM


In article <MPG.21bf5d1b3c1566249896b7@news.netcologne.de>,
 Dietmar Braun <spam2007-09-10@arath.org> wrote:

> Hi,
> 
> I am quite new to Solaris10 and ZFS and I want to change /var from UFS 
> to ZFS.
> 
> What I did:
> 
> ufsdump -0f /export/var.dump /var
> umount -f /var
> zpool create -f -m /var var c0t2d0s4
> cd /var
> ufsrestore rvf /export/var.dump
> 
> Now after removing the /var mount point from /etc/vfstab and rebooting, 
> no /var is mounted at all - therefore the system doesn't come up 
> correctly.
> 
> Relating to svcs -x and some console errors, I got the following hints:
> "set mountpoint=/var" to automount, or:
> "set mountpoint=legacy" and set a proper entry in /etc/vfstab
> 
> None of these worked. Can you give me any help? How has the /etc/vfstab 
> entry to look like? What am I missing?
> 
> Thanks in advance,
> Dietmar

AFAIK, none of the boot disk which contains the running system can be 
ZFS currently.  For now put your data on ZFS and keep the system on UFS.

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...



0
Reply Michael 12/4/2007 11:11:18 PM

On Dec 4, 6:11 pm, Michael Vilain <vil...@NOspamcop.net> wrote:
> In article <MPG.21bf5d1b3c156624989...@news.netcologne.de>,
>  Dietmar Braun <spam2007-09...@arath.org> wrote:
>
>
>
>
>
> > Hi,
>
> > I am quite new to Solaris10 and ZFS and I want to change /var from UFS
> > to ZFS.
>
> > What I did:
>
> > ufsdump -0f /export/var.dump /var
> > umount -f /var
> > zpool create -f -m /var var c0t2d0s4
> > cd /var
> > ufsrestore rvf /export/var.dump
>
> > Now after removing the /var mount point from /etc/vfstab and rebooting,
> > no /var is mounted at all - therefore the system doesn't come up
> > correctly.
>
> > Relating to svcs -x and some console errors, I got the following hints:
> > "set mountpoint=/var" to automount, or:
> > "set mountpoint=legacy" and set a proper entry in /etc/vfstab
>
> > None of these worked. Can you give me any help? How has the /etc/vfstab
> > entry to look like? What am I missing?
>
> > Thanks in advance,
> > Dietmar
>
> AFAIK, none of the boot disk which contains the running system can be
> ZFS currently.  For now put your data on ZFS and keep the system on UFS.
>
> --
> DeeDee, don't press that button!  DeeDee!  NO!  Dee...- Hide quoted text -
>
> - Show quoted text -

Michael is right.  The UFS reader in the Solaris bootstrap code cannot
read ZFS yet.  That may change in the near future.
0
Reply Gorkhan 12/5/2007 2:30:53 AM

Gorkhan wrote:
> On Dec 4, 6:11 pm, Michael Vilain <vil...@NOspamcop.net> wrote:
>> In article <MPG.21bf5d1b3c156624989...@news.netcologne.de>,
>>  Dietmar Braun <spam2007-09...@arath.org> wrote:
>>
>>
>>
>>
>>
>>> Hi,
>>> I am quite new to Solaris10 and ZFS and I want to change /var from UFS
>>> to ZFS.
>>> What I did:
>>> ufsdump -0f /export/var.dump /var
>>> umount -f /var
>>> zpool create -f -m /var var c0t2d0s4
>>> cd /var
>>> ufsrestore rvf /export/var.dump
>>> Now after removing the /var mount point from /etc/vfstab and rebooting,
>>> no /var is mounted at all - therefore the system doesn't come up
>>> correctly.
>>> Relating to svcs -x and some console errors, I got the following hints:
>>> "set mountpoint=/var" to automount, or:
>>> "set mountpoint=legacy" and set a proper entry in /etc/vfstab
>>> None of these worked. Can you give me any help? How has the /etc/vfstab
>>> entry to look like? What am I missing?
>>> Thanks in advance,
>>> Dietmar
>> AFAIK, none of the boot disk which contains the running system can be
>> ZFS currently.  For now put your data on ZFS and keep the system on UFS.
>>
>> --
>> DeeDee, don't press that button!  DeeDee!  NO!  Dee...- Hide quoted text -
>>
>> - Show quoted text -
> 
> Michael is right.  The UFS reader in the Solaris bootstrap code cannot
> read ZFS yet.  That may change in the near future.

But that logic should mean that / MUST be UFS but /var COULD be ZFS...

Back in the day before UFS logging, /var was the filesystem most likely
to be corrupted during a power cut (and so a strong argument for having
it on its own disk slice); logging almost completely fixed that but ZFS 
would make it even better.

Pete.
0
Reply Peter 12/5/2007 8:09:02 AM

In article <fj5mav$dvh$1@gemini.csx.cam.ac.uk>,
 Peter Bunclark <psb@ast.cam.ac.uk> wrote:

> Gorkhan wrote:
> > On Dec 4, 6:11 pm, Michael Vilain <vil...@NOspamcop.net> wrote:
> >> In article <MPG.21bf5d1b3c156624989...@news.netcologne.de>,
> >>  Dietmar Braun <spam2007-09...@arath.org> wrote:
> >>
> >>
> >>
> >>
> >>
> >>> Hi,
> >>> I am quite new to Solaris10 and ZFS and I want to change /var from UFS
> >>> to ZFS.
> >>> What I did:
> >>> ufsdump -0f /export/var.dump /var
> >>> umount -f /var
> >>> zpool create -f -m /var var c0t2d0s4
> >>> cd /var
> >>> ufsrestore rvf /export/var.dump
> >>> Now after removing the /var mount point from /etc/vfstab and rebooting,
> >>> no /var is mounted at all - therefore the system doesn't come up
> >>> correctly.
> >>> Relating to svcs -x and some console errors, I got the following hints:
> >>> "set mountpoint=/var" to automount, or:
> >>> "set mountpoint=legacy" and set a proper entry in /etc/vfstab
> >>> None of these worked. Can you give me any help? How has the /etc/vfstab
> >>> entry to look like? What am I missing?
> >>> Thanks in advance,
> >>> Dietmar
> >> AFAIK, none of the boot disk which contains the running system can be
> >> ZFS currently.  For now put your data on ZFS and keep the system on UFS.
> >>
> >> --
> >> DeeDee, don't press that button!  DeeDee!  NO!  Dee...- Hide quoted text -
> >>
> >> - Show quoted text -
> > 
> > Michael is right.  The UFS reader in the Solaris bootstrap code cannot
> > read ZFS yet.  That may change in the near future.
> 
> But that logic should mean that / MUST be UFS but /var COULD be ZFS...
> 
> Back in the day before UFS logging, /var was the filesystem most likely
> to be corrupted during a power cut (and so a strong argument for having
> it on its own disk slice); logging almost completely fixed that but ZFS 
> would make it even better.
> 
> Pete.

Except that if /var is tmpfs, it's created when the system is booted.  
If /var is a filesystem that mounts when the system boots as part of the 
OS, it must be UFS.  If you doubt or want to quibble, try it and report 
back what you find.  But AFAIK, it won't work currently.

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...



0
Reply Michael 12/5/2007 8:16:18 AM

On Dec 4, 1:49 pm, Dietmar Braun <spam2007-09...@arath.org> wrote:
> Hi,
>
> I am quite new to Solaris10 and ZFS and I want to change /var from UFS
> to ZFS.
>
> What I did:
>
> ufsdump -0f /export/var.dump /var
> umount -f /var
> zpool create -f -m /var var c0t2d0s4
> cd /var
> ufsrestore rvf /export/var.dump
>
> Now after removing the /var mount point from /etc/vfstab and rebooting,
> no /var is mounted at all - therefore the system doesn't come up
> correctly.
>
> Relating to svcs -x and some console errors, I got the following hints:
> "set mountpoint=/var" to automount, or:
> "set mountpoint=legacy" and set a proper entry in /etc/vfstab
>
> None of these worked. Can you give me any help? How has the /etc/vfstab
> entry to look like? What am I missing?
>
> Thanks in advance,
> Dietmar

Solaris or OpenSolaris?
Sparc or x86?
0
Reply pavelj 12/5/2007 1:45:01 PM

Michael Vilain wrote:

> 
> Except that if /var is tmpfs, it's created when the system is booted.  

can't be, /var needs to be persistent.

Pete.
0
Reply Peter 12/5/2007 2:38:19 PM

On Dec 5, 1:09 am, Peter Bunclark <p...@ast.cam.ac.uk> wrote:
> Gorkhan wrote:
> > On Dec 4, 6:11 pm, Michael Vilain <vil...@NOspamcop.net> wrote:
> >> In article <MPG.21bf5d1b3c156624989...@news.netcologne.de>,
> >>  Dietmar Braun <spam2007-09...@arath.org> wrote:
>
> >>> Hi,
> >>> I am quite new to Solaris10 and ZFS and I want to change /var from UFS
> >>> to ZFS.
> >>> What I did:
> >>> ufsdump -0f /export/var.dump /var
> >>> umount -f /var
> >>> zpool create -f -m /var var c0t2d0s4
> >>> cd /var
> >>> ufsrestore rvf /export/var.dump
> >>> Now after removing the /var mount point from /etc/vfstab and rebooting,
> >>> no /var is mounted at all - therefore the system doesn't come up
> >>> correctly.
> >>> Relating to svcs -x and some console errors, I got the following hints:
> >>> "set mountpoint=/var" to automount, or:
> >>> "set mountpoint=legacy" and set a proper entry in /etc/vfstab
> >>> None of these worked. Can you give me any help? How has the /etc/vfstab
> >>> entry to look like? What am I missing?
> >>> Thanks in advance,
> >>> Dietmar
> >> AFAIK, none of the boot disk which contains the running system can be
> >> ZFS currently.  For now put your data on ZFS and keep the system on UFS.
>
> >> --
> >> DeeDee, don't press that button!  DeeDee!  NO!  Dee...- Hide quoted text -
>
> >> - Show quoted text -
>
> > Michael is right.  The UFS reader in the Solaris bootstrap code cannot
> > read ZFS yet.  That may change in the near future.
>
> But that logic should mean that / MUST be UFS but /var COULD be ZFS...
>
> Back in the day before UFS logging, /var was the filesystem most likely
> to be corrupted during a power cut (and so a strong argument for having
> it on its own disk slice); logging almost completely fixed that but ZFS
> would make it even better.
>
> Pete.

I'm unclear on all the dependencies, but the package and install tools
don't support ZFS yet
so I wouldn't recommend ZFS for /var, which contains package
information and other system
files.

We'll keep you posted on when this support is available.

Cindy
0
Reply cindy 12/5/2007 3:52:57 PM

cindy wrote:
> On Dec 5, 1:09 am, Peter Bunclark <p...@ast.cam.ac.uk> wrote:
>> Gorkhan wrote:
>>> On Dec 4, 6:11 pm, Michael Vilain <vil...@NOspamcop.net> wrote:
>>>> In article <MPG.21bf5d1b3c156624989...@news.netcologne.de>,
>>>>  Dietmar Braun <spam2007-09...@arath.org> wrote:
>>>>> Hi,
>>>>> I am quite new to Solaris10 and ZFS and I want to change /var from UFS
>>>>> to ZFS.
>>>>> What I did:
>>>>> ufsdump -0f /export/var.dump /var
>>>>> umount -f /var
>>>>> zpool create -f -m /var var c0t2d0s4
>>>>> cd /var
>>>>> ufsrestore rvf /export/var.dump
>>>>> Now after removing the /var mount point from /etc/vfstab and rebooting,
>>>>> no /var is mounted at all - therefore the system doesn't come up
>>>>> correctly.
>>>>> Relating to svcs -x and some console errors, I got the following hints:
>>>>> "set mountpoint=/var" to automount, or:
>>>>> "set mountpoint=legacy" and set a proper entry in /etc/vfstab
>>>>> None of these worked. Can you give me any help? How has the /etc/vfstab
>>>>> entry to look like? What am I missing?
>>>>> Thanks in advance,
>>>>> Dietmar
>>>> AFAIK, none of the boot disk which contains the running system can be
>>>> ZFS currently.  For now put your data on ZFS and keep the system on UFS.
>>>> --
>>>> DeeDee, don't press that button!  DeeDee!  NO!  Dee...- Hide quoted text -
>>>> - Show quoted text -
>>> Michael is right.  The UFS reader in the Solaris bootstrap code cannot
>>> read ZFS yet.  That may change in the near future.
>> But that logic should mean that / MUST be UFS but /var COULD be ZFS...
>>
>> Back in the day before UFS logging, /var was the filesystem most likely
>> to be corrupted during a power cut (and so a strong argument for having
>> it on its own disk slice); logging almost completely fixed that but ZFS
>> would make it even better.
>>
>> Pete.
> 
> I'm unclear on all the dependencies, but the package and install tools
> don't support ZFS yet
> so I wouldn't recommend ZFS for /var, which contains package
> information and other system
> files.
> 

Just to follow up on what Cindy said, we do not support upgrading or 
patching a system which uses ZFS for parts of the file system where the 
OS is located, and that includes /var.  Even once we add support for 
using ZFS for those file systems, we will not support mixed 
installations where part of the OS is on UFS and part on ZFS.

Dave
0
Reply Dave 12/5/2007 9:07:36 PM

9 Replies
257 Views

(page loaded in 0.201 seconds)

Similiar Articles:













7/24/2012 1:48:29 AM


Reply: