Syslog Server Disk Space with ASA5510

Hi,
i'm about to configure a syslog server to receive syslog messages from a Cisco ASA5510 and being it a one week test I was wondering how much space should I allocate on the machine hosting the tool (kiwi syslog).
I see that the ASA fills the internal syslog buffer to 4MB and then it overrides it. How many messages would those 4MB be?
Thanks for your help.

Hello,
I copied 30 messages off my firewall into a text file and it's a little over 3 KB in size (which averages out to about 100 bytes per message). That means that 4 MB would be about 40,000 messages. As a side note, the ASA's maximum local buffer size is about 1 MB, rather than 4 MB.
How much disk space you should allocate for log storage will depend greatly on what level of syslogging you're doing, how much traffic the firewall sees, and how long you want to keep the logs for. Hopefully the above numbers will give you a rough idea of a baseline that you can expand on to meet your requirements.
Hope that helps.
-Mike

Similar Messages

OCS server disk space is getting occupied automatically

Hi All,
I was observing my OCS server (10.1.2.3.0)
Even when the system is idle also i can find the disk space is getting used
I had faced the problem twice like, the total diskspace (100%) has been used
Please observe the following (this is a test instance), see the /d01 disk space:
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040540 2138320 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040548 2138312 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040552 2138308 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040552 2138308 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71040556 2138304 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
[oracle@ocs oradata]$
[oracle@ocs oradata]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 2063504 507836 1450848 26% /
/dev/sda1 101089 15131 80739 16% /boot
/dev/sda2 77095104 71085668 2093192 98% /d01
/dev/sda10 15172120 5820760 8580644 41% /d02
/dev/sda9 1035660 84628 898424 9% /home
none 1282912 0 1282912 0% /dev/shm
/dev/sda7 2063504 44676 1914008 3% /tmp
/dev/sda6 3194048 2182744 849052 72% /usr
/d01 is the location where i installed the OCS
Is this a problem coz of the database configuration.. when it reaches the 100% usage, then it wont allow any new connections to the database.
I feel like this may damage the application
Anybody has any idea about why this is happening..???
Please update ....
Best Regards and Many Thanks in Advance...!!!,
Prasant

Hi,
Many Thanks for your update..
Answering to your queries..
1. I am not copying data
2. The database is not in ARCHIVELOG mode
3. I can find the following location files are getting updated continuously
$ORACLE_HOME/network/log/sqlnet.log (infra Home) (File size : 28672 KB)
$ORACLE_HOME/network/log/listener.log (infra Home) (this file size is 1057443840 KB)
$ORACLE_HOME/sqlnet.log (infra Home) (File Size: 1306624 KB)
$ORACLE_HOME/network/log/sqlnet.log (apps Home) (File Size: 2789376 KB)
well as well as how can i regain my free spaces.. it had around 15GB free space available before..!!
So what can i do to rectify this ...
Awaiting your response...
Best Regards....
prasant
Message was edited by:
ark_505

How can I see the rest of the disk space with SCCM 2012 R2?

I can see most the elements of PCS in the report of assets intelligence function in SCCM 2012 R2 ,except for the free disk space.
Thus, I cannot be noticed when some servers need more space.
What should I do?

Hi,
Please check the following steps.
SCCM Console -> Administration -> Client Settings -> Hardware Inventory -> Set classes -> Logical Disk(SMS_LogicalDisk) -> Free Space(MB)
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Error message "Insufficent disk space" with no reason

While I play back my soundtrack on Soundtrack Pro I sometimes get a message that SP has hit a "disk size" limit even though my drive has more than enough capacity. I was wondering if anyone got a similar message.
Thank you!

i've run into similar problems while assembling large files (4+ hours) out of multiple bits. After watching my primary hard drive mysteriously dwindle from 16GB free to <300gb free during a work session yesterday, i figured out a simple solution - save your project early to a secondary (or tertiary) drive that's got *a lot* of free space. i started my project again, and saved almost immediately to my open 120gb scratch drive. i then was able to work through the rest of my project without my primary drive's free space mysteriously disappearing and without getting any more errors.
if you don't have a space scratch drive in your box, just go get one. it will be well worth it.

Saving disk space with aperture, help please?

Ok, let me start by saying I am using a Macbook Pro 17inch model, with a 120gb HD. I just recently switched this summer to Mac over from PC. Now iPhoto has not been very satisfying to me, so that prompted me to buy Aperture. When I used my PC, which I still use now since it is a powerful desktop that I customized and has all my main hard drives hooked up to, I was used to using Google's Picasa software for organizing and searching my photo database. Picasa was very good for me, and I really wish that they had a Mac version of it, but since they don't, I need something to fill that need on my Macbook Pro. As I wrote before, iPhoto does not exactly satisfy me, so I would prefer to find an alternative to it. I am hoping that Aperture can do this, but I am having trouble so far.
Now I only need Aperture for its organizing and database qualities, which I am very impressed by. I do not plan to use it at all for image editing, I leave that to PS, and I don't particularly like the way it creates so many files for each photo and such. My main problem that I am coming across is that when I import my entire photo library (which I have already organized into a very convinient folder heirarchy) into Aperture, it literally doubles the size of my photo library by creating the huge Aperture Library file, and all of the project files within that file. Now I wouldn't mind this too much if it was on my desktop where I have plenty of hard drives to absorb these huge files created, but my desktop is PC for now and can't use Aperture, I plan to get the new Mac Pro next year when my budget can allow for it, but even still, I am not happy with the idea of creating a huge Aperture Library file that essentially doubles the size of my entire photo archive.
Now I noticed this huge file is due to the huge Project files created within the Aperture Library file. Unfortunately, to my knowledge and my trial and error this far, it is impossible to import photos into Aperture without importing them as projects. Am I correct in noting that I can not simply use Aperture for just its organization or database tools? I was really looking forward to getting aperture, but I can not afford to double the size of my entire photo archive on my laptops hard drive, because it is only 120gb and will not be able to sustain a growing photo library like this, especially if it grows at double the size for every photo imported.
Now I do own plenty of external hard drives, and am aware that I can direct Aperture to create its library file on an external hard drive, but it is not too convinient to have to have an external hard drive connected to my laptop every time I want to use Aperture, and not very cost-efficient to have to dedicate a whole external HD just for Aperture's library file, plus I have doubts to how fast the program would run if it is running my library off of an external hard drive.
So in the end, do I need to find another piece of software from an outside company to suit my needs for an image database program? Is it possible to import all my photos into aperture without creating any project files? Please anyone with suggestions for what could help me, please do respond, and thank you in advance for any help.

Thanks for such a quick reply. What you wrote is helpful, and I did consider that at one point... but to go that route would require me to commit completely to using Aperture only for accessing my photos, and would never be able to use other programs to access my photos, I would have to do it all through Aperture, which is not all that bad, but I would like the freedom to access my photos from any program, or from simple folder view. I do see that in the long run it will help conserve HD space, but I really don't like having to commit completely to using only Aperture.
Is it really too much to ask for to have Aperture support maintaining my files in their original location while referencing them in its own library? I don't think that's too much to ask for, every other photo management software is capable of doing this, and at great speeds as well. Even iphoto doesn't create copies of every single item, Google's Picasa on the PC side is EXTREMELY fast and does exactly what I need it to do... I only hope that someone from Apple understands the needs of people like me, as I'm sure I'm not the only one out here who wishes Aperture could work the way I am describing, and hopefully Apple can do something to appeal to this group of people like myself.

Disk space with Photos on Nano 3G

If I sync a folder of 39.7MB of pictures...it becomes 566MB on the Nano. If I sync 300MB of photos it becomes 566MB.
Shouldn't 39.7MB = 39.7MB?
...300MB = 300MB?
Anyone know why this is? Solution?

I don't have a solution but I am running into the same problem.
I found this interesting, on my 1g nano, 2,000 photos takes up about 100 megs of space on the iPod or about 2.5% of my 4 gig iPod. However, on my new 3g nano, the same 2,000 photos takes up about 2 gigs of space which is about a 25% of my 8 gig iPod. That is way too much space to be dedicating for photos. I also notice that the different photo sizes are coming from the same "iPod Photo Cache" in my iPhoto Library.
It seems odd that the new nano creates 1 meg files per photo - the screen is only 320x240. It looks like Apple needs to tweak its software a bit to prevent this waste of space.

How to migrate from my old MacBook Pro to a new one with less disk space and an external hard drive?

I have just bought a new MacBook Pro and an external hard drive.
Yet I have problems migrating data from my old MacBook Pro (more internal disk space with around 500 GB data) to my new one (internal disk space less than 500 GB).
I have connected all 3 devices but it seems the Migration Assistant does not have an option for us to select to migrate to an external hard drive.
Any other way to do it?
Kindly help me. Thanks.

For your situation, Target disk mode may be the most efficient method:
http://support.apple.com/kb/ht1661
Ciao.

I Can't Erase the Empty Space with Disk Utility

It always gets stuck. Last time i tried it, it went all the way almost to the end of the fill bar. then it got stuck.
But even when i did manage to do it using the FASTEST option which just writes ZEROS over the free space 1 time.. I used DISK DRILL to see if it could recover data and yup..it was still recoverable. Another thing i did was fill my free disk space with big huge movie files. And old stuff was still recoverable with Disk drill.
But anyway why Disk Utility Erase Free Disk Space gets stuck? And also why disk drill can still find files even after i empty free disk space or when i fill empty free disk space with new files?

Drive Preparation
1. Boot from your Tiger Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. After completion quit DU and return to the installer. Continue with Tiger installation.

Help-Erasing a Boot Camp Partition Caused 32 GB of Disk Space to Vanish

Hi
I'm a new mac user I'd I have been really happy so far, expect for this problem:
-I created a 32 gb partition with boot camp.
-I tried installing windows xp without knowing I had to format the system to NTFS during the install
The installation didnt work, and I erased the bootcamp partition.
-When I tried to create a new boot camp partition, it said my Mac HD size hard drive is 227 gb, ie the *32 gb allocated to the partition had vanished*. In addition, I could not recreate a partition because of an error message.
-I ran the snow leopard CD's disk utility and thought that I had fixed the problem.
-However in boot camp, the mac drive is still only 227 gb (missing 32 gb). I can create partitions now, and deleting these partitions does cause any additional loss of disk space.
-I tried erasing empty disk space with no luck.
Does anyone know how to recover space lost by Boot Camp?
Thanks

qcpharaoh wrote:
-When I tried to create a new boot camp partition, it said my Mac HD size hard drive is 227 gb, ie the *32 gb allocated to the partition had vanished*. In addition, I could not recreate a partition because of an error message.
-I ran the snow leopard CD's disk utility and thought that I had fixed the problem.
-However in boot camp, the mac drive is still only 227 gb (missing 32 gb). I can create partitions now, and deleting these partitions does cause any additional loss of disk space.
Let me ask a simple question. What size HD do you have in your Mac? You say you see 227 GB and that 32GB is "missing". If I add those two numbers up I com up with 259 GB. I suspect that your "missing" space is due to the inconsistencies in which Snow Leopard now reports 1 GB. In some places it reports 1 GB as a hard disk manufacturer (1 GB = 1,000,000,000 bytes). In other places it reports 1 GB as a binary number (1 GB = 2^^30 [IIRC] = 1,073,741,824 Bytes). Since I do not know of any drive manufacturer that sells a 259 GB drive, I suspect that this is just due to the differing definitions of 1 GB.

Running out of disk space - External Drive Advice

Hi,
I've been importing all of our HDV video in "Large" fomat (Not the original or full size). We have an Apple TV so wanted to get the qaulity up for our large TV.
Anyway, we have lots of digital pics, huge iTunes library and now I'm starting to run out of disk space with all of my iMovie imports.
I would like to buy a huge external drive to help offload:
Is there any reason I should be concerned about storing my video on external drive? Any editing performance issues?
I use time machine, if I buy a huge external, can I split it in half and use part for time machine and part for imovie?
Just curious.
Thx,
Brent

I agree that you can make this work. Your external drive must be formatted as Mac OS Extended (journaled). You can do this as you are creating your 2 partitions in Disk Utility, if it has a different formatting when you buy it.
If you want to move your Events from your internal drive to your new external drive, you need to do it from within iMovie so you do not break the links to your projects. To do this, open iMovie and click VIEW/EVENTS BY VOLUME. You should be able to see a small icon in your Event Library List for your external drive. You can Command-Drag your event icons in the event library list to this icon for your external, and all the links to your projects will be preserved. (hold down the command key while dragging). If you do a simple drag and drop, it will copy not move.

Erase free disk space: 1 time or 7 times?

hey guys,
if I erase free disk space (with disk utility), should I do 1 cycle or 7? Why would there be a difference? In the first cycle, all data will be overwritten with zeros, right? (This does suggest a cycle is not 100% accurate, and you therefore need more cycles?)
And if I do 7 times a single cycle, is that the same as doing one time 7 consecutive cycles?
Thanks for making this clearer... (obviously this is not very urgent, I'm just wondering)

And if I do 7 times a single cycle, is that the same as doing one time 7 consecutive cycles?
No. A single pass just writes zeroes. Do it seven times, and it writes zeros seven times. The multi-pass command uses different bit patterns for each pass. One pass is sufficient, though. A modern drive packs the bits so close together that recovery of any data after a singe overwrite of zeroes is very unlikely. If somebody is that determined to get your data, they will go after you, not the disc. Use the Dictionary widget to look up the second definition of "rendition".

How to find out disk space?

I know two ways to get some information about HD space. One is to Control-click on Mac HD and select Get Info. A dialog is displayed with detail information which contain Capacity, Available and Used numbers in GB.
Another way is to use Terminal with command df -lhg. This command displays similar information. However, by using command, the numbers I get are less than those in Get Info. They are not the same. Not sure if my command is correct or not. If not, what is the correct command to get disk space information?

Great! I will not need to worry about to reset the BLOCKSIZE back to the default value.
One thing interesting. Before I installed the Snow Leopard, I checked my disk space with Get Info. My HD available space was about 466GB. After the OS update, Get Info shows the capacity as 499GB. I thought that I got 30GB more space back. Actually, today I realize that the Get Info value of the pre-OS as based on the binary decimal, and the Get Info value of the Snow Leopard is 10-based decimal! This explains my question about my question of the difference of the Get Info value and the value of command "df -lhg"! "df -lHg" shows the same result, which is 10-based decimal value! I actually did no get more than 30GB disk space.

OCD about disk space

Ok. I'm very ocd about my disk space. I keep track of everything. I'm also a video editor and music collector. This is a funny, 'cause those are the biggest files you can have.
NOW, my Mac says that I've used 83.69gb of disk space with 27.78 left.
I've look through the computer and can only account for roughly 60gb.
I right clicked everything in my "macintosh hd" hard drive folder.
I have 4.72gb of apps, 1.86gb of system info, 19.88gb of library, 34.63gb of user data, and 4k each for cache data and manuals.
I'm still missing 20gb.
I don't really know what to ask.
How do I find that 20gb, or how do I get a detailed map of what my hard drive is holding.
Please and thank you.

Hi Valentine Moreau;
May I suggest a little application that I find to be great when you are attempting to find out what is using up your disk sapce it is called WhatSize.
Allan

QT movie exports taking up double the disk space?

I've been using FCP 5.1.4 to edit a feature film. When I've exported QuickTime movies (Final Cut Pro) movies, I send them to a designated hard drive (Bay 2 of my MacPro). But during the last two exports, I've noticed that when I export to my scratch drive, roughly the same amount of data is suddenly used up on my main start-up drive (in Bay 1).
So, for instance, if I have a 20 GB movie to export to my designated scratch drive, I will suddenly "lose" about the same amount on my main hard disk, even though no movies or FCP settings are saved to that drive. It's quite frustrating, because I'm losing serious disk space with each export, and I can't seem to find the "phantom" movie files on my main hard disk. Simply put, I have no idea what's going on.
If anyone has experienced this (or can refer to to the proper forum, as it might be a MacPro or OSX question), I would appreciate it immensely.
Thank you.

Hi, Patrick.
Thanks for taking the time to respond.
I hadn't thought of the render files possibility... but all of my saved info is going to my designated drive, NOT my main system drive. At least, that's how I set it up. Is it possible that I made an error and accidentally re-routed the file path to my main drive? Possible, but I consider myself to be pretty thorough on such matters...
As for the project info: it's a feature film, and the reason I'm rendering is because I have to create use one of FCP's filters to create a running timecode through out the project (for composers, sound team, etc.). I basically create a QT movie of the sequence, then reimport that movie into FCP, and then apply the timecode filter, and then output a NEW movie with the timecode filter rendered into place.
I'll search around for any errant render folders/files on my main HD. If you (or anyone else) happens to consider some other possibility, by all means, give me a shout out.
Once again, thank you.

Disappearing disk space Windows Server 2012 R2 with SharePoint Server 2013 Enterprise

I've got an interesting problem with a virtual machine in our VMWare environment. It is Windows Server 2012 R2 with SharePoint Server 2013 Enterprise installed. I started out with a 60GB disk and it started running out of space, so I increased
it in VMWare and extended the partition to 100GB. Well, that lasted for a bit and so I extended it again. I've done this 3 or 4 times and now I've got a 160GB disk with about 2-3GB of space remaining (and it started with 10GB remaining).
WinDirStat shows 105GB of <Unknown> space being used, which is probably my issue. However, I can't determine what this is and it keeps growing like a tapeworm. The context menu on the <Unknown> files has all the options disabled,
so WinDirStat doesn't appear to have access to whatever the file(s) is/are. I've performed several chkdsk /f on the C: drive and nothing bad is reported. I don't have any restore points and am not running VSS (that I'm aware of). The pagefile
reports as being about 4.9GB, so that's not the issue. No large files are shown anywhere and my explorer settings are set to show me all files, including system files.
When I try to run WinDirStat with elevated permissions, it hangs and becomes unresponsive.
I've even resorted to running CCleaner to see if it found anything, but it simply found the standard temp files and such...about 1GB.
I'm pulling my hair out...and I don't have much to start with. Anyone have any ideas?
Thanks
Russ

It appears that somehow, Microsoft Fusion Assembly binding logging was turned on and many of the temp folders located at c:\users\username\AppData\Local\Microsoft\Windows\InetCache\IE were filling up with hundreds of thousands of Fusion HTM log files.
This is controlled by an entry in the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\ForceLog which was set to 1. Hopefully, setting it back to zero will fix the issue. As a result of figuring this out, I have recovered almost 80GB of disk
space occupied by the log files.
I thought WinDirStat would show me what I needed to know, but it turns out TreeSize (which I've used in the past) works much better.
Russ

Syslog Server Disk Space with ASA5510

Similar Messages

Maybe you are looking for