Hi -
For info, I generally set my root volumes to 15Gb overall with a 20% Snap reserve (12Gb FS and 3Gb snap)
I heavily restrict access to the chosen few and exclude the 'noddy' administrators often found in Domain Admin groups :o)
The remainder of the AGGR aggregate I set up as an 'admin' volume where I store install and other misc data away from the user data.
From Johns comments, I think what had happened is I had rebooted the filer on the newroot flex vol and issued the command which succeeded because it had already set AGGR aggregate as root.
I have another cluster pair I will be playing with and upgrading this weekend. I will check out my theories (we do not have the luxury of a test filer here)
That aside, has anyone seen any problems with SID based quotas after upgrading ? It seems that some explicit entries in our /etc/quotas. file which are recognised when the volume is bought online seem to revert to the standard default quota over time.
A minor problem (just off/on quotas every now and then to workaround), would be nice to see if anyone else experiences this and if there is a fix available / or in the pipeline ?
~Jason
-----Original Message----- From: John Stoffel [mailto:john.stoffel@taec.toshiba.com] Sent: 24 March 2005 17:50 To: Charles Bartels Cc: Palmer, Jason (EMEA); Adam McDougall; toasters@mathworks.com Subject: RE: converting root volume to flexvol
Charles> A small comment on the plan below. The command to set the root Charles> aggregate (step 4) gives an error:
Filer1> aggr options aggr1 root Charles> aggr options: option 'root' can be modified only in maintenance mode
Charles> This isn't a problem though since you just need to set the Charles> root volume. The root aggregate will change automatically Charles> upon reboot.
Just to clarify things here, since we're looking to goto OnTap 7.0 in the near future... you can just skip step 4 below, since upon reboot the aggregate with the root volume will automatically get the 'root' flag set properly? So you just need to the:
vol options root newroot
and reboot?
Charles> And just a generally comment on the Netapp size Charles> "recommendation" for a flexible root vol. I've seen three Charles> different docs that discuss the size of the root vol. One Charles> suggested 30GB, two others said you should use something Charles> around 90GB. All those suggestions are patently insane.
I assume they want to leave room for upgrades and log files. But sure, I think 30gb is way to damm big as well...
Charles> I keep 3 months works of root vol snapshots; the total size Charles> is somewhere around 300MB. A few gigs should easily be Charles> enough to handle most situations. I don't understand what Charles> the people who wrote the docs were thinking.
Charles> -----Original Message----- Charles> From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Charles> On Behalf Of Palmer, Jason (EMEA) Charles> Sent: Wednesday, March 02, 2005 5:49 AM Charles> To: 'Adam McDougall'; toasters@mathworks.com Charles> Subject: RE: converting root volume to flexvol
Charles> Hi Adam, Charles> I successfully moved to a root volume on a flexible volume within an Charles> aggregate last week without any problems... Charles> I used ndmpcopy from the command line of the filer and followed the Charles> steps below - Charles> 1. Create the Aggregate (In our case a 3 disk root aggregate called Charles> AGGR) Charles> 2. Create new flexible root volume within that aggregate (I called Charles> this rootnew as we already have a root volume) Charles> 3. NDMPCOPY -l 0 -f <filer>:/vol/root/etc <filer>:/vol/newroot/etc Charles> 4. aggr options aggr root <-- To set the aggr aggregate to Charles> the root aggregate Charles> 5. vol options newroot root <-- To set the rootnew volume to Charles> the root volume Charles> 6. Reboot the filer and verify everything comes back up OK (If not Charles> you can boot in maintenance mode to reset the root volume) Charles> 7. Check that newroot in aggr is the root volume using vol status Charles> 8. If this is the case, rename root volume to rootold and rootnew Charles> to root Charles> 9. Use vol offline rootold to ofline the old root volume and if Charles> 100% happy use the vol destroy Charles> Worked fine for us - I only used the NetApp KB as a guideline. Charles> I have another 5 machines to convert in the same way - I was lucky, as Charles> the first system I did was not storing production data so there were Charles> plenty of disks and no pressure of system downtime to consider. Charles> I hope this helps, Charles> Jason Palmer Charles> Storage Architecture Charles> MCI EMEA