Creating 32MB diskd.img with zerofile script.

[Luis Felipe Bitencourt Emilio]

When I feed 65536 to the zerofile script as it says on the project
description, the diskd.img file it creates has a length of 0 instead of
32MB.

The largest I can get the script to create a file is about 20MB... is
there something wrong with the script?

[Iulian Neamtiu]

Most probably, you've exceeded your quota.
Try running this in your build directory:
$ strace perl ../scripts/zerofile diskd.img 85536

Do you see smth like
close(3) = -1 EDQUOT (Disk quota exceeded) ?

You can check your quota using
$ fs quota
or
$ quota -v

To free some space up, remove some big file, most probably core files
This command will find all files larger than 5 MB:
$ find ./ -size +5000k -exec ls -l {} \;


Iulian

Post by Luis Felipe Bitencourt Emilio
When I feed 65536 to the zerofile script as it says on the project
description, the diskd.img file it creates has a length of 0 instead of
32MB.
The largest I can get the script to create a file is about 20MB... is
there something wrong with the script?

[Luis Felipe Bitencourt Emilio]

Yup! You're right.

Now that I have enough space I have another question. Does it matter
which of the three parameters in the .bochsrc drive geometry we change?
Or do we just need to make sure they multiply to the correct size?

I'm planning on changing cylinders since that seems easy to me.

[Iulian Neamtiu]

Post by Luis Felipe Bitencourt Emilio
Yup! You're right.
Now that I have enough space I have another question. Does it matter
which of the three parameters in the .bochsrc drive geometry we change?
Or do we just need to make sure they multiply to the correct size?
I'm planning on changing cylinders since that seems easy to me.

I don't think it matters, as long as their product is the # of sectors
you set diskd.img to. Cylinder # is a fine choice.

Iulian