NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Performance/Admin Page Access - Does available disk space affect access to the ReadyNas
Hi, I have a ReadyNAS NV+ and it has been running well for a while. A while back, I got a warning about the fan failing so I took the NAS out of commission for a while and got a replacement fan....
Are you using jumbo frames on your network?
It is a bit odd that you can't change the MTU. Perhaps try turning jumbo frames off, and do another test.
===== dumpe2fs /dev/c/c ===== dumpe2fs 1.40.11 (17-June-2008) Filesystem volume name: c Last mounted on: <not available> Filesystem UUID: e4456484-0503-4c24-81a8-39ecdaf52923 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: not clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 30310400 Block count: 60561408 Reserved block count: 0 Free blocks: 32902557 Free inodes: 30308588 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: 256 Filesystem created: Thu Jan 20 16:00:26 2011 Last mount time: Tue Sep 6 13:25:01 2016 Last write time: Tue Sep 6 15:15:03 2016 Mount count: 5 Maximum mount count: -1 Last checked: Mon Nov 30 08:14:16 2015 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: tea Directory Hash Seed: aa818a31-d661-43ed-a6ac-44aac4a2485b Journal backup: inode blocks Journal size: 512M
Looks like my block size is 14384.
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 2 4096001 2048000 83 Linux Partition 1 does not end on cylinder boundary. /dev/hdc2 4096002 4608001 256000 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/hdc3 4608002 1953092233 974242116 5 Extended /dev/hdc5 4608003 1953092233 974242115+ 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
Does this look OK to you?
Thanks.
The block size is fine. But since the starting sectors aren't divisible by 8 (e.g, 2, 4096002) you don't have 4K sector alignment. That likely is impacting performance somewhat.
A reset would probably help, but of course you need to balance the potential gain against the time it takes.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
