Hello again, following up from the mkudffs issues message i posted yesterday.. Looking at the mkudffs source, i found that the application (mkudffs) prints out an error message, and exits without further information when the blocks > start_ext->blocks.. do you have an explanation of what actually happens here, Ben? :) I'm getting this error each time i try to run the mkudffs app through a 'system' function call from a C++ program. Another thing, is that the code looks like this: if (start == start_ext->start) { if (blocks == start_ext->blocks) { ... } else /* blocks > start_ext->blocks */ { printf("trying to change type of multiple extents\n"); exit(1); start_ext->space_type = type; return start_ext; } ..... The statements after the exit(1) are never reached.... why are they there? Thanks, gustavo
On Wed, Sep 11, 2002 at 10:22:24AM -0700, guStaVo ZaeRa wrote:
Hello again,
following up from the mkudffs issues message i posted yesterday..
Looking at the mkudffs source, i found that the application (mkudffs) prints out an error message, and exits without further information when the blocks > start_ext->blocks.. do you have an explanation of what actually happens here, Ben? :)
This occurs when the detected file-system size is smaller than the minimum file-system size. (there prolly should be an explicit test for that case, but there isn't). This usually happens when it detects the size as 0. Could there be some kind of permission problem where it can't determine the actual size? You could try specifying the number of blocks to format explicitly.
The statements after the exit(1) are never reached.... why are they there?
Cut and pasted from the condition 2 above =] Ben
more comments: So, i finally found out what's going on. when the tray is locked mkudffs freaks out. :) gustavo Ben Fennema wrote:
On Wed, Sep 11, 2002 at 10:22:24AM -0700, guStaVo ZaeRa wrote:
Hello again,
following up from the mkudffs issues message i posted yesterday..
Looking at the mkudffs source, i found that the application (mkudffs) prints out an error message, and exits without further information when the blocks > start_ext->blocks.. do you have an explanation of what actually happens here, Ben? :)
This occurs when the detected file-system size is smaller than the minimum file-system size. (there prolly should be an explicit test for that case, but there isn't).
This usually happens when it detects the size as 0.
Could there be some kind of permission problem where it can't determine the actual size? You could try specifying the number of blocks to format explicitly.
The statements after the exit(1) are never reached.... why are they there?
Cut and pasted from the condition 2 above =]
Ben
-- guStaVo ZaeRa | Software Engineer BRE Systems 1532 State Street Suite C Santa Barbara, Ca 93101 gzaera@bresystems.com http://www.bresystems.com --------------------------------------------------------------------- Privacy and Confidentiality Notice: The information contained in this electronic mail message is intended for the named recipient(s) only. It may contain privileged and confidential information. If you are not an intended recipient, you must not copy, forward, distribute or take any action in reliance on it. If you have received this electronic mail message in error, please notify the sender immediately.
On Wed, Sep 11, 2002 at 10:22:24AM -0700, guStaVo ZaeRa wrote:
Hello again,
following up from the mkudffs issues message i posted yesterday..
Looking at the mkudffs source, i found that the application (mkudffs) prints out an error message, and exits without further information when the blocks > start_ext->blocks.. do you have an explanation of what actually happens here, Ben? :)
This occurs when the detected file-system size is smaller than the minimum file-system size. (there prolly should be an explicit test for that case, but there isn't).
This usually happens when it detects the size as 0.
Could there be some kind of permission problem where it can't determine the actual size? You could try specifying the number of blocks to format explicitly.
well... like i said, mkudffs doesn't like that the ioctl( cdromFD, CDROM_LOCKDOOR, 1 ); has been issued, so i solved it by unlocking it before i called system( mkudffs );
The statements after the exit(1) are never reached.... why are they there?
Cut and pasted from the condition 2 above =]
hehe... i kinda figured. :] gustavo
participants (2)
-
Ben Fennema
-
guStaVo ZaeRa