SmartFileSystem 1.290 issue
Re: SmartFileSystem 1.290 issue
I use blocksize 512 and buffersize 1000.
Re: SmartFileSystem 1.290 issue
That is really strange. Could it be a harddrive *cable* problem? I have had bad SATA cables much more often than I have had harddrives fail. Please try using a brand new SATA cable.mcleppa wrote:There is an issue with the SFS. There are some consistent faults repeating itself.
I have a partition where I copy a lot of data,moves and deletes. It goes smooth and fast when partition has just been formatted, but when I have deleted a lot of files and copy new files again, the harddisk is working a lot without getting anything copied. It seems to me like it is searching or preparing the required space for the copy. I also thought it could be a HardDisk problem so I bought a new one, but the same thing happens again.
Also, what is your partition's size, and which version of SFS are you using (e.g. SFS/0, SFS/2, etc).
Re: SmartFileSystem 1.290 issue
I have tried a different cable with same result, but I haven't tried to connect it to another SATA port. My partition size was 300GB and I used SFS/2. At the moment I have reformatted it with JXFS to see if I get other results. I would also like to say that I mostly use filesizes of 4.7GB on this partition, that might also be an issue here.
Re: SmartFileSystem 1.290 issue
Ah ha! I think I know the cause then. You previously said:mcleppa wrote:I mostly use filesizes of 4.7GB on this partition, that might also be an issue here.
What is probably happening is that SFS is making space by emptying the hidden .recycled directory, which contains deletes files (which thus take up space until they are automatically deleted).but when I have deleted a lot of files and copy new files again, the harddisk is working a lot without getting anything copied. It seems to me like it is searching or preparing the required space for the copy.
Normally this "emptying the .recycled directory" process is very quick, but I have noticed that it can hang for noticable periods if I have greatly increased the number of files allowed in the .recycled directory. Most likely you are seeing a similar issue, but in this case it is the size (rather than quantity) of deleted files which is causing the problem.
I have no experience with JXFS, but I doubt it suffers the same problem, and so I predict using it will solve your problem. An alternative work-around would be to format the SFS partition with very few files being allowed in the .recycled folder (or even disable the .recycled folder entirely).
Re: SmartFileSystem 1.290 issue
Thanx a lot for the info, I haven't noticed the .recycled folder! That will actually solve my issues, because then I can empty it now and then when I'm not using it, and such get free of the annoying waiting while doing the actual work.
Re: SmartFileSystem 1.290 issue
If you use the "SFSFormat" command, you should be able to format it to have NORECYCLED .mcleppa wrote:I haven't noticed the .recycled folder! That will actually solve my issues, because then I can empty it now and then when I'm not using it
Alternatively, if you use the "SFSconfig" command, you should be able to change the number of RECYCLEDENTRIES to a suitably small number (perhaps 1 ?).
I don't think those commands come with OS4, but they should be in the ancient OS4Depot release of SFS, and I think they still work with OS4's built-in version of SFS. (Also, X1000 users can defrag their partitions using SFSdefrag, even though PartitionWizard currently doesn't work. Might be risky using an unofficial method, but it works for me - your mileage may vary!)
Re: SmartFileSystem 1.290 issue
I will format a new test partition and give this a try, maybe it can be implementd in OS4?If you use the "SFSFormat" command, you should be able to format it to have NORECYCLED .
Re: SmartFileSystem 1.290 issue
FileSystem issue still on my Amiga, altrough for now i can replicate the issue mostly when i start YAM, ehm to be honest anytime i start YAM !
This is the error i got:
As i said in my first post such error appear since i update SmartFileSystem to version 1.290, to be noted also that the system still working perfectly fine after that
This is the error i got:
Sadly I can't do any grab because the system will not respond until i close the popup requester.SmartFilesystem DH1: (sii3114ide.device, unit 0)
findextentbnode: line 2186 findbnode() can't find key 22741182!
error=0 * returned_bnode=59425684 (*returned_bnode)->key=22741177
As i said in my first post such error appear since i update SmartFileSystem to version 1.290, to be noted also that the system still working perfectly fine after that
Re: SmartFileSystem 1.290 issue
I just found this thread. Some time back I had the same issue samo79 has. I coincides with the timeframe I installed Update 5. I thought it to be a drive problem, and since I had a backup, I formatted the partition and used it as cache drive. After a while i noticed no error appeared I copied all the data back again and I'm still using the drive to this day. I had no errors eversince, so as seemingly formatting helps to solve the issue, IMHO it very likely points to a FS issue.samo79 wrote:FileSystem issue still on my Amiga, altrough for now i can replicate the issue mostly when i start YAM, ehm to be honest anytime i start YAM !
This is the error i got:
Sadly I can't do any grab because the system will not respond until i close the popup requester.SmartFilesystem DH1: (sii3114ide.device, unit 0)
findextentbnode: line 2186 findbnode() can't find key 22741182!
error=0 * returned_bnode=59425684 (*returned_bnode)->key=22741177
As i said in my first post such error appear since i update SmartFileSystem to version 1.290, to be noted also that the system still working perfectly fine after that
Re: SmartFileSystem 1.290 issue
So it seems we need a quick format before switching from SFS 1.289 to the latest 1.290 (?) 
