Hi!
I have a problem with the charset in the following scenario:
- OSOL Server with zfs pool und NFS/CIFS shares enabled
- OSX Client with CIFS mounts
- OSX Client with NFSv3 mounts
If one of the clients saves a file with a special character in the
filename like 'äüöß', the other client can not
On 15 Jan 2011, at 13:44, Achim Wolpers wrote:
Hi!
I have a problem with the charset in the following scenario:
- OSOL Server with zfs pool und NFS/CIFS shares enabled
- OSX Client with CIFS mounts
- OSX Client with NFSv3 mounts
If one of the clients saves a file with a special
On Fri, Jan 14, 2011 at 11:32:58AM -0800, Peter Taps wrote:
Ed,
Thank you for sharing the calculations. In lay terms, for Sha256, how many
blocks of data would be needed to have one collision?
Assuming each block is 4K is size, we probably can calculate the final data
size beyond which
Am 15.01.11 14:52, schrieb Chris Ridd:
What are the normalization properties of these filesystems? The zfs man page
says they're used when comparing filenames:
The normalization properties are set to none. Is this the key to my
solution?
Achim
signature.asc
Description: OpenPGP digital
On 15 Jan 2011, at 13:57, Achim Wolpers wrote:
Am 15.01.11 14:52, schrieb Chris Ridd:
What are the normalization properties of these filesystems? The zfs man page
says they're used when comparing filenames:
The normalization properties are set to none. Is this the key to my
solution?
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Peter Taps
Thank you for sharing the calculations. In lay terms, for Sha256, how many
blocks of data would be needed to have one collision?
There is no point in making a generalization and a
the ZFS_Best_Practises_Guide states this:
Keep vdevs belonging to one zpool of similar sizes; Otherwise, as the
pool fills up, new allocations will be forced to favor larger vdevs
over smaller ones and this will cause subsequent reads to come from a
subset of underlying devices leading to
On Fri, 14 Jan 2011, Peter Taps wrote:
Thank you for sharing the calculations. In lay terms, for Sha256,
how many blocks of data would be needed to have one collision?
Two.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick
I could resolve this issue:
I was testing FreeNAS with a raidz1 setup before I decided to check out
Nexentastore and it seems Nexentastore has some kind of problems if the
harddisk array already contain some kind of raidz data. After wiping the discs
with a tool from the Ultimate Boot CD I
The different methods should be chosen based on the types of clients you
expect. Mac and Linux work better with one, and windows works best with
another.
Searching for formkc, etc. should yield some information on which is best
for your purposes.
-B
Sent from my Nexus One.
On Jan 15, 2011 6:17
10 matches
Mail list logo
