NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
fsck has taken 6 days so far
Following an abrupt power-off (powercord was unplugged), my ReadyNas NV has been busy doing an fsck for the past 6 days. I'm able to monitor progress by ssh into the box and looking at /var/log/front...
Welcome to my world.
I have no ReadyNAS but can confirm the problem with high numbers of hardlinks. An old Fileserver (Single-Core-Xeon @2,8Ghz) crashed its external RAID which we used to store rsync-snapshot-backups. Ext4 clearly is not made for very high numbers of hardlinks, we are talking about one million files hardlinked in four complete backuptrees totaling three to six million files. For every single inode fsck has to compute the dangling links which makes 6.000.000 x 6.000.000 = 36.000.000.000.000 calculations.
When this happened first the Xeon took nearly a month for repair. Btw, it was the RAID-controller which spilled bad data over the drive.
My solution: take the raid or an image of the partition and put it on a faster system. My Corei7-2600k@4Ghz made it in sixs days.
Alternatve approach: Let the fsck run until you enter the lengthy "multiply claimed blocks" cycle. At this point your filesystem should(!!!) be mostly(!?!?!) readable as long as you mount it read only. Stop fsck, copy everything, format the corrupted drive, be happy. But beware, hardlinks will not be recognized after stopping fsck, so you will copy every single file as often as it is hardlinked.
I have no ReadyNAS but can confirm the problem with high numbers of hardlinks. An old Fileserver (Single-Core-Xeon @2,8Ghz) crashed its external RAID which we used to store rsync-snapshot-backups. Ext4 clearly is not made for very high numbers of hardlinks, we are talking about one million files hardlinked in four complete backuptrees totaling three to six million files. For every single inode fsck has to compute the dangling links which makes 6.000.000 x 6.000.000 = 36.000.000.000.000 calculations.
When this happened first the Xeon took nearly a month for repair. Btw, it was the RAID-controller which spilled bad data over the drive.
My solution: take the raid or an image of the partition and put it on a faster system. My Corei7-2600k@4Ghz made it in sixs days.
Alternatve approach: Let the fsck run until you enter the lengthy "multiply claimed blocks" cycle. At this point your filesystem should(!!!) be mostly(!?!?!) readable as long as you mount it read only. Stop fsck, copy everything, format the corrupted drive, be happy. But beware, hardlinks will not be recognized after stopping fsck, so you will copy every single file as often as it is hardlinked.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
