DriveStation FlexNet - NAS Mode - Filename Wildcards Don't Work Right

[eroesinger]

   Model Name: HD-CELU2
Firmware Version: BUF-CELU2-1.4.7 LOADER 3.5W1.9

With current working drive/directory directed to the unit's share:

 

echo blah > a.b
echo blah > a.c
echo blah > d.e
echo blah > f.e

creates files as expected, and:

 

del a.*

works, but:

 

del *.e

fails, reporting that file "*.e" is "not found". Failure occurs from both XP and Vista hosts.

The same operations all work on a "real" SMB share.

--
egr

[Dustrega]

We've experienced issues regarding command line interface commands as a problem with this unit. Mkdir and your wildcard issue have been noted and we're looking into it.

[eroesinger]

   Thanks for the ACK; now for another ENQ (assuming that isn't a "SYN", here): can you post a link, in this thread, to anything on the mkdir issue, as well as to anything else relevant to wildcard and/or shell filename completion issues? Guessing the right search keywords doesn't seem to be my forté.

Once I know where the right threads "live", I'll want to read them, and possibly repost relevant data from this post there.

Regarding filename completion: that it seems to work better with rooted, rather than relative paths might shed some light on root cause for both it and for wildcard problems.

Also, I may also have observed the mkdir issue and/or something similar/related: in particular, I'm seeing "the operation is not supported" in error messages, and this may be dependent on particular (perfectly legal) characters in the directory pathname. One suspect may be the '%' character, which a number of apps (most painfully, Cygwin setup) use to URLencode network pathnames for representation within the filesystem. Interestingly, these paths copy fine when using Explorer; but XCOPY and a number of other apps (that may be using an older API call--just a guess, as it's been a while since I've poked through those parts of the Windows SDK documents) choke on them.

"FIN"ally, would a wild guess that the FlexNet uses a Linux-based SaMBa implementation "under the hood" of the NAS point toward root cause and/or solutions of any of the issues?

--
egr

[Dustrega]

You are correct in your assumption that this device is utilizing a Samba kernel however it is really scaled down but does have a few limitations in that respect. We have also seen issues with http://forums.buffalotech.com/buffalo/board/message?board.id=0101&message.id=7440#M7440" target=_blank>XCOPY where bits were corrupted on a LinkStation Quad but not on a TeraStation (I think this might be related to the Samba version) and have suggested the use of Robocopy in such a case. To sum up what we're looking into definitive fixes for these problems but have yet to come across a solution to be released in the form of a firmware update.