search for: utf8on

Hi all, I''m setting up a new fileserver, and while I''m not planning on enabling CIFS right away, I know I will in the future. I know there are several ZFS properties or attributes that affect how CIFS behaves. I seem to recall that at least one of those needs to be set early (like when the filesystem [or pool?] is created? Which properties might those be? Where can I find

Do we have enormous fragmentation here on our X4500 with Solaris 10, ZFS Version 10? What except zfs send/receive can be done to free the fragmented space? One ZFS was used for some month to store some large disk images (each 50GByte large) which are copied there with rsync. This ZFS then reports 6.39TByte usage with zfs list and only 2TByte usage with du. The other ZFS was used for similar

...pool/users canmount on default remotepool/users xattr off temporary remotepool/users copies 1 default remotepool/users version 5 - remotepool/users utf8only off - remotepool/users normalization none - remotepool/users casesensitivity insensitive - remotepool/users vscan off default remotepool/users nbmand on...

...restricted default pool1/fs1 canmount on default pool1/fs1 xattr on default pool1/fs1 copies 1 default pool1/fs1 version 5 - pool1/fs1 utf8only off - pool1/fs1 normalization none - pool1/fs1 casesensitivity sensitive - pool1/fs1 vscan off default pool1/fs1 nbmand off default pool1/fs1 shar...

...ult fsdata/admin/ENS shareiscsi off default fsdata/admin/ENS xattr on default fsdata/admin/ENS copies 1 default fsdata/admin/ENS version 4 - fsdata/admin/ENS utf8only off - fsdata/admin/ENS normalization none - fsdata/admin/ENS casesensitivity sensitive - fsdata/admin/ENS vscan off default fsdata/admin/ENS nbmand off...

...default tank/lxc/tipper/brick1 xattr on default tank/lxc/tipper/brick1 copies 1 default tank/lxc/tipper/brick1 version 5 - tank/lxc/tipper/brick1 utf8only off - tank/lxc/tipper/brick1 normalization none - tank/lxc/tipper/brick1 casesensitivity sensitive - tank/lxc/tipper/brick1 vscan off...

...default storagepool/ndc shareiscsi off default storagepool/ndc xattr on default storagepool/ndc copies 1 default storagepool/ndc version 3 - storagepool/ndc utf8only off - storagepool/ndc normalization none - storagepool/ndc casesensitivity sensitive - storagepool/ndc vscan off default storagepool/ndc nbmand off default storagepool/ndc...

...off default rpool xattr on default rpool copies 1 default rpool version 3 - rpool utf8only off - rpool normalization none - rpool casesensitivity sensitive - rpool vscan off default rpool nbmand...

...default zhome/username shareiscsi off default zhome/username xattr off temporary zhome/username copies 1 default zhome/username version 3 - zhome/username utf8only off - zhome/username normalization none - zhome/username casesensitivity sensitive - zhome/username vscan off default zhome/username nbmand off def...

...default data/mysqldata3 shareiscsi off default data/mysqldata3 xattr on default data/mysqldata3 copies 1 default data/mysqldata3 version 3 - data/mysqldata3 utf8only off - data/mysqldata3 normalization none - data/mysqldata3 casesensitivity sensitive - data/mysqldata3 vscan off default data/mysqldata3 nbmand off default data/mysqldata3...

...ount on default home1/willm1 shareiscsi off default home1/willm1 xattr on default home1/willm1 copies 1 default home1/willm1 version 1 - home1/willm1 utf8only off - home1/willm1 normalization none - home1/willm1 casesensitivity sensitive - home1/willm1 vscan off default home1/willm1 nbmand off default home1/willm1 sharesmb...

Hello all, I''ve tried changing all kinds of attributes for the zfs''s, but I can''t seem to find the right configuration. So I''m trying to move some zfs''s under another, it looks like this: /pool/joe_user move to /pool/homes/joe_user I know I can do this with zfs rename, and everything is fine. The problem I''m having is, when I mount

Looking for help regaining access to encrypted ZFS file systems that stopped accepting the encryption key. I have a file server with a setup as follows: Solaris 11 Express 1010.11/snv_151a 8 x 2-TB disks, each one divided into three equal size partitions, three raidz3 pools built from a "slice" across matching partitions: Disk 1 Disk 8 zpools +--+ +--+ |p1| .. |p1| <-

Hello, ZFS is behaving strange on a OSOL laptop, your thoughts are welcome. I am running OSOL on my laptop, currently b124 and i found that the performance of ZFS is not optimal in all situations. If i check the how much space the package cache for pkg(1) uses, it takes a bit longer on this host than on comparable machine to which i transferred all the data. user at host:/var/pkg$ time

...default rpool/export shareiscsi off default rpool/export xattr on default rpool/export copies 1 default rpool/export version 4 - rpool/export utf8only off - rpool/export normalization none - rpool/export casesensitivity sensitive - rpool/export vscan off default rpool/export nbmand off default rpo...

I have Solaris 10 U7 that is exporting ZFS filesytem. The client is Solaris 9 U7. I can mount the filesytem just fine but I am unable to write to it. showmount -e shows my mount is set for everyone. the dfstab file has option rw set. So what gives? Phillip -- This message posted from opensolaris.org

I have a 5-500GB disk Raid-Z pool that has been producing checksum errors right after upgrading SXCE to build 121. They seem to be randomly occurring on all 5 disks, so it doesn''t look like a disk failure situation. Repeatingly running a scrub on the pools randomly repairs between 20 and a few hundred checksum errors. Since I hadn''t physically touched the machine, it seems a