NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
astyler74
Aug 29, 2013Aspirant
WARNING : 2120 NFS share ends up read-only.
I'm having problems with a new 2120 (6.1.1) using 4*4TB disks HUS724040ALE640.
I am trying to use a new feature introduced in PHD backup 6.5 to create a replica backup store. The store is 4.6TB on disk and is on a older 3100 it makes use of hard linked files quite extensively ( 20TB of data without).
During the copy process the PHD vba will hang with the following.
Aug 28 14:45:43 phdvb archived[1007]: [ tid #0x3ef ] error: Unable to rename block [/dd/blocks/1048576/md5/none/56/4d/564d8b5a818cd199b185bac0a8f6298b.tmp] - Read-only file system
A reboot of the NAs will allow it to proceed a little before hanging again. I have tested again using a old Thecus as the archive store and left it running it has got to 260Gb archived and is still proceeding. So I know its not a PHD issue.
Also once this problem occurs I cant modify any of the settings for the NFS share via the GUI. Commit failed with 100203001
any pointers for what log files I should look in.
Hang on have i run into this
Anyone know if the btrfs used in the readyos 6 is the newer release which this fixed?
I am trying to use a new feature introduced in PHD backup 6.5 to create a replica backup store. The store is 4.6TB on disk and is on a older 3100 it makes use of hard linked files quite extensively ( 20TB of data without).
During the copy process the PHD vba will hang with the following.
Aug 28 14:45:43 phdvb archived[1007]: [ tid #0x3ef ] error: Unable to rename block [/dd/blocks/1048576/md5/none/56/4d/564d8b5a818cd199b185bac0a8f6298b.tmp] - Read-only file system
A reboot of the NAs will allow it to proceed a little before hanging again. I have tested again using a old Thecus as the archive store and left it running it has got to 260Gb archived and is still proceeding. So I know its not a PHD issue.
Also once this problem occurs I cant modify any of the settings for the NFS share via the GUI. Commit failed with 100203001
any pointers for what log files I should look in.
Hang on have i run into this
Files with hard links in other directories have multiple reference items, one for each parent directory. Files with hard links in the same directory pack all of the links' filenames into the same reference item. This was a design flaw that limited the number of same-directory hard links to however many could fit in a single tree block. (On the default block size of 4KB, an average filename length of 8 bytes and a per-filename header of 4 bytes, this would be less than 350.) Applications which made heavy use of same-directory hard links, such as git, GNUS, GMame and BackupPC were later observed to fail after hitting this limit.[47] The limit was eventually removed[48] (and as of October 2012 has been merged[49] pending release in Linux 3.7) by introducing spillover extended reference items to hold hard link filenames which could not otherwise fit.
Anyone know if the btrfs used in the readyos 6 is the newer release which this fixed?
16 Replies
Replies have been turned off for this discussion
- astyler74AspirantRight after today's testing it fails in the same manner, definitely a btrfs issue with the hard links.
- astyler74AspirantNG DEV's have recreated issue, it does now seem the btrfs build they are using is lacking in some areas. I have found one but what else is there to find.
NG are treated us like BETA TESTERS. - MichaelSulzAspirantI have the same Problem with 2120. I have 3 TB on the nas and no it is red only, realy great :-)
- astyler74AspirantWelcome to the club MS
This looks like its not the hard link issue as i first hypothesized but instead a corruption issue resulting in CRC errors on the file system.
What content are you storing is it hard linked NFS data? - beisser1Tutor
MichaelSulz wrote: I have the same Problem with 2120. I have 3 TB on the nas and no it is red only, realy great :-)
hi,
please open a case with techsupport and have it escalated.
please also include a fresh set of logs if possible so that support can determine if this is indeed the same problem. - astyler74AspirantRight so its seems this problem I had wasn't related to the hardlink issue, but it was infact a problem with the 2120 chassis only. I have applied a fix(8.1.2) and all seems good for now.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!