nwsp2 classic gpt support

[Mijzelf]

Could losetup/mk2efs set something that could make that when accessing the disk always the offset is used ?

I don't know what you mean. You'll always have to losetup with the same offset.

Shouldn't then the offset not be a mutiple of 4096 + 1
Now it will start at the end byte of a physical sector. That will affect performance of these disk I read on the internet

Offset 0 is the start of the disk. (Sector 0). So offset 4096 is the start of sector 1

You mean the offset of 3686809600?
This is the offset you and fvdw recommended.

Yes, that value is imposed by the way the firmware is setup. But that doesn't necessarily mean losetup can read that value correct. But

Code: Select all

/dev/loop1           2880742272    205940 2734203024   0% /rw_fs/tmp/mountpoint

Code: Select all

Disk /dev/sda: 3000.5 GB, 3000592982016 bytes

Which means an offset of 50712895488 is being in effect? I must be missing something.

[fvdw]

when it has been mounted
create a folder with name public within /share/1000

Code: Select all

mkdir /share/1000/public
chmod 777 /share/1000/public

If you now connect to the nas-ip in explorer (verkenner) then you should see this public folder
In the web interface you can now create more shared folders

[fvdw]

So in this order?

Code: Select all

losetup -o 3686809600 /dev/loop1 /dev/sda
mkdir /share/1000
chmod 777 /share/1000
mount /share/1000


yes in this order but use for mount

Code: Select all

mount /dev/loop1 /share/1000

ps creating /share/1000 should only be necessary once at next reboot it will still be there

did it boot ?

[fvdw]

But

Code: Select all
/dev/loop1 2880742272 205940 2734203024 0% /rw_fs/tmp/mountpoint

Code: Select all
Disk /dev/sda: 3000.5 GB, 3000592982016 bytes

Which means an offset of 50712895488 is being in effect? I must be missing something.

yes you miss something, first df is output is in 1K blocks so the size is 2949880086528 bytes
Furthermore when creating a ext3 file system some space is reserved for superuser (a few %, don't know the number by head, thats why we specify in the how to guide a the -m 1 option to limit this space to 1%)

--edit
from man page mke2fs
-m reserved-blocks-percentage
Specify the percentage of the filesystem blocks reserved for the super-user. This avoids fragmentation, and allows root-owned daemons, such as syslogd(8), to continue to function correctly after non-privileged processes are prevented from writing to the filesystem. The default percentage is 5%.

[minibike12]

Yes it did boot

Code: Select all

login as: root
root@192.168.1.142's password:
root@fvdwsl-base:/ # losetup -o 3686809600 /dev/loop1 /dev/sda
root@fvdwsl-base:/ # mkdir /share/1000
mkdir: cannot create directory `/share/1000': File exists
root@fvdwsl-base:/ # chmod 777 /share/1000
root@fvdwsl-base:/ # mount /dev/loop1 /share/1000
root@fvdwsl-base:/ #


/share/1000 already existed.
When i go to my nas-ip in browser and click on "System Information"
I get an pie chart that says this :

Code: Select all

Total Storage:   0 MB
Available Storage:   0.00 GB


But, under the pie chart
it says this :
Does this mean succes?

Code: Select all

Share Name   Volume   Total Size   Free Size   Public   Samba   FTP
public   Default   2747.29 GB   2607.54 GB   Yes   Yes   No


P.s.
When entering the nas-ip in me explorer (verkenner)
It opens my browser with the web interface.

[fvdw]

yes it means success :punk

The pie chart is trying to find sda8

But I need to go now because visitors for Christmas arrived. To be continued tomorrow

[minibike12]

Nice!

When entering "\\fvdwsl-base" in me explorer (verkenner)
It opens the drive with the "public" folder.
But when double click it, it says, "Windows cannot access \\fvdwsl-base\public"
So no access to the folder yet...
How van i fix this?

Edit
Forgot this part, hehe

Code: Select all

mkdir /share/1000/public
chmod 777 /share/1000/public


Did this, and i am now able to access \\fvdwsl-base\public

Now just fix the startup script, and we are done i guess.

Have fun, and merry Christmas!

Edit 2
Hmm, uploadspeed is terrible.
Only 8mb/s
And uploading a file to the disk pauses every 2 seconds for about half a second.
Is there a way to increase this speed.
Writing a 12GB file to the drive takes >35minutes :shock:
Out network is 100% Gbit btw.

Read is an steady 20mb/s.
Not very spectacular, but a lot better than 8mb/s write.
Read is steady, instead of the small breaks while copying.

I am getting upload (write) speeds of +25mb/s with the original 1TB seagate drive.

Oh and i noticed that i doesn't go in standy automatic after a certain amount of time.
How can i fix this, i do need the standby function.

[fvdw]

In between the afternoon drinks and dinner a quick reaction

Edit 2
Hmm, uploadspeed is terrible.
Only 8mb/s
And uploading a file to the disk pauses every 2 seconds for about half a second.
Is there a way to increase this speed.
Writing a 12GB file to the drive takes >35minutes :shock:
Out network is 100% Gbit btw.

This not normal. I achieve 25 MB/s upload speeds.
But for big files, many small files like pictures are much slower because of file header writing and so on.
If you have a file of lets say 1 GB it should achive the speed I mentioned.
See for instance this topic viewtopic.php?f=4&t=805 (we use samba 3.0.24 , in version 14-0 this will be 3.0.39 but that has same performance as 3.0.24)

If not then I think the start byte is not on a physical sector boundary. On advanced format disk this can seriously degrade performance (see internet) Thats also the reason why fdisk complained when choosing partition begin and end not being on physical sector boundary.

But this can be solved by finding the appropriate start byte

Oh and i noticed that i doesn't go in standby automatic after a certain amount of time.
How can i fix this, i do need the standby function.

yes it will go to standby (the hard disk) after 15 minutes of inactivity. In fvdw-sl-14-0 you can set the period.

[Mijzelf]

Can you have a look with

Code: Select all

tune2fs -l /dev/loop1

to see if the used blocksize of the filesystem is a multiple of 4k? Theoretically it could be 2k for a 3TB partition, which should have impact on write speed.
And do also a simple speed test:

Code: Select all

dd if=/dev/zero of=/share/1000/public/bigfile bs=1M count=1k

This will write a 1GiB file, and tell you the write speed.

[minibike12]

@fvdw
8mb/s was with an single 12GB file.
and the fdisk partition errors that the startbyte not in physical sector boundary was, were gone with this partition table.
Shouldn't be the problem now?

And thanks for the info on standby time.

This is tune2fs -l /dev/loop1

Code: Select all

root@fvdwsl-base:/ # tune2fs -l /dev/loop1
tune2fs 1.41.14 (22-Dec-2010)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          457aaab8-010d-42a1-8f2c-8cc21d879631
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         unsigned_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              182919168
Block count:              731666546
Reserved block count:     36583327
Free blocks:              716973354
Free inodes:              182919142
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      849
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Tue Dec 25 02:08:03 2012
Last mount time:          Tue Dec 25 14:59:18 2012
Last write time:          Tue Dec 25 14:59:18 2012
Mount count:              4
Maximum mount count:      30
Last checked:             Tue Dec 25 02:08:03 2012
Check interval:           15552000 (6 months)
Next check after:         Sun Jun 23 02:08:03 2013
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      85dffcc1-95c6-4e7d-bb26-8c9559fe46c0
Journal backup:           inode blocks
root@fvdwsl-base:/ #


Hmm, this is not giving me any information except for 1024+0 records in and out.

Code: Select all

dd if=/dev/zero of=/share/1000/public/bigfile bs=1M count=1k


I have added an screenshot.
I am copying a single 8.5GB mkv file.
Writespeed 7mb/s
Any other options?

Furthermore.
Upgraded to firmware 14.0.
Now my access is gone.
/dev/loop1 is mounted.
And ls is showing my public folder.
I even made an new folder named private (it is open)
but only the public folder shows up in my explorer.
ls shows both public and private folder.

Code: Select all

root@fvdwsl-base:/ # ls /share/1000
lost+found  private  public
root@fvdwsl-base:/ #


Edit what is this trickery :scratch
Now my explorer is showing both public and private folder.
I am able to access my private folder, but still not my public folder? ...
Pic added

This is mount and df command

Code: Select all

root@fvdwsl-base:/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,errors=continue,barrier=0,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
/dev/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
/dev/loop1 on /share/1000 type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
root@fvdwsl-base:/ # df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root               247968    162232     72936  69% /
/dev/sda1               247968    162232     72936  69% /
/dev/sda5               822216     17500    796364   2% /rw_fs
tmpfs                     5000       172      4828   3% /rw_fs/tmp/usr/var
/dev/root               198368    126044     62084  67% /lacie-boot
/dev/loop1           2880742272  13898464 2720510500   1% /share/1000