Re: Problem with fcntl/F_LOG2PHYS (was: Re: How to read files from disk directly?)
Re: Problem with fcntl/F_LOG2PHYS (was: Re: How to read files from disk directly?)
- Subject: Re: Problem with fcntl/F_LOG2PHYS (was: Re: How to read files from disk directly?)
- From: Ken Hornstein <email@hidden>
- Date: Thu, 07 Jul 2011 10:06:08 -0400
>> you can see that you get ENOTSUP if the file is compressed (looks like
>> you need to do some magic to make that happen).
>>
>
>Although I didn't specifically mention it, I check functional results /
>errno all the time :) I.e., I did not get any errors.
Ah, I was talking about the return code from VNOP_BMAP(). If you look at
the code section you posted, any error from VNOP_BMAP() gets silently
eaten. (actually, now that I look at it myself ... what source are you
using? In 10.6 that VNOP is now called VNOP_BLOCKMAP()).
>Now that I think about it, the vmem file and the size db files are probably
>open for some kind of access at this time (because VMWare is running, as is
>the Bitcoin computation demon)
>... still, there's no question in my mind this is probably a bug. The
>question is: in fcntl or in the documentation?
Looks like to me that there are no guarantees with F_LOG2PHYS; if
you've got the file open, seems reasonable for F_LOG2PHYS to fail in
this way.
--Ken
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden