November 9, 20169 yr Hello all, I've got a directory that looks like it's permissions have gotten screwed up, or something like that - it looks like the destination directory went read only somehow. When I try to move some disc images to the server, they get stuck on the cache drive and won't leave. I don't really know how it broke or how to resolve this. Here's the relevant section of my syslog: Nov 8 19:25:37 Shiva root: mover started Nov 8 19:25:37 Shiva root: moving "Shared" to array Nov 8 19:25:37 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync: failed to set times on "/mnt/user0/Shared/Game Images/PC": Read-only file system (30) Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/ Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/Supreme Commander (PC)/ Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] Nov 8 19:25:38 Shiva move: cmd: Success Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync: failed to set times on "/mnt/user0/Shared/Game Images/PC": Read-only file system (30) Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/ Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/Supreme Commander (PC)/ Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] Nov 8 19:25:38 Shiva move: cmd: Is a directory Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync: failed to set times on "/mnt/user0/Shared/Game Images/PC": Read-only file system (30) Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/ Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] Nov 8 19:25:38 Shiva move: cmd: Is a directory Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync: failed to set times on "/mnt/user0/Shared/Game Images/PC": Read-only file system (30) Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/ Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] Nov 8 19:25:38 Shiva move: cmd: Is a directory Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync: failed to set times on "/mnt/user0/Shared/Game Images/PC": Read-only file system (30) Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/ Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] Nov 8 19:25:38 Shiva move: cmd: Is a directory Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync: failed to set times on "/mnt/user0/Shared/Game Images/PC": Read-only file system (30) Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/ Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] Nov 8 19:25:38 Shiva move: cmd: Is a directory Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync: failed to set times on "/mnt/user0/Shared/Game Images/PC": Read-only file system (30) Nov 8 19:25:38 Shiva root: .d..t...... Shared/Game Images/PC/ Nov 8 19:25:38 Shiva shfs/user0: err: shfs_utimens: lutimes: /mnt/disk3/Shared/Game Images/PC (30) Read-only file system Nov 8 19:25:38 Shiva root: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] Nov 8 19:25:38 Shiva move: cmd: Is a directory Nov 8 19:25:38 Shiva move: rmdir: /mnt/cache/./Shared/Game Images Directory not empty Nov 8 19:25:38 Shiva move: rmdir: /mnt/cache/./Shared Directory not empty Nov 8 19:25:38 Shiva root: mover finished Running Unraid 6.2 if that matters. I assume I need to change the attributes of the directory in question but I don't know the exact commands to do so.
November 9, 20169 yr Disk 3 is mounted Read Only Oct 18 03:16:33 Shiva kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 4644 does not match to the expected one 1 Oct 18 03:16:33 Shiva kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 383090689. Fsck? Oct 18 03:16:33 Shiva kernel: REISERFS (device md3): Remounting filesystem read-only You need to Check Disk File System
November 9, 20169 yr Author Ok, that was fairly straightforward, thanks. It looks like I need to do a rebuild tree: root@Shiva:~# reiserfsck --check /dev/md3 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Wed Nov 9 05:50:46 2016 ########### Replaying journal: Trans replayed: mountid 106, transid 22861, desc 5960, len 1, commit 5962, next trans offset 5945 Trans replayed: mountid 106, transid 22862, desc 5963, len 1, commit 5965, next trans offset 5948 Trans replayed: mountid 106, transid 22863, desc 5966, len 1, commit 5968, next trans offset 5951 Trans replayed: mountid 106, transid 22864, desc 5969, len 1, commit 5971, next trans offset 5954 Trans replayed: mountid 106, transid 22865, desc 5972, len 1, commit 5974, next trans offset 5957 Trans replayed: mountid 106, transid 22866, desc 5975, len 1, commit 5977, next trans offset 5960 Trans replayed: mountid 106, transid 22867, desc 5978, len 2, commit 5981, next trans offset 5964 Trans replayed: mountid 106, transid 22868, desc 5982, len 1, commit 5984, next trans offset 5967 Trans replayed: mountid 106, transid 22869, desc 5985, len 1, commit 5987, next trans offset 5970 Trans replayed: mountid 106, transid 22870, desc 5988, len 1, commit 5990, next trans offset 5973 Trans replayed: mountid 106, transid 22871, desc 5991, len 1, commit 5993, next trans offset 5976 Trans replayed: mountid 106, transid 22872, desc 5994, len 1, commit 5996, next trans offset 5979 Trans replayed: mountid 106, transid 22873, desc 5997, len 1, commit 5999, next trans offset 5982 Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 13 transactions replayed Checking internal tree.. / 17 (of 20)/130 (of 170)/ 47 (of 170)block 383090689: The level of the nod e (4644) is not correct, (1) expected the problem in the internal node occured (383090689), whole sfinished ) Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Wed Nov 9 06:49:24 2016 I'm not sure I have the syntax correct. The device in question is md3, and I'm on unraid 6.2 using reiserfs, so what i want to do is: reiserfsck --rebuild-tree /dev/md3 is that correct? Thank you again for the advice.
November 9, 20169 yr Correct. (you can also do all this through the webUI also) Sent from my LG-D852 using Tapatalk
November 9, 20169 yr Author I'm running this now. Should I be replacing this drive, regardless of how the rebuild goes?
November 10, 20169 yr Author This seems mostly resolved. I had one movie that was identified as damaged but it was a terrible movie so, whatever. The files (a handful of iso files for video games) that were stuck in the cache drive seem to have disappeared - they're not on cache anymore, but they never wound up on the array, either. The directories were created, but are empty. I checked the lost+found folder but it's empty as well. Not really a problem there either really, I know which files they are and can restore them from elsewhere. Thanks again for the help.
Archived
This topic is now archived and is closed to further replies.