Text Editing Problem in RT-AC68R

[mtrains]

I was editing a .m3u playlist file sitting on the drive connected to the router using Textpad on Windows 8.1. When I saved it, it said it is saved, but if I reopen the file I see that the changes are not committed to the file. I am using NTFS format on the drive.

I have seen this on the 36 beta1 firmware. But user 'mosou' who reported the same problem in the AC Routers forum has seen it on .454 and .501 and possibly earlier versions also. So it seems to be a problem with the base Asus code that was inherited by 36 beta1.

 

[RMerlin]

I was editing a .m3u playlist file sitting on the drive connected to the router using Textpad on Windows 8.1. When I saved it, it said it is saved, but if I reopen the file I see that the changes are not committed to the file. I am using NTFS format on the drive.

I have seen this on the 36 beta1 firmware. But user 'mosou' who reported the same problem in the AC Routers forum has seen it on .454 and .501 and possibly earlier versions also. So it seems to be a problem with the base Asus code that was inherited by 36 beta1.

Quite frankly, NTFS write support under Linux just sucks, and it always will since Microsoft is keeping everything closed source. Stick with ext3 for anything that involves writing if you value your data integrity.

I certainly don't trust my data to a filesystem that had to be reverse-engineered.

The Paragon NTFS driver is closed source, so nothing that can be done there.

 

[mtrains]

Quite frankly, NTFS write support under Linux just sucks, and it always will since Microsoft is keeping everything closed source. Stick with ext3 for anything that involves writing if you value your data integrity.

I certainly don't trust my data to a filesystem that had to be reverse-engineered.

The Paragon NTFS driver is closed source, so nothing that can be done there.

Thanks for the advice. I will look into reformatting the drive with ext3. I need to educate myself on the various ext formats before I venture into it.

But it looks like this problem is happening on ext4 format also. Not knowing the difference between ext3 and ext4 I would think that the problem will happen on ext3 also.