Bennett, let's be more explicit:
It takes about 2 min. to boot, probably starting to answer NFS calls a little bit earlier (it depends on your networking config - if you use trunking, it takes a few seconds to setup the trunk). The 5 minutes is if there's writing of a core file. I don't believe that generic server with big memory that crashes will take less to write its core file also (you can choose not to write a corefile, but this is probably unwise). Anyway, let's not forget that even if it is 5 minutes with core, a generic server crash will take longer to boot for replaying journaling, which the filer needs only a few seconds for.
Does anyone have numbers for generic server boot times ?
eT.
--- Bennett Todd bet@rahul.net wrote:
2000-07-20-16:25:44 Bruce Sterling Woodcock:
+++ NetApp (F720) Boots in under 2 minutes due to the use of NVRAM even after an improper shutdown. [...]
2 minutes is really unlikely unless you're just using vanilla NFS and haven't generated a core. Think more like 5 minutes (still impressive).
That is such a bummer!
I remember only a couple of years back, the proud boast was that you could kick the plug out of a netapp, and no more than 45 seconds after plugging it back in, it'd be live serving NFS data once again. I even remember a salescritter saying (I think on this list) that they'd had customers take that boast and try and feed it to 'em, with a line like ``Ok, let's try it, if it's not back in 45 seconds by my watch, you're outa here'', and stood by with confidence while the box passed the test.
When did the time increase to 2.6-6.6 times that once-proud 45-second figure?
At 5 minutes, that means Netapps are no longer booting significantly faster than generic servers.
-Bennett
ATTACHMENT part 2 application/pgp-signature
===== Yours, Eyal Traitel eTraitel@yahoo.com, Home: 972-3-5290415 (Tel Aviv) *** eTraitel - it's the new eBuzzword ! ***
__________________________________________________ Do You Yahoo!? Get Yahoo! Mail � Free email you can access from anywhere! http://mail.yahoo.com/
Eyal Traitel wrote:
Bennett, let's be more explicit:
It takes about 2 min. to boot, probably starting to answer NFS calls a little bit earlier (it depends on your networking config - if you use trunking, it takes a few seconds to setup the trunk). The 5 minutes is if there's writing of a core file. I don't believe that generic server with big memory that crashes will take less to write its core file also (you can choose not to write a corefile, but this is probably unwise). Anyway, let's not forget that even if it is 5 minutes with core, a generic server crash will take longer to boot for replaying journaling, which the filer needs only a few seconds for.
Does anyone have numbers for generic server boot times ?
I've never done any real timing but we have an E450 with Solaris 2.6, 4*250MHz, 4GB of memory, 40*18GB drives in 4 shelves connected to 2 FCAL loops. We use disksuite to mirror and log the disks.
Without a crash dump the system takes a couple of minutes to reboot, looking at the last printout I would guess that it takes around 3 minutes. With a crash dump it would take I guess about 30 seconds more, of course one's sense of time isn't that accurate while waiting for a large server to reboot. It takes longer from cold start due to te POST but IIRC we had an outage of 15 minutes when I increased the memory, i.e. take the machine down, open it, install the memory, close it and boot up.
/Michael
-
Eyal Traitel -
Michael Salmon