On Mon, Aug 06, 2007 at 03:11:26PM +0100, Robert Milkowski wrote: > Hello Ed, > > Thursday, June 14, 2007, 2:42:26 AM, you wrote: > > ER> On Wed, Jun 13, 2007 at 05:27:18PM -0700, Matthew Ahrens wrote: > >> To summarize my understanding of this issue: st_size on directories is > >> undefined; apps/libs which do anything other than display it are broken. > >> However, we should avoid exercising this bug in these broken apps if > >> possible. > >> > >> My question: What apps are these? I heard mention of some SunOS 4.x > >> library. I don't think that's anywhere near important enough to warrant > >> changing the current ZFS behavior. > > ER> As mentioned before, NetBSD's scandir(3) implementation was one. The > ER> NetBSD project has fixed this in their CVS. OpenBSD and FreeBSD's > scandir() > ER> looks like another, I'll have to drop them a line. > > > Does it mean that FreeBSD won't be able to properly mount via nfsv4 from > Solaris 10/ZFS box? Or just that some applications using scandir() > won't work properly...?
Only the latter. All the *BSD distributions have fixed their scandir() libraries in CVS, so if you encounter that a fix is available. The problem is not really NFS related. It would happen locally if you could somehow mount a local ZFS filesystem on your FreeBSD box. > What I'm asking is if FreeBSD nfs client is > depending somehow on this. No. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
