Just rebooted my NAS today after 200 days uptime and thought I'd request a volume scan and it found errors! I've never had a power outage etc so am keen to know what could have caused this file system corruption? Anyu ideas???
I'm running 4.2.21 on a ReadyNAS Pro6
***** File system check forced at Fri Apr 26 20:08:38 WEST 2013 ***** fsck 1.41.14 (22-Dec-2010) e2fsck 1.42.3 (14-May-2012) Pass 1: Checking inodes, blocks, and sizes Inode 4195619, i_blocks is 3135728, should be 3135904. Fix? yes
Running additional passes to resolve blocks claimed by more than one inode... Pass 1B: Rescanning for multiply-claimed blocks Multiply-claimed block(s) in inode 4195619: 167904376 167904377 167904378 167904379 167904380 167904381 167904382 167904383 167904384 167904385 167904386 167949296 167949297 167949298 167949299 167949300 167949301 167949302 167949303 167949304 167949305 167949306 Pass 1C: Scanning directories for inodes with multiply-claimed blocks Pass 1D: Reconciling multiply-claimed blocks (There are 1 inodes containing multiply-claimed blocks.)
File /PREMIER/Premier Automation Purchase OrdersApp V18.5.mdb (inode #4195619, mod time Fri Apr 26 20:07:42 2013) has 22 multiply-claimed block(s), shared with 0 file(s): Multiply-claimed blocks already reassigned or cloned.
/dev/c/c: ***** FILE SYSTEM WAS MODIFIED ***** /dev/c/c: 616825/30212096 files (13.6% non-contiguous), 62748564/483393536 blocks
Volume seems clean now after reboot and keeps coming back clean.
Any ideas based on this? The old Database was over 1.6 GB in size. The re-created one from backup is much smaller 33MB (as it was compacted before restoring). Once these DB files grow they don't get smaller until compacted. Although I'm sure file size should not have a bearing on this.
Hi steveoelliott, File system is OK when you see the problem, it don't affect your data. We have addon to avoid this released already. 5.3.8 also included fix, please update to 5.3.8.
Hi steveoelliott, Sorry! I don't see your issue is on Pro6. We found Inode error issue on 5.3 firmware, the issue has been fixed on 5.3.8, I aksed a support to track your support case.
That update didn't work for me at all, still getting the rubbish speeds. I have deleted more things to get 10% free, still very poor. I really give up on this, shouldn't have to deal with issue's like these on a expensive NAS.
18MB/s write and 22MB/s read is the absolute max i get.
when i initially got the nas I got around 40MB/s Write and 85+MB/s Read.
As already mentioned I am on x86 so 5.3.8 is not an option.
I've already got a case with support (21042203) but my issue is basically resolved now but am after a root cause and preventing it happening in future.
Well, in my case no root cause was found but I'm interested as to why debugfs doesn't return anything useful on the NAS device. Maybe it's something to do with the way the RAID is setup.
