April 30, 201313 yr Everything was working great last night. I did recently recover from a failed drive, but that may be another story. This morning I noticed an issue when I couldn't add a movie to my CP install and I was getting "Failure in tempfile.mkstemp" errors in Sabnzbd when trying to download something. Checked my syslog and I'm seeing these errors: Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 2949119: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS (device sdg1): Remounting filesystem read-only (Drive related) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 251122: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 247836: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 2949119: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 251122: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 247836: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 2949119: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 251122: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 247836: bit already cleared (Errors) Apr 30 10:20:35 Tower kernel: REISERFS error (device sdg1): vs-4080 _reiserfs_free_block: block 2949119: bit already cleared (Errors) It appears sdg1 and sdg is my cache drive. Any ideas? Looks like I need to check this: http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems syslog-2013-04-30.txt
April 30, 201313 yr Looks like I need to check this: http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems Exactly. this is not a 5.0 issue, so I'm moving it to general support. Joe L.
April 30, 201313 yr Author Cache drive refuses to unmount.. lsof |grep /mnt is coming up with nothing.. i'll give it some more time. EDIT: something was stuck, powered down/on and was able to stop the array without much issue. hmm, is it normal when i start the array in maintenance mode the "assignments" change? sdg was my cache drive earlier, now its sdf... not sure if it matters.
April 30, 201313 yr Cache drive refuses to unmount.. lsof |grep /mnt is coming up with nothing.. i'll give it some more time. lsof will not detect your use of the disk for a swap file or fr a mount-point for another disk or for a loop file-system. Good luck. You've now discovered why the cache drive is a poor choice for many program/processes/operations.
April 30, 201313 yr hmm, is it normal when i start the array in maintenance mode the "assignments" change? sdg was my cache drive earlier, now its sdf... not sure if it matters. Yes, absolutely normal. The drive designations are assigned as the disks spin up and are recognized by the OS. With nearly identical drives, it is very normal for drives to initialize in a seemingly random order. It is why unRAID uses drive model/serial number t track assignments.
April 30, 201313 yr Author reiserfsck --check /dev/sdf1 and found 33 errors. was able to fix with reiserfsck --fix-fixable it looks like. all is looking good now! at least i think. i will continue to monitor throught the day.. i just want to verify should I run --check for /dev/sdf too? In the wiki it says for cache use /sdX1
April 30, 201313 yr reiserfsck --check /dev/sdf1 and found 33 errors. was able to fix with reiserfsck --fix-fixable it looks like. all is looking good now! at least i think. i will continue to monitor throught the day.. i just want to verify should I run --check for /dev/sdf too? In the wiki it says for cache use /sdX1 The file-system is NOT on /dev/sdf, it is n the FIRST partition ( /dev/sdf1 ) Do not run it n the base drive, it will not find a file-system, and you'll cause damage if you try t repair one where it does not exist.
Archived
This topic is now archived and is closed to further replies.