headers
Frank Cusack | 1 Sep 2006 01:00

can't create snapshot

[root <at> milk:~]# zfs snapshot export/zone/smb/share/it <at> 5
internal error: unexpected error 16 at line 2302 of ../common/libzfs_dataset.c

I don't have this problem with other filesystems.  There was one existing
snapshot which, after getting the above error, I deleted successfully.  But
I still can't take a new snapshot.

The filesystem is not mounted.

-frank
Permalink | Reply | 2 comments |
headers
Frank Cusack | 1 Sep 2006 01:08

Re: can't create snapshot

On August 31, 2006 4:00:52 PM -0700 Frank Cusack <fcusack <at> fcusack.com> wrote:
> [root <at> milk:~]# zfs snapshot export/zone/smb/share/it <at> 5
> internal error: unexpected error 16 at line 2302 of ../common/libzfs_dataset.c
>
> I don't have this problem with other filesystems.  There was one existing
> snapshot which, after getting the above error, I deleted successfully.  But
> I still can't take a new snapshot.
>
> The filesystem is not mounted.

This was on a zoned filesystem.  I booted the single zone mounting this fs
(which then mounted the fs) and was able to take the snapshot.  After halting
the zone, I am still able to take snapshots.  Note that this same zone mounts
other filesystems, on which I was able to take snapshots without any problems.

-frank
Permalink | Reply | 0 comments |
headers
Matthew Ahrens | 1 Sep 2006 01:15
Picon

Re: can't create snapshot

Frank Cusack wrote:
> [root <at> milk:~]# zfs snapshot export/zone/smb/share/it <at> 5
> internal error: unexpected error 16 at line 2302 of 
> ../common/libzfs_dataset.c
> 
> I don't have this problem with other filesystems.  There was one existing
> snapshot which, after getting the above error, I deleted successfully.  But
> I still can't take a new snapshot.
> 
> The filesystem is not mounted.

Hmm, I wonder if this is related to 6462803 "zfs snapshot -r failed 
because filesystem was busy"?  If you mount the filesystem (thus causing 
any latent intent log to be played), can you take the snapshot?

--matt
Permalink | Reply | 0 comments |
headers
Casper.Dik | 1 Sep 2006 14:20
Picon

Re: zpool import: snv_33 to S10 6/06


>Hi,
>
>root <at> u20# cat /etc/release
>                            Solaris Nevada snv_33 X86
>           Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.
>                        Use is subject to license terms.
>                           Assembled 06 February 2006
>
>I have zfs running well on this box.  Now, I want to upgrade to Solaris 
>10 6/06 release. 

Aside from mentioned ZFS issues note that "upgrade" is not the proper
word to use here; it's a "sidegrade" of sorts and it requires a reinstall
of the OS.

Casper
Permalink | Reply | 0 comments |
headers
Detlef Drewanz | 1 Sep 2006 14:37
Picon

Changes during zpool import

If I do a zpool import, all the properties gets read and 
accepted, right ? So this include mount points and 
nfs-shares too.

Is there a way to change a property (e.g. mointpoint) before 
I import and also can I list properties before I import to 
have a preview ?

Detlef
Permalink | Reply | 1 comment |
headers
Marlanne DeLaSource | 1 Sep 2006 15:03

zfs clones

As I understand it, the snapshot of a set is used as a reference by the clone.

So the clone is initially a set of pointers to the snapshot. That's why it is so fast to create.

How can I "separate" it from the snapshot ? (so that df -k or zfs list will display for a 48G drive
pool/fs1 4G 40G
pool/clone 4G 40G

instead of 
pool/fs1 4G 44G
pool/clone 4G 44G )

I hope I am clear enough :/

Thanks

Marlanne

 
This message posted from opensolaris.org
Permalink | Reply | 11 comments |
headers
Nicolas Dorfsman | 1 Sep 2006 16:05

Re: Changes during zpool import

extract from man zpool :

[I]zpool import [-d dir] [-D] [-f] [-o opts] [-R root]  pool  |
     id [newpool]

         Imports a specific pool. A pool can be identified by its
         name or the numeric identifier. If newpool is specified,
         the pool is imported using the name newpool.  Otherwise,
         it is imported with the same name as its exported name.

         If a device is removed from  a  system  without  running
         "zpool  export" first, the device appears as potentially
         active. It cannot be determined if  this  was  a  failed
         export,  or  whether  the  device  is really in use from
         another host. To import a pool in  this  state,  the  -f
         option is required.

         -d dir   Searches for devices or files in  dir.  The  -d
                  option can be specified multiple times.

         -D       Imports destroyed pool. The -f option  is  also
                  required.

         -f       Forces import, even if the pool appears  to  be
                  potentially active.

         -o opts  Comma-separated list of mount  options  to  use
                  when  mounting  datasets  within  the pool. See
                  zfs(1M) for a description of dataset properties
                  and mount options.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nicolas Dorfsman | 1 Sep 2006 16:09

Re: ZFS with expanding LUNs

It's a really interesting question.

I used to have the issue on UFS, and the answer was "use VxVM or ZFS".  Mmmm.

Does it really work on ZFS ?

 
This message posted from opensolaris.org
Permalink | Reply | 0 comments |
headers
Matthew Ahrens | 1 Sep 2006 18:53
Picon

Re: zfs clones

Marlanne DeLaSource wrote:
> As I understand it, the snapshot of a set is used as a reference by the clone.
> 
> So the clone is initially a set of pointers to the snapshot. That's why it is so fast to create.
> 
> How can I "separate" it from the snapshot ? (so that df -k or zfs list will display for a 48G drive
> pool/fs1 4G 40G
> pool/clone 4G 40G
> 
> instead of 
> pool/fs1 4G 44G
> pool/clone 4G 44G )
> 
> I hope I am clear enough :/

There is no way to "separate" a clone from its origin snapshot.

I think the numbers you're posting are:

FS		REFD	AVAIL
pool/fs1	4G	40G
pool/clone	4G	40G

So you want it to say that less space is available than really is?

Perhaps what you want is to set a reservation on the clone for its 
initial size, so that you will be guaranteed to have enough space to 
overwrite its initial contents with new contents of the same size?

--matt
(Continue reading)

Permalink | Reply | 1 comment |
headers
Arlina Goce-Capiral | 1 Sep 2006 18:53
Picon

Question: Looking for ways on copying zfs filesys between disks

All,

System (SunFire T2000) migrated to Solaris 10 6/06 and old lucopy 
methods do not work for copying zfs
filesystems between disks for backups. Customer is looking for way to do 
"ufsdump" type method between
c0t0d0s4 and c0t2d0s4 for backup?

I checked the ZFS Admin guide and i saw regarding ZFS backups and 
restore commands like "zfs send" and
"zfs receive". More informations can be found on page 96 of the admin 
guide.  Is this what the customer is
looking for?

Any suggestions?

Thank you in advance,
Arlina

NOTE: Please email me directly as i'm not on this alias.
Permalink | Reply | 2 comments |

Gmane