OK, the alternative method I've just discovered is to go to the keyboard settings under System Preferences and check the box that says:
Use all F1, F2, etc. keys as standard function keys.
This worked today. We'll see what happens tomorrow.
Working my way toward being a Full Stack Engineer. I work for a state University leading the Systems Team, looking to chart a future of the data center and how it looks to build into the cloud in a responsible and innovative manner. This blog is largely a place to stash things I pick up in daily work life and pursuit of knowledge.
Tuesday, December 1, 2015
Monday, September 28, 2015
Sending F11 to ESXi through UCS KVM on Mac
I just need a place to put this so I remember. I switched to using a Macbook Pro - which I love. But there are some things that just require learning again...
Sending F11 to an ESXi host through a KVM requires:
Fn+Cmd+F11
Now I may remember...
Sending F11 to an ESXi host through a KVM requires:
Fn+Cmd+F11
Now I may remember...
Friday, February 20, 2015
Data Domain CLI commands
In the process of replicating data from a DD640 to DD2500 and we're hitting capacity issues. The Data Domain locks data and won't allow cleaning to have access when it is replicating.
So...
I cancelled replication and manually started cleaning. Last night there was no decrease in data size once cleaning finished. I'm running it again today manually. The commands of the day are:
#filesys clean stat
which displays the current condition of the cleaning, such as:
DD640# filesys clean status
Cleaning started at 2015/02/20 09:00:50: phase 1 of 10 (pre-enumeration)
2.5% complete, 1130 GiB free; time: phase 0:57:55, total 0:57:57
Which is nice, but when you're as retentive as me, you want real-time info on the condition. That's when we use:
filesys clean watch
That will present real-time, updating status of the cleaning job, such as:
DD640# filesys clean watch
Beginning 'filesys clean' monitoring. Use Control-C to stop monitoring.
Cleaning: phase 1 of 10 (pre-enumeration)
3.4% complete, 1130 GiB free; time: phase 1:24:26, total 1:24:28
I also allocated more resources to the cleaning in hope that it gets finished sooner than later. I'm not running any backup during the day to speak of, so I can afford to let those jobs take a back seat to the emergency maintenance.
More as it happens...
So...
I cancelled replication and manually started cleaning. Last night there was no decrease in data size once cleaning finished. I'm running it again today manually. The commands of the day are:
#filesys clean stat
which displays the current condition of the cleaning, such as:
DD640# filesys clean status
Cleaning started at 2015/02/20 09:00:50: phase 1 of 10 (pre-enumeration)
2.5% complete, 1130 GiB free; time: phase 0:57:55, total 0:57:57
Which is nice, but when you're as retentive as me, you want real-time info on the condition. That's when we use:
filesys clean watch
That will present real-time, updating status of the cleaning job, such as:
DD640# filesys clean watch
Beginning 'filesys clean' monitoring. Use Control-C to stop monitoring.
Cleaning: phase 1 of 10 (pre-enumeration)
3.4% complete, 1130 GiB free; time: phase 1:24:26, total 1:24:28
I also allocated more resources to the cleaning in hope that it gets finished sooner than later. I'm not running any backup during the day to speak of, so I can afford to let those jobs take a back seat to the emergency maintenance.
More as it happens...
Subscribe to:
Posts (Atom)