GarrettC Posted December 22, 2010 Share Posted December 22, 2010 Wierd problem that just popped up today, has happened twice now. As im moving files to the server it will intermittantly loose perimissions to the shared folders, seems to happen after about 2tb are moved. I have to stop the array then restart it, after that its fine for a while then locks down again. I haven't had it running long enough to see if its a time thing or it just doesnt like being bombarded with files. Quote Link to comment
GarrettC Posted December 22, 2010 Author Share Posted December 22, 2010 Noticed this in SysLog Anyone have any idea's as to whats causing this? All drives have at lease 500gb remaining. System has 2gb memory If I stop the array and restart it, that works for a while but eventually does it again. Now its to the point where that doesnt work anymore... I can't write anything to the unRaid server. Dec 22 02:19:04 storage emhttp: Restart CIFS... Dec 22 02:19:04 storage emhttp: shcmd (114): killall -HUP smbd Dec 22 02:19:04 storage emhttp: shcmd (115): /usr/local/emhttp/emhttp_event svcs_restarted Dec 22 02:19:04 storage emhttp_event: svcs_restarted Dec 22 02:24:47 storage shfs: shfs_ftruncate: ftruncate: (5) Input/output error Dec 22 02:24:47 storage shfs: shfs_write: write: (12) Cannot allocate memory Dec 22 02:24:47 storage last message repeated 4 times Dec 22 02:24:47 storage kernel: REISERFS error (device md3): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 65568768 is corrupted: first bit must be 1 Dec 22 02:24:47 storage kernel: REISERFS (device md3): Remounting filesystem read-only Dec 22 02:24:47 storage shfs: shfs_write: write: (12) Cannot allocate memory Dec 22 02:24:47 storage last message repeated 3 times Dec 22 02:25:01 storage shfs: shfs_ftruncate: ftruncate: (12) Cannot allocate memory Dec 22 02:25:01 storage shfs: shfs_write: write: (12) Cannot allocate memory Dec 22 02:25:01 storage last message repeated 8 times Dec 22 02:25:24 storage shfs: shfs_utimens: utimes: /mnt/disk3/Movies/*****/VIDEO_TS/VTS_02_1.VOB (30) Read-only file system Dec 22 02:25:24 storage shfs: shfs_unlink: unlink: /mnt/disk3/Movies/*******/VIDEO_TS/VTS_02_1.VOB (30) Read-only file system Dec 22 02:25:24 storage shfs: shfs_create: open: /mnt/disk3/Movies/******/VIDEO_TS/VTS_02_2.VOB (30) Read-only file system Dec 22 02:25:24 storage last message repeated 3 times Dec 22 02:25:30 storage shfs: shfs_create: open: /mnt/disk3/Movies/******/VIDEO_TS/VTS_02_3.VOB (30) Read-only file system Quote Link to comment
Joe L. Posted December 22, 2010 Share Posted December 22, 2010 There are two different clues in the segment of the syslog you posted. First you are running out of memory. (Don't know why just yet) The most likely reason is the file-system on disk3 has some corruption. (as reported in the syslog lines you posted) Once the file-system corruption is detected by unRAID's OS, the file-system is mounted as read-only to prevent further corruption. To fix it, you'll need to follow the steps as outlined in the wiki here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Joe L. Quote Link to comment
GarrettC Posted December 22, 2010 Author Share Posted December 22, 2010 Bingo, you nailed it! Found 10 corruptions on disk3 that have been corrected. System is back up 100% now. Thanks for the help! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.