Raikeen Posted June 3 Share Posted June 3 Hi to all. I'm having problems with ZFS Snapshot 6.12.10 because have directory with non utf8 character, and when I doing the Snapshot create a temporaly files with error that finished in _temp. I see for other publications that the problem its the UTF8 codification in ZFS, that have a property utf8only=on, that need to create another dataset with uft8only=false, but when I created with "zfs create -o utf8only=off pool_name/new_dataset" or similar "zpool create -o utf8only=off pool_name /path/to/disks" "zfs create -o normalization=formD pool_name/new_dataset" and later use "zfs get utf8only pool_name/new_dataset" to see the property it's created with otf8only=on, and the error in snapshot continue. How I can change to utf8only=false/off to avoid problem in Snapshot? Quote Link to comment
JorgeB Posted June 3 Share Posted June 3 41 minutes ago, Raikeen said: zfs create -o utf8only=off pool_name/new_dataset I believe this should work, can you post an actual example? Quote Link to comment
Raikeen Posted June 3 Author Share Posted June 3 12 minutes ago, JorgeB said: I believe this should work, can you post an actual example? Thx for repply Quote Link to comment
JorgeB Posted June 3 Share Posted June 3 Hmm, it works for me: Do you have normalization set to none? I believe that's required to be possible to disable utf8only. Quote Link to comment
Raikeen Posted June 3 Author Share Posted June 3 No, How I do? with this? "zfs create -o normalization=formD pool_name/new_dataset" Quote Link to comment
Raikeen Posted June 3 Author Share Posted June 3 Now with this "work" I test with the Snapshot If have error now with utf8 in off Quote Link to comment
Raikeen Posted June 3 Author Share Posted June 3 the dataset converter continues to fail with normalization to none and utf8 off Creating and populating new dataset disk3/test/a/tést... cannot create 'disk3/test/a/tést: invalid character '�' in name cannot create 'disk3/test/a/[Ñ] ': invalid character '[' in name Any solution to this? Quote Link to comment
JorgeB Posted June 4 Share Posted June 4 Post the output of zfs get all pool/dataset Quote Link to comment
Raikeen Posted June 4 Author Share Posted June 4 NAME PROPERTY VALUE SOURCE disk3/test type filesystem - disk3/test creation Mon Jun 3 23:13 2024 - disk3/test used 96K - disk3/test available 4.04T - disk3/test referenced 96K - disk3/test compressratio 1.00x - disk3/test mounted yes - disk3/test quota none default disk3/test reservation none default disk3/test recordsize 128K default disk3/test mountpoint /mnt/disk3/test inherited from disk3 disk3/test sharenfs off default disk3/test checksum on default disk3/test compression off inherited from disk3 disk3/test atime off inherited from disk3 disk3/test devices on default disk3/test exec on default disk3/test setuid on default disk3/test readonly off default disk3/test zoned off default disk3/test snapdir hidden default disk3/test aclmode discard default disk3/test aclinherit restricted default disk3/test createtxg 192375 - disk3/test canmount on default disk3/test xattr sa inherited from disk3 disk3/test copies 1 default disk3/test version 5 - disk3/test utf8only off - disk3/test normalization none - disk3/test casesensitivity sensitive - disk3/test vscan off default disk3/test nbmand off default disk3/test sharesmb off default disk3/test refquota none default disk3/test refreservation none default disk3/test guid 7652998764921562179 - disk3/test primarycache all default disk3/test secondarycache all default disk3/test usedbysnapshots 0B - disk3/test usedbydataset 96K - disk3/test usedbychildren 0B - disk3/test usedbyrefreservation 0B - disk3/test logbias latency default disk3/test objsetid 208 - disk3/test dedup off default disk3/test mlslabel none default disk3/test sync standard default disk3/test dnodesize auto inherited from disk3 disk3/test refcompressratio 1.00x - disk3/test written 96K - disk3/test logicalused 42K - disk3/test logicalreferenced 42K - disk3/test volmode default default disk3/test filesystem_limit none default disk3/test snapshot_limit none default disk3/test filesystem_count none default disk3/test snapshot_count none default disk3/test snapdev hidden default disk3/test acltype posix inherited from disk3 disk3/test context none default disk3/test fscontext none default disk3/test defcontext none default disk3/test rootcontext none default disk3/test relatime off default disk3/test redundant_metadata all default disk3/test overlay on default disk3/test encryption off default disk3/test keylocation none default disk3/test keyformat none default disk3/test pbkdf2iters 0 default disk3/test special_small_blocks 0 default The Output, thx for repply Quote Link to comment
JorgeB Posted June 4 Share Posted June 4 12 hours ago, Raikeen said: the dataset converter continues to fail with normalization to none and utf8 off I missed that it still happened with both disabled, but AFAIK those properties only control what you can write inside the dataset, the dataset name itself cannot have any special characters. Quote Link to comment
Raikeen Posted June 4 Author Share Posted June 4 Sorry what its AFAIK? Is there no way for the dataset to have special characters in the name to take snapshots? I was seeing that in the next version 6.13 it will have snapshot natively, but I couldn't find a beta to test, do you know if snapshots with special characters will be allowed in this version? Thx Best Regards Quote Link to comment
JorgeB Posted June 4 Share Posted June 4 8 minutes ago, Raikeen said: Is there no way for the dataset to have special characters in the name to take snapshots? Not as far as I know (AFAIK) Quote Link to comment
Solution JorgeB Posted June 4 Solution Share Posted June 4 https://docs.oracle.com/cd/E26505_01/html/E37384/gbcpt.html Each ZFS component, such as datasets and pools, must be named according to the following rules: Each component can only contain alphanumeric characters in addition to the following four special characters: Underscore (_) Hyphen (-) Colon (:) Period (.) Pool names must begin with a letter, and can only contain alphanumeric characters as well as underscore (_), dash (-), and period (.). Note the following pool name restrictions: The beginning sequence c[0-9] is not allowed. The name log is reserved. A name that begins with mirror, raidz, raidz1, raidz2, raidz3, or spare is not allowed because these names are reserved. Pool names must not contain a percent sign (%). Dataset names must begin with an alphanumeric character. Dataset names must not contain a percent sign (%). In addition, empty components are not allowed. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.