NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNasMan123
Oct 16, 2010Aspirant
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...
ReadyNasMan123
Oct 17, 2010Aspirant
Prior to this last fsck I had logged in and performed a 'kill' on the fsck process because I needed to get access to my files. While I understand the file system may have had errors, I had to take the risk. It worked out, I accessed the files I needed and rebooted... with the intent of letting fsck finish.
So far it has been over a week... progress right now is at 73.4%.. that's 0.6% since Friday evening (it's now Sunday morning).
Could fsck take longer because the filesystem contains many hard-links? I primarily use the device for backups and each night a hardlink is made to all files from the night before. All together I keep 7 daily backups and 4 weekly backups, so each file is basically hardlinked 11 times. (The exception are new, changed or deleted files)
nas1:/var/log/frontview# cat enclosure.log
temp!!1!!status=ok::descr=36.5C/97.7F::expected=0-60C/32-140F
fan!!1!!status=ok::descr=2142RPM
ups!!1!!status=not_present::descr=
volume!!1!!status=ok::descr=Volume C: RAID Level X, Redundant. 1442256 MB (51%) of 2743 GB used
disk!!1!!status=ok::descr=Channel 1: Seagate ST31000520AS 931 GB, 38C/100F
disk!!2!!status=ok::descr=Channel 2: Seagate ST31000520AS 931 GB, 42C/107F
disk!!3!!status=ok::descr=Channel 3: Seagate ST31000520AS 931 GB, 44C/111F
disk!!4!!status=ok::descr=Channel 4: Seagate ST31000520AS 931 GB, 39C/102F
model!!0!!::descr=ReadyNAS NV [X-RAID]
Boot!!FS_CHECK!!73.4%
nas1:/var/log/frontview# cat /tmp/fsck.log
***** File system check performed at Sat Oct 9 20:24:13 CST 2010 *****
fsck 1.40.2 (12-Jul-2007)
e2fsck 1.40.2 (12-Jul-2007)
c was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
nas1:/var/log/frontview# ps -eaf | grep fsc
root 574 435 0 Oct09 ttyS1 00:00:00 fsck -R -A -y -- -C-1
root 575 574 99 Oct09 ttyS1 7-13:21:47 fsck.ext3 -y -C-1 /dev/c/c
nas1:/var/log/frontview# ls -alt /proc/575/fd/
total 0
l-wx------ 1 root root 64 Oct 15 22:19 0 -> /dev/tty
l-wx------ 1 root root 64 Oct 15 22:19 1 -> /tmp/fsck.log
lrwx------ 1 root root 64 Oct 15 22:19 3 -> /dev/mapper/c-c
lrwx------ 1 root root 64 Oct 15 22:19 5 -> /var/cache/e2fsck/fef9ff86-773d-4c8a-84f3-c4af0c65fc21-icount-DyM5Bm
lrwx------ 1 root root 64 Oct 15 22:19 6 -> /var/cache/e2fsck/fef9ff86-773d-4c8a-84f3-c4af0c65fc21-dirinfo-2EAyps
lrwx------ 1 root root 64 Oct 15 22:19 7 -> /var/cache/e2fsck/fef9ff86-773d-4c8a-84f3-c4af0c65fc21-icount-c6M7BM
dr-x------ 2 root root 0 Oct 15 22:18 .
l-wx------ 1 root root 64 Oct 15 22:18 2 -> /tmp/fsck.log
dr-xr-xr-x 4 root root 0 Oct 9 20:24 ..
So far it has been over a week... progress right now is at 73.4%.. that's 0.6% since Friday evening (it's now Sunday morning).
Could fsck take longer because the filesystem contains many hard-links? I primarily use the device for backups and each night a hardlink is made to all files from the night before. All together I keep 7 daily backups and 4 weekly backups, so each file is basically hardlinked 11 times. (The exception are new, changed or deleted files)
nas1:/var/log/frontview# cat enclosure.log
temp!!1!!status=ok::descr=36.5C/97.7F::expected=0-60C/32-140F
fan!!1!!status=ok::descr=2142RPM
ups!!1!!status=not_present::descr=
volume!!1!!status=ok::descr=Volume C: RAID Level X, Redundant. 1442256 MB (51%) of 2743 GB used
disk!!1!!status=ok::descr=Channel 1: Seagate ST31000520AS 931 GB, 38C/100F
disk!!2!!status=ok::descr=Channel 2: Seagate ST31000520AS 931 GB, 42C/107F
disk!!3!!status=ok::descr=Channel 3: Seagate ST31000520AS 931 GB, 44C/111F
disk!!4!!status=ok::descr=Channel 4: Seagate ST31000520AS 931 GB, 39C/102F
model!!0!!::descr=ReadyNAS NV [X-RAID]
Boot!!FS_CHECK!!73.4%
nas1:/var/log/frontview# cat /tmp/fsck.log
***** File system check performed at Sat Oct 9 20:24:13 CST 2010 *****
fsck 1.40.2 (12-Jul-2007)
e2fsck 1.40.2 (12-Jul-2007)
c was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
nas1:/var/log/frontview# ps -eaf | grep fsc
root 574 435 0 Oct09 ttyS1 00:00:00 fsck -R -A -y -- -C-1
root 575 574 99 Oct09 ttyS1 7-13:21:47 fsck.ext3 -y -C-1 /dev/c/c
nas1:/var/log/frontview# ls -alt /proc/575/fd/
total 0
l-wx------ 1 root root 64 Oct 15 22:19 0 -> /dev/tty
l-wx------ 1 root root 64 Oct 15 22:19 1 -> /tmp/fsck.log
lrwx------ 1 root root 64 Oct 15 22:19 3 -> /dev/mapper/c-c
lrwx------ 1 root root 64 Oct 15 22:19 5 -> /var/cache/e2fsck/fef9ff86-773d-4c8a-84f3-c4af0c65fc21-icount-DyM5Bm
lrwx------ 1 root root 64 Oct 15 22:19 6 -> /var/cache/e2fsck/fef9ff86-773d-4c8a-84f3-c4af0c65fc21-dirinfo-2EAyps
lrwx------ 1 root root 64 Oct 15 22:19 7 -> /var/cache/e2fsck/fef9ff86-773d-4c8a-84f3-c4af0c65fc21-icount-c6M7BM
dr-x------ 2 root root 0 Oct 15 22:18 .
l-wx------ 1 root root 64 Oct 15 22:18 2 -> /tmp/fsck.log
dr-xr-xr-x 4 root root 0 Oct 9 20:24 ..
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!