mmccurdy

Members
  • Posts

    19
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mmccurdy's Achievements

Noob

Noob (1/14)

0

Reputation

  1. ..bump.. most of this stuff is still available, including one of the two SAS cards. If you don't like my prices, make an offer!
  2. I'm going in another direction with my NAS, so I have a bunch of stuff left over from my unRAID build. This stuff contributed to a very nice unRAID box, so I'm guessing it might be of interest to this forum. Items are in northern California, but shipping is no problem (buyer's expense). 4GB USB drive with unRAID Pro license - $100 Update: $80 shipped within the continental US ($119 retail for just the license) RAIDMAX case, (http://www.raidmax.com/chassis/platinum.html) very nice looking, 9+1 drive bays. Upgraded with additional 3-drive carrier from manufacturer (~$20) and super quiet Antec fans (~$80 in fans alone) - $100 Update: $75 (~$200 retail incl. carrier and fans) 2x Supermicro AOC-SASLP-MV8 SAS cards, each one includes two SAS -> 4x SATA breakout cables. - $70 ea. Update: both sold, thanks for your interest! Intel PRO/1000 PCIe NIC - $25 (apparently I paid $35.95) Here are some pics of the items: RAIDMAX case (note that I'm selling the case only which includes all hardware, manual, original box, etc. just no internals as in the pics): Flash drive, SAS cards and cables, Intel NIC:
  3. (sorry in advance for the long post) I had high hopes for AFP, but I can not get a stable/workable configuration. More details here. tl;dr: whenever AFP shares are placed under moderate load, files and directories start randomly becoming momentarily unreadable, which was wreaking havoc on a media file scanner that I run (Plex), as well as several other processes. I've tried numerous solutions to this, but I believe it's currently unsolvable given current RC versions of unRAID and my configuration. I had previously written off using SMB, since in my initial experimentation, I was noticing serious issues with name mangling when using an OSX client. I recently picked this investigation back up in the hopes of finding a stable solution, and I found some potentially interesting asymmetry between files written/read through SMB and AFP, particularly when it comes to special characters in filenames. Here's a sample file on a local HFS+ formatted volume (note the "|" character in the name, which shows up just fine in the Finder and the terminal on OSX): -rw-rw---- 1 mmccurdy staff 14304501 Jun 8 05:13 1| Chapter 01 - Bran.mp3 If I write this file to my unRAID via a mounted AFP volume, this is what I see in the filesystem on the unRAID: -rw-rw---- 1 nobody users 14304501 2012-06-08 05:13 1\|\ Chapter\ 01\ -\ Bran.mp3 If I then mount that location via SMB using the default unRAID configuration, and list the file, I get the following (which is problematic to say the least): -rwxrwxrwx 1 mmccurdy mmccurdy 24894125 Jun 8 05:14 10Z0B8~9.MP3 However, if I write the original source file through the same SMB mount, I see the following on the unRAID side (note the odd character in the place of the "|"): -rw-rw---- 1 nobody users 14304501 2012-06-08 05:13 1?\ Chapter\ 01\ -\ Bran.mp3 ... but if I read the SMB-written file through SMB on the OSX side, everything looks just fine, no mangling: -rwxrwxrwx 1 mmccurdy mmccurdy 14304501 Jun 8 05:13 1| Chapter 01 - Bran.mp3 If I add the following options via /boot/config/smb-extra.conf: mangled names = no unix charset = UTF8 display charset = UTF8 I can now successfully read all the files through the SMB mount, even those originally written via AFP. Hooray! However, for files written via SMB, I am still seeing some really funky characters in the unRAID filesystem: ... and more importantly looks the same as that image in the terminal and Finder on the OSX side if I use the AFP mount. So even though I have a stable/workable solution using SMB for now, I'd like to know if anyone has a solution for this, since I would really like to get to an all-AFP setup at some point. Thanks for reading, and thanks in advance for any suggestions anyone has.
  4. Out of curiosity, when you say you've been having trouble "lately," does that imply that there was a time when AFP was stable for you under moderate to heavy use? I've seen one confirmed account of AFP working well for someone (understanding of course that folks who post on the forums tend to be the ones having problems), but I'm having ongoing issues myself, so I'm really just looking for data points on this to see if it's worth trying to save my investment in the unRAID license and hardware. Thanks.
  5. Having just found this thread, I tried this in a last ditch effort to solve my AFP issues (http://lime-technology.com/forum/index.php?topic=21638.0), and I got a popup error message on my Mac Mini after about 20 or 30 minutes of light disk usage saying that there was something wrong with the CNID database, and that it was using a temporary one and switching to read-only mode. Something to consider maybe if AFP support remains a priority, which it seems like it may not be.
  6. I've been having issues where files are intermittently inaccessible, which often manifests itself to the OS like a permission problem. I'm having the issue with AFP/NFS and user shares specifically, but I also haven't used SMB much at all so it's possible that it would also have issues. Unfortunately I don't have a solution and I'm kind of at a dead end trying to debug it. Here's a writeup of my issue, not sure if it's the same or related: http://lime-technology.com/forum/index.php?topic=21638.0
  7. Unfortunately deleting all the Apple metadata I could find (.DS_Stores, the .Apple*'s and a bunch of ._[filename] files that somehow got created), the behavior of the server is exactly the same with files and directories being intermittently inaccessible. I am racking my brain for why this seems to be happening only to me. I'm using standard, modern hardware across the board, everything is on a hardwired gigabit connection with a single switch between the client and the unRAID box, nothing special about my Mac Mini or OSX install, all config options for AFP are at their defaults, etc. Any other ideas welcome. Thanks again for taking a look.
  8. Hey, thanks for the reply and for taking a look at my issue. I actually didn't realize AFP was supported under 4.7, but in any case 4.7 doesn't seem to support my NIC (newer Intel Gbit on an Asus motherboard), so that's not an immediate option. I actually wouldn't mind picking up a compatible PCIe NIC, but I'd rather not be stuck in 4.7 land as unRAID moves on to 5.0 and beyond. Previously, I had deleted all .DS_Stores and set my Mac Mini not to write them to network drives anymore. They have not reappeared, and I'm no longer getting the error in the log about the duplicate objects, so that seems good. Per your suggestion, I just deleted all the .Apple*'s, but I had to use the following: find . -name ".Apple*" -printf '"%p"\n' | xargs rm -Rf Nevertheless, I verified they are gone. I'll keep an eye on it to see if things improve. Thanks again for your help.
  9. I turned off all NFS sharing, and I'm having a hard time nailing down this problem to where I can recreate the "ls" problem using AFP. To be sure, it's still failing/missing random directories and files in the media scans (and rsyncs and large transfers with lots of files), but when I go to do the "ls" it lists the directory. It seems like when I use AFP the problem is much more transient -- I can run an rsync and it'll fail on a handful of files once, and run it just a second or two later and it will work for those same files. I have to ask -- are people out there heavily using AFP/NFS with Mac clients and not seeing this issue? It seems like the vast majority of unRAID users are just using SMB. I'm pretty bummed because I've invested a lot of time and money in this solution (not realizing this limitation) but this is definitely not workable as-is.
  10. This post shows "ls" and "ls -l" output from when the problem is happening, both on the Mac side and the unRAID side. It also has the full paths on both sides: http://lime-technology.com/forum/index.php?topic=21377.msg191887#msg191887 I don't have "ls -la" output from this instance, but I can recreate the problem and grab some later when I get home. I am using a cache drive.
  11. I'm really trying to get a workable AFP or NFS solution running between my Mac Mini and my unRAID box. Unfortunately SMB is a non-starter for me since I have thousands of files, many of which have long names or special characters which seem to be fundamentally incompatible with SMB/CIFS. I first noticed issues when I was copying files on to the array via rsync to an AFP mount. During a large transfer (I was basically doing a terabyte at a time), I noticed that a handful of files would inexplicably fail with permission errors. I wrote this issue up in the AFP forum here: http://lime-technology.com/forum/index.php?topic=21155.0 but I didn't get much traction over there. When I saw that the NFS stale file handle issue was addressed, I upgraded to -rc6-8168-test and tried switching to NFS. Indeed, I did not get stale file handle errors, but I did see some very similar behavior where files and directories would just "go missing" and then mysteriously reappear. I wrote this issue up in this post here: http://lime-technology.com/forum/index.php?topic=21377.msg191887#msg191887 Given the similarity between these two issues, it seems like it may be something more fundamental with how AFP/NFS are playing with the user shares. The issue seems worse under load, but I've seen it happen "at rest" too, as in the NFS issue writeup. It'll basically just be sitting there, and then refuse to see or enter existing/readable directories when I "cd" into them. In part I'm using unRAID for storage for a media server, and I have a scanner process that looks for new files every so often or when something is added. One super-annoying consequence of this issue in this application is that TV shows and movies will disappear during one scan, then reappear during the next scan with no other config or underlying FS changes in between. It also just seems like a very serious issue if you can't count on all your files and directories being accessible at any given time. I'm attaching a full syslog where I do a fresh boot and then do a couple of scans from my media server. As you'll see, there's very little to go on, except for a few messages at the very end (generated during the scans) about duplicate .DS_Store objects. I don't know if that's a clue or not. Nothing else that I can think to check seems amiss with the system -- all my drives are green, parity is valid, etc. If anyone has ideas, please let me know what else I can do here. I'm more than willing to do any kind of tweaking and debugging to figure this out, but I'm kind of at a dead end. Thanks a lot in advance... syslog-2012-07-23.txt
  12. I upgraded to this version today in the hopes that I would be able to use NFS instead of AFP from my Mac Mini, since I'm having issues with AFP: http://lime-technology.com/forum/index.php?topic=21155.0 ... previously I was getting the "stale file handle" message all the time trying to use NFS. Now I'm seeing some even more bizarre behavior with NFS, were directories become inaccessible or disappear for no obvious reason. In this example, "content" is the name of my Mac Mini and "thedisk" is the name of the unRAID box. I'm running this from the command line. Here, I see the (correct) list of subdirectories when I do a standard "ls", then if I try to cd into one, it says "No such file or directory": content:ExampleShow mmccurdy$ pwd /Volumes/thedisk-nfs/TV/ExampleShow content:ExampleShow mmccurdy$ ls Season 1 Season 2 Season 3 content:ExampleShow mmccurdy$ cd Season\ 1 -bash: cd: Season 1: No such file or directory content:ExampleShow mmccurdy$ ls -l ls: Season 1: No such file or directory ls: Season 2: No such file or directory total 1 drwxr-xr-x 1 1000 _lpoperator 112 Jul 18 05:05 Season 3 content:ExampleShow mmccurdy$ ls Season 1 Season 2 Season 3 I am using automount to mount "TV," here is the line item from "mount" on the Mac Mini: 192.168.1.97:/mnt/user/TV on /Volumes/thedisk-nfs/TV (nfs, nodev, nosuid, automounted, nobrowse) .. and here is the line item form /etc/exports on the unRAID box: /mnt/user/TV -async,no_subtree_check,fsid=102 *(rw,insecure,anonuid=1000,anongid=100,all_squash) Everything will be working fine one minute, then suddenly I'll do something like try to enter (cd into) some directory, and I get the "No such file or directory" error. Here is how the directories appear on the unRAID box itself: root@thedisk:/mnt/user/TV/ExampleShow# ls -l total 0 drwxrwsr-x 1 mmccurdy users 80 2012-07-11 12:07 Season\ 1/ drwxrwsr-x 1 mmccurdy users 80 2012-07-11 12:10 Season\ 2/ drwxr-xr-x 1 mmccurdy users 112 2012-07-18 05:05 Season\ 3/ There is nothing at all suspicious in the syslog when this is happening. At least I'm no longer getting stale file handles I guess. If no one else is having this problem, I guess it could be a config issue on my end, but it just seems odd that it would work fine one second and then not the next.