Pro/Forums - View Single Post

Phoenix32 · 09-27-2006, 09:12 PM

I thought I might start a new thread to get some of the messages concerning the SNAP 4000 spread around in other threads into one place.

Okay, radio has provided some logs on a rebuild for the 4000 with OS 4.0.860 and using 4 x Seagate 320 GB drives.

One of the other 4000 owners (sorry, I just can't recall the name at the moment) has a 4000 with 4 x Seagate 4000 GB drives he was going to do some testing on. I am not sure the OS he is using.

I have no idea what happened to DC4 and his 4000 with 4 x Seagate 320 GB drives and OS 3.4.807.

Okay, so you Unix/Linix/BSD software and IT types (you know who you are, lol), what can we determine from the logs already provided? Are there some memory or cache allocations they should try out? Is there anything in those logs that might lead us to a near rock solid idea where the limit might be or how to get around it? Is there more information that needs to be tested and reported?

There is the swap file usage that may have turned out to be something else maybe. There are a few errors being reported here and there. There is also some sectors in the last cylinder not being used, etc... I think Dave (and others)had some good ideas. Did I miss anything?

(hey, I am trying okay?)

09-27-2006, 09:12 PM	#1
Phoenix32 Thermophile Join Date: May 2006 Location: Yakima, WA Posts: 1,282	SNAP 4000 Errors and Limits I thought I might start a new thread to get some of the messages concerning the SNAP 4000 spread around in other threads into one place. Okay, radio has provided some logs on a rebuild for the 4000 with OS 4.0.860 and using 4 x Seagate 320 GB drives. One of the other 4000 owners (sorry, I just can't recall the name at the moment) has a 4000 with 4 x Seagate 4000 GB drives he was going to do some testing on. I am not sure the OS he is using. I have no idea what happened to DC4 and his 4000 with 4 x Seagate 320 GB drives and OS 3.4.807. Okay, so you Unix/Linix/BSD software and IT types (you know who you are, lol), what can we determine from the logs already provided? Are there some memory or cache allocations they should try out? Is there anything in those logs that might lead us to a near rock solid idea where the limit might be or how to get around it? Is there more information that needs to be tested and reported? There is the swap file usage that may have turned out to be something else maybe. There are a few errors being reported here and there. There is also some sectors in the last cylinder not being used, etc... I think Dave (and others)had some good ideas. Did I miss anything? (hey, I am trying okay?)