If POSIX is undefined in this regard then we should also be opening bug reports with the developers who have this problem.
I see people here complaining about GNOME, I looked through their bugs and couldn't find any one reporting this. For people who would want to run with the special ext4 mount option that would speed up their system, it might be a good idea to open a bug. Following that train of thought, Theo says KDE has the same problem, although no one here has mentioned it. I use KDE and if this is a design flaw I'd like it fixed so ext4 can be mounted with the faster mount option. I searched through the KDE bugs and only found people complaining that KDE fdatasyncs too often (preventing their laptop hard drive from spinning down). I also ran across closed reports of people saying it fsyncs too often. Has anyone seen the 0 byte truncation issue with KDE, or is Theo just assuming since GNOME does it, KDE must also? -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
