Using a real harddisk
Wolfgang Schmidt
wolfgang.schmidt at ...243...
Mon Aug 11 15:48:22 CEST 2014
Hi,
I have still the old problem with using the blk_cache and rump_fs (latest
release 14.05).
I tried to do the following:
- have a larger blockcache which is used by part_blk
- have multiple partitions and rump_fs (which is working) which nearly no
cache and which shoudl threfore use the blockcache (which is not working)
I shortened the configuration below to the relevant(hopefully) part with
only one partinion.
If I use the configuration 1 i can read / write a file on the system.
With configuration 2 the system seems to stop without any further
information. (same result with config 3)
[init -> rump_fs] upgrading quota donation for SIGNAL session
[init -> rump_fs] Backend::Backend(): Backend blk_size 512
[init -> rump_fs] rump: /genode: file system not clean; please fsck(8)
-execution seems to stop here-
The "file system not clean" seems not to be the relevant part, it is also
shown if the program steps through.
(with config 1
[init -> rump_fs] upgrading quota donation for SIGNAL session
Quota exceeded! amount=20480, size=4096, consumed=20480
[init -> rump_fs] upgrading quota donation for SIGNAL session
[init -> rump_fs] Backend::Backend(): Backend blk_size 512
[init -> rump_fs] rump: /genode: file system not clean; please fsck(8)
Quota exceeded! amount=24576, size=4096, consumed=24576
[init -> rump_fs] upgrading quota donation for SIGNAL session
Quota exceeded! amount=94208, size=4096, consumed=94208
[init -> rump_fs] upgrading quota donation for Env::RM (8192 bytes)
Quota exceeded! amount=28672, size=4096, consumed=28672
[init -> rump_fs] upgrading quota donation for SIGNAL session
... and so on until file is read/written
)
What am i possibly doing wrong?
Best regards,
Wolfgang
----------------------------------------------------------------------------------------------------------
Config 1 (part)
<start name="ahci">
<binary name="ahci" />
<resource name="RAM" quantum="10M" />
<provides><service name="Block" /></provides>
<route>
<service name="IRQ"><child name="acpi" /></service>
<any-service> <parent /> <any-child /></any-service>
</route>
</start>
<start name="part_blk">
<resource name="RAM" quantum="18M" />
<provides><service name="Block" /></provides>
<route>
<any-service><child name="ahci"/>
<parent/><any-child/></any-service>
</route>
<config>
<policy label="rump_fs" partition="5"/>
</config>
</start>
<start name="rump_fs">
<resource name="RAM" quantum="42M" />
<provides><service name="File_system"/></provides>
<config fs="ext2fs"><policy label="" root="/" writeable="yes"/></config>
<route>
<service name="Block"><child name="part_blk" /></service>
<any-service> <parent /> <any-child /></any-service>
</route>
</start>
-------------------------------------------------------------------------------------------------
Config 2:
<start name="ahci">
unchanged ..
</start>
<start name="blk_cache">
<resource name="RAM" quantum="18M" />
<provides><service name="Block" /></provides>
<route>
<any-service><child name="ahci"/>
<parent/><any-child/></any-service>
</route>
</start>
<start name="part_blk">
<resource name="RAM" quantum="18M" />
<provides><service name="Block" /></provides>
<route>
<any-service><child name="blk_cache"/>
<parent/><any-child/></any-service>
</route>
<config>
<policy label="rump_fs" partition="5"/>
</config>
</start>
<start name="rump_fs">
unchanged ...
------------------------------------------
Config 3
<start name="blk_cache">
<resource name="RAM" quantum="18M" />
<provides><service name="Block" /></provides>
<route>
<service name="Block"><child name="ahci" /></service>
<any-service> <parent /> <any-child /></any-service>
</route>
</start>
More information about the users
mailing list