Hi, forgive me if these questions are too basic, but I need to clarify them first before start using our F760 Ontap 5.3.5R2. I'm in the learning process and I just could'nt find any faq on the net.
true or false ?
we cannot reduce size of a volume or reduce number of disk once allocated to a volume.
we connot take a volume offline (from online state) without rebooting.
we cannot create a volume in that it will become offline when created.
we have to destroy entire volume to delete qtree.
we cannot set maxfiles value for qtree. We have to set by volume. (I'm worrying about the news spool where we used to have a 512 bytes/inode on our UFS. How does everyone set their news spool, create a qtree for news spool or a separate volume ?)
I don't understand below statement in System Administration Guide pg 72-73 : what does it mean by "The maximum RAID group size is 52 disks." when "The largest RAID group size you can create manually is 28 disks."
thanks, --ihsanna
__________________________________________________ Do You Yahoo!? Get Yahoo! Mail � Free email you can access from anywhere! http://mail.yahoo.com/
forgive me if these questions are too basic, but I need to clarify them first before start using our F760 OnTAP 5.3.5R2. I'm in the learning process and I just couldn't find any faq on the net.
true or false ?
I'll do my best :)
we cannot reduce size of a volume or reduce number of disk once allocated to a volume.
True.
we connot take a volume offline (from online state) without rebooting.
True; this is not currently supported. This will change in a future release.
we cannot create a volume in that it will become offline when created.
Not as far as I'm aware. Once the point above is resolved, I suspect this wouldn't be as much as issue for you.
we have to destroy entire volume to delete qtree.
False; just delete the directory (after removing any NFS & CIFS shares that refer to it)
we cannot set maxfiles value for qtree. We have to set by volume. (I'm worrying about the news spool where we used to have a 512 bytes/inode on our UFS. How does everyone set their news spool, create a qtree for news spool or a separate volume ?)
You can use qtree quotas to limit the # of files in a qtree (the last field; refer to quotas(5) for more info).
The benefits of using a separate volume for news is that you probably want a different snapshot regime for news than general purpose data, and you'd also probably set the minra and no_atime volume options (which you can't adjust per qtree)
I don't understand below statement in System Administration Guide pg 72-73 : what does it mean by "The maximum RAID group size is 52 disks." when "The largest RAID group size you can create manually is 28 disks."
I believe certain older systems & releases *may* have supported up to 52 disks but I'm not 100% certain. I definitely know it was at least 28 disks on the F330. The default is now 14 disks per raid group, and you can tweak this up to 28 disks per raid group but this isn't recommended due to the increase change of data loss due to the exposure to a double disk failure. There's a white paper on the NetApp web site tech library about this: http://www.netapp.com/tech_library/3027.html
Hope that helps, Luke.
-- Luke Mewburn lukem@netapp.com Systems Engineer, Network Appliance Melbourne, Australia Phone: +61 419 361 266, Fax: +61 3 9866 1011
Here is what used to be: F210-> max of 14x4GB or 7x9GB disks F220-> same F230-> max of 28x4GB or 14x9GB disks F520-> max of 28x9GB disks F540-> max of 52x4GB disks F630-> max of 52x4GB or 52x9GB disks
All of these system are able to run pre-5.0 software. Before 5.0, there was no concept of multiple RAID groups. Filesystems that were upgraded to a newer release are "grandfathered"...i.e. we let all the disks in a single volume move forward, and in the case of a F540 or F630, that could mean, in a worst case, 51 data and 1 parity drive.
So, when the docs say "The maximum RAID group size is 52 disks.", that would be a grandfathered filesystem.
The default RAID group size if 14 disks, unless you tell it to use 28, or the filesystem already has more than 14 disks.
--tmac
I don't understand below statement in System Administration Guide pg 72-73 : what does it mean by "The maximum RAID group size is 52 disks." when "The largest RAID group size you can create manually is 28 disks."
I believe certain older systems & releases *may* have supported up to 52 disks but I'm not 100% certain. I definitely know it was at least 28 disks on the F330. The default is now 14 disks per raid group, and you can tweak this up to 28 disks per raid group but this isn't recommended due to the increase change of data loss due to the exposure to a double disk failure. There's a white paper on the NetApp web site tech library about this: http://www.netapp.com/tech_library/3027.html
Hope that helps, Luke.
-- Luke Mewburn lukem@netapp.com Systems Engineer, Network Appliance Melbourne, Australia Phone: +61 419 361 266, Fax: +61 3 9866 1011
-- ******All New Numbers!!!****** ************* *************
Timothy A. McCarthy --> System Engineer, Eastern Region Network Appliance http://www.netapp.com 240-268-2034 Office \ / Page Me at: 240-268-2001 Fax / 888-971-4468
I believe certain older systems & releases *may* have supported up to 52 disks but I'm not 100% certain.
Luke is correct. Once upon a time, Data ONTAP only supported one volume (file system), underpinned by one RAID group. The largest configuration that was ever made available during this period was the 468GB (raw) F630, which achieved that capacity using 52x9GB drives.
When multi-volume, multi-RAID (MV/MR) functionality was first introduced in Data ONTAP 5.0, it was decided to reduce the maximum RAID group size down to 28. This was not because 52 drive RAID group configurations had ever shown themselves to be a problem in practice (they hadn't), but because it just seemed prudent given the new capabilities. As I believe most of the folk on this list will attest to, the default of 14 drive RAID groups yields tremendous reliability, at a parity-cost that most customers are happy to accept.
Anyway, when MV/MR came along with its then-new 28 drive maximum RAID group size, the software continued to support the existing/preceeding SV/SR configurations that involved more than 28 drives, such that those configurations didn't have to be disrupted or reconfigured to run the new code. This was, and still is, handled as an exception to the "new" MV/MR rules.
Keith
-
Abu Ihsan -
Keith Brown -
Luke Mewburn -
Timothy A. McCarthy