no. think about it. You are not even writing data at that point. But
even if you were drives write thousands sometimes millions of files or
records without a problem. The drive just failed.
If you had a proper raid config it would have been only one drive
failing and it could have kept going.
Anyway in a production server situation you do need to plan for
replacing those drives every 3 years or so.
Dan
--
Dan Stein
FileMaker 7 Certified Developer
FileMaker 9 Certified Developer
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Cell: 610-256-2843
Fax 215-799-0192 ( Call 1st)
FMP, WiTango, EDI,SQL 2000, MySQL, CWP
[EMAIL PROTECTED]
www.dss-db.com
"The love of one's country is a splendid thing. But why should love
stop at the border? "
Pablo Casals
On Nov 6, 2008, at 2:45 PM, Roland Dumas wrote:
My dev server melted down. coincidentally, I had a taf that returned
a foundset with 1000 records. A mistake, but it would choke the http
server. I was in the process of fixing that taf when my server just
died. Hard drive failure. It seemed like a coincidence. No way that
a too-big foundset could corrupt a hard drive, right?
I moved the files to another server. I fixed the taf to make sure it
only retrieved 75 records at a time. (<@ARG number> = 75) Another
person kept restoring the old taf, though. It crapped out the http
server. Then a hard drive failure.
Is it possible that a taf that returns too big a data set could crap
out the hard drive? Coincidence?
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
