|
Its unlikely to be that simple, with filesystems the usual culprit is not an unsupported call, but a pattern of calls that has some side-effect that is not supposed to happen. So you do calls X Y Z and they work fine on filesystem's A B C but cause errors with filesystem M.
Filesystem semantics really are not designed for remote storage, all the various efforts to shoehorn neetworks into filesystem layers sooner or later trip up against this.
|