Hi, long time reader, first time poster, love your list, etc etc etc.
Do max inode counts follow snapshots? That is, if I do a snapshot on Monday, increase the inode counts on Tuesday, wipe my files on Wednesday and bring things back from the snapshot on Thursday, do I still need to increase the inode count as I did on Tuesday?
-dan
chaney@iglou.com (DANIEL CHANEY) writes:
Hi, long time reader, first time poster, love your list, etc etc etc.
Do max inode counts follow snapshots? That is, if I do a snapshot on Monday, increase the inode counts on Tuesday, wipe my files on Wednesday and bring things back from the snapshot on Thursday, do I still need to increase the inode count as I did on Tuesday?
What sort of "bringing things back" are you talking about here? Copying individual files from a snapshot into the active filing system will assign new inode numbers to them anyway. If you are doing this to so many files that you run out of inodes, then you probably also have a problem with available space.
If you are reverting the whole volume with SnapRestore, then my initial thought was that the maxfiles values would revert as well, but I've found something on now.netapp.com that says that it won't. Anyone done the experiment?
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.
chaney@iglou.com (DANIEL CHANEY) writes:
Hi, long time reader, first time poster, love your list, etc etc etc.
Do max inode counts follow snapshots? That is, if I do a snapshot on Monday, increase the inode counts on Tuesday, wipe my files on Wednesday and bring things back from the snapshot on Thursday, do I still need to increase the inode count as I did on Tuesday?
If you are reverting the whole volume with SnapRestore, then my initial thought was that the maxfiles values would revert as well, but I've found something on now.netapp.com that says that it won't. Anyone done the experiment?
Yes, I meant SnapRestore, sorry for the vagaries associated with "bringing things back" - Out of curiousity, what did you find on now.netapp that addresses this, my initial search came up thin at best.
-dan
chaney@iglou.com (DANIEL CHANEY) writes: [...]
Do max inode counts follow snapshots? That is, if I do a snapshot on Monday, increase the inode counts on Tuesday, wipe my files on Wednesday and bring things back from the snapshot on Thursday, do I still need to increase the inode count as I did on Tuesday?
If you are reverting the whole volume with SnapRestore, then my initial thought was that the maxfiles values would revert as well, but I've found something on now.netapp.com that says that it won't. Anyone done the experiment?
Yes, I meant SnapRestore, sorry for the vagaries associated with "bringing things back" - Out of curiousity, what did you find on now.netapp that addresses this, my initial search came up thin at best.
Searching on "snaprestore" and picking the first hit got me to
"Volume reversion using SnapRestore" http://now.netapp.com/NOW/knowledge/docs/ontap/rel53/html/sag/disk9.htm
in which one finds:
| What SnapRestore reverts | | SnapRestore reverts only the file contents. It does not revert attributes of | a volume. For example, the snapshot schedule, volume option settings, RAID | group size, and maximum number of files remain unchanged after the reversion. | | Option settings applicable to the entire filer, however, might be reverted. [... etc ...]
Of course, having found this, one can see that it also appears in the downloaded 5.3 SAG (html or pdf), page 101, and I suppose even in the printed version... :) [I've only got the 5.2 SAG in the form of dead trees.]
Chris Thompson Email: cet1@cam.ac.uk
-
Chris Thompson -
DANIEL CHANEY