Re: [zfs-discuss] problems accessing ZFS snapshots
Tim On Wed, 30 Jul 2008, Tim Haley wrote: > Ah, ignore my previous question. We believe we found the problem, and filed: > > 6731778 'ls *' in empty zfs snapshot directory returns EILSEQ vs. ENOENT we > get in other empty directories > > Fix will likely go back today or tomorrow and be present in snv_96. > > Thanks for finding this. Thanks for fixing but it also happens if the snapshot directory isn't empty as /.zfs/snapshot holds the name of the snapshot that was taken Thomas - GPG fingerprint: B1 EE D2 39 2C 82 26 DA A5 4D E0 50 35 75 9E ED ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] problems accessing ZFS snapshots
Thomas Nau wrote:
> Dear all.
> I stumbled over an issue triggered by Samba while accessing ZFS snapshots.
> As soon as a Windows client tries to open the .zfs/snapshot folder it
> issues the Microsoft equivalent of "ls dir", "dir *". It get's translates
> by Samba all the way down into stat64("/pool/.zfs/snapshot"*"). The stat()
> call fails with error EILSEQ (Illegal byte sequence). It can easily
> reproduced by
> mybox# /bin/ls /pool/.zfs/snapshot/\*
> *: Illegal byte sequence
>
> Doing the same on the original ZFS the snapshot was taken from everything
> works fine.
>
> BTW, I'm running snv_93.
>
> Any hints on that?
> Thomas
>
> -
> GPG fingerprint: B1 EE D2 39 2C 82 26 DA A5 4D E0 50 35 75 9E ED
> ___
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Ah, ignore my previous question. We believe we found the problem, and filed:
6731778 'ls *' in empty zfs snapshot directory returns EILSEQ vs. ENOENT we
get in other empty directories
Fix will likely go back today or tomorrow and be present in snv_96.
Thanks for finding this.
-tim
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] problems accessing ZFS snapshots
Thomas Nau wrote:
> Dear all.
> I stumbled over an issue triggered by Samba while accessing ZFS snapshots.
> As soon as a Windows client tries to open the .zfs/snapshot folder it
> issues the Microsoft equivalent of "ls dir", "dir *". It get's translates
> by Samba all the way down into stat64("/pool/.zfs/snapshot"*"). The stat()
> call fails with error EILSEQ (Illegal byte sequence). It can easily
> reproduced by
> mybox# /bin/ls /pool/.zfs/snapshot/\*
> *: Illegal byte sequence
>
> Doing the same on the original ZFS the snapshot was taken from everything
> works fine.
>
> BTW, I'm running snv_93.
>
> Any hints on that?
> Thomas
>
> -
> GPG fingerprint: B1 EE D2 39 2C 82 26 DA A5 4D E0 50 35 75 9E ED
> ___
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Interesting. What are the normalization and utf8only property values for the
ZFS file system? I.e., what's the output from
'zfs get normalization,utf8only pool/fs'
-tim
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] problems accessing ZFS snapshots
Dear all.
I stumbled over an issue triggered by Samba while accessing ZFS snapshots.
As soon as a Windows client tries to open the .zfs/snapshot folder it
issues the Microsoft equivalent of "ls dir", "dir *". It get's translates
by Samba all the way down into stat64("/pool/.zfs/snapshot"*"). The stat()
call fails with error EILSEQ (Illegal byte sequence). It can easily
reproduced by
mybox# /bin/ls /pool/.zfs/snapshot/\*
*: Illegal byte sequence
Doing the same on the original ZFS the snapshot was taken from everything
works fine.
BTW, I'm running snv_93.
Any hints on that?
Thomas
-
GPG fingerprint: B1 EE D2 39 2C 82 26 DA A5 4D E0 50 35 75 9E ED
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
