Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Amiga Software News => Topic started by: MichielP on April 10, 2011, 06:02:54 PM
-
Good news: I just uploaded PFS3 and sources to Aminet.
Enjoy!
Michiel Pelt
author of PFS3
-
Excellent news! Thank you for making your software available.
-edit-
Not showing up yet, how long does it usually take?
-
Excellent news. There most certainly will be a MorphOS port at least, and license permitting it will be included in future MorphOS releases directly.
Current 68k PFS3 already works fine in MorphOS so there shouldn't be any major trouble porting it.
-
Hooray, thanks! ...although I do already have a commercial copy kicking around somewhere.
@ Piru and/or MichielP
How is PFS in terms of maximum file/partition/drive size?
-
How is PFS in terms of maximum file/partition/drive size?
Filesize limit is 2GiB-1 bytes. Partition size limit (about) 107GiB. HDD size limit is 2TiB as far as I can remember.
Once the current PFS3 is running we'll probably look into cause of those limits and see if it might be possible to adjust them. That'd lead into binary incompatible new version though.
So even if a new incompatible version is created we'll also keep a version compatible with the "original" PFS3 around for sure (so that you can easily mount legacy AmigaOS PFS3 partitions).
-
Thanks Michiel - highly appreciated!
-
Thank you... :)
Need to download it now and compare it against SmartFileSystem and see which one really is the best... :)
-
Thanks a lot Michiel!!!!!!!! Merci.
[UPDATE] and thanks to Gulliver too!
-
Thank you very much!
-
great! thanks a lot.:)))))))))))))
using pfs3 since some time i noticed strange attitude to refuse overwriting files, ie looks like certain file (library) v.1 gets overwritten by v.2, but after reboot v.1 is avaliable again instead of v.2. must have something to do with the recovery option, maybe some wrong setting. does anybody else experienced it?
-
Good news: I just uploaded PFS3 and sources to Aminet.
Enjoy!
Excellent!!! Is there any bugs fixed in the new version? Do you want bugs reported to you still? Thanks.
-
Once the current PFS3 is running we'll probably look into cause of those limits and see if it might be possible to adjust them. That'd lead into binary incompatible new version though.
And unlike with SFS, it would be nice if there was a SINGLE "ng" codebase available for all platforms (68k, MorphOS, AmigaOS4, AROS) so there would be absolutely no compatibility issues...
-
Hallellujah!!!!!! :banana:
Michiel Pelt for President of the Amigaverse!!! :bow: :bowdown: :knuddel:
-
Thanks, for share your fantastic job.
-
And unlike with SFS, it would be nice if there was a SINGLE "ng" codebase available for all platforms (68k, MorphOS, AmigaOS4, AROS) so there would be absolutely no compatibility issues...
+1
-
Awesome news. Thanks so much.
-
Yay!
Thank you so very much! :D
-
And unlike with SFS, it would be nice if there was a SINGLE "ng" codebase available for all platforms (68k, MorphOS, AmigaOS4, AROS) so there would be absolutely no compatibility issues...
I certainly hope so, though one can't speak for the guy who forked SFS and made it incompatible with the 68k/AROS/MorphOS versions.
-
i noticed strange attitude to refuse overwriting files, ie looks like certain file (library) v.1 gets overwritten by v.2, but after reboot v.1 is avaliable again instead of v.2. must have something to do with the recovery option, maybe some wrong setting. does anybody else experienced it?
This happens if you don't wait long enough for the writes to get committed to the disk. Wait couple of seconds more before rebooting and the problem goes away.
-
I wonder if that is a "commitment" problem or a "write-cache" problem.
-
Thank you, Michiel! Just in time for my two new 8GB CF drives which I plan on preparing and installing this week.
-
I wonder if that is a "commitment" problem or a "write-cache" problem.
It's a commit problem and not a write cache problem. Write cache is disabled by default, and needs to be specifically enabled.
PFS3 relies on the atomic commit of the HDD. Use of any sort of write cache that changes the order of which the writes are written to the HDD (be it in HW or SW) will endanger the filesystem integrity. If it would be a write cache problem you'd end up with a totally corrupt FS rather than a missing file.
To reiterate: You get the old file because the filesystem automatically reverts to the state before the final commit. When this happens the filesystem integrity stays intact, but you lose the latest changes to the filesystem. It's far better than losing the filesystem integrity for sure. Also, I have plans to add resethandler support to the FS, making it write out the remaining data to the HDD before letting the system to continue with the reset.
-
Thank you for your explanation Piru.
I had been theorizing that PFS3 secretly had a tiny write-cache. That would explain the super tremendous speed of PFS3 and wawrzon's problem.
In any event I hope that PFS3 gives you many hours of coding pleasure. :)
-
I have plans to add resethandler support to the FS, making it write out the remaining data to the HDD before letting the system to continue with the reset.
That sounds very gr00vy!!
-
Thank you Michiel !!!
-
Thank you Mr Pelt. Your FS is legendary in the amiga world... So this is availble on aminet for free now or just sources? I'll have to change over my FFS partitions to PFS now :)
-
Thankyou muchy
-
So for those of us who aren't smart, how do you change the file system of a partition?
-
Excellent! Many years of happy use here, without a single hiccup. Thank you!
So for those of us who aren't smart, how do you change the file system of a partition?
The PFS3 docs are very good, that's where I would start. It's not terribly difficult, but you'll need to reformat. It's worth it, the difference in performance (especially from FFS) is instantly obvious.
-
Double Plus Good!!!
I've heard great things about this software, at last I can finally check it out for my self (because I was too cheap to register). Thank you very much!
-
So for those of us who aren't smart, how do you change the file system of a partition?
Generally... all you should have to do is install PFS3 on the system you're using and then select the partition you'd like to make a PFS3 partition and with the likes of HDToolbox set that partition to PFS3, save the changes to the disks RDB then do a quick format of the partition... :)
Remember of course to backup anything first from the partition that you want to keep... :)
-
Excellent. This might be a stupid question, but I can update one partition to PFS, test it out, then do the others right?
That way I can do backups etc, a bit at a time.
-
And what I am wondering, is if I could take an 8Gb CF card, plug it into my MorphOS machine, partition it and format it with this file system, then plug it into my Amiga 1200 or what ever, and be able to do a WorkBench 3.1 install onto it.
Or, would I need to make a custom boot disk for my Amiga, then do the dirty work from there?
-
many thnaks..I'd like to mess around with it once I get my 1200 back up & running:)
-
Excellent. This might be a stupid question, but I can update one partition to PFS, test it out, then do the others right?
That way I can do backups etc, a bit at a time.
Yes, given that PFS3 will fit on your RDB. Try and add it with any filesystems you already have installed, then you'll see.
And what I am wondering, is if I could take an 8Gb CF card, plug it into my MorphOS machine, partition it and format it with this file system, then plug it into my Amiga 1200 or what ever, and be able to do a WorkBench 3.1 install onto it.
Yes.
Or, would I need to make a custom boot disk for my Amiga, then do the dirty work from there?
That is also a possibility, but MOS should do fine.
-
Thanks for the release of this great file system for the Amiga!
-
@Michiel
Many thx!
@Piru
Great news :)
-
Excellent news. There most certainly will be a MorphOS port at least, and license permitting it will be included in future MorphOS releases directly.
Current 68k PFS3 already works fine in MorphOS so there shouldn't be any major trouble porting it.
It has a BSD license. So yes, you can include it in MorphOS, and yes, you can modify it for your needs.
Michiel
-
I just noticed PFs3 + sources really appeared in the recent uploads list:
m68k-amigaos PFS3 V5.1 (http://aminet.net/package/disk/misc/PFS3)
generic Sources of PFS3 (http://aminet.net/package/disk/misc/PFS3src)
Thanks Michiel!
-
Filesize limit is 2GiB-1 bytes. Partition size limit (about) 107GiB. HDD size limit is 2TiB as far as I can remember.
Once the current PFS3 is running we'll probably look into cause of those limits and see if it might be possible to adjust them. That'd lead into binary incompatible new version though.
So even if a new incompatible version is created we'll also keep a version compatible with the "original" PFS3 around for sure (so that you can easily mount legacy AmigaOS PFS3 partitions).
There are two PFS3 versions (actually more, but not relevant to this discussion), one that uses the standard disk interface and one that uses direct scsi. The standard disk interface version obviously doesn't support large file or partitions because it uses a 32 bit partition offset in bytes. So there you have the maximum.
The direct SCSI version also uses 32 bit offsets, but here the offset is not in bytes, but in 512 blocks. So there you have 2TB. In theory at least. At the time PFS was released such disks did not exist, so this was not actually tested.
A few problems with large disks have already been reported and I intend to have a look at it.
-
It is good to see there are some people interested in extending PFS and bugfixing. The potential problem of separate incompatible PFS versions has been raised. How about collaborating - enhance PFS together instead of spreading our efforts into subprojects. I could set up a public domain source repository. Github perhaps, or something similar.
Please note that this only makes sense to me if there are at least some people intending to participate. Please let met know.
Michiel
-
A few problems with large disks have already been reported and I intend to have a look at it.
Have you given any thought to how any future updates to the source code would be distributed? New uploads to aminet would be okay I guess, but something like a SVN repository would be even better. How about creating a project in sourceforge or so?
EDIT: heh, you got there first... :-)
-
Please note that this only makes sense to me if there are at least some people intending to participate. Please let met know.
Piru is a hardcore coder. He will totally help you. I vouch for him.
You can safely set up a repository. No need to delay. :)
-
@Admins
This GENUINE "Amiga news" doesn't show up at the top of the home page, yet drivel from CUSA recently did.
Problem? ;)
-
It is good to see there are some people interested in extending PFS and bugfixing. The potential problem of separate incompatible PFS versions has been raised. How about collaborating - enhance PFS together instead of spreading our efforts into subprojects. I could set up a public domain source repository. Github perhaps, or something similar.
Please note that this only makes sense to me if there are at least some people intending to participate. Please let met know.
Michiel
I would be very interested to participate. Years ago I already did some (private) binary patch to PFS3 to avoid certain "beta warning requester" that would pop up if large amounts of changes were committed to the FS (for instance if you deleted more than 1GB of data in a one go you'd easily get this requester). I did this by raising some buffer size. It raised the memory usage but made it possible to delete large amounts (tens of GBs) without any issues. (quick search: It appears to be that ResToBeFreed /* this should never happen */ does happen in some cases :) Anyhoo now I can see that my patch modified RTBF_CACHE_SIZE for the allocation and the comparison.)
Also I've already mentioned the resethandler improvement I'd like to add. Additionally I'd like to include support for the MorphOS 64bit dospacket interface (even though the FS itself only supports 32bit file sizes so far).
Also improvements to softlink support would be nice thing to have. At least making it work closer to how FFS works.
However, I'll be able to work on this may the earliest.
-
@Admins
I was noticing the same thing that Nicholas noticed.
-
Good news: I just uploaded PFS3 and sources to Aminet.
Enjoy!
Michiel Pelt
author of PFS3
Thanks for releasing PFS3 for free.
I just thought I would post and let you know that its not just the classic and next gen OS4/MorphOS users that are interested in using PFS, us next gen 68k users with our FPGA amigas such as the Minimig are also interested.
I have just tested it on my 68000 Minimig and it makes a very noticeable speed increase when using it with my stock 2MB Minimig and unlike SFS I can use it as it does not need an 020 or higher.
Sadly the stock Minimig only has 1.5MB of usable ram after loading kickstart so PFS3 300K memory usage is a bit limiting, but on my 4MB minimig and newer FPGA amiga re-implementations I am sure this will be far less of an issue.
Thanks again for all the hard work :-)
-
@Admins
I was noticing the same thing that Nicholas noticed.
It's still not showing. :/
-
Has been several hours:
http://aminet.net/disk/misc/PFS3.lha
-
Information from the Readmes:
The binary version in the release is PFS3 V5.1 (with some changes for public domain release) - you need the patch also available on Aminet to update it to V5.3.
Also the sources are for PFS3 V5.2 (with some changes for public domain release).
@MichielP
Thanks heaps for this release!!!
I guess you could not find/extract the sources for PFS3 V5.3? Will any of those bugs fixed as described in the V5.3 patch readme have to be refixed in the source?
-
@Admins
This GENUINE "Amiga news" doesn't show up at the top of the home page, yet drivel from CUSA recently did.
Problem? ;)
*bump test*
-edit-
Shows up in the news section on the front page, but not the recent threads. Wonder if it's an either/or thing...
-
This is honestly great news. Thank you so much.
I had just finished the photos of my A1000 system to put it up for sale. I guess I'll re-think that move.
-
Thank you Michiel. I'll give it a whirl on my A4000.
:)
-
Thank you Michiel!!! Lots of thanks!
-
Thanks for this nice software release.
I'm trying to upgrade from v5.1 to 5.3 but it's asking for the cd??
How can I upgrade to v.5.3 ?
I want to install this nice pice of software in my new FPGA Replayboard (i'm installing now).
-
Michiel, Ma Belle...
WD
-
I just put PFS on sourceforge. See the new thread I created for this.
-
I just put PFS on sourceforge. See the new thread I created for this.
http://sourceforge.net/projects/pfs-amiga/
:)
-
@Piru
If you doesn't mind, plz, ifdefs all morphos-only specific changes (such as you mention "Additionally I'd like to include support for the MorphOS 64bit dospacket interface (even though the FS itself only supports 32bit file sizes so far"). All the other changes i think should be usable on both oses with no problems.
-
@Piru
If you doesn't mind, plz, ifdefs all morphos-only specific changes (such as you mention "Additionally I'd like to include support for the MorphOS 64bit dospacket interface (even though the FS itself only supports 32bit file sizes so far"). All the other changes i think should be usable on both oses with no problems.
Not both, but all. I am fairly sure AROS guys are interested as well.
And of course all OS specific changes must not break other builds. As I said elsewhere: "I propose that anyone committing changes must always make sure that the 68k version still builds with the changes."
-
Thanks!
-
Thanks very much Michiel :)
:pint:
-
Thanks for this nice software release.
I'm trying to upgrade from v5.1 to 5.3 but it's asking for the cd??
How can I upgrade to v.5.3 ?
I want to install this nice pice of software in my new FPGA Replayboard (i'm installing now).
Good question. I guess I have to fix that :hammer:
-
Not both, but all. I am fairly sure AROS guys are interested as well.
Indeed. Perhaps not exclusively AROS related but Toni Willen plans to adapt PFS3 to make it compatible with AmigaOS1.3.
-
Good question. I guess I have to fix that :hammer:
I just want to say thanks so much for your awesome donation to the community. I really wish there was more educated programers like yourself resurfacing to aid the community.
-
Thanks a lot for this fine piece of software!
-
Good news: I just uploaded PFS3 and sources to Aminet.
Enjoy!
Michiel Pelt
author of PFS3
Thank you very kind really looking to trying for first time
-
Indeed. Perhaps not exclusively AROS related but Toni Willen plans to adapt PFS3 to make it compatible with AmigaOS1.3.
Very cool. :-)
It would also be nice for us users with far more limited Amiga's if a version
with a lower memory foot print could be created PFS3 150K memory requirement is just too high to be useful on a Minimig with only 1.5M (or my 1MB A500 with external HD) of usable but a version with a similar memory foot print to FFS would be very useful if it PFS3 could be slimmed down a bit.
-
Very cool. :-)
It would also be nice for us users with far more limited Amiga's if a version
with a lower memory foot print could be created PFS3 150K memory requirement is just too high to be useful on a Minimig with only 1.5M (or my 1MB A500 with external HD) of usable but a version with a similar memory foot print to FFS would be very useful if it PFS3 could be slimmed down a bit.
Increasing the maximum partition size and file size also increases the memory footprint. PFS already what is called internally as smallmode which is used if the partition is 4G or smaller. Smallmode has a smaller memory footprint. Perhaps we can reduce it further. However, PFS will always need more than FFS to be able to do the atomic commit scheme.
-
Good question. I guess I have to fix that :hammer:
Regarding the 5.3 patch requesting the CD and a serial. I have been able to circumvent the CD request by assigning PFS3: to the directory in which the PFS3 installer is extracted (ie RAM:pfs3,) but I cannot circumvent the serial request.
Any fix to this, yet?
-
Not yet LoadWB. Assign was easy but spatch can't patch the L: files and C: PFSDoctor.
Tried them even manually but didn't work.
Even if you supply a valid Key it still doesn't patch it (cause I guess it needs to find the same Key in the original unpatched files).
Michiel said that he have to fix that (some posts back :))
-
If anyone is interested. I have a modified spatch from years ago that doesn't do CRC checking.
Would be a bad idea to put it on Aminet though.
This might be able to patch PFS3 but i'm just going to guess here that since it'd be patching something likely built with a different compiling environment (no matter how insignificant the difference might be) and slightly changed sources, that the result would just be garbage.
-
If anyone is interested. I have a modified spatch from years ago that doesn't do CRC checking.
Would be a bad idea to put it on Aminet though.
This might be able to patch PFS3 but i'm just going to guess here that since it'd be patching something likely built with a different compiling environment (no matter how insignificant the difference might be) and slightly changed sources, that the result would just be garbage.
This might work. The reason spatch doesn't work is that the binaries on the Aminet release are already registered with a registration number. The patches are from the unregistered binaries from the CD. So the binaries differ and so the CRCs differ. But if you use your non-checking spatch and be very careful to apply the right patch to the right file it might just work.
You can also hold on and wait - I will post updated binaries, the complete package, not a patch, in a few days.
Michiel