With I/O, the only thing that could possibly cause more I/O beyond syslogging (as Blake stated), is synchronous snapmirror - the transient data during mirroring is stored on the partner's root vol.

The only other concern is uptime - if something happens to an aggr containing the root vol (and other data vols) due to some unforeseen bug or doubldisk failure, then your root vol will also be offline. This may not be that much of a concern due to the fact that the data vol is offline, but if the root vol was on a separate aggr and the data vol was unimportant you could at least get the filer up and serving data to the rest of the clients\systems until a maintenance window to deal with the other unimportant vol. That being said, the probability is extremely low for volumes to go offline in the first place - be sure to use RAIDDP at the very least with your aggrs... (and other forms of HA if possible)

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Blake Golliher Sent: Monday, January 23, 2006 2:51 AM To: Jerry Cc: list toasters Subject: Re: root volume / flexvol / aggregate

It's a common concern I hear from DBA's. They worry that the extra IO from the root volume can rob io's from the data volumes. But except for the sysloging, there's not a lot of activity on the root volume. As long as you have a large enough aggregate, in terms of IO's, then you should be fine. I've never heard of a problem either, which makes sense.

-Blake

On 1/22/06, Jerry juanino@yahoo.com wrote:

Anyone see any issues with having your production volumes and your root volume on the same aggregate. I assume there is no issue, but wanted to get input before I go where I can't go back.

Jerry

---

Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com