reporting incorrect remaining space

Discussion of bugs and problems found in Altap Salamander. In your reports, please be as descriptive as possible, and report one incident per report. Do not post crash reports here, send us the generated bug report by email instead, please.
Anne
Posts: 19
Joined: 09 Mar 2006, 00:10
Location: Florida

reporting incorrect remaining space

Post by Anne » 19 Apr 2016, 02:51

Salamander is showing 29MB of space remaining on all of my server drives while there is TB's available on each drive.
Example,, one drive properties show 1.54TB..?. while when I try to use the drive it says I have 29MB
The result is that I can no longer move files to any drive because Salamander is reporting not enough capacity (only 29MB) ??????
Anne

Jan Rysavy
ALTAP Staff
ALTAP Staff
Posts: 5196
Joined: 08 Dec 2005, 06:34
Location: Novy Bor, Czech Republic
Contact:

Re: reporting incorrect remaining space

Post by Jan Rysavy » 19 Apr 2016, 09:20

Please let us know more about your setup. What Altap Salamander version are you using? What Windows version?

Is Salamander reporting wrong free space only on network drives (you are talking about server)?
What server is it and how do you access it (operating system, network protocol).

It would also help to post screenshot to show us the problem. It is possible to attach PNG image to the post.

Anne
Posts: 19
Joined: 09 Mar 2006, 00:10
Location: Florida

Re: reporting incorrect remaining space

Post by Anne » 19 Apr 2016, 22:17

The server is a Dlink DNS 323 upgraded to Alt-F software.. Only on the server drives report incorrect information, Operating system is Windows 7 Ultimate. I correctly access the drives through Windows 7 as network attached drives..... The drives are attached as network drives on Salamander. I can "read" any amount of data through Salamander regardless of what drive size is indicated. I can NOT write through Salamander unless the size of the file is less than 29MB...
A.png
A.png (512.6 KiB) Viewed 5046 times
The server drives are ext4 formatted.
C.png
C.png (498.21 KiB) Viewed 5046 times
Attachments
B..png
B..png (598 KiB) Viewed 5046 times

therube
Posts: 628
Joined: 14 Dec 2006, 06:22

Re: reporting incorrect remaining space

Post by therube » 20 Apr 2016, 02:45

WAG


"By the way, the DNS-323 can support up to 3TB of disk space with the new firmware update. That's 1.5TB per disk! Could you imagine such capacity twenty years ago?"
https://www.ifixit.com/Teardown/D-Link+ ... rdown/2084

So maybe the drive had to use some (software-based) "drive translation software" in order to recognize larger (1.5 TB in this case) drives, & for whatever reason Salamander is not interpreting it correctly. (But you would think Salamander would query via system calls, in which case it should "just work".)


Maybe if the drive is turned on prior to booting the OS instead of after ... ?
Last edited by therube on 20 Apr 2016, 06:42, edited 1 time in total.
WinXP Pro SP3 or Win7 x86 | SS 2.54

Anne
Posts: 19
Joined: 09 Mar 2006, 00:10
Location: Florida

Re: reporting incorrect remaining space

Post by Anne » 20 Apr 2016, 02:59

Hi guys....
Just to let you know... with Alt-F installed on the DNS-323 it can handle 4TB drives !!!

Anne

Anyone got a work around for this problem ????? or maybe even a fix ???

Jan Rysavy
ALTAP Staff
ALTAP Staff
Posts: 5196
Joined: 08 Dec 2005, 06:34
Location: Novy Bor, Czech Republic
Contact:

Re: reporting incorrect remaining space

Post by Jan Rysavy » 20 Apr 2016, 08:42

Thank you for posted screenshots. Btw, it is possible to take screenshot using Altap Salamander:
1. open window you want to capture
2. press PrtScn on your keyboard (for whole screen) or Alt+PrtScn (for active window) to capture screenshot to Windows clipboard
3. start Salamander and choose Plugins > PictView > View Bitmap from Clipboard (Ctrl+Shift+B)
4. screenshot will be displayed in PictView window, save it to PNG

Another option is to use Windows Paint for steps 3. and 4. - so you don't need Salamander / PictView plugin, see http://www.sevenforums.com/tutorials/97 ... paint.html

Back to free space problem. Could you please post more screenshots?
1. Altap Salamander Drive information window for DNS-323 drive (to open it press Ctrl+F1 in Salamander).
2. Windows Explorer window with Computer item selected - there is list of all mapped drives with disk size displayed.
3. Windows Properties dialog box for DNS-323 network drive - first General page with disk size displayed. (open it by right-clicking disk in Windows Explorer and choosing Properties command)

Thank you.

User avatar
SvA
Posts: 461
Joined: 29 Mar 2006, 02:41
Location: DE

Re: reporting incorrect remaining space

Post by SvA » 20 Apr 2016, 13:18

By the way, did you notice there is a "Yes" button on the dialog as a response to the question "Do you want to continue?"

Salamander does not use the initially calculated free space during copying. If the space indeed is running out, the remote system will report a write failure. If, regardless, the space is sufficient, either because the initial report was wrong, or because you created some more space while the copy process is under way, e.g. by deleting some files, salamander will successfully copy the whole lot.

Of course the matter needs to be investigated and fixed, but until then, just press "Yes".

Anne
Posts: 19
Joined: 09 Mar 2006, 00:10
Location: Florida

Re: reporting incorrect remaining space

Post by Anne » 21 Apr 2016, 22:04

PROBLEM SOLVED !!!!.... MY error.... I forgot you can not create a share to \mnt and have it report correct disk info !! ---You can read everything below the \mnt , but disk info is for that point only.
......As soon and I created my share to the individual disk \mnt\sda everything is good and all disk info is correct...
....My THANKS to -- João Cardoso at Alt-F -- for kicking my brain into gear... Hope this long description helps someone else. Anne

Post Reply