Hello, On Sat, Jul 11, 2009 at 02:23:28AM +0200, olafbuddenha...@gmx.net wrote: > On Wed, Jul 08, 2009 at 03:41:51PM +0300, Sergiu Ivanov wrote: > > > I also checked the implementation of fsys_forward in libdiskfs and > > found that it returns EOPNOTSUPP. Since libdiskfs usually has all > > necessary stuff implemented properly (as different from libnetfs and > > libtrivfs), I'd say we can forget about this RPC as well. > > fsys_forward() is only implemented by translators that accept > forwarding. For disk filesystems, that's probably never the case, so > it's quite expected that libdiskfs doesn't handle it.
Since I have a rather vague understanding of the notion of ``forwarding'', I'll take your position as the true one, and remember it for future use :-) > The question is whether it makes sense ever to union-mount any of the > translators supporting forwarding. That's probably not the case for the > currently existing use cases of fsys_forward(), but I can't say that it > will never ever be useful. > > So I stand by what I said before: If it seems trivial to forward it, do > so; otherwise, ignore it. OK. I'll try to forward the call completely. Regards, scolobb
