ThOr101

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

ThOr101's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi Rob, Thanks for the pointer. I downloaded the rc11a and tried it, it didn't solve my problem. But I posted that in the other thread. It seems to have Tom's attention. Here's hoping! --THOR!
  2. Hi, I was directed to this post from this one that I started: http://lime-technology.com/forum/index.php?topic=26085 rc11a sounded good since it addressed issues with extended attributes and the SHFS. So I downloaded it, copied over the bzimage and bzroot, rebooted, the array came back up with 11a, and I immediately went to try my stock mover (with X for extended attributes) and I still got this: moving tank1/ ./tank1/temp/temp/menu.c32 *** glibc detected *** rsync: free(): invalid next size (normal): 0x080d2410 *** ======= Backtrace: ========= /lib/libc.so.6(+0x705aa)[0xb761d5aa] /lib/libc.so.6(+0x73503)[0xb7620503] /lib/libc.so.6(cfree+0x70)[0xb76236b0] rsync[0x807cd74] rsync[0x807de60] rsync[0x804f3aa] rsync[0x8050b5f] rsync[0x8051e56] rsync[0x8065825] rsync[0x80666ac] /lib/libc.so.6(__libc_start_main+0xe6)[0xb75c3b86] rsync[0x804aad1] ======= Memory map: ======== I couldn't get more than that because the kernel panics & terminates my connection to the box. So thanks for the 11a, but I still have some issues. Again, I've checked all the drives for reiserfs checks, and nothing came back to be fixed. Because of the unclean shutdown, I'm now doing a full parity check, so I'll be happy to experiment again when it is stable. Thanks! --THOR!
  3. I should add one more thing. At one point, I had a bad set of memory in the box. My fear is that somewhere along the way of moving files to the share, that something got corrupted in the SHFS, but not the individual REISERFS system. But I don't really know how to go check the integrity of the SHFS, and this is also only a hypothesis. --THOR!
  4. I don't see any errors in the syslog, until I enable the "X" and then it all goes wonky.
  5. What version of unRAID are you using? If the current 5.0-rc11, then report this to lime-tech in the release thread so it can get fixed. Sounds like handling extended attributes is causing the crash. Joe L. Hi Joe, Thanks for your help. I am running rc11, and I thought I was in the right place to put release candidate bugs. Is there another thread / forum section I'm missing? Thanks for the help.
  6. I am hoping someone can help. My mover will consistently crash my unraid box when mover runs. If I change the command to remove the X it doesn't crash, so my rsync line looks likes this: rsync -i -dIWRpEAogt --numeric-ids --inplace {} /mnt/user0 I've done an reiserfsck on every drive and had NO errors to correct. It almost seems as though the share is a little wonky. So how do I correct that? --THOR!
  7. So, I just tested it, and the -delete does indeed delete the file when rsync core dumps. Or something is deleting the file. I appreciate your offer to send you the trace / dump when rsync fails. But... are you going to tell me to uninstall all of my add-ons and other seemingly useless things that don't really have an effect on some funky setting on the shared file system? I'm happy to upload it from my system as is. If you see a problem that points to one of the add-ons, I guess I can go for it. But I don't have the time to deconstruct, and reconstruct my system just to make it core dump again. Still want the stack trace / core dump with the kernel panic? There it is as an attachment. Thanks for looking into this. Best of luck trying to figure out what happened. Some history of my system is at one point one of the drives did fill up. I moved data around, but I would imagine that the mover ran smack dab into this problem at one point. I'm not sure what could have gotten out of whack. I did the resiserfsck on all the drives, including the cache. No issues found. kernelpanic.txt
  8. I had this same problem, and decided to dive as deep as I possibly could into it, and I found a "solution". Edit your /usr/local/sbin/mover script Change this line: -exec rsync -i -dIWRpEAXogt --numeric-ids --inplace {} /mnt/user0/ \; -delete to this line: -exec rsync -i -dIWRpEAogt --numeric-ids --inplace {} /mnt/user0/ \; -delete When rsync tries to set the extended attributes of the file on the /mnt/user0 files system it coredumps / kernel panics. I'm not exactly sure what extended attributes need to be brought through when the cached file is moved, I don't think I'm using any of them, but I guess time will tell. One other thought while looking at the mover script. If you have been having these problems, you have probably lost a lot of files. The mover script will delete the file without a successful copy: find "./$Share" -depth \( \( -type f ! -exec fuser -s {} \; \) -o \( -type d -empty \) \) -print \ -exec rsync -i -dIWRpEAXogt --numeric-ids --inplace {} /mnt/user0/ \; -delete I would probably suggest to the owner of this script to use --remove-source-files and allow rsync to ensure the file has been properly moved, and let it remove the original. This just deletes files when there is a failure. I hope this helps. --THOR!
  9. I've been reading plenty of threads, and can't seem to find anyone who has this combo working. I think the Norco 4224 case will support this, but I've read about some quality control issues with that case. There is a nice super micro case, but I'm not sure it supports sata3, and I hear if you don't get a super micro motherboard, it might not fit well (and have front plate header issues). I'll need to use 3TB drives (and yes, I'll be running 5.0 rc8 and above). Was wondering if anyone has any recommendations for these requirements. Not sure if this is tacky, but if someone really wants to consult and put together a recipe, I'd be happy to paypal someone for the assist. At the moment, I think this meets these requirements. http://lime-technology.com/forum/index.php?topic=21470.0 Thanks. P.S. While you are still reading, I'm trying to wrap my head around if I can plug SATA3 drives into SAS controllers. Are these two connectors identical, and are the protocols compatible?
  10. Hi there. unRAID (but not Linux) newbie. I was using ReadyNAS, but I just out grew it. Moved to unRAID, and am running the latest Beta (to support current hardware). I used to NFS mount everything, but have now had to revert to CIFS because of all the stale NFS mount issues I'm getting from the box on multiple operating system (clients). I only post this here (to echo what others have posted in the beta forum) because you mention the code has been solid for a while. I'm here to offer any information I can to you in case you need to replicate the error. I'm happy to offer whatever you need. I just didn't want you to think that there weren't any errors other than some known HW issues. Thanks for a decent product, can't wait to fully utilize it, please let me know how I can help. Cheers! --THOR!