Kristof Van Damme wrote: > Hi Tim, > That's splendid! > > In case other people want to reproduce the issue themselves, here is how. > In attach is a tar which contains the 2 files (UTF8 and ISO8859) like the > ones I used in my first post to demonstrate the problem. Here are the > instructions to reproduce the issue: > > Create a zfs filesystem with casesensitivity set to mixed and create one > without this setting. > Unpack the tar outside the pool and try to copy both the files from the tar > on to the zfs fileystem. One (UTF8) will work fine, the other will not. > # zfs create -o casesensitivity=mixed mypool/mixed > # zfs create mypool/normal > # cp UTF8-Köln.txt /mypool/mixed/ > # cp ISO8859-K?ln.txt /mypool/mixed/ > cp: cannot stat `/mypool/mixed/ISO8859-K\366ln.txt': Operation not supported > # cp UTF8-Köln.txt /mypool/normal/ > # cp ISO8859-K?ln.txt /mypool/normal/ > # > > > Kristof/ > Thanks, Kristof
I filed 6783995 file creation sometimes failing within a zfs where casesensitivity=mixed a short while ago. I believe I already have a fix: chinook:~/bugs/nonutf[1016] ls ISO8859-K?ln.txt* UTF8-Köln.txt koeln.tar chinook:~/bugs/nonutf[1016] zfs get casesensitivity tp/timh/mix NAME PROPERTY VALUE SOURCE tp/timh/mix casesensitivity mixed - chinook:~/bugs/nonutf[1017] cp UTF8-K\303\266ln.txt /tp/timh/mix chinook:~/bugs/nonutf[1019] cp ISO8859-K\366ln.txt /tp/timh/mix chinook:~/bugs/nonutf[1021] ls /tp/timh/mix ISO8859-K?ln.txt* UTF8-Köln.txt Still will need some folks to look at the change, though. -tim > ------------------------------------------------------------------------ > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
