Any interest in a bounty for a native ext2/ext3 file system?

@Raziel

Check your PMs.

@salass00

You too

@Raziel

Replied.

@salass00

...and finally the answer, sorry for the delay

@salass00

Well, the third party ext2 I've been using for a year was kinda left in a beta state of its own and it works well enough to accomplish what it needs. If your version is at a similar state then I'd be happy to test/use it as I been using the other implemetation which has drawbacks and works ok only if used with a ext2/3 partition on a rdb partition table.

It seems they added the Xattr to the current version (not 1.43) as it causes me issues when I switch to AOS.

Thanks for your work.

man morphos has had this for years!

@magnetic

Linux has had it for far longer still, so what's your point?

I only do Amiga programming as a hobby and not as some stupid contest to compete with MorphOS/AROS/Windows or whatever.

FWIW the only issues currently stopping a release are to do with the write mode which the fuse-ext2 author explicitly warns against using (you even have to use a force switch to enable it).

If I was happy with just releasing just a read-only filesystem I could do that right now but I'm not sure how that would be received and also I'm a bit lazy.

The current AOS third party implementation lets you write if you follow procedure and format and even fix it on the Linux side - as long as you managed the partition first on the AOS side and made it on a RDB. They changed something recently on the Linux side so when I have a ext3 partition on a MBR and try to write to it on AOS it says something about Inode 2 and that I can't write because of unsupported features. I think they changed something so the format command on Linux adds extra parameter/s.

e2fsprogs (1.43~WIP.2016.03.15-2) sid; urgency=low

* Fix FTBFS on big-endian systems

-- Theodore Y. Ts'o <tytso@mit.edu> Thu, 17 Mar 2016 22:55:52 -0400

e2fsprogs (1.43~WIP.2016.03.15-1) unstable; urgency=low

* New upstream release
* Fix resize2fs bug that could leave block allocation bitmaps
uninitialized
* The tune2fs program will ask the user for confirmation before
starting dangerous operations if the terminal is available, and it
will replay the journal if necessary
* Fix a bug which in rare cases would cause e2fsck -fD to corrupt an
extent-mapped directory.
* E2fsck will now check for extent mapped inodes with no extent header
and clear them if found
* E2fsck now checks to make sure the extended attribute header doesn't
result in the xattr extending beyond the bounds of the inode
* Teach mke2fs to parse a human-readable argument for -i option
* Teach mke2fs to automatically handle creating file systems > 500T by
automatically enable the meta_bg feature
* Mke2fs will now prompt for user verification before rewriting a file
system's superblock using the -S option
* Mke2fs no longer complains if the user tries to create a file system
using the entire block device (e.g., without using a partition).
The minor number convention is not used by all block devices, and
it's quite normal in some circumstances to create a file system
on /dev/sdc instead of /dev/sdc1
* Debugfs now can properly display and set extended timestamps
* Add an ext2/3/4 FUSE server
* Fix an "mke2fs -d" bug which could create inodes with invalid
extended attribute blocks
* Fix miscellaneous file encryption bugs
* Fix miscellaneous MMP bugs in debugfs
* The e2fsck program will no longer update the quota inodes when it is
interrupted
* The filefrag program now accounts for holes in sparse files created
by the file punch operation as an expected/optimal mapping
* Clean up gcc/clang warnings
* Add support for the checksum seed feature
* Add support for the project quota feature
* Add fallocate support to libext2fs and to debugfs
* Clean up various man pages (Closes: #798425)
* Update debian policy compliance to 3.9.7

Time for an update?

Just bought an Ext driver for the PC. Just saying...

@salass00 Quote:
I'm sure that a read-only filesystem is MUCH more useful than no filesystem at all! (And adding write support to a filesystem is so much more complex, that I think releasing a read-only version is well worth it.)

Not that I personally have any immediate need for an ext2/ext3 filesystem... but you never know what you might need in the future :)

The fuse-ext2 port is now updated to use e2fsprogs version 1.43.3.

As the latest version now requires newer versions of diskio.library, filesysbox.library and newlib.library than are available in AmigaOS 4.1 FE a public release might not be possible until AmigaOS 4.2.

This might be because of added attributes on that version format command, right? because eventually you format it properly on the Linux side. Could a previous version format command, work with current libraries? I've been experiencing a one-way Ext3 partition after that e2fs version came out - can only copy to it on the Linux side.

@salass00

Could you share a changelog since the last release, please?

Especially interested if utf-8 support is in?

@salass00

Th ntfschk prorgam now crashes reproducable every time...no matter if used on a ntfs partition or simply trying to get information out of it. ("ntfschk ?")

Are there plans to rebuild the tools to make it work again without crashing or do we have to wait for AmigaOS4.2 and a new release of the package?

Not sure if it started to behave like this with update 1, but it used to work before

Also, there is version 1.43.4-2 available

@salass00

Any comment?

@salass00

I take it we can forget about this software then...