Re: SNAP 4000 Errors and Limits
 

I tried the system with 64m RAM. No luck. The "memory to be written" rose as always, and delays are just as long. I guess I'm stuck. the software must be doing something the snap just can't handle - at least for my application. :cry:

oidar

Re: SNAP 4000 Errors and Limits
 

Do you have ftp turned on? Some programs uses its protocol to speed things up. Might try turning it on or off and see if it make a difference. Remember the snap uses SAMBA v2 with v4 OS. Which is not very fast. And can not handle long file names.

Re: SNAP 4000 Errors and Limits
 

This is confusing. I am using windows networking and mapping drives. No FTP. it's simply a program accessing a share. FTP is off.

I am not sure what you mean by not handling long filenames. It handles long filenames just fine. I would say that 90% of the 280Gigs worth of music has filenames longer than 8 characters, many with filenames much longer.



At this point I've given up. I'll probably keep the snap around for backup, but it's useless in production. I may checkout FreeNAS in the future. It's just not worth the time and hassle anymore.

I hope the testing I did helps someone.

oidar.

So long and thanks for all the fish.

Re: SNAP 4000 Errors and Limits
 

Long file names is 32 chr, a restriction in SAMBA v2. But still some chr are not allowed.

I have seen some of the activity here after doing some testing. It apears the snap has to halt net traffic then use the cpu to do xor bit calculation for writes. Mine in no were close to yours. I would wire the cpu fan to run 24/7. As the cpu heat goes up the cpu will throttle back even stall till it cools down.

Do you see these hickup during reads? should be there but less.

How may users are attached to the server? more than just 1?

Re: SNAP 4000 Errors and Limits
 

Here is a long (50+ character) filename we have on the snap:

Elegy for William Burroughs and Allen Ginsberg .mp3

it seems to work fine.

mostly the activity is reading the id3 or similar tags from audio files when the scheduling program starts. I am not sure how you can simulate reading tiny bits of large files.

As far as I know, it's durring reads.

There is only one user connected that is doing anything - sometimes other computers have the dirve.

Peace,
oidar

Re: SNAP 4000 Errors and Limits
 

Adaptec Knowledge base say this:

Question : Is there a limit for Mac OS X clients on the number of characters in a filename on SnapOS ?

This information applies to the following Product(s):

- Snap Server 1000
- Snap Server 1100
- Snap Server 2000
- Snap Server 2200
- Snap Server 4000
- Snap Server 4100
- Snap Server 12000

This information applies to the following Operating System(s):

- Mac OS X
Answer : 31 characters is the limit. File names exceeding 31 cannot be saved or copied onto the SnapOS from a MAC OS X client.

and:

You must upgrade your Snap server to Snap OS 4.0854 to get support for Mac OS X.

The max path including filename is limited to 254 chr or less. This applies to windows and mac.

Re: SNAP 4000 Errors and Limits
 

I don't have a Mac.

Re: SNAP 4000 Errors and Limits
 

I have two 4000's and a 4400 and I stream MP3's off my 4000 all the time.
What software are you running that hangs up your songs?

Re: SNAP 4000 Errors and Limits
 

This has nothing to do with streaming MP3s. streaming just shows the symptoms of the problem. I am using Station Playlist Creator (free trial come to think of it) which causes the problem when it loads. It's not even heavy traffic, but for some reason the snap can't handle it. It does something to drive up the "memory to be written" and the snap stops all data transfers while getting it back to zero. (writing?)

Re: SNAP 4000 Errors and Limits
 

Just to recap
So- 4 x 250 drives = known working
4x 320 drives = ???????

Did radio (or anyone) confirm 320 drives as working with no problems?

Re: SNAP 4000 Errors and Limits
 

IMO, 4000 + 4 x 250 = A O K, 4000 + 4 x 320 = A F U

Re: SNAP 4000 Errors and Limits
 

To clarify,

The problem was not the 320GB drives, they worked fine.:nod: The problem was the snap.:mad: It can not constantly stream files under certain conditions. I tried building a mirror and got the same results. The 320GB drives do work in the snap in raid 5 like any other drives.

This is experience, not opinion.

Re: SNAP 4000 Errors and Limits
 

So let me get this right.

- Just because every single 4 x 320 GB 4000 setup we have seen or heard of has had various "problems" is just coincidence?

- David digging up the documentation on the OS it is built from, which flat out said there is a 1TB limitation, doesn't matter?

- A full formal education in analog and digital electronic engineering and 30 years of hands on tech work in the field "opinion" is worthless just because someone on a forum with a malfunctioning SNAP Server said so?


Nevermind, please don't answer...

Re: SNAP 4000 Errors and Limits
 

Radio, The info Phoneinx32 say is correct.

I don't know what your problem is. We have been through this before. :hammer:

Everything Phoenix32 has said about the HW in a 4000 and the 1T has been confirmed. Others have also reported problems with HD's > 250gig.

The OS has a 1T limit, due to the fact that the XFS file system is 24bit. Just because the HD Supports LBA48bit does not make it a 48bit system. The weakest link rules here.

Failure to build the raid5 array should tell you something.

You come here for help, then you disregard what we say.

Time for you to move on.

Enough said, case closed.

Re: SNAP 4000 Errors and Limits
 

Phoenix, I am very sorry I hurt your feelings. That was not my intention.

FYI, I am a senior systems programmer, and have been in the field for over 25 years. I also have extensive electronic experience. I don't consider experience worth much if you can't use it to point to a specific reason whys someone will not work. What does matter is when something does work and you experience it. If you look at it from my point of view you can clearly see how ridiculous it sounds. I have it working. but you tell me it cant work. I guess I'll trust 'the horses mouth' experience over your opinion any day. I am sorry you don't like it and it contradicts much of what you have posted here, but there it is.


Your three bullets in order:
1) because some have had problems does not mean everyone will. (10 people with broken legs couldn’t run a marathon, therefore it's not possible) - logical fallacy. not to mention there are other who have gotten 250+ drive raids working and posted here. infact, there are very few who have tried larger drives that have posted anything here.

2) "is built from" is the key phrase here - it means nothing. you have no idea what modifications were made.

3) again, this is opinion, that is, your belief. Belief does not hold up against the reality of experience. Experience wins.

Re: SNAP 4000 Errors and Limits
 

Blue, It certainly is time to move on. (not because of your suggestion)

It's also time for anyone thinking about buying an old snap. While you guys seem stuck on reviving a dead technology, which is fine for hobbyists, I would also have to recommend anyone thinking of using these in production to move on as well. They would be better off working with FreeNAS - even in beta.


My problem, at the moment, is your collective egos. You can't seem to admit that you were wrong. I have the proof, and I am using it. (though I'll sell it soon.) I built a RAID5 just fine - no failure as you suggest. you have to remember that this is not religion. Belief does not trump evidence. It works, and I am sorry that makes you feel bad. But for honesty sake I have to report it like it is.

I appreciate the jump start help I did get here in the early stages. This site and the info here is great for hobbyists (thought I'll have to warn people not to take it as gods word. there is much speculation and belief offered as gospel.) I offered to financially support this site, but was asked to continue posting and adding to the knowledge base instead. You also asked me to report back my results, but now that you don't like it, you are asking me to leave.

that suits me fine.

You know, I really wasn't out to hurt your feelings either. I am sorry.

Re: SNAP 4000 Errors and Limits
 

If you would to look at the results, you would reconize that you are still having issues with the large drives. Other wise you would not be coming back with all the problems. All other with the 400gig hd (and 320+gig) have had problems in raid5. You must remember STABILITY IS THE KEY, with out it you can not trust the unit. This means starting and stopping, this is where a lot of problems show up. If it has to go through a 24+ hr check every time it boots, someting is wrong. The snapos also is working on a 24bit file system which clamps the capacity. 750 gig drives have worked in some units, as long as the share is under the 24 bit limit, ~ 1T. I have also done research that there are a lot of other NAS (early ones) that also have this limit. But most of those the MFG supplied upgraded firmware.

Your welcome here but with new problems that have not been addressed.

Re: SNAP 4000 Errors and Limits
 

Excuse me?

I was not even going to reply until I read that.

In case you haven't noticed pal, I am not trying to revive jack squat. In fact, I am using Guardian OS Units. I have one SNAP 4000 which will probably go away soon, one SNAP 1000 which I keep for playing with and due to it's small footprint, and then six Guardian OS units. So exactly how am I trying to revive a dead technology? I'm not, unless you consider trying to help those who have SNAP OS units for whatever their own reasons are (mostly money) as reviving dead technology.

You have a right to think and believe what you want. But the fact is, in this case, you are wrong, but no point trying to convince you either (I could not care less). But I do care about you putting out info that is dead on wrong and may cause someone else problems. You keep on thinking what you want. I really don't care. Honest. But do not expect me to sit by idle while you tell someone they can do something that is going to cost them money only to find out it won't work, or will work, but will have various "issues" all the time.

And, don't apologize to me, it's not needed. My feelings were not hurt even a little. But you might want to apologize to anyone who took your opinion and spent their hard earned cash only to end up with problematic SNAP 4000.


To be fair. Has anyone here put 4 x 320 GB drives in a SNAP 4000 in a 4 Drive RAID 5 array (no spares) and not had one single issue or problem? Now I do mean zero issues of any kind at all, even small ones? And I don't mean just slapped the the drives in, formatted and built a RAID 5, then called it good. I mean had it up and running a while with real usage in various situations and/or even had to rebuild the array due to a dead drive (or simulated). Anyone?

Re: SNAP 4000 Errors and Limits
 

Oooops, here's me trying to revive dead technology again...

http://cgi.ebay.com/ws/eBayISAPI.dll...6266&rd=1&rd=1


Sorry Hallis... :(

Re: SNAP 4000 Errors and Limits
 

You know, until I saw the picture for this auction, I never realized that the Snap 4500 came with 24 ethernet ports. :eek:

Re: SNAP 4000 Errors and Limits
 

:uhh: You mean they don't? :bawling:


LOL :D


(yes, I asked questions)

Re: SNAP 4000 Errors and Limits
 

Wow, like brand new, 4 x 250 GB drives, and OS 4.2.054 taboot... Not bad...