nwsp2 classic gpt support

[fvdw]

Yes you should be able to upgrade to 14-0

The possible problem with physical sector size boundary is not the the system partitions but the byte were /dev/loop1 starts (the offset) if that is not on a physical sector boundary then this problem may arise. I asked mijzelf if we should not use a multiple of 4096 + 1, he said no but maybe he is wrong.

In case writing does not start on a physical boundary then the writing of data to the disk is more time consuming because it has to adapt two sectors instead of one. read more here for example http://www.ibm.com/developerworks/linux ... tor-disks/

I am not sure if this explains what you observe but seeing that read speed is almost ok and write speed is significant reduced makes me think that we have an alignment issue here.

[minibike12]

I can experiment with the offset.
If you can give me spa few different offsets, i will test the performance.


Also, i've upgraded to 14.0
1 weird problem
Public folder is not accesseble.
I've made a new folder with the web interface called private (it is open/public but i needed a name.)
I can access the folder "private" but not the folder "public" that worked before the update.

When using ls /share/1000 i can see both folder (private and public).
The contents are good too.
So it is weird that i can access the folder made with 14.0, but can't access the folder made with 11.0.
See my previous post (bottom page 11) for some screenshots and terminal code.

[fvdw]

did you define also users ? and give them access per shared folder ?

A shared folder can be of type "Public" or " Private". (Don't confuse this with the name of the shared folder)
A "Public" shared folder can be accessed by anyone, you can protect it with a password that and you can access it then as user with name equal to sharename and the password set.
A "Private" folder can not be accessed by anyone. For those folders you can set the r/w rights per user.

ps . be aware that in Linux folder names are case sensitive

For experiment on the offset. I would try the number you have + 1
Ps if you do this you need to format the space again and all data stored there is lost

[minibike12]

I did not define users, and both folders are "Public" (open).
So i should be able to access both folders.

I changed original offset 3686809600 to 3686809601.
Btw, noticed that 3686809600 is not a multiple of 4096 (3686809600/4096=90010.001464)
Maybe that is the problem?
And you said 4096+1, is it +1 on the total, or for each 4096bytes ?
Else it would be 3686809600+90010 ( in this case, but it is not a multiple of 4096, so maybe a other offset is needed).
And this line of code would do it for the new offset?
I guess i don't need to use /tmp/mountpoint first, or is this necessary?

Code: Select all

losetup -o 3686809601 /dev/loop1 /dev/sda
mke2fs -j /dev/loop1
mkdir /share/1000
chmod 777 /share/1000
mount /dev/sda /share/1000
umount /share/1000
reboot (with web interface).

losetup -o 3686809601 /dev/loop1 /dev/sda
mount /dev/sda /share/1000


[fvdw]

on my calculator 3686809600 is a mutiple of 4096 ( 900100*4096 = 3686809600) ??

indeed I meant to use 3686809601 as offset

No need to use tmp mountpoint, you can directly mount it on /share/1000

I don't know why you can not access the share "public".
In a firmware upgrade nothing is done on the data partition nor the nas database. Try to create a third shared folder and see what happens with the other two.
ps which operation system do you use on your pc to access the nwsp2 ?

[minibike12]

Ah, maybe i made a typo...
I will use 3686809601 as offset.
Maybe my public folder will work again after i rebuild the loop partition.

I've used ubuntu 10 or 11 to build the parition table.
And i am using windows 8 pro to ssh and acces the nas.

[fvdw]

And i am using windows 8 pro to ssh and acces the nas.

aha.. that could explain something, nice test to see if windows 8 is compatible with our firmware, until now we could only test it with windows 7 as we don't have windows 8.
Which browser do you use for the webinterface ? fvdw-sl-14-0 is adapted to get compatibility with windows 8 and IE10 (see release notes)
But as said we can not test it on our own pc's. So this is a nice test as well to see how it works in windows 8. So still some bugs may be present

[minibike12]

Windows 8 worked perfectly before the update!
But public folder was not accessable anymore after update to 14.0.
This is when i've made the new folder called "private".

So the folder called "public" made in 11.0 does not work.
Folder called "private" made in 14.0 does work.

I don't think this had to do with the firmware, but with our loop1 partition.
I think the "symbolic" link or something is corrupt.
Because "public" and "private" are both in "/share/1000" and i can both reach them with ls.
All files are still intact.

I am happy to help you with finding windows 8 bugs.
I have access to windows 8, windows 7, ubuntu and osx 10.6.8 operating systems here at home.

[fvdw]

Windows 8 worked perfectly before the update!
But public folder was not accessable anymore after update to 14.0.
This is when i've made the new folder called "private".

So the folder called "public" made in 11.0 does not work.
Folder called "private" made in 14.0 does work.

I don't think this had to do with the firmware, but with our loop1 partition.
I think the "symbolic" link or something is corrupt.
Because "public" and "private" are both in "/share/1000" and i can both reach them with ls.
All files are still intact.

which browser did you use in windows 8 before upgrading to 14-0 ?

about the "public" folder this is strange. As said create a a third folder and see what happens with the previous ones. Just to check if creating a new folder cause this problem.
As the samba server is controlling the access to shared folders most likely something could be not properly set in the samba configuration file. Or the permission of the folder /share/1000/public are reset (try the chmod 777 command). However all this should not be necessary. This part should just work out of the box.
ps If you remove a shared folder with the web interface it will delete the content as well. If there is a problem with a folder and you want to recreate it then rename the folder first via ssh (command line), then delete the shared folder via the webinterface, recreate it in the web interface and then rename the folder back via ssh (command line) to the original name. Then the content will still be there

[Jocko]

aha.. that could explain something, nice test to see if windows 8 is compatible with our firmware, until now we could only test it with windows 7 as we don't have windows 8.
Which browser do you use for the webinterface ? fvdw-sl-14-0 is adapted to get compatibility with windows 8 and IE10 (see release notes)
But as said we can not test it on our own pc's. So this is a nice test as well to see how it works in windows 8. So still some bugs may be present

Hi both,

Remember fvdw I tested our firmware on a virtual host with win8 OS without any trouble : I can create, delete samba shares and access to samba shares (created before vers14.0 or after). Think may be there is an error in the file /tmp/usr/lib/smb.conf. (but why ?)

(before 14.0 there is only some compatibility issue with some browsers like IE or Chrome)

---edit---
I just created a new share with my virtualhost win8 and no trouble in smb.conf and the folders permissions into '/share/1000' are OK