Wednesday, January 31, 2007

Quick Googler Updates

I'm hurting from a surprisingly small amount of alcohol last night. I'm getting nothing done today which may be for the better. Here are some more search referrals which ended up landing people here, none of whom actually posted a comment explaining what exactly they wanted to know.

canine slavegirl
I don't want to know. I really don't.

I hate Citrix

Me too, but CTRX stock looks like it might be on an uptrend (although it's down almost 50% from seven months ago). If it drops below $30 I might buy some.

"String data, right truncated" Oracle xp
Your buffer's too small for the data or message you're pulling.

Pretty much limited to pantomime. Despite the appearance of live bovines in the Muppet Show episode with Julie Andrews and a few seasons of Green Acres, there's surprisingly little opportunity for LIVEBEEF in the entertainment industry, and not a single reference to stageplays calling for actual moo-cows. Sorry. You could always try a 4-H show.

Hillary. And yes, her balls are bigger.

filemon what is fastio_write
what is fastio_write
what does FASTIO_WRITE do

All very good questions, all about FileMon and Process Monitor, and answered nowhere on the fucking Intarweb's tubes. Until now. All of you "Expert's Exchange" cut-and-paste scum better give me fucking credit for this answer.

FastIO is a simple extension for normal IRP-packet queues. When some part of the code wants to read data it creates an IRP packet. This packet is then passed to the IO manager which determines which device will receive this IRP request. Unfortunately IRP requests are slow since they need to wake internal subsystems. If FastIO is called, it throws driver objects directly. IRP (Interrupt Process) is device-level and FastIO is driver-level. If a file operation is requested and that operation had already been completed recently, the file system can perform its operations faster by a direct call to allocated buffers.

FastIO will always be called for disk reads and writes first. If it fails for whatever reason, the
IRP call comes right behind it and is normally successful. If it isn't, there's your problem.

If you see a FASTIO_WRITE which fails followed by a retry in the interrupt routine IRP_MJ_WRITE which succeeds, and the the offset and length are the same, everything is fine.

they are all out to get me
Sure feels like it sometimes, huh?

Labels: ,


Anonymous Chris pulled out a crayon and scribbled:


I've been trying to find out information about this, as I was starting to panic that the something was wrong with the storage sub-system we had.

You cleared it up for me.

Thanks again

14 June, 2011 16:55  
Anonymous Anonymous pulled out a crayon and scribbled:

It sure does.

26 May, 2016 22:02  

Post a Comment

Links to this post:

Create a Link

<< Home

In compliance with $MegaCorp's general policies as well as my desire to
continue living under a roof and not the sky or a bus shelter, I add this:

The views expressed on this blog are my own and
do not necessarily reflect the views of $MegaCorp, even if every
single one of my cow-orkers who has discovered this blog agrees with me
and would also like to see the implementation of Root Cause: 17-Fuckwit.