Performance/Admin Page Access - Does available disk space affect access to the ReadyNas

Hi,


Sorry for the delayed response, but here is the latest.  I copied data from the NAS that I wanted to keep, then performed a factory reset.  The factory reset took around 4 hours to fully initialize the drives. (2 X 1TB.)  The following are from the logs:


Disk /dev/hde doesn't contain a valid partition table

Disk /dev/hdc: 999.9 GB, 999991611392 bytes
255 heads, 63 sectors/track, 121575 cylinders, total 1953108616 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1              32     4096031     2048000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/hdc2         4096032     4608031      256000   82  Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdc3         4608032  1953092263   974242116    5  Extended
/dev/hdc5         4608040  1953092263   974242112   8e  Linux LVM

Disk /dev/hde: 999.9 GB, 999991611392 bytes
255 heads, 63 sectors/track, 121575 cylinders, total 1953108616 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000


===== dumpe2fs /dev/c/c =====
dumpe2fs 1.40.11 (17-June-2008)
Filesystem volume name:   c
Last mounted on:          <not available>
Filesystem UUID:          689eab2f-f32b-493e-9513-ad422fc6c899
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:         signed_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              30310400
Block count:              60561408
Reserved block count:     0
Free blocks:              60051222
Free inodes:              30310384
First block:              0
Block size:               16384 ********
Fragment size:            16384 ********
Reserved GDT blocks:      127
Blocks per group:         65528
Fragments per group:      65528
Inodes per group:         32768
Inode blocks per group:   512
Filesystem created:       Fri Sep  9 06:07:12 2016
Last mount time:          Fri Sep  9 06:14:32 2016
Last write time:          Fri Sep  9 06:14:32 2016
Mount count:              3
Maximum mount count:      -1
Last checked:             Fri Sep  9 06:07:12 2016
Check interval:           0 (<none>)
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:          256
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      8a17c6bb-817d-442a-bba8-031a38365558
Journal backup:           inode blocks
Journal size:             512M


NAS performance tester 1.7 http://www.808.dk/?nastester
Running warmup...
Running a 400MB file write on \\nas\backup 5 times...
Iteration 1:      7.59 MB/sec
Iteration 2:     17.91 MB/sec
Iteration 3:     18.36 MB/sec
Iteration 4:     18.17 MB/sec
Iteration 5:     18.17 MB/sec
-----------------------------
Average (W):     16.04 MB/sec
-----------------------------
Running a 400MB file read on \\nas\backup 5 times...
Iteration 1:     17.79 MB/sec
Iteration 2:     19.62 MB/sec
Iteration 3:     19.51 MB/sec
Iteration 4:     19.06 MB/sec
Iteration 5:     27.68 MB/sec
-----------------------------
Average (R):     20.73 MB/sec
-----------------------------


The surprising this is after I formatted, the backups took longer than it did the previous weeks.  I verified that all links between the NAS and the server are 1Gbps.  The NAS itself has autonegotiated the connection speed to 1000Mbit / Full Duplex according to the dashboard.  The switch has also reported a 1Gbps link.  There are 3 switches in the connection; the switch that the NAS is connected to, a stack of 4 switches connected via a backplane and another switch connecting the servers to the stack.


I'm not sure why it would be slower this week than previous weeks though.


Any ideas?

Thanks.