As far as I can remember this is a normal behaviour of SFS if you mean what you can see in Scouts Task list. Only J?rg can tell you details about this.

@Framiga
Quote:

Sorry for the very late reply (forgot this forum). Yes I allways used HDInstTools.

Quote:

Does that mean that you couldn`t write any further file to that partition?

@Framiga

>150 dosbuffers on a ~30 GB partition? no way!

Do you mean that the amount of 150 dosbuffers are responsible for the problem? I would use a higher amount but I`ve only 32MB available. Thats the reason for the 150 buffer. :(

Alas I have to report that I got the same problem again. After deleting some files from .recycled it worked again.

Hi J?rg! I hope you can tell something about.

I mentioned something strange. I add a partition (DH11) with HDInstTools 10 days ago. The whole last range of the HD. Until now I used it only for recordings with AHIRecord what writes 256kb at once (editable) to the file. That worked fine until now. Suddenly AHIRecord start writing 256kb and then hangs. I can reboot an start AHIRecord what wirts another 256kb file and hangs. On other partition (eg. DH4) it works well. I thought maybe someting is full or think so. Then I delete .recycled dir (about 8GB) on DH11 and tried AHIRecord again. Now it works. It would be a pitty if this happens again.

On my other (nearly full) partition (DH4) with SmartFilesystem 2.3 (28.09.00) I never had such a problem.

Einheit Gr??e Genutzt Frei Voll Fhlr Status Typ Name
DH4: 12,9G 12,3G 624,4M 95% 0 schr.-/lesbar SFS2 Rec


Here the problem partition:

Einheit Gr??e Genutzt Frei Voll Fhlr Status Typ Name
DH11: 27,2G 8,0G 19,3G 29% 0 schr.-/lesbar SFS0 Rec2

SFSquery information for dh11: (SFS Version 1.279)
Start/end-offset : 0x0000000b:d3234000 - 0x00000012:a1f16000 bytes
Device API : NSD (64-bit)
Bytes/block : 512 Total blocks : 57108240
Cache accesses : 30688 Cache misses : 24855 (80%)
Read-ahead cache : 8x 8192 bytes (Copyback)
Flush timeout : act. 20s - inact. 0.5s
Max Name Length : 107
DOS buffers : 150
SFS settings : [RECYCLED]

SFSCheck:
Partition start offset : 0x0000000b:d3234000 End offset : 0x00000012:a1f16000
Surfaces : 1 Blocks/Track : 324
Bytes/Block : 512 Sectors/Block : 1
Total blocks : 57108240
Device interface : NSD (64-bit)

Checking RootBlocks
...okay
Checking AdminSpaceContainers at block 2
...okay
Checking NodeContainers at block 7
...okay
Checking ObjectContainers at block 3
...okay
Checking Bitmap at block 34 (14278 blocks, 4000 bits/bitmap)
...okay

Ok, when we at least talk about CF-to-IDE Adapter then the CF should recognized as a normal HD. This is what I read about it and users that use CF-to-IDE Adapter told me. Of courese you can remove and replace it with another CF like HD`s. :)

BTW somebody knows if a CF can be dis- connected while Amiga is working? I think this won`t work.

@TetiSoft

Hmm... I thought CF-Cards can be used and will be detected as a normal harddrive. So removeable or not shouldn`t make a difference. As far as I know CF-Cards can also partitioning with HDToolBox or HDInstTools. So writing a RDB should be possible too.

Somebody else have such problems formating CF-Cards with SFS 1.267?