Buffalo Forums

Files stored on the TS ProII in  a RAID 5 setup suddenly briefly become read only. This causes problems with Access for example, and other files that require constant read-write access. Sometimes Excel files open as read only, meaning that when you come to save them, you can't overwrite the original. Most of the time its fine, and it has worked OK for at least 1 year. I have done Raid scans and disk checks and whenever there have been errors detected, they have been repaired by the system. I occasionally get a disk error 5 on the daily "Terastation Status" email - don;t know if this links, but that always repairs OK!!

Somebody pls help

Taken from a reply to a previous post:

Put simply the ability to save files simply by writing the data to the  disk has become more complicated than it used to be.  Most applications  that save data will use an API and "instruct how the file should be  written".  Since this device utilizes a Samba kernel it would be much  along the same lines as trying to have MS Word instruct Linux using APIs  to save a file to hard disk.  Linux cannot understand these commands  and these NAS devices cannot be "reworked" to be able to accept MS API  file instruction.  The long and short of it is these devices cannot have  the data saved directly to them, you will need to save the file locally  (on a workstation) and then transfer it to the NAS.

Thanks for your help on that

Does that mean that to use a Terastation Pro (model no: TS-HTGL/R5 F/W 1.33) as a kind of file server is not appropriate?? Or, to do so, we need to transfer files locally, and then open / modify / close them there, before moving them back to the TS?

One other point, does the fact that the trashbox facility is switched on make any difference. May that make matters worse??

Is there any guidance on this sort of think and/or the proper use of Terastaion NAS drives (or NAS drives in general)??

Cheers

Well since APIs are involved more often with most software (especially PC based) it gets dicey on what can be saved directly vs. what can be saved locally and then needs to be moved.  General advice I can give would be to try saving directly and if the file doesn't exhibit any problems (i.e. reading or writing to/from it) then all should be well.  However, if problems crop up after making changes to the file then I would say save locally and backup the info to the NAS.