I have a vm running windows 2003 with DFM on it monitoring a few filers. Its been running for years, and I have gone from DFM 3.3 on up to 4.x.
The question is this.
The drive that has the application installed on it is heavily fragmented. All the fragmentation is in the perf data type files.
Any thoughts? I have run the defrag multiple times.
12,610 7.26 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_1331 9,746 8.19 GB \Appspub\DFM\DFM\perfdata\perf_183_5279_12249 8,363 7.46 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_5022 6,523 1.65 GB \Appspub\DFM\DFM\perfdata\perf_8_282_1333 5,505 264 MB \Appspub\DFM\DFM\perfdata\perf_245_5390_4 4,483 3.52 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_1310 2,941 4.64 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5808 2,433 4.33 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5425 2,256 4.73 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5881 2,028 4.59 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2356 1,943 190 MB \Appspub\DFM\DFM\perfdata\perf_4_21270_3 1,224 1.74 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2541 1,063 3.51 GB \Appspub\DFM\DFM\perfdata\perf_183_5279_12995 1,017 1.72 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2539 966 2.33 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_2658 866 160 MB \Appspub\DFM\DFM\perfdata\perf_1_21270_13 770 121 MB \Appspub\DFM\DFM\perfdata\perf_6_26686_8 724 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-0.log 718 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-1.log 681 416 MB \Appspub\DFM\DFM\perfdata\perf_184_5279_141 645 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-2.log 615 3 MB \Appspub\DFM\DFM\log\audit-2.log 614 3 MB \Appspub\DFM\DFM\log\audit-1.log 585 3 MB \Appspub\DFM\DFM\log\audit-0.log 580 2 MB \Appspub\DFM\DFM\log\dfmwatchdog.log 561 5.27 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_4561 525 290 MB \Appspub\DFM\DFM\perfdata\perf_9_21271_62 517 173 MB \Appspub\DFM\DFM\perfdata\perf_242_5390_26 499 2.84 GB \Appspub\DFM\DFM\data\monitordb.db 485 714 MB \Appspub\DFM\DFM\perfdata\perf_9_10195_134
It's a lot of huge constantly open files. To defrag it you're probably going to have to stop DFM, move the files to a separate file system and then restart DFM.
Then it will not be fragmented for a few weeks until the drive starts to fill up again!
As far as preventing it you can schedule defrags but I think mostly that will just slow it down :(
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of steve klise Sent: Thursday, March 17, 2011 12:15 PM To: toasters@mathworks.com Subject: DFM 4.01 fragmentation on windows 2003 server
I have a vm running windows 2003 with DFM on it monitoring a few filers. Its been running for years, and I have gone from DFM 3.3 on up to 4.x.
The question is this.
The drive that has the application installed on it is heavily fragmented. All the fragmentation is in the perf data type files.
Any thoughts? I have run the defrag multiple times.
12,610 7.26 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_1331 9,746 8.19 GB \Appspub\DFM\DFM\perfdata\perf_183_5279_12249 8,363 7.46 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_5022 6,523 1.65 GB \Appspub\DFM\DFM\perfdata\perf_8_282_1333 5,505 264 MB \Appspub\DFM\DFM\perfdata\perf_245_5390_4 4,483 3.52 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_1310 2,941 4.64 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5808 2,433 4.33 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5425 2,256 4.73 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5881 2,028 4.59 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2356 1,943 190 MB \Appspub\DFM\DFM\perfdata\perf_4_21270_3 1,224 1.74 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2541 1,063 3.51 GB \Appspub\DFM\DFM\perfdata\perf_183_5279_12995 1,017 1.72 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2539 966 2.33 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_2658 866 160 MB \Appspub\DFM\DFM\perfdata\perf_1_21270_13 770 121 MB \Appspub\DFM\DFM\perfdata\perf_6_26686_8 724 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-0.log 718 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-1.log 681 416 MB \Appspub\DFM\DFM\perfdata\perf_184_5279_141 645 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-2.log 615 3 MB \Appspub\DFM\DFM\log\audit-2.log 614 3 MB \Appspub\DFM\DFM\log\audit-1.log 585 3 MB \Appspub\DFM\DFM\log\audit-0.log 580 2 MB \Appspub\DFM\DFM\log\dfmwatchdog.log 561 5.27 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_4561 525 290 MB \Appspub\DFM\DFM\perfdata\perf_9_21271_62 517 173 MB \Appspub\DFM\DFM\perfdata\perf_242_5390_26 499 2.84 GB \Appspub\DFM\DFM\data\monitordb.db 485 714 MB \Appspub\DFM\DFM\perfdata\perf_9_10195_134
-- View this message in context: http://old.nabble.com/DFM-4.01-fragmentation-on-windows-2003-server-tp31 174070p31174070.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.
+1 on this recommendation and fix.
It's also a very good idea to put PA data on a different disk for performance IO. DFM services are quite intensive, mostly in cpu but disk as well.
I would highly recommend NOT putting it on a different partition of the same drive. If it's staying on one drive, leave it all in the same partition.
Jeff Kennedy Qualcomm, Incorporated QCT Engineering Compute 858-651-6592
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Page, Jeremy Sent: Thursday, March 17, 2011 9:31 AM To: steve klise; toasters@mathworks.com Subject: RE: DFM 4.01 fragmentation on windows 2003 server
It's a lot of huge constantly open files. To defrag it you're probably going to have to stop DFM, move the files to a separate file system and then restart DFM.
Then it will not be fragmented for a few weeks until the drive starts to fill up again!
As far as preventing it you can schedule defrags but I think mostly that will just slow it down :(
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of steve klise Sent: Thursday, March 17, 2011 12:15 PM To: toasters@mathworks.com Subject: DFM 4.01 fragmentation on windows 2003 server
I have a vm running windows 2003 with DFM on it monitoring a few filers. Its been running for years, and I have gone from DFM 3.3 on up to 4.x.
The question is this.
The drive that has the application installed on it is heavily fragmented. All the fragmentation is in the perf data type files.
Any thoughts? I have run the defrag multiple times.
12,610 7.26 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_1331 9,746 8.19 GB \Appspub\DFM\DFM\perfdata\perf_183_5279_12249 8,363 7.46 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_5022 6,523 1.65 GB \Appspub\DFM\DFM\perfdata\perf_8_282_1333 5,505 264 MB \Appspub\DFM\DFM\perfdata\perf_245_5390_4 4,483 3.52 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_1310 2,941 4.64 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5808 2,433 4.33 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5425 2,256 4.73 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_5881 2,028 4.59 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2356 1,943 190 MB \Appspub\DFM\DFM\perfdata\perf_4_21270_3 1,224 1.74 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2541 1,063 3.51 GB \Appspub\DFM\DFM\perfdata\perf_183_5279_12995 1,017 1.72 GB \Appspub\DFM\DFM\perfdata\perf_205_5281_2539 966 2.33 GB \Appspub\DFM\DFM\perfdata\perf_8_5279_2658 866 160 MB \Appspub\DFM\DFM\perfdata\perf_1_21270_13 770 121 MB \Appspub\DFM\DFM\perfdata\perf_6_26686_8 724 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-0.log 718 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-1.log 681 416 MB \Appspub\DFM\DFM\perfdata\perf_184_5279_141 645 3 MB \Appspub\DFM\DFM\log\dfmwatchdog-2.log 615 3 MB \Appspub\DFM\DFM\log\audit-2.log 614 3 MB \Appspub\DFM\DFM\log\audit-1.log 585 3 MB \Appspub\DFM\DFM\log\audit-0.log 580 2 MB \Appspub\DFM\DFM\log\dfmwatchdog.log 561 5.27 GB \Appspub\DFM\DFM\perfdata\perf_8_21270_4561 525 290 MB \Appspub\DFM\DFM\perfdata\perf_9_21271_62 517 173 MB \Appspub\DFM\DFM\perfdata\perf_242_5390_26 499 2.84 GB \Appspub\DFM\DFM\data\monitordb.db 485 714 MB \Appspub\DFM\DFM\perfdata\perf_9_10195_134
-- View this message in context: http://old.nabble.com/DFM-4.01-fragmentation-on-windows-2003-server-tp31 174070p31174070.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.
ok, with the help of a Netapp person, I was able to resolve or at least work around the issue. I had over 1 years worth of fiber channel perf data, as well as some other perf counters that were stale. I also had stale perf counters from previous filers that may have never been properly cleaned up. I have been running DFM since 3.3 or so, so it was recomended to delete all perfdata. I stopped DFM, deleted all the perf data, and started again. New files are created... and I reclaimed about 130GB of FRAGMENTED space.. Some counters are set to 1 year by default (FC for example). I only really need a month for that, or less.. I was worried about loosing my trending data, but this is in the db, so no loose there.
There is an internal netapp doc which is GREAT in determining which filers relate to the perfdata file, and how to clean them up a bit. You will have to call support and ask for it. KB ID: 1011879
Reid walked me through changing some new values in performance advisor. Launch NMC, click on setup, hosts, edit data collection. Change the values you want, done.
Reid from Netapp, your a rock star! Thanks
ok, with the help of a Netapp person, I was able to resolve or at least work around the issue. I had over 1 years worth of fiber channel perf data, as well as some other perf counters that were stale. I also had stale perf counters from previous filers that may have never been properly cleaned up. I have been running DFM since 3.3 or so, so it was recomended to delete all perfdata. I stopped DFM, deleted all the perf data, and started again. New files are created... Some counters are set to 1 year by default (FC for example). I only really need a month for that, or less.. I was worried about loosing my trending data, but this is in the db, so no loose there.
There is an internal netapp doc which is GREAT in determining which filers relate to the perfdata file, and how to clean them up a bit. You will have to call support and ask for it. KB ID: 1011879
Reid walked me through changing some new values in performance advisor. Launch NMC, click on setup, hosts, edit data collection. Change the values you want, done.
Reid from Netapp, your a rock star! Thanks
-
Kennedy, Jeffrey -
Page, Jeremy -
steve klise