NASLite Network Attached Storage

Hi:

Testing Windows Vista with NAS-Lite USB v2.03.

Mapped "Z:\" to "<ip>\Shares". Three disk drives ... Disk-2 has 43GB available. Copying a 1.6GB file from one sub-folder to another triggers an error message as follows. This does not happen under WinXP.

There is not enough space on NAS. You need an additional 1.54GB to copy these files. NAS space free: 3.68MB Total size: 7.74MB

Obviously this is the capacity of the NASLite USB boot drive.

This message will not come up if I map just Disk-2 to (for example) "X:" and try the copy again underneath of "X:\".

Is this issue fixed on v2.04 ?

Thanks,
Georg

This behavior is correct since the root of the shares share is a different filesystem than the actual storage drives. Windows incorrectly assumes that the size of the shares root is representative of the entire storage area.

Changing this behavior on the NASLite end will be unsafe. For example, let's say that there are a 10G and a 20G drive installed in the server for a total of 30G. Saving a 20G file will then be permitted to the 10G drive, however the transfer will fail due to lack of space.

Tony:

Your example makes sense ... but I don't think it addresses the issue. Remember I said "This does not happen under WinXP." Your example would make sense if it applies to any client O/S.

Also see http://www.serverelements.com/phpBB2/viewtopic.php?t=1594. Therein gaiden says "Edit: versions 1.5 and 2.0 do not have this error." ... is it possible that the issues are related and apply to Vista (as a client) in v2.03 (that I use) ?

Edit: never mind the second paragraph ... I just reviewed the post and realized the NAS version in that case is the the floppy version ... but I still wonder why XP does not exhibit the behaviour.

Georg

This has been noted in XP as well. see http://www.serverelements.com/phpBB2/vi ... 8a92fcb88e

Ok ... thanks gaiden. I do understand what Tony is saying and that NASLite's behaviour should not be changed to something that results in an unstable system ... HOWEVER ...

I must report that MY WinXP does NOT exhibit this problem, only my Windows Vista !

(Yes, my WinXp also exhibits the low 3.68MB DiskFreeSpace information (at the bottom of the Windows Explorer window) when pointing to Z:\ in Windows Explorer or ANY "Disk-x" folder, or sub-folder or sub-sub-folder (etc), but it does NOT cause the problem of the "out of space" message when copying anywhere underneath Z:\ (which is mounted in both XP and Vista as "\\Maestro\Shares"). Only Windows Vista causes this issue. This issue results in my having to map each Disk-X to a separate drive letter in Windows Vista (!) ... a major inconvenience and inconsistency.)

Anyone else see this difference ?

Georg

I have this problem too.
I have about 10 win Xp computers connected to my 3 NASlite 2.0 servers.
They all work fine when using the shares: share. I can read and write any filesize. It even fails when the disks are full.
But when writing under Vista I cannot write files anymore. The I need to use the disk-x shares to be able to write. Else I only get not enough space. Just the size of the ram disk it seems.
This is a major drawback. Since I have 3 servers with 4 disks in each that means 12 driveletters spent instead of 3.I am planning to expand with one more server but I don't hava to many driveletteres left now...

It all WORKED FINE under XP.

I get the same issue under Mac OS X too.

As /Shares, there is no reporting of how much space is available on each drive compared to /Disk-? which does report the space.

I don't think this was an issue under v2.02.

This is the correct behavior, even under OSX, reread Tony's explanation.

I just upgraded from XP to Vista and run into the same issue. Copying onto the shares was fine in XP, but doesn't work in Vista any more. I wished there was a solution, but I guess not...

Dirk